yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] wallsg:
Why are hashes necessary?

Here's something I've always wondered about...

Why is it necessary to do a hash check of downloaded images? Why is it that every other single file downloaded through the internet has error detection/correction and comes through without problems but these images are so prone to corruption? When was the last time you downloaded a corrupted ZIP file that wasn't a flash image? 1996?
[Nook Color Android Development] christoophat:
I've noticed battery life seems a quite bit reduced running n136. I fully charged it before updating to it, wiped battery stats, used it for a couple hours for just reading, shut it off all day, took it with me for a Dr.s visit yesterday, again just reading for maybe 1 1/2 hours ,even turned off wifi, and down to 29% left on charge. Not good. Also noticed on CPUSpy that my deepsleep % & 300 mhz % were almost the same.
[Nook Color Android Development] slider2828:
But still it does not make sense that clock speed would increase while losing GPU speed.... That doesn't make sense....

BUT it could be the physical architecture.... Just speculating.
[Nook Color Android Development] doncaruana:
I understand that. But if I add something and then remove it, shouldn't it be like it was before? 2 +2 = 4, but shouldn't 4-2 = 2, not 3? Sounds to me like they weren't completely removed...
[Nook Color Android Development] frankusb:
Except if you look at the files that were added and removed in the change log you can verify exactly which files changed.

Of note, the wifi driver was updated and not removed between the 2 changes.

Frank
[Nook Color Android Development] doncaruana:
Okay folks...manually applied Dalingrin's OC kernel via recovery/update zip (even thought it's embedded) and my nenamark scores went back up to 23.6 like they were in n131! I reported it over in the CM7 development thread - hopefully it means something to someone.
[Nook Color Android Development] dalingrin:
I default the CM7 kernel to 32bit framebuffers. My overclock kernel defaulted to 16 bit. You can switch between the two with Nook Color Tweaks.
[Nook Color Android Development] doncaruana:
That's it exactly! When I switched back to 32-bit, I get the same rates as with the nightlies. I never even looked at the bit-depth previously. Thanks for explaining that!
[Nook Color Android Development] christoophat:
Would running 32 bit versus 16 bit have any effect on battery power timefence?
[Nook Color Android Development] lschroeder:
Bluetooth Logitech V470 mouse works

Using Nightly 139. See my post in the Bluetooth accessories thread

http://xdaforums.com/showpost.php?p=15873027&postcount=71

I do not know if any of the developers can help us out. The bluetooth seems much more stable in the new nightlies and with a couple of tweaks would be great. I love using a mouse and keyboard when I have the nook on a stand.

Edit 2: Is it possibly an HID driver issue? Can other HID drivers being substituted that might work?

Our problem as stated by TheAmazingDave "if the Nook registers movement before the mouse pointer appears, the GUI will likely lock." Is there any possiblity that you developers can help with this one?

Specifically the problem with using a Logitech V470 bluetooth mouse is preventing the GUI lockup when setting it up or rebooting the computer (solved see Edit). Thanks to TheAmazingDave I was able to get it setup and work every time on reboot. As TheAmazingDave said "once you get it showing the cursor their does not seem to be any problem with it."

Edit: Since I ran Android Assistant from market (selected tools, in lower right hand corner selected airport icon, it turns grey, disabled), when I reboot both wifi and bluetooth are now there. I just wait for the wifi and bluetooth to be enabled and the mouse and wifi both work with no interaction from me.

It looks like for most bluetooth keyboards that work will let you run a bluetooth mouse and bluetooth keyboard concurrently. The exception being my Xoom bluetooth keyboard with its 30 second battery saving feature and after several minutes of inactivity pressing a key causes it to reconnect which also locks up the bluetooth mouse. See post above.

Edit 2: Read that all bluetooth keyboards have sleep and reconnect function. So far the only one that I can find on the Nook that works concurrently without a problem is TheAmazingDave combo. Anybody else have combo that works? Lots of bluetooth keyboard and mouse combo success on other Android devices? Mine nook is close the automatic reconnect lockup of GUI is the problem.

I know I can do the same thing with usb host mouse and keyboard, but I like having my Nook plugged into its AC power adapter when I have it on a stand.
[Nook Color Android Development] bobster0001:
Did anyone lose their root after n139?
[Nook Color Android Development] derekr:
I don't know what is happening...

On flashing #136 and again on #139 my sdcard has been totally corrupted to the point where nothing can read it, and it requires a low level format to bring it back.

