[Q] when using nook for first time - Nook Color Q&A, Help & Troubleshooting

is it normal to get lag, typing, and touch screen issues on first boot up?....my nook (refurbished) started bugging out during initial setup..typing on its own, no touch response... after reboot all good
after cm7 install it did same thing and all good as well after a reboot
i got 30 days to see if happens again or not, just wondering if normal first time or if it could be hardware issue
thanks

djcyph said:
is it normal to get lag, typing, and touch screen issues on first boot up?....my nook (refurbished) started bugging out during initial setup..typing on its own, no touch response... after reboot all good
after cm7 install it did same thing and all good as well after a reboot
i got 30 days to see if happens again or not, just wondering if normal first time or if it could be hardware issue
thanks
Click to expand...
Click to collapse
Can be normal if you're plugged in while doing it... phantom touches have been reported when attached to power charger.

DizzyDen said:
Can be normal if you're plugged in while doing it... phantom touches have been reported when attached to power charger.
Click to expand...
Click to collapse
it was plugged in! could be it..thanks!

Related

Black Shroud of Death

FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?

[Q] Nook Color Stuck Key

Hello,
I have a Nook Color 8gb first gen that I have put CM 10 (10-20130414-nightly-encore) on. My problem is that sometimes the tablet seems to take on a life of its own and what it seems to be doing is to be persisting screen taps. So for example you will be typing with the on screen keyboard and all of a sudden it will keep hitting a key even while your not still touching the screen. This also occurs while playing games the game will keep on playing even while your not tapping the screen again I think it is persisting previous taps.
I have tried two CM 10 builds with no luck. I have cleaned the screen - no luck. I have rebuilt the tablet - no luck.
I was wondering if anyone else had the same issue and how they resolved it if at all?
Thanks
Check out Nook Screen Recalibrate from the market and make sure the screen is very clean. I know you said you cleaned it but they can be really picky.
Sent from my HTC Fireball
wmuflyer said:
Check out Nook Screen Recalibrate from the market and make sure the screen is very clean. I know you said you cleaned it but they can be really picky.
Sent from my HTC Fireball
Click to expand...
Click to collapse
Thanks I recalibrated the screen and tried it for a few weeks. Strange thing is that for a little while the frequency of the stuck key problem went down but it still happens. Not sure if there is anything else I can do might try a new Cyanogenmod build but I don't think that is the problem I have a kindle fire that has Cyanogenmod on it with no problems so maybe just the device.
Thanks

[Q] Boot loop - cannot access recovery or download mode

Hello, maybe this was posted a lot of times, I just wanna get a second opinion before getting this to the shop. My phone (GT-i9500) suddenly went on to boot loop. I cannot enter download mode nor recovery mode. When attempting to put on download mode, when it tells me to press volume up, nothing happens and it restarts again. I was partially able to boot to recovery but it only showed the TWRP splash page then it reboots again. Does this mean that I have a broken motherboard? Any suggestions?
golokipok said:
Hello, maybe this was posted a lot of times, I just wanna get a second opinion before getting this to the shop. My phone (GT-i9500) suddenly went on to boot loop. I cannot enter download mode nor recovery mode. When attempting to put on download mode, when it tells me to press volume up, nothing happens and it restarts again. I was partially able to boot to recovery but it only showed the TWRP splash page then it reboots again. Does this mean that I have a broken motherboard? Any suggestions?
Click to expand...
Click to collapse
Hi
Seems like a hardware problem ( most likely ) power button defective or battery
MAX 404 said:
Hi
Seems like a hardware problem ( most likely ) power button defective or battery
Click to expand...
Click to collapse
I'm currently letting it run to drain the battery. Would it help?
golokipok said:
I'm currently letting it run to drain the battery. Would it help?
Click to expand...
Click to collapse
Yes why not but if the battery is defective that will not fix it or help.
Did you try to go into recovery with the phone plug in to the charger? how it does behave?
MAX 404 said:
Yes why not but if the battery is defective that will not fix it or help.
Did you try to go into recovery with the phone plug in to the charger? how it does behave?
Click to expand...
Click to collapse
Still the same. Sometimes it would show the battery icon but only for a split second.
golokipok said:
Still the same. Sometimes it would show the battery icon but only for a split second.
Click to expand...
Click to collapse
Mate ,
It looks like is in constant reset.......seems like a defective power button, have it check should not be too expensive
golokipok said:
I'm currently letting it run to drain the battery. Would it help?
Click to expand...
Click to collapse
Draining your battery is always bad. It will damage your battery.
MAX 404 said:
Mate ,
It looks like is in constant reset.......seems like a defective power button, have it check should not be too expensive
Click to expand...
Click to collapse
That is exactly what is happening. Gonna get this checked tomorrow
golokipok said:
That is exactly what is happening. Gonna get this checked tomorrow
Click to expand...
Click to collapse
Let us know how it goes
The exact same thing happened to me a few weeks ago. It happened exactly a year after I got my GT-I9500. Around midnight one weekend the phone had quite a bit of charge and was working fine. As I unlocked the screen to check a WhatsApp message, the phone suddenly shut down and entered a bootloop with the same symptoms as yours. I couldn't enter my stock recovery and download mode would only come up for a few seconds and it would re-enter the bootloop. I tried numerous battery pulls and made it loop over quite a bit and then gave up after an hour and left the battery out. Throughout the day I occasionally tried my luck to no avail. Maybe after 48 hours or less - a day without trying my luck included - since the initial incident, I carried it to the shop and as the employee put the battery in the phone I was baffled. The phone booted normally, no issues and has worked perfectly fine since then. She said sometimes our phones need a little rest.
I've also read that our model has had some battery problems like swelling. I noticed no swelling by the way. So my advice, leave the battery out for a day or two. My phone was not rooted at the time and was running stock TouchWiz Android 4.4.2. Good luck!
MAX 404 said:
Let us know how it goes
Click to expand...
Click to collapse
So I finally got it repaired, the guy replaced something, about the size of 2x1 mm. He said it was for the power button. He charged me around $10 which I think is not bad.
golokipok said:
So I finally got it repaired, the guy replaced something, about the size of 2x1 mm. He said it was for the power button. He charged me around $10 which I think is not bad.
Click to expand...
Click to collapse
Hi Mate,
Great to know , glad it was something cheap and easy.

