yashsingh1/xdaforums huggingface dataset:
[Nook Color General] jleecong:
If you want a tablet now/today I think the NookColor is a great choice if you are willing to hack on it a bit. My only suggestion is to NOT buy a tablet from China... I'm still cleaning up from that mistake after almost 2 months! (Damn you Pandawill!)

While I haven't done it you can unroot the NookColor.

It may never, just as there are never any guarantees that a device will be updated. Thankfully we have XDA and some great ROM cooks!
[Nook Color General] Musicman247:
Only you can decide if it is a good time for you.

I got the Nook Color as a Christmas present, but would have bought it myself, probably. I had heard of it being rooted and wanted a fairly cheap tablet.

Right now the Nook Color is the cheapest Android Tablet with the best build quality (for the price).

Froyo is coming this month according to a few people. Rooting now isn't an issue because you can always go back to stock.

My suggestion, wait until after CES and see what is brought to the table if you are wavering. But know that if you are always waiting for the "best thing", you will never buy anything, because new and upcoming products are always being announced. :)
[Nook Color General] Geezer Squid:
The NC is a good little tablet. There are better ones and there will be more coming soon.

It's an excellent time to root the NC. It can do so much more than B&N enabled. We don't know when the/if any update is coming. But we do know that custom roms are just around the corner. As soon as the new Clockwork Recovery gets sorted, there will be custom roms. The new recovery is a game changer for the NC.

I think 2.3 will come to the NC in the form of a custom rom. I do not have much faith that B&N is going to push it. I mean they still haven't done 2.2 and how long has that been out for other devices?
[Nook Color General] elcape:
That's what I'm looking for a budget tablet, and you are right about the new gadgets ;)

I'm sure that the dual-core tablets will be way more expensive than US$250, and I'm not welling to spend more than that for a device to browse the web, email and videos.

Another question, what video formats(codecs) are supported on the rooted nook??

Thanks for the answers
[Nook Color General] elcape:
something like Archos?
[Nook Color General] HotShotAzn:
Ask yourself what you want in a device. Are you using it as an ereader first, tablet second? Or tablet first, ereader second? I’ve had many, MANY Chinese tablets (G10, G11, Xpad, etc) and they are all junk. In the end, I still only used it as an ereader.

I wont get into an argument about Archos vs NC. There are other threads that compare the two. However, know this about technology: if you keep waiting for the next best thing, you’ll always be waiting. Buy now and make a stand that you wont care about another tablet for one year. You’ll be much better off with that mind set.

That being said, know what you want and find it:

-	7” or 10”?

-	Resistive or Capacitive screen (obviously Capacitive)

-	Large user community or you don’t care?

The NC fits what I want and use it for. I’d recommend it as an ereader AND a tablet. All these fancy options like HDMI out are rather useless to me. I have my netbook with infinitely better specs than any tablet out there.
[Nook Color General] elcape:
I not looking to read on it, (book or magazines) just as a tablet, browsing and all the other good stuff

i dont know archos quality
[Nook Color General] spikey911:
The Nook was designed as a book reading device.

If you want a tablet, then buy a tablet, that way your not going to be disappointed.

Archos is a good choice, as is a few others out there right now.

Just because the Nook can function as a tablet, doesn't mean it will do everything you want it to do, and it certainly won't do it out of the box.

Nook is missing a Camera, Microphone, Native Functional Bluetooth, HDMI/Video out.

Its all up to you.
[Nook Color General] markiejones:
The nook is the best way to spend $250 on a tablet, if.....

these are important to you:

- Screen quality

- book Reading

- comic reading

- web browsing, other "connected" applications

- some gaming (is surprisingly robust in this regard, but compatibility issues are out there)

- Strong wifi reception

- overall build quality

- ease of basic rooting

- quality capacitive touch interface

and

These are not important to you

- Full out-of-box functionality

- Built in camera / gps / hdmi out

- having flash Right Now

- having native support for vid codecs other than mp4 encoded with mpeg4/h.264

- compatibility with future versions of Android

- the most processing muscle

The future will only increase the attractiveness of this device, with a 2.2 update from BN, custom roms, possible bluetooth etc.
[Galaxy Tab General] pakalrtb:
Since there is no such option in the recovery menu, I thought it would be useful to let you know how to reset your battery stats. It comes handy every now and then in order to calibrate the battery meter. IT'S IN NO WAY a magic formula to improve your battery life, but it's beneficial after a series of ROMs flashing or several charges cicles.

