The response received to the issue I raised on Gitlab is that the intention is to rectify issues arising from the changes made in v1.7 to App Lounge.
The response also confirms that these changes affect already installed apps as well as new installations - currently you will not be able to update the Play store version of an app if it is also present on F-droid without first uninstalling it and then installing the F-droid version. This may result in reduced functionality when the two versions have different features.
The predefined colors on each card do not work well when a call is received (background color)
Example: Sim 1: red and sim 2: blue = call sim 1 red call sim 2 red. which complicates the visual on the origin of the calls.
Voicemail
The display of the two voicemail boxes at the same time is impossible, we first see sim 0 then sim 1, but the display of sim 0 disappears
Impossible to delete a message with both voicemails activated when it works when there is only one
When there are two messaging systems to activate and one is deactivated, the messaging tab disappears while there is still one active. have to deactivate both then reactivate one.
I created a ticket, but they told me to file a bug report and I donât have much time, I made video captures and am ready to share them with a developer if interested.
We had a complaint from some FP3 users that they were unable to boot after the update. This update was specifically to address that issue.
There is a document addressing this issue - specific to FP3 post v1.6
The document doesnât explain why thereâs a 1.7.1-r build, as the fix âafter v1.6 updateâ explained there wasnât involving 1.7.1-r initially. 1.7.1-r is in the downloadable ZIP file there right now, but the text still references the earlier 1.7-r build as the fix instead.
So the question would now be whether the 1.7.1-r build is really connected to this issue. Was it made because the earlier 1.7-r build wasnât sufficient as a fix for this issue?
Update from the team:
No it fixes only the recovery issue that users encountered after the upgrade from /e/OS below 1.3-q to 1.Y-r. Now users can only perform the upgrade from 1.4-q to 1.Y-r. (where Y can be 5,6, 7âŚ)
Anything regarding the âOverlaying app detectedâ issue on the FP3 with some banking apps?
Should an issue be raised on gitlab directly, or what is the best way to proceed?
Today I discovered this âOverlaying app-problemâ while operating the German comdirect-APP. Disallowing all overlaying-grants doesnât help to fix the problem! Help urgently wanted!
Version of /eos e/os/1.7-s-20230110250403-stable-fp4
rooted
Update itself worked flawlessly.
What I encountered was that images taken in HDR mode had a strange color effect (without any filter being set). Deleting camera data reverted this to normal.
What changed is that the lens is now shown as text - much better as there is now less confusion with the button to change front/back camera.
Still in camera app tapping lens will first change to wide lens, then to a 3rd lens (that does not exists, so an error is thrown). This behaviour has not changed.
Also unchanged is the speed of the autofocus: extremely slow. Taking pictures might take seconds (or does not start at all if the object is moving). That is quite annoying.
Overall the update did not change anything notably to the worse and it is a joy to work with /e/os. Also battery life is extremely good (though I have no real life comparison with my fp4).
Version of /eos e/os/1.7-s-20230110250403-stable-fp4
Not rooted
Everything works well. Did not notice any new bug.
Still not able to rotate and save pictures that are stored on the SD card with the native gallery app, but this is a minor bug as I can do it right with âsimple gallery appâ.
Thank you to the whole team for their valuable work!
When charging while the phone is turned off, the circular charge-level gauge eternally remains at the same level, not reflecting the actual charge level youâll see when booting up. I hope itâs just a display issue and not something that could set the battery on fire by overcharging it, haha.
Vendor Name: Sony
Device name: Experia XA2 Ultra
Device CodeName: discovery (H3213)
Version of /e/OS or Stock which existed previously:
1.6-s-20221201239247-dev-discovery
Is the device Rooted / Not rooted: Rooted
Turned my device on today, OTA update notification arrived. Performed update which seemed to go well at first but on reboot I got stuck on the recovery screen (which did show v1.7). Tried setting bootslot to âaâ with fastboot (was on âbâ) and reboot - performed the update again, same result.
Did a full install (from Pop OS and following the install guide, which I think is very clear and simple to follow), and succeeded in booting 1.7-s-20230111250406-dev-discovery.
Will have to reinstall all apps and test.
My current experience (with 1.6) is: I really like that I can see and block trackers per app (such as my banking app that uses Google Analytics). Privacy mode does seem to slow down browsing, but it seems the battery lasts forever :).