- Vendor Samsung
- Device S5e
- Device gts4lvwifi
- Version LOS 21
- Not rooted
Installation from scratch - no problems so far.
- Vendor Samsung
- Device S5e
- Device gts4lvwifi
- Version LOS 21
- Not rooted
Installation from scratch - no problems so far.
Tu pourrais dĂ©tailler sâil te plait ?? Quel est le message prĂ©cisement ?
Vendor: Samsung
Device name: Galaxy S10
Device codename: beyond1lte
Previous version: 2.7
OTA update without any trouble!
Thanks
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 2.7-t-20250112460980-community-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 2.8-t-20250225471522-community-FP3.
The following things work for me:
Fairphone | FP3+ | FP3 | previously on e-2.7-u-20250110460550-community-FP3 | rooted
Update seems to be working OK, but I got five error messages from âAccount Managerâ
These are all Network or I/O errors and soft errors (Max retries)
Hereâs some text from the debug message. (Iâve omitted some lines that had my email address and other personals)
EXCEPTION
java.net.UnknownHostException: Unable to resolve host âmurena.ioâ: No address associated with hostname
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
at java.net.InetAddress.getAllByName(InetAddress.java:1152)
at okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:6)
at okhttp3.internal.connection.RealRoutePlanner.plan(RealRoutePlanner.kt:464)
at okhttp3.internal.connection.FastFallbackExchangeFinder.launchTcpConnect(FastFallbackExchangeFinder.kt:10)
at okhttp3.internal.connection.FastFallbackExchangeFinder.find(FastFallbackExchangeFinder.kt:61)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:137)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:1034)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:137)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:233)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:137)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:173)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:137)
at at.bitfire.davdroid.network.HttpClient$UserAgentInterceptor.intercept(HttpClient.kt:87)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:137)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:95)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:42)
at at.bitfire.dav4jvm.DavResource$propfind$2.invoke(DavResource.kt:9)
at at.bitfire.dav4jvm.DavResource$propfind$2.invoke(DavResource.kt:1)
at at.bitfire.dav4jvm.DavResource.followRedirects$build(DavResource.kt:14)
at at.bitfire.dav4jvm.DavResource.propfind(DavResource.kt:72)
at at.bitfire.davdroid.syncadapter.ContactsSyncManager$queryCapabilities$1.invoke(ContactsSyncManager.kt:3)
at at.bitfire.davdroid.syncadapter.ContactsSyncManager$queryCapabilities$1.invoke(ContactsSyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:5)
at at.bitfire.davdroid.syncadapter.ContactsSyncManager.queryCapabilities(ContactsSyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:8)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:2)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager.retrySyncOperation(SyncManager.kt:69)
at at.bitfire.davdroid.syncadapter.SyncManager.access$retrySyncOperation(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:21)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:60)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager.retrySyncOperation(SyncManager.kt:69)
at at.bitfire.davdroid.syncadapter.SyncManager.access$retrySyncOperation(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:21)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:60)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager.retrySyncOperation(SyncManager.kt:69)
at at.bitfire.davdroid.syncadapter.SyncManager.access$retrySyncOperation(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:21)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:60)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager.retrySyncOperation(SyncManager.kt:69)
at at.bitfire.davdroid.syncadapter.SyncManager.access$retrySyncOperation(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:21)
at at.bitfire.davdroid.syncadapter.SyncManager$performSync$2.invoke(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:60)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:6)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:4)
at at.bitfire.davdroid.syncadapter.ContactSyncer.sync(ContactSyncer.kt:218)
at at.bitfire.davdroid.syncadapter.Syncer.onPerformSync(Syncer.kt:119)
at at.bitfire.davdroid.syncadapter.SyncWorker.doWork(SyncWorker.kt:644)
at androidx.work.Worker$1.run(Worker.java:3)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
at libcore.io.Linux.android_getaddrinfo(Native Method)
at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:133)
at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:222)
at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:133)
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
⊠63 more
SYSTEM INFORMATION
Android version: 13 (e_FP3-user 13 TQ3A.230901.001 eng.root.20250219.200746)
Device: Fairphone FP3 (FP3)
Locale(s): [en_GB]
Time zone: Europe/London
Internal memory (/data): 41 GB free of 46 GB
CONNECTIVITY
â wlan0
Data saver: disabled
CONFIGURATION
App standby bucket: 5
Power saving disabled: yes
System-wide synchronization: automatically
Notifications:
Permissions:
I am using a new FP4 with v2.8 - 1 month in and new to this forum. So, some of this feedback is on the eOS more generally, vs just this version - my apologies if covered elsewhere. But here goes:
I agree about the failings of Bliss Launcher. Iâve had the best luck with Lawnchair 14. Itâs open source, has no trackers, and is highly customizable. It works quite well with /e/os.
Thereâs a newer version in beta, but Lawnchair 14 is the latest stable release. Best to go to the Lawnchair home page to get it (https://lawnchair.app). Itâs kind of obscured by all the launchers in the various app stores and thereâs older versions you donât want to install since theyâre obsolete and may not function well.
Lawnchair also provides a recent apps switcher. Bliss Launcher provides that function normally and I find it lacking as well. However itâs a convoluted process to change the switcher, you need to root the device for one. The Launcher is no problem, just install and select as your default home app, but if you want to replace the switcher on top of that you have to dig in under the hood.
Wow, great tip about Lawnchair! Thanks
Everything fine after update except for a problem that I had rotating images that caused the app to crash. Otherwise, no other problems so far.
je ne suis visiblement pas le seul :
Suddenly standard mail APP (Version 6.711 foundation.e.mail) keeps on crashing today. Clearing cache doesnât resolve issue.
Iâm unsure if this is related to v2.8. Because i didnât had any problems so far ( 2weeks)
PF4 - vendor : Murena
Doesnât send any mails, and crashes with following window:
Edit: K-9 mail works fine.
Edit 2 ; changed outgoing server settings to ssl/tls and this solved sending.
Device: Murena One
Not rooted
Previous version: 2.7
The fingerprint sensor is not working. Neither for unlocking the phone nor apps that should support it (banking), in fact, these apps directly ask me for a security pin, as if the fingerprint does not exist. I guess this started with new eOS update, but could be that the sensor got broken.
Any other user of a Murena One to confirm the issue?
Regards,
All seems fine so far.
Two problems I have encountered, but I do not consider them to be real issues:
Update March 20: after the App Lounge update that was pushed yesterday everything now works perfectly fine for me.
No, AppLounge in anonymous mode still doesnât work this morning, nor for me nor for my wife. (FP4 2.8 stable)
Did manually both updated to 2.13.5, no change.
âAccount unavailable - Refresh sessionâ comes in bootloop.
If I âIgnoreâ the message and click an app to install, a white screen with âunknown errorâ comes at the bottom.
Clear cache and data did not change nothing.
Will continue to use Aurora Store instead.
All rest is perfectly fine.
Iâm experiencing the same issue. The solution that worked for me was switching to 4G/5G, which allowed me to download or update apps again. When Iâm on Wi-Fi, I encounter a loop with the message âAccount unavailable - Refresh session,â just like you.
2.8-a14 (Android u) - community on a Sony âkirinâ: App lounge works fine, battery drain initially high, then ok
Today it happened, that AppLounge updated itself. Now I get the described issue. I canât load any App from Playstore. Even when using 5G connection instead of WiFi.
The second issue is the missing privacy estimation x/10 which was calculated by the data from exodus-privacy.eu