You need to be rooted :

1) drain your battery completed until the tab shuts down

2) charge your tab ( with the tab OFF ) completely

3) turn the tab ON (still with the charger connected ) and run Root Explorer

4) go to : /data/system/batterystats.bin and delete batterystats.bin

5) turn the tab OFF

6) disconnect from the charger

7) turn the tab ON

DONE !

If you do not have Root Explorer you can use the Terminal app of your choice :

1) drain your battery completed until the tab shuts down

2) charge your tab ( with the tab OFF ) completely

3) turn the tab ON (still with the charger connected ) and run the Terminal App

4) type the command : rm /data/system/batterystats.bin

5) turn the tab OFF

6) disconnect from the charger

7) turn the tab ON

DONE !

P_
[Galaxy Tab General] amanchen:
nice share bro thanks.
[Galaxy Tab General] andrisd:
Thanks a lot! This solved battery drain issue after flashing Overcome Kratos!
[Galaxy Tab General] cgigate:
I don't think it is necessary to wipe battery stats.

I changed my rom, battery life is pretty good!
[Galaxy Tab General] Manuele83:
Thx, useful!
[Galaxy Tab General] Alvin Lai:
There is a wipe battery stat in recovery
[Galaxy Tab General] SamDenial:
This is great and i will definitely give it a go. Very handy indeed.
[Galaxy Tab General] andrisd:
After wyping tab run more than 3 days. :)
[Galaxy Tab General] ryn888:
Same here bro. Im not into a root tab anymore.
[Galaxy Tab General] neurocutie:
Just wondering, your procedure is similar but not identical to others that have been posted, e.g.:

Specifically the ordering of the complete drain and the full charge are reversed. Does it matter?
[Galaxy Tab General] Mjoelnir77:
I also asked myself about that whenever i read such advices. I guess the most important thing is to have the tab recreate the stats file when it is loaded to the max. It will anyway afterwards need some time (read: charging cycles) until everything runs smooth again. But if the new stats file would be created with less than 100% charged then it would never get charged full thereafter.
[Galaxy Tab General] Kiattz:
nice share thanks.
[Galaxy Tab General] pvtjoker42:
this is a common issue, if you install a rom with less than full battery charge (though going back to stock firmware works at any batt %)

Not all tabs have CWM working to wipe battery stats from the advanced menu or the console. Root explorer/ES File explorer, and the ADB shell option work with stock rooted Tabs no matter if they are GSM/CDMA or have CWM..

Always glad to see good info posted up.
[Galaxy Tab General] maxima0002:
Hi guys,

I'm still new to my SGT.. Wondering is there any way to "reset/re-calibrate" battery without opening the unit (to unplug batt) and or if I don't have my SGT Rooted yet?

Mine is dropping to 3% from 35-40%... without any warning..

Thanks..
[Galaxy Tab General] adomila:
no batterystats.bin

Hi Guys/Gals,

I envy you :o I don't have the batterystats.bin file and I don't have any folders or files inside /data. I also have search the said file in vain. I have the default OS which is 2.2/2.3. Any ideas why is this so? Or is there any other way to totally wipe out the battery stats? TIA(thanks in advance)
[Galaxy Tab General] Edawg79:
It shouldn't be able to be done on a stock phone...nor should it be needed. You need root to see the data\system folder which contains batterystats.bin
[Galaxy Tab General] nhecas:
I've read somewhere that wiping your battery stats is useless, because that's what all roms do on reboot... is it true?

Anyways, I've flashed several roms and haven't had any battery issues.
[Galaxy Tab General] JJEgan:
Multiple posts on the subject .

Wiping battery stats does nothing for your battery .

Recalibration is via the battery itself after a few charges .

Nothing to stop anyone wiping the stats .

But read

http://www.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer

http://xdaforums.com/showthread.php?t=2256038
[Galaxy Tab General] nhecas:
Ah, that's what i thought :) Thanks for the post.
[Galaxy Tab General] Moondaughter6:
Worked like a charm

Thank you, Thank you, Thank you, After 3 weeks of trying various different battery calibrations, from various sources, I just happened on your page, and it worked

it still randomly turned off today, but at least it's staying on for longer than it did before. I have however still ordered a new battery as it's like 5 years, and many custom rom changes over the years I have also bookmarked this for future use :)

