[Q] Help building CM for Nook HD+ - Nook HD, HD+ Q&A, Help & Troubleshooting

I've been running CM on my HD+ for the last few months and it's been great. I'm working on making some modifications to the VM and to the kernel and it requires building CM from source. I've already done this with several other devices and have had only minor problems. I'm following the instructions and it can't build. I get the following error:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140120-UNOFFICIAL-ovation
TARGET_PRODUCT=cm_ovation
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.7.10-1.16-desktop-x86_64-with-SuSE-12.3-x86_64
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/home/david/Android/system/out
============================================
make: *** /.config: Is a directory. Stop.
I've searched and haven't found a solution but It seems like I'm missing a manifest or something. I'm wondering if this is missing from 10.2 and I should just try building 11 or if there's a way I can build from source.
Thanks to anyone who can help!

No experience building CM but it looks like maybe /.config instead of ./config got invoked?
Sent from HD+ MAG2GA CM 11 from SD

Did you follow this guide? -> http://wiki.cyanogenmod.org/w/Build_for_ovation (repo init for cm11 instead if cm11 is desired)
Its probably just an error that you made. I don't remember seeing it before.
Edit it doesn't like /.config. That much is obvious. So try to rename or move it or fix your problem to avoid it. (if its ~/.config be careful as that is an important dir.)
There is a .config in /out during building process which is the kernel defconfig file. There is also ~/.config. And that's all I know about that. Look around for .config or google your error with "/.config;" removed and see how the "make: *** is a directory. stop" plain version helps you.

I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.

ddpruitt said:
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
Click to expand...
Click to collapse
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Some other thoughts based on testing:
You get the correct manifest, etc. with the git and repo sync so again its not with what your getting. That all will build it without that weird error.
If there's no .config file in android/system/out/target/product/ovation/obj/KERNEL_OBJ/ then its because it didn't do enough to put one there yet. That shouldn't be the issue as it will rename a .config dir and continue or if it can't then have a different error.
Did you try make clean or make clobber and try building again?

sandsofmyst said:
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Click to expand...
Click to collapse
I had someone else try it on an Ubuntu machine and it has the same issue. I'll try to get the verygreen repos instead of the official CM ones see if that helps

Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.

sandsofmyst said:
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
Click to expand...
Click to collapse
You're an absolute genius. For some reason I did have a /.config directory, I never even though of looking in the root directories. Must be some strange KDE issue. I deleted it and build kicked off and it's rolling fine now.

Related

Building CM6

