hi all,
Am new to Building Android from source.. Am compiling AOSP based Android M preview 2 rom for Google Nexus 5 device, but getting errors when compiling and it stops.. could anybody guide me anyposts which explains complete AOSP rom building for nexus 5... not custom rom
Thanks
Related
Hello, I am newbie of Android development
I am started build an AOSP to my Samsung Galaxy S2
I heard build an AOSP rom is very difficult on Windows, so I will use Ubuntu.
However, what ubuntu version is recommended for build an AOSP?
I need your help Please help me
I've attempted to port a nexus 5 lollipop ROM to our beloved device using android kitchen. It ported successfully but I can't get it to flash. Any seasoned developers wanna give it a shot? Let's work together and bring lollipop our way!!!
Here's the android kitchen post but is no longer supported by developer... http://forum.xda-developers.com/showthread.php?t=633246
Here is the rom i ported:
http://goo.gl/I3Durt
I have another updated build I will be uploading soon
Gapps are included..
Won't let me edit op anymore... But here's the original thread I took the ROM I ported from
http://forum.xda-developers.com/showthread.php?t=2840901
Bad.Fish said:
I've attempted to port a nexus 5 lollipop ROM to our beloved device using android kitchen. It ported successfully but I can't get it to flash. Any seasoned developers wanna give it a shot? Let's work together and bring lollipop our way!!!
Here's the android kitchen post but is no longer supported by developer... http://forum.xda-developers.com/showthread.php?t=633246
Here is the rom i ported:
http://goo.gl/I3Durt
I have another updated build I will be uploading soon
Gapps are included..
Click to expand...
Click to collapse
Seeing that there is no kernel source, you need to build your own kernel, look at the HTC One (M7) L Preview rom and you will see that a heavily modified kernel was used to make it boot. Anyway, you would have been better off building it from source generally, AOSP. If a kernel dev was to help me with a working kernel, then I would gladly build Lollipop for the One S
dd98 said:
Seeing that there is no kernel source, you need to build your own kernel, look at the HTC One (M7) L Preview rom and you will see that a heavily modified kernel was used to make it boot. Anyway, you would have been better off building it from source generally, AOSP. If a kernel dev was to help me with a working kernel, then I would gladly build Lollipop for the One S
Click to expand...
Click to collapse
Can you post the link of the lollipop preview you mentioned? I can't seem to locate it
Bad.Fish said:
Can you post the link of the lollipop preview you mentioned? I can't seem to locate it
Click to expand...
Click to collapse
[PORT] [ROM] Android L Developer Preview for HTC One [ALPHA 2]
Hi all,
I've a question for you guys.
I've a SG3 (i9300), I'd like to know if using the cyanogen device tree for my device (located here) is possible to build AOSP source code.
if yes, then it looks like that would be possible to compile Lollipop AOSP for my device.. am I right ?
Thank you very much.
Cyanogen IS AOSP... Lol. Its AOSP with added features. If that's not an Android 5.0 lollipop kernel source, then it won't boot out of the box. Your best bet would be to get some Android 4.4 kernel source and do ramdisk edits and what not needed to get an Android 5.0 ROM booting. Alternatively, if your device is CM supported, I know they were talking about releasing CM12 soon, you could just hold out to see if your device is supported. Outside of CM, many custom ROMs (AOKP, Pacman, etc.) Take it upon themselves to release ROMs as well. Example: PACman had a 4.4 custom ROM out and in circulation, even before cyanogenmod, so u never know!
mingolianbeef said:
Cyanogen IS AOSP... Lol. Its AOSP with added features. If that's not an Android 5.0 lollipop kernel source, then it won't boot out of the box. Your best bet would be to get some Android 4.4 kernel source and do ramdisk edits and what not needed to get an Android 5.0 ROM booting. Alternatively, if your device is CM supported, I know they were talking about releasing CM12 soon, you could just hold out to see if your device is supported. Outside of CM, many custom ROMs (AOKP, Pacman, etc.) Take it upon themselves to release ROMs as well. Example: PACman had a 4.4 custom ROM out and in circulation, even before cyanogenmod, so u never know!
Click to expand...
Click to collapse
Hello, thanks for your answer.
I'd like to know this only for learning purpose, I'm not going to compile the AOSP
What I don't understand, is why adding the device tree to the lollipop AOSP is not sufficient to boot out of the box, can you please explain this in details ? Many thanks.
Hi guys!I want to become an android developer and I know about the AOSP project,but I have not found based of android versions.I want worker on ICS ROM for galaxy pocket(GT-S5300)or cyanogenmod 9,but on a "pure"ROM,without any modification,like nexus android version,for worked on it and optimize for any devices.
1)How I can optimized an android version like Nexus devices for a specific device?
2)Where I can download the necessary for a ROM or a ROM to be optimized?
Thanks
Simply start by downloading cori's source and aosp android of your choice, then edit & merge things from source to aosp then compile.
Hi all,
I want to build my first rom. I'm a software developer (Java and Web), but my Linux knowledge is somewhat intermediate.
I have a Moto G4 Plus laying around. Here's what I have done so far:
1. Downloaded the AOSP source from Google for android-7.0.0_r15 (Nougat)
2. Found the Kernel Source for the Moto G4 Plus (Nougat)
I'm stuck at adding the device's kernel source to the AOSP source. How do I combine the two?
Here's the link for the kernel source: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPJS25.93-14-10
I've tried looking this up online but the results are very limited.
As far as I understand this kernel source provides everything I need to make the ROM compatible with my device, right?
Could someone point me to the right direction?
Much appreciated.