I've checked the md5 sum each time before flashing.

Another peculiar thing, when trying to use Dal's tweaks on display settings, I get an error message that my kernel is not compatible with display settings and I need to load a newer version of CM7! But these ARE the latest and greatest versions of CM...

I wonder - could it be actually installing on to the sdcard?? Thus corrupting it. It still boots from eemc. That would explain the apparently old version of CM7 as well. If that's the case, how do I force the install to eemc? I've been flashing nightlies since the 30s with no problems.

Nope - Settings says version of CM is 07212011, ie today.
[Nook Color Android Development] dvdivx:
I always use a dedicated card for flashing the emmc with a recovery image plus a few other files on the card. Wipe the dalvik cache, regular cache and then fix the permissions after the install. Never had any issues with any nightly except 106 which didn't have superuser included with the rom.
[Nook Color Android Development] ambogt:
This! The same dreaded thing happens to me! My stupid gui totally locks up when connecting my mouse.
[Nook Color Android Development] khaytsus:
You don't have about 200 things installed either I suspect..
[Nook Color Android Development] lschroeder:
Try doing what's in this post, your bluetooth mouse should work and now that I used Android Assistant from market to keep wifi and bluetooth during reboot the wifi connection and bluetooth mouse are still there.

http://xdaforums.com/showpost.php?p=15873027&postcount=71

Does anybody beside Stevebez have the new Logitech Tablet Keyboard for Android 3.0+? Might call it 3.1+ now. Walmart Superstores carry it. Stevebez reported that it worked in the above thread.

Edit: If anybody has the Logitech Tablet Keyboard, does it ever time out or does it always stay connected? If it stays connected then it would be a good candidate to use with the Logitech V470 Bluetooth Cordless Laser Mouse for Notebooks (Blue) that I have.

Edit 2: The Logitech Tablet Keyboard enters a battery saving state when it is not used for several minutes. The keyboard will automatically power back up when you start using it again. While the keyboard is powering back up and re-establishing the Bluetooth connection with your tablet, your first few key presses may not register. This is normal and will occur with any wireless Bluetooth keyboard.

@ TheAmazingDave or anybody else using both bluetooth keyboard and bluetooth mouse concurrently. Are your bluetooth keyboards going to sleep? Is anybody having the same problem as my Xoom keyboard where this automatic reconnecting causes lockups of GUI(probably affecting the bluetooth mouse since lockups of GUI do not occur when mouse is not used)?
[Nook Color Android Development] harpo1:
Is firefox working on the latest nightlies? I don't use it but a friend of mine said it doesn't and I haven't read anything stating firefox doesn't work.
[Nook Color Android Development] SeaFractor:
Not sure how many might be using it. Most seem to prefer the Dolphin HD browser. Don't get me wrong, Firefox is great on a PC but seems to be pretty "bloated" on Android.

Several guides/reviews on browsers make a note of that. http://hubpages.com/hub/Review-of-Web-Browsers-for-Android-2x

So if one doesn't mind the resource impact, it's pretty good.
[Nook Color Android Development] dalingrin:
The Aurora 7a2 builds are faster than any other browser I've tried on Android. By faster, I mean page load time and such. Scrolling is very fast on my phone but it does not scale well to large screens like the Nook yet. Scrolling on the Nook isn't the fastest. I would definitely not label the latest Firefox builds to be bloated. It does have a large download and install size like any app that uses the NDK.
[Nook Color Android Development] Colchiro:
Not too long ago, Opera Mobile was the only browser that used hardware acceleration.

Can you get h/w acceleration with the NC's new kernel? Maybe not, but I bet Dalingrin would know.

Personally, I can't stand the Opera browsers.
[Nook Color Android Development] dvdivx:
Waiting for the GPU issues to get ironed out on the nightlies but for browsers:

Firefox: Bloated but still works as fast as others. Flash does not work so it's a no go for me.

Opera: Weird menu system but works when Dolphin doesn't with some java buttons on some web pages.

Boat browser: Works but self-starts and operates in background. Uninstalled.

