Unfortunately, can’t access APN settings until there is a valid SIM.
- Vendor Name: Google
- Device name: Pixel 4
- Device CodeName: Flame
- Version of /e/OS or Stock which existed previously: 2.5t
- Not rooted
OTA update failed / unavailable
Performed ‘Dirty-Upgrade’ as outlined by @piero (no issues, all data retained)
All seems fine, file transfers via USB still works (Mac)
1 Like
Teracube_2e
e_emerald-user 12 SQ3A.220705.004 eng.root.20241217.030444
Vendor Xiaomi
Device name: Mi 11 Lite 5G NE
Device codename: Liisa
Previous /e/ version: /e/ OS 2.5 T
Is the device Rooted: Not rooted
I just updated through exsiting recovery 2.5t. All went well
Working oke
Vendor Name: Google
Device name: Pixel 8
Device CodeName: Shiba
Version of /e/OS or Stock which existed previously: Stock Android 14
Is the device Rooted / Not rooted: No Rooted
Hi there after using the new version in a new device I have noticed the follwing problems.
-
Bliss search is not working.
Everytime I search for an App it crashes and reboots. -
I installed a few Banking Apps and there is one “Swissquote App” which can not be started and I am getting the following message:
" App integrity Error
Ths Swissquote app does not support this environment.
It seems you have an outdated version of the Google Play Store or Play Service on you device. Please update them to the latest version".
Error Code: -9".
The rest of the Apps are working well.
Thanks for you support.
Hi @Manoj
bliss-launcher issue after upgrade to v2.6.3-t
device-name: Samsung Galaxy S9 (exynos)
device-codename: starlte
device-model: SM-G960F
regards
Pl can you share what issue you are facing with the launcher…will help the developer debug / test and verify
Good to know, that 2.6.3 works in general, but as I mentioned above an installation from scratch fails because of the setup wizard stuck.
The character selector popup misalignment also can be observed on LOS 21.
*to be honest, at 1st I was nervous and was hesitating on doing dirty flash.
I’m late in the game… anyways, reporting that the upgrade went smoothly through recovery using
adb -d sideload filename.zip
Vendor Name: Xiaomi
Device Name: Redmi K40 pro
Code Name: haydn
Version of /e/OS which existed previously: e-2.5-t
No root
Everything seems to be working smoothly (in fact, smoother than previous version as for animation and other stuff in general)
Thanks for your work
1 Like
Vendor Name: OnePlus
Device name: Nord
Device CodeName: avicii
Version of /e/OS or Stock which existed previously: 2.4.1-s
Is the device Rooted / Not rooted: not rooted
Since I was on 2.4.1-s I manually update to 2.6.3-t via sideloading which went totally wrong in the first place but now the system is running again. See here.
The only thing that is not working is WIFI.
In cannot enable it and it does not discover any networks. When I click the button, it stays enabled for a few seconds and then automatically becomes disabled again.
What can I do?
I am writing this post on Murena Pixel5 e_redfin-user 13 TQ3A.230901.001 eng.root.20241217.030510
It feels like it takes longer for available updates to be displayed via my VPN provider than with a direct connection. This version has only been displayed to me in the last few days. But that is of course acceptable. Thank you and here’s to the new year.
P.s. The refurbished Google Pixel5 is practically scrap after a year! Battery is fucked and the power button has fallen out. USB-C charging socket unreliable. Too bad, after one year for 400€!
I have a problem with the v2.6.3 update on my phone
About phone: FP4.
/e/OS version: 2.6.3-u-20241217455359-official-FP4
Description
Problem before this last update: cannot use the physical sim and the esim at the same time (two different providers). I red that is ok when we have the same provider.
So I switch off one of them several times a day…
Since last update (December 17), i cannot switch on the esim. “something wrong during switch off” (free translation), they say.
Physical sim is OK.
Vendor Name: Fairphone from Murena
Device name: Fairphone 4
Device CodeName: fairphone-fp4
Version of /e/OS or Stock which existed previously: 2.6.2
Is the device Rooted / Not rooted: Not rooted
After updating last night I have been unable to connect to the T Mobile network. During install of updates I had no issues. After first restart an error popped up when I first put my passcode but disappeared to fast for me to read it.
I have tried restarting. Disabling WiFi calling. Switching into airplane and back. No luck getting connected to the TMobile network.
EDIT: Fixed it somehow. I just started toggling the SIM off, then did the same for 4G then did the same for roaming, then it suddenly connected. I have never encountered this before in the past year I have had this phone.
I’m not affected by the eSim issue, nonetheless I’m wondering if reseting mobile network settings (Config > System > Reset) does anything here.
1 Like
I have the same problem here, but only on my LTE. If I’m connected to a wifi, everything is fine.
Tried with proton VPN and unifi VPN, same problem.
Pixel 3 XL after upgrade to 2.6.3-u.
Melinoe did but it didn't fix the problem.
https://community.e.foundation/t/esim-activation-error-murena-mobile/64555?u=moldu
Vendor Name: Fairphone from Murena
Device name: FP4 (Two FP4)
Device CodeName:
Version of /e/OS: 2.6.3-u-20241217455359-official-FP4
Version of /e/OS or Stock which existed previously: 2.5-t
Not rooted
Everything went flawlessly on my 2 FP4. I’m delighted with the Murena FP4, best smartphone experience I ever had. Kudos to the team.
Dom
3 Likes
I have updated to /e/OS U 2.6.3 several days ago. Generally speaking, I am really satisfied by the overall experience! The system feels more than fast enough, even a bit “snappier” than before.
- I did a complete clean install, no “dirty flash”. I used the opportunity to first update the system to the latest stock ROM, as suggested in the installation notes. I did the reset to stock ROM with the OnePlus MSM tool and then used the OnePlus OTA app, as discussed in this thread. (The reset may be one reason why the system feels “snappier”.)
- I could root the phone with Magisk. I then tried to install LSPosed, which is supposed to be compatible with Android 14. Unfortunately, LSPosed crashed immediately. I could however use the LSPosed fork by JingMatrix and then the XPrivacy Lua fork XPL-EL by ObbedCode without issues. (Disclaimer: While these forks are still open source, you may be more hesitant than me to use them because they are not as popular as the original apps/modules. Theoretically, these forks could contain backdoors because the code may not be as thoroughly reviewed as the original modules - it is up to you to decide whether you take the risk using them.)
- Until the upgrade to /e/OS U, I used the app AccA, a GUI for acc, to limit the charging of the smartphone battery to 80%. Unfortunately, the latest stable release v2023.10.16 of acc does not seem to be compatible with Android 14. Newer versions (which are release candidates) are no longer compatible with AccA. Hence, I use the built-in Android functionality to limit the charging, and a rather “weak” charger to avoid that the battery is charged too quickly.
- Strangely, the setting that automatically enables the energy saving mode when the battery charge falls below a certain percentage is always reset to 20% after a reboot if it is enabled, regardless of the value set before the reboot (e.g. 15%). I have decided to deactivate this setting as I never really used it anyway. (However, a message still appears at 20% and suggests to activate the energy saving mode.)
- EDIT: Something odd happened after the fresh install: The wallpaper that I had set before the complete data wipe was offered in the customisation options although it is a custom one not included with /e/OS. I can only guess how that happened. However, I had already copied some data (including my saved pictures) to the smartphone, so I think that this background was somehow included and set as some default.
- EDIT: I also had to reset the Wifi and Bluetooth settings after the fresh install so that my headpones could pair with the smartphone - odd, but pairing and using the headphones works as intended now.
- EDIT: As I prefer Pixel-like launchers, I have successfully installed the current Lawnchair beta (not from Google Play, but from IzzyOnDroid with an F-Droid client). It works as intended so far.
A big “thank you” to the /e/OS team for this upgrade!
2 Likes
@Manoj 2.6.3 for Shiftphone 6mq axolotl is missing.
Stock FP4
Not rooted
Since 2.5 the stock browser still lagging