This is my second feedback as I have gone from eOS r to s:
Google
Pixel 4a5g
Bramble
previous version 1.7-r
not rooted
updated to 1.7-s
Stable
This is my second feedback as I have gone from eOS r to s:
Google
Pixel 4a5g
Bramble
previous version 1.7-r
not rooted
updated to 1.7-s
Stable
Faiphone 3+
Updated from 1.6 to 1.7-202300110250404
Not rooted
Sadly have to report same bugs as some before:
Any chance for a quick bug fix on the above? This is making /e/OS very though to useâŚ
Thanks a lot!
Try clearing cache and storage for the âTrebuchetâ app. Settings | Apps | Show all | Show system
Thanks for your response!
Assuming you mean try clearing the cache & storage for the BlissLauncher?
I donât have Trebuchet showing up in App info.
Tried clearing the cache of BlissLauncher already, was not a fix. Can push it as far as clearing storage if you think that might help?
No, I mean Trebuchet. It is installed as a system app (though you canât use it as a launcher / home screen app - thatâs a different bug ).
In Settings | Apps | Show all apps, you need to clock on the âthree dotsâ menu and choose âShow systemâ. Then either scroll down to Trebuchet, or use the search box
Thanks for the clarification
I just did as you suggested (clear data&cache for Trebuchet), but getting the same crash.
In Bliss ⌠so you could go on to do this. It will have the effect of reorganising all your apps layout to the Bliss default on the home screen.
It is also significant that Bliss should Open by default in Apps and notifications.
That is to say that Apps and notifications > Default apps shows Bliss as the default Home screen
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/ OS 1.6 (stable version, Android 11)
Is the device Rooted / Not rooted: not rooted
Problem: GPS localization fails (except within Here WeGo app).
Location
⢠Settings - System - Advanced - microG - Self-Check: all ok, including location permissions
⢠Settings - System - Advanced - microG - Location modules - Mozilla Location Service: enabled, configured for using Wi-Fi and Cell
⢠Settings - Advanced Privacy - Location: Exposed
⢠Settings - Advanced Privacy - Manage my location: Use my real location
⢠Settings - Location - Wi-Fi and Bluetooth scanning - Wi-Fi scanning: enabled
⢠Settings - Location - Wi-Fi and Bluetooth scanning - Bluetooth scanning: disabled
⢠Settings - Location - App permission - âAllowed only while in useâ: Apps are listed
(setting descriptions copied from AnotherElk , I hope you donât mind, AnotherElk)
Vendor Name: Google
Device name: Pixel 4a
Device CodeName: sunfish
Version of /e/OS or Stock which existed previously: 1.6 r stable
Is the device Rooted / Not rooted: Not rooted
Did not notice any issue so far.
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.6-s-20221201239247-dev-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.7-s-20230111250406-dev-FP3.
The following things work for me:
Surprisingly deleting Bliss launcher data seemed to do the trick (only for the crashing bug reported) - two other issues still present.
Thanks a lot for helping troubleshoot - much more useable now!
Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.6-q-20221204240086-dev-FP2
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.7-q-20230112251029-dev-FP2.
The following things work for me:
I gave this hint to others but did not check it for my own phone âŚ
now I find that after update APs functions âtracker blockerâ and âfake my locationâ were ON whereas they were OFF before update.
Not a big thing but can be quite confusing, so in my opinion an update should avoid changing essential settings.
Iâve started to see something unusual since upgrading to v1.7, though I have no idea if itâs connected to that upgrade or not.
Sometimes, on waking, black vertical lines are drawn about 40% from the left side of the screen.
Affter a few seconds, some of them disappear. Often one line remains for some time, though eventually it too may disappear (but also sometimes not).
This does not appear to be a problem with my deviceâs screen, since the lines can disappear on their own.
Is this any kind of known problem with e/Lineage of this version, perhaps running on particular devices such as my xz2c?
Hello,
I have a problem with the OTA upgrade 1.7 on my S8. Previous OS was 0.23 from /e/shelf.
The âinstallâ phase went quite well and the phone works (phone, data, internet and most apps). Meanwhile, I have this notification
âsystem android
Finalisation de la mise Ă jour du systèmeâŚâ (processing the update)
and a progress bar which is not progressing at all since yesterday more than 14 hours now. The notification come back after any restard, with the only change as a different position of the progress bar, quite erratic.
I cannot cancel the notification. It says âimpssible de modifier ces notificationsâ and I cannot find an ongoing app to end.
Misfunctioning app:
App Lounge can upload new app or updated app, but stop at the time to install. Meanwhile, Aurora works as previously.
impots.gouv (French) demand to âCheck that Google play is enabled on your deviceâ, but I suspect it is a request of the last update.
Otherwise, everything is fine and quick.
Thank you for this /e/OS.
Rule 1: be patient. My problem is solved.
About 20 hours after I lauched the installation of 1.7, my device restarted on its own. The notification for âfinishing updateâŚâ is no longer present. So it was a long process.
The App Lounge is fully functionnal.
Moreover, my banking apps which were half disabled for the alleged reason of ârouted phoneâ are now functionnal.
Once again, thank you for this great OS.
Update:
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.
There seems to be a 1.7.1 build for FP3, but I donât find any communication about it on the forum. Does anyone know about it?
I am also curious what the reason for this âhotfixâ is. As far as I see, there is no information for now.
Only for R stable so far, it seems.
https://images.ecloud.global/stable/FP3/
https://images.ecloud.global/dev/FP3/