yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] brianf21:
Thanks fattire, I am using the new ramdisk and I am able to pull logs now.

I am still getting a black screen with a backlight. Here is some of the output of logcat.

I/SurfaceFlinger( 1170): SurfaceFlinger is starting
I/SurfaceFlinger( 1170): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/FramebufferNativeWindow( 1170): couldn't open framebuffer HAL (No such device)
E/SurfaceFlinger( 1170): Display subsystem failed to initialize. check logs. exiting...
D/AndroidRuntime( 1173):
D/AndroidRuntime( 1173): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1173): CheckJNI is ON
I/SamplingProfilerIntegration( 1173): Profiling disabled.

Does anyone have any ideas what I am doing wrong?
[Nook Color Android Development] gambit07:
Just wanted to commend you guys on the great work you're doing. It's been said so many times BUT still awesome! Thanks again!
[Nook Color Android Development] Dj-Gutz:
Thanks again Fattire ( and obviously Dalingrin ) for all of the hard work you guys put into this!

I wish the development would be more public , with the kernel git and a compiled-build for first impression ( I think we are far ahead than some of the devices... )

I think there are a lot of devs here just waiting to get it compiled right to starting messing with it and maybe get some of the things working ( and get some load off of you and dal )

An observation I made , dunno if it matters but maybe it will fix your problem

the TAG on egl.cfg file is configured for SGX540 for some reason

0 1 POWERVR_SGX540_120

Should be :

[B][COLOR="Red"]0 1 POWERVR_SGX530_125[/COLOR][/B]
[Nook Color Android Development] zequav:
Awesome :). I don't care much about video and sound, since I use the tablet for email, chat, reading news and casual puzzle games.

Waiting impatiently for the first kangs :D
[Nook Color Android Development] :
That is the best news i've heard all week!

Anyone have a link to fattires how-to? I have been unsuccessful in finding it and currently don't have access to IRC to ask there. I have started to sync the repo, but just want to make sure I get the compile process done properly.

Thank You in advanced...
[Nook Color Android Development] Midnitte:
There is always this or this, but I don't think fattires ever posted it, he was merely saying he has it (in google docs)
[Nook Color Android Development] unsivil_audio:
Holy hell fattire, you are a freaking genius.
[Nook Color Android Development] :
Thanks for the links - have already been following the general nook color guide, was just hopeing for a specific ICS guide for the nook color. I will wait for fattire to post a link - no rush, obviously he has enough on his plate.
[Nook Color Android Development] ganovim:
Kol Ha Kavod
[Nook Color Android Development] 511pf:
You guys really, really ought to setup a donation bucket. I believe that there are something like 15,000 CM7 Nook Color users. If even a thousand of those donated $5 bucks, you guys would get something nice for Christmas. I would absolutely donate.
[Nook Color Android Development] andyrubin1:
my 2 cents

if einstein had waited for a fellow human being to guide him in the discovery of relativity, we wouldn't have nuclear bombs today

ooops actually i wished we don't have nuclear bombs, but that's a side-effect and im going off-topic

guess what? writing a step-by-step guide takes a lot of time, i would rather the dev use their precious time to "hack" (downloading a compressed zip, flashing it according to a step-by-step guide isn't hacking)

theres something that can use a step-by-step guide, but i don't think it's valuable to the community if daligrin spend lots of time writing a STEP-BY-STEP guide.

i'm sure they can suggest you some books or websites to start with, but then you have to get your hands dirty yourself, learn by trial-and-error, there's not shortcut

think about it, why don't the surgeons write a step-by-step guide of all kinds of surgery so you can, i don't know... diy?

oh yes, actually they had, and it's called "enrolling into a medical school".

you get it???

btw, if you have "real" dev questions, drop into the irc, it's where the dev work (instead of posting utter non-sense and "i support this" posts here).
[Nook Color Android Development] sark666:
Just curious, do these latest updates mean ui hardware acceleration might be doable again or is that something that probably still won't ever make it in?
[Nook Color Android Development] fattire:
speaking only on behalf of myself, I don't ask for anything, but if you feel the need to donate somewhere, I encourage you to make a tax-deductible (in US) donation to EFF.org
[Nook Color Android Development] mmark66:
SD Card install

I just posted some information relating why sneak2 and our customs zip don't but without having sneak1 installed onto the sd card first. It doesn't solve the problem yet, but it should help to understand why it is not booting:

http://xdaforums.com/showpost.php?p=21176890&postcount=1590

Let me know if you can reproduce my findings...

Thanks,

Mark
[Nook Color Android Development] Jainyankee1993:
booting from sd

I need help guys..for some reason this isn't working for me... I wrote the img iles on my sd card, and i can see that there is 115 mb left to write on the sd card...then, i go ahead and paste the update-cm file to the boot sd card, and when i insert in into my NC, it just boots up normally, to "Read Forever"....wth? Thank You in advance
[Nook Color Android Development] redhawk79:
I'm getting some of this

host Executable: mkbootfs (out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs)
host StaticLib: libhost (out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/libhost.a)
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6.1/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6.1/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs] Error 1
make: *** Waiting for unfinished jobs....

