. Vendor Name: Fairphone
. Device name: Fairphone 4
. Device CodeName: FP4
. Version of /e/OS or Stock which existed previously: /e/OS-1.15-stable
. Is the device rooted: Not rooted
This time the update worked without problems. But I have the issue (for longer now) that a restart from the software does not work. If I klick on restart in the on/off-menu or after an update, the phone hangs up. I have to press the on/off-button for longer to restart the phone.
Fairphone 3+
FP3
Updated from v1.15-s-stable to v1.16-s-stable
Not rooted
Usual straightforward update in just under 40 mins.
Initial testing so far shows all working OK, just the same couple of long standing issues mentioned previously (VPN not reconnecting on reboot / changing VPN server, upward swipe to return to home screen very unreliable).
Samsung S8 SM-G950F
Update from 1.15-r-stable
Not rooted
App Lounge : āThe anonymous account youāre current using is unavaibleā¦ā
Hit āRefresh sessionā but the message appeair again and again.
Clear cache and data.
No wayā¦
Edit: problem seems appeared only with wifi, not with 4G !
OTA upgrades via the updater to new major Android versions (in this case Android 12 S to Android 13 T) need to be specially prepared by the developers per device per upgrade step, which needs considerable time and effort. As @MRTN already pointed out, this is under testing for redfin currently.
Vendor name: Fairphone
Device name: FP4
Device code name: FP4
Version of /e/OS or Stock which existed previously: 1.15-s-20230913330639-stable-FP4
Device not rooted
Gigaset
Gigaset GS 290
GS 290
1.16-s-20231017342507-stable-GS290
Not rooted, phone bought from e.foundation
I have still the same ācom.mediatek.ims.ImsApp keeps stoppingā -problem after 1.16 installation, that started after 1.15 update. I have cleared caches, reset apps, called operator (just getting instructions to clear caches and reset apps). There was advice to check āadb logcatā on this forum, but after previously bricking one phone with lineageOS installation, Iām not willing to try that advice. I really donāt know how to, and on the other hand, what to do after seeing the logā¦
Iām sending SMS-messages to manage my smart home devices and I donāt feel very smart after this update either.
Vendor Name: Fairphone
Device name: FP4
Device CodeName: fp4
Version of /e/OS existed previously: 1.15-stable
Is the device Rooted / Not rooted: not rooted
After 1.16-s update I still get ācom.mediatek.ims.ImsApp keeps stoppingā when sending SMS-messages. First SMS goes, but if sending more, āfailed sending messageā appears. This started to happen after 1.15-s update, and continues still.
Vendor Name: Gigaset
Device name: GS 290
Device CodeName: GS 290
Is the device Rooted / Not rooted: Not rooted
Version of /e/OS existed previously: 1.15-s-stable
Updated to version: 1.16-s-20231017342507-stable-GS290
OTA update went well without issues.
No problems so far with my daily driver.
CanĀ“t confirm issue with sending SMS. It might be a device specific problem.
Because we run two GS290 with /e/OS and face sometimes issues on the second device.
Many thanks to Manoj and the whole murena team!
Br.,
Thank you for your comment. My household has two GS290ās with ready installed eOS, and both of them has had same problem after 1.15-s update. I donāt know if Gigaset builds same phone models with variable components, or would that affect with ImsApp problem?
Hi @mok wanted to understand the issueā¦you are facing an issue on a GS290 after v1.15 s update in sending sms messages? @obdi you are facing this on one GS290