yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jschill31:
OK, I will try it again... It has been building and the files have flashed fine for a couple of weeks now. Not sure why all of a sudden I would have a gremlin but I do appreciate the pics! :good: For me at least the last build that flashes without any loops was 8/2/12. BTW, I pulled from CM9 and have not changed it since I started playing with CM10. I would say at least a dozen builds with no issues, it wasn't until I did a clobber and git reset to pull the new wifi stuff that I hit a wall.

Cheers

---------- Post added at 05:25 PM ---------- Previous post was at 05:10 PM ----------

Hello,

I have been traveling with no access to adb...I should be home tonight to see if I can pull something. It could just be poor timing on when I did a clobber and repo sync, looks like one other poster had a non-booter the other day.

OK, so this is odd... My adb just sits there and says "waiting for device" and no logcat is generated??? As you stated it should kick out something since I am getting the boot animation for second. The cm9 arrow completes a circle then the unit reboots. It does this 3 times and then kicks itself into recovery. I reverted back to an earlier build to verify adb is indeed working. I got nothing on this one, never seen anything like it. Maybe my Nook is on the outs? It reminds me of my Hero when I would try to overclock it too high, has there been any voltage or power changes in the past week?

Cheers
[Nook Color Android Development] jschill31:
Hello,

Not sure if anyone reminded you or not but here goes...

Cheers:)
[Nook Color Android Development] leapinlar:
With your description I could not at first understand why after 3 fails it was booting to recovery. I think I understand now. It is the 8 failed boot reset trying to kick in. It is trying to boot to stock recovery to start the reset, but your stock recovery is replaced by CWM so it goes there. Then when you exit CWM, it resets the recovery flag and the next boot tries the ROM again. Why 3 fails instead of 8, I don't understand.

I know this does not help you on getting your ROM to boot, but at least it explains why you end up in recovery.
[Nook Color Android Development] jschill31:
Hello,

Well it gets even stranger. I built again last night and tried again today to pull a logcat when the unit fails to boot. I have now tried (3) different PC's that I know I have adb set up correctly on and none of them will give me a logcat on this thing? I did get a partial last night but it was kinda worthless, it locked up after some omap3 reference to camera? I know it was not a complete log since the Nook continued into the boot animation for a split second. This was the only time I got anything from logcat out of at least a dozen tries. I would say it is my Nook and yet my older builds flash fine as well as restore. My understanding of make clobber and make clean is that they just remove the OUT folder and do not modify anything else...is this correct? Since everyone confirms that there hasn't been any kernel changes I am at a loss.

bummed...
[Nook Color Android Development] captfoss:
I'm currently running my first build using the latest andbot build environment after spending a few days to actually get Linux setup properly (and by properly, I mean like I'm used to...). Exciting stuff.

Made me wonder... is this andbot environment suitable for building CM10 for other devices (Specifically, the Galaxy S3 on Sprint) or is it only suitable for producing a CM10 build for the encore?
[Nook Color Android Development] fattire:
I'm not terribly familiar with andbot, but my guess is that if you can build for encore, you can build for anything. The only thing that needs to change is--

So, in the base directory for the repository you've got a directory structure that looks something like this:

abi bootable cts device frameworks kernel Makefile packages prebuilts test

android build dalvik docs gdk libcore ndk pdk sdk vendor

bionic build.prop development external hardware libnativehelper out prebuilt system

Inside these directories is all the source code you need for building android. The result goes in the "out" directory above.

Most of the source code is identical for all the different devices, but there are two special directories that are especially unique for any particular device. The first is called "device", and the second is called "vendor".

Both the device and vendor folders follow the same format:

device/manufacturer/device_model_codename

vendor/manufacturer/device_model_codename

The device folder has special build instructions, settings, source files, firmware, and other files particular to any certain device. When someone does a port for a new device, this is generally where the unique items for that phone or tablet or whatever goes.

