Stock browser really fast.
Secure navigatins has been disabled by default and CANNOT be turned on. “This setting is enforced by browser”
I just got a report from the QA team members who tested Android Auto on the v3.6 build. The testing was done using FP5 and the build is the 3.6-a15-20260312593772-official-FP5
The issue is reported here in gitlab. You may not be able to read the QA comments as he marked it the response as internal. The summary is that Android Auto is working in their tests on v3.6.
Suggest you share your issue details on the same bug ticket in gitlab. They may need as much detail as possible.
Is it only possible to upgrade from 3.6.15 to 3.6.16 by performing a clean install, or can this be done as an update?
1 Like
As of latest 3.6-a16-20260319596015-community-dre Secure Navigation has been disabled by default and CANNOT be turned on.
“This setting is enforced by browser”
versión 145.0.7632.159
foundation.e.browser
1 Like
Shared with the development team.
1 Like
When do you see this error. Pl can you share more details as to what you were trying to do when this shows up.
There was an issue raised similar to this some time back and a forum issue which contributed towards it.
I was on 3.2-a15-20251025540112-community-dre and I was using Standard Secure Navigation setting available in stock e browser (configuration - privacy and security - secure navigation)
Today, I upated to latest 3.6-a16-20260319596015-community-dre and noticed browser navigation was very fast… So I checked Secure Navigatin and noticed it’s disabled and cannot be changed showing
Thanks.
@N200 safe-browsing was broken, as in, half disabled (and uses Google infra), see A bit concerned about Safe Browsing setting - #2 by tcecyk
If you want the feature, use a non default browser. I think Brave implements it too. “Safe Browsing” is a misleading title too. Adblockers do similar
1 Like
Today I definitely learned!
I had the same Android Auto issue on my Murena FP6 running v3.6, but I found a solution.
Android Auto updated to version 16.4.661034-release, and after that everything started working fine again.
The update didn’t appear in App Lounge for me. I searched for the Android Auto app manually from my FP6 browser:
https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead
If the update is available, install it manually. After updating, Android Auto works solid on v3.6.
2 Likes
Thanks for the update @Robbie linking this on the issue in Gitlab.
For example the QA team tested using the following required google apps
- version 16.4.661034-release com.google.android.projection.gearhead
- version 17.10.55.ve.arm64 com.google.android.googlequicksearchbox
- version 26.12.05.884026066 com.google.android.apps.maps
- version googletts.google-speech-apk_20260216.02_p0.871028523 com.google.android.tts
Feel free to add your inputs in Gitlab. Pl add Android Auto version details to your posts. That would make it easier for the developers to pin point the issue.
.
Vendor Name : Murena
Device name : Teracube 2e
Device CodeName :
Version of /e/OS or Stock which existed previously : 3.5
Is the device Rooted / Not rooted : not rooted
Version : 3.6 - a15 … why not a16 ?!
Thanks for the note about the update that refused to show up. Once I convinced Aurora Store to do something useful, I got the update. For some reason, though, all my AA settings were wiped so I had to spend the time adjusting to my preferences.
Media apps I use aren’t happy at all with the updates, though - Google seems to have decided that playing media should split the screen with maps or something, it’s tough to tell as both Tidal and Jellyfin crash when trying to launch now.
Probably very separate from /e/’s update, though… but holy dear lord do I hate the garbage “we need to change the UI all the damn time” stuff that’s pulled on users.
-
Vendor Name: Oneplus
-
Device name: 11
-
Device CodeName: Salami
-
Version of /e/OS or Stock which existed previously: 3.6 A15
-
Is the device Rooted / Not rooted: not rooted
“Dirty” Upgrade to 3.6 A16. Everything good so far. Nice job. Thank you!
1 Like
Success, installed on two devices 3.6 and it’s working fine.
Vendor Name: Samsung
Device name: Galaxy S7
Device CodeName: “herolte”
Version of /e/OS or Stock which existed previously: 3.5 beta
Is the device Rooted?: Not rooted
The second one:
Vendor Name: Google
Device name: Pixel 5
Device CodeName: “redfin”
Version of /e/OS or Stock which existed previously: 3.5 beta
Is the device Rooted?: Not rooted
2 Likes
I have the same issue on my FP6 with the latest eos update. I got communication error code 14 reported on my phone. Android Auto did not show up to be updated in the App Lounge. I performed a manual update on this App.
Regarding Android Auto not working on FP5:
I suspect the App lounge to be broken, maybe temporarily and/or only locally. At least for me, the recent AA version will not be patched, in addition, the app is “not found” by App Lounge, not inapp or through an android app store link. Circumvented that error with Aurora Store and getting the AA Update there. I forgot to to delete all local files from the app lounge first, so maybe resetting it to default also enables it again. I only noticed App Lounge to be fully broken after I wanted to install Brave browser, which was also suddenly not found. After resetting all app data Brave could be installed again. Hopefully, AA now works again, I’ll test it during the day, and if it’s not working, I will post it here. But my hopes are up as it seems not to be a specific v3.6 error but a version error of AA and App Lounge.
Edit: AA works again, wireless and with USB calble.
2 Likes
Murena CMF Phone 1
I just installed 3.6 and I’m impressed: the download speed has considerably improved! Thank you! (I had already noticed a big improvement when I installed 3.5 but it was in the middle of the night; I thought it was why.)
So far, so good; as far as I can tell, things are working as they should.
1 Like
Vendor name: Fairphone
Device name: FP5
Pre-existing version: /e/OS 3.4 stable / official
Device rooted: Not rooted
All is well. On the last step (I think “finalizing package installation”) the installation hovered at 0% for a few minutes and then it immediately showed the reboot button. After I rebooted, I’m now on 3.6.