Dolphin HD: Best overall but does not work on some webpages. Craps out every once in a while.
[Nook Color Android Development] xpri:
any idea when the next stable is coming out? been awhile since rc1. Any recommendations on more stable nightlies? Am thinking of upgrading from my 7.0.3
[Nook Color Android Development] fattire:
I think the 7.1 nightlies are pretty good. If you do update, expect some weirdness with how your battery levels are reported for the first few cycles as the method for reporting usage to the battery has changed from 7.0.3, in that in 7.1 it does it and in 7.0.3 it doesn't. That should get more accurate over time tho. The first few boots it'll over or under estimate the usage.
[Nook Color Android Development] dsf3g:
I went from Phiremod 6.3 (CM7.0.3) to CM7.1 RC1 and I couldn't be happier. The gain in battery life alone is worth the price of admission. Go for it.
[Nook Color Android Development] patruns:
I always just use ROM Manager to find, download and install the latest nightly. Leave the wipe Davlik cache box checked by default and always include the market app. I hope I do not jinx myself by saying it but I have not had a single problem updating and I have done 6 so far.
[Nook Color Android Development] Ronin3178:
I do a variation of that process, download via ROM Manager, cancel install, boot into CWR, do a manual install and wipe cache/davlik reboot. All is well in the world of nightlies. :)
[Nook Color Android Development] Bimboy:
This is exactly my process, too, but I did have issues recently with N136. My MicroSD card corrupted after attempting to boot for the first time flashing. Unrecoverable corruption, so something happened there... Mine's probably a fluke, but I read that another person had the exact same thing occur with N136 as well.
[Nook Color Android Development] leapinlar:
I always use ROM Manager to install the latest nightly also. I also leave Dalvik cache checked and include gapps.

I have taken it one step further in modifying the gapps zip to customize my install. I have added a notification ringtone that CM7 does not have, it modifies the build.prop on the fly to change the LCD density to what I like and to add HTC so that Netflix works properly. Until Dal added the OC kernel to the nightlies I used to add that too. All automated. Never have had a problem and have been doing this with every nightly since 108.

EDIT: I have since discovered that with the new version of Netflix (1.3), it's no longer required to edit the build.prop to HTC so I removed it from my script.
[Nook Color Android Development] RASTAVIPER:
Is Bluetooth having longer range with latest nightlies? How far can you keep your BT devices?

Haven't tried after Phiremod had only a few cm range.

Sent from Nook Color on Cm7 Nightly 129 @1.350Mhz
[Nook Color Android Development] J-ROCK:
I'm about to test BT in my truck with JVC stereo unit, previously it didn't have much range, and sound statically

UPDATE: seems to still be the same to me.
[Nook Color Android Development] Colchiro:
^^^^ This ^^^^ is the preferred way to install. :D

I always format system, cache and wipe Dalvik cache (under advanced menu) before updating.
[Nook Color Android Development] dvdivx:
Don't forget to fix permissions though unless you're going to reinstall everything.
[Nook Color Android Development] Ronin3178:
I don't run the fix permissions everytime, and I don't have problems 99% of the time.
[Nook Color Android Development] Ronin3178:
Ok, just had something weird happen with N141, installed from cwr, wiped cache/davlik 3x each. Rebooted, and within 30 secs of coming up, screen went black, and didn't turn on until I held power for 10secs. Here is the last_kmsg, can someone take a look that might understand what happened? I don't really know what I am looking at, other than it's what Dal has asked for before when a SOD happens, although I know wasn't a SOD because it happened as I was using the Nook.
[Nook Color Android Development] keyodi:
Some good news: You no longer need to modify the build.prop to get Netflix to play. It seems that the latest version fixed the fast forward issue. One less thing to change after flashing a nightly.

Here is the latest netflix apk: http://xdaforums.com/showthread.php?t=1177955
[Nook Color Android Development] edgie168:
..you wipe system when updating nightlies?

You must really enjoy reinstalling everything all the time, huh? O_o
[Nook Color Android Development] clamder:
wiping the data partition would require you to reinstall everything. system is just the rom partition.
[Nook Color Android Development] gudism:
Surprised no one ever mentions Maxthon for tablets. In my experience it has been the best browser. Dolphin HD just didn't suit me.....was slow and bugged out too much for my liking.
[Nook Color Android Development] leapinlar:
You are wasting your time manually formatting system, wiping Dalvik and fixing permissions. If you look at the scripts in the nightly install you will see that it first backs up your gapps, then formats system, installs the new nightly system and then restores the gapps. Then it fixes permissions. If you have checked the "wipe Dalvik" box, it also does that. But I guess some people believe in both belt and suspenders.

