Jerry- First of all, this guide is really phenomenal. No joke. You really have a
true knack for walking a beginner's mind through a seemingly chaotic procedure, and making it less intimidating by speaking direct, and on-level with the reader.(as opposed to some Internet tutorials, where an author is clearly writing in a format that serves their own ego, and couldn't care less how it might translate to someone a bit less savvy.)........ So thanks for the careful work and dedication you put in this.
To get to my point...I actually have a question.(this might shock those who know me around here, or from XDA, due to the fact that I have never really,
formally asked for help, lol.)
I have successfully compiled ICS for the Crespo4g, and it built correctly, I believe.. however, I have a couple nagging "issues". The first and most important question I have is: The ota package that I built is very much like a CyanogenMod ota-flashable, in that it has included only the core OS/kernel.. Theres no Gapps of
any kind, not even the market. Now, this isn't shocking to me, as I'm obviously familiar with the agreement between Google and CyanogenMod. What confuses me, is there doesn't appear to be an instruction set anywhere that explains how to compile a Gapps package separately,
or how to compile and merge the official apks with the base OS package. I tried flashing the newest Gapps, however the market fails every time I attempt to update any google app, as well as most non-google apps too. If I had to guess, I'd assume that it's because the signatures are different between the Gapps and my personally signed build, therefore causing conflict. If thats the case..then we're brought back to my main question: Where do I get
official google apks to merge into my build, and how can I do it?
Second question is small
...My core build has everything working flawlessly within it, except for one stupid thing. The keyboard. Its spelling correction/suggestion setting does not work, no matter what. Everything is underlined in red, as if it were misspelled. I remember this being an issue around the time Kwiboo/Koush started pumping out their early, unofficial builds of ICS,and I think it was resolved pretty quickly. You have a Nexus S Jerry, and you ran the early ICS builds; Do you have any insight on this possibly being an error in my compiling, or do you think this is a native issue residing within the ICS source code? If anyone else has built AOSP ICS, and has had this problem, but fixed it, please give me a shout-out on how you achieved thats.
And
those are my two gigantic questions....Any insight offered would be immensely appreciated! Thanks for reading my book!
Facebook
Twitter
Instagram