Feedback for v1.14

  • Vendor Name Fairphone 4
  • Device name FP4
  • Device CodeName FP4
  • 1.13-s
  • Not rooted

Bluetooth is completely broken. I have 2 different BT Headsets which can be paired, but no audio.

I also have a PineTime smartwatch which can’t connect at all.

→ Cleared Cache of BT and Wifi → no Change.
→ Repairing Headset → no change.
→ Turning off HD-Audio: Qualcomm aptX audio → Audio plays.
→ Pairing with PineTime still fails.

This is an really bad thing as I use my FP4 80% only for listening to Podcasts and watch YT with headphones :frowning:

1 Like

Same for me. I really hope we can have a hotfix here. Waiting for 2-4 weeks(?) seems really annoying for me right now. Maybe its possiblr to roll back to 1.13?

There is no easy rollback in Android nowadays, in short.
But you can install the older version from scratch, which will delete your data.

Vendor Name: Murena Fairphone
Device name: 4
Code name: FP4
Version of /e/OS which existed previously: 1.13
Rooted: no

I found 2 issues so far.
First some Problem with blue tooth audio.
HD-Audio: AAC, worked,
but HD-Audio: Qualcom® aptX™
dosent work anymore.
Standard audio worked also.

The secound, was that the “updater programm” crashed.
I fixed it by clearing the data storeage, but i lost my saves of the former OS’s.

1 Like

Galaxy S7edge
1.13-q-20230724313392-stable-hero2lte

Not seeing the update in the updater, although there is one online:
https://images.ecloud.global/stable/hero2lte/

Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.13-s-20230727314102-dev-FP3
Is the device Rooted / Not rooted: Not rooted

No issue with updating, now on 1.14-s-20230819321663-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.0
    (nightly 27.01.2023 - for sync with Betterbird instead of Thunderbird)
  • Bluetooth (music playback, data connection)
2 Likes

Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.13-r-20230727314472-dev-FP2
Is the device Rooted / Not rooted: Not rooted

No issue with updating, now on 1.14-r-20230817321316-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: enabled
    • 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.0
    (nightly 27.01.2023 - for sync with Betterbird instead of Thunderbird)
  • Bluetooth (music playback, data connection)
2 Likes
* OnePlus
* 6t
* Fajita
* 1.13
* Not rooted

Wifi will not work after update. I had this problem previously on another phone, but it was fixed after updating the recovery. I therefore tried updating the recovery to 1.14. This did not fix wifi, which is unfortunate because I do not have cell service where I live.

After updating recovery to 1.14 and verifying non-functionality of wifi, I decided to try re-installing e-1.14-s by downloading the full package from the website and applying via adb instead of using the OTA update option. This did not resolve the issue.

After this, I ADB installed 1.13 and wifi worked. I will be skipping this version I guess. I’ll try 1.15 or any further hotfix or w/e of 1.14 and update if it doesn’t work.

Did you refresh a few times? (Refresh icon top right in the updater)

20-60 times every day, last several days…
I’m about to tcp_dump to see, where it goes… do you know the server the OTA app requests, by any chance?

It isn’t there: https://ota.ecloud.global/api/v1/herolte/stable but is here https://ota.ecloud.global/api/v1/herolte/dev. Stable is always last.

Fairphone 3+
FP3
Updated from v1.13-s-stable
Not rooted

Update went smoothly - 40 minutes to complete (rebooted 1st, screen set to stay on & phone not used during update).

Initial tests show no problems - thanks for all the good work.

Had the two issues noted in earlier posts of the Maps app icon moving to final screen and Updater closing but these readiliy resolved as described.

My outstanding issue (dating from v1.9) is phone still not reconnecting to a Proton VPN server when I try to change VPN server or on reboot (issue #6793 in Gitlab).

I’m on: 1.13-q-20230724313392-stable-hero2lte

but in either case - and others I checked – I find mostly:

{“incremental”:“eng.root.20230312.212838”,“api_level”:“29”,“url”:“https://ota.ecloud.global/builds/full/dev/hero2lte/e-1.9-q-20230312268823-dev-hero2lte.zip”,“timestamp”:1678656493,“md5sum”:“8acf1b7f322325c088474831ecf11579”,“changes”:“”,“channel”:“dev”,“filename”:“e-1.9-q-20230312268823-dev-hero2lte.zip”,“romtype”:“dev”,“datetime”:1678656493,“version”:“1.9”,“pre_version”:“”,“display_version”:“1.9-20230312268823”,“android_version”:“10”,“id”:“a74bebae6e50d0fe3039e5ea84f2d223ca13b7e8db00509bfa38c5d31baf3957”,“size”:1038025683,"is_upgrade_supported":false}

Is "is_upgrade_supported":false the cue to look for? In dev and stabel?

Find ( ^ F ) 1.14 in the JSON view. Sorry missed the 2 … I see the same result with hero2lte urls.

Vendor Name Fairphone 4
Device name FP4
Device CodeName FP4
updating from 1.13-s
Not rooted

Just like reported before bluetooth is brocken.
Cleared Cache of BT and Wifi → no Change.
Turning off HD-Audio: Qualcomm aptX audio → Audio plays.

1 Like

No probs – I have this one too – also not showing q.14

This is in the return:
{“incremental”:“eng.root.20230816.164233”,“api_level”:“29”,“url”:“https://ota.ecloud.global/builds/full/dev/hero2lte/e-1.14-q-20230816320942-dev-hero2lte.zip”,“timestamp”:1692204126,“md5sum”:“7c6cb6d4110065a3e128ef28acefdb86”,“changes”:“”,“channel”:“dev”,“filename”:“e-1.14-q-20230816320942-dev-hero2lte.zip”,“romtype”:“dev”,“datetime”:1692204126,“version”:“1.14”,“pre_version”:“”,“display_version”:“1.14-20230816320942”,“android_version”:“10”,“id”:“c8d7edb195360302e9600f95815ed5a4c10e5fc6f40674b3e4fcb7d5302e397a”,“size”:1047711195,“is_upgrade_supported”:false},

It’s “channel”:“dev”, but I’m on stable

Initially, and then I refreshed 1 time …

Thanks … interesting how the “staged rollout” might work ! I did refresh a number of times before posting, and again now ! and now !

I guess this demonstrates the nature of the rollout … (and the pointlessness of my comment).

It seems that 1.14 broke BT audio on FP4.
I did not notice this issue on mine since I don’t use a BT headset.

I assume one should raise an issue ticket on Gitlab (?) Otherwise this problem won’t be handled…

Me too!

It has arrived.