Are you running /e/OS R or /e/OS S ?
I donāt know really which one could it be.
Now under the settings I could copy the number of the build :
e_beyond2lte-user 11 RQ3A.211001.001 eng.root.20230205.200220 dev-keys
Donāt know for itās good
And the os Version a little bit hidden
1.8.1-r-20230205257804-dev-beyond2lte
Thus, thatās did R one
What good news! (/s)
It seems like I should not use Android at all.
The solution should be using adb
as root, but, even enabled, I donāt get how to use it.
I also saw and backup menu in the settings, but I donāt understand it at all.
So we see from the link from @MRTN that no 1.9-r is published.
This fits with Important information : Plans to drop support for multiple OS versions on the same device
Backup is problematic for many of us !
Perhaps my prejudiced view but it is as if Google would prefer users only to be able to backup within the āPure Googleā system.
The headline of the linked article reads Android 12 Developer Preview 1 Changelog: Google Finally Restricts the Power of āadb backupā
adb backup is the item which is getting increasingly error prone, imho.
Hmm Iām not sure to understand why there so many variants of the os.
is there anywhere some explanation and overview of it?
Some documentation?
It is not possible to merge all in one?
or split in 2 parts :
1 core which is specific to the hardware
1 other on higher level which is the same for all
Both independent to manage, support an updateā¦
I saw on the device matrix that for the samsung galaxy s10+ the version os is S
Iām still with R on my device, maybe is that here a block.
How may I switch or upgrade into S?
Could someone give me an hint? or a link?
Some background, but not a full explanation !
/e/OS is a fork of LineageOS. By default LineageOS publishes the latest builds only. Even if an older build is possible, only the latest is published.
/e/OS has tended to try to stabilise things for users (particularly who might be daunted by a necessary backup when upgrading Android version) and has continued to publish āolder Android versionsā.
The link from #e-smartphone-operating-system:development-updates warns us of the change of policy in store ā users will do well to look for the relevant Upgrade page, in the case of Galaxy S10+, https://doc.e.foundation/devices/beyond2lte/upgrade.
I answer to me seems to be only possible manuallyā¦
https://doc.e.foundation/devices/beyond2lte
https://doc.e.foundation/devices/beyond2lte/upgrade
And wanted to ask for further update on R or automatic upgrade is answered below of last linkā¦
Known issue
try to find time and nerves to applicate it manuallyā¦
thank you very for your help and effort.
short question about the upgrade and the recovery part to download.
Should we download the recovery of the current installed variant (in my case R)
or the one for the future variant to upgrade (would be for me S then)
In resume for me who have the 1.8 R.
Should I download the recovery 1.8 R first, and apply the 1.8S?
or the recovery 1.8S and switch to build 1.8S?
or directly download the recovery 1.9S and build 1.9S?
Seems that i could directly install the build 1.9Sā¦ But with which recovery? 1.9S?
Hmmm ā¦ but there is this ā¦
Caution: Before following these instructions please ensure that your smartphone is on the latest Android firmware available for your device. For example if available , before flashing /e/OS āSā install Stock Android 12. [Snip, edit]
ā¦ complicated by ā¦
Warning: Please note this upgrade build could not be tested as there were no device specific testers available. Some devices may need a revert to stock ROM prior to upgrade. To flash the stock ROM you would need to use a tool provided by your vendor.[Edit - split]
I have split this quote ā¦ it carries on
You may also need to download a recovery image built specifically for your device.
This is a generic warning, but in your case https://doc.e.foundation/devices/beyond2lte/install would simply have you use https://images.ecloud.global/dev/beyond2lte/ ā and, yes, you would want the recovery to match your Android 12 = S build.
Sometimes the LineageOS Upgrage page offers another insight. https://wiki.lineageos.org/devices/beyond2lte/fw_update
You may want more specific advice about Samsung Stock ROM, in which case probably best to search for a more Samsung specific thread or start your own new topic / thread, I suggest.
Android Backup and Restore Tools (ABRT) make use of it, for instance ā¦
This should be Seedvault, I didnāt look much into it, there should be info available via the search, or here perhaps for a start ā¦ [HOWTO] use Seedvault early to understand Android backup - #38 by fab
you means maybe the recovery 1.9 ( recovery-e-1.9-s-20230311268558-dev-beyond2lte.img ) which passed to the build one 1.9s
No need to need to apply the 1.8.1 s with its recovery at first, the 1.9 s afterwardsā¦
Thank you very much for your effort and your time to explain it.
Iām sorry iām little bit scared to make a wrong manipulation, and need confirmationā¦
I donāt want to spent too much time and money to catch up what I made wrongā¦
Thanks a lot for this!
Some I hate a lot is to be the only one to have a problem, and it happens to me too much.
Yes, āas ifāā¦
Yes, thatās SeedVault, I found the project on Github and read the FAQ, I got all the informations that I need.
I activated the backup, I donāt really understand how to get the data in the backup and if I will be able to restore it, but Iāll see (very good way to manage backups, lol).
I searched a lot and I found a way to do the backup using root adb
. I could get a full backup of the data using this command on the computer on which the phone is pluged:
adb root > /dev/null && rsync -a --delete --rsh="adb" shell:/data/data/ /mnt/home/almtesh/Temporaire/Pledge/e/data/
Yes, I know I should do adb unroot
when done, but I donāt want scrcpy
to be terminated at each backup.
On both
Sony Xperia Z5 Compact (āSzuzuranā) R 1.9
and
Sony Xperia Z2 Tablet (āCastorā) Q 1.9
The camera app is broken.
It is a complex subject and you have a valuable, modern device. I think it simply takes a bit of time for oneās mind to absorb the importance and sequence of the necessary steps. Sorry, but I do not think I am in a position to improve on my previous answers.
I found another issue, with network location provider.
The one from Mozilla often gives me wrong location.
The solution would be to disable it, but if I do so, no other app can list nearby Wi-fi access points (of what I understood).
I have the same problem if I tell Mozilla NLP to do not use Wi-fi.
Can happen ā¦ I add Local NLP Backend ā¦ other backends are available !
I just reinstalled it and I have data about the problem.
When I ask it to show nearby emitters, I only get the LTE cell after a long scan, but when I enable Mozilla Location Service or Apple Wi-Fi, the nearby emitters show more quickly and I get the Wi-Fi emiters in the results.
I donāt really understand how itās possibleā¦
I set all the apps to have permanent access to exact location.