Feedback for v1.19.1

  • Device: Fairphone 3
  • Previous version: 1.17-s-20231111351092-dev-FP3
  • New version: 1.19.1-t-20240113373116-dev-FP3

As outlined by @AnotherElk, I downloaded the new version from https://ota.ecloud.global/api/v1/FP3/dev, since it was a system upgrade from Android 12 to Android 13 and I didn’t want to make a fresh install that would’ve wiped all data.

New issues

I have not yet observed any issues that hadn’t already been present in Android 12.

Persisting issues

Issues that had been present in Android 12 and are also present in Android 13:

Persisting issues
  • NFC doesn’t work properly on Android 11, 12 and 13 anymore (5088)
  • SIM card name disappears when entering PIN (5089)
  • System profile automatically chooses secondary SIM for cellular data (5395)
  • Power-off alarm not working when phone connected to power source (6150)
  • Advanced Privacy (and possibly other VPNs too) are unable to connect immediately after the upgrade (6793)
  • Randomized MACs are not available (7199)
  • Screen recordings don’t record system sounds (7026)
  • It is not possible to block access to the front camera (7044)
  • NFC trigger for lineage system profiles does not work (7446)
  • Visual distortions on boot (7714)

Fixed issues

Issues that had been present in Android 12 but are not present in Android 13 anymore:

Fixed issues
  • Nothing happens after entering SIM card’s PIN (6443)
  • On/off menu unusable in landscape (6722)
  • Finger taps are not visible in screen recordings (6723)
  • Clock alarm invisible after creation (7465)
1 Like

Thank you, for the suggestion.
That option is off.
Interestingly, turning them on and off, does not help either.

Edit: found a bug report with a workaround regarding the issue: #6842
The relevant setting is found under Sytem > languange and input > on screen keyboard > AOSP > Settings

Interestingly, that setting does not show up when searching the settings

Hi,

Thanks for sharing @pixelphone2

After a few days of use. When I have the internet on (from time to time), the email application tells me that it can’t connect to my email addresses.
I have to go to the settings, make the password appear (confirm its appearance with the fingerprint), then do next. If you don’t make the password appear, it doesn’t work.

Sometimes, if I do nothing, the email addresses resynchronise themselves.

Otherwise, Etar (calendar) doesn’t share very well with my partner’s calendar. I think the bug was there before (a few days ago). This is blocking and problematic. In the meantime, I’m going to switch to Proton Calendar.

This isn’t a bug, but an observation: on the latest Android version, when you choose the sound with the keys, there’s a phone part and a bell part. It’s quite complicated to know which one is working to set the sound correctly. I don’t find it very intuitive.

Thank you very much
My pleasure

1 Like

I don’t really know if it is a good idea: if the phone is mine, I remove the battery for a while

  • Vendor Name: TeraCube
  • Device name: 2e
  • Device CodeName: emerald
  • Version of /e/OS or Stock which existed previously: Stock, as shipped

Installed, from Stock, as per what I believe to be an old version of
the command-line instructions page:

https://doc.e.foundation/devices/emerald/install

as I have a downloaded version of the page that has a lot more
“troubleshooting” info displayed on it?

Just wanted to note, in case it’s of use to anyone looking for
info about the same thing, that the one thing that tripped me
up, until I realised what was actually happeneing, was that I
kept being told, when running ‘adb’ commands, that the device
was “unauthorized”.

The emerald install page I have a copy of, has a link to

https://doc.e.foundation/pages/unauthorized-device.html

which says

  1. Check the box on the popup on the device.

however, during the install process, the phone was re-starting
onto a screen that didn’t show the “allow access” pop-up, and,
as I eventually discovered, required me to swipe past it, in
order to see that pop-up: indeed, a couple of them!

Once I could see them, and confirm the access, everything then
proceded as per the install doc.

Thinking that it might be worth mentioning, that the “allow access”
pop-up might not be immediately visible, on one of the e-OS support
pages.

HTH someone.

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

No issue with updating, now on 1.19.1-t-20240113373116-dev-FP3.
Upgraded from /e/OS Android 12 (S) dev to 13 (T) dev without wiping the phone (for now, I’m prepared to still do it in case of weird issues, it’s a major Android version upgrade after all) via unofficial ADB sideload way, see here.

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)
4 Likes

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

No issue with updating, now on 1.19.1-r-20240110372392-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.1
  • Bluetooth (music playback, data connection)
1 Like

Updated my FP3+ and everything seems fine except my phone torch / flashlight is now flashing rapidly when turned on.

Saludos:
Vendor Name: Xiaomi
Device name: Redmi note 9 Pro
Device CodeName: miatoll
Version of /e/OS previously: e-1.18-s
Device not rooted
Updated OTA
Thanks

1 Like

Saludos:
Vendor Name: Xiaomi
Device name: Mi 10T Lite 5G
Device CodeName: gauguin
Version of /e/OS previously: e-1.18-s
Device not rooted
Updated OTA
Thanks

I took test pictures with auto flash … worked as intended for me. Torch is working as intended, too.

  • Asus
  • ZenFone Max Pro M1
  • X00TD
  • Stock 9 Pie
  • Not rooted

Using a 084 firmware solved heating issues on the phone. Also legacy login with Google is working for apps that never did. WhatsApp backup working without any problem from previous MicroG builds.

Vendor Name: Gigaset
Device name: GS290
Previous /e/OS: 1.18
Device status: Not rooted

Updated via OTA. Very happy with update. I have found that the UI flow has become smoother. As ever thank you very much.

Vendor: Motorola
Device: Moto G 5G Plus
Device CodeName: nairo
Version of Stock which existed previously: QPN30.37-Q3-42-51 (Android 11)
Is the device Not rooted


Build 1.19.1 works, but the home screen display is faulty. The four lower standard apps are not displayed (see screenshot)

Despite multiple deletions via ‘Clear storage’ and ‘Clear cache’, the 4 icons aren’t displayed.

You can add them manually, same as moving icons from one page to another.

2 Likes

@smu44, many thanks for the tip! Yes, it works perfectly. The screen is probably so big (6.7 inches, 1080 x 2520 px) that all apps still slide to the top.

1 Like

i had problem with Browser on this Forum, so i downgrade to previous version (e-1.18-r)

  • Vendor Name : Samsung
  • Device name : s4 active
  • Device CodeName : jactivelte
  • Version of /e/OS or Stock which existed previously : e-1.18-r-20231209360969-dev-jactivelte
  • Is the device Rooted / Not rooted : not rooted
Vendor FAIRPHONE
Device FP3 / (3+)
Device FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.17-s-20231111351092-dev-FP3
Device Not rooted

Did the Upgrade via “adb sideload” as described in some posts here.
Everything went smooth. No data loss.
Good job, thanx to the team.

Found one restriction: I’m not able to stop / kill Bluetooth Service
Now there are no more buttons to control this service.
Can someone confirm this?

Can’t confirm. Bluetooth tile is still where it was before in the quick settings menu, and works.

Sorry for my inaccuracy. I didn’t meant the tile
but the “App Info”. For Comparison:


vs