Feedback for v1.16

Namaste Manoj,
nope.
We own 2 Gigaset GS290 with /e/-OS and we do not face issues with sending SMS yet.
My device is on v1.16-s the other is on v1.15-s.

We noticed in the past sometimes different behaviour of the phones, especially the second one had once issues during the update via OTA. The second one is approx. 12 month older than my daily driver.
Br.

Where do you see “com.media… keeps stopping” message? I’m hoping to create an issue in gitlab. Currently awaiting access to gitlab.

Hi kirk! When sending SMS, often first message is sent ok, but mostly after second message, a notice appears on top of the messages. Sometimes second message is sent ok, despite of …“ImsApp keeps stopping” notice, but often I get “failed to send message” notice, that appears under the message with smaller letters, like delivery confirmation. Message is not sent. Some website recommended setting APN to “default”, but it didn’t help. I send SMS commands to remote controlled temperature sensors, and the response comes as SMS message. It used to come within maybe 10 to 15 seconds, now it lasts longer, over one minute. Would all of this be indication of problem at operator’s server, or something like that? Problem just happened to appear after 1.15-s update?

OTA new version: 1.16-s-20231017342507-stable-FP4

Vendor name: Fairphone
Device name: FP4
Device code name: FP4
Version of /e/OS or Stock which existed previously: 1.15-s-20230913330639-stable-FP4
Device is hidden Magisk rooted

Until now no problems detected.

Thanks :slight_smile:

  • Vendor Name - Teracube
  • Device name - Teracube_2e
  • Device CodeName - Emerald
  • Version of /e/OS or Stock which existed previously - 1.14 S
  • Is the device Rooted / Not rooted - not rooted

Everything working fine

Hi mok,
My problem might be different to yours . Also I’m not using mediatek. After installing 1.15s (and also 1.16s), on my phone, no SMS sends are possible.
Do I think this is an operator problem? I would guess not, it’s no coincidence.

Hi! I encounter the same issue as @Pazu since 1.16 update: I can’t control the call volume at all now, whereas I could before 1.16. Even set to the minimum, the volume is so high that it’s no longer possible to keep calls discreet, which is rather annoying.

  • Fairphone
  • Fairphone 4
  • FP4
  • 1.15-s
  • Not rooted

edit: issue #7509 corresponding to the problem has been opened by another user.

2 Likes

I find that if I restart and then click Resend on the message that was stopped by Mediatek, the message goes.
Which is similar to what someone said earlier that the first text after restarting goes and it’s likely that the second message is where the problem returns.
stanley

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)?

https://images.ecloud.global/dev/star2lte/

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.