Call for testing: Ubuntu Touch 24.04-1.3

[gpatel-fr]

@sixwheeledbeast said:

Bluetooth can't be disabled or enabled from the battery menu. The toggle moves but it doesn't work and stays in the same state.

Yes I see that on my FP5.
I searched a bit and I think that the problem is not in the settings, it's in the Bluetooth stack itself.
Rationale: launching bluetoothctl, I can see that when activating the switch, there is this message:

[bluetooth]# hci0 new_settings: connectable bondable ssp br/edr le secure-conn 

the interface is made 'connectable' and 'bondable'.
When activating the bluetooth in the bluetooth page, these messages are displayed:

[bluetooth]# hci0 new_settings: powered connectable bondable ssp br/edr le secure-conn 

that is, in one case the interface is powered while it's not in the second case. The switch is changed but after a few seconds when the system realizes the discrepancy between the real state of the bluetooth interface and the switch, it switches back the indicator statute.
When going from the battery page to the bluetooth page, the state is checked immediately and the switch is going back to enabled almost instantly.

While it's the same action in both case ('bluetooth-enabled') it has 2 different effects!,
I'd need to check what are the messages passing at the Dbus level in both cases.

For now it's a bit late for me, logging off.

[ralf]

Hi there,

I'm new here. I view myself as a user, not a developer, but I want to try and do my fair share to contribute. I got myself a Fairphone 4 back in December and flashed it with Ubuntu Touch and played around a bit, tried some other Custom ROMs, placed it in a drawer, forgot about it... long story short, I got the Fairphone 4 out of the drawer again last week and flashed it with the latest stable release again, that being this here 24.04-1.3

Now I observed a few bugs I wanted to share, some of them already mentioned here, some not.

• I can confirm the empty signal strength triangle. From a user's perspective, I'd not call this cosmetic, as it is highly confusing.
• I can confirm the empty release channel. It is a strange kind of fluke. I took a screenshot 5 minutes ago, however, now I cannot reproduce it and all release channels are displayed properly?
• I can confirm the Bluetooth slider in the battery menu not having an effect.

That's about what I recall from the discussion here. Now to my very own bugs.

• Battery drops from fully loaded to about 70% in about an hour. After that, power consumption looks normal.
• Phone "dead" in the morning. It's switched on and fully loaded in the evening, and the next morning the display remains black and I have to long-press the power-button to bring it back to life again.

Thinking about it, these two might coincide, and have only been observed these past two days. However, I recall having none of the above back in December.

So long

[gpatel-fr]

This MR should fix it.

Well if it's committed and backported to stable - there is some serious backlog on this repo

[stanwood]

I confirm the lost of cellular signal indication on the top bar menu (Redmi Note 9S), though all phone, sms & data do work fine.
Channel: Stable (24.04-1.3)

I did also confirm the issue on the Gitkab ticket.

[OtaDr]

I'm not sure, but I feel like after updating to 24.04-1.3 (Pixel 3a XL),
the battery drain is significantly higher, or maybe the battery indicator is showing something different.
Has anyone else experienced this?

[ralf]

@OtaDr I actually do have the feeling that the battery indicator is not very relyable anymore.
I mean, see screenshot, how is this normal?
It charges from about 50% to 100% in a straight vertical line, discharges normally over night, then randomly decides to discharge quicker? Mind you, I didn't use this phone at all throughout the day, it was just lying on my desk...

[OtaDr]

My graph looks similar
Before the x.1.2 update, I had 70–60% at the end of the day; now, after the x.1.3 update, it shows 50–40%

[gpatel-fr]

@ralf

from your description of your usage, I'd say that it's a bit early to affirm that there is a problem with the battery indicator. What I gathered of your post is that you bought a FP4 in december last year - so it's a used device with an unknown years of use (or abuse: it's well known that not using a li-ion battery carefully leads to signficantly reduced usable life), you used the phone for a few days then set it in a drawer and with the last update of UT 2 weeks ago flashed it again.
That's not enough to be confident that there is a problem in the software and not in the hardware IMO. Strange patterns of charge/discharge are usual for damaged batteries.

As of myself, I have a FP5 since I bought it new 8 months ago, used it every day, I can't confirm a marked change since 24.04-1.3. This phone was energy hungry before, particularly if every feature is on, and it's still the case, no more or less as far as I can tell.

[ralf]

@gpatel-fr
Hi, thanks for the reply.
It was a new device purchased from Amazon.
Not pre-owned nor refurbished.
I recall the battery drainage to have been more consistent on previous releases.

I'm sorry if by abbreviating my story, some details might have been lost.
About two weeks ago I tried to make the Fairphone with Ubuntu Touch my daily driver, and I had consistent battery drainage then, similar to what @otadr described.
As I need some Android Apps for work, I tried to live with waydroid for some time, but ultimately decided against it.
Wednesday last week I went on a flashing spree which led me from LineageOS via /e/OS to IodeOS and back to Ubuntu Touch, just in time for the 24.04-1.3.
I did not observe this battery drainage on the previous Ubuntu Touch release, nor on the other ROMs.

