You can add your comment to #7509
For help on how to raise and issue or comment on gitlab check this guide.
Hello @jalmer ,
Can you confirm me that your bluetooth is working fine ?
Mine is no more working: no device detected by my S10 and my S10 is not detected by other devices. It was working normally in the previous /e/os S release.
I cleared the cache of the bluetooh app but no effect !
Thank you
Dear @Lionel.R I teste right Now a Bluetooth Key Finder Musegear and Bluetooth Speaker and both are working.
Best regards Johannes
1 Like
Vendor Name: Samsung
Device name: S7
Device CodeName: SM-G930F
Version of /e/OS: 1.15 Q
Not rooted
No problem so far
1 Like
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.15-s-20230916331435-dev-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.16-s-20231019342893-dev-FP3.
The following things work for me:
- Call / be called
- Send SMS / receive SMS
- Notification LED
- Alarm
- Internet via Wi-Fi
- Internet via mobile network
- Wi-Fi hotspot
- Location
- Settings - System - microG - Self-Check: all ok, including location permissions
- Settings - System - microG - Location - Wi-Fi location - Request from Mozilla: enabled
- Settings - System - microG - Location - Wi-Fi location - Request from Hotspot: enabled
- Settings - System - microG - Location - Wi-Fi location - Remember from GPS: enabled
- Settings - System - microG - Location - Mobile network location - Request from Mozilla: enabled
- Settings - System - microG - Location - Mobile network location - Remember from GPS: enabled
- Settings - Advanced Privacy - Location: Exposed
- Settings - Advanced Privacy - Manage my location: Use my real location
- Settings - Location - Location Services - Wi-Fi scanning: enabled
- Settings - Location - Location Services - Bluetooth scanning: disabled
- Settings - Location - App location permissions - “Allowed only while in use”: Apps are listed
- Compass
- Screenshot
- Main camera (original FP3 Camera module, not +) photo + video
- Selfie camera (original FP3 Top module, not +) photo + video
- USB connection to PC / MTP
- MyPhoneExplorer 2.1
- Bluetooth (music playback, data connection)
Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.15-r-20230915331434-dev-FP2
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.16-r-20231020343335-dev-FP2.
The following things work for me:
- Call / be called
- Send SMS / receive SMS
- Alarm
- Internet via Wi-Fi
- Internet via mobile network
- Wi-Fi hotspot
- Location
- Settings - System - Advanced - microG - Self-Check: all ok, including location permissions
- Settings - System - Advanced - microG - Location - Wi-Fi location - Request from Mozilla: enabled
- Settings - System - Advanced - microG - Location - Wi-Fi location - Request from Hotspot: enabled
- Settings - System - Advanced - microG - Location - Wi-Fi location - Remember from GPS: enabled
- Settings - System - Advanced - microG - Location - Mobile network location - Request from Mozilla: enable-d
- Settings - System - Advanced - microG - Location - Mobile network location - Remember from GPS: enabled
- 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 access to location - “Allowed only while in use”: Apps are listed
- Compass
- Screenshot
- Main camera (Camera module 12 MP version 2) photo + video
- Selfie camera (Top module version 2) photo + video
(Camera records completely black video from the moment surrounding light is too dark or changes into too dark when moving … years old issue I already had with Open Camera on LineageOS, can live with it.) - USB connection to PC / MTP
- MyPhoneExplorer 2.1
- Bluetooth (music playback, data connection)
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 1.15-q-20230913330637-stable-herolte
now: 1.16-q-20231017342506-stable-herolte
not rooted
… no issues …
Thanks a lot for keeping that hardware alive!
1 Like
I have a FP4. Install of 1.16s was smooth and easy. Only issue I have is if I do a call my speaker sounds loud like a PA-speaker. Settings are on minimum but without effect.
So are mine and that seem to be a general problem.
There seem to be an Github issue already according to some post above.
Hello all.
Is there a reason why my S9+ (1.15 dev) has not received an “update ready” notification for 1.16 ? (as I see that 1.17 is arriving … I’m a bit puzzled)
Thanks.
Maybe because your device is still running on Android 10 (Q)?
There would be a reason if you would still be on Android 10 (Q) … please refer to [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc.
There are /e/OS 1.16 dev builds for your device based on Android 11 (R) and Android 13 (T) currently, 1.15 seems to have been the last Android 10 (Q) build according to https://images.ecloud.global/dev/star2lte/.
It is likely that only the T builds will continue to be built, as update support for multiple basic Android versions on a device was dropped a while ago.
Ok, thanks (don’t remember this was announced / reminded recently, but I may have missed it).
So, it seems I’m doomed for a full manual OS R or T install and the many hours and energy to invest for that 
, as no OTA exists for dev builds IIUC.
Do you have an advice about which build & version I should choose ? (seems there’s stable R, dev R and dev T available for 1.16 AFAICS).
Thanks.
The announcement about supporting only one version of android per device and the explanation of why support for older versions is being dropped, is under subheadings of the Weekly Development and Testing updates post. Not sure how many weeks ago the info first appeared in the post but at least in my browser you have to click on the subheadings themselves for the info to be visible otherwise you just see the sub-heading bullet point, so that could be why you missed it.
2 Likes
Correct.
Since you are in for a new install anyway, waiting for T stable might be worth it, as an OTA upgrade via the updater from R to anything newer seems nowhere on the horizon for your device currently, and R builds will be dropped in favour of T as per announced current build policy.
So with T stable you would have the newest Android base, and while there’s no guarantee future upgrades to new Android versions will be available OTA via the updater, on the stable release channel at least the possibility exists.
1 Like
Thanks a lot guys, very clear !
But … as my S9+ was not purchased to murena.io, is it really eligible for installation of a “stable” build type ?
Reference : https://doc.e.foundation/build-status#stable :
These builds are currently only available on the Murena smartphones
Murena smartphone are phones purchase through the murena Shop"
Yes, the restriction to the phones sold by the e foundation was the initial stance, but it was loosened in the meantime. (@Manoj: https://doc.e.foundation/build-status#stable needs updating.)
You can install what’s available via the download pages.
Also, the S9+ is supported by the Easy Installer, and the Easy Installer installs only stable.
1 Like
For some reasons, I can’t access 1.16 version on my pixel 5, I look for updates but it always tells me that there is no update available for my phone, I begin to worry a bit that I’ll have to use the easy installer to update my phone.
If you are using 1.15-s-stable (how to check), this would seem to be correct, as 1.15 is the last S (Android 12) version on offer.
Currently you could either install 1.16-t yourself, or you could wait for the /e/OS developers to finish work on the OTA upgrade from S (Android 12) to T (Android 13) via the updater (= without wiping your data, if the upgrade works out as intended), you can follow proceedings in https://community.e.foundation/tag/development-updates …
(redfin is the codename of the Pixel 5, see https://doc.e.foundation/devices)