Expect testing to continue for 2 weeks. If there are no issues we should be able to release the build for all users by mid or 3rd week else there will be a delay
Issues fixed as part of v0.18 which as you can see is 46
Issues identified in this testing will be reopened or added to the v0.18 where possible. Else they get moved to the next cycle of testing
/e/ R
To be released for testing on 9 Aug. We have got a small group of volunteers who will do the testing.
Check out the list of devices we plan to upgrade to R or introduce this year
List can be modified in case builds fail or there are other issues during the build process
There are some devices which are missing from this list…this is as they have maintainers. Will get the details from the maintainers when the devices can move to R and update the list
The feedback on the /e/ R testing has been positive so far
Development Updates
OS OTA Upgrade : development in progress. No ETA’s for now
VoWifi /VoLTE : development in progress. No ETA’s for now
Team has been busy working on the v0.18 fixes for GS290 and FP3 which are all merged in the v0.18 build being tested
Will share more updates once I receive them from the team
The s9 is not supported on Android 11 as yet. No support on LOS as well.We will have to port the device to /e/ R . That will need dedicated resources and a timeline. We are also looking towards other and newer devices to support.
[quote="[HOW-TO] Flash /e/-OS on Fairphone 3 using Debian based GNU/Linux, post:1, topic:15498"]
Warning: This process will completely wipe all data in the internal storage of your smartphon…
[/quote]
Installing is no problem (I used the easy installer without any issue). My problem will be the wipe of all data - which means, complete new installation and setup of 108 APPs several calenders and email accounts. The biggest headache will be the setup of my banking APPs, they’ll guide me a hard way to authenticate…
Not so easy to reinstall all your user apps and re-input all your settings and data. Would be much easier if the integration of SeedVault (which has been going on for a long time, but seems to have stalled at the moment) were completed before doing the migration from Q to R which breaks the only existing method of backing up user apps and data (i.e. TWRP backups).
If you read the instructions for upgrade (17 → 18) of lineage OS, they recommend an adb sideload. As far, as I understood, without a wipe of data. Maybe…
Please don’t get mixed up between LineageOS versions and /e/ versions:
Lineage OS
Lineage OS 17 is Android 10 / Q. LOS 18 is Android 11 / R.
Everything I have read,and my experiments upgrading from LOS 17 to 18 on one of my devices indicates that you must do a clean install and wipe your date beforehand. If you don’t you will probably find yourself in a ‘bootloop’ where the phone fails to start.
Also TWRP backups of LOS 17 data will not work when restored on LOS 18: doing so will cause a bootloop and an unbootable phone.
Lineage OS includes SeedVault which does allow LOS 17 backups to be restored on LOS 18 (though it does not back up all user data or app settings). I have not yet got round to trying this solution out, so it may or may not work
/e/
/e/ 0.17 exists in Android 7 / Nougat, Android 8 / Oreo, Android 9 / Pie and Android 10 / Q versions: you can tell from the name of the ROM zip file
/e/ 0.18 currently exists in Android 9 / Pie and Android 10 / Q versions, and the Android 11 / R versions are currently being tested.
Updating from /e/ 0.17 to /e/ 0.18 can be done without wiping data so long as they are both the same Android version.
No /e/ versions include SeedVault, so when /e/ release the Android 11 / R versions, then you will need to wipe your data before flashing, and reinstall all your apps and re-input all your settings from scratch.
As an alternative method, as a /e/ R beta-tester I made the promise to fireproof AppManager, and I will
I already took a backup of all user apps from my testing device, and also of all system apps settings to check if we could restore some (in example, /e/ Account Manager).
But it will take some time : I have to wait for the R build, find some time to flash it and conduct the requested tests, and then I could try to restore apps with AppManager.
Looking at the content of the backup, I’m pretty confident it’ll go the right path
Thanks for reminding me I have a couple of R ROMs to test too, and at least one of the devices already has App Manager installed, after your earlier post. I’ll try using it to backup (at least some of) my Q apps and data before I flash the R ROM. I really would make upgrading much less tedious if it does (or could be made to) work. Please refresh my memory: do I install App MAnager from F-Droid or Aurora Store? Thanks
create a profile, in t’s configuration enable backup/restore and scroll down to enable “Save APK” (don’t forget to save from 3-dot button)
back to packages list, filter only user apps, then long-press one, use “select all” button at bottom, and add them all to your profile
back to profile, use 3-dot button to apply : this should start backup. You’ll be probably asked for “profile state”, as I could understand from doc “on” is for backup and “off” for restore
In backup settings I choose APK, External and OBB; I don’t know if all these data are relevant.
By the way, you may find some interesting feature of this app by taping some app them in the list
Now, having re-read some of the docs, I’ve remembered why I didn’t follow up much further on App Manager after your first post. Looks like it can backup and restore app .apks without root, but to backup app data and settings I would need to root the phones. I’m not a fan of rooting phones. I’ll sleep on this one and work out what to focus on next. I may just take the hit of reinstalling this time
Can it be used to back up and restore app .apks from say device manufacturer A to device manufacturer B? Sorry for my noob question. I am in the sameboat and don’t root so I decided to stop testing it when I couldn’t block trackers via ADB.