The vendor/*/devicename folder contains the "proprietary blobs"-- for some reason generally non-redistributable (perhaps merely because the license has not been fully determined yet) files such as special drivers, prebuilt libraries, or firmware that typically are expected to be extracted (backed up) from an original stock device to then be re-added back with the build to the original device. These prop files are kept separate from the open-sourced portions of the build in this vendor tree. A caveat-- some files may actually be redistributable but remain in the vendor folder for legacy reasons-- many if not all of the OMAP blobs are actually provided by TI to be redistributed, but for whatever reason some device maintainers may prefer that certain parts be extracted or pulled from an original device. Many devices have an extract-files.sh script that will automatically back up the files from your device (via adb) and put them in the right place in the vendor folder.

So if you have a valid device/*/* set up for your device and it has all the files cm10 requires, it should work. If some files, such as cm.mk, are missing-- take a look at similar devices (other devices that use the same architecture) and you might be able to figure out what's missing. That's what I did for CM7 on the nook in the first place...
[Nook Color Android Development] captfoss:
Alright, thanks. That makes some sense, and I'm sure it'll make some more sense when I'm beyond the copy & paste phase of getting this working. Eventually I'd like to (1) be able to build (2) be able to build without andbot (3) have a clue what I'm doing.

What I take away from all of that at this point is (a) you can do builds for multiple devices from the same build area without them colliding (b) andbot's "convenience" functions are going to greatly hinder my understanding of the build process.

Ultimately, I guess I'll be better off if I get rid of andbot and get my system configured to allow me to build like a big kid. :)
[Nook Color Android Development] mateorod:
Actually, from what I understand, andbot is only for encore. I do know inportb is considering expanding to all devices. Now, you could configure it to make for a different device, but I am guessing most won't.

It adds a bunch of user friendly things, but successfully building with andbot can really teach you to build. But the package setup removes all of the completely maddening common mistakes that new builders encounter; i.e. forgetting to install a package, adb configuring, java path etc. It takes care of all the stuff you are usually expected to bring to compiling software and let's you just build.

Edit

Krylon360- thanks for the tip about the boot classpath in init.rc. That was the missing piece. My patched build boots and runs perfectly now, thanks.
[Nook Color Android Development] riverzhou:
MTK's MT6575 will on market this month, it has dual A9 CPU and SGX 531 Ultra GPU.

Those MT6575 phones are released with Android ICS.

Maybe, we can get those close source drivers from those phones.
[Nook Color Android Development] lekofraggle:
Hey all,

This is great. A few days ago, Fattire posted a note directed toward krylon.

<quote>Don't forget to enable hwcomposer.omap3 etc in device make.</quote>

Is this something we all should do as we troubleshoot?

If so, do we just edit the line

hwcomposer.omap4

To

hwcomposer.omap3

Am I poking through the wrong make file?

Thank you again.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] tomsawyer14:
As of my latest build a few hours ago, charging from AC appears to be working again. Wake lock issue still occurs when on AC tho. Could having ADB enabled when connected to USB have something to do with this not happening when connected to my laptop?
[Nook Color Android Development] msaraiva:
I don't know if that's what you mean, but the device isn't supposed to sleep when on AC, that's why this wakelock exists.
[Nook Color Android Development] krylon360:
gonna be pushing some changes to CM here within the next day or so. 32bit framebuffer performance increase. and some other neat things that I need to do a little more debugging on.
[Nook Color Android Development] riverzhou:
I get device fold from git://github.com/fat-tire/android_device_bn_encore.git . checkout jellybean branch ,

and get kernel from git://github.com/keyodi/ti-omap-encore-kernel3.git , checkout encore-omap3-3 branch .

Built rom and flashed.

NC booted but got black screen.

root@ubuntu:/river/cm10/device/bn/encore# modinfo prebuilt/GFX/system/lib/modules/omaplfb.ko

filename: prebuilt/GFX/system/lib/modules/omaplfb.ko

license: GPL

author: Imagination Technologies Ltd. <gpl-support@imgtec.com>

depends: pvrsrvkm

vermagic: 3.1.0-g70d02de mod_unload modversions ARMv7

info in dmesg:

<4>pvrsrvkm: disagrees about version of symbol module_layout

The omaplfb.ko and pvrsrvkm.ko are built for 3.1 kernel . What can I do?

---------- Post added at 01:34 AM ---------- Previous post was at 01:30 AM ----------

How about you now?

Booted or not?

---------- Post added at 01:53 AM ---------- Previous post was at 01:34 AM ----------

more infomation:

adb logcat

D/AndroidRuntime( 656): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<

D/AndroidRuntime( 656): CheckJNI is OFF

I/SurfaceFlinger( 655): SurfaceFlinger is starting

I/SurfaceFlinger( 655): use dithering

