Feedback for v2.6.3

/e/OS Smartphone Operating System Build Feedback
335
  • Samsung
  • Galaxy S7
  • herolte
  • 2.5-s → 2.6.3-s
  • Not rooted

No bugs spotted so far. Many thanks for the work !

2 Likes
336

Sorry for another question. Any idea how the eSim problem is affecting other device than FP4? Or is the OTA OS Upgrade the only one with eSim problems? Asking for other eSim users and myself.

337

You should be able to track progress for FP4 here

338
  • Fairphone 4
  • FP4
  • 2.5-t → 2.6.3-u
  • Not rooted

I upgraded it a while ago and everything was fine, I was not imapacted by the eSim problem.
But since a few days, text messages are not working. I cannot send and cannot receive them.
Also another thing is that when I put my phone on vibration mode, I still have sound for notifications.

339
1 Like
340

Samsung
Galaxy Tab A7 10.4 2020
gta4lwif
Stock Android 12
Not rooted
binary: T500XXS8CXG1

all is working well.

341 
Vendor Name: Motorola
Device name: Moto g9 play
Device CodeName: Guamp
Version of /e/OS or Stock which existed previously: Stock Android 11
Not rooted.

Not tested in depth. Installation without any problems. I find the same bug for LineageOS Rom regarding distorted audio problems in applications such as Whatsapp.

342

Gigaset GS290
e-2.5-s → e-2.6.3-s

update through recovery on SD-card, basic applications are OK.
but new behavior for next udate, see :

or:
new; the GS290 is now at version e-2.6.3-s, after updates via recovery with SD card. Looking at:
settings → applications → all → “…” → process-system → update manager → mobile data and wifi
I see that I can enable: allow-network-access, data-wifi, mobile-data (were they grayed out before?).
Then, the Update-manager tells me (today) “no new update available” as expected. I can’t wait to upgrade to e-2.7 :smile:
thank you very much to those who helped me explore the dense tree of parameters, and use the “recovery” mode.

343

Device name Redmi Note 9s
Device CodeName miatoll
Version of /e/OS or Stock which existed previously 2.5
Is the device Rooted / Not rooted not rooted

After a dirty upgrade via the local update feature things seem to be working fine in the sense of not having encountered new bugs.
I personally don’t like that Bluetooth can no longer be switches on/off with one touch but I understand this is an android 14 feature rather than an eos bug.

Interestingly the reported memory (ram) usage is significantly lower than under T (from an average of 3,5gb ram used to 2,5gb used, even after several days of the phone not having restarted)

Last but not least, thank you very much for your continued work on this project!

1 Like
344

So I updated to 2.7-u since I thought it was somehow related to the esim problem but I still had the issue.
So I went to the esim settings and I just checked the “Use 4G for calls” and then I was able to receive and send messages again.

1 Like
345

Hi
I’m still waiting a update because i lost my phone with v2.6.3 and my life became very tricky.
As far as I understood the 2.7 version is available. It doesn’t appear on my phone. I suppose it is possible to download it from a PC and install it. Where can i find help to do that?

346

2.7 is not available yet. Only available for people on the test channel

347

Instructions are on the Gitlab issue if you want to take the testing route.

348
  • Vendor Name: Google
  • Device name: Pixel 6a
  • Device CodeName: Bluejay
  • Version of /e/OS or Stock which existed previously: 2.5-T-community (updated to 2.6.4-T-community)
  • Device no rooted

Update went smoothly. No issues detected so far. Thanks to the team.

349

I have two Murena FP4s. One got the 2.6.3-u…official-FP4 update through the usual “System updates” method. Everything seems to be working great!

The other FP4 is still running 2.5-t…official-FP4 and says I’m up to date / running the latest version.

Is this a phased rollout? Should I just wait for the 2nd phone to automatically receive it? Or should I do/change something to update the 2nd one? Both are on USA T-Mobile, in case that matters.

350

When did you get the U update (upgrade) for the first one?

The e/OS/-Team had to stop the OTA OS Upgrade to 2.6.3-u because of an issue with eSim’s. MAybe one of the devices checked the server at the right time…

2 Likes
351

In v2.6.3 I can’t move app icons to a different position on a page (Fairphone 4). I can drag but no space opens up to drop.

352
  • Vendor Name : Samsung
  • Device name : S10e
  • Device CodeName : beyond0lte
  • Version of /e/OS or Stock which existed previously : 2.5-t
  • Is the device Rooted / Not rooted : not rooted

Well, I did not upgrade to 2.6.3, but to 2.6.4-t (not 2.6.4-u), because I’m not yet ready to reinstall (and reconfigure) all.

No issues so far.
Thanks for the update!

I’m still looking for a reliable backup/restore process, maybe this script pkerling/adbrootbackup, could do the job.

353

Fairphone
FP3
FP3
2.6.3-t-community
updated to 2.6.4-t-community
not rooted

There is an persistent error I forgot to report in time, can’t say with which version it appeared, but definitely before 2.6.3: Incoming calls are not immediatly shown on the display, only about after the fifth ring the expected pop-up appears and I can take the call.

Otherwise all good so far.

354

I don’t remember exactly. Maybe a week ago?

Oh good to know, thanks! Yep, maybe I was just “lucky” with the timing. And that I don’t use an eSIM.