Updating my Samsung S9+ R dev to v.1.17 went smoothly. I then tried to upgrade to T, but no luck. I successfully flashed the T recovery and then sideloaded the OS with no errors. After rebooting I got stuck on the bouncing dot logo, though. Back on R for nowā¦
Version previously: /e/OS 1.16-s-20231017342507-stable
Device is: Rooted (Magisk 26.4 [26400])
General Notes
Installed for 2 days now
Positive Notes
Finally, Browser & WebView was updated from last Bromite Version 108 (unmaintained for almost a year now) to Cromite Version 117.0.5938.156, still not the lastest but way to go
Looks like upgrade to Android T stable is on the horizon for FP4 1.17-t-20231109350751-stable image is already available. Looking forward to when this gets actually rolled out via OTA, if you dont want to wait you can already sideload the 1.17-t OTA upgrade manually. Iāll just take the time and wait
Issues
[UNSOLVED since v1.15] Issue with OpenCamera focusing, same as reported here: ācamera focus works fine though the rectangle appears red after tapping for focus on a certain area. Taking a picture results in a fine sharp photo.ā With v1.13 focusing was fine and mostly showed a green rectangle when with v1.15 there is now mostly a red one
Are you still referencing to this issue here?
I just tested this with FP4 on 1.17-s, doing calls
With bluetooth headphones: Volume slider offers a wide range to lower or increase the volume, from very loud to nearly inaudilbe, best
With USB Headset: Volume slider is very small, only allows to choose between a limited range of volumes, lowest volume is low, though (like it should be)
Just speaker, without any headphones: Volume slider is very small, only allows to choose between a limited range of volumes, but the lowest volume level is quite loud in comparison to the above.
So, yeah, if those small volume sliders when calling someone are not a āfeatureā of Android 12, the lowest volume option on built-in speakers.should not be that loud, I guess.
Version previously: /e/OS 1.16-s-20231017342507-stable
Not rooted
Wanted to update to 1.17-s stable OTA and went into bootloop AGAIN. So I had to unlock the bootloader AGAIN to change the slot. Then I installed 1.17 t stable via adb sideload and now the device ist stuck in a fastboot loop unless I unlock the bootloader.
Hi. You could download the previous version of eOS, copy it to your external SD card and install it from there with the eOS recovery - like you did the first time you installed eOS.
Gigaset
GS-290
GS290
1.16s-20231017-stable-GS290
not rooted
New version available from yesterday, tried to install twice. Both attempts failed, after reboot still on 1.16. Now this afternoon click Refresh button - 1.17 is no longer available.
Version of /e/OS or Stock which existed previously : 1.17S from android stock12
Is the device Rooted / Not rooted: Not rooted
trying the stable S
i canāt access the recovery. i think there is some issue with the recovery zip as if i switch to the lineage recovery, i can access the recovery but i canāt complete the OES1.17S install because of an SPL error - downgradeā¦
i believe because linage recovery 20 is on A13.
if i try a precedent lineage20, no SPL error but EOS1.17S canāt be installed due to a different vendor nameā¦ file expected for Oppo Nord while are for Nord onlyā¦ this is the error reported more or lessā¦
what a confusionā¦
other installed on Nord without any issue?
i had been able to put Eos 0.23 when i had Android 10 in the pastā¦
That is right. But in the meantime Iāve installed 1.17t. I did a factory reset and made a clean installation. After this I had no more trouble with my phone calls. Volume control works like it should. I have no idea what was the reason to be honest. But its ok, problem is solved.
I decided to leave the bootloader unlocked as Iām forced to. So I can install the next updates via ADB sideload and can change the slot if necessary.
But that was the second time among the last three updates I ran into that bootloop. Iām a little bit pissed offā¦