I/SurfaceFlinger( 655): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

E/FramebufferNativeWindow( 655): couldn't open framebuffer HAL (No such device)

E/SurfaceFlinger( 655): Display subsystem failed to initialize. check logs. exiting...

I/mediaserver( 657): ServiceManager: 0x40cedd80

I/Netd ( 703): Netd 1.0 starting

I/SurfaceFlinger( 704): SurfaceFlinger is starting

I/SurfaceFlinger( 704): use dithering

I/SurfaceFlinger( 704): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

E/FramebufferNativeWindow( 704): couldn't open framebuffer HAL (No such device)

D/AndroidRuntime( 705):

D/AndroidRuntime( 705): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<

/dev/graphic/fb0 and /dev/pvrsrvkm are exist.

And when I cat "111111111111111111111111111111" > /dev/graphic/fb0 , I can see something on screen.

And then, I check the config of kernel , pvrsrvkm and omaplfb are already built in kernel .
[Nook Color Android Development] eyeballer:
You also need the hw/ti/omap3 and hw/ti/wlan from fattire's git, replace the cm ones.

Easiest way is to put http://pastebin.com/vZFKdc8m in .repo/local_manifest.xml
[Nook Color Android Development] sakisa950:
http://xdaforums.com/wiki/Wakelocks idk im no dev but this may help
[Nook Color Android Development] jschill31:
Nothings been booting for me on my past 4 builds. Builds fine with no errors but bootloops every time. Was going to replace my device folder tonight in case something got hosed but I am stuck in the emergency room now...kidney stones suck! I think I have narrowed my issue down to omap4 stuff. I am going to try manually changing a couple of things. Need more morphine first...

Cheers

EVO LTE
[Nook Color Android Development] riverzhou:
My local_manifest.xml has fattire's ti_omap3 and I use CM wlan.

But the problem is not wlan not. It's graphic system.

I took those vendor files from stock rom(.zip) using unzip-files.sh .

Is it the reason black screen?
[Nook Color Android Development] riverzhou:
After all, I solved the problem.

I download a CM9 rom and get vendor files from it using unzip-files.sh

It's OK now.

CM10 is nice but lag .
[Nook Color Android Development] eyeballer:
Edit: oops, I see you fixed it :)
[Nook Color Android Development] csrabear:
I have successfully built cm10 and it boots fine. So far the only problem is the browser. It closes after about 4 seconds. No problem connecting to any web sites. It just closes shortly after it opens.
[Nook Color Android Development] riverzhou:
Rebuilt CM10. It's as smooth as CM9 now, just no sound.
[Nook Color Android Development] cybertimber2007:
Hmm... I wonder if it is similar to the google location issue we had back in CM7 or CM9. Any chance you can get into the settings and disable location sharing and see if that helps?

I really need to sit down and make a build system.
[Nook Color Android Development] fattire:
Left this for you on IRC, but jic I'll put it here too.. whenI was buildng hwc I had a similar situation-- are you building dsscomp? You need to enable it in DEFCONFIG + change the Kconfig so that SGXSOMETHINGOROTHER isn't one of the dependencies for dsscomp... it will build and you'll see it in /sys/...
[Nook Color Android Development] lekofraggle:
Hello all,

After many successful builds, I am now getting the dreaded Java memory issue referenced in the tutorial.

I tried using xmx value as low as 128 and it still would not build.

I even tried to increase my Java heap size to no avail.

I am on Ubuntu 10.04 in parallels on a MacBook pro dual core.

With 80 gig hd and 28 gig swap (in vm)

3 gigs of ram and both cores are now trying to crunch this build.

So anyone have any thoughts?

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] krylon360:
for those wondering if netflix now loads...well...it does, but there is a memory leak that causes libc and the meadia service to die with a memory heap exception once the video tries to load in netflix.

Here is the log

http://pastebin.com/V0HXLQhh

as you can see, the decoders load, but as soon as it tries to play, they system crashes... doesn't freeze, or reboot, just the media server dies and restarts.
[Nook Color Android Development] fattire:
Wonder if changes are needed to ion and/or other stuff to deal with 512MB. I know it had to be done for KFire. If hashcode is around I'll ask him...
[Nook Color Android Development] mateorod:
Are you saying you created a 28 gig swap file? Wow, you can probably go ahead and reclaim a good 20 gigs of that space, if yo have a mind to. At least.

