My french farming team using Blackviews rugged phones (BV 9000 Pro / 9700 Pro / 9900) and i’m using Open Source software since 15 Years and i’d always wish to “ungoogleize” my phones.
Do you know if it have some project for Blackviews phones?
Thx again, sorry for my bad english, i hope i’m in the well topic.
Currently running the build 0.19-r-20211101143778 on ASUS Zenfone Max Pro M1 (X00TD) but it’s been a while since the first beta build. Are updates coming or waiting for feedback from more users?
From my experience, the build is smoothly running without any major issues except the weather widget on Bliss Launcher is not working and Miracast (Wireless Display) is not working. The LineageOS builds are getting updates as usual though.
I am pleased to inform that we have been able to complete the release as per this plan. The statistics around the new devices we added and the ones we upgraded is as under
Device Type
Count
New
81
Existing
63
Total
144
The only device we had to leave out was OnePlus one ‘bacon’ as we have been unable to build for it. Unless we get a dedicated ROM Maintainer for the device, we may have to drop it from our release list.
Just to reiterate, we will continue to support the maximum number of devices possible, as not all devices are available or affordable to users in all regions.
I would like to thank the users who shared their feedback for the devices builds and also to the team of /e/ developers who helped with getting these builds out week after week.
Hope to come out with a new list of devices to upgrade or add to our list for 2022.
Hello
Is there any hope to see /e/OS switch to Android ‘R’ on the Samsung A5 (2016) a5xelte?
Note that LineageOS also does not offer a version 0.18 for this terminal.
But still a huge thank you to the developers and maintainers for the work done .
It’s an odd sample. It’s very old, very new and the middle is missing. How come the Redmi Note 8 (ginko), for example, is missing. And yet there is LineageOS for it and the list of models goes before and after it.
This may or may not have something to do with it, but a while ago around here somewhere i posted about (magisk’s) John wu’s “android booting shenanigans” post; essentially android 9 changed the way booting was handled, then android 10 did again, so I imagine a lo of android 9 native phones suffered. Just a s guess
i successfully installed /e/OS on my wife’s Samsung S7 phone and my Samsung S5e tablet.
Now the only device i am not de-googled is my HTC U Ultra Smartphone.
Is there a plan to support HTC U Ultra in the future? It’s still a great device.
And i would prefer /e/ OS over e.g. a custom Lineage ROM.
/e/ OS is a complete system, including all apps i need, it would be really great to have it on my HTC, too…
My understanding is that officially, HTC does not allow unlocking of the bootloader. As you are aware, without that, flashing a custom ROM is not possible.
All that little article did was show how to toggle a switch to allow unlocking. No actual unlocking, no fastboot instructions, no nothing. A fake guide.
If it were only that easy.
Would it be possible to look at dropping out the Oneplus One 16GB version only? as far as I can tell from the forum/wiki the problems seem to be around partition sizes. the moslty used (AFAIK) Bacon has 64GB storage.
Hi @bonusbartus welcome to the /e/ forum. As far as I can see, the filesystem size error (which has been part of the blocker for /e/) is probably not connected directly; where both devices share the devicecode ‘bacon’, this has to be accommodated within the build. If you have the device and you could test or examine this experiment, Experimental Custom build 'extra_minimal_apps' for Oneplus One - bacon, I would love to look into this deeper.
(I do not think bacon will be on the release plan for /e/ R soon !)