Vendor Name: Samsung
Device name: S7
Device CodeName: SM-G930F
Version of /e/OS: v1.14
Not rooted
Works fine, another big thanks to the team keeping the aged hardware alive so well!
1 Like
Device name Fairphone 4
Version of /e/OS which existed previously **IMG-e-1.14-s
Is the device Not rooted
Over the OTA Update - works fine
@eOS Team: Thank you very much.
Same here:
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 1.14-q-20230815320612-stable-herolte
now: 1.15-q-20230913330637-stable-herolte
Not Rooted
… no issues …
Thanks a lot for keeping that hardware alive!
- Vendor Name Fairphone
- Device name Fairphone 4
- Device CodeName FP4
- Version of /e/OS or Stock which existed previously IMG-e-1.14-s-20230816320616-stable-FP4
- Is the device Rooted / Not rooted
All good so far.
Once again big thanks to the e-team.
- Vendor Name Gigaset
- Device name Gigaset GS 290
- Device CodeName GS 290
- Version of /e/OS or Stock which existed previously IMG-e-1.14-r-20230815320614-stable-GS290.zip
- Is the device Rooted / Not rooted
Seems to work fine, but I’ve got a huge problem: The device does not charge anymore when powered off - Or at least does not display the charging unit with battery percentage. When I plug the USB cable it’s stuck to “Gigaset powered by Android”.
I tried several cables, several chargers, unsuccessfully.
I noticed that the setting “update recovery” was unchecked in update system settings. So I reflashed recovery.img (1.15 last version), but no change…
I checked the recovery version with adb reboot recovery and I’m well on 1.15 recovery as well.
Is there any way to fix the offline charge?
Thank you very much!
Murena Fairphone 4
Update from 1.14s
Since OTA update 1.15s the touchscreen has issues: It’s reacting very unsensitive, scrolling ist hard to do.
Also high battery drain compared to previous version!
- Vendor Name : Samsung
- Device name : S9+
- Device CodeName : SM-G965F
- Version of /e/OS or Stock which existed previously : 1.14
- Not rooted
It works !
Yes, there is. It’s in Fastboot-Mode.
Vendor Name: Samsung
Device name: Samsung S9 SM-G960F
Device CodeName: starlte
Version of /e/OS or Stock which existed previously: 1.14-q-20230816320942-dev-starlte
Is the device Rooted / Not rooted: Not rooted
Just update to 1.15-q-20230914331056-dev-starlte and everything work perfectly 
Well done /e/ team !!!
Next step OS upgrade to 1.15-t.
1 Like
- Vendor Name Fairphone
- Device name Fairphone 4
- Device CodeName FP4
- Version of /e/OS or Stock which existed previously eOS 1.14-s-stable
- Is the device Rooted / Not rooted
Updated the device without any issues.
1 Like
Fairphone 3+
FP3
Updated from v1.14-s-stable to v1.15-s-stable
Not rooted
Update went smoothly as usual, slightly quicker than recently at 37 mins.
Initial testing so far shows all working OK, just a couple of long standing issues remaining (VPN not reconnecting on reboot / changing VPN server, upward swipe to return to home screen very unreliable).
Thanks for all the work - fingers crossed for an OTA update to T.
3 Likes
- Vendor Name: Google
- Device name: Pixel 5
- Device CodeName: redfin
- old Version of /e/OS: 1.14, dev
- The device is Not rooted
Working very well, thanks…
- Vendor Name: Samsung
- Device name: S7 Edge
- Device CodeName: hero2lte
- Version of /e/OS: 1.14, dev
- The device is Not rooted
Working very well, thanks…
Installed on Samsung S10e, Samsung Tab S6 lite and Sony Z5 compact. All good.
Installed stable upgrade OTA on Samsung S9.
Only two things to mention:
- In Settings → System the entry for Backup/Seedvault is missing. So I can’t setup device backup.
- Got a second version offered after upgrade, installed without problem.
Xiaomi
Mi A2
jasmine sprout
1.14 r dev
Not rooted
many thanks flawless update again
- Vendor Name: Fairphone
- Device name: Fairphone 4
- Device CodeName: FP4
- Version of /e/OS or Stock which existed previously: /e/OS 1.14-s-stable
- Not rooted
All fine, thanks to the team
I’m currently upgrading my S9 from 1.14, but i noticed there were two different 1.15 releases published a day apart (see Screenshot).
Would anyone care to explain?
Edit: is the newer one a hotfix? Some explanation in the UI would be nice in such a case since it’s impossible to tell them apart in the updater other than from the publish date.
Had you gost touch issues before the update?
In that case, new stock firmware could be responsible. Gost touches would be solved but less display reactivity.
I didn’t have that issue before, now I don’t have less reactivity.
If I understand the Fairphone forum, that is an issue software and hardware too. Fairphone support in the last case told to return the phone.
Here is the discussion: https://forum.fairphone.com/t/ghost-inputs-on-fp4/82837
I updated to the newer of the two offered, from 1.14-q, on my s9. After upgrade finished device showed 1.15-r installed and seems to be working fine so far.