yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] dtownsend:
The beta 2 build worked really nicely but for some reason since beta 3.1 the problems with false screen presses has become really bad for me. I can't use it for more than a couple of minutes without turning the screen off and on now.
[Nook Color Android Development] MedLine:
hey welcome back

maybe this from fattire couple days ago:
[Nook Color Android Development] mooglesoft:
Does the new beta3 build fix video playback? I'm having problems on beta2 with videos in the stock player. I didn't have any problems playing the same files with CM 7.0.3.
[Nook Color Android Development] TJNooker:
I can report that my Nook is definitely sleeping with this kernel. I left the Nook at 100%. After almost 6 hours it was at 99%. :)
[Nook Color Android Development] ADude:
If you find the revert to stock threads, unzip the zips and they should include u-boot.bin for 1.01 or 1.1 that are for .29
[Nook Color Android Development] aludal:
thanks, I've got it myself, as there were not a single change in uboot since B&N stock while it was on .29. Have decided not to revert -- too much hassle, hopefully, crackle.com will stop stuttering/hang automagically, or with new codecs. Or new dalingrin's beta, lol. On the other hand, it's a pity Google has so many movies still outside YouTube. That is, it links to Crackle. On the other hand, YouTubeTablet apk out of Android 3.0.1 (pre-Renderscript) needs a very careful backporting, lol. Our regular YouTube apk is too dumb and doesn't have an access to youtube.com/movies -- while offering best video quality of all streaming video without HW overlay on NookColor.
[Nook Color Android Development] 360Razir:
Moved to OC thread.
[Nook Color Android Development] bachviet:
I went from phiremod 6.2 (cache and Dalvik-cache cleared/formatted) and I got my first "black screen of death" aka Nook Color unresponsive from sleep (1.5 to 2 hours). It's probably because I didn't format everything.
[Nook Color Android Development] c0ldburn3r:
No offense but scores don't mean jack. Drop in a class 10 card and your scores go way higher.

3.1 has stay awake permentaly enabled while on usb. Reading the op helps ;)

I would stay away from oc kernels until this is stable. Sod kernel panics... no good.

Sent from my Nook Color
[Nook Color Android Development] ADude:
It has nothing to do with OC kernels.

I am using 1.2 u-boot.bin; 3.0.2.8 CWM, flashed from 7.0.2 to Beta 3.1 and I have been using stock kernel on both of those (925).

I have experienced the following problems mentioned by others in this thread, with the Beta 3.1 build:

- Just experienced my 3rd occurrence of black screen and no response to N key, each time had to hold down the power button to do a hard reboot.

- I also experience the Nook continuing to charge past 100%, although I confess to not having paid much attention to that before Beta 3.1 (were any changes made in charging by the CM7 encore devs, or is this controlled solely by hardware?)

- And I have experienced for the first time ever with ny Nook, wifi disconnecting while the wifi icon is still there in the status bar (disconnect and connect fixes it temporarily).

All three of those have been reported by more than other person above in the threads, so they seem to be verified issues with the Beta 3.1 build (particularly the first and third ones - in fact, the wifi disconnect is actually the most annoying, since the black screen freeze only happens when one is not using the Nook).
[Nook Color Android Development] 360Razir:
Um, yeah, that is why I said it is a point of reference for my NC and my NC alone. Others were posting that they were getting better speeds on newer kernel, but I am not. I don't even care what the number is, just was hoping the number wasn't lower than older kernel.

As for perm stay awake, I enable that on all my builds, so all this new beta did was just save me a step. But, I was always able to charge fully via USB, esp after 6 hours and the battery being more than half full.

No SOD so far. Moving to the OC thread now since I am going to stick with that kernel for the time being.
[Nook Color Android Development] :
No offense but class ratings don't mean Jack. Sandisk vs pny. ..c'mon.
[Nook Color Android Development] chisleu:
I formatted system/data/cache and installed from SD card, installed 3.1 + OC kernel.

I think the lockup problems were related to the battery stats being off. ADB Shell didn't help either. That buggy piece of crap can't even boot up without claiming it crashed last time. Looks great, but doesn't work for me.

