The Volla 22 (Gigaset GS5) Thread

Hmmm. Why not? I have laptop and rephone connected to a fritzbox wlan and can start the hotspot (which I connect another phone to) and all’s well?

In any case when I tried starting the hotspot with wifi on. my rephone stopped showing up:).

I had to turn off wifi and then turn on hotspot to get a decent connection. With which this message is being sent.

Testin :slight_smile: EDIT: so it seems like, which makes sense, wifi off if you want to run a hotspot via cellular.

My ifconfig, connected to the laptop via ssh on the hotspot:

[root@Phone22 defaultuser]# ifconfig
ap0       Link encap:Ethernet  HWaddr 5A:9E:C6:3E:A4:58  
          inet6 addr: fe80::589e:c6ff:fe3e:a458/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:653 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:158281 (154.5 KiB)  TX bytes:146692 (143.2 KiB)

ccmni1    Link encap:UNSPEC  HWaddr D2-75-C7-93-6F-19-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.37.191.179  Mask:255.0.0.0
          inet6 addr: fe80::aed1:6f47:26c6:5918/64 Scope:Link
          inet6 addr: 2a02:3032:210:cedf:aed1:6f47:26c6:5918/64 Scope:Global
          UP RUNNING NOARP  MTU:1500  Metric:1
          RX packets:13318 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9999 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12695531 (12.1 MiB)  TX bytes:1163735 (1.1 MiB)

ifb0      Link encap:Ethernet  HWaddr 0A:51:17:D6:F5:6D  
          inet6 addr: fe80::851:17ff:fed6:f56d/64 Scope:Link
          UP BROADCAST RUNNING NOARP DYNAMIC  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:20 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:1400 (1.3 KiB)  TX bytes:0 (0.0 b)

ifb1      Link encap:Ethernet  HWaddr 16:F6:0C:50:C6:36  
          inet6 addr: fe80::14f6:cff:fe50:c636/64 Scope:Link
          UP BROADCAST RUNNING NOARP DYNAMIC  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:20 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:1400 (1.3 KiB)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:3580 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3580 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:400380 (390.9 KiB)  TX bytes:400380 (390.9 KiB)

rndis0    Link encap:Ethernet  HWaddr 2E:AE:C7:9C:0C:2C  
          UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tether    Link encap:Ethernet  HWaddr 5A:9E:C6:3E:A4:58  
          inet addr:172.28.172.1  Bcast:172.28.172.255  Mask:255.255.255.0
          inet6 addr: fe80::84b:7aff:fefa:a96f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:863 errors:0 dropped:0 overruns:0 frame:0
          TX packets:654 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:146971 (143.5 KiB)  TX bytes:149270 (145.7 KiB)

wlan0     Link encap:Ethernet  HWaddr 58:9E:C6:3E:A4:58  
          UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan1     Link encap:Ethernet  HWaddr 58:9E:C6:3C:A4:58  
          UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:6846 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:1398751 (1.3 MiB)  TX bytes:1136365 (1.0 MiB)

When i compare your output to mine, I can see, that wlan1 has an IP whereas your’s hasn’t. WLan was switched off. When I made the screenshot. I double checked that.

With a bit of switching on and off the wifi, I managed to get the rephone to no longer be visible. Rebooted the rephone, stopped wifi, made sure cellular was on. And now I’m connected to the hotspot again and sending this. GS5 seemed to connect a bit faster, but this seems stable.

This is the ifconfig from the rephone (the one above was from the GS5. confusing).

ap0       Link encap:Ethernet  HWaddr 5E:9E:C6:3D:1A:0E  
          inet6 addr: fe80::5c9e:c6ff:fe3d:1a0e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:779 errors:0 dropped:0 overruns:0 frame:0
          TX packets:606 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:137880 (134.6 KiB)  TX bytes:134552 (131.3 KiB)

ccmni0    Link encap:UNSPEC  HWaddr 3E-19-94-94-3D-70-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.32.55.160  Mask:255.0.0.0
          inet6 addr: fe80::1e14:c8c0:ec1c:f15f/64 Scope:Link
          inet6 addr: 2a02:3032:20d:4c57:1e14:c8c0:ec1c:f15f/64 Scope:Global
          UP RUNNING NOARP  MTU:1500  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8160 (7.9 KiB)  TX bytes:5404 (5.2 KiB)

