So, I bought my wife a nook Color. She's an English teacher and she's embraced technology as a teaching aid, so I figured it would be perfect.
I did not modify the nook AT ALL. All I did was put some ebooks on it from around the web, loaded onto an SD card. Nothing unusual beyond it being a few THOUSAND files in .epub and .pdf format.
ANYHOW, she's seen issues.
First, she saw issues where the nook thought she was tapping constantly in the exact same spot. To be exact, the spot where the 'b' is. If we hit the nook home button, it kept clicking the book that was in the exact same spot as the 'b' button was. Shutting the nook off entirely fixed it.
Second, frequent lockups during normal use. Sometimes in the browser. Other times flipping through PDFs. Android itself usually wasn't locked up since we could hold the power button and get the dialog asking us if we REALLY wanted to shut it down, but the nook overlay GUI was certainly dead to us. Again, a hard reset (power button until it shut down) and power up fixed this without a problem.
At this point, we thought it would be a good idea to swap this out as a potential hardware issue. We bought it from Best Buy, so back to BB we went and swapped it out for another nookColor.
Now, we're seeing more issues, but different ones.
Third, the power cable doesn't seem to want to fit properly into the USB port like the last one did. A little play and it slides in ok, so no big deal.
Fourth, buttons are sensitive to where it thinks we tapped twice. I don't think this is a real issue since it's a matter of learning the device I think.
Fifth, and fairly important... this only happened once. It lost all sound. We have a child who's just over 1 year old, so the B&N's stance to try to set a high focus on that aspect was awesome, especially the childrens' books with the professional voice actors.
Now, it's my opinion that it's just an OS that was released prematurely. I think many of these issues will be fixed with the first update. Am I alone in these issues? Has anybody else seen anything similar?
For the record, I've taken a very hands-off experience with this since I'm extremely technologically savvy, and I wanted my wife to be able to run it without needing me there. None of these issues have persisted throughout a shutdown-reboot except for the sound issue. It required an 'erase and unregister' through the device info in settings.
I bought a NC for myself and a day later my wife bought one at the same B&N. The one she bought had terrible screen flicker so we exchanged it for another. The second NC would FC on her ebooks, drop wifi, and would make a cheap plastic creak when pressed to tight on the left side. Thinking the bad batch idea we exchanged the NC at a different B&N and the third one had the same screen flicker the first one had so we turned around and went back and exchanged it for a fourth one. Finally. The fourth one worked fine and does not creak at all.
I wouldn't necessarily say your problems are OS related. Android has been running on a lot of portable devices for quite some time now. I think it can be considered a mature OS. The ebooks we have that caused the second NC to FC work flawlessly on my NC and the new fourth one. Rebooting the second NC didn't help with the FC'ing and wifi dropping. So we felt the problem was hardware related like the screen flickering. Our feeling was we didn't want to mess around, it's $250, we were determined to keep exchanging until we found one that worked.
You might want to think about exchanging it for another. Who knows how many will remain to be in stock as the date gets closer to Christmas. I wouldn't recommend trying to exchange it after Christmas, you may end up getting a re-shrink wrapped one that was returned for some unknown reason.
android is becoming mature but the nook is oem'dto death. This os is crap by all accounts! Once something better is available we will see improvements
The screen thing is turning out to be kinda common.
Good news is.... its being blamed on an oversensitive screen, dirt and or moisture. Any tiny bit of the latter two. Usually fixes itself right up with a wiping or a screen protector and a lock/unlock of the device.
I have experienced and read about the charger cord too.....have yet to see any problems because of it but do worry about having to re-solder something sooner or later.
I have to wonder about the usefulness of a Nook Color as "a teaching tool" right outta the box though?? Besides making your wife a walking reference that is.
was it plugged in? There are issues when plugged in and tapping.
I also had to "wiggle" the USB cord to get it to fit into my Nook as well.
I had the creak on the left side as well. Haven't had a chance to exchange it yet, but it's on the radar.
I don't mean a tool to use with the students, I figured it may make things easier on her if she's got ALL of the books she uses with her students on a single table that she can carry around the classroom referencing instead of needing 30 different books. I don't know if it was a fool's idea yet or not! It's the thought that counts.
Defiantly save on the back!!
Nice one, guess I just want mine to do everything
Galaxy Tabs.....Worth every penny!!
My first nook had the sound problem, except it would happen every 15 minutes and only hard reboot would fix it.
I replaced it and the second works flawlessly (as far as I can tell).
Related
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
My nephew may have or may not have smacked the touchscreen too hard playing angry birds. We are not sure, he is 4, but has never been rough before this with eletronics.
So I had a rooted phiremod cm7 nook. The screen stopped responding. I, thinking it was toast, reformatted back to stock since it is under the 1 year warranty still.
Now the screen works. This is great. I need to know if this could be just a fluke though. Did perhaps the screen crash from 4 year old fingers trying to get it to do ten things at once? Could something be loose in there, just waiting to die? It has frozen up before but in the past waiting a second always brought it back to normal. This time, several restarts and nothing. The touchscreen did not respond till after the reformat.
Now it seems fine but it did do this weird flashing over response thing when I tried to read the notifications in stock.
Should I take it back and tell them the screen is being wonky or not? What are the odds of it needing replaced/repaired?
Did you restart before you reflashed? Every once in a while my screen just completely stops working and I have to hold the power button until it turns off. And then all is good, seems to happen when it gets bogged down in an application
So it's just a thing these do then?
Whew. I was not looking forward with dealing with warranty repairs or replacement. I will just reflash it then.. after I mess with it some to be really sure..
I believe so, I used to have the screen freak out and phantom taps but a screenprotector solved that problem. I think its just because the screen is so sensitive
Hmmm.. my Nook is naked. It spends most of its time at home by my bed or in a practically perfect sized bag for travel so it was not something I worried too much about. But if it will help...
I will 'dress' my nook. A screen protector, a silicone thin skin and I'll even get a cheap leather case just in case.
And I think I need to stop lurking so I can edit my posts faster.
It couldn't hurt, I recommend getting a three pack of "crystal clear" ones from eBay at about $3. You will want more than one in case you don't get all the dust off the first time
Hello all, I just replaced a broken LCD and digitizer on my HD7 with a unit bought from eBay. It's from a supplier that I've used very frequently, so I trust the component. When I got the phone back together, it will sometimes boot, sometimes not. It will also sometimes display just fine, and other times it looks like it's garbled, or just not display at all. The screen will be blank and not react. I'm pretty versed at repairing phones, I've probably done 30 for myself and friends, so I'm pretty good at reassembly. Is anyone familiar with this issue and can maybe give me some ideas? Cause I'm flat out of them.
The other thing is that when I start moving the phone around after reassembly, this is when I start experiencing troubles. I tried putting electrical tape in places under the mobo to keep from grounding something out, but it doesn't seem to help. Any ideas would be great.
Did you put on gloves when you were doing the replacement. Cause like you I have done alot of screen replacements on a wide range of phones and I would have to say that there are devices out there were if something got grounded out while you are doing the replacement it tends to start doing all kinds of goofy things once the phone is back together. I have found that by wearing "gloves that do not conduct electricity" the chances of something like that happening is gone. Ive only had two devices do weird and strange things like some of what you have said. These were some of my first repairs and after changing to putting gloves on I haven't had a problem since.
Hope that helps and also I am about to replace the screen on a HD7 that I just bought just wanting for the screen so, I will let you know what happens.
Thanks, probably good advice. I've been very lax about using grounding protection of any kind. I've seen those guys who use the "finger condoms" where the rest of their hand is open. Couldn't hurt to use a grounding strap too, pretty cheap and easy precaution. The other thing I noticed about the phone was the SD that came with it isn't recognized by any OS, so wondering if there wasn't something else wrong with the phone.
I have no idea what's happened but the screen on my Z is completely unviewable. Was in my pocket, got a text took it out and it's dark (backlit making it appear grey) but with lines moving all over the place. Every now and then I get a brief glimpse of my home screen but then it disappears. The phone itself appears to be working but I can't see anything at all on the screen.
I've tried a reset (pressing vol+ and power button) but same issue right from the start (even on boot the sony logo appears as lines all over the place).
I suspect it's a hardware issue and i'll have to take it back but any thoughts before I go down that route?
Phones4U are going to do an exchange for me so problem solved but it does make me nervous about any future problems. Not even a month old yet and it's not like i've been throwing it around.
PHTC said:
Phones4U are going to do an exchange for me so problem solved but it does make me nervous about any future problems. Not even a month old yet and it's not like i've been throwing it around.
Click to expand...
Click to collapse
I do understand. We have to accept though that every devise we purchase there is always going to be some that are faulty. When it happens to us we tend to think its a devise problem that affects the whole range. Some people actually decide not to purchase that brand again meaning from phone to TV etc?
I am an Asus fan yet the hell I had with their range of tablets could have turned me against the brand. It didn't I own some very good Asus products.
These forums tend to be negative places as an awful lot of members only join a forum because they develop a problem. If we read every thread published here it would be impossible to purchase any phone from any brand as every single one of them has some problems.
You must, obviously, return your phone for an exchange. I hope all goes well with your replacement. It should be fine.
Let me start off by saying that I really like this phone and I'm no where near giving up on it.
With that said, I bought 3 of these within the first couple of days after release.
For me - Current occupation - IT System Administrator with 18 years of experience in various areas of IT
My son - Current in college, going for his Computer Science degree.
My daughter - Currently in college and surrounded by tech her whole life as I am a tech lover.
I mention who we are only so people don't assume that we are typical end users that can't figure out the difference between their heads and their asses.
My son has returned his Turbo twice (both metallic black). The first time, he had major scrolling issues. Phone would "fling" through pages unprompted while touching the screen. The second one he returned because there is a glue problem or something like it with the back of the phone, near the bottom. Makes a creaking noise (loud) if you press on the back near the bottom.
My daughter has just returned her first (32 GB Ballistic). Hers will not connect to WiFi without a reboot. Very annoying. Airplane mode first then trying didn't work.
Mine - I have not returned by 64 GB Ballistic yet but I think I am going to exchange it. I have problems with WiFi connecting also. It isn't as bad as hers in that mine occasionally connects without a reboot. In addition, mine definitely has some sort of touch screen issue. The screen becomes unresponsive at times and requires me to press the home button to "reset" the screen. I installed display tester and checked the multi-touch test and found that sometimes it won't register all fingers or one fingers touch is chaotic, wiggling all around while the others are ok. I also have a volume issue of some kind. I have to turn the phone up past half volume just to hear it... even in a quiet room.
I do really like this phone and have every intention of keeping it assuming that I can get one that doesn't have issues. Not sure if it was rushed or whatever but there is a definitely some build quality issues going on here.... Makes me very sad.
The second one he returned because there is a glue problem or something like it with the back of the phone, near the bottom. Makes a creaking noise (loud) if you press on the back near the bottom.
This is an issue for some and I believe there are some youtube videos demonstrating it.
For the call volume issue try disabling the equalizer, I read on here from a few people that that is the fix, I use the equalizer but haven't had a problem with the sound.
Sent from my XT1254 using XDA Free mobile app
Thanks guys. I'm surprised that there haven't been more comments. I was kind of hoping that people would say, "no problems here" or "yeah dude, wtf". Still love this phone. I think its the motorola apps and how they have nailed it in the "what I personally like" categories. Active screen and such are great.
Despiadado1 said:
Thanks guys. I'm surprised that there haven't been more comments. I was kind of hoping that people would say, "no problems here" or "yeah dude, wtf". Still love this phone. I think its the motorola apps and how they have nailed it in the "what I personally like" categories. Active screen and such are great.
Click to expand...
Click to collapse
I'm one of the few who got a good Turbo. Bought it on launch day and have had none of the problems people on here have mentioned. No creaking on the back, no scroll issue, no screen temperature issue, nothing. The connectivity issues you talk about don't happen to me. I'd say just keep getting them exchanged until you have a good one.
Despiadado1 said:
Let me start off by saying that I really like this phone and I'm no where near giving up on it.
My daughter has just returned her first (32 GB Ballistic). Hers will not connect to WiFi without a reboot. Very annoying. Airplane mode first then trying didn't work.
Mine - I have not returned by 64 GB Ballistic yet but I think I am going to exchange it. I have problems with WiFi connecting also. It isn't as bad as hers in that mine occasionally connects without a reboot. In addition, mine definitely has some sort of touch screen issue. The screen becomes unresponsive at times and requires me to press the home button to "reset" the screen. I installed display tester and checked the multi-touch test and found that sometimes it won't register all fingers or one fingers touch is chaotic, wiggling all around while the others are ok. I also have a volume issue of some kind. I have to turn the phone up past half volume just to hear it... even in a quiet room.
Click to expand...
Click to collapse
OMG FINALLY someone with my same problems! So I'm not going crazy. I swapped it out once, had same issue with the new one, but now it seems the issue is only at my works wifi. I have seen online there are issues with the phone and Cisco routers, and I assume we have Cisco routers here at work since our phones are Cisco...so I'm just chalking it up to an issue with my works wifi and letting it go. But what happens for me is I'll connect to wifi and then it'll disconnect randomly, so I have to either turn airplane mode on and off and fiddle with that and "forgetting" the network, or just restart my phone. It's rather annoying, but I have no other option as the phone works wonderfully on all other wifi networks.
Never knew I had the same glue/creaking problem until I read this. Now it will bug me until I do something about it. ?. What's the solution? Exchange or diy repair?
Despiadado1 said:
Let me start off by saying that I really like this phone and I'm no where near giving up on it.
With that said, I bought 3 of these within the first couple of days after release.
For me - Current occupation - IT System Administrator with 18 years of experience in various areas of IT
My son - Current in college, going for his Computer Science degree.
My daughter - Currently in college and surrounded by tech her whole life as I am a tech lover.
I mention who we are only so people don't assume that we are typical end users that can't figure out the difference between their heads and their asses.
My son has returned his Turbo twice (both metallic black). The first time, he had major scrolling issues. Phone would "fling" through pages unprompted while touching the screen. The second one he returned because there is a glue problem or something like it with the back of the phone, near the bottom. Makes a creaking noise (loud) if you press on the back near the bottom.
My daughter has just returned her first (32 GB Ballistic). Hers will not connect to WiFi without a reboot. Very annoying. Airplane mode first then trying didn't work.
Mine - I have not returned by 64 GB Ballistic yet but I think I am going to exchange it. I have problems with WiFi connecting also. It isn't as bad as hers in that mine occasionally connects without a reboot. In addition, mine definitely has some sort of touch screen issue. The screen becomes unresponsive at times and requires me to press the home button to "reset" the screen. I installed display tester and checked the multi-touch test and found that sometimes it won't register all fingers or one fingers touch is chaotic, wiggling all around while the others are ok. I also have a volume issue of some kind. I have to turn the phone up past half volume just to hear it... even in a quiet room.
I do really like this phone and have every intention of keeping it assuming that I can get one that doesn't have issues. Not sure if it was rushed or whatever but there is a definitely some build quality issues going on here.... Makes me very sad.
Click to expand...
Click to collapse
What's the verdict on the crackling noise underneath the ballistic nylon? Did they exchange it?
Only problem I have is the call volume could be a little louder. Coming from a S4 I usually had to turn it down.
I'm really wondering if you guys that are having trouble with call volume are not holding the speaker in the right position. I never had a problem with my call volume until today. My third call of the day seemed to be extremely quiet until I repositioned the phone and got the speaker lined up more with my ear. For comparison sake, I had to do the same on my S3 on almost every call, so I wouldn't consider this phone bad on that account either. It's something easy to try anyways before exchanging a potentially otherwise good/perfect phone. If it doesn't work you wasted 10 seconds.
Sent from my XT1254 using XDA Free mobile app
SFG said:
What's the verdict on the crackling noise underneath the ballistic nylon? Did they exchange it?
Click to expand...
Click to collapse
Yeah, they exchanged it. No real problems with Verizon in that regard.
RobinsonR810 said:
OMG FINALLY someone with my same problems! So I'm not going crazy. I swapped it out once, had same issue with the new one, but now it seems the issue is only at my works wifi. I have seen online there are issues with the phone and Cisco routers, and I assume we have Cisco routers here at work since our phones are Cisco...so I'm just chalking it up to an issue with my works wifi and letting it go. But what happens for me is I'll connect to wifi and then it'll disconnect randomly, so I have to either turn airplane mode on and off and fiddle with that and "forgetting" the network, or just restart my phone. It's rather annoying, but I have no other option as the phone works wonderfully on all other wifi networks.
Click to expand...
Click to collapse
I dont think its just Cisco though I did read some other articles about that and the type of wifi encryption. This has been at a few different locations. For my daughter, it happens at our home but my son doesn't have any issue.