The only reason I check the gapp box is so I can use the modified zip to customize my install. As I said in an earlier post, I install a new notification ringtone and change the LCD density automatically using the customized gapps zip.
[Nook Color Android Development] christoophat:
running n140, and for some reason whenever I (re)boot up my NC, wifi isn't enabled by default any more. I have to go in each time manually & turn it on. I never had to do that in past builds. Any ideas?
[Nook Color Android Development] oldman_58:
You might try this:

Open up Terminal

at the $ sign type:

su

Then cut and paste the following (or type this in)

sqlite3 /data/data/com.android.providers.settings/databases/settings.db

delete from system where name = 'airplane_mode_on';
.exit

Then

exit

exit

You will need to reboot

Hope this helps
[Nook Color Android Development] christoophat:
Thanks, this seems to have fixed it. So is this problem w/ this particular build, or did I change some setting inadvertently, or?

Using a terminal emulator on this screen is a nightmare for me, tiny font + bad eyes = fail. Am suprised I was actually able to type it in correctly, since I could really see what I was typing :p
[Nook Color Android Development] leapinlar:
Thank you for this. I had the same problem and did not know it. I just noticed it was not on a lot after a reboot. This fixed it.
[Nook Color Android Development] christoophat:
I remember now that one day last week , I had a Dr's appointment, and switched it to Airplane Mode while having to sit for almost 3 hours awaiting my Doctor :mad:. I later switched it back. So is Airplane Mode broken? Or again is it just this particular nightly build?
[Nook Color Android Development] junkrobot:
I have had a strange with issue nightlies since about 136 where plugging the NC into my computer to transfer files over totally breaks the battery reporting. After I unplug it, after a minute or so, it just says 100%. It's pretty frustrating. Any clue as to why this is, anyone? Battery issues forever and ever.
[Nook Color Android Development] Divine_Madcat:
it has always been this way..
[Nook Color Android Development] oldman_58:
See Post 4435 it will fix your issue.
[Nook Color Android Development] boxcar8028:
just download android assistant. this is a free app in the market. just hit tools and you'll see if airplane mode is on, just turn it off. done. fixed.

https://market.android.com/details?id=com.advancedprocessmanager&feature=search_result
[Nook Color Android Development] doncaruana:
I noticed that too, but it went back to normal after a short bit.
[Nook Color Android Development] darkamikaze:
I'm having really bad battery drain on 136.. even when the screen is off.. the thing drains like there's no tomorrow.. anyone else notice anything?
[Nook Color Android Development] leapinlar:
I had a similar problem when using an ordinary micro-usb cable to charge with instead of the nook cable. It would jump to 100%. This was during the period when everyone was complaining about the premature battery death and before the devs fixed the problem by periodically reading a file in one of the partitions. It still happens but the fix of reading the file periodically corrects it. I have stopped using that kind of cable to charge with. I suspect that our problems are related.
[Nook Color Android Development] rhester72:
I have also seen this, and also only with a 'normal' (read: phone) USB cable attached to a laptop. It 'fixes' itself immediately after a reboot.

Rodney
[Nook Color Android Development] junkrobot:
That's so strange. This happens with the actual NC cable for me. It took ages for it to get up to being "green" this time, at which point I wiped the batt stats again.
[Nook Color Android Development] christoophat:
Seeing similar behavior w/ n140 too. Deep sleep appears to be working, but it seems that overall the battery drains quite a noticeable bit faster than w/ RC1 & earlier nightlies .
[Nook Color Android Development] miniaturepeddler:
Thanks this fixed a recurring problem that plaqued my NookColor.

Plus it adds another nice tool to my library.
[Nook Color Android Development] o0adam0o:
Does anyone have CM7 working with Motorola S9-HD? Im not getting any sound frm my Nook Color. It pairs and connecs but no sound. Then it disconnects on its own. Headphones r working fine with my Evo 3D.

Thanks.
[Nook Color Android Development] ianPhillips1:
hmmmmmm.....

Dev's does this mean anything for us nook users? Its an edit on the flyer that activates the mic on a Bluetooth headset. I fear its ony good on an htc rom.

http://xdaforums.com/showthread.php?t=1185688
[Nook Color Android Development] dasingleton:
Updating Nightly

Nook Noob Here…

I installed CM7 on my sdcard with version 7.03. Everything is working fine.

However, when I tried to update to the latest nightly (i.e. 141)..it doesn’t work.

