Vendor Name: Samsung
Device name: Galaxy S7
Device CodeName: SM-G930F
Version of /e/OS or Stock which existed previously: (2.1 Herolte)
Is the device Rooted / Not rooted: Don’t know
Hi there,
I have faced a problem on my device:
After charging the phone the battery drains power super fast and the phone gets hot. Using the android app “Ampere” I messured 1770mA leaving the battery, even though no other app was running. That is almost charging speed and that means, the phone loses power as fast as it gets power when charging. I tried a different cable also, same result. I also checked if a certain app is sucking a lot of energy but there does not seem to be one (using the German version, under “Akku” and “Akkunutzung” there are no peculiarities). Btw there is no difference if “fast charging” is turned on or not (between these two I cannot notice a different speed anyway).
My workaround right now is the following: Charging the phone, unplugging the cable, restarting the phone - after this the battery usage is within a normal range between 200 and 500mA.
Has anyone had similar problems?
Thanks a lot
p.s. I have noticed that under 2.1—stable-herolte there was a feature “wifi calls” (German “Wlan-Anrufe”) even though it was not working. After the update this feature seems to be gone entirely. Will it come back one day?
Vendor Name: Motorola
Device name: Moto G7 Plus
Device CodeName: “lake” XT1965-T
Version of /e/OS or Stock which existed previously: /e/OS1.8
Is the device: Not rooted
No major issues
Minor issues:
Dialer app kept crashing until app data & cache cleared.
Visual voicemail in dialer app not working (US carrier ATT has its own app) Night Light not working. When enabled using sunrise to sunset, it always thinks its nighttime. Disregard. User error!
Home screen background shifted to left, cannot be centered.
Not to that extent.
But I also noticed that S7 needs more power with 2.2 than with 2.1.
Have you tried clearing cache of apps incl. system-apps? Least it’s worth trying.
Version of /e/OS or Stock which existed previously 1.19.1
Is the device Not rooted
Actually everything is going smoothly, I noticed 1 issue. In the search field (Blisslauncher) I cannot search for numbers. An app that I use a lot is called 4411, I cannot enter this.
Vendor Name: Samsung
Device name: Samsung S8 SM-G950F
Device CodeName: dreamlte
Version of /e/OS or Stock which existed previously: 2.1-r-20240603406611-stable-dreamlte
Version installed now : 2.2-r-20240715417776-stable-dreamlte
Is the device Rooted / Not rooted: Not rooted
No problem so far (it’s been 3 days).
The OS has been very stable on my device for the past few month. Thank you for the fantastic job !
Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3 /(+)
Previous Version: /e/OS 2.1-t-20240605406922-dev-FP3
Device is Not rooted
No issue with updating.
But since Version 2.0 i sometimes have a little problem with the network, both mobile and wifi.
After Boot some Apps cannot connect to their Servers. The only App that give me a hint on the issue, is FairEmail. This App points on DNS-Lookups. So Servernames could not be translated in IP-adresses. One or two Reboots had helped me in the meantime.
As a Workaround i now switch to airplane mode before shutting down the device. After a new boot next morning i wait a couple of seconds before switching off airplane mode. This doing seems to help connecting properly to network. May be a help for others.
Fortunately not, battery usage seems to be normal on my S7.
And by the way: I also would be delighted if wifi calls where possible with the S7. Or with the Murena one. The feature can be activated there, but doesn’t work.
Vendor name : Samsung
Device name : S8
Device CodeName : SM-G950F
Version of /e/OS or Stock which existed previously : 2.1-r-2024060340661-stable-dreamlte
Rooted : no
Upgrade OK. Everything work fine !
Many thanks e/OS team !
This is now the fourth consequtive version to have this same issue. Are they even seriously looking at this? I’ve had it since I purchased the phone (v1.21), it was not fixed in 2.0, I held off on 2.1 because of the known issues on that version and now I see it’s STILL not fixed in 2.2?
I already fed them back on V2.0 how to reproduce the crash reliable, but didn’t see anything happen with that. I REALLY need/want them to solve this, it’s high priority item. Imagine this happening when you are placing a 112 / 911 call in an emergency?
Again, please, dear people @ Murena: I know you do not want this to happen, but please realise the FP5 is the most high-end phone currently running your OS. It’s a popular device and a crashing issue like this will seriously hurt your sales apart from the fallout of a potential issue in an emergency situation which would likely put a serious dent in your reputation. Please give this 100% priority.
Like I posted previously, it seems to coincide with app updates. My crashes to boot logo are ALWAYS preceded by, or followed immediately, by automatic app updates. Disabling 5G does not help. To help drive this point home: I just spent 2+ weeks in a remote region with BARELY any mobile coverage, 1 bar and 2~5kb/sec upload 3/4g connections at most. Under these conditions, NO app updates could be triggered, and the phone was rock stable.
As SOON as I briefly hit an area with sufficient coverage to trigger the updates to start rolling, BAM - reboot, Murena logo…
It is indeed highly problematic FP5 users have one of the core features of a phone -calling in case of an emergency- not being guaranteed.
Could the devs advise how they deal with this (or not)? I read the/some issues are pending Fairphone actions, and not (only?) /e/os. Who is currently acting on what?
For now I chose to keep v1.21, as I understood the issues may get worser with 2.x. Am I wrong?
*Vendor Name - Google
*Device name - Pixel 5
*Device CodeName - Redfin
*Version of /e/OS or Stock which existed previously : 2.1
*Is the device Rooted / Not Rooted - Not Rooted
*Vendor Name - Gigaset
*Device name - GS290
*Device CodeName - GS290
*Version of /e/OS or Stock which existed previously : 2.1
*Is the device Rooted / Not Rooted - Not Rooted
Both devices updated smoothly, staggered between around a few days, if my memory serves me. No issues initially, however this morning I got limited wifi connectivity issues on the pixel 5. I rebooted my router and checked connectivity but the problem persisted. I restarted the pixel 5. Still an issue with limited connectivity. This is after forgetting the network and reentering the wifi password.
On the GS290 I have mobile data on with a sim card and no issues with limited connectivity. I turned on mobile hotspot and the pixel 5 has the same message of limited connectivity when connected to the cell signal of my GS290 via tethering of the mobile hotspot. I then disconnected from my mobile network, connected the GS290 to the router wifi and got a message of limited connectivity, same as the pixel 5.
I do not have any issues related to limited connectivity with a Huawei running google android connected via wifi or with any of my desktop machines running ethernet.
Everything else is working great and has been perfect until this morning but I wanted to pass on this recent issue for any devs who might want to know about it.
Gigaset
GS290
2.2-s-20240715417774-stable-GS290
Not rooted
“No internet connection” shows above Browser, also network icon has “!” over it. But internet works, on mobile data, I use wi-fi very seldom, almost never. If I use VPN (fsecure), icons disappear, but some apps don’t work. Just noticed this today (20.8.), long after 2.2 installation.
Now when tested wi-fi, I noticed that a warning appeared: “(SSID) has limited connectivity, Tap to connect anyway”. Then appears warning: " Some apps and services may not work due to limited connectivity. Use anyway?" with No Yes -options. When choosing Yes, wi-fi is connected. App Lounge now shows udates for some apps. I had “Automatically install updates” setup previously, it is still there, but “Only on un-metered networks” has a tick now. I had unticked that long time ago.
