I'm working on my first android build for toro using the CM10 jellybean branch. I'm able to get everything to build, including the four proprietary binaries provided by AOSP, but am obviously missing the camera, gps, and nfc binaries which AOSP does not distribute.
My question is, what are other ROM developers using for these? Will the 4.0.4 binaries for this hardware work? What about the binaries from maguro?
Thanks in advance.
Related
First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Sent from my HTC Vision using XDA App
thrice43 said:
First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Click to expand...
Click to collapse
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Moved to Q&A
dhkr123 said:
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Click to expand...
Click to collapse
Well, I pulled the files from AOSP git but I have no other build/make files to go off of other than Cyanogen's. How would I know what lines to comment out and what lines to keep?
Sent from my HTC Vision using XDA App
I think you will have more to do to get something built from scratch. From a software engineering perspective you will have to use some code that was built to bridge between the hardware (G2 specific) and the stock operating system. This is a classic UNIX paradigm - the source is portable, but you have to have the interfaces to the hardware to hook in and create a complete set.
I'm finding that my phone has a Froyo WiFi calling app, and this is being used under Gingerbread because I'm using CM7.0.3 (Gingerbread based ROM). Not a clean combination.
I'm working from the CM source tree... Take a look here: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vision
Tommy.
Hi,
I started seeing 4.0.4 available in some ROMS. I have been running 4.03 on AOKP for the past couple weeks, but where is the official release of 4.03 ??
I monitor this site every day: http://code.google.com/android/nexus/images.html
Why dows people flashing 4.04 and 4.03 here and there but Google dont release officially those builds??
Thanks.
4.0.4 isn't in any ROMs, modaco is a hybrid and CDMA might have some deodexed versions of 4.0.4
4.0.3 is tagged in AOSP, so we can build that. The only 4.0.4 ROMs will be for CDMA Galaxy Nexus AFAIK, and there can't be a source built 4.0.4 ROM until it is tagged and released in the AOSP tree.
4.0.3 was released on the Nexus S and found to have a few issues so it's been pulled. Because of that, it would appear Google thought twice about releasing it on their flagship dev phone so are holding off until they get a nice build - rumoured to be 4.0.5 but nothing confirmed so far
The latest OTA update is up to 4.02 only. All other versions are unofficial leaked/custom ROMs.
MilkPudding said:
The latest OTA update is up to 4.02 only. All other versions are unofficial leaked/custom ROMs.
Click to expand...
Click to collapse
4.0.3 isn't leaked. It's in AOSP repo, yes it's in custom ROMs but you can compile a AOSP 4.0.3 only version as if it was a OTA.
just to underline what's already been said;
you can build 4.0.3 tag from aosp;
you can also build from aosp master branch: this is the bleeding edge branch of aosp. in other words, in terms of the android dev tree, master has all the latest fixes (and "features") of ics.
Sorry to come in all noob and stuff. Just a quick one, what's AOSP?? = /
Helmet321 said:
Sorry to come in all noon and stuff. Just a quick one, what's AOSP?? = /
Click to expand...
Click to collapse
Android Open Source Project.
http://lmgtfy.com/?q=What+is+AOSP?#
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
Hey all, new to here but not new to android. I wanted to try to build AOSP (not CM10, or AOKP) from source so that I can have a pure Google AOSP ROM to play around with (never built from source before) . I've gotten the source for 4.2.1 from Google source and everything is setup in my virtual Ubuntu machine, but I don't know what to do about the proprietary binaries for the 747.
Can someone tell me which files I would need from say, Cm10's github and where to put them?
Thanks.
Sent from my SGH-I747 using xda premium
Bump
anyone?
There is a well known issue with wpa_supplicant on 4.2.2 JB being broken for LEAP (802.11X Enterprise) authentication.
There is a development version of wpa_supplicant available (https://android.googlesource.com/platform/external/wpa_supplicant_8/) that solves the issue however recent patches from there didn't yet go into Google's release.
AOSP build from CM doesn't seam to be usable on non-AOSP ROMs and moreover I'm not sure it solves the issue (if it takes official Google release code then it doesn't).
If anyone could compile the code (https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master) for non-AOSP builds (preferably ARHD ROM), it would be greatly appreciated.