You got the sign.apk fail error or just a make error? Try running htop in a separate terminal and see what's going on with your memory. I have never seen those jars fail with the memory limited to 512, not with 3 gigs of ram.

You have 3 gigs allocated to the VM? How much is left to the host? If you have more than 2 gigs for the host, you could try nudging up your guest allocation, although 3 gigs should be fine for CM. Restart the VM and resume your build and watch top. It shouldn't take long to get to where the error s happening, and you can see how much of your CPU is being used and what is going on with your memory.

Plus you'll get to see how much of that swapfile is just sitting there.
[Nook Color Android Development] lekofraggle:
Thanks a lot. I backed up the cm and am starting over. There was another networking issue that was breaking repo. It did break during the signing.

I have 3 gigs in all and am sending 2 to the vm. I kept running out of memory during make. That is why I went so big on the swap.

I had to move my build environment to an external disk so I could repo in host and build in vm. (I know, worst idea ever).

It worked for a while, but then it just kept failing. So, I am starting clean. In hind sight there were many issues. Htop is going to help me a lot.

~Leko

Edit,

That totally did the trick. I do not know what issue it was, but it is building. It did take 1.8 gigs of the 2 gigs of memory I gave it. And, only used 3 gigs of swap. Though, I gave the vm both cores. I know you are not supposed to do that, but as long as I do not use the host when it builds, I am fine. Thanks for the help. Htop is amazing. For those interested, as long as you follow directions made for it (you need to install some separate packages), ubuntu 12.04 was easier to deal with than 10.04. Though unity does not work well on my vm without some tweaking.
[Nook Color Android Development] krylon360:
08/10 update

some changes pushed to our device tree

libskiahw now building from source - Not pushed yet

Fixed an issue with OMX that has been hanging around since ICS. - pushed

SystemUI is now HW Accelerated - not pushed yet

EGL now reads the correct EGL lib in system/lib - not pushed yet

liboverlay source is now in the device tree. will be moved to omap3 when we merge in omap3-compat source from defy.

removed the prebuilt pvr modules. They are built into the kernel.
[Nook Color Android Development] fattire:
wrong header location...

I can't believe no one noticed that until now! :silly:

Tx!
[Nook Color Android Development] Dj-Gutz:
@krylon360

Check out the new DDK 1.10 if you haven't seen it already

According to the notes it doesn't supposed to do anything special , but who knows..
[Nook Color Android Development] cpkroboth:
Hello, I decided to jump in with both feet. I am not a developer, but wanted to try Fatire's CM10 directions.

I thought I had made it through to the point of being able to brunch encore, but something wasn't right. I tried to repair, but decide to start over. I have been through the build directions for CM multiple times and get this on repo Sync....

fatal: unable to connect to github.com:

github.com[0: 207.97.227.239]: errno=Connection refused

fatal: unable to connect to github.com:

github.com[0: 207.97.227.239]: errno=Connection refused

I have tried the HTTP method, and even checked the local manifest.xml, nothing seems to be working to let me repo the build environment again.

If you need more info to help me let me know.
[Nook Color Android Development] fattire:
Hmm...

looks like you may be having network issues. are you able to ping http://www.github.com ?
[Nook Color Android Development] cpkroboth:
I can browse the site, but get unknown host when pinging in terminal.

EDIT: Just tried http again and it worked... Fingers crossed

carp....failed.
[Nook Color Android Development] lekofraggle:
The website uses a different protocal than repo does. Are you on a vm? If so, what app?

You can try repo init again using HTTPS://... instead of git://...

That is what they suggest, but that did not work for me. I used vmware instead of parallells.

Good luck,

Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] krylon360:
Thanks,

We'll look into it. Keyodi will have to merge it into our kernels. Wont be able to use the binaries until that happens.
[Nook Color Android Development] meteorrock:
I got a guide down in cyanogenMod central for those wanting to get a handle on using git and the github. Check it out here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/

If you are using "Putty" or a different client as your ssh client, it can be kind of temperamental some days on the git. Read over my threads in the link above and see if it helps. Feel free to leave me any questions on getting started at cyanogenMod through my email. All you really need to know at first is to pull and push commits, and I got all of the links for our project in that thread. Make sure you got your public keys pasted in your git page under the "key" options and that they match your key in your ssh client. This CVS seems buggy to me at times. Just keep trying. If you are using a git GUI try to input a command into the git bash and see if that gets you up and going. Any errors I have encountered so far I have found solutions for them by copy pasting the error directly to "stackoverflow.com."