Mucho appreciation :D
[myTouch 3G, Magic General] renedlog:
Hi im interessted in. How can i flash a rom via the update.zip file??

I have a goldcard, so i can flash every update.zip i want.

Can i just rename the (for example) ''FroyoRider_FeeyoCM61_6.35_34_v2.1.zip'' to update.zip and flash via recovery?
[myTouch 3G, Magic General] DonJuan692006:
Yes you can and if you've got a custom recovery you don't need the Goldcard to do it. Most recoveries though will recognize the .zip with any filename so you won't need to rename it.
[myTouch 3G, Magic General] renedlog:
.. yes i know the other method... but i have never found a method to restore the orginal recovery, so i want to keep it.

but the phone dont accept my goldcard :mad: or the file... the recovery said. the file isnt signed.
[myTouch 3G, Magic General] renedlog:
Thanks a lot. This is an answer!
[myTouch 3G, Magic General] yurifranzoni:
Let me ask you about the goldcard now: I have a HTC Magic here which currently has an incorrect SPL and radio combo due to a failed official update from HTC Brazil (SPL 1.76.0010 and Radio 3.22.20.17, SAPPHIRE PVT 32A SHIP S-ON H)

I've found in another thread in the xda-developers forums a SAPPIMG.ZIP built by Rogers Canada for their Magics. Looking inside the zip, the android-info.txt file says it's meant for a SAPP50000 model. But my Magic has the model ID SAPP60000... then, when I try to flash it to my phone (using Fastboot commander ;) ), it rejects the file.

I've created a goldcard using another Magic (identical but working OK) that I have here. The messages I get when trying to flash the Rogers zip are these below:

###Calling fastboot with: flash zip C:\android\SAPPIMG_Sapphire_Rogers_WWE_3.54.631.3_R_Radio_63.18.55.06Q_6.35.16.19_release_144134_signed.zip###

sending 'zip' (110447 KB)... OKAY [ 19.522s]

writing 'zip'... INFOadopting the signature contained in this image...

INFOsignature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 52.576s

The signature error is due to the differences between the model ID of the file and my phone, or have my zip file been modified since signed by Rogers?

Thanks a lot!
[myTouch 3G, Magic General] mumilover:
You need to rename it as sappimg.zip (not sappimg.zip.zip) and flash it from hboot mode. It's only there the goldcard will take effect...

But sadly, there is a BIG chance this will fail.

The spl has different partition layout which will make the flash of the radio fail!

What you have to do is to match the spl with the radio, then flash a new spl/radio combo.

In your situation, that's gona be hard... you have perfected spl! Plus any update will start with the radio which is likely to fail....

In other words, you kinda fu*ked.
[myTouch 3G, Magic General] yurifranzoni:
mumilover, I've renamed it to sappimg.zip and this is the result:

###Calling fastboot with: flash zip C:\android\SAPPIMG.zip###

sending 'zip' (110447 KB)... OKAY [ 19.516s]

writing 'zip'... INFOadopting the signature contained in this image...

INFOsignature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 52.567s