I have no issues now (yet.)

I also modified the build.prop and signed up for a netflix 1 month trial. haha :)
[Nook Color Android Development] breebauer:
I also had an orange cable with battery stats showing 100% and 4200mV

Just out of curiosity:

Does the orange light mean its still charging, even if the battery is 100%?

(if it is, should I unplug it after it says 100%?)

Is 4200mV is the correct voltage for a fully charged battery?

I'm wondering what's the best way to reset the battery stats- when it's fully charged?
[Nook Color Android Development] 12paq:
maybe this is what the devs need to help fix this. so heads up next time, and pull the info needed.
[Nook Color Android Development] rhester72:
The manufacturer's spec says 4010mV.

Rodney
[Nook Color Android Development] HarleyChick:
I'm curious: I haven't had any issues (yet) with SOD, but I know from the OP that "Stay Awake" is supposed to be permanently enabled with the Beta 3.1 build. But when I checked under Settings > Applications > Development, Stay Awake is not checked on my NC. Should it be? I'm just trying to stay ahead of any potential problems......

P.S. And before anyone directs me to read the entire thread, I have (and do) on a daily, well make that almost hourly, basis.
[Nook Color Android Development] ansleyj44:
I made sure to have it selected just to be safe, but i forgot last night when I plugged in the charger. I had no problems this morning with waking it up, although it doesn't seemed to have entered deep sleep. My guess is it is enabled, but just doesn't show it?
[Nook Color Android Development] newellj79:
My understanding is that while charging it will not go into deep sleep. Unplugged, there should b know problems with it getting to deep sleep.
[Nook Color Android Development] cpuks:
I have blue screen and reboot when I plug my nook to windows 7 netbook - anyone have this?
[Nook Color Android Development] Ronin3178:
I have always let my Nook charge until the cable is all/90% green, I even turn the Nook all the way off when charging (from the stock AC plug).

4200 is when my cable turned mostly green, the battery booster app I run had said my battery was 100% back at like 4150 or so. As far as resetting battery stats, from what I remember seeing others post, and what I did. Once you have the phone/nook fully charged, boot into CWR and reset.
[Nook Color Android Development] HarleyChick:
That's what I was thinking. I just didn't want to do anything wrong by going ahead a checking it. Oh, well, I guess I'll find out if it doesn't wake up.
[Nook Color Android Development] yourm0m1:
losing wifi

i am losing wifi...

currently cm7.1.0 beta 3 w/0513 kernel 300/1200 smartass

heres a logcat http://pastebin.com/mtbT2wJV

anyone got a clue? gonna turn off the oc for now

sidenote...adb is not working either.
[Nook Color Android Development] bitnerd:
Ok, now when I fully charge my nook it only goes to about 96% before I get the green light and it seems to have stopped charging. I've rebooted twice so far to cwm to reboot battery stats but it hasn't seemed to change anything.
[Nook Color Android Development] Ronin3178:
Try turning it off completely once plugged into charge (on wall charger, not USB to laptop/PC) if it was green while on, it may not be once off.
[Nook Color Android Development] :
OMG!

Can we password protect the beta rom/kernel, and you need to answer a question to prove you know what you're doing/getting yourself into?

I just checked out the Q&A and General, and EVERYONE is f'in up this build. Saw 4/24 kernel with beta 3.1, OC kernel .32 w/nightlies/stable, 5/13 OC with Phiremod...

This is nuts!
[Nook Color Android Development] lafester:
I'm pretty sure the battery % indicator is not accurate enough to know the difference.

I say forget about it and be happy :)
[Nook Color Android Development] Colchiro:
Using root explorer, go to "system", change to R/W (read write) at the top, long press on the build.prop and choose "edit". Change your dpi, press menu button and choose "save", exit. Change to R/O (read only ) by tapping the button at the top, reboot.

I believe 240 dpi is about the max you want to go. Bad things like boot looping or the virus that steals your identity, car and credit cards (but leaves your kids :D) happens.

