Trying to build AOSP for Sprint s3 - Android Q&A, Help & Troubleshooting

I'm having issues building a pure AOSP ROM for my Sprint s3. I made a local_manifests file and created a roomservice.xml file with Muppet repo installed. Now when I run the lunch command I see my device, cm_d2lte, as a option. I select it and I get a error saying, "can't locate config makefile for product cm_d2lte". After doing some research I found that I needed to make edits to the Android.mk and AndroidProduct.mk so it will point to the correct device and I still get this error. This is my 1st time having this issue building a ROM, built cm11 without a hiccup. Could use the help. Thanks.

Related

[Q] Help with AOSP build?

HI, I'm trying to build a ROM for the Samsung Transform Ultra, its a low-use device so not much going on with it in the open-source community, and its been really hard trying to get everything together that i need to build. I have a build running in the emulator and i am just trying to get all the proprietary bits together so that i can put int on my device. I have copied a repo from someone on github who was attempting to get CM running on the device. I DO NOT WANT TO BUILD CM. I just want to build stock GB, but this is the only repo i could find for my device, so what i am trying to do is remove all the cyanogen bits and sort of reverse engineer the rest. so right now, my question is this:
I had a generic build running in the emulator, but since i have added the device/samsung/transformultra/ directory to my build i get this error when i run lunch and choose option 6 (transformultra-eng):
Code:
Lunch menu... pick a combo:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
6. transformultra-eng
Which would you like? [generic-eng] 6
build/core/product_config.mk:203: *** No matches for product "transformultra". Stop.
** Don't have a product spec for: 'transformultra'
** Do you have the right repo manifest?
[email protected]:~/mydroid_GB$
after the first time i received the error, i added this line
Code:
<project path="device/samsung/transformultra" name="device/samsung/transformultra" />
to .repo/manifest.xml, but it didnt seem to change anything and i still get the same lunch error...any ideas? its been a while since ive built a rom for a device and last time i did it was way easier because it was an htc device, but this is my first samsung device and its sprint, too, so also my first CDMA device, and everything is so different from what i know of htc devices, its really throwing me for a loop. Can somebody please help me troubleshoot this? thanks in advance...
-BMFC

[Q] merge manufacturer source into android source

total noob here - web developer turned bad
I was wondering how to merge manufacturer source code into android source code? I see instructions every where for compiling android's source, and the manufacturer's source, and they all say "merge the source code", but they don't say how to do that. i've downloaded, via android's "repo" script, allllllllllllllllllllllllll 20gb of android source code (once it's setup), and i've also got all the LGE source code (for their hardware kernel drivers, i guess?). the instructions are pretty clear, but, there's that 1 damned step that is not clear for this noob "... And, merge the source into the android source code".
what i'm stuck on, is "HOW do i do that, and WHERE do i do that"? Do i just copy the manufacturer source into a specific android source folder, or what?
thanks in advance.
bump.... this is where i'm stuck at too. would like to build from pure source ATT/AOSP Have dl'ed both sources and need to be merged. I have seen several tutorials on building from source but they get vaige and want to use CM all the time. is it possible to do w/o CM? if so how.
Thank you also.
I also was unsure about that point, but after looking at the file, it seems pretty clear. Just extract the content of LGE-file to the android directory, as mentioned in the LGE Readme and overwrite existing files and try your luck with a compile. I tried it, but my installation of OpenJDK conflicts with building Android from sources. Maybe you've got more luck!
00001101 said:
I also was unsure about that point, but after looking at the file, it seems pretty clear. Just extract the content of LGE-file to the android directory, as mentioned in the LGE Readme and overwrite existing files and try your luck with a compile. I tried it, but my installation of OpenJDK conflicts with building Android from sources. Maybe you've got more luck!
Click to expand...
Click to collapse
Thanks for the suggestion, but still no such luck, I tried that and still fails at webcore(permissions denied) =I tried to build as user and as root user and still get some thing, I posted the error in the forums for my phone but no one has replied. but again thank you for the suggestion.
BTY, did you get the JDK to work?
Thanks for your feedback. I couldn't resist and installed Oracles Java version, just to see what problems might be left .
And of course, there came the final point, where I got a 'make no rule to make target' message while compilating, so the process stopped. First with pure AOSP and today with CM 11. Obviously I'm no coder, I just fiddle around with stuff, so there's unfortunatly where I have to give up. But it was interresting to learn a bit about the essentials
Did you have a look at this: http://code.google.com/p/android/issues/detail?id=38879
Following that, it might be, that there is a file missing in your sources?