I've tried flashing it through Fastboot commander (which is the same thing than typing the commands in the DOS prompt, right?). I expected that it would not work, because, well, I've tried nearly everything I found here in the forums :(

I'm still trying to find a RUU or HTC signed zip that contains the 1.33 SPL, so it would match the 3.22 radio. Does anyone know where to find something like this? Updating my radio do 6.35 is not an option...

I've reached this situation because of a ****ed brazilian official HTC update to Android 2.1. Before I tried to install it, my phone had CyanogenMod 6.1, with SPL 1.33 and radio 3.22. My mistake was to apply the update directly to the phone, without flashing the new SPL/Radio BEFORE.

During the update, it updated the SPL to the new 1.76 version, but when it starts to update the radio to version 6.35.xx, the phone screen becomes blank, then goes slowly white. I've tried that many and many times, still the same result.

I've tried applying the latest Rogers RUU (available for download in shipped-roms.com), which has similar SPL and Radio versions than the brazilian update, but no luck: even with the goldcard inserted, when it reaches the radio flash phase, the screen blanks again :(

Is there anything that could be done before sending my brick to service? They are replacing the logic board of every phone they receive in this situation - believe me, they have received many of them... I know a bunch of people that made the very same mistake as I did.

Thanks!!!
[myTouch 3G, Magic General] mumilover:
Again... as i wrote earlier, this has to done in hboot mode (volume - & power) with a goldcard.

You CANNOT do this with fastboot commands!

And yaa, i told you that you were screwed. Very bad combo which seriously messes with the your ability to fix it.
[myTouch 3G, Magic General] yurifranzoni:
Right... my mistake, I forgot to mention that my brick does not boot in hboot mode anymore. It keeps stuck at the RUU USB screen, with the icon of the microchip and the red cross sign at the bottom.

Worse, it does not have the custom recovery anymore, so I'm not able to go there and do a "flash zip from sdcard".

Finally, if I try to do a "fastboot boot recovery.img", using any custom recovery image, what I get is a eternal "booting..." message, and the phone does not load the custom recovery image.

Any other ideas?

Thanks again!
[myTouch 3G, Magic General] yurifranzoni:
GOOD NEWS!!

I've managed to FINALLY make it boot the system! I don't know why, but I tried the following and it restarted in CM 6.1 (the ROM installed before I tried to apply the official update):

- with the phone turned on, connected via USB and froze at the RUU USB screen, type the following in a command prompt:

fastboot oem boot

It will display a lot of data and then the PC screen will show FAILED (status read failed (Too many links))

- Then, I typed:

fastboot boot recovery-RA-sapphire-v1.7.0H.img

It told me "(waiting for device)". I left it there....

- Then, I fired up the Radio Switcher app and chose the "Shutdown device" option. My idea was to turn the brick off to try anything else...

BUT it took about 20 seconds and RESTARTED, then the CM logo shown up... and some seconds later it was RUNNING CM 6.1 again! Like it was before I tried to update!

I still can't reboot into recovery to flash the right SPL version, but that's a chance of success, isn't it? It still has the bad SPL/radio combo, but at least, it's starting!

How can I flash the right SPL into the phone WITHOUT restarting into fastboot or recovery? Is it possible?

Thanks!
[Wildfire General] 23Kie:
Hey, I have readed for solutions, and downgraded method that there is in this forum is valid for Desire no for Wildfire, my question is.... It will have solution for guys kile me with froyo 2.2 and get root for a new revolked or it will be imposible? Thanks for all, and happy new year
[Wildfire General] 3xeno:
Its unknown yet, and, theres no ETA. You will just have to be patient and wait.
[Vibrant Q&A, Help & Troubleshooting] mac1133:
I'm using Eugene's Ginger R2: in the keyboard when I tap on a word and replace it with another, the word is inserted into the oringinal word instead of being replaced. How do I fix this?
[Vibrant Q&A, Help & Troubleshooting] sunny4:
Bump...I too noticed this...surprised no one else hasn't comments on this till now.
[Vibrant Q&A, Help & Troubleshooting] mac1133:
One developer who made a keyboard gingerberad keyboard for 2.1 reached out and commented to me in a previous PM saying: I hope someone could use this code to fix the bug

InputConnection ic = getCurrentInputConnection();

1994	1994

if (ic != null) {

1995	1995

rememberReplacedWord(suggestion);

1996

+ if (correcting) {

1997

+ EditingUtil.deleteWordAtCursor(ic, mWordSeparators);

1998

+ }

1996	1999

ic.commitText(suggestion, 1);

1997	2000

}

1998	2001

saveWordInHistory(suggestion);
[Nook Color General] jleecong:
Per the Nookie Froyo thread they have a suggestion to increase the refresh rate to 68000 to stop/reduce flicker.

I noticed a similar flicker on "stock" 2.1 and checked /sys/devices/omapdss/display0/timings only to find out it is also set at 48000. I increased it to 68000, but it is reset after each reboot.

What is the proper refresh rate? Anyone else notice a flicker on the stock ROM?
[Nook Color General] paleh0rse:
what process did you use to modify the file?
[Nook Color General] jleecong:
I used the following from the thread I linked.

adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
[Nook Color General] paleh0rse:
Did you su and mount as r/w first?
[Nook Color General] khaytsus:
You don't remount /sys ;)
[Nook Color General] dennisi01:
so does anyone know how to make this stick after boot?
[Nook Color General] JoshMiers:
See the thread I just made: http://xdaforums.com/showthread.php?t=901791
[Nook Color General] gedster314:
Thank you both. Seems to work. Now I know how to run my own scripts afterboot. :D
[Nook Color General] DatterBoy:
Does that mean we add the

at the end of the clrbootcount.sh text to have it run that command to fix the refresh and make it stick?
[Nook Color General] greenmky:
I did this (as I posted in the nook flicker thread):

I did a CAT on immediately after, and it had defaulted instead to 66461 instead of 68000 (maximum rate for the chip?)

Of course it also cleared upon reboot. Should I have seen a flicker improvement right away?
[Nook Color General] here.david:
After clearing up all the posted suggestions listed here is what worked for me

I also get 66461

------------------------

increase the refresh rate to 68000/66461 to stop/reduce flicker.

---------------------------------------------------------------------------

adb pull /system/bin/clrbootcount.sh

gedit clrbootcount.sh (assume you stay in specific dir)

add this to end of file and save

---------------------------------------------------

#run other commands

setprop persist.service.mount.umsauto 0

---------------------------------------------------

NEXT

adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system

adb push clrbootcount.sh /system/bin/clrbootcount.sh

adb shell chmod 755 /system/bin/clrbootcount.sh

adb shell mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system

adb shell reboot

--------------

NEXT

adb shell - NOW AT THE su # PROMPT (HAD NO LUCK WITH THE ADB SHELL and then commands all in one line)

cat /sys/devices/omapdss/display0/timings

mount -o remount,rw /dev/block/mmcblk0p5 /system

chmod 0755 /sys/devices/omapdss/display0/timings

echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system

reboot

-----------------------------------------------

NEXT

cat /sys/devices/omapdss/display0/timings

66461,1024/70/200/40,600/10/11/10

----------------------------------------------

Three reboots and I still have the changes...

Read all the posting listed if you want/need more details....
[Nook Color General] khaytsus:
You do not need to remount /system to write to /sys, and if you have chmod at all (unlikely) it would not be 755, it would be 644.
[Nook Color General] DatterBoy:
Tried all that and it did not stick. The final CAT showed a reversion to 48000. Still don't understand how the change to the clrbootcount.sh is supposed to make it stick but it isn't working.
[Nook Color General] khaytsus:
It wouldn't. The change to the clrbootcount.sh only changes the automount, the change to the /sys var is completely temporary. I assume one could also put it in the clrbootcount.sh, assuming it isn't modified later by the system (negating the change made from the clrbootcount.sh script).
[Nook Color General] DatterBoy:
Yeah. not sure how anyone is getting this to work but i can't figure it out. As a warning, modifying the clrbootcount.sh and trying to incorporate the fefresh change script has force firmware into boot loop to needing a factory reset twice now. Wonder if anyone else had the same experience.

The flicker is annoying and the refresh change works, but just won't stick.
[Nook Color General] JoshMiers:
To get it to stick, follow the steps on my other thread http://xdaforums.com/showthread.php?t=901791.

When you edit clrbootcount.sh, add the following to the end:

echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

The final file (if you also want to disable automounting), will look like:

#!/system/bin/sh
##################################################################################
#
# File clrbootcount.sh
# Description	Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
#run other commands
setprop persist.service.mount.umsauto 0
echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
[Nook Color General] cutterjohn:
While I've never really looked at this, but isn't the "refresh" "rate" largely irrelevant with LCD based screens? I'd always just assumed that even assigning them a "refresh" "rate" was just a place holder to make things work and not break CRT compatibility in drivers/display engines.
[Nook Color General] DatterBoy:
Did all this from a super clean root. Did not hold.
[Nook Color General] DatterBoy:
Don't know if that is true, but I have seen flicker on other LCD panels that could be addressed with refresh changes. The echo command does work instantly on the NC but just won't hold for me.
[Nook Color General] jleecong:
I have been playing with this and while the changes in clrbootcount.sh do stick, I'm unable to get it to either set the refresh rate or run a script that sets the refresh that I KNOW works from the terminal. Seems idealy this should be set in the ROM. Back to the terminal...

I should add I'm running 1.0.1 (Auto-Nooter 2.12.25) and also tried it in Nookie Froyo.
[Nook Color General] jleecong:
I copied that code section exactly from your post and uploaded it, not only is the refresh rate not being applied, but USB is also still auto mounted. :(

What version are you running (1.0.0 or 1.0.1)?
[Nook Color General] DatterBoy:
Agreed. The chnages made to the text of the clrbootcount.sh do stay but adding the echo command to it does not seem to do anything to the target file. Thus, no screen flicker fix without running ADB or terminal.

I ended up just making a screen command I can launch from terminal and will have to do it if the Nook ever boot cycles.