Enjoy. :D
[Nook Color Android Development] lafester:
I think you are exaggerating a little. Let them play and learn.
[Nook Color Android Development] Backwardsblade:
I agree, I learn the most about this platform after i COMPLETELY mess up the first 10... or 100 times haha
[Nook Color Android Development] Sigvard:
Got SODs with the OC Kernel and now I'm stuck on a bootloop and whenever I try to flash something on CWR it crashes and reboots. Help?
[Nook Color Android Development] Ronin3178:
Start over, boot with SD card, flash whatever you were trying to flash. Or as a last resort, off of same bootable SD, wipe boot and everything else, reinstall 1.2 uboot, whatever ROM and kernel.
[Nook Color Android Development] Animec:
Silly question perhaps, but...

... is it possible that some of the new "SOD" cases are in fact caused by the nook shutting down due to insufficient power? Eg. I and at least a few others have had our nooks shut down with the battery meter at around 30% (first time I've experienced that btw), and I've noticed that my battery drains faster now in standby than it did with the previous beta. So is it possible that in some cases it's just that the nook's drained faster than expected and then shut down with the battery indicator showing an incorrect reading?
[Nook Color Android Development] khaytsus:
Not to say it couldn't be, but in my case definitely not, both times I had good charge going in AND coming out once I rebooted.
[Wildfire Themes and Apps] daddyspud:
I now this is point less but I just brought lockbot pro and I'm little confused

I keep getting two lock screens one I downloaded and a default one but can't figure out how to just have one lockscreen

Any advice welcome thanks
[Wildfire Themes and Apps] kevin2516:
Sense roms seem to have problems with lockscreen apps, maybe you should download an app called no lock, to disable the sense lockscreen, that might work.
[Wildfire Themes and Apps] daddyspud:
Cheers Kevin I thought u mite b the one to reply lol
[Wildfire Themes and Apps] daddyspud:
Sorted it it was because I had lockpro free n lockbot pro installed lol al sorted now
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).

He has Odin. He has the Windows drivers installed. But I have some questions.

I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?

Best place to get the European firmware is here? http://xdaforums.com/showthread.php?t=846913

Does he need just a pit file, or other files (e.g. tar) too?
[Galaxy S I9000 Q&A, Help & Troubleshooting] iammodo:
JPY is the lastest UK rom pointless using anything else until its out for the UK

People here just love new numbers and letters.

if he is going from branded would be best to use a pit file. ( pit 512)

then flash the 3 JPY files.

I tend to debrand phones when I get them in as I don't think its fair being stuck on older versions.
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
So... download Odin + PIT from the top of that page I linked. Flash the 512 PIT using Odin with repartition. Download the JPY firmware from the same page. Flash the 3 files in there. Reboot. Done?

What about clearing cache? Factory reset?

Anything else?
[Galaxy S I9000 Q&A, Help & Troubleshooting] iammodo:
Flashing with Odin will do the factory reset.

Sent from my GTI-9000 Using that XDA app thingy
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
We've hit a problem :D

He's been trying the files on this thread: http://xdaforums.com/showthread.php?t=846913

He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).

Now when he reboots his phone it doesn't boot - it just vibrates.

He's tried going into recovery and clearing the cache, user data, factory reset, etc.

He can still get into download mode and recovery.

Any suggestions?
[Galaxy S I9000 Q&A, Help & Troubleshooting] iammodo:
Flash pit with repartition selected.

Wait till you see a green box with pass

Unplug phone take battery out.

Then put it back on download

Click reset it Odin

Untick repartition

Select all three jpy files.

Plug in phone. Click start.

Leave till you see green pass.

Sent from my GTI-9000 Using that XDA app thingy
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
[Galaxy S I9000 Q&A, Help & Troubleshooting] iammodo:
Different to how I get them direct for Samsung. So wouldn't know sorry.

Sent from my GTI-9000 Using that XDA app thingy
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
Can we get the JPY firmware direct from Samsung?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Logseman:
No, but samfirmware.com has all those firmwares.
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
Yeah they have JPY. However it's just a 512 PIT file. Is that all he needs?
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
Thats what i flash JPY with .

