Hi,
I am new to ROM building.
I setup AOSP build setup on all my machines, eventually getting it to build on a Ubuntu machine (cold build took around 10 hours, but subsequently has been fast).
I build Android 10 build for Pixel, and successfully flashed it (also could build and flash for Pixel 2). But, I noticed the skin is nothing like a stock Pixel skin. It looked like a Cup cake UI, with all UI elements looking super basic / primitive.
How to build and flash an AOSP build from scratch, that looks like a Pixel ROM?
What did I miss?
Thanks in advance, excuse noobie stupidity
Related
I want to begin development on a new rom but I'm kind of a newb with this development junk :/
If anybody can help me go towards the right path that would be pretty frikking awesome
soooo..where do i begin?
http://source.android.com/
I made a working AOSP build years ago, wasn't that hard, probably easier now.
I'd suggest starting with stock aosp (see above) then trying to build using the Cyanogenmod source.
Good evening all,
I came across a post on here a while ago which asked about the ability to run Gingerbread on a Nexus 7 of 2012 and the response was basically, why? And, co pile it yourself.
So, I thought I'd give it a go, just to see what it does.
Previously I've only ever flashed custom ROMs and I've never downloaded AOSP before, but everyone starts somewhere.
My position at the moment is I've built Gingerbread from AOSP on my server but as I didn't choose Nexus 7 when building it (due to it not having an option to lunch Gingerbread) I opted for the generic build.
So, this built but as it's generic it seems to only be the system, no recovery or boot.img etc.
So, I looked around at guides, building a boot.img for your device in AOSP etc, kernel compilation, but due to my bizarre project, I can't find anything on how to downgrade or retrofit a new boot.img into an older version of Android. Or even how to compile an older boot.img against newer hardware. Even the guides talk about swapping one ROM for another and taking pieces out but they tend to be the same versions of Android.
So, I'm asking for advice really, where do I start?
Sent from my Nexus 4 using Tapatalk
Quick update (not that I've done much on it for a while).
I managed to get the older Gingerbread bootloader installed on my Nexus 7 2012, however I couldn't get further then that, not sure what I'm missing at the moment, potentially the kernel isn't compiled.
I have been doing some research on XDA and some other sites to see what would be required to put android 7.0 on a nexus one.
I know, that sounds crazy, but I wanted to challenge myself and try to do something I should do more often - android development.
I have been sifting through the other nexus one ports and the builds and ports for the 2 phones similar to the nexus one, the HTC HD2 and HTC desire.
So far, It seems some developers have been successful in getting android 6 working on the HD2 and desire. I figured I would try to do so on the nexus one, seeing as it has identical hardware in a lot of respects.
I am wondering if my approach is on target. To get this to work, I think I would need:
-custom hboot to allow for booting off sd card for OS (internal memory too small for android 7, even if slimmed down)
-custom partitioning of sd card
-custom rom built from android 7 and nexus one hardware drivers
-porting of linux kernel from HD2 to nexus one
-boatload of debugging
-compile rom and kernel into one zip installation package
Is there anything else I am missing? I apologize if I am using the wrong terminology, I have only been doing this for a few days (but have been rooting and installing roms for years).
I figured it was my turn to dig a bit deeper and try development myself.
If anyone has any input, I would be all ears. thanks a bunch!
mods: If this post is in the wrong thread (or you think it should be pushed to nexus one thread), feel free to push it anywhere that makes sense. thanks!
I did some more research and I think It will make most sense to port the 3.0.101 kernel from the HD2 and then build the rom
I am going to try android 4.4.4 rom with the 3.0.101 kernel to see how that goes first.
The main questions now:
-am I going to need a new version of TWRP for the new 3.0.101 kernel, or can I get away with TWRP 2.6.0.0 recovery?
-will I need to make a new version of blackrose / hboot because of android 6.0 / 7.0 / new kernel?
thanks for any input!
I just got a Moto G Power, replacing a UMIDIGI Power 3(don't ask). I'm currently on the stock ROM and rooted.
I'm hoping to move to a custom ROM.. Can someone let me know which custom ROM is the most stable and consistently updated? Looking for one that is kept security patch updated.
Also, has anyone tried to flash a GSI?
I can try all of these myself, just trying learn by shortcut.
smvsmv said:
I just got a Moto G Power, replacing a UMIDIGI Power 3(don't ask). I'm currently on the stock ROM and rooted.
I'm hoping to move to a custom ROM.. Can someone let me know which custom ROM is the most stable and consistently updated? Looking for one that is kept security patch updated.
Also, has anyone tried to flash a GSI?
I can try all of these myself, just trying learn by shortcut.
Click to expand...
Click to collapse
I've tested a couple of times out on here which were the OmniRom and the Pixel experience. I like certain features on the Pixel experience but I think Omnirom is a bit more stable and things work better on Omnirom. I'm currently on Pixel Experience which has a few notable problems such as that I get a camera error on PE and the Bluetooth won't connect to my speakers on PE. But I like the ringtones and notification sounds better on PE. Don't get me wrong. The PE is still a usable rom though.
I tried OmniRom, Havoc, RRMix and Erfan Generic Gsi(This one was Android 11). Decided to stick to Havoc as I like customization and Havoc is next to RRMix in this. RRMix would have been my choice but I was unable to install Viper4Android successfully and hence had to settle down with the next best (Havoc with November 5 Security patch). All of them were otherwise stable. Omni was on March Security Patch if I remember right. Can't say about the update frequency as It's just over 3 weeks for me. Have fun!!.
havoc seems to be the only rom that's up to date with security patches. that's what I'm running.
Havoc. It just works and can be beautiful.
Hello all,
Im newbie in the site and also in Android AOSP.
I would like to know if is possible:
I have a AOSP X86 Emulator and I made some changes in HAL . So I desire to test in a Pixel 6 . i believe that I need to install the custom ROM.
Some Steps that I identified.
1- Convert my X86_64 AOSP Android 12 Custom ROM => ARM.
2- De-activate BootLoader .
3- Flash my Pixel 6.
Would you help me if these steps are correct?
I have no idea where to start. Any suggestion to tacke the task is well apreciated.
Thanks a lot
Convert? I'm not sure that is the right word here, though I know it can be done if you have the source code. In essence you would be compiling with ARM as the target processor instead of x64. From there your steps are essentially correct, though I would take steps to ensure you can recover from a problem prior to unlocking the bootloader and flashing the ROM.
Thanks a lot for your reply!. Sorry to bother again.
In my case I did some changes in HAL AOSP Master X86_64 and I've tested in Cuttlefish Emulator (aosp_cf_x86_64_phone-userdebug).
If I didn't misunderstand, what you suggest firstly is to compile, Im a little confused in which I have to use:
lunch:
1-armv8-eng
2-aosp_arm64-eng
3-aosp_cf_arm64_phone-userdebug
4-aosp_oriole-userdebug ->( I guess this one).
and then continue with the steps detailed above.
Many Thanks for your help!
@Palinamarne And I wouldn't be able to tell you which one to use. My days of tinkering that deeply beneath the hood of Android are long since behind me.
@Strephon Alkhalikoi No problem! I'll play around a bit and put the details here. Thank you very much for your help.
Were you able to run this custom aosp build in an emulator?