Maybe we can get a group knowledge base going, I'm attempting to build CM6 right now. The idea is to help out with Vibrant porting, but I'm getting stuck and thought you guys might have some hints. If I can get it going, I'll update the wiki or create one somewhere else for Vibrant specific stuff.
So, right now my build system is 64-bit Ubuntu 9.04. I can switch, it looks like it might be better to be on a 32-bit setup, so there's one option.
The basic path to where I am now, following basic directions from here: http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Code:
sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
sudo aptitude install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
curl http://android.git.kernel.org/repo >~/bin/repo
chmod a+x ~/bin/repo
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(Path modified to match my local path)
repo init -u git://github.com/CyanogenMod/android.git -b froyo
repo sync
source build/envsetup.sh
make -j4 adb
This results in a segfault....
Code:
host Executable: adb (out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb)
true
Install: out/host/linux-x86/bin/adb
make: *** [out/host/linux-x86/bin/adb] Segmentation fault (core dumped)
Using "lunch" and selecting a target, then "make clean" gives me the same error building adb. Attempting to build the ROM also gives me a segfault, so at least I'm consistent. It always seems to be on an "Install" step, if that helps.
If you get it to compile be sure to post, I'd love to start helping I just lack motivation and free time... And knowledge around Android, but I'm working on that piece
ttabbal said:
Maybe we can get a group knowledge base going, I'm attempting to build CM6 right now. The idea is to help out with Vibrant porting, but I'm getting stuck and thought you guys might have some hints. If I can get it going, I'll update the wiki or create one somewhere else for Vibrant specific stuff.
So, right now my build system is 64-bit Ubuntu 9.04. I can switch, it looks like it might be better to be on a 32-bit setup, so there's one option.
The basic path to where I am now, following basic directions from here: http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Code:
sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
sudo aptitude install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
curl http://android.git.kernel.org/repo >~/bin/repo
chmod a+x ~/bin/repo
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(Path modified to match my local path)
repo init -u git://github.com/CyanogenMod/android.git -b froyo
repo sync
source build/envsetup.sh
make -j4 adb
This results in a segfault....
Code:
host Executable: adb (out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb)
true
Install: out/host/linux-x86/bin/adb
make: *** [out/host/linux-x86/bin/adb] Segmentation fault (core dumped)
Using "lunch" and selecting a target, then "make clean" gives me the same error building adb. Attempting to build the ROM also gives me a segfault, so at least I'm consistent. It always seems to be on an "Install" step, if that helps.
Click to expand...
Click to collapse
This usually meanings that there is a memory management issue but im no dev hope this helps
Now if we had others posting about what they have done.... hint...
OK, I know there aren't a ton of us messing with things at this level. Hopefully someone else has seen this. I'll try to install a 32-bit Ubuntu 10.whatever tonight and see if that helps. It is possible my issues are being caused by the 32-bit compatibility libraries or similar.
ttabbal said:
Now if we had others posting about what they have done.... hint...
OK, I know there aren't a ton of us messing with things at this level. Hopefully someone else has seen this. I'll try to install a 32-bit Ubuntu 10.whatever tonight and see if that helps. It is possible my issues are being caused by the 32-bit compatibility libraries or similar.
Click to expand...
Click to collapse
I just installed ubuntu32, and am going through the repo sync, as soon as that finishes, I'll pack up and head home and finish there, hopefully it compiles on 32bit. I'll post back as soon as i know.
I've considered contacting them that way, I was hoping the community would be interested in getting a few more devs going. I'm downloading the Ubuntu 32-bit ISO now. If you want to send them a message, cool. I'll fool with things a bit more and if I still can't get anywhere, I'll see if I can get in with thouse guys. If I do get it working, I'll try to document everything that's not covered elsewhere. I just hate to take time away from their work to help out a newb.
If you can't build, you can't contribute. The Android build system is somewhat custom and weird, so it can be off-putting to people that would be interested in helping. More people hopefully means we can get more done.
ttabal, seg fault during a "make" usually means it tried to access something that wasn't there. Make sure you have all dependencies installed. Someone said seg fault has to do with memory management ... yeah, only when running an app. When building (aka "make"), there are a lot of things being linked and each thing has a ton of dependencies and that continues recursively ... it's why I hated working with Unix back in the day. You change one thing, you have to change everything and its mother.
Still, I have been frustrated at the lack of progress recently that I am toying with the idea of jumping back in the pool and building things myself. I wish one of the more experienced folks here would offer a primer. I know what they're afraid of though ... every noob coming back with a million questions, like, "what's apt-get?" or "what's a make file?".
Yeah, maybe we should start up an invite-only dev forum and only allow public read-only access to a wiki or something so we can share with everyone. I'd love to be more open, but I do see why the big devs don't do their dev conversations here.
I did install the depandancies they listed on the Cyanogen Wiki, but it is possible they need something new that isn't listed. Hopefully someone can help us out. It's also possible my versions of the libraries need updating as I am on an older build of Ubuntu. I have another machine I can install the newer version on, and I'll try that first. May as well make sure I'm doing everything I can. I just can't install on the other machine as it's a production server for my home system. The wife gets mad if I break the TV server.
I know you are attempting to build the source, and I'm sorry I cannot help you with that. I just wanted to put a link up here for people that are getting inspired by you and are considering contributing to the rom development community.
http://forum.xda-developers.com/showthread.php?t=667298
It's a post by cyanogen about how you should go about getting in to rom development.
I managed to get it to build for Dream/Sapphire by first doing
Code:
#repo init -u git://android.git.kernel.org/platform/manifest.git
THEN
Code:
#repo init -u git://github.com/CyanogenMod/android.git -b froyo
#repo sync
#source build/envsetup.sh
on 64 bit Ubuntu. Did a bit more fidgeting after that to get it working, I'll see if
I can figure it out next time I'm home.
Interesting. I'll try pulling the aosp manifest first. Perhaps that will help. Did you do a repo sync on the aosp or just init?
There was a core dump, so if you have the core.dump file in the same directory where you ran "make" run strings against it, it might tell you what's segfaulted on you.
I got past make adb on Ubuntu 10.04 64-bit. Compile has been going for quite some time now. I haven't tried building a kernel yet.
Will be attempting a build on Monday with my secondary box at work running ubuntu. I have a knack for jury rigging things to work and more than willing to contribute, despite lacking the experience. For reference, you could try to converse with then on irc, freenode.net server, in #cyanogenmod or #sgs_dev, a bit more of a direct line to #teamdouche
Sent from my SGH-T959 using XDA App
ttabbal said:
The G1 was easy to dev for by the time 2.2 came out, and CM was already building on that platform. It's a lot easier to update an existing setup than trying to start on a new platform.
And proof-read, swype isn't perfect.
Click to expand...
Click to collapse
From what I understand (witch is very little) the G1 drivers have all been reverse engineered for some time and building it from source is incredibly easy at this point. While the Galaxy S is incredibly hard to develop for because all the drivers are wrapped up in all the kernel mods Samsung did, even though they open sourced much of it, its hard to unravel the code.
Build completed. Only issues I ran into:
1) repo sync didn't complete at first because I had never talked to android.git.kernel.org. Running "repo init -u git://android.git.kernel.org/platform/manifest.git" as anomalous3 said fixed that.
2) make complained about not being able to find RomManager.apk, so I went into vendor/cyanogen and ran get-rommanager. While I was in there i ran get-google-files and extract-google-files as well, but not sure if that was necessary.
At this point I'm not sure of the kernel requirements for attempting to run this system.img. Until I learn a bit more about the kernel and ramdisk I'm hesitant to do anything with this.
elderberry said:
Build completed. Only issues I ran into:
1) repo sync didn't complete at first because I had never talked to android.git.kernel.org. Running "repo init -u git://android.git.kernel.org/platform/manifest.git" as anomalous3 said fixed that.
2) make complained about not being able to find RomManager.apk, so I went into vendor/cyanogen and ran get-rommanager. While I was in there i ran get-google-files and extract-google-files as well, but not sure if that was necessary.
At this point I'm not sure of the kernel requirements for attempting to run this system.img. Until I learn a bit more about the kernel and ramdisk I'm hesitant to do anything with this.
Click to expand...
Click to collapse
Thanks! I'm running repo sync after the kernel.org init now. I'll see if that gets me building. I don't suggest installing anything you build yet, I want to see if we can get a couple people building before we take that step. Though it looks like we can create some nice update.zips now that flash the kernel and such. Very cool.
Anyone know how to replace parts of a local git with your own repo? I would like to clone my fork of wesgarner's vibrant tree into the main tree so I can do commits and such without messing with anyone else's stuff. git rebase? I'm a little new to git, I've only ever used it for basic stuff that SVN can do.
Looks like the sync is going to take a bit for me. Damn. I'll install the latest Ubuntu in a VM while I'm waiting on it. Who do I have to kill to get FIOS in Utah?
Hmmm... Still no joy for me. Must have done something wrong I guess. Build still segfaults and I don't get a coredump. Weird.
Thanks for the contact info for teamdouche, I'm trying to avoid bothering them until I at least have a working build. This isn't the sort of level one should bother them about IMO.
Looks like you guys are talking to wes and the others
If you guys get it working. I have a build env setup + a build bot. Just let me know
i'm installing the dev support packages right now. i'm worried, though. how much space are we looking at? my linux partition is only 8gb. so i may have to modify some things so it's all on my raid storage.