does anyone know what i need to do to fix this? Am I missing some files or what because I thought I had everything all lined up. I've done a repo sync today yeah and I am not building off anything that I started before that sync.

Thanks in advance for any help

---------- Post added at 05:07 PM ---------- Previous post was at 05:04 PM ----------

did you build via Fattire's instructions? I think it says that those instructions are for EMMC only not for bootable SD? Not sure.
[Nook Color Android Development] michaeljr10wv:
Thanks, that did it...
[Nook Color Android Development] MДЯCЦSДИT:
Can anyone llink me to the latest compiled version? My Linux PC decided to take a *$&@ on me and I don't currently have a build setup...
[Nook Color Android Development] Homer_S_xda:
Best we can do.

Homer
[Nook Color Android Development] redhawk79:
second round of sneakyness

I flashed it but there was no touch capability?!

Do I need to flash sneak1 before sneak2?

Either way I'm still working on my build
[Nook Color Android Development] MДЯCЦSДИT:
Thanks! Seriously, read it...
[Nook Color Android Development] Homer_S_xda:
I took a look at the images in the zip file and they look fine. I find it interesting that rotation is fixed for the lock screen and an option on the home screen. It look to me more like a rotation issue on the screen where the boot slideshow/animation is drawn and not a scaling issue.

Homer
[Nook Color Android Development] EverythingNook:
I've read it so many times and I cannot find sneakpeak2.
[Nook Color Android Development] fattire:
So to explain the rotation thing-- when cm7 was first ported to nook, it started up sideways and was all screwy w/the touchscreen rotated 90 degrees, so I added a preference setting in Android (ro.sf.hwrotation=270 in /system/build.prop if I remember right) to rotate everything 270 degrees. It worked great, and cm7 has that setting to this day.

On cm9, however, suddenly there were problems when you used that setting. You may remember the rotation animation in sp1 was totally screwy, and screenshots weren't possible.

The solution, which was implemented first by deeper-blue when he did his sdk port of honeycomb, was to rotate everything- not by Android, but in the kernel. This had to be done twice: The first time in the display driver, and then again in the touchscreen driver to match.

Once I made those changes in the kernel, things were rotated nicely in the kernel rather than Android, so the old build.prop setting could go away. Android is now displaying "natively" without any rotation. The result of this was working rotation animations and working screenshots. The sacrifice for these benefits is that the startup animation is rotated. The solution will need to be, if someone cares enough to do it, to rotate the animation images or settings or whatever so it's oriented in the other direction...
[Nook Color Android Development] fattire:
I feel guilty. Try reading just the second half. Out loud.
[Nook Color Android Development] sark666:
Stop asking. No one is going to help you here. PERIOD!

Hint. I'm helping you.
[Nook Color Android Development] MДЯCЦSДИT:
Actually read it... it is not obvious. The instructions for the location of 2 are in plain text. Don't look for a link. Im sure at least 3 people looked for links in the sentances but couldn't find it because they wont read.
[Nook Color Android Development] EverythingNook:
I love you two, thanks.

Edit: Now that I see it, its so obvious.
[Nook Color Android Development] Homer_S_xda:
Now THAT I think I'm capable of. Let me give it a go and see if I can rotate the images without changing quality or size.

