I have download AOSP Android 5.0.0r1 and '$ git clone' both tuna and toro into the device/samsung folder from source. Then I took the drives for toro (Android 4.3) and extract them into the vendor folder. Then I '$ make clobber', then '$ source build/envsetup.sh', then lunch aosp_toro-userdebug. Next I '$ make -j4' and then '$ make otapackage' but it did not work... It had a make error. I did all the right steps to compile AOSP Android 5.0 for Galaxy Nexus (Verizon) but it won't let me make a ota zip or make in general!!! So I need help compiling my own AOSP Android 5.0 for my Galaxy Nexus... Can any one help?????? (I will share the ota zip after I get it to work... I will be needing testers!)
You must modify device trees to be compatible with Lollipop... otherwise you'll face errors.
Ok.... I never really did that before. Do you think you can tell me how or give me a link to a tutorial on how to edit the device's tree?? And plus do I have to do tuna's device tree too?
Related
I found a guide for compiling AOSP for 4.0.3, but I'd like to do it for 4.0.4. I'm more interested in learning about roms and stuff, but I don't want to use the rom kitchen. I have a working dev environment (ubuntu 10.04, followed the setup procedures on the AOSP site).
I have my repo sync'd and ready to build, but I read that I need proprietary libraries for my phone. Unfortunately I don't see anything about the cdma G nexus on this page (only maguro):
https://developers.google.com/android/nexus/drivers
So.. where do I find these? I've been doing a lot of searching but unfortunately I can't find any information on this. Thanks in advance.
The bottom of the page you linked has a few binaries for the CDMA Nexus. Other than those, use the extract-files.sh script in the device folder (device/samsung/toro) and if you run that with your phone attached and adb enabled/setup, it will pull the rest of the files that you need off of the phone.
Thanks! The files in that guide were from 4.0.3, would these be different from 4.0.4?
Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.
The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung
Hi everyone
Well, I'm trying to build my first rom today, and after a lot of tutorial, still something I don't understand.
So, I want to start with the last AOSPA and for now, I don't really know how to put in the local_manifest file. I have found some Github with android_device_samsung_klte source (I guess ?), but I see a lot of local_manifest (for aospa) with vendor = pa_klte. Someone can explain me that ? x)
Other question, what's the command "brunch" is ? Seems to be used to build, but my Linux didn't recognize it...
So, to sum up, I looking for someone who had already build an AOSPA Rom, in order to help me to build the klte build !
I would like to see a version of Paranoid Android for the Galaxy S5 as well. I own the Verizon Developer Edition of the phone and am willing to test out Paranoid Android builds for it.
We will never officially support the s5
#stayparanoid
No problem about the "officialy supported".
Anyone to help me ?
After some tests... Same error...
Why will you never officially support the s5?
Hey XDA!
I've been trying to learn to compile AOSP so I can customize ROM's from scratch instead of having to steal someone else's compile and make modifications from there. I definitely don't want to take the work of others and back track to make changes.
I've got a Nexus 7 2013 LTE and I've setup a Linux build environment. I've installed the correct packages, followed all the instructions on the AOSP site, and downloaded the proprietary binaries (both the current 4.4.4 and preview binaries) to try and create a AOSP Lollipop 5.0.2_r1 build. I know there are ones out there that are working almost flawlessly, but I can't seem to get it to boot. My file sizes for system.img and all other packages are the same after compiling, I "make clobber" once executing the shell scripts to create the vendor folder in my source root, and I see the vendor files being processed during the build, but once the package (both ota and manually built attepts) are fastboot loaded, I get a boot loop, and I'm not sure why, it instantly hangs and reboots as soon as the "ANDROID" screen appears.
If anyone can give me any guidance, I want to start building ROMs for the community, but I just can't seem to get a bootable build to compile.
I may have missed some details, so if anyone can help me with figuring this one out, feel free to PM me, or leave a note on this topic.
Thanks!
Hello, guys.
I have a problem with building Paranoid on my D855 device, here's a log: https://pastebin.com/raw/EUZfeFgg
I put https://github.com/xiaolu/mkbootimg_tools already and that fixed dt.img problem, but there's next one with ramdisk-recovery.img (or recovery.img).
Can you help me?
What was your first error, show your device and common tree, show your local_manifest.
ppajdek said:
What was your first error, show your device and common tree, show your local_manifest.
Click to expand...
Click to collapse
the first error was the same, but instead of ramdisk-recovery.img/recovery.img was just dt.img
https://github.com/LineageOS/android_device_lge_d855
https://github.com/LineageOS/android_device_lge_g3-common
https://github.com/LineageOS/android_kernel_lge_g3
https://github.com/TheMuppets/proprietary_vendor_lge
these are all that I use
You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it
ppajdek said:
You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it
Click to expand...
Click to collapse
wielkie dzięki, spróbuję. można jakiś bliższy kontakt (telegram, whatsapp)?
(thank you so much, I am going to try it)