Week 46, 2022: Development and Testing Updates

[AnotherElk]

@HekatheGreat

So no stock android before sideloading eos S? Am I brave enough to try this with my Oneplus 8

Please keep in mind that the e foundation and Fairphone have an official partnership going, so we Fairphone users expect /e/OS to have the relevant firmware bits included for our devices (at least from the Fairphone 3 on).
Circumstances on other devices might differ.

[Usem]

Hi @Manoj ,
I tested the v1.5-rc R in test channel on OP8T - codename Kebab - and then installed the stable version, all things work perfectly. But recently I realized that the Bluetooth audio does not work when using none /e/ apps. ie : when listening my podcasts on antennapod or my music on VLC the audio stops in 1-2 min. This is not the case when i use the music /e/ default app. Has this ticket already been raised?

[Libre]

Hi,

I flashed /e/-S on my FP3 without flashing stock first, everything works as of now. I’ll create a short Topic about this

[HekatheGreat]

I am currently on 1.5 r dev and I tried to go to 1.5 r stable. I sideloaded the stable version with erecovery and everything went fine. Still, my phone, Oneplus 8, shows me that I am on dev:

e_instantnoodle-user 11 RQ3A.211001.001 eng.root.20221102.151621 dev-keys

Any comments?

[Libre]

Please post a screenshot from your “Device Info”.

It should show the currently installed /e/OS version. It MIGHT be that the dev-keys are just for signing something which is not tied to the “flavor” of the /e/OS build.

[Libre]

I "upgraded" (flashed WITH dataloss) my FP3 from /e/-0.23-dev-p (Android 9) to /e/-1.5.1-dev-s (Android 12) and here is how

Since the installation documentation for the FP3 is a little outdated and OTA upgrades won’t be available for Android 9 to 10/11/12, I decided to report how I successfully flashed 1.5.1-dev-s on my device WITHOUT using the easy installer. YOU WILL LOSE ALL DATA ON THE DEVICE! Here is what I did: Backup all the things. Most of the Apps offered backup/restore functionality, for a few it was just a pain. Unlock Bootloader Download and flash the latest available stable build which was not relea…

Here we go

[HekatheGreat]

Ok, I found this

And yes there it says it is eos version is stable. I mix it with the build number. Thank you for help me to find this information!

[Lobster]

Hi all !

Newbi question : installing eOS S (Android 12) on my FP3 from 1.5 stable R (Android 11) will keep me on the stable branch ? Will it reset all my datas ? Is it something manageable from a Windows phone without any experience ?

Thanks guys for your amswer !

[Manoj]

You can check on the testing channel if this issue is known, if not raising an issue is the correct way to handle it.

[MRTN]

@Lobster

Newbi question : installing eOS S (Android 12) on my FP3 from 1.5 stable R (Android 11) will keep me on the stable branch ?

Stable channel on FP3 is only for Android 11 (for now…)

[ne20002]

Ho @Manoj

I wonder about two things anf haven’t found clear recommendations or documentation:

• /e/OS gives the option ‘Update Recovery’ on updating OS. Is this recommended? Not recommended? What could go wrong?

• Is there a way to lock the bootloader after installing /e/OS? If so, is it recommended, not recommended? What could go wrong?

[Lobster]

@MRTN Thanks for your quick answer !

[Nicolas_Sas]

@Nicolas_Sas

@Manoj

Some of the devices we sell / sold on the Murena shop will get the S OS upgrade via OTA for example the s8

Beside the FP4 is there a ETA for other device like S8/9, Murena One or FP3+ OTA upgrade ?

@Manoj do you have any information about this ?

Thank you very much

[sam-a]

Hi @urs_lesse, i’ve two questions.

1. Did you update the recovery too and would it be manual or automatic?
2. Can / must the bootloader afterwards be locked?
   Did not noticed that anyware.

Thanx for u hints and experience.

[urs_lesse]

1. I did not update the /e/ recovery and started ADB sideload through it. Assumption: Through the successful upgrade of /e/, the recovery also gets updated?
2. I think locking the bootloader is only (strongly) recommended for general security (in case someone else gets access to the device), but not for functionality of /e/OS.

[Libre]

@urs_lesse

Assumption: Through the successful upgrade of /e/, the recovery also gets updated?

Depends on the phone. If the device supports seamless updates (a/b slots) the recovery is contained within the boot.img.

[Confused]

Manoj, any roadmap for a full phone backup software to mac / pc?

Many of us really rely on our phones. Its huge work to set the phone up as desired, then to remember and install all the apps we use together with their data. Its a huge project if the phone goes wrong/lost/stolen/smashed.

Regularly backing up to a computer, would mean that if the worst should happen, I and others could rush out, get a secondhand phone and quickly restore and be back in action quickly and easily.

The 2 things I miss from apple, the great backup and restore software, (either theirs or imazing) and AirDrop. Airdrop is nice, a simple full backup and restore is essential.

[Manoj]

@Confused

roadmap for a full phone backup software to mac / pc

No not yet. Will share details in case there is any progress on this. This is a much requested feature.

[aibd]

Here we have a link from the TWRP FAQ – regarding backup, What is EXCLUDED from a TWRP backup? updated today !

• What is a data/media device?

Full disclosure: I have had no interest in anything Apple since I first became aware of it.

As I understand, /e/OS is unlike Apple in that there is not a one stop shop for backup. /e/OS supports, quoting Get Support - e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data, some 269 Smartphone models, not one hardware type.

So I regard a TWRP backup as only a part of my backup strategy.

Lineage has been working on Seedvault for some time; is it ready for general use ? idk.

[urs_lesse]

@urs_lesse

I lost my Calendar entries (they are still in my Murena cloud though)

Update:
I just got my Calendar entries back following Manoj’s suggestions on Troubleshooting (although originally for Android N and O, they worked on my Android S FP3+ now, too).