Homer
[Nook Color Android Development] Ophbalance:
Fascinating. "I Got It." Has anyone tried the new kick ass PS apps yet?
[Nook Color Android Development] EverythingNook:
When flashing sneakpeak2 i keep getting "Random offset: 0x28f" ive re downloaded it 3 times. Also market just opens and closes.
[Nook Color Android Development] saulhaul:
Happy camper here... finished my build and crazy enough it works. Hardest thing I had to setup was ADB on Ubuntu to recognize the Nook.

Anyway, thanks for the lesson Fatire. I'm still going though posts to learn more.
[Nook Color Android Development] boomn:
"random offset" isn't an error, it's just letting you know that it has performed address space layout randomization as part of the installation
[Nook Color Android Development] Homer_S_xda:
OK,

I have a working bootanimation.zip, where can I send it so it can get worked into the files? Size did not get overly large (1.87 v. 1.75 MB). Thanks to fattire and pioneersohpioneers.

Fattire, see your PM for a linky.

Homer
[Nook Color Android Development] KCKitsune:
If you download Quick Settings from the Market, it has the ability to switch WiFi and Blue Tooth on and off. You can also make it so it has an icon in the Notification bar.
[Nook Color Android Development] MДЯCЦSДИT:
I get a black screen after the kernel logo...

First I flashed sneak peak 2 using ROM manager and it failed so I did it manually. During the flag it did that "random offset" thing and then finished. When I rebooted it was just a black screen...
[Nook Color Android Development] MДЯCЦSДИT:
Edit: fixed with a reflash
[Nook Color Android Development] crono141:
I'm running sneak 2 off sd card, and the only major problem I've got is that none of the adblock programs work. They get root permission, but then are unable to remount /system as r/w. I tried using es file explorer to change permissions on the hosts file, but it failed as well.

Also can't get Netflix or you tube to work, but that was not unexpected. Great work folks. Works as a daily driver. :-)
[Nook Color Android Development] douginoz:
Just a note for consideration in the current build development. I think the DPI setting is wrong (it's possibly set up for a phone, not a 7" tablet). [Update: According to Dev Tools, DisplayDPI is currently set to 160. The NC's actual screen pixel density is 169. Don't know if that's it though]

The reason I suspect that is because I ran Honeycomb on my NC for several months and had many widgets running. Now that I'm running sneakpeek2 (after a total and complete wipe of everything), the widgets are the wrong size - the widgets, not the icons. They're a lot bigger (unnecessarily so) than they were with Honeycomb.

I don't know if you'd notice if you hadn't used HC in the past and those of you coming from CM7 or running ICS on a phone won't think there's anything wrong, but there is.

It appears that the NC running ICS only has an array of 4x4 for placing widgets, and only 6x4 for icons. Honeycomb allowed (at least) 6x4 for widgets and 8x6 for icons.

Here's some screenshots of my NC running Honeycomb. You can work out the relative size of the widgets from the icons. It appears that HC allowed at least a 6x4 array for widgets. If you try installing these same apps and adding the widgets to ICS, you'll see that they totally dominate the screen and you can't get close to fitting the same number of widgets on the same screen.

http://i955.photobucket.com/albums/ae36/dirinoz/NookMain1.png

http://i955.photobucket.com/albums/ae36/dirinoz/NookMain2.png

http://i955.photobucket.com/albums/ae36/dirinoz/NookMain3.png

http://i955.photobucket.com/albums/ae36/dirinoz/NookMain4.png
[Nook Color Android Development] HacDan:
This is not a bug, this is how 7'' tablets lay out their homescreen by default. The honeycomb build you had was built statically for a larger screen and ported down to a smaller and lower resolution screen. If you'd like something different, there are a quite a few launcher replacements, even for ICS. I'd recommend checking a few out.
[Nook Color Android Development] douginoz:
Ah, ok. Have spent 20 mins searching for ICS launchers - there's "ICS Launcher" and adw.launcher. The rest are all themes. Neither allowed changing the density of the screen, i.e. you can't have, say, 6x4 instead of 4x4 icons on the screen. And they both force you to have the tray at the "bottom" (the side, in landscape mode) to launch the phone app.

It seems a real shame that we'll have to use the NC as either a very large phone or with messed up widget sizes.

