Call for testing: Ubuntu Touch 24.04-1.3

[gpatel-fr]

@sixwheeledbeast

I don't see the same behaviour on my FP5, that is, the FP5 displayed quality is not constant. I have no external way of have an objective estimation of the actual signal strength.

Although while I wrote that I noticed that the symbol is now stuck to empty like you said. Restart the phone just now. The symbol is not varying like before. Maybe it's the fact of switching the wanted signal type (5G/4G/3G...) that is making the signal strength get stuck to empty ? I never did that before. Or it was a fluke and the signal strength is really changing fast at my place.

While I can't know the real signal strength, last time I checked the official info, my location is not well served (my provider's nearest tower is behind a small elevation).

[sixwheeledbeast]

Signal strength isn't the issue, I wouldn't expect them all to be the same.
I know the signal strength is displayed much lower on 1.3 for 5G and 4G compared with 1.2 is the point

[domubpkm]

@gpatel-fr I switch from RC to stable. H-2 again. I did the command line and i confirm it solved the problem : good clock.

[gpatel-fr]

@domubpkm

interesting. Now this behaviour is a bit surprising since the service is supposed to be activated on-demand, so it's pretty normal it's stopped.

I did not check where and how in the code it's tested that the service is stopped but it's astonishing that such a check is even done.

Nonetheless, if starting the service actually fixes the clock it's an indication that this hypothesis deserves further research..

[domubpkm]

@gpatel-fr I seemed to see that at the end of booting the smartphone (before I entered the pin code) when switching to stable, the screen showed the correct time (H) and very quickly went to H-2.

[kristatos]

@gpatel-fr I've searched a bit and there is aleady a bugreport for that (it was already filled some days ago for the daily channel).
I've linked the thread to this bugreport.

[sixwheeledbeast]

Possible issue found in 1.3, maybe this could be checked it's not only myself?
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.
I use this regularly as a quick way to achieve some power savings from one place, part of discussions on usage here
Disabling from there own respective pull down works correctly.

[d4f0]

@sixwheeledbeast said:

Possible issue found in 1.3, maybe this could be checked it's not only myself?
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.
I use this regularly as a quick way to achieve some power savings from one place, part of discussions on usage here
Disabling from there own respective pull down works correctly.

It also happens on my FP4 with 1.3

[projectmoon]

@d4f0 said:

@sixwheeledbeast said:

Possible issue found in 1.3, maybe this could be checked it's not only myself?
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.
I use this regularly as a quick way to achieve some power savings from one place, part of discussions on usage here
Disabling from there own respective pull down works correctly.

It also happens on my FP4 with 1.3

Seems to be a bug, yes. Happens to me on a Volla Quintus with stable 1.3.

[messayisto]

This post is deleted!

[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.