Error solving with a rom install i usually wipe everything flash back to eclair with 512 pit and repartition . That works i then flash to Froyo no repartition .

jje
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
Still no joy :(

OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.

Did we do something wrong? We noticed in Recovery there is an error displayed:

E:can't mount /dev/block/st110 (invalid arguement)

E:copy_dbdata_media:cant mount DBDATA:

copy default media content failed

What else can we try to get to JPY?

The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
[Galaxy S I9000 Q&A, Help & Troubleshooting] mossy1963:
You only use the PIT file and choose re-partition when you have the 3 separate flashing files.

When you have the singe JPY tar file you do not select re-partition and do not use the PIT file - do the following:

put phone into download mode

open Odin

choose your single JPY file as the PDA

make sure "re-partition" is UNTICKED

DO NOT select your PIT file

connect your phone to PC via USB

Odin will detect your phone - click start

let Odin do its stuff until your phone restarts

you are now on 2.2.1 stock

I always do an immediate factory reset.....it seems to sort out any lags or issues that you occasionally get after flashing

good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
When he tries to just the .tar without repartition or .pit, Odin fails. :(

When he tries to format the internal SD card from Recovery it says:

E:can't mount /dev/block/st110 (invalid arguement)

E:copy_dbdata_media:cant mount DBDATA:

copy default media content failed

It could be that repartitioning previously has messed stuff up? Maybe the wrong PIT (we used 512)? I've read in a few places that Clockwork recovery can fix this. Thoughts?

Or is there a 3 file JPY option we can use?
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
So, according to this thread http://xdaforums.com/showthread.php?t=784958#8180949 it seems we messed up the partitions by using the pit file originally with repartition. If JPY isn't a full firmware we'll need to flash back to a full firmware to fix it. For example he says "The reason for this screwup is because the JH7 tar package does not contain params or dbdata files, it's not meant to be a full installer- it's meant to be an upgrade. When you partitioned you deleted your existing dbdata and params partitions on your phone, so when JH7 tried to set them up they didn't exist."

We're going to try JPU (somewhere said that's a full update) with 512 pit + repartition, then if that boots update to JPY (no pit, no repartition).
[Galaxy S I9000 Q&A, Help & Troubleshooting] extorian:
FIXED!!! :)

After putting the three-file JPU on it from samfirmware.com with 512 pit and repartition, it booted up into 2.2.1 fine. We then flashed the JPY tar (no pit, no repartition), and it's working.

Thanks for the help guys.
[Galaxy S I9000 Q&A, Help & Troubleshooting] footsteps88:
Thats great news. X
[Galaxy S I9000 Q&A, Help & Troubleshooting] chrisb1977:
Hi I am the friend that has caused the headache throughout this thread, I'd just like to say a big thank you to extorian and everyone else that provided input and solutions to getting the rom installed on my phone.

I'm over the moon with the update, phone runs better than ever. Thanks again.
[Nook Color Android Development] fattire:
For a list of what's changed recently, bookmark:

--->>>>>>>>>>>>> this link <<<<<<<<<<<---
[Nook Color Android Development] jerrygon:
Link to the latest nightly...

