yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Three-0-3:
cc1: some warnings being treated as errors

Hi,

Thank you for making JB on NC!

I got the compile error in hardware/ti/omap3/omx/audio/src/openmax_il/wbamr_enc/src .

<<snip>><<many case value errors but some case values are not warned>>

hardware/ti/omap3/omx/video/src/openmax_il/video_encode/src/OMX_VideoEncoder.c:2571:5: warning: case value '2130706455' not in enumerated type 'OMX_INDEXTYPE' [-Wswitch]

hardware/ti/omap3/omx/audio/src/openmax_il/wbamr_enc/src/OMX_WbAmrEnc_CompThread.c: In function 'WBAMRENC_CompThread':

hardware/ti/omap3/omx/audio/src/openmax_il/wbamr_enc/src/OMX_WbAmrEnc_CompThread.c:208:24: warning: return makes pointer from integer without a cast [enabled by default]

cc1: some warnings being treated as errors

<<snip>>

My local copy is CM9 - "hardware-ti-wlan" + fattire's hardeare-ti-wlan + hazenme's omap-kernel-encore3 + hazenme's device_bn_encore .

ICS was built without errors on my build environment. Proprietary files were extracted from ICS and hazenme's surround71.conf was copied.

Any clue appreciated.
[Nook Color Android Development] Hephaestus_:
-snip- nm Problem solved through repo sync.
[Nook Color Android Development] krylon360:
What hardware/ti/omap3 source are you using?
[Nook Color Android Development] Three-0-3:
Original cm10's tree.
[Nook Color Android Development] krylon360:
That's why. That source is very very old. Grab the source from fat tires github. We are still testing the p-ics-mr1 branch so use the jellybean branch. It builds just fine.
[Nook Color Android Development] jdpdata:
How do you get WiFi to stay? WiFi was OK at initial setup, but as soon as I rebooted, it's borked. I install Wake Lock PARTIAL_WAKE_LOCK and make sure it's set to start at boot, but still lost WiFi.:confused:
[Nook Color Android Development] newellj79:
If anyone has any ideas on why I can't get the touchscreen working, I'd appreciate it. I've tried both the regular manifest, as well as test4, and still no go. Thanks.
[Nook Color Android Development] jdpdata:
Why don't you try Andbot method? Build successfully for me, and touchscreen works great. But i'm having WiFi dropout issues.:confused:
[Nook Color Android Development] eyeballer:
Wifi issues are well known. Wipe cache/dalvik cache should bring it back.
[Nook Color Android Development] newellj79:
Maybe I will. Truth be told though for me figuring out how to build it is most of the fun.
[Nook Color Android Development] MACLUIS1:
Wow, it's incredible how much you can learn when you're given a good explanation.

I'm talking about fattire's explanation about compiling from source.
[Nook Color Android Development] keyodi:
I pushed the fix for the newer touchscreens last night. Make sure you have your local_manifest set to:

<project name="keyodi/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
[Nook Color Android Development] krylon360:
Welcome back!
[Nook Color Android Development] jschill31:
Hello,

Go into recovery and wipe dalvik cache and cache then reboot into your CM10 build. It will go through all of the upgrading apps stuff then into your rom. As long as you had the Wake Lock set to go on boot you should recover the WiFi and not loose it going forward. If that does not clean it up for you I am not sure....but one thing we do know is not all Nook's are created equal. There is up to a 10% tolerance difference in the chips so millage may vary. :)

Hope it works for you. Today was the first day I tested it from a full charge, so far 8.5 hours and at 25% but with little use.

Cheers
[Nook Color Android Development] jdpdata:
Thanks, eyeballer explained it was a known bug. I assume WiFi only stay until next reboot, then I'll have to wipe again?

Also noticed that my battery only charges until 66% on CM10, then stops.

Booted back in CM7, it's now charging properly.
[Nook Color Android Development] newellj79:
Try wiping battery stats in recovery.
[Nook Color Android Development] jdpdata:
I would but TRWP doesn't have wiping Battery Stats!:confused:

Guess I'll download Battery Calibration to try.
[Nook Color Android Development] Hephaestus_:
Edit: When trying to brunch encore, it spits out this:

Also, at the beginning it says this. Is this normal?:

including vendor/cm/vendorsetup.sh
Looking for dependencies
Dependencies file not found, bailing out.
[Nook Color Android Development] krylon360:
Please for the love of my eyes. Take your post and put it in a pastebin and edit your post to just have the pastebin link