[Q] A few AOSP compile questions

I am trying to compile a clean AOSP ROM for my O2X, there is a few things I am having trouble with.
1. What is the significance of overriding the build prop with the following:
Code:
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=lge_star BUILD_ID=FRG83G BUILD_DISPLAY_ID=GRJ22 BUILD_FINGERPRINT=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys PRIVATE_BUILD_DESC="star-user 2.2.2 FRG83G 2ED2ADCFFC release-keys"
Clearly its used for something, else CM7 wouldn't be doing it.
2. When I try to boot the compiled system (using either CM or EternityProject kernel), it simply stops at the LG logo, no logcat, no dmsg, nothing and after a while it reboots. What could I be missing?
I am using the init.rc from the CM7 p990 source, do I need some extra modules for it to boot? (I have added busybox and bash)
Tips on how I could debug the issue would be appreciated (any additional logs?).
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
fallout0 said:
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
Click to expand...
Click to collapse
Yea I am trying to create a device tree that will make AOSP compile and run. Its compiling just fine and it uses bits from the CyanogenMod device tree. The problem is that it wont run, it gives me no logcat output at all.
Here is the p990.mk:
http://pastebin.com/SxUZZDau
The boardconfig and proprietaries are identical to CM7. (Merged star-common and p990 configs since I have no use for p999)
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
fallout0 said:
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
Click to expand...
Click to collapse
Same problem, no dmsg or logcat.
Im gonna start from scratch now
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
L10nH34Rt said:
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
Click to expand...
Click to collapse
That would make it rather useless
KernelCrap said:
Same problem, no dmsg or logcat.
Im gonna start from scratch now
Click to expand...
Click to collapse
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
fallout0 said:
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
Click to expand...
Click to collapse
Im gonna try to build using the 2.3.3 gingerbread-tegra source from nvidia
EDIT: Same problem, when running something i get "Segmentation fault". I am using the gingerbread-tegra source from nvidia :S
I have the following in BoardConfig.mk:
TARGET_HAVE_TEGRA_ERRATA_657451 := true
Busybox is working fine though :/
Shouldn't the source from nvidia allow me to execute the compiled binaries without giving segmentation fault?
The funny thing is that busybox is working, and I can access dmesg through busybox.
KernelCrap said:
That would make it rather useless
Click to expand...
Click to collapse
It wouldn't if you couldn't access the market now would it?
L10nH34Rt said:
It wouldn't if you couldn't access the market now would it?
Click to expand...
Click to collapse
I'd rather have it boot atm.
Still same problem even though I have moved to the gingerbread-tegra source
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
L10nH34Rt said:
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
Click to expand...
Click to collapse
For starters I don't care about camera or hdmi, I want a clean AOSP rom - CM is great, but it includes too many extra features for my taste.
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Hi guys, where i can find sources from nvidia ? I only found the kernel git...
Thank's
fallout0 said:
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Click to expand...
Click to collapse
I am sure and I am using the leaked libraries too. Anything else i can try?
Sent from my Optimus 2X using XDA App
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
fallout0 said:
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
Click to expand...
Click to collapse
Will try that once I get home later today
I commented it out the following places:
Code:
./bionic/libc/Android.mk:497: ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
./bionic/linker/Android.mk:46:ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
Still not booting, now the error is (from logcat):
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
But /system/bin/sh does exists, with the following permissions (also tried with chmod 777):
Code:
-rwxr-xr-x 1 root shell 82840 sh
If I do adb shell when in recovery and executes the binary files, they all seg fault (except for busybox) :/
Here is my BoardConfig.mk:
http://pastebin.com/ZsmJp0v1

