[LENNY5][UNOFFICIAL][GSI]LineageOS 16 Treble with FLOSS, MicroG, Root, FakeStore

[LENNY5][UNOFFICIAL][GSI]LineageOS 16 Treble with FLOSS, MicroG, Root, FakeStore - Android General

I DONT TAKE ANY WARRANTY WHATSOEVER IN ANY DAMAGE THAT MAY RESULT IN FOLLOWING THIS GUIDE OR USING THE SOFTWARE, ROM IN QUESTION, IN ANY WAY, MAY IT BE AS INTENDED OR NOT. IF YOU HAVE ANY FEELING YOU COULD END UP SUING ME FOR RISKS *YOU ALONE* ACCEPTED TO TAKE, YOU SHOULD IMMEDIATELY STEP BACK AND LEAVE THIS POST, ALL THE OTHERS: BE CAREFUL. YOU WILL LOSE ALL OF THE DATA ON YOUR PHONE'S USERDATA, CACHE AND SYSTEM PARTITION AND THE PHONE WILL BE FACTORY RESET!
STOCK FIRMWARE INSTALLER: https://support.wikomobile.com/maj/Lenny5_OPE_V34.zip <-- if you brick your device.
Hey folks
This is just a brief explanation on how i built this ROM, a complete guide to building the rom may be published at a later point in time. For the Downloads, go to the Links section. The flashing guide will be focused on Lenny 5, but the image may work on other treble-enabled devices, too, so feel free to try and report if your device works with this build.
Build variant: arm-aonly-floss-su-userdebug
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Build description:
I have an old Wiko Lenny 5 around here and wanted to use it as a Kodi Remote etc. at home, but didn't want to use their stock ROM. Also i wanted some freedom in using my device, specifically a rooted device and microg implementation. After trying to build TWRP with no success and the Wiko Build information being massively outdated i then focused on Generic System Images, as Lenny 5 is Treble-enabled. Big thanks to @phhusson for the whole lot of effort he put into building AOSP GSI's (and also clues towards building LineageOS GSI's). After having AOSP9 installed on it for some time, i got bored and tried to compile LineageOS using the patch-and-build system provided on phhusson's github. That worked just great on AOSP9, but failed to build a bootable LOS16 in the first place. So after some recherche, i stumbled across @AndyYan's thread, containing some LineageOS GSI's prebuilt and ready to use. These worked great on my phone, but as stated above, i wanted to customize my LineageOS even further, so i manually patched my build-tree with AndyYan's Lineage-Treble-Patches by doing what this build script does, tested and it booted (i guess it's mainly related to the SELinux Policies not being correctly built for LOS with only phh's treble-patches). So far so good.
Additionally, i implemented the MicroG services by cloning these prebuilts on github to the respective folder in the build tree and before the build executed
Code:
export WITH_SU=true
to include LineageOS's root system in the build. I adapted the treble_arm_afS.mk device config to not use phh's su and the device/lineage/floss.mk file to include
FDroid
FDroidPrivilegedExtension (which is being built from treble sources)
MicroG services (use Play Store Apps)
FakeStore (use Play Store Apps)
MozillaNlpBackend (MicroG Network Location backend)
NominatimNlpBackend (MicroG Network Location backend)
OpenWeatherMapWeatherProvider (for LineageOS Weather Provider)
You are then free to use no Playstore at all or i.e. Yalp Store to download Play Store Apps.
After downloading the Image you may need to Unpack it via 7-zip or another tool.
Flash the device:
To install this custom ROM on the Wiko Lenny 5, in your stock ROM go to Settings->Developer Options->OEM unlock->Enable. Also, in the Developer Options, make sure, ADB Debugging is active and, on prompt, accept debugging connections from your computer.
On your computer, enter Command Prompt and issue the following commands:
Code:
adb reboot bootloader
*wait for device reboot*
fastboot oem unlock [COLOR="Red"]<-- this will factory reset the device!!![/COLOR]
*press vol up on the phone to allow unlocking the bootloader, and wait for the phone to return to fastboot mode*
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot flash system <path-to-the-downloaded-gsi>
*wait for each process to finish*
fastboot reboot
now, wait for the phone to reboot, it should, after some time, show you the usual LineageOS startup screen. Take your time to set up your phone. To make MicroG and FakeStore work properly, you will have to Go to Settings->Apps&Notifications->App-Permissions->Spoof package signature->Menu->Show System Apps and allow FakeStore to spoof Signature. Go to Settings->System->Advanced->MicroG Settings and add your Google account. Activate Device Registration. Then activate Google Cloud Messaging and Google SafetyNet, if you want to take advantage of those services. Inside the UnifiedNlp Settings choose MozillaNlp in the first, and NominatimNlp in the second setting.
Go back and choose "Self check", if required, if required, grant MicroG GmsCore the permission to spoof signature, this should make most of the boxes go "checked". If Phonesky shows errors about signature spoofing, this should normally be gone after a reboot of the phone (given you allowed FakeStore sig spoofing). Disable battery optimization and then reboot the phone.
Check back in MicroG Settings->Self check, if all the boxes have been checked. If not, most mandatory points are self-explanatory.
This Lineage ROM will not allow you to update to a newer version. I cannot guarantee continuous updates, but encourage you to try building LineageOS treble with the way explained above, yourselves. If enough interest is around, i will consider doing updated builds from time to time.
Update:
Today i compiled a recent source tree containing the 5th of October patches. I will try to keep up with updating the Image whenever security fixes are released. The download links below have been updated to the newest version. To update your phone without deleting the data on it (make sure you have adb debugging enabled), you can simply do
Code:
adb reboot bootloader
fastboot flash system <system-image.img>
fastboot reboot
and then give your phone some time to "update". it should boot normally without erasing your data.
Links:
ROM .7z [~430MB]
ROM .img (~1.1GB)
(version was compiled at 19th of October '19, containing the October 5th security fixes.)
Let me know if this works for you, too!
Cheers
ivelischt

*reserved for additions/build guide*

Nice work
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.

Hanthonious said:
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Click to expand...
Click to collapse
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better

ivelischt said:
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
Click to expand...
Click to collapse
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400

Hanthonious said:
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Click to expand...
Click to collapse
Hi Hanthonious
ivelischt said:
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Click to expand...
Click to collapse
as the microG variant requires some "special sauce", namely the ability to spoof signature as well as other small fixes in the source code, my source tree is a bit different from the "vanilla/gapps" source tree. thus, to build variants not containing microg, you can simply sync the lineage source tree and apply the additional phh treble sources&patches. *edit: next to phh's patches, you will also need AndyYan's patches; you can find information about it in the OP. given, i write a guide (which i still intend to, but this takes some time), the patching step will be explained more clearly* basically, it's one step less than compiling it with microg. at the moment i cannot afford enough disk space to create another work tree, which is why i "can't promise" other build variants, until this issue is gone. which may be tomorrow or in a year. maybe you can find a gapps-version of treble-lineage 16 here in the xda boards. otherwise you will have to wait, or try to build it yourself. also, you might be interested in @AndyYan's lineage version, which is vanilla (no gapps or microg).
i would guess that the system image will not grow excessive just by including opengapps, but i may be wrong. i think that you'd possibly would have to choose a "non-complete" opengapps-package, to make it fit.
to quickly summarize what microg does is, that it spoofs its signature to make your phone think that you have the real Google Services Framework, Google Cloud Messaging, etc. services installed. this makes apps, which depend on these services, work even though you don't really "have" them. additionally, microg establishes an "essential" communication between itself and the real google services to allow you to use google services despite having all their bloatware.
to round this up, you have fakestore which spoofs existence of Google Play Store for those apps and games, which specifically check for GPS's existence (Phonesky app).
i think this should quite generally point out, what microg is for (an api which connects you to google, whilst only handing out information, which is crucial to keep a specific connection alive)
you can then use i.e. Aurora Store to download and update your preferred playstore apps. i tell you this specifically, as i hope that, using it right, microg might be able to give you a "fully stocked" phone experience, whilst keeping most of your data secure and your phone unbloated by google's app-hoard.
if you follow the instructions in the OP on how to fully enable microG, this might be a very handy solution for you, too, so maybe, you want to give it a chance.
to point out my issues with twrp (as far as i can tell using my little experience): twrp is device specific. which means, you need a vendor tree and you need to include it whilst building, so twrp can compile against it. now, treble is a way of excluding your device specific vendor tree from the build altogether (your system image basically doesnt contain the vendor files in a "folder" (/vendor), but in a seperate partition. this partition is "simply" beeing symlinked to from your system partition. this way you will never need to build vendor-specific sources but android builds against standardised "api's" which are being "serviced" by treble-enabled phone's vendor-files (lying at the vendor-partition). this makes building aosp and/or lineage, etc. easier as you can build one variant per architecture, which fits all treble enabled phones of that architecture (arm/64/binder32/64,a/ab,...). this is, very basically said, what is called a HAL (hardware abstraction layer) on a desktop computer.
but at the same time it's much more difficult to find vendor sources for those phones, as there is no more need at all for manufacturers to make these sources publich (as far as i understand it). as a matter of fact, you may not need these vendor sources for modern aosp (8.1+), which really is a grace!! but twrp doesn't seem to work when compiled against treble trees.
i even managed to compile a kernel which is mentioned at the wikogeek site for the lenny 5. i tried to include that kernel when compiling the recovery image but even that did not work out. as i am no experienced programmer (especially not in the high languages), i will not be the person to ask when it comes to finding out what bugs and how to circumvent it.
there is a little light at the end of the tunnel, though. as far as i understand it, treble-phones come with mostly generic kernels, which *could* make it easier to find a way to build a kernel/boot/recovery image in a similar fashion we build the gsi (generic system image) with. additionally, if there is some effort on it, i imagine, that it would be possible to generally modify twrp in a way so it's able to build against treble source trees with missing vendor source. this would enable twrp to run on virtually any phone which is treble enabled and there would be few to no need to port it for each device, specifically. maybe there would then be versions as in the treble gsi's (arm/64,a/b,...) as well as build variants for alternative display sizes etc.
but i wouldn't even know where to start...
i hope i was able to answer your questions. if you decide to stick with the variant in the OP, you should consider downloading and installing the most recent updated build.
best regards

Problems I found in the rom and if there is a way to solve them
Yo,
I wanted to point out the problems I found in the rom and if there is a way to solve
These are the problems I encountered:
1: *THE MOST IMPORTANT*
I can't pass the safetynet test, I researched a lot and I still couldn't solve
When I try to pass the safetynet test on magisk it gives "safetynet API Error"
When I try to do the test with the "SafetyNet Helper Sample" app it gives "SafetyNet request: success
Response validation: fail
Error Msg:
ApException [17]: API: SafetyNet .API is not
available on this device. Connection failed with:
ConnectionResult {statusCode = SERVICE_INVALID,
resolution = null, message = null}
And the "SafetyNet Test" app gives me "fail (Google Play services not available)"
I am aware of the new problem with the safetynet:
(sometimes people are still able to pass the test probably because it is still in maintenance or something)
https :// www . androidpolice . com /2020/03/11/safetynet-improvements-kill-magisk-hide
https :// twitter . com /topjohnwu/status/1237656703929180160
https :// twitter . com /topjohnwu/status/1238514375150850048
https :// twitter . com /topjohnwu/status/1237830555523149824
But even so I should be able to run the test even if it give both negative should run instead of showing those errors
2: The contacts I had on the SIM card and Google account do not appear in the contacts.
So I went on WhatsApp to save the ones I wanted to save, but after a few days and a few restarts the contacts are still saved, but on WhatsApp it shows that they are not saved even appearing in the contacts, to appear again saved on WhatsApp, I have to save them all again
3: Cant login in Clash Royale with google play games account, can i flash the rom and gapps to work or the microg and google play services will create some conflict, is there a way to unninstall microg completly and reflash the rom without microg and flash gapps?
4: Error when login in pokemon go: unable to authenticate, I researched it and it seems to be because the safetynet is negative but I can't even run the test (only after I became aware of the new safetynet problem) even with this new problem I would like to try to run the test to see if it passed since some people still are successfully passing the test
5: in the microg settings in self-check an option is not checked in the box "UnifiedNlp do not have location to test geocoder" I already researched to see if it solved something but I couldn't
edit: I solved it using the "Apple WI-FI" backend instead of the "Déjà Vu Location Service"
BUT NOW ITS GIVE ME AN UNCHECKED BOX
"Network-based location enabled:
you either disabled network-based location
(in system settings) or the system is not
supported"
6: some times in the time widget just appear "loading widget..."
and these are all the problems that I encountered, pls help me
solving these problems, thx!:good:
sorry for some mistakes i translated from portuguese to english with google translator and my knowledge of english

CooperTUGA, thanks for writing. And I want to apologize for letting you wait for so long. In fact, at the moment i do not actively develop this ROM (due to data loss on my virtual machine).
Anyways, i will try to address your issues as good as i can, though i must admit, none of these issues happened on my device.
ad 1: The only thing that comes to my mind is, that something went wrong when registering your device with the Android-ID. (see OP activation instructions). The SafetyNet-API itself should be working, atleast I had no similar issues (after Registering the device it takes some time - around 5 minutes - for Android to reflect the registered state).
But if someone happened to have this issue and knows another solution, you are welcome to tell!
ad 2: Does it help when you try to import the Files from the SIM card? As for Google contacts, it is - from my POV - stringent, that, if the SafetyNet API doesn't work properly, you will be unable to access Google Services (as Google Contacts) which would explain the missing Google Contacts.
ad 3: GApps and microG are two different things. GApps install a version (open-source fork, contains proprietary binaries) of the Official Google Apps, that is, they provide full functionality towards google services, provided you registered your device correctly.
microG is a pure Open Source fork of that, providing but the Framework with which Google Apps can be run. It does not provide Google Apps (like PlayStore etc.) by itself but merely allows them to run, given the configuration is right. This microG-ROM is not built to work with GoogleApps like PlayStore, but instead relies on the microG Services to get Apps, providing same or similar services, running (like Aurora Store etc.). To address your question, it is possible, to change the source code which was used to build this ROM, so it builds with Gapps or completely free of any such services, in fact it would mean to exclude certain patches, but such projects (Treble-enabled) are covered by others and because of above stated reasons i will not be able to provide such in near future.
Short but clear: No, there is no way to "uninstall" microG as it is built together with the ROM and the source used was especially prepared to use microG. But if configured right, you should be able to use your Google-Account in combination with Google-Services-Apps or Games despite using microG.
ad 4: See above. If everything's configured right, you should be able to play Pokemon GO, although i don't use any of these Apps (Clash Royale, Pokemon GO, WhatsApp). I never encountered any Problems along using Google Apps with this ROM.
ad 5: Well, the error says it all. I have Mozilla Location Service installed, which works like a charm. Maybe try this one? You can get it from FDroid, search for "MozillaNlpBackend" and see if it helps to sort this out? This works for me, after all.
ad6: as this is very unspecific, i cannot really tell what's the problem, but i would guess it has to do with the SafetyNet API not doing what it should or even the Location Backend not reporting position in time...
Did you clean your cache and data partitions while installing this ROM? I really am not sure what could create the behaviour you describe. Maybe there was a change in the SafetyNet/Device Certification process since this ROM-Build, maybe theres someone in those boards who could answer this, but i unfortunately can't...
I'm sorry that i cant give you more positive news, but hopefully it helps you in orienting what some common problems could be caused by.
Let me know about your success in trying to get the ROM working.
Best regards and greetings to portugal!
ivelischt

additionally: if you are interested in porting the Lineage Source for GSI/Lenny 5, you might be interested in this Thread: https://forum.xda-developers.com/android/help/how-to-root-wiko-lenny-5-t3819469
specifically, i wrote a guide there on how to build Android/Lineage Source for Treble devices. Maybe this helps you in getting your own build environment, enabling you to build to your disguise.

Images are not available anymore. Anyone here?

Related

SRGX2 Rom for the Life One X2 Mini

SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)

Screenshots: comming soon

Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app

Troubleshooting

reserved

Does quick charge work?

Been running for a couple of days now without issue.

cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.

Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!

cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk

enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy

srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.

New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170

Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?

Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814

New rom rebuilt from the 01/04/2018 update.
v 1.1.0

There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.

Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825

Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.

[KERNEL][MIUI] PWn3R-K3RN3L GLOBAL SafetyNet Bypass Updated: 3/17/2020

I started working on this almost 8 months ago. Originally (and possibly at some point in the future) my goal was to provide a slightly modified kernel from the source code Xiaomi releases on Github for MIUI that is modified to allow CN or other hardware to boot with the Global ROM and pass a SafetyNet check. Ultimately, I had given up on this endeavor because I was able to accomplish that using the Magisk module I created and posted here. Due to needing to have a device that was not rooted (running it for work with both personal and work SIM, and Airwatch detects Magisk no matter what I do), I came full circle.
Due to a design decision made by Google, I have found it is possible to make the androidboot.verifiedbootstate show up in a manner that is perceived by Google as "green" without triggering the bootloop code that is included in the system services that Xiaomi is running. To that end, I am posting an AnyKernel3 file here with the stock Global 10.3.2.0 ROM kernel, configured in such a manner as to bypass SafetyNet checks.
I only have one device to test this with, so hopefully it works for you too.
Edit: The patcher version should work on most versions of anything MIUI. It does not contain a kernel, it simply patches the CMDLINE to make it pass SafetyNet.
Standard Disclaimer: I have tested this, and it's a stock kernel, just with modifications to the kernel boot cmdline. I am not responsible if your device bursts into flames, fails to alarm clock and you are late for work, sends inflamatory SMS messages to Kim Jun Un, etc.
Patcher V2: Updated with AnyKernel3 changes:
Download V2
NOTE: I was not able to get my device to allow Google Pay with this. I believe Google is doing even more stringent checking now. If others want to test and report back, please do. This sets androidboot.verifiedbootstate=green now, and sets the ro.boot.hwc to GLOBAL and ro.boot.hwcountry to GLOBAL to avoid the bootloop in Xiaomi's services.
Generalized version:
Download Patcher
10.3.2.0 Specific:
Download
Edit: I was just messaged via Github by someone from Xiaomi that they are aware the source no longer works. They provided patches that *should* fix it. If that ends up working out, my intent is to provide a compiled from source version, possibly with some optimizations, and certainly using Linaro.

The patcher version linked above does not contain a kernel image. It just patches the cmdline and should work on all Xiaomi ROMS, atleast for the Mix 3. I have not tested it outside of the global ROM. I spent about 25 hours in the last two weeks working to try to backport the patches that were suggested as fixes to get the kernel to boot, but it is not done yet.

Updated Patcher above. I believe the new attestation api changes are stopping anything like this from working.

is it support miui 12 eu now ?
thx

Question attempt at learning how to compile TWRP for our device.

I am not an experienced dev, and only know enough to be dangerous. that said, i used twrpdtgen from https://github.com/twrpdtgen/twrpdtgen to generate what ought to be the berlna device tree with the necessary board files etc.
what do i have to do, specifically, to clone the twrp source via git/repo? can anybody here explain it like you realize i don't know what i am doing i'll figure git and repo out eventually, but this will go quicker if someone would enlighten me
which android version do i want to build twrp with? apparently 12.1 support isn't finished yet, so i should use 11 with aosp source?
note, for our deivce you need to use the script on upon boot.img as we've a/b format, grab from latest stock rom to gen yourself, or see attached. also, necessary to use WSL on windows with a linux distro, or a linux vm, python on windows will not work.
please feel free to use these if it furthers the cause of compiling twrp before i learn how to use git and repo and compile it.. hehe

I wanted to try my hand at this and start digging into git and repo. I got as far as getting all the files ready, setting up the tree where it needed to be, used ". build/envsetup.sh", then lunched with option 5, which is omni-berlna_eng, which is closest to the twrp minimal manifest build option.
After I lunch, the issue arrives with the fact that omni-berlna_eng uses a depreciated PRODUCT_STATIC_BOOT_CONTROL_HAL, whatever that means. So I tried using lunch option 2, which would be an aosp-arm64_eng, but that just gives me the error "#### failed to build some targets (1 seconds) ####".
As of now, I'm at a loss. I don't have the extra time to spend working on this to make it function, and I only get a few hours at a time to get a crack at it, but nothing seems to work.
Edit:
I should mention, this is my first attempt at anything android development. I got this phone as a secondary carry on and I've dirtyflashed Pixel Experience onto it using a method found for Moto G Power TONGA. Wanted to see if I could get TWRP running since dirty flashing killed my mms and calling services.

[ROM][UNOFFICIAL][SUNFISH][A11] LineageOS 18.1

I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com

GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.

P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.

The September update is now live.

Does banking app works?

My bank's app has always worked fine on LineageOS. Your bank's hasn't?

icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box

icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!

Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.

The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy

Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?

I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?

Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running

It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.

Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!

Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!

icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts

I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!

Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.

I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!

[ROM][UNOFFICIAL][A13.0][sunfish Pixel4a 4G] crDroid v9.5+ with GApps

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device, while adding a lot of eye-candy (ie features).
Features:
https://github.com/crdroidandroid
Screenshots
https://crdroid.net/#gallery
Flashing Instructions:
See the post: https://forum.xda-developers.com/t/...crdroid-v9-5-with-gapps.4593649/post-88663897
Pre-installation:
Download the ROM
download the May 2023 stock firmware (*NEW STEP*)
Backup any important data
Have an exit strategy if it goes wrong
GApps are included
Magisk 25.0 or newer for root (after first boot) - NOTE: v26.1 is the currently latest stable build.
NB: The FASTBOOT release method i use is not that well documented. But, iuts basuically what occurs from flashing google supplied firmware releases, so it must be at least half good. It's a few more build steps & time, but it also makes it far easier for me to flash ( and for you). Not having a working TWRP, I dont understand (apart from the extra steps. time & storage) why all ROMs for P4A are not released like this.
Update installation:
Leave out the -w from the command. Its hard to miss
Sources:
ROM: https://github.com/crdroidandroid
Device: https://github.com/LineageOS/android_device_google_sunfish
Kernel: https://github.com/crdroidandroid/android_kernel_google_msm-4.14
Vendor: https://github.com/TheMuppets/proprietary_vendor_google_sunfish
Gapps: https://github.com/BlissRoms/platform_vendor_bliss
Download:
ROM crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT.zip MD5: 575B8DEDB8371839AD38888BBB4F820E
BOOT IMAGE crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT-boot.img MD5: A9BD232C4773E4B6C5A5BA19E2C1DC68
Changelog: see attached in the release post listed above as flashing instructions
Known issues:
You tell the rest of us!
Visit official website @ crDroid.net https://crdroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help the crDroid team pay server costs
OR
Donate to help others

The initial "out of the box" builds of crDroid 9.5 (A13) kept failing at the veeeeery last stage, where it would try to build a flashable image, and would fail the check that it would fit on the devices partitions.
I then built a non-googled version (by accident) and that succeeded. Obviously because the google apps installed by default, by crDroid, were taking too much space.
I spent HOURS trying to find where in crDroid the list of which google apps are installed, but failed. I am sure if someone pointed it out to me, I would slap my forehead, and say "obviously"!. And that is one of the difficulties in building crDroid. Other ROMs have telegram channels where one can speak directly with the ROM devs to ask questions. All I could find for crDroid was a user channel.
So, to get a build with google installed, I set it up to build crDroid without google, and added in the code from Bliss (a ROM I have already built, and they have addressed the size issue specifically for pixel devices. inc sunfish) to add google services & apps. That worked! I also noticed that there is an official release here for another device, on XDA, that also has no google...
The google apps installed by what I have done are actually pretty comprehensive. Below is a list:
GoogleExtShared
GooglePrintRecommendationService
DocumentsUIGoogle
GooglePackageInstaller
TagGoogle
CalculatorGooglePrebuilt
CalendarGooglePrebuilt
Chrome-Stub
DevicePolicyPrebuilt
GoogleContacts
GoogleTTS
LatinIMEGooglePrebuilt
LocationHistoryPrebuilt
Maps
MarkupGoogle
ModuleMetadataGoogle
Photos
PixelThemesStub
PixelThemesStub2022_and_newer
PrebuiltDeskClockGoogle
PrebuiltGmail
SoundPickerPrebuilt
TrichromeLibrary-Stub
WebViewGoogle-Stub
talkback
AdaptiveVPNPrebuilt
AndroidAutoStubPrebuilt
ConfigUpdater
DeviceIntelligenceNetworkPrebuilt
DevicePersonalizationPrebuiltPixel2022
FilesPrebuilt
GoogleDialer
GoogleOneTimeInitializer
GoogleRestorePrebuilt
PartnerSetupPrebuilt
Phonesky
PrebuiltBugle
PrebuiltGmsCore
PrebuiltGmsCoreSc_AdsDynamite
PrebuiltGmsCoreSc_CronetDynamite
PrebuiltGmsCoreSc_DynamiteLoader
PrebuiltGmsCoreSc_DynamiteModulesA
PrebuiltGmsCoreSc_DynamiteModulesC
PrebuiltGmsCoreSc_GoogleCertificates
PrebuiltGmsCoreSc_MapsDynamite
PrebuiltGmsCoreSc_MeasurementDynamite
AndroidPlatformServices
SafetyHubPrebuilt
ScribePrebuilt
SecurityHubPrebuilt
SettingsIntelligenceGooglePrebuilt
SetupWizardPrebuilt
TurboPrebuilt
Velvet
WellbeingPrebuilt
EmergencyInfoGoogleNoUi
Flipendo
GoogleServicesFramework
PixelSetupWizard
QuickAccessWallet
StorageManagerGoogle
TurboAdapter
WallpaperPickerGoogleRelease
com.google.android.dialer.support
Personally, im a little chuffed I got it working. I would also like to say, the instrctions for building crDroid on trheir guthuib page are really lacking. I had to use what I learnt from other ROMs (and their instructions) to even get started.

AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.

MY future plans for this ROM.
Firstly, this is UNOFFICIAL. I am not associated with crDroid in anyway. Any of you could do the same as what I have done.
If there is a bug, 1 of three things could happen.
1. Its something you have added to the ROM. Its now up to you to fix.
2. If the bug is sunfish specific, but I dont get bothered by the same bug, Meh. Chances are I wont fix it
3. Its a crDroid or LOS bug, I will direct you to post the bug with crDroid / LOS.
By all means, post the bug here to let others & me know and maybe help you, but do not get perturbed If I dont start spending time coding to fix it.
Changes to the ROM I foresee right now, since it is a personal share of the ROM I plan to run on my daily, primarily for ME, are:
The QS tile headers are a Japanese anime theme. I will probably replace those with some abstract textures
The default wallpaper which appears on the lockscreen before you unlock, although is better than others, I will change to another space theme to match my Live Wallpaper
The theming colours are missing Teal!?!? I will probably replace an existing colour.
Im thinking *maybe* the boot animation to the old nexus prime prime one (see below)
maybe others I haven't noticed thus far, but I dont think anything too crazy or offensive.
NO GUARANNTEE, but since crDroid add features very often (eg brightness slider styles since the official v9.5 release), I will probably go with close to monthly builds to keep up.

Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available

chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.

DiamondJohn said:
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.
Click to expand...
Click to collapse
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.

chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Click to expand...
Click to collapse
And to state the obvious, I LOVE this device and build custom ROMs for it, for me to use.
A few weeks ago I watched a number of videos about how this device is still a good choice today. So we two are not the only ones.
https://www.youtube.com/results?search_query=pixel+4a+2023
chozendroid said:
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever? I tried adding Google services via a Magsk module and it wasnt great. The keyboard never popped up when I entered a text field, and I couldnt install the updated GBoard. I had to install the M$ keyboard. AND that GApps module obviously requires root/Magisk.
I personally would of assumed "VANILLA" android (ie ASOP / Pixel Device) includes Google Services, but meh, what do I know.
chozendroid said:
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.
Click to expand...
Click to collapse
As for Force_Close-Clear-Freeze-Hide, im pretty sure you don't have to root the device.
And maybe, dont forget the link I posted to the other android file host build. Maybe he has built with less google stuff. But, I think he built before the brightness slider themes were added and who knows when the next build will occur. He has no contact details. I would like to know how he got GApps to be included.

I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.

DiamondJohn said:
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever?
Click to expand...
Click to collapse
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb

prog19 said:
I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.
Click to expand...
Click to collapse
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
prog19 said:
.... I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload)....
Click to expand...
Click to collapse
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.

chozendroid said:
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb
Click to expand...
Click to collapse
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.

DiamondJohn said:
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.
Click to expand...
Click to collapse
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.

DiamondJohn said:
DOPO aver creato quanto sopra, ho scoperto che qualcun altro ha effettivamente creato crDroid con googl;e installato e l'ha pubblicato su Android File Host. Non ho testato la loro build, ma sono passati 10 giorni e ci sono stati commit extra da quella build. In particolare gli stili del dispositivo di scorrimento della luminosità.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
Penso che qualche anno fa mi sono imbattuto in questi caricamenti AFH di questo ragazzo quando avevo un Nexus 5, e non sono riuscito a trovarlo comunque per contattarlo allora.
Click to expand...
Click to collapse
DiamondJohn said:
AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.
Click to expand...
Click to collapse
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it

DiamondJohn said:
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.
Click to expand...
Click to collapse
Thank you for the very detailed answer

Marcia8246 said:
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it
Click to expand...
Click to collapse
Yes. I already explained the difference, in addition to not knowing any details that I have also doc'd in the OP.
To be clear, I know nothing more about this ROM than you. Actually, even less, as you have flashed it.

chozendroid said:
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.
Click to expand...
Click to collapse
As for working for "other devices", thats one of the changes in Googles newer devices. But the same would go for the Pixel 4A 5G, the 5, 6 & 7 series pixel devices. Try and find a single sideloadable ZIP that makes an incremental change on one of these devices, to one of the system partitions. And its not just google. Thats one of the reasons to use Magisk modules, they allow a partial targeted change to a RO partitions.
I think there is an official A13 GrapheneOS ROM for the Pixel 4A, that has no GApps.

FYI: Im kicking off a kinda test build, with a smaller google footprint, and 11 modified header QS images.
Also ONLY on my installed ROM on personal device (NOT in the ROM). I have debloated Aperture (the Camera)l, Eleven & Audio FX and installed Google Camera (It has "Night Vision" which I dont know if its better, but I like the option), Vinyl as my music player, and ViperFX as my Eq. Viper eq's the sound for the player, but not from some other apps.
See below post for how:
[OFFICIAL] BlissRom 16 [Typhoon] [sunfish][Android 13]
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience. Our focus...
forum.xda-developers.com
The RisingOS actually has a good Music player, that is updated on F-Droid, I would probably go with that, if I remembered the name, and wasn't committed with boot scripts to Vinyl. Since its part of a ROM, probably get more attention.
I also liked the calculator on RisingOS. I'll check if someone can get me the APK and it works, and the name of the Music player.

FYI: I did a test build over last night, but three of my changes didn't go as expected, so I will need to fix them and do another build before release. DOH!
The boot animation frame rate is WAAAaay to fast
One of my new QS Tile headers isnt displaying. Dont get it as it is literally the same as another one just a different shade/colour pallet
The default wallpaper remained unchanged.
I did note that there was a small flurry of changes (bug fixes, not new features)
One of the new headers is interesting, but I dont think I will personally use it (ironically I would use the one that failed...)
Its basically a view of the circuit board from the back. Kind-a simulates you are actually dragging the screen off to reveal the circuits underneath. If only I could find a photo of the correct side of the main board and not from the back. Anyone?
Another FYI, I installed ReVAnced as root and it went without a hitch, All I did was:
Downloaded & installed the revanced manager APK
Started it up to see which version of You Tube it expected
Source the correct version of youtube from APK Mirror OR APK pure etc etc etc
Installed the base correct & expected Youtube
Ran ReVanced Manager. Selected it to apply the "Default Patching" BUT turned off the MicroG support
Ran the patching
Installed it as root
rebooted
Detach youtube from playstore
Enjoy!

forgot step 8.5 for ReVanced install, Detached it from the playstore
also realised the reason / where I failed on the three points of the ROM build issues.

Database Info

welcome