But I see your issue. You synced with the wrong source. In your local manifest everything should be jellybean for the revision except for keyodi's kernel source.
[Nook Color Android Development] krylon360:
Yes it does. Its in the wipe tab. Big button that says battery stats.
[Nook Color Android Development] Hephaestus_:
KK thanks. I'll do that from now on.
[Nook Color Android Development] Hephaestus_:
Also, not that I've resynced my repo, I'm getting a new error:

build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/encore/cm.mk]]: "frameworks/native/build/tablet-dalvik-heap.mk" does not exist. Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Here's my local_manifest.xml: [LINK]
[Nook Color Android Development] inportb:
Right, you also need to repo init -u git://github.com/CyanogenMod/android.git -b jellybean ;)
[Nook Color Android Development] jschill31:
Hello,

My guess is that they are using the new TWRP 2.2 which I do not believe has a battery wipe tab? When I flashed the new version I no longer have the button either...maybe Eyeballer can confirm? Anyway I do not think it would correct the issue. My guess is that he is trying to charge the unit either when it is powered up or from a PC USB (or both). So far the only way I have been able to achieve 91% (full on my Nook) is to use the factory USB cable and factory wall charger without the Nook turned on. In order for the Nook to stay powered down while charging you need to plug it in when the Nook is on and then power down.

Cheers
[Nook Color Android Development] Hephaestus_:
Oh, ok, so it's different than the OP that says to do -b ics?

*facepalm* NM. XD I was trying to build cm9 and cm10 at the same time, making it have an error. kk, got it now.

Also, when repo syncing, can you use more than 16 threads? I'm currently running -j32, but I'm not sure if it's faster than -j16.
[Nook Color Android Development] jschill31:
Hello,

CM10 boot animations: http://xdaforums.com/showthread.php?t=1782074

Cheers
[Nook Color Android Development] fattymcdirty:
so... i've set-up a VM with ubuntu on it... now is there a complete tutorial on how to set up a build environment and build cm10 from those sources? i'd really like to give it a try!
[Nook Color Android Development] newellj79:
Yes. It's a combination of these two guides.

http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Compile_CyanogenMod_(Linux)

https://docs.google.com/document/d/194wk4Tx0NyR7pIpFtBw76dltF7Igj0Uaquha5q1ZoDc/edit
[Nook Color Android Development] Hephaestus_:
When I try to boot, I keep on getting this bug.. even after wiping cache and dalvik through twrp. How can i fix it? thanks.
[Nook Color Android Development] eyeballer:
Yes, we removed wipe battery stats from TWRP with 2.2.0. It was time to remove the useless placebo stuff we've all fallen for at times =P