[Q] Building aospa errors on d802

*update* Building successful. Help no longer needed,
Hello there
I'm currently attempting to built aospa and it keeps failing while loading settings for my phone d802 (lg g2) it claims the repo doesn't have information for this phone or manifests etc., I decided to look this up on the repo and discovered it only has d801 and d803, I figured not a problem so i set out to searching forms upon forums and google searches that just angered me more and more because either I was doing it wrong or it was just loading the wrong information,
I Finally gave in and decided to load the Proprietary_vendor_lge from muppets repo which includes d802, had to alter some file names with the pa_prefix and finally it starts the build process but then stops shortly after with cannot find config errors. I also tried this using my cm repo's lge device settings and this causes more errors than is good.
I decided to now start a fresh, new build environment with a fresh aospa 3+ repo sync for 4.4 android. and would like help on where to go from here, even if just suggestions on where I can look myself, what terms to use to do my own research or if you feel like giving the answer's please feel free.
In the past I've not had such issues but that results I guess from usually owning a nexus. (off topic)or the dreaded i9500 ubuntu errors that caused my system to overheat and die on compile(off topic)
I have setup a build environment in linux (ubuntu for ease of use) i decided this time to go with a pre-built one mentioned from the news page (in case of my own setup errors)
I have repo synced with aospa-legacy
I am awaiting further direction.
--------------------------------------------------------------------
* Update*
Fixed the problems,
In case interested, also please tell me if there was an easier way....
I repo sync'd with aospa-legacy,
I then oulled the d802 files from cm11 repo and copied into the device and vendor locations (as needed)
Then pulled the kernel for my device from cm11 repo and copied to the root under kernel
repo synced again and it filled in the gaps (not sure if this was needed)
got device proprietary files by linking phone and using ./extract-files from the d802 folder
then built the rom.
New error
no rule to make target vendor/lge/d802/proprietary/lib/libacdbloader.so
* Update * fixed libacdbloader.so by getting file from "TheMuppets/proprietary_vendor_lge/d802/"
-----------------------------------------------------------
thanks
Thank you
Also please if in wrong section i tired to locate correct place
Added my spelling is flame worthy as is my grammar, please be lenient with this.
accidental "double post so to speak"

[Q] Kernel build error for AOSP 4.4.2

Hi,
I am trying to compile a kernel for a specific device on AOSP 4.4.2 and got the following error. I understand that the variable is declared twice and need to be removed from one. Vendor folder cannot be removed since it has device specific configuration files. Looking into external/jpeg folder I am not able to decide which particular file to remove. Could some one let me know how to fix this.
HTML:
build/core/base_rules.mk:134: *** vendor/google/libs: MODULE.TARGET.SHARED_LIBRARIES.libjpeg already defined by external/jpeg. Stop.

[TUTORIAL][AOSP_BUILD] How to fix "no rule to make target" error

Hi everyone !
After spending a lot of time trying to fix this error while building AOSP lollipop 5.1.1, I found a "magic" solution, that I was unable to find on xda or stackoverflow. Thus, I want to share this "fix" with you today, because I realized that a lot of people were having the same trouble without finding any solution.
So, what's the problem ? You want to build AOSP lollipop 5.1.1 for your device, for me it was a Nexus 5 (hammerhead). This is what should be done :
- repo sync google source
- download Nexus 5 binaries
- execute extract-*.sh files so that binaries are extracted
- source build/envsetup.sh
- lunch and select aosp_hammerhead
- make updatepackage -j# (# corresponding to the maximum number of jobs, according to your CPU)
Yet, after doing lunch, no include was done while doing "make". Therefore, there were lots of errors like "no rule to make target mkbootimg".
Then, I realized the problem was the "lunch" command. So, I opened a new terminal, and I only did the "source build/envsetup.sh" without the lunch, and then I exported the target like that :
> export TARGET_PRODUCT=aosp_hammerhead
And thanks to that, make udpatepackage worked !
Last tip, if you get some weird compiling error, after loosing your mind trying to find the solution, close your terminal, open a new one, source build/envsetup.sh and re-make again. Sometimes it does the work, don't ask me why
That's it ! Hope it helps =)
PS : Sorry if my English is bad
Thanks, bro... U saved my day

Categories

Resources