[Q] ICS on a similar phone

Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.
jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.
whoshotjr2006 said:
jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.
Click to expand...
Click to collapse
Thanks for the tip...I have sent a message on github to mattcrystal so maybe he will respond if he has time.
bads3ctor said:
Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.
Click to expand...
Click to collapse
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5
MattCrystal said:
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5
Click to expand...
Click to collapse
Thanks for posting. ICS on the Samsung Intercept is up and running.
Do me a favor and click thanks perhaps and your welcome
Sent from my HTX Zero Hero Sense 3.5
no wip/dev thread on the intercept forums yet? that would be awesome, i a know a few with intercepts that would love to see ics on their phones. op you should think about making it happen, at least posting a guide/howto.

[Q] Build instruction for Xdandroid for the X1

Hi
I am working on the Kovsky kernel at the moment, but would really like to be able to make changes to the Andoid part of the system as well. Does anyone have build instructions for the XDAndroid system?
I have done cross compiling to various platforms before, so the part I need is:
*What sources to download
*What commands to run
As I didn't get any feedback I have decided to figure it out for myself and publish as I go along:
To get the sources follow the instructions at:
xdandroid.com/wiki/Getting_the_Source
mkdir ~/xdandroid
cd ~/xdandroid
repo init -u git://gitorious.org/xdandroid/manifest.git -b gingerbread
repo sync
Now I have lots of code, and the next step is found at:
xdandroid.com/wiki/Build_Configuration
What I need is a "buildspec.mk" file. If anyone has one that has been used for NAND compiles feel free to share
I have now realized that all the ROMS have been compiled based on CyanogenMod7 source that have separate repositories from xdandroid.
Sp3dev created a repo for some of the kovsky files he used in november last year at: https://github.com/astarasikov/device_kovsky
Next up is integrating them into the cyanogen tree and creating vendor files based on leo/dream
I am starting to piece everything together now. I am still not able to compile it, but I am getting closer:
Here are some steps that have only been tested on an Ubuntu system:
1. Follow the steps here http://wiki.cyanogenmod.com/wiki/HTC_Dream_&_Magic:_Compile_CyanogenMod_(Linux) down to "Install the Repository"
Code:
# 2. Install repository by running (This will take several hours):
cd ~/android/system/
repo init -u git://github.com/CoolRunnerII/android.git -b gb-release-7.2
repo sync
# 3. get the propriatary files from a running phone connected by usb by running. You may need root to do this:
cd ~/android/system/device/htc/kovsky/
./extract-files.sh
# 4. copy vendor file to correct place by running:
cp device/htc/kovsky/cyanogen_kovsky.mk vendor/cyanogen/products
# 5. Get Rom-manager by running
~/android/system/vendor/cyanogen/get-rommanager
# 6. sync repo again by running:
cd ~/android/system/
repo sync
# 7. get ready for compile with:
. build/envsetup.sh
lunch cyanogen_kovsky-eng
# 8. Start compile with:
make
Great news.Hope you can finish it!
Compile now runs to the end
On my system the compile runs to the end when doing the steps above. I have not started packageing it yet, but everything seems to compile correctly.
The other guides recoment running "make bacon" witch are supposed to create a "over the air" OTA package. This crashes when I try it. If anyone has some good information as to how the final packages is supposed to be please share. all the other CM7 roms have folder in the zip fil called META-INF that contain the update script. The .zip-file created by running make does not.
I just added Alex's fork of the gps library from xdandroid to the manifest.
If someone could try the steps above and report to me wether it works on their system or not I would be very thankfull. My goal is to create a streamlined rom build directly from source. That way getting the last issues out of the way should be possible even without guys like Alex working on it.
CoolrunnerII said:
I just added Alex's fork of the gps library from xdandroid to the manifest.
If someone could try the steps above and report to me wether it works on their system or not I would be very thankfull. My goal is to create a streamlined rom build directly from source. That way getting the last issues out of the way should be possible even without guys like Alex working on it.
Click to expand...
Click to collapse
very very nice job!!!!!! currently downloading kovsky repos to check if i can build but it will take hours with slow connection and i've little time cause of exams...
btw: if someone has problems with syncing cause of slow internet repo sync -f is a nice option
EDIT:
in time i'm going to improve cwm recovery (currently porting cwm-touch to another device...)
EDIT2: any chance to add wpa repo to existing working directory?
btw: you could also use a local_manifest.xml for the additional repos... (just if you don't already know ) (would be more official???)
i can't test cause i don't know how to add wpa repo
this should be in android development section... you posted here cause of limited posts right? btw thanks a lot for missed call fix
Yes I posted here due to limited rigths.
I'll start a new thread in the developer section now that I can
Cool runner the rhodium android development forum has a 7.2 build but I don't know how to make work for our device. I pm the maker he said I can use his rom

[Q] Repo init git error

Ok so I've only found this one other time on and the solution was taken down. I am currently building BlissPop LP 5.1 for the LG L90 and when I run the command "repo init -u https://github.com/TeamBliss-LP/android.git -b lp5.1" All I get when I hit enter is the terminal goes down a line and gets stuck on "Get https://gerrit.googlesource.com/git-repo/clone.bundle". I don't understand why the repo won't keep going or why it's just stuck there. I've tried deleting my working folder and starting from scratch and this does not work. If you have any idea how to fix this issue I would greatly appreciate the help! The sooner I get done with Blisspop the sooner I can build more ROMs. Thanks!
Screenshot: https://drive.google.com/file/d/0B_s...ew?usp=sharing
it's something on your side - for me init works properly
judas1977 said:
it's something on your side - for me init works properly
Click to expand...
Click to collapse
I know but idk what it could be. I've already deleted my repo and reinstalled it and all that. So I'm kinda stuck :/ So I figured a few more opinions couldn't hurt.
And what about initializing other ROMs repos? Get stuck too?
judas1977 said:
And what about initializing other ROMs repos? Get stuck too?
Click to expand...
Click to collapse
Yes
Maybe you try to reproduce all steps made during compilation environment preparation. I'm out of ideas

Categories

Resources