V20 Black Screen

Woke up this morning and started using my phone, noticed that the screen became unresponsive for a few seconds at a time and then I saw some gray horizontal lines.
Did a battery pull and restarted the phone, however, the screen is completely black and I can still hear the boot sound.
It requires a pin to start completely and I can feel the vibration when I touch the location of the back button (the only navigation key available on the pin screen).
Since this started happening I have tried restarting several times and I have seen the "LG splash screen" once, it freezes, the boot sound plays and the screen goes black once again.
The phone is unrooted and has never been modified any at all. It is the US996 variant.
Has anyone ever faced this issue? Could it be the display itself and maybe a replacement LCD will fix the issuse?
UPDATE
Got past the pin screen and think the phone has fully booted, fingerprint scanner works, I can touch the navigation keys and get feedback and I am still getting notifications.
However, the main screen is still blank and the second screen shows the time surrounded by static surrounded. I have attached a photo.
Sounds like a hardware issue.
mausam233 said:
Got past the pin screen and think the phone has fully booted, fingerprint scanner works, I can touch the navigation keys and get feedback and I am still getting notifications.
However, the main screen is still blank and the second screen shows the time surrounded by static surrounded. I have attached a photo.
Click to expand...
Click to collapse
Hi Have you fixed the issue?
Hi
it looks like a corrupt bootloader,
Was it rooted? try to press with the phone off volume + and plug in the usb to enter in download mode, if you enter download mode go back to factory
gilbertlucas46 said:
Hi Have you fixed the issue?
Click to expand...
Click to collapse
Had to send it in to LG to have it repaired
Oddly enough once it was returned the problem reoccured a few weeks later after using an aukey quick charge3.0 charger that I had. Which was when it happened the first time but I didn't make the connection until the second time around
I got rid of the phone though
No more LGs for me, I haven't had much luck with them
Throw that charger seems like or the cable or the charger itself gone bad ,one charger killed 2 of my phones not diferent brands

Ghost Touches

My tablet suddenly started to suffer from "ghost touches". I already factory reset it and removed it's (great) screen protector, but to no avail.
Any thoughts besides service it?
Thank you!
Leo
Updated 1: problem solved rebooting to safe mode.
Update 2: see my post (#8) dated 10/10/18.
Does the problem occur all the time or only with the charger plugged in?
The reason I ask is that my Android YB has a similar problem with the Halo keyboard. Pressing and holding the shift or backspace key generates random characters. It happens only when plugged in and (interestingly) only in one room of the house. I've yet to find a reason, so I just unplug the power and run on battery while typing.
Another thought: my old Nexus 7 sometimes does the same thing (random touches) or becomes non-responsive. Turning it off and then gently squeezing around the edges and the middle of the screen fixes the problem for several months. I'm guessing that some internal connector is going bad (loose or corroded). It's one of those "can't hurt to try" things.
tjupille said:
Does the problem occur all the time or only with the charger plugged in?
The reason I ask is that my Android YB has a similar problem with the Halo keyboard. Pressing and holding the shift or backspace key generates random characters. It happens only when plugged in and (interestingly) only in one room of the house. I've yet to find a reason, so I just unplug the power and run on battery while typing.
Another thought: my old Nexus 7 sometimes does the same thing (random touches) or becomes non-responsive. Turning it off and then gently squeezing around the edges and the middle of the screen fixes the problem for several months. I'm guessing that some internal connector is going bad (loose or corroded). It's one of those "can't hurt to try" things.
Click to expand...
Click to collapse
Never tried plugged.
But I found the solution: just like Windows (!?) I rebooted to safe mode and... ...it's fine now. Seems that it was some weird driver error that a factory reset alone could not fix.
Thank you very much for your help!!
I just got a "refurbished" one from Amazon. What a nightmare! The random ghost touches are so bad I can't use this damn tablet! Now I have to send it back, get a refund and buy another. Ughhhh.
You rebooted into safe mode and then what?
Sent from my Self
Hi any updates to this? glad I found your post yes it is only when plugged in! must be a known problem.
Unplugged, fine
elcidroyale said:
You rebooted into safe mode and then what?
Click to expand...
Click to collapse
After a few days the ghost touches came back from the grave...
adamz2013 said:
Hi any updates to this? glad I found your post yes it is only when plugged in! must be a known problem.
Unplugged, fine
Click to expand...
Click to collapse
Tried another cable and charger?
I've found a workaround that made de Yoga usable again. In short:
1. Find where are the ghost touches using (developer options -> show taps). If you're lucky as I am they will be confined in just a few pixels is some border.
2. Root the device following this link:
https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268
3. Use some "screen resizer" from Google Play in order to disable the faulty row or column. In my case I started disabling the first 20 pixels. Now I'm with 10 and the Yoga is still usable.

Categories

Resources