ifb0      Link encap:Ethernet  HWaddr 76:E9:6B:CC:F0:AD  
          inet6 addr: fe80::74e9:6bff:fecc:f0ad/64 Scope:Link
          UP BROADCAST RUNNING NOARP DYNAMIC  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:9 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:630 (630.0 b)  TX bytes:0 (0.0 b)

ifb1      Link encap:Ethernet  HWaddr B2:57:56:DE:7C:59  
          inet6 addr: fe80::b057:56ff:fede:7c59/64 Scope:Link
          UP BROADCAST RUNNING NOARP DYNAMIC  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:9 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:630 (630.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2096 (2.0 KiB)  TX bytes:2096 (2.0 KiB)

rndis0    Link encap:Ethernet  HWaddr 12:55:72:98:18:A9  
          UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tether    Link encap:Ethernet  HWaddr 5E:9E:C6:3D:1A:0E  
          inet addr:172.28.172.1  Bcast:172.28.172.255  Mask:255.255.255.0
          inet6 addr: fe80::8094:d0ff:fe87:4c09/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:796 errors:0 dropped:0 overruns:0 frame:0
          TX packets:609 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:127858 (124.8 KiB)  TX bytes:137536 (134.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 58:9E:C6:3D:1A:0E  
          inet addr:192.168.178.90  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::5a9e:c6ff:fe3d:1a0e/64 Scope:Link
          inet6 addr: 2a02:8109:a788:b700:5a9e:c6ff:fe3d:1a0e/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:835 errors:0 dropped:0 overruns:0 frame:0
          TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:146686 (143.2 KiB)  TX bytes:88341 (86.2 KiB)

wlan1     Link encap:Ethernet  HWaddr 58:9E:C6:3F:1A:0E  
          UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Your phone connects to wlan0 the GS5 to wlan1. Something is very odd here. I try again with a reboot and report. If I have no success, I try it with a reflash. On the longer sight I need the hotspot functionality on my daily driver. I can abdicate android support, but not hotspot.

Ok. rephone, all comms off. connect to wifi:

32: wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
    link/ether 58:9e:c6:3d:1a:0e brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.90/24 brd 192.168.178.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 2a02:8109:a788:b700:5a9e:c6ff:fe3d:1a0e/64 scope global dynamic mngtmpaddr 
       valid_lft 7145sec preferred_lft 3545sec
    inet6 fe80::5a9e:c6ff:fe3d:1a0e/64 scope link 
       valid_lft forever preferred_lft forever

GS5 all comms off, connect to wifi:

33: wlan1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
    link/ether 58:9e:c6:3c:a4:58 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.64/24 brd 192.168.178.255 scope global wlan1
       valid_lft forever preferred_lft forever
    inet6 2a02:8109:a788:b700:5a9e:c6ff:fe3c:a458/64 scope global dynamic mngtmpaddr 
       valid_lft 6970sec preferred_lft 3370sec
    inet6 fe80::5a9e:c6ff:fe3c:a458/64 scope link 
       valid_lft forever preferred_lft forever

So I see to see similar wlan1 behaviour on the GS5 but not on the rephone. Though there is not much difference.

Maybe you should actually reflash and try with a clean slate after all.

In any case, both variants supply stable hotspots with cellular only on.

I rebooted and stopped wifi, made sure cellular was on. Rephone showed up, but no connection was possible. I’ll reflash and report in the evening the status with a freshly flashed phone.

Ok I reflashed. Nothing installed. Connected to WLan , to set up Jolla account.
Switched off WLan, turned on Hotspot The Wlan Icon Was dark, at that moment I turn on Hotspot it lights up and tells me it is connected to my Home Wifi.
I tried to connect with another device to the rephone: Not possible. I tried to turn off WLan, which leeds to switching of Hotspot. Turn on Hotspot again. Phone doesn’t show up anymore. No way to change this.
So I deleted all WLan Passwords on Phone, rebooted it. Turned on Hotspot and connected my Laptop with the Phone. Access to internet :partying_face:. Switched off Hotspot and afterwards on again: Phone doesn’t show up. :flushed: After a further reboot: Same procedere same result. I can connect exactly once to the phone, when there is no known WLan around afterwards it doesn’t show up anymore.
And now??? I’m clueless!

At least there seems to be a reliable method to use it as hotspot, but this is on the long term not suitable.
What has improved, is, that the Icon isn’t switching between WLan and mobile data. The situation with a freshly installed Sailfish connect is as well the same as before.

For today my SIM and my SD will move to the XPeria again. It takes some hours to set up all anew. And I have some appointments later on.

Ok. I’ll investigate the issues I have which are probably related:
a) can’t connect to qmllive
b) ipp printing doesn’t work (new issue).