I've done a bit of research and discovered that the NC's form factor was a bit strange when it came out and yes, the HC ports dealt with that (quite well). Perhaps when ICS ROMs start being created someone will make it work better.
[Nook Color Android Development] HacDan:
Well, there's Trebuchet, which is used in CyanogenMod which will allow multiple icons eventually. It's a coming feature, but it'll be there I'm sure.

There's Nova Launcher, which allows you to change the amount of icons on the screen.

There's adw.ex which works quite well on ICS.

In regards to widget placement, I can't replicate your issues. All of the stock widgets work just fine if stretched to fill the current grid size. I don't see a bug here at all. Maybe it is an app widget that hasn't been updated for ICS/3.1 Honeycomb?

6x5 Grid here. Trebuchet launcher included with CyanogenMod.
[Nook Color Android Development] douginoz:
Actually, your screenshots precisely replicate the issue. On Honeycomb, there's room for 8x6 icons on the screen. Your screen clearly shows that you can only get 6 across, so the InTray widget uses up almost all the space on the screen instead of about half (I'm exaggerating to make the point). You probably don't think much of it because you aren't used to anything better - but it means that most widgets dominate a screen because there's no room for much else. Pretty poor for a 1024x600 screen.

Have a look at this screen showing the InTray widget under HC - notice that it's using only a small area of the screen and is still totally legible:

Notice how the Evernote widget is a 4x2 widget and only uses half the width and 1/3rd of the height of the screen. The same 4x2 widget on ICS dominates the screen.

The problem, to me, is that running the NC in this current "low granularity" way means that quite a few widgets become pretty useless, because you end up filling one screen with only one widget. You may as well just run the app "full screen" because you can't see much else. Widgets aren't designed to be that - they're meant to share the available space with other widgets. Maybe not so much on a phone, but on a 1024x600 tablet, you shouldn't have to sacrifice the entire display for one widget.

It's very much like when you come across someone that's been running their 1024x768 monitor at 640x480 resolution and never knew any different.

And what I'm afraid of is that people will get used to running ICS on their NC at this lower resolution and then defend it as "normal", exactly like those people defend running their monitor at 640x480.

Although, having said all that, the analogy doesn't quite work because I'm not talking about changing the actual resolution of the screen - fonts, etc. wouldn't change, it's just that widgets will fit properly on the screen.

I've already found some apps that have widgets that don't even fit on an empty screen because there's not enough room, yet they were developed for tablets. Perhaps that's why the chefs altered HC to run on the NC with the higher granularity of a tablet; otherwise the NC is really just running exactly like a phone but with a bigger screen.
[Nook Color Android Development] rabshear:
Then you didn't read it. I just read it again to be sure. But it's as clear as day.
[Nook Color Android Development] zequav:
Thanks, will test as soon as I get home.
[Nook Color Android Development] fattire:
A Numbers Game

So I just realized that pastebin.com lets you see the number of times your pastes have been viewed. Wanna know how many times the local_manifest.xml file for the encore ics device tree-- which as far as I know is ONLY linked from within the build walkthrough document-- has been viewed?

1,257 times.
[Nook Color Android Development] MrColdbird:
1200 times from me.
[Nook Color Android Development] khaytsus:
No, there is zero reason to flash anything before anything, as it formats /system when it flashes. This is in the update script which is ran every time you flash:

