The Volla 22 (Gigaset GS5) Thread

[Seven.of.nine]

@jenix

the front camera in the top middle, some of the screen content isn’t displayed properly. The major issue with that is that the clock (which sits in the middle of the top bar) gets completely covered by the front camera.

This can be solved easily. This is not my work, all honours to @poetaster , wo gave me the hint!

Quick ‘n’ easy:

File is /usr/share/lipstick-jolla-home-qt5/statusarea/StatusArea.qml

In line 88 there is:
x: Math.max((iconBar.width - width)/2 - parent.x, 0)
Replace old content with:
x: (parent.width - width)/2 + width + (width /2)

Then restart GUI with SF utilities.

Many thanks to @poetaster !

I did it successfully an an old Volla (GS290). The line number may differ depending on SFOS version. It is line 111 on Volla / 4.4.0.72 + 64 and line 88 in SFOS 4.5.0.19.

edit:

@jenix

Unfortunately, I noticed that the volume buttons are not working in SFOS. The physical press seems to get detected. When the phone is suspended (sleep mode) and I press one of the buttons (Vol Up in this case), there is a wakeup event in the journal:

Does your phone wake up from sleeping/standby on short pressing the Power button or touch fingerprint sensor? As I know, it’s not the planned way to wake up the device by Volume buttons.

[poetaster]

@Seven.of.nine

This is not my work, all honours to @poetaster

I believe I got it from: Project: nocentralclock

@jenix

Unfortunately, I noticed that the volume buttons are not working in SFOS.

Just to forgo working on a release that can be updated anyway, I’d try updating to 4.5.0.19

ssu re 4.5.0.19 
ssu ur
zypper ref
zypper dup

Of course make sure it was the Halium Mimameid image and not the original Volla that you flashed?

My Rephone, also originally flashed with 4.4.0.72 the volume buttons worked as expected.

One last question, you made sure to use encryption for the home partition?

[jenix]

