*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"
Related
I am trying to get my build environment set up so I can build froyo from AOSP source for the Gtab.
I have gotten my linux mint box set up to the point that I have successfully built 2.2.2_r1 for the emulator and its working fine. (followed the instructions from the AOSP site)
Now I want to get everything set up so I can build specifically for the GTab, but I cant really figure out what I need to do next. (I don't want to build CM6, but I did read the wiki there for tips)
I have already extracted all the required files from the stock ROM. (followed the list in the script mentioned in the CM wiki)
I know there is some other setup I need to get done (other repos that need to be pulled down?) but I am lost at this point. Seems that no one has taken the time to properly document how to do it for a froyo build, but I am sure someone has built a system for us (like CM6 - but I cant even get that repo to sync so I can look at what they did).
I hope someone can give me a little direction so I can get back on track with my second project for the GTab.
Thanks
BUMP.... I could use a little help here guys, I have a ton of source code on my drive and I just need to know what I do with the files I extracted from the gtab and the device info from cyanogenmod 6.
Am I just creating a new device in the froyo tree or do I need to get more involved with the initial setup. I want just a box stock clean froyo build that I can work from.
Thanks
First off, I have been running Ubuntu 12.04 x64 (OpenJDK) for a while now, and build regularly for Grouper and d2usc (US Cellular SGS3 variant). Grouper builds fine, flashes fine, runs great. The d2usc also builds fine, flashes fine, but I get zero radio; no bars of any color, Settings - Status reports Unknown Baseband version, same with IMEI and MEID, not even showing grey roaming bars.
This has been going on for about 1-2 weeks now. Zero build errors, the "brunch d2usc" command works great, creates a flashable zip, and the zip flashes. I have to then wipe everything in TWRP, and restore a backup (I do NOT have to do adb nv restore or anything, radio works just fine when restoring backup for Black Bean 7).
Here's what I've tried:
1. Delete entire repo, create new folder and resync. After resync, build. Flash build (again, zero errors), same result.
2. Delete entire repo again, create new folder and resync. After resync, run ./get-prebuilts AND ./extract-files.sh while running official d2usc CM10.1 nightly. Rebuild (zero errors), same result.
At this point I'm at a loss, Grouper (N7) flashes and works great (obviously wifi only version). The d2usc version works great minus the fact that I get no radio, not even roaming. I've tried the CDMA subscription thing, rebooting, and no dice still.
I need some expert advise. Anyone that could provide some clues, suggestions, insight, would be greatly appreciated. It is much easier for me (saves time, etc) to do my personal theming THEN building, so I'm not doing things twice (using apktool to decompile/compile).
Thank you for your time!
-Ryan
-Sent from my US Cellular SGS3
I think I may have gotten to the bottom of this with invisiblek/termleech's help: Building from CM10.1's repo if you don't have the d2usc stuff, it'll sync what it needs straight from CM. That was fine and all. After talking with those two guys, there's another repo called TheMuppets where all the device vendor blobs are kept (which I had totally forgotten about). I had to add this to my Local_Manifest.xml to pull down those updated blobs from this repo.
I am sync'd up, and kicked off my build. That's gotta be it. I'll know in about 45 min to 1 hour.
RMarkwald said:
I think I may have gotten to the bottom of this with invisiblek/termleech's help: Building from CM10.1's repo if you don't have the d2usc stuff, it'll sync what it needs straight from CM. That was fine and all. After talking with those two guys, there's another repo called TheMuppets where all the device vendor blobs are kept (which I had totally forgotten about). I had to add this to my Local_Manifest.xml to pull down those updated blobs from this repo.
I am sync'd up, and kicked off my build. That's gotta be it. I'll know in about 45 min to 1 hour.
Click to expand...
Click to collapse
so how did that go?? i am curious as i am sync'd up but am lost due too my lack of ubuntu experience, also i jumped into learning this with no linux experience. i have the d2usc. i dont follow how github and my sync works together to build . but i hope yours works out
Hey XDA, no time no speak,
After writing a story about it, I went and purchased the HiSense Sero 7 Pro (I recommend you go buy one), and I decided to do a source build of CM10.1 on it. There is a problem though, the manufacturer is not responding to my request of releasing the kernel source (even though I know that GPL requires it), so an issue there obviously.
Moving on though, I decided to go ahead and sync the repo. The only problem is, I am at the part where I need to make the local_manifest.xml (which I have), but because I don't have kernel source, my directories on github (located here) are empty.
I think it's worth noting that I am on an OS X system (only got 500GB, gave 75 of it to a windows partition and its already slow, couldn't imagine fighting with a Ubuntu partition), and I read the CM wiki top to bottom, spent hours upon hours googling, and no luck. Another issue I have is that when running this command:
$ ./build/tools/device/mkvendor.sh samsung i9300 ~/Desktop/i9300boot.img
I get errors with it questioning whether or not my environment is correctly set up. I also try saw that it said "Create extract-files.sh and setup-makefiles.sh scripts" but I cant run the scripts because they arent available for mac! Sooo im in a rock and a hard place man, any assistance??
Im very much welcome to giving any additional information that you may need Thanks in advance for help
Hello guys, first of all let me clarify that im a noob, but what the hell. i decided making my first steps into android development,
so i decided first of all i ll try make a build of my favorite rom (pacman rom) from their source.
im following this guide : http://opensourcegangster.com/blog/...d-your-own-cyanogenmod-custom-rom-from-source
and the videoguide related to it : http://www.youtube.com/watch?v=GAyxypK7_K8
but obviously replacing the cyanogenmod github used in the guide by pacman's github.
well lets get started, i set up a virtual machine using virtual box and ubuntu, and i got till step 5 without issues.
its repo sync time, i initiallise the repo, start repo sync, and here is the first problem i encountered.
at 32% more or less, i starting getting errors(couldnt resolve host,url return error 403,could fetch something) finally after a few minutes the repo sync ends with the message " stop sync due to fetching errors". looking up on the internet i found a way to solve this.instead of using repo sync. i had used repo sync -f . this makes the repo continues syncing although fetch errors.with this modification repo sync finish correctly
the first question is: is this well done or my source ll be incomplete because of those thing it couldnt fetch?.in case its not well done what should i do?.
once i solved this doubt i ll continue explaining other problems i had after this one.
thanks a lot guys
Hi everybody,
I'm currently in process of making my first builds of CM13 for my A310F.
The repositories for CM are unofficial, maintained by a user i tried to get in contact with, who didn't respond yet.
Now, while the stock kernel sources of MM are open sourced and a few hacks were already done in the unofficial CM repositories, the CM device/vendor/kernel sources are already a bit deprecated with a few erroneus configurations in the device repo, so I'm on my way to clean it up a bit.
Currently CM itself builds, but after booting most of the hardware features are broken and they were using the 5.1.1 kernel instead of the 6.0.1, and the blobs were not taken over correctly, or not all blobs were taken.
My question is now, how are you managing to get the correct list of the blobs needed? What is the best way to find out which blobs i need to take from the system.img?
I'm wondering the same thing. How do you know which blobs to pull in the first place when you're trying to build up the first rom?
There will be some dlopen errors for missing files in the logcat. After resolving them, it's mainly trial and error
Believe it or not, there is a method to this, and it requires some trial and error and a good sense of knowing what android needs to boot. If you look at the start up classpath and are just generally aware that the modem/network connection and filesystem utils need to be executed first (though for some reason binder and zygote can't start them themselves, despite the fact they are to running under init, but whatevs) so after bootloader hands off to kernel, you can go through the ramdisk and make sure all the on boot, on init on fs related libs/binaries are present. If you use a qcom device, just assume any lib or binary that starts with "libq" or even just the letter "q" is proprietary and required. Qcom is a bit full of themselves (ironic were talking about cm here) but anyways then there's the rild/crypto/fs libs and binaries. rngd, rmt_storage, rild daemons and anything that starts drmsever or netd will be required as well.
You can get significant hints from boot logs as well.
Aside from that, just keep note of what isn't produced by the aosp tree yet is present on the devices stock system, then determine how important it looks for android to able to start up