Cheers

[Linus67]

On the subject of battery consumption. It is very difficult to compare battery consumption when devices are being used simultaneously.

I only test and compare battery consumption under identical conditions without active use (for example, at night)

7 hours in aeroplane mode
7 hours with only calls and texts active
7 hours with selected background services also active. (Selected apps, such as Dekko, or those with connections to NextCloud)

Using this test method, I have not observed any increased battery consumption with RC 1.3.

[nogoogle]

I have just updated FP4 to 24.04-1.3. I noticed that the cellular network strength indicator remains an empty triangle (as if I have no mobile network connection). Phone calls, SMS and cellular data however work and the carrier is also shown in cellular settings. Any one else experienced this?

[messayisto]

@nogoogle see post 63 in this thread, An I read it somewhere else, too, forgot where. But I think its a known issue.

[nogoogle]

@messayisto said:

@nogoogle see post 63 in this thread, An I read it somewhere else, too, forgot where. But I think its a known issue.

Thank you, despite searching the thread for "indicator" post 63 did not pop up.

[messayisto]

@nogoogle At the right bottom corner you can see a blueish field. Scroll up to the number 63.

[Linus67]

I've been using it on three Pixel 3a devices running 24.04-1.3 for over a week.
Test conducted without using any apps and with all background processes disabled.

On all devices, I'm seeing significantly higher battery consumption when Wi-Fi is turned on.

I don't know if this is a general issue with the Pixel 3a or if it has to do with the current RC 1.3.

[gpatel-fr]

@sixwheeledbeast

Taking a look at what ofono is providing:

gdbus monitor --system --dest org.ofono --object-path /ril_0
Monitoring signals on object /ril_0 owned by org.ofono
The name org.ofono is owned by :1.12
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x1e>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x0f>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x23>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x11>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x16>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x07>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x19>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>)
/ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x16>)

it's clear that the triangle is optimistic, when ofono is reporting 0x25 (that is a signal quality of 38% the display is showing a good quality (a casual observing would say 75% although estimating surfaces on a triangle is misleading)

However when rhe reported quality change, the triangle changes also; it's not either empty or full.
In this my observations on my phone don't confirm what you see.

Since I had not yet this trick to get at the ofono reported quality before, I can't say if the triangle was already optimistic before 24.04-1.3.

I got the idea of getting my phone near a window and it jumped to 0x2f (that is 47% where the triangle was full.
Optimistic indeed. That said, is this a bug or a feature ? Maybe 50% is as good as it gets.

[sixwheeledbeast]

Overall 24.04-1.2 seemed to work perfect in my day to day usage.
Whereas 1.3 has some occasional quirks/regressions/differences? that are noticeable to me but not breaking enough to remember or make a note of each of them while out at work.
This signal strength was a noticeable one, I know the nearest mast is not far away and I know what is displayed now is very different to 1.2. Which is correct/accurate is another matter, if it's correct that's fine but ultimately people want to know at a glance if they can make a call and an empty triangle with even poor signal is not a helpful indicator if a call would be possible. Is there a different symbol for no signal as I haven't seen it? I believe you have to pull down and look at the carrier showing "Searching..." for this?
Another change I can remember is cellular data, before I could open the default browser anywhere and just browse straight away. Now intermittently with no WiFi available the browser will not have a data connection, the quick way I found to resolve this is shuffle cellular data off and on again.

[projectmoon]

@sixwheeledbeast said:

Overall 24.04-1.2 seemed to work perfect in my day to day usage.
Whereas 1.3 has some occasional quirks/regressions/differences? that are noticeable to me but not breaking enough to remember or make a note of each of them while out at work.
This signal strength was a noticeable one, I know the nearest mast is not far away and I know what is displayed now is very different to 1.2. Which is correct/accurate is another matter, if it's correct that's fine but ultimately people want to know at a glance if they can make a call and an empty triangle with even poor signal is not a helpful indicator if a call would be possible. Is there a different symbol for no signal as I haven't seen it? I believe you have to pull down and look at the carrier showing "Searching..." for this?
Another change I can remember is cellular data, before I could open the default browser anywhere and just browse straight away. Now intermittently with no WiFi available the browser will not have a data connection, the quick way I found to resolve this is shuffle cellular data off and on again.

I have noticed some similar things as well. Also having to reboot the phone way more often than normal because something gets funky. It's not like it's ALL the time, but it is a noticeable increase. I've also had the phone outright freeze completely when something too big in the browser was happening.

[messayisto]

@projectmoon I can confirm this exactly. I have to reboot more often, today i.e. I couldnt stop a call, so every day something weird is happening. volla quintus, 24.04-1.3 rc

[Linus67]

@ralf
I tested on three Pixel 3a devices for one week. No active use. All background services turned off. Location services and Bluetooth also turned off.

The same behavior occurred on every device. When I turn on Wi-Fi, power consumption increases dramatically.

Without Wi-Fi: 1 to 2% per hour
With Wi-Fi: 4 to 6% per hour