Thanks for the reply.
I installed the Mimameid image from Artifacts · sailfishos-porters-ci / Halium Mimameid Ci · GitLab (the one from pipeline #899010251). I also upgraded my device to SFOS 4.5.0.21, this seems to have been my fault. After downgrading to 4.5.0.19, the droid-config-halium-mimameid-policy-settings was installed again and the volume keys are working again.
So, I learned the important lesson to only upgrade to device-specific version Btw, is there a place where I can see which versions are available?

The answer regarding encryption may be irrelevant, but yez, I have enabled it during the initial setup.

[jenix]

One thing I noticed during the upgrade: zypper is complaining about a missing GPG key to check the signatures of packages:

Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY

Is it be possible to include the key into the image? Or can I at least import it myself?

[poetaster]

@jenix

Is it be possible to include the key into the image? Or can I at least import it myself?

I think the gpg signing issue is general. It’s just not implemented It’s a topic of discussion that’s ongoing and one of the hopes that I had for Chum, that we’d go in the direction of properly signed packages. But it is non-trivial.

[jenix]

I see. That’s unfortunate, let’s hope there will some development in the future.

Are there any updates on the issue that BLE (bluetooth low energy) devices are not recognized? That’s my last big hurdle into making the Volla / Rephone my daily driver.

This and hopefully finding a better browser than the stock one. Compared to Fennec it is inferior (no addons, hardly no privacy setttings, a lot of crashing).

Also, I noticed in ‘top’ that my phone constantly has a load of around 30. This does not seem to be cpu load releated, so I presume it is some I/O. Does anybody know if this is normal?

[poetaster]

@jenix

Are there any updates on the issue that BLE (bluetooth low energy) devices are not recognized? That’s my last big hurdle into making the Volla / Rephone my daily driver.

That’s one for @piggz … I think it may matter to him as well since he uses some devices that might be of that class?

@jenix

This and hopefully finding a better browser than the stock one. Compared to Fennec it is inferior (no addons, hardly no privacy setttings, a lot of crashing).

The coming 4.5.0.21 update should fix most of the core browser issues. I have Angelfish (chum) installed and it is more stable than the stock browser.

@jenix

Also, I noticed in ‘top’ that my phone constantly has a load of around 30. This does not seem to be cpu load releated, so I presume it is some I/O. Does anybody know if this is normal?

This is indeed really odd and I’ve been trying to figure it out for 6 months. I did some ‘minimal use’ testing and actually got 5+ days out of the GS5 but, still. I noticed that the behaviour was more extreme on 4.4.0.72 than 4.5.0.16/18 (can’t remember exactly). With 4.5.0.19 the spiking at 100% on multiple cores seems to almost be normal when the display is on (!), logged in, and the spiking takes place almost entirely when the phone screen is off / you’re logged out. Very strange. @piggz any idea? I’m guessing sensor stuff / waiting for wake foo.

[Pasik2]

@jenix

Are there any updates on the issue that BLE (bluetooth low energy) devices are not recognized? That’s my last big hurdle into making the Volla / Rephone my daily driver.

The same problem seems to exist in other Volla models (original Volla Phone and Volla Phone X). With X23 I don’t know, because I don’t have it.

[poetaster]

@piggz … the last couple of days I’ve been checking the data counters since it seemed that wifi traffic was consuming much more power than LTE. Over a period of 2 days, 4G/LTE only I have number like 10.3 MB up / 143.4 MB down. WLAN on for 2 days I have 8 GB up and 8.2 GB down. Same kind of usage (ie. reading rss feeds and wikipedia). I think the constant acitivity we’ve noted is conman and it’s pretty extreme. It really sucks battery.

[piggz]

With X23, BLE works fine … X23 is now my DD as it can connect to my watch. Suffice to say, we dont know why it doesnt work on other volla models, but i think the same applies to UBPorts

[jenix]

I can confirm this observation. I was already puzzled why my phone uses so much more battery when it is located at home (connected to my wifi). The data counter currently show about 900GB of traffic, both download and upload (so a total of 1.8 TB) since I installed my phone 10 days ago.
Interesting to note is that my wifi controller does not show a lot of traffic from the phone, so I presume this is related to interface configuration or control messages.

I also noticed a lot of repeating system journal entries of the following kind:

Aug 01 08:21:12 Phone22 kernel: -(1)[0:swapper/1][name:spm&][SPM] IdleBus26m wake up by  R12_SYS_TIMER_EVENT_B, timer_out = 29, r13 = 0x6046000, debug_flag = 0x1910f0 0x0, r12 = 0x10000, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x1ff,  req_sta =  0x2000400, event_reg = 0x90100000, isr = 0x0, raw_ext_sta = 0x4005a0a5, wake_misc = 0x0, pcm_flag = 0x204182 0x0, req = 0x0
Aug 01 08:21:12 Phone22 kernel: -(0)[0:swapper/0][name:spm&]Power/swap op_cond = 0x1
Aug 01 08:21:12 Phone22 kernel: -(0)[0:swapper/0][name:spm&][SPM] IdleBus26m wake up by  R12_SCP_IPC_MD2SPM_B, timer_out = 7, r13 = 0x6046000, debug_flag = 0x11000 0x0, r12 = 0x800, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x1ff,  req_sta =  0x2000400, event_reg = 0x30000000, isr = 0x0, raw_ext_sta = 0x4005a0a5, wake_misc = 0x0, pcm_flag = 0x204182 0x0, req = 0x0
Aug 01 08:21:15 Phone22 kernel: -(1)[0:swapper/1][name:spm&]Power/swap op_cond = 0x1
Aug 01 08:21:15 Phone22 kernel: -(1)[0:swapper/1][name:spm&][SPM] IdleBus26m wake up by  R12_SYS_TIMER_EVENT_B, timer_out = 496, r13 = 0x6046000, debug_flag = 0x1910f0 0x0, r12 = 0x10000, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x1ff,  req_sta =  0x2000400, event_reg = 0x90100000, isr = 0x0, raw_ext_sta = 0x4005a0a5, wake_misc = 0x0, pcm_flag = 0x204182 0x0, req = 0x0
Aug 01 08:21:15 Phone22 kernel: -(1)[0:swapper/1][name:spm&]Power/swap op_cond = 0x1
Aug 01 08:21:15 Phone22 kernel: -(1)[0:swapper/1][name:spm&][SPM] IdleBus26m wake up by  R12_CONN2AP_SPM_WAKEUP_B, timer_out = 7, r13 = 0xa604e010, debug_flag = 0x11000 0x0, r12 = 0x20, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x1ff,  req_sta =  0x2000700, event_reg = 0x30000000, isr = 0x0, raw_ext_sta = 0x80059095, wake_misc = 0x0, pcm_flag = 0x204182 0x0, req = 0x0
Aug 01 08:21:18 Phone22 kernel: -(0)[0:swapper/0][name:spm&]Power/swap op_cond = 0x1
Aug 01 08:21:18 Phone22 kernel: -(0)[0:swapper/0][name:spm&][SPM] IdleBus26m wake up by  R12_CONN2AP_SPM_WAKEUP_B, timer_out = 7, r13 = 0xa604e010, debug_flag = 0x11000 0x0, r12 = 0x20, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x1fb,  req_sta =  0x2000700, event_reg = 0x30000000, isr = 0x0, raw_ext_sta = 0x80059095, wake_misc = 0x0, pcm_flag = 0x204182 0x0, req = 0x0

They repeat every few seconds, even when the screen is off and the phone is supposed to be in sleep mode.
I can’t see those events on my old Xperia 10 II, even though there is no SIM inside it.

[poetaster]

The phone never seems to go to sleep with wlan on: there’s also tons of:

Aug 01 14:26:29 Phone22 kernel: .(1)[1544:teei_daemon]Freezing user space processes ... 
Aug 01 14:26:29 Phone22 kernel: .(1)[1544:teei_daemon][tz_vfs][ERROR]: [tz_vfs_read][156] wait_for_completion was interrupt
Aug 01 14:26:29 Phone22 kernel: .(0)[6368:kworker/u16:8]PM: Pending Wakeup Sources: WLAN timeout 
Aug 01 14:26:29 Phone22 kernel: .(0)[6368:kworker/u16:8]Freezing of tasks aborted after 0.014 seconds

@piggz, I’ve lost track of which github repo to report to? At the current rate, the battery will be dead in less than two years. GitHub - HelloVolla/droid-hal-version-halium-mimameid ?

[jenix]

I have to correct my observation regarding the connman interface blacklist. Turns out there is an additional config file /etc/connman/main-mtk.conf which does contain the ccnmi interface and is used by connman.

[poetaster]

I also need to note that the Freezing, Error, Pending Wakeup behaviour is not the case on my Rephone. I switched DD 5 days ago and observe different behaviours. Slightly different hardware so, who knows.

I just started to use WLAN again (was on the road) with the Rephone which had this 8GB in traffic on the first activation 5 days ago. I’ll observe it now and track daily traffic.

[piggz]

4.5.0.21 is available for regular users. Ive installed it an it seems to be working. Possibly only the vibration isnt working. Not had a SIM in yet.

[ric9k]

This is great, thanks!
I’ll try when I have some time.
Have to say I had to leave the GS5 on the side, mostly because of this SIM issue.
I had to meet someone, had to reboot and it was endless until I could be reachable again.

Second important issue: the alarm has been soundless one morning, which never happened on my XA2. This is very bad as I use it to go to work.

Some minor issues:
-no GPS from Waydroid
-WD not always restarting after crash
-I couldn’t listen callrecordings.

But still:
-camera are great, sensible in low light conditions
-GPS is fast
-Big memory
-Faster device
-Big removable battery with 3 days autonomy for my usage.

Thanks @piggs!

[widex]

Hello everyone,
I updated the system to the newest version. No problems or errors. The problem with no prompt when two sim cards are enabled does exist.
Waydroid has to be reinstalled but it’s a layer 8 problem. I wanted to install spotify and destroyed the container.

Thank you @piggs for your job the os is very stable

[poetaster]

Hej! I seem to have munged something again. Just doing the ordinary ssu re/ur when I try to upgrade I get:

  droid-config-halium-devel

The following package is going to be REMOVED:
  droid-config-halium-testing

Which doesn’t look correct, or?

[piggz]

ah good catch, one moment

[poetaster]

You rock. I wait Happily.