format("ext4", "EMMC", "/dev/block/mmcblk0p5", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");

Adblock has never ran correctly when the OS is installed on the SD card, it can't "find /system" for whatever reason. You can always get the hosts file from somewhere else and install it manually, I kept a copy on /sdcard and every flash I would copy it over using a script running in GScript when I ran CM7 off SD card.
[Nook Color Android Development] Zorkman:
Fattire mentioned that video is not working in his first post in this thread.

You can get youtube to work if you untick the high quality box

(works for me at least...)
[Nook Color Android Development] crono141:
I realize that about video, which is why it was not unexpected. What I'm most concerned with is being unable to mount system as r/w. Seems to me that many root apps need to write to the system partition at some level, and are rendered non-functional. I'm curious if anyone else is having this issue, or if it's unique to my circumstances.

EDIT: Just saw khaytsus post relevant to mine. Thanks for the info. Can you PM me your most recent hosts file. I'll try to push it somehow. I'm wary to install ICS to the EMMC, mostly because it's my wife's nook. Perhaps once a sneakpeek 3 or better comes around, I'll do it then. Seriously, this is an amazing port, and runs very well even without hardware acceleration. Plays most of the popular games just fine (Angry Birds, Plants vs Zombies). Haven't had any issues except this one. Great work everybody.
[Nook Color Android Development] sip70:
was cm7.1( with root) ... flashed cm9, without GAPS ... how to make root
[Nook Color Android Development] Homer_S_xda:
I fixed your statement above. Are we certain that Verygreen's 1.3 performs the wipe? It is sort of designed for dual-boot and makes no changes to emmc. In VG1.3, /system is a partition on the sdcard and not the emmc. Initially, I could not get v2 to run from VG1.3 without flashing v1 first. I've gotten braver and started editing the updater-script: remove the two font symlinks and remove the whole section involving retouch_binaries to get it to boot without a boot loop.

Homer
[Nook Color Android Development] HacDan:
It is normal. That's what you're missing. Go play with Honeycomb on a 7 inch tablet. You'll notice the same thing. You used something that was NOT designed for a 7'' screen, but for a 10'' screen. I don't know how else to explain to you that this is normal behavior. There is no reason for you to 'worry' about people getting used to this. This is how 7'' tablets work. You got used to something that WASN'T normal.

Please watch a review of a Galaxy Tab 7.0Plus or another Honeycomb running 7'' tablet. There is nothing wrong.

Here's a video for you to take a look at, you won't even have to search Youtube for one: http://www.youtube.com/watch?v=A0FGgCxBSpM

And for the reference, I used Honeycomb on my NookColor up until the point I flashed ICS on it.
[Nook Color Android Development] 911jason:
Pardon my ignorance, but can't he just edit the build.prop to change the density to a number that is more to his liking?
[Nook Color Android Development] HacDan:
Sure, if he wants to break market compatibility. And it wouldn't help anyway, the launcher will still only allow a certain icon grid, they'd just be smaller.
[Nook Color Android Development] khaytsus:
Can't say for sure what happens on SD, if it wipes its own /system path or not. Of course it won't touch the internal devices.

I didn't use sneakpeak2 on SD, I did the first, and several since. I doubt there are any interdependencies..
[Nook Color Android Development] Homer_S_xda:
Do you have any insights into what we are doing wrong? I'm not the only one having issues with booting v2 or a new build on VG1.3 without either flashing v1 first or editing the updater-script.

Homer
[Nook Color Android Development] FletchF:
Anyone have a workaround to enable wifi location? That's the only key feature missing for me.
[Nook Color Android Development] pavlos46:
Actually the problem is not the wifi location but the map app, try loading the map 5.9.0 and it will work.
[Nook Color Android Development] bdcrim:
I tried to change the density setting, but could not find it in build.prop. Is it there? Also i tried to change it to 200 with a density changing app and the launcher crashed on me after rebooting. I had to shut things down and reinstall the rom. Maybe someone else will have better luck.
[Nook Color Android Development] HacDan:
The launcher doesn't support above 160DPI afaik(Unless you're going into phone territory, which it then should support). I tried changing to 169 to see if I could get things a bit crisper and hopefully fix the keyboard. Didn't help :(
[Nook Color Android Development] therkr:
I'm just being curious but is it so that for ICS, the NC needs to br upgraded from a 2.6.29 kernel to a .32 kernel and that's causing several issues?

Actually, I saw this: https://github.com/verygreen/ti-omap-encore-kernel/wiki/encore-2.6.32

And thought maybe...
[Nook Color Android Development] xxsxx:
When I ran CM7 off of the SD card I use to run this from adb shell:

# busybox mount -o rw,remount /system
# cd /system/xbin
# ln -s busybox mount

That fixed that problem for me. I don't know if that will work on ICS, though, as I haven't dug around in it much yet, and I just installed it in emmc last night.
[Nook Color Android Development] HacDan:
We're using a .32 kernel.
[Nook Color Android Development] FletchF:
Thanks, I'll try that. I assumed it was a general problem because location services fail with other apps such as Facebook.
[Nook Color Android Development] greiland:
There's an option in Settings, Trebuchet, Homescreen, Resize any Widget. Does that get you what you want?