If you just want to pull without setting up a git page you can do it too with selecting the HTTPS option on the git pages, like it was noted in box 2821. Or as a .zip. If, however, you got knowledge with coding you should look into setting up your own git page and helping commit to the git.

Hope this helps.
[Nook Color Android Development] krylon360:
all changes have been pushed and we are testing out a new local_manifest with the omap3-compat stuff. Ive been using it for the past couple of days, and fattire started testing it last night.

keyodi pushed a couple of changes to the kernel which fix the headphone jack, increased audio volume, and changed the sampling rate; however, something in this changed messed up the audio quality. (voices sound slowed down. Most likely it is the sampling rate change. I reset my kernel branch locally to the last commit 4d81408f4b and audio quality is back to normal; but HP Jack no longer works, so Keyodi might have to revert the commit and just enable the headphone jack and leave sampling and volume alone for now.

also pushed a new BoardConfig to the ICS branch. This enables OMX (not sure why it was disabled) and fixes the path for the OMX headers.

Keyodi also started testing DDK@1.10 last night on his local branch as well.
[Nook Color Android Development] keyodi:
Is the audio quality messed up when playing youtube videos?

I fixed my audio slow down, so if i'm not having any issues, then there's no issue at all :p

I'll look at today, but if you want you can try changing the values for the sampling rate in the codec:

static const struct aic31xx_rate_divs aic31xx_divs[] = {
/* 8k rate */
{13000000, 8000, 1, 6, 3803, 128, 16, 1, 128, 48, 2, 24},
/* 11.025k rate */
{13000000, 11025, 1, 6, 1876, 128, 15, 2, 128, 30, 2, 8},
/* 12K rate */
{13000000, 12000, 1, 6, 3803, 128, 15, 2, 128, 30, 2, 8},
/* 16k rate */
{13000000, 16000, 1, 6, 6166, 128, 12, 2, 128, 24, 2, 8},
/* 22.05k rate */
{13000000, 22050, 1, 6, 5153, 128, 8, 2, 128, 16, 2, 8},
/* 24k rate */
{13000000, 24000, 1, 6, 3803, 128, 8, 2, 128, 16, 2, 8},
/* 32k rate */
{13000000, 32000, 1, 6, 6166, 128, 6, 2, 128, 12, 2, 8},
/* 44.1k rate */
{13000000, 44100, 1, 6, 5153, 128, 4, 4, 128, 8, 2, 4},
/* 48k rate */
{13000000, 48000, 1, 6, 6166, 128, 4, 4, 128, 8, 2, 4},
/*96k rate */
{13000000, 96000, 1, 6, 6166, 64, 2, 2, 128, 4, 2, 8},
/*192k */
{13000000, 192000, 1, 6, 6166, 32, 2, 1, 128, 4, 1, 16},
};
[Nook Color Android Development] lekofraggle:
1 more noob question,

Now that I am building frequently and pulling updates smoothly, how often should I make clobber or (clean)? If I just repo sync, brunch and everything works, am I to assume I am utilizing the changes or should I always make clobber?

Thanks again.

Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] fattire:
When there are changes to BoardConfig.mk in the device/bn/encore folder, you probably should make clobber.

Or if there are replaced repositories... or if you havent built for a while... its just a good way to start fresh and make sure you are building the very latest w no stale files...
[Nook Color Android Development] krylon360:
Yes YouTube was slowed down, and a Harold and Kumar mp4 trailer on my SD. NPH sounded big, black, and wanted some... (that deep toned voice) kinda thing.

I reset the head and rebuilt the kernel without the change and audio sounded fine.
[Nook Color Android Development] jschill31:
Hello all,

I gave up on tracking down my issue with builds not booting for me and formatted. After rebuilding my workstation I happened to notice this scroll by while the kernel was building:

MODPOST vmlinux.o

WARNING: modpost: Found 2 section mismatch(es).

To see full details build your kernel with:

'make CONFIG_DEBUG_SECTION_MISMATCH=y'

I am not sure if this is normal or not but thought it was odd?

Cheers
[Nook Color Android Development] krylon360:
Its fine. does it on every kernel ive ever built.