Feedback for v1.10

Can I just do the sideload command or do have to format the phone, etc.?
=> “Denying OTA because it’s SPL downgrade” I guess I have to format…

Have upgraded to 1.10s (Samsung Galaxy S10+) and it’s working well.

But I see the already reported issue around Advanced Privacy and Microsoft login URL is still present (if Advanced Privacy is on, neither Teams nor Outlook can connect).

Yes … I seem to remember more than one report of “touch screen / touchscreen is not responding” in brief searching I found this (is OnePlus 7T Pro ‘hotdog’) Feedback for v1.9 - #17 by anon29344687 . Might be worth investigating further before you wipe your data ?

Also: OnePlus 8T Touchscreen Doesn't Work After Install

2 Likes

I have backups :slight_smile: )
Thank you, I will try this tonight.

If you look at Advanced Privacy in more detail you can enable/disable the trackers found within outlook on a case by case basis. Normally, from memory, you only need to disable “mobile engagement” to send the emails.

Maybe it could help…

I tried performing the update on FP3, from 1.9.1-s, but my device is now stuck on boot screen.
I have just created a topic for this:
Device stuck on boot screen after 1.10-s update - FP3.

Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3
Version of /e/OS which existed previously: 1.9-dev
The device is: Not rooted

1 Like

Hello,

My Fairphone 3 was running /e/OS-1.9.1-s;
a few hours ago I downloaded the proposed 1.10-s update (can’t see the exact build version, given my issue).
After the background update process finished, I have hit ‘restart’ but now my device is stuck on boot screen (with “Fairphone” and “Powered by android”, not the one with /e/ logo) since 1 hour.

I fear that pressing Power+Volume buttons might break it even further, as it was performing an update.
Can I do it? Or do you have any other advice?

I know of this feature, but it still doesn’t work for these two apps.
I remember reading something in a thread (maybe in the 1.9 feedback thread, but I can’t exactly remember) that there is a bug: when advanced privacy is enabled, one of the URLs needed for Microsoft login cannot be accessed, at all - it was officially logged as a bug. It seems the fix for this bug was not included in the 1.10 update (hopefully it will make it into the next update)

1 Like

After that much time, you can do it, there’s not much else to do.

Keeping the power button pressed for about 15 seconds will force a reboot.
Keeping Volume + pressed while starting/rebooting the phone will boot the phone into recovery mode.
Keeping Volume - pressed while starting/rebooting the phone will boot the phone into Fastboot Mode.

2 Likes

I did that in the end, and it worked. My phone now shows 1.10-s-20230413279105-dev-FP3 as current version.
Tried rebooting a second time without issue.

Thank you.

Note: my storage only has 4.63 GB (now, after the update is finished). Could this be a cause of the issue? (Since it is an A/B device, I suppose not, but just asking)

1 Like

Hello,

  • Xiaomi
  • Mi8
  • dipper
  • previous /e/ version: 1.10-beta.2-s-20230403274741-dev
  • not rooted

I left the test channel and updated to 1.10-s via OTA. No install bug and the device is ok.

Thanks to the Team!

1 Like

I cannot definitely say if this caused it, but I’d strongly recommend to clear some storage. There’s no fixed amount, but I usually recommend to other FP3 users to keep 20% free (it appears there’s just over 7% left on yours) to avoid laggy performance, slowly launching apps etc.

1 Like

Samsung S8 (950F)
Prev ver: 1.9
not rooted
all seems ok

1 Like

On FP4 stable the build is visible here but not with the updater on the device.

The 1.10 doesnt appear ota when i go to update. It says my 1.9 is thr latest build

Can someone post step by step guide for fp4 on how to manually update to 1.10

I have magisk isntalled, would that update break it? Does the phone need bootloader unlocked ? Will we be able to relock the bootloader with the new security patch update?

Hello,
on my Poco F3 (alioth, not rooted), update was fine from 1.9 to 1.10.
All seems to be OK.
Thanks

You should be able to update OTA. Still not available for FP4.

Builds will be rolling out in a staggered manner over the next couple of days. It will be released for a few devices at a time.

Hello
Vendor Name: Xiaomi
Device name: Mi10T Lite
Device CodeName: gauguin
Version of /e/OS which existed previously: 1.9-s-20230311268558-dev-gauguin
and 1.10-beta.2-s-20230403274741-dev-gauguin
The device is: Not rooted

English version below

J’ai eu plusieurs un souci au passage de 1.8.1 vers 1.9 qui m’ont obligé à repasser sous ROM Stock.

J’ai suspecté la modification du fichier /system/build.prop que j’ai effectuée pour faire fonctionner mon application bancaire (Xiaomi, faut-il rebloquer le bootloader - #3 by saroumane38).

Aussi pour cette migration j’ai procédé en 2 temps:

  • Tout d’abord avec fichier build.prop non modifié, je suis passé sous 1.10.beta.2 sans soucis.
  • Ensuite j’ai modifié le fichier system/build.prop et lancé la migration vers 1.10 => au redémarrage j’ai eu un message “Echec de mise à jour”. Mais contrairement aux fois précédentes je n’ai pas noté de soucis de fonctionnement mais le système est resté en 1.10 beta.

Je remercie ici @PraksuQ pour son commentaire (Feedback for v1.10 - #2 by PraksuQ) car j’ai essayé sa commande adb enable-verity qui a permis de régler ce problème.

J’ai toutefois été obligé de modifier à nouveau le fichier build.prop pour faire fonctionner mon appli de banque.

A quoi sert ce fichier build.prop et que fait la commande adb enable-verity à part supprimer mes modifications (sachant que je n’ai pas réglé mes soucis en remettant manuellement le fichier à son état d’origine) ?

English version
I had several problems when I went from 1.8.1 to 1.9 that forced me to switch back to ROM Stock.

I suspected the modification of the /system/build.prop file that I made to make my banking application work (Xiaomi, faut-il rebloquer le bootloader - #3 by saroumane38).

So for this migration I proceeded in 2 steps:

  • First with unmodified build.prop file, I switched to 1.10.beta.2 without worries.
  • Then I modified the system/build.prop file and launched the migration to 1.10 => when I restarted I got a “Failed to update” message. But contrary to the previous times I did not notice any problem but the system remained in 1.10 beta.

I thank here @PraksuQ for his comment (Feedback for v1.10 - #2 by PraksuQ) because I tried his adb enable-verity command which solved this problem.

However, I had to modify again the build.prop file to make my bank application work.

What is the purpose of this build.prop file and what does the adb enable-verity command do besides deleting my modifications (knowing that I did not solve my problems by manually restoring the file to its original state)?

1 Like
  • OnePlus
  • 9 Pro
  • LE2127 (Not supported)
  • /e/OS 1.9-s
  • Not rooted

Updated via OTA. I think all it’s working fine, thank you!

1 Like