1 Like

If I can help with anything, let me know. I’m not able to code, but with testing or other more trivial tasks I can cope with.
Short info: After updating to 4.5.0.21 the switching icon is back. At least it was for a short while. Now it looks stable again. Having things working sometimes and sometimes not, doesn’t make it easier to nail itdown.

As I told, I tried wifi hotspot from my GS5 (not lite).
The first time, it started and was seen from my SFOS XA2.
I tried to connect. It lasted long and didn’t work.
Then, my XA2 could not see the hotspot any more.
Restarting network from the Settings → Utilities allows to restart the procedure but my XA2 could not connect.
So, I took a book and a bath :sunglasses:

2 Likes

I wonder why both of mine work?! There are other issues with networking for sure. I cannot do ipp (works on the GS290/volla). I cannot connect to qmllive from the SDK. So, off I go to debug another issue.

EDIT: just tried with the GS5 again and when wifi is OFF and cellular on, hotspot works really well. Just spent a hour trying different things with it as the hotspot. Was even relatively snappy! On the otherhand, can’t print with it via wifi and seaprint :frowning:

Did anyone with a rephone make a backup of the ROM/vendor images? I, sadly, neglected to do so. Looking for the vendor binary blobs for the camera.

Sorry, no, I always start making backups, when I have a for me suitable system. In my tests with the Hostspot directly after flashing, the experience WHEN I was able to established a working connection, was as well stable and snappy.

Sorry, no, I didn’t know it was possible :frowning:

Just to get a ‘clean slate’ on the rephone, I’m going through VollaOS first and testing all functions. So far, good news:

  1. video recording works just fine in vollaOS.
  2. Wifi, Bluetooth, USB MTB work
  3. FM radio works ( :slight_smile: )
  4. Multi-boot installer running … I’ll edit this when I’ve been able to test.
  5. SIM really flaky :slight_smile:
  6. Skipping multi-boot and installing 4.4.0.72
  7. Which required re-installing vollaos again (sigh)
  8. Confirm it boots and camera video works.
  9. Realize I’m stuck in a loop. VollaOS multi-boot select with VollaOS ‘only’ even after flashing with sfos

Lesson learned, never touch multi-boot into VollaOS unless you want to be stuck with a bootloader you don’t want. Hmmmm. Anyone know how to get rid of the boot image selector!?

2 Likes

Does this help?:

Sadly not relevant to this device, though I could probably screw about with twrp for a while. But I don’t have the time for that.

Maybe asking on Volla or ubports forum helps.

I’ll go low level I guess. No worries, it just changes some ‘default’ advice I used to give or at least means a warning for what not to do.

EDIT: well, the simple solution is to remove the SD card. I also used the UT install just to see what the state was since it’s at 20 now. But, removing the SD card got me booting SFOS again.

EDIT: Sadly, video recording is still broken.

News from my side regarding network. After the reflash I’m now more or less constantly on interface wlan0. My Ip is now shown on the developer site in settings. The WLan Icon is now most of the time stable.
…And Sailfish connect works now. Not very good compared to my other devices, but it seems so far reliable. I have to set the IPs of the devices I want to connect. So no autorecognition. And I have to be patient. It takes up to two minutes until the devices show up and are getting connected. Connection quality is sometimes as well somewhat flaky, but anyway. It works at least.
I hope you get the network issues debugged. I have moved SIM Card and SD to the rephone again. :sunglasses: