Feedback for v1.6

/e/OS Smartphone Operating System Build Feedback
132

Did I get it right that I have do the upgrade on FP3 dev from q to r manually with data loss?

133

Hi, I get the update on my Fairphone 3 with the auto updater.
Unless this error message at the very beginning when each time the Os starts, no problems detected.

com.qualcomm.qti.workloadclassifier stoped working.

Screenshot_20221219-172221_BlissLauncher
Screenshot_20221219-172221_BlissLauncher1080×2160 95 KB

Screenshot_20221219-173252_Paramètres
Screenshot_20221219-173252_Paramètres1080×2160 136 KB

134

Hello,

so far I am very happy with my eOS on my Fairphone 4 but with the Android 12 Update I have got some issues. If I call someone then I dont have these “calling sound” anymore which makes you (the caller) know, that the phone of the other person (the called) is ringing (I dont know how to describe it better). Before the update that was fine.

Second problem, if I open for example a “open.spotify” link in any app, it will open spotify, but it never starts playing this song. Similar problem with open a wikipedia or newpipe/youtube link. I have installed the wikipedia app and the newpipe app on my phone, but now links will be opened in my browser and not in the special app they are for.

I hope you can help me! Best regards, Jelle

135

After I upgraded my Fairphone 3 (TWRP recovery, Magisk) from 1.5-q-dev to 1.6-r-dev via adb sideload the crash logger app “Scoop” (F-Droid) shows this crash every time when the phone has booted:

FATAL EXCEPTION: main
Process: com.qualcomm.qti.qms.service.trustzoneaccess, PID: 8620
java.lang.UnsatisfiedLinkError: dlopen failed: library "libnative-api.so" not found
    at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
    at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
    at java.lang.System.loadLibrary(System.java:1664)
    at com.qualcomm.qti.qms.service.trustzoneaccess.TZAccessService.<clinit>(TZAccessService.java:15)
    at java.lang.Class.newInstance(Native Method)
    at android.app.AppComponentFactory.instantiateService(AppComponentFactory.java:129)
    at android.app.ActivityThread.handleCreateService(ActivityThread.java:4177)
    at android.app.ActivityThread.access$1500(ActivityThread.java:237)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loop(Looper.java:223)
    at android.app.ActivityThread.main(ActivityThread.java:7664)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

v1.5-q-dev worked without problems.

Also: Magisk Zygisk remains deactivated although the respective setting is activated.

(I sent this issue to the helpdesk also.)

136
  • Vendor Name: Google
  • Device name: Pixel 4a
  • Device CodeName: sunfish
  • Version of /e/OS or Stock which existed previously: e1.5r-stable
  • Is the device Rooted / Not rooted: Not rooted

No issues detected over the weekend after installing on friday

137
  • Vendor Name: Fairphone
  • Device name: Murena Fairphone 4
  • Device CodeName: FP4
  • Version of /e/OS: 1.6
  • Device: Not rooted

I am using a Murena Fairphone 4 in the USA with the carrier Mint Mobile (T-Mobile MVNO), and /e/OS 1.6 has made it possible to enable 4G calling!

I made a separate post here.

Thanks again to all of the developers that made this possible!

2 Likes
138

Hi & thanks for your great work!

Unfortunately, on my FP3 Q (1.5-q-20221031230909-dev-FP3) the OTA update to 1.6 is still not available, not to mention an OTA upgrade from Q to R.

Any idea what might be the problem?

Vendor name: Fairphone
Device name: Fairphone 3
Device codename: fairphone-fp3
Version: 1.5-q-20221031230909-dev-FP3
Device is rooted
1 Like
139

_______________ This : :arrow_down:

140

For me, that means never dev again. Anybody who flirts with the dev build of S should also keep this obstacle in mind when choosing: As an early adopter, installing /e/ when Q was still dev only, you never where updated to the stable channel, but remained dev. I never realized that until now. That seems to unnecessarily complicate updating and upgrading, because one is now stuck on dev channel without OTA updates or the possibility of OTA upgrades.

I really love /e/ and the effort that is put in it by its team and community, but I hate the prospect of completely setting up my phone once again. Meeh, but well, it’s worth the effort^.^

2 Likes
141

What is the problem with using dev builds?

