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/
Hello,
I noticed some bugs when using two sim cards:
Call reception
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.
Oneplus nord V1.7-20230110250404
Sim 1 = orange
Sim 2 = bouygues
Not speaking English I use a translator, cordially
I am experiencing extreme battery drain with my fp3 (battery down in a few hours) and it now takes longer to restart.
Let me check about this and get back.
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?