Here is what I did…

Downloaded nightly and place and sdcard and flashed (thru CWM Recovery) after wipe dalvik & cache.

Rebooted…however it still shows verison 7.03.

Then I tried placing the nightly zip (141) on the boot partition of the card. I initially thought nothing happened…however, when I ejected my sdcard to boot back into stock nook…it instead showed…the latest nightly… !!

Any advice / hints/ suggestions will greatly be appreciated.
[Nook Color Android Development] bigbob23:
When you updated with CWM, it wrote to the internal ROM. Probably the easiest way to run from, and update to, your SD card is described here: http://xdaforums.com/showthread.php?t=1000957.

If you want to get back to stock, see http://xdaforums.com/showthread.php?t=914690.
[Nook Color Android Development] DigitalMD:
I tried the change to build.prop on my Nook. No effect. BT Mic not working, audio plays fine, just like before.
[Nook Color Android Development] dasingleton:
Thanks...went back and did it this way. Works like a champ!
[Nook Color Android Development] andyrubin1:
i have to always "safely remove" 2 drives from pc for the nook separately, can I just do it with one click?

besides, after safely removing them, can I re-enable usb storage without re-plugging the nook in?

thx in advance.
[Nook Color Android Development] Nburnes:
I do it just to be "safe" yanno? Also, yes you can just re-enable usb storage without re-plugging.
[Nook Color Android Development] Divine_Madcat:
20% per hour battery drain?

So, i made a general mention of this in a different thread, but i think it warrants a post here.

First off; what kids of actual USE times are people seeing? Using a battery monitor widget (for the excellent graphing), when web browsing, i am seeing around a 20% hour battery drain, with the screen at ~40% brightness.

OK, So i just did a test, of how i would use my nook at lunch for instance (web browsing, contacts updating, etc), to scientifically measure out how my battery use is.

Start: 8:56 - 90%

End: 9:35 -80%

10% / .5 hour (still seeing a very smooth 20% drain).

Activity: Using a WiFi connection from my phone (hotspot), use Opera Mobile, and browse a few web pages (in this case, 3 tabs). Nothing crazy; just load a page, read, change tabs, etc.

Battery use (according to android, for the total of 1H 12M 21s on battery)

Display (40% brightness) 72% (45m on)

Opera Mobile 15%

Cell 4%

Android Sys 3%

Android OS 3%

WiFi 3%

Launcher Pro: 2%

Phone 2%

CPU spy for the total time reports:

1200Mhz: 0:02:13

1100Mhz: 0:16:48

800Mhz: 0:01:03

600Mhz: 0:06:29

300Mhz: 0:24:16

DS: 0:30:07

My Voltages for each stepping:

0.9125

1.0625

1.2125

1.2875

1.325

I more than welcome any other input people have. Basically, if i use my nook for any time in the day, i will probably have to throw it on the charger a night. It IS sleeping fine, and i can pick it up after letting it sit for 10 hours, and only lose a point or two.. but in use.. ouch..
[Nook Color Android Development] rhester72:
Wow. Your method was very precise, yet your actual usage appears to be roughly double of what I'd expect, even though your display % ratio is quite within expectations. You didn't mention what brightness level your testing was at, but I'm assuming it is still ~40%. Can you stand to run it lower (basically, the dimmest setting you can set with the notification icon/button) for an hour of testing to see if it makes a difference? My own experience says that utilization drops about 40% from 100% brightness to 50% brightness, but further battery gains from going below 50% brightness fall off rapidly, saving maybe another 5% battery per 25% brightness beyond the 50% threshold.

Rodney
[Nook Color Android Development] Divine_Madcat:
Rodney - you are correct, i am at 40% brightness (its in there, just burried). I can try going lower, but in real use, i would hate to do so.

Oh.. and an odd thing - my notification bar does not have a brightness button (only the wifi, BT, location, and sound). No doubt a setting i have missed somewhere.
[Nook Color Android Development] rhester72:
Settings/CyanogenMod settings/Interface/Notification power widget/Widget buttons, put a check next to "Toggle Brightness". (Easy to find, right? ;)

Rodney
[Nook Color Android Development] ziggy34:
I see from your above post that you have cell standby. I have not tried this with CM7 but did it on my Acer tablet and it helped battery life. I will be trying on the nook tonight.

[*]Disable Mobile Data if needed (add ro.carrier=wifi-only to /system/build.prop