Reference: https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[Nook Color Android Development] jschill31:
Figured as much:highfive:
[Nook Color Android Development] newellj79:
Damn. Just built clean again. Still no TS. :( Could somebody refresh my memory on how to pull a logcat so I can post for people to look at it?
[Nook Color Android Development] pbot:
If you want a shortcut, use inportb's andbot package. I use it in a vm as well.
[Nook Color Android Development] biohazrd51:
You're in luck. This was just on the front page of XDA.
[Nook Color Android Development] krylon360:
You're building with keyodi's kernel source and not Haze's repo right?
[Nook Color Android Development] newellj79:
I'm using keyodis. Tried hazes a couple times to though. No ts on either.
[Nook Color Android Development] eyeballer:
Join us on IRC.. Or anyone else that has a newer touchscreen nookcolor.

Also you should rm -rf kernel/bn/encore make sure your local_manifest is correct (use fattire's) and then re-sync.
[Nook Color Android Development] newellj79:
Thanks. I'm going to try and catch you guys there tomorrow. My wife will probably be on facebook most of the night. Ha! :(
[Nook Color Android Development] Hephaestus_:
Well, for some reason, my media_profiles.xml keeps on getting deleted when I boot, and then proceeds to give me the media_profiles.xml boot-loop. Even after clearing cache and dalvik, and manually inserting the revised media_profiles.xml manually, it still boot loops. :(

[ADB LOG]
[Nook Color Android Development] krylon360:
thats not your issue.

E/libEGL (12361): validate_display_connection:224 error 3005 (EGL_BAD_CONFIG)

E/libEGL (12361): validate_display_connection:224 error 3005 (EGL_BAD_CONFIG)

means your props did not copy over. Make sure you are running the extract-files script while you have CM9/AOKP loaded.
[Nook Color Android Development] Three-0-3:
Thanks

Krylon360, Thank you for your info.

Succeeded to build, install and boot from the primary partition of SD card.

The MAC address is changed to 00:d2:8b:43:9f:fd .

I don't find the calibrator of ti-utils on cm10. How do I change the Mac address?

Sorry for noob question.

Thanks in advance.
[Nook Color Android Development] fattymcdirty:
So next, type:

croot

brunch encore

The build should begin. If that doesn’t work, first, type lunch. You should see a list of devices, including something like cm-encore-userdebug Select it by typing its number. Then...

Following error:

sebastian@DEV:~/Downloads$ cd ~/android/system/

sebastian@DEV:~/android/system$ lunch

You're building on Linux

Breakfast menu... pick a combo:

1. full-eng

2. cm_grouper-userdebug

3. cm_maguro-userdebug

4. cm_toro-userdebug

5. cm_toroplus-userdebug

... and don't forget the bacon!

Which would you like? [full-eng]

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

---------- Post added at 11:26 AM ---------- Previous post was at 10:59 AM ----------

This is wrong, too, isn't it?

sebastian@DEV:~/android/system$ lunch

You're building on Linux

Breakfast menu... pick a combo:

1. full-eng

2. cm_grouper-userdebug

3. cm_maguro-userdebug

4. cm_toro-userdebug

5. cm_toroplus-userdebug

... and don't forget the bacon!

Which would you like? [full-eng]

dang and what is this?

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

It REALLY seems to need that for building, because it stops building with this:

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

make: *** [out/target/product/encore/obj/lib/crtbegin_static.o] Fehler 126
[Nook Color Android Development] krylon360:
did you create the local manifest before you sync'd? did you type . build/envsetup.sh before the lunch command?
[Nook Color Android Development] fattymcdirty:
to both: yes

sebastian@DEV:~/android/system$ . build/envsetup.sh

including device/bn/encore/vendorsetup.sh

including device/generic/armv7-a-neon/vendorsetup.sh

including device/generic/armv7-a/vendorsetup.sh

including device/ti/panda/vendorsetup.sh

including vendor/cm/vendorsetup.sh

including sdk/bash_completion/adb.bash

and i did that:

BEFORE you repo sync per the next instruction, you’ll need to add the encore (nook) device folder for jellybean, which is temporarily hosted on github by me, fat-tire. To do this, create a file in ~/android/system/.repo/local_manifest.xml

and add the pasted contents of this page into it: http://pastebin.com/vZFKdc8m

What is this file? The local_manifest.xml file supplements the regular manifest, adding this needed repository to those provided by the main cyanogenmod ones so that a regular “repo sync” command will update changes from there as well.

Helpful tip! If you’re using Ubuntu (or the GNOME desktop in general) you can create and edit this text file with the following command: gedit ~/android/system/.repo/local_manifest.xml

but whats the error for this?

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: Kann die Datei nicht ausführen.

i'd really lik to test JB on my nook :(

EDIT:

added some lines and now i have:

sebastian@DEV:~/android/system$ lunch

You're building on Linux

Breakfast menu... pick a combo:

1. full-eng

2. full_x86-eng

3. vbox_x86-eng

4. full_encore-eng

5. cm_encore-userdebug

6. mini_armv7a_neon-userdebug

7. mini_armv7a-userdebug

8. full_panda-userdebug

9. cm_grouper-userdebug

10. cm_maguro-userdebug

11. cm_toro-userdebug

12. cm_toroplus-userdebug

... and don't forget the bacon!

but what about that gcc error? prevents me from building atm... :(
[Nook Color Android Development] frikakwa:
Try with Rom Manager. If I remember good, it detects when your device has changed the MAC adress and propose you to go back to the original one!!
[Nook Color Android Development] Hephaestus_:
I can confirm that touch-screen works with the newer nook color... but that it quits working after the device goes into standby mode. Will try to install wakelock and see what happens.

Edit: Wakelock fixes the problem, just use the partial wakelock.
[Nook Color Android Development] newellj79:
Maybe that's my problem. Right after the boot animation it goes into stand by and I have to press a button to wake it up. Is there a way to enable wake lock other than in the UK?
[Nook Color Android Development] Hephaestus_:
You're saying that immediately after you boot, the screen goes black and into standby? :( It shouldn't be doing that. If you haven't done so already, go into recovery, wipe cache, dalvik, data, and system, then re-install cm-10, it should show the google account setup thing, and directly afterwards, install wakelock asap and select partial wakelock and toggle it on.

---------- Post added at 05:30 AM ---------- Previous post was at 05:18 AM ----------

OK, this is weird. After a few minutes of standby, even with wakelock, it starts picking up phantom touches, which prevent the phone from being unlocked(unless you try a bunch of times). I managed to pull a logcat though, and I've found some errors (though I do not know what they mean or if they are relevent). Here's the link. [LOGCAT]

Also, wifi is not working after going into standby mode.
[Nook Color Android Development] lekofraggle:
So thank you all for your help. I finally got my build together and this rocks. I am on an old nook color and do need wake lock.

So I figured out tablet ui. I am not sure this will work for everyone and I apologize if my code is wrong but I followed the directions here http://xdaforums.com/showthread.php?t=1780970
and it worked for me.

The reason changing dpi does not work is that jellybean needs to pull the files from a different folder to build tablet ui. Flashing his zip did not work (maybe because I am not deodexed), but hardcoding the changes did with no problems thus far. Here is what I did.

A huge credit to barrmulio over in the nexus forums. None of this code is mine. Take a look at his thread to understand what is going on here.

In

frameworks/base/policy/src/com/android/internal/policy/impl/ PhoneWindowManager.java

Change

if (shortSizeDp < 600) {
// 0-599dp: "phone" UI with a separate status & navigation bar
mHasSystemNavBar = false;
mNavigationBarCanMove =true;
} else if (shortSizeDp < 720) {
// 600-719dp: "phone" UI with modifications for larger screens
mHasSystemNavBar = false;
mNavigationBarCanMove = false;

To

if (shortSizeDp < 600) {
// 0-599dp: "phone" UI with a separate status & navigation bar
mHasSystemNavBar = true;
mNavigationBarCanMove = false;
} else if (shortSizeDp < 720) {
// 600-719dp: "phone" UI with modifications for larger screens
mHasSystemNavBar = true;
mNavigationBarCanMove = false;

I changes both because we are on the cusp between the two conditions. With dpi set to 160 you are in the former, but if you change your dpi to 169(native for the nook), you will jump to the later condition.

/frameworks/base/services/java/com/android/server/wm/WindowManagerService.java

Change

outConfig.smallestScreenWidthDp = (int)(mSmallestDisplayWidth / density);

To

outConfig.smallestScreenWidthDp=721;

I could host this on git, but do not want to lose changes upstream in these two files and the coding is easy. Let me know if you want it and I will share.

Thank you all for your help. It was a process, but now I have a great build and am learning a lot.

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] Hephaestus_:
OK. So... my touchscreen is working now, WITHOUT a wakelock. It turns out that I had to wipe /system/ in addition to /data/, cache, and dalvik; but now all the phantom touches are gone, and the touchscreen is responsive, even after a long time in standby. Currently, this is 30 minutes after I first booted it up and the touchscreen is still working; I will keep on watching it, and see if the issue is gone.

Also, is there a way to overclock cm10 beyond the standard 1000mhz? SetCPU has 1000 mhz as the max, and nook color tweaks is not compatible with my kernel.
[Nook Color Android Development] fattire:
Gotta add the extra steppings to the kernel... there are no doubt a few 3.0 kernels you might be able to use as a model.. If you want to add it, as well as some new governors, go for it and contribute the changes back once you've tested it..
[Nook Color Android Development] krylon360:
As long as the UI doesnt break on phones, I say have him submit it to CM
[Nook Color Android Development] atharchian:
Thanks for providing this, got mine working on tablet ui.

Settings

Easter Egg
[Nook Color Android Development] jschill31:
Hello,

The tablet UI does seem to be off a bit, maybe needs a tweak in build.prop? Auto-rotation does work even on home screen using the tablet version which is nice but my grid pattern must be odd numbers. All widgets seem to be shifted one position to either the left or the right. Any advances in figuring out how to keep the screen from breaking, it would be great to not need the wake-lock?

Cheers

PS, anyone who does build in tablet mode will need to revert back the modified files before you can repo-sync again. The good news is your cursor should stay at the place you saved it so no need to search through all the code again. :)
[Nook Color Android Development] tomsawyer14:
I've noticed that when I do a build, it names it the same as the first one I compiled, with a 20120724 date. I'm assuming ccache has something to do with that? Is there a way to get it to put the correct date on the build? Really minor thing, I know. Renaming is easy enough I was just curious.

I'm about to flash with the tablet changes suggested above. Looking forward to seeing the result.

---------- Post added at 01:20 PM ---------- Previous post was at 12:52 PM ----------

OK I see what an earlier poster was talking about with the desktop being shifted slightly to the left. Odd thing is, any applications are drawn dead center. Also noticed in Rom Toolbox the dpi is set to 160 instead of 169. Changing it didn't seem to do anything. Doesn't change the usability in any way, just looks like a TV with a bit of overscan.
[Nook Color Android Development] deeper-blue:
Forcing it into tablet UI like this doesn't look like a good idea. I will look into a better way to do this, maybe something that allows people to switch UIs from device settings.
[Nook Color Android Development] mateorod:
Just make clean or clobber. You are using some prebuilts from the build you made on that day. The clobber will pick up all of the changes.

I have a booting JB encore build and just finished building CM10 for grouper. I have been watching you guys work, very nice.

After struggling through the grouper process, I finally had to write my own cm.mk modeled off of the nooks, along with several other irritants. The build was almost done before I finally figured out that all the necessary changes are only available as cherry-picks, they just aren't committed.

I guess they are trying to head off the kangers...lol. I need to get better at git, that is one lesson.

I wish I could pick you guys up whole cloth and deposit you in the Nexus 7 forums. It is prettty wild and wooly out there.

Edit I just saw deeper-blue's post..and before you spend too much time...barmullio who helped devise this change has pretty much stopped working on his patch (Edit: Well, he might have changed his mind and gone back to work..idk) since molesarecoming release a ParanoidAndroid build for the Nexus 7.

I actually have a mostly working JB ParanoidAndroid port on my Nook already.

So it is a thing that has already been made.

However, those sources aren't open yet, and I can't really say they look like they are getting anywhere near to releasing them or commiting them upstream to CM (which they say they intend to do). So something open from you might be just the ticket.

I wanted to mention that someone had done this just in case you you didn't feel like replicating existent work...although I would probably switch to your stuff the second I could...
[Nook Color Android Development] jschill31:
Hello,

The dpi is actually set at 160 by the build.prop in system. I doubt that any program like Rom Toolbox can alter this, I can't even text edit the file and get it to save. I think the only way to alter the dpi would be to do some other build alteration such as the one those of us did to get the tablet UI. The best way would be to have it be a choice such as Paranoid uses.

Cheers
[Nook Color Android Development] biohazrd51:
I was able to use Rom Toolbox to modify DPI and get tablet UI. I had to drop down to like 120 to do it. If that is what you are referring to.
[Nook Color Android Development] tomsawyer14:
Ah yes 120 was a pretty big improvement though it made things really tiny. I tried 140 and while it does fix the "overscan" it didn't do the actual tablet interface. I'm with the actual devs on this one. Those changes are maybe not so ready for prime time. Fun way to waste a few hours on a slow afternoon tho ;)
[Nook Color Android Development] lekofraggle:
Thanks all for the support. All the issues with the tablet ui mentioned are in the Nexus thread. I did not have any of them so I thought it was fine on the nook. I do not use either stock launcher. I go between apex and nova and it works fine.

If you edit local files you will get sync issues. I just move them sync and replace. This is why git is so good.

I would like to do a toggle or better yet incorporate paranoid, but those are beyond me right now. I have almost got a toggle but need to learn a bit more about how to do that.

As far as pixel density, you can use lcd density changer in the market.

The way I changed it, this will break phone ui because I changed both the lines which trigger phone and phablet to point to tablet ui.

But, this gets me a nicer ui while we fry bigger fish.

If your layout is messed up, check your lcd density. I had issues with things being off center when I changed mine (this happens on all versions of Android if the stars align).

Happy hunting

~Leko

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] jschill31:
Hello,

Has anyone made progress on the screen death?

Cheers
[Nook Color Android Development] fattire:
The best way to phrase that question is like this:

:eek:
[Nook Color Android Development] Tiezane:
I'm no developer, myself, but thank you to everyone contributing to this project. I watch eagerly for each new breakthrough you make!