http://mirror.teamdouche.net/?device=encore
[Nook Color Android Development] epakrat75:
The current CM7 encore zip seems like it will write to mmcblk0p5 (NC's internal EMMC). Any chance of getting one that uses something like mmcblk1p2 instead to install on my EXT4 SD Card? Why? I'd prefer my internal eclair install to remain unaffected by these experiments.
[Nook Color Android Development] danbutter:
Ditto

10char
[Nook Color Android Development] fabienk:
can we remove the lock screen ? ( "none" in the settings doesn't work )
[Nook Color Android Development] altimax98:
A free app called no lock worked for me on other roms

Sent from one of those missing Droids
[Nook Color Android Development] adma84:
Anyone running nightlies yet? Any early reviews? Screenshots would be great too :) If you can even install n app to do that yet
[Nook Color Android Development] KitF:
I made an awful video:

http://www.youtube.com/watch?v=u1Z29zs70YE
[Nook Color Android Development] cainhunpi:
Its fine. I got no idea on how to install it. But when video works ill look Into it. Is there a way to move the taskbar down?

Nook Color via Xda App
[Nook Color Android Development] myteematt:
Install to EMMC Instructions

I dont get how to install this to EMMC. Can someone post a quick guide. Thanks in advance
[Nook Color Android Development] lafester:
instructions are posted in the ext4 thread.
[Nook Color Android Development] captive:
Hi, I watched your video on youtube, now I'm wondering what devs mean saying dsp video playback is broken, as you were playing a flash video.. can someone explain?
[Nook Color Android Development] ganovim:
At this point, an sf version would be much more practical.
[Nook Color Android Development] aludal:
Great video, and I subscribed to your collection of videos on YouTube. Thank you for not adorning it with some idiotic music.

However, out of what I heard, I didn't understand, you sounded like Flash (10.1?) is working (and it shows full YouTube Web page where it's needed), but YouTube itself is not working. Could you elaborate on this? Could you try to adb install other versions and tweaks of YouTube apk, like "HQ" YouTube, or "signed_YouTube", or whatever?

Please post more videos on Flash/YouTube/other (mv4, avi, etc.) videos playing, Flash Web pages and elementary Flash games.

Thank you. Have posted your video in my blog, and will be posting more.

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

fineoils.blogspot.com
[Nook Color Android Development] ChrisJ951:
From what Ive gathered (i could be completely wrong) it lacks video decoding drivers. Youtube.com works because its using flash and is based on the cpu. Where-as youtube apps do not use flash, and thus try to load a video codec which doesn't exist causing it to error. The youtube app alongside other non-flash video apps fail to load for me.
[Nook Color Android Development] faceman66:
My Installation Diary

For those that need more in depth instructions, I logged my entire install process and am sharing. If anyone has suggestions for changes, please let me know. I might have done something different from another person, but I had no problems getting the first release installed, running and overclocked.

Your mileage may vary, I am not responsible for anything you do to your Nook, even if you did follow my advice. I am not claiming to be anything special here, just sharing what worked for me and my Nook.
[Nook Color Android Development] aludal:
Sounds like a good enough explanation to me. Except for the part that YouTube presumably based on CPU (=software decoding?) is using Flash (? Flash requires specific hardware decoding support for its quasi-H.264 stream decoding, if none offered, it won't even install).

Missing "commercial" decoders capable to use HW assisted decoding (and rendering) in a "clean" CM7 nightly could be to blame, the question now is what decoders are missing and how to add them.

In any case, I would love to hear (and possibly see in video clips) some other experiences. Namely, my first impression was quite opposite: YouTube (inline, in a Web page, and not in apk) is now working whereas full Flash 10.1 doesn't install, or FCes if installed somehow, etc.

Lack of list with known unfixed bugs for the nightly turns the build into a puzzle. Sure the CM devs are in no way under any obligation to accommodate every piece of proprietary code (YouTube, Flash, Market, Gapps, etc.) but at least they might state simply that IVA2/DSP doesn't work yet in this initial build.

On the more positive note, I would love to hear and see the video of improved GUI responsiveness and some racing game showing nice response and detailed textures, etc. Neocore benchmark? Linpack?
[Nook Color Android Development] adma84:
it's so early on, I think we are lucky to even have nightlies. I doubt they will release any 'known issues' until an RC
[Nook Color Android Development] aludal:
yeah..., I thought so too. Still good to know that SGX GPU core has started to breathe (in GUI responsiveness and maybe in some games) instead of just sucking the battery juice for nothing.

Forgot to ask: has anyone rooted it to see and change LCD density to its physical 169.3333? Maybe some stuff with wrongly scaled lock screen, etc. will resolve better? Back arrow in a right upper corner is weird, hopefully Volume keys hack is still doable.

Forgot to ask how does new fake name "Encore" for the NC affect the completeness of the Market?
[Nook Color Android Development] jhnstn00:
I installed the update zip above but don't know how to get into that recovery.

Sent from Continuum 2.2 w/ Sensation 1.2 (Awesome)