That looks like a good choice of apps to remove (because I don’t use any of them )
It would be great if, at some point, there were a way to make unofficial ‘lite’ builds for devices that are not due to receive official ones (e.g. condor). Even better if it were possible in Docker (e.g. by a flag or parameter in the docker build... command)
Updating through the Updater App is also working for dumpling now (from Version of 10.08.2020 to 14.08.2020).
So i guess everything important works flawless, maybe it could be offered as a “production-ready” build.
Well one thing doesnt work, which is wifi calling.
But that also didnt work with lineage so i guess its a device specific issue, and no dealbreaker at all.
First of all there are limitations on how long a post can be on Discourse …which is why I broke it into parts.
Added a small explanation as to what each article is about to the title…hope that makes it easier to understand the contents.
If you think the plan is confusing think how confusing managing all the existing , upgrade and new builds can get
Still plan on getting the Q builds our hopefully this week.
haha i’m sure. Any thoughts on the YTX703L not showing OTA updates? I did a clean install this time, so the dirty flash from last time cannot be the issue.
Hi Manoj,
just discovered recently about /e/ and switched from LOS with Microg to the Nougat release. Today I installed Pie with the unofficial e-0.11.n-2020082569744-test.crackling rom on my Wileyfox Swift with TWRP 3.2.1.0. Just flashed it over the previously installed official e-0.11.n rom.
It runs like a charm. No issues so far. Great work! Thank you so much for providing such an impressive system that makes the phone feel much cosier in my pocket.
Is this the right place to give feedback about the builds performance too?
I am running the crackling Pie test build on a Wileyfox Swift. I observe that battery consumption is notably higher than it has been with Nougat before. Additionally the screen freezes somtimes for a moment, when I wake up the phone. I had made these observations previously running lineage 16.0 before on the phone, so I assume it is a lineage problem and not related to /e/.
Thanks for sharing the feedback about the crackling build. May be an issue with the source code but we will still need to look into it. You could raise an issue in Gitlab and we can check against subsequent OTA test builds.
I have reinstall /e/ for get OTA update : work fine
Now, i search to “clean” my rom, because i like use simple(contact/sms/etc) apps and nextcloud* apps with regular update.
if add fairemail, termux, openvpn, osm => all via f-droid + firefox, itsme (Belgian app for federal website) and magisk
i don’t use any others apps on my phone. (i like apps integrated : openkeychain and davx5 )
I have duplicate apps with e.foundation/lineage/android.
For me, the best is proposal to install it on start up phone for first time :
Do you need these apps (check box for select one on more) (example only) :
e.drive
e.calendar
e.sms
lineage.x
…
with little description per app and if no needed, we can start only with e.store (why not f-droid?) browser and … (another by default if needed ?)
i miss some time to check all app installed on my phone, i have already extract this list and remove all apps installed by me via pm list packages --user 0
(need root, via Magisk for me)
need to check required by system and “optional” apps
I just installed the test built on the 5T and am trying to figure out the spreadsheet but have a little hiccup around the filename:
device_roadmap_yyyymmdd_devicecode
What is the devicename/roadmap/device code?
For the 5T would this be:
Oneplus5T_roadmap_202020919_dumpling
?
Or is roadmap supposed to be something different? pie?
The OnePlus 5 T on pie is officially supported now. You can find the ROM here
Roadmap is just a term like a plan. The device code for the OnePlus 5T is dumpling.
I guess that means there’s no need to report that test then
Is there an ideal bug reporting method in general though?
And for future reference/info: what should the file name theoretically have been be then?
Did I have it right, just leave roadmap as the word roadmap? And use the plaintext device name?