From what I know there is no real problem being on dev builds rather than stable. They are built from the same code. dev builds can even be better than stable because, as user-debug builds they allow rooted debugging, which allows more flexibility in backing up your device.

A large number of users have always used dev builds, with no obvious problems

1 Like
143

There are no OTA upgrades for dev builds, that’s the pain in the ass. With a Q stable build I would have been automatically upgraded to R (OTA 1.4Q to 1.5R), but with my Q dev build I am now in an dead end, Q updates are no longer provided and I have to manually upgrade to R, which means total data loss and starting with my phone from the scratch again. That won’t happen to S dev very soon (but eventually will), but could come up with R dev in a year or so.

What I don’t really understand is, why the Q dev build wasn’t OTA updated to a Q stable build at any time whatsoever. That would save users from running in this annoying dead end. What’s the reason for that? Is it technically not possible?

144

Here’s a mention I found in the search …

Perhaps @Manoj could explain this a bit more?

145

That would be nice indeed.

I would also propose that the documentation is complemented, pointing out that you can’t switch (or get switched by updates) from a certain dev build to its stable counterpart and that OTA upgrades are not available for dev builds (unless there are plans to offer them in the future).

That would perhaps save some people from this dead end. Well, at least those who mindfully read the documentation^o^ Over my journey with /e/, I had my learning by doing (and undoing) moments, too, I have to admit, and here is another one…

146

In several posts in the issue tracker developers say that for dev builds there will be no OTA upgrade. I don’t understand that either.
But there is a way to upgrade the dev build without data loss: You can flash the R-dev package with adb sideload and keep data.
I did that but I am having some trouble with several apps, but mostly with root access. So if your phone is not rooted the upgrade may work smoother.

1 Like
147

It does not mean total data loss. I have updated from Android 7 / Nougat builds right up to Android 13 / S and have never lost data.

It’s quite straightforward:

  • Back up your Q data
  • Dirty flash the upgrade
  • If it doesn’t boot, format your data partition
  • Clean flash the upgrade
  • Boot and go through first time setup
  • Restore your Q data

You can back up EITHER

More information on both methods here

2 Likes
148

Do you mean with “dirty flash” adb sideload? An /e/ developer recommended that procedure. I read that flashing the upgrade e.g. from TWRP is not recommended, especially not on A/B devices.

149

Yes, that would be nice to know! And while explicating, could you also give your opinion on a “dirty flash” from a dev build to a stable build? Do you see any complications? I liked learning to do nerdy stuff when starting with /e/OS, but now I am old and just want to stay stable, easy and comfortable, enjoying OTA upgrades in the future^o^

That looks pretty interesting, something I have longed for quite a time. I will give it a try tomorrow.

150

I don’t think that will work. See this quote from above:

151

No. TWRP and adb sideload are both methods of flashing a ROM. None of my devices are A/B, so TWRP just works for me. From what I’ve read, I believe adb sideload is the best way to flash A/B device but I don’t know for sure.

“Dirty flash” means flashing the new ROM over your existing data, using either method. This is what the 'Updater" app does with updates (and upgrades), so that your installed apps and user data are not affected.

“Clean flashing” involves getting rid of your existing installed apps and user data - either by wiping of formatting - before flashing the ROM. After a clean flash you do have to set your phone up again from scratch, either by hand, or by restoring a backup.

Sorry but I can’t - none of my devices have stable builds. And I wouldn’t install them if they were available because, from what I have read, there is no rooted debugging, so TWRP is the only functional way of making a restorable backup.

I use TWRP backup for backing up my current phone, but I need/use Android Backup and Restore Tools project for migrating between devices, because restoring a TWRP Backup

  1. is tricky - but not impossible - to do when the new device is the same model
  2. is not possible (as far as I know) when the new device is a different model

ABRT handles both those situtaions admirably. The only things it doesn’t restore is account data for apps like Mail (which allows you to export settings from your old phone and import them to the new one) and Account Manager. TWRP does that better.

1 Like
152

For upgrading via adb sideload data is kept, so restoring not necessary.
I don’t think that a data restore with TWRP will work after an upgrade. TWRP restores the whole data partition, that includes system data that will have changed through the upgrade.

For app and app data backup and restore in case it is necessary I use the 3C App Manager which is also included in the 3C-Toolbox (both from Play Store). For app data backup the phone must be rooted, of course.