Dremor
June 10, 2024, 8:45am
41
Manoj:
Vendor Name : Fairphone
Device name : FP5
Device CodeName : FP5
Version of /e/OS : 2.0-t
Is the device Rooted / Not rooted : Not rooted
The usual crashes are still there (https://gitlab.e.foundation/e/backlog/-/issues/7678 )
The “Recent App View” bug (https://gitlab.e.foundation/e/backlog/-/issues/7748 ) was not tested for now in order to exclude any other causes than the multiple account feature, I will create a new user to test this next week.
I did not encounter the updater bug I reported during the beta (https://gitlab.e.foundation/e/backlog/-/issues/7994 ) while updating to the stable version.
1 Like
jobal
June 10, 2024, 10:02am
42
In my experience (italian carrier), usually FP4 gets OTA update the last days.
It’s already available in Portugal. I’ll upgrade when arrive home.
1 Like
I got my notice this AM, after hitting refresh 20 times. And watch, if you hit reset too fast, it will tell you no update available.
Manoj:
Vendor Name : Fairphone
Device name : Murina FP4
Device CodeName : FP4
Version of /e/OS : 2.0-t
Is the device Rooted / Not rooted : Not rooted
Cannot delete BLOCKED numbers from the SMS app.
When I click the “x” next to the number one of two things happens: The app crashes, or it simply returns to my list of sms messages, without removing the number. Needs addressed as I blocked a number by accident, and now cannot remove the block.
1 Like
Vendor Name : Fairphone
Device name : FP5
Device CodeName : FP5
Version of /e/OS : 2.0-t
Is the device Rooted / Not rooted : Not rooted
Update went smooth but it took 2 hours
Crashes / Reboots are still happening
AppLounge shows “Account not available / Renew session” every few minutes
Bliss Launcher: Icons often cannot be moved, instead apps are always opened
Xxpsilon:
Samsung Galaxy Tab A7 10.4 2020 (LTE) SM-T505
Device CodeName: gta4l
Version of Stock which existed previously: T505XXS7CXB1 Binary BIT-7 (seven)
The device is Not rooted
The installer does not recognize the existing stock Android 12 firmware (binary 7). Therefore, the /e/ installation process of e-2.1-t-20240605406922-dev-gta4l is aborted with the following message, although stock firmware Android 12 is installed::
The same error message is displayed when trying to install with Stock Android 12 firmware T505XXS7CXB1 ~ BINARY-7 :
e-2.0-t-20240508399779-dev-gta4l
e-1.21-t-20240324389105-dev-gta4l
lineage-21.0-20240506-microG-gta4l
lineage-21.0-20240510-nightly-gts4lv-signed
The bug was recognized and corrected by the LineageOS Android Distribution (LOS) and since version lineage-21.0-20240517-nightly-gts4lv-signed a problem-free installation is possible again.
I already pointed out this bug on May 27, 2024
The solution to the problem: Change META-INF
Change T505XXS6CWI2 TO T505XXS7CXB1
SM-T505 e-2.1-t-20240605406922-dev-gta4l
SM-T500 e-2.1-t-20240605406922-dev-gta4lwifi
e.g.: e-2.1-t-20240605406922-dev-gta4l\META-INF\com\android
metadata
metadata.pb
otacert
metadata
ota-property-files=metadata:69:336,metadata.pb:473:216
ota-required-cache=0
ota-type=BLOCK
post-build=samsung/gta4lxx/qssi:12/SP1A.210812.016/T505XXS6CWI2 :user/release-keys
post-build-incremental=eng.root.20240605.053621
post-sdk-level=33
post-security-patch-level=2024-05-05
post-timestamp=1717565706
pre-device=gta4l
metadata.pb
"J
ota-property-files4metadata:69:336,metadata.pb:473:216 a
gta4l2
gta4lFsamsung/gta4lxx/qssi:12/SP1A.210812.016/T505XXS6CWI2 :user/release-keyseng.root.20240605.053621 Šòÿ² 332
2024-05-05
For comparison:
e.g.: fully functioning lineage-21.0-20240607-microG-gta4
metadata
ota-property-files=metadata:69:336,metadata.pb:473:216
ota-required-cache=0
ota-type=BLOCK
post-build=samsung/gta4lxx/qssi:12/SP1A.210812.016/T505XXS7CXB1 :user/release-keys
post-build-incremental=eng.root.20240607.053855
post-sdk-level=34
post-security-patch-level=2024-05-05
post-timestamp=1717738734
pre-device=gta4l
metadata.pb
"J
ota-property-files4metadata:69:336,metadata.pb:473:216 a
gta4l2
gta4lFsamsung/gta4lxx/qssi:12/SP1A.210812.016/T505XXS7CXB1 :user/release-keyseng.root.20240607.053855 ³ 342
2024-05-05
Vendor Name : Murena
Device name : Murena One
Device CodeName : Murena
Version of /e/OS : 2.0-s
Rooted : No
No issues detected, everything OK
JA13
June 10, 2024, 2:56pm
49
Vendor Name : Fairphone
Device name : FP5
Device CodeName : FP5
Version of /e/OS : 2.0-t
Is the device Rooted / Not rooted : Not rooted
Reboot bug still present…
manjar
June 10, 2024, 3:42pm
50
Vendor Name : Fairphone
Device name : F3
Device CodeName : F3
Version of /e/OS : 2.0-T
Rooted : No
No issues detected, everything OK
1 Like
jobal
June 10, 2024, 3:52pm
51
Here it is, after 4 taps.
Hi,
Same behaviour for Gigaset GS290.
Only after checking the availability in https://images.ecloud.global/stable/GS290/ I went to Settings / Updater, but it could not find any new updates … after several trials of refresh, it discovered the update there
Today afternoon after one tap it was showing. Now starting…
1 Like
mu88
June 10, 2024, 4:45pm
54
Vendor Name : Fairphone
Device name : FP4
Device CodeName : FP4
Version of /e/OS : 2.1-T
Rooted : No
Some apps do no longer vibrate (although vibration in general works for phone calls, message notifications, etc.) - so far, I’ve noticed this on the apps dev.codeplex.intervaly
and ch.zkb.digipass
.
BlissWeather shows the current weather conditions, but no forecast.
Beside those minor issues, everything seems to work smoothly. Thank you very much for your hard work!!!
1 Like
obacht
June 10, 2024, 4:52pm
55
Vendor Name Samsung
Device name Galaxy S7 (SM-G930F)
Device CodeName herolte
Version of /e/OS or Stock which existed previously
2.0-r-20240506399551-stable-herolte
Is the device Rooted / Not rooted
… all well, no issues from what I see so far…
Thanks a lot for keeping that hardware alive !!!
2 Likes
Vendor Name : Fairphone
Device name : Fairphone FP4
Device CodeName : FP4
Version of /e/OS : 2.1-T - Stable
Previous version of /e/OS: 2.0-S - Stable
Is the device Rooted / Not rooted : Not rooted
Just upgraded 2 devices: Mine + my spouse’s one
The only (very minor) bug is still present in 2.1 (Android 13): Unable to rotate and save a picture that is stored on the SD card: https://gitlab.e.foundation/e/backlog/-/issues/6226
For the rest, everything’s fine, upgrade was done quite “fast” (45 minutes) and smooth.
Once again, thanks to all devs for your work!
2 Likes
Xiaomi
Mi8
dipper
2.0-dev
not rooted
Everything looks good after few days.
Thx to the dev team!
Same with me, another happy thanks to all of you at /e/!
1 Like
So I wanted to let people know how to get around this, in case they see the same issue.
I used F_Droid and installed the Fossify Message app, making it the default SMS app.
I used it to import the existing SMS messages.
I then Forced the /e/os Message app closed, and deleted the cache and app data.
I left the Fossify app as default for now.
Vendor Name : Fairphone
Device name : Fairphone FP4
Device CodeName : FP4
Version of /e/OS : 2.1-T - Stable
Previous version of /e/OS: 2.0-S - Stable
Is the device Rooted / Not rooted : Not rooted
All seems well at first glance. … and at long last wireless screencasting seem to work now
Thanks e-team, great work again !
Edit: Minor issue on another glance, vlc lost access to the media folders on sdcard
1 Like