ok, I am a noob. I freely (and sadly) admit this. I have watched the videos, read the rules, searched the forums, searched the internet etc. etc. on this site there were 2 threads to help me and neither really helped so here goes.
I have a tmobile Dell streak 7 that i purchased on EBAY. It works great EXCEPT the accelerometer is off. I cannot play TempleRun without the little guy running to the side of the screen. I downloaded a bubble level app to check it just to make sure it wasn't the app itself. the bubble app has my bubble sitting about 28.5 degrees to the left of center. I know on my cell phone there is a G-sensor calibration option but I have looked everywhere on this silly tablet and cannot find one. i did have to do a hard factory reset because I was stuck on the spinning Dell logo and I had hopes that it would fix the calibration issue at the same time but it did not. Can anyone help me? Thanks much friendlies
I guess thr problem may be hardware. Sent it for warranty. Also make sure you bhave the process com.oem.engineering.calibrate running
Sent from my Dell Streak 7 using xda app-developers app
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
mr23 said:
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
Click to expand...
Click to collapse
I also bought my device about a week ago but im still on 4.1. i think i will wait before i apply any update, to make sure things getting stablized with a new version
Edit.. Nevermind.. I'm in a jumping to conclusions bad mood.. Away from the keyboard I go.
4.2 update won't brick your device. It is a Nexus - just about impossible to brick. You had a problem - but it was not the update.
Sent from my Nexus 7 using xda app-developers app
There are many running 4.2 Builds (Eclipse being one of them) and are having no issues.
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I concede with approximately three million people updated by now, you could have been the one to find the error in the update.
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Jellybean 4.2 Ruined my Asus nexus 7.
X_Fact0r said:
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Click to expand...
Click to collapse
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Kpennett said:
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
Click to expand...
Click to collapse
The guy you were replying to was talking about the OP's issue which was supposedly a bricked Nexus as a result of upgrading to 4.2. It has nothing to do with the items you mentioned, so I would suggest that he is not the one who needs to "get a clue".
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Click to expand...
Click to collapse
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
mr23 said:
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed.
Click to expand...
Click to collapse
THANK YOU. The term brick started with the Linksys routers and a brick was just that, a brick, a paperweight, doorstop, and was a very real possibility (though rare).
Before that PCs would be called anchors or door-stops but those terms were also used for PCs that were beyond any possible usefulness rather than just being beyond repair.
At least say soft-brick.
Sent from my Nexus 7 using xda premium
---------- Post added at 02:07 PM ---------- Previous post was at 01:51 PM ----------
dilldoe said:
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
Click to expand...
Click to collapse
If you can pull or remove the battery you can leave the battery out for 15 minutes. That can revive a device that has become non responsive.
I dunno is the battery on the N7 soldered in or use a ribbon connector?
Sent from my Nexus 7 using xda premium
OP, your device probably wasn't bricked, you need to press the power button for 5>7 seconds and it would of powered on, if for you get the count wrong the Nexus 7 wouldn't power up, this is why you thought it was bricked, in any case, all you needed to do is press and hold the power button for 20>30 seconds and i would of powered on.
fernando sor said:
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
In some parts of the world the day comes before the month, the UK > 24/11/2012, US > 11/24/2012.
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I only mentioned the above because you didn't say in any of your posts that you had tried this.
Just what this forum needed, more *****ing.
May be a defect device most likely due to hardware. Other than the some performance issues and some minor ones here and there, I don't think anyone got their device bricked. I hope the new one will be a better experience. Also it'll be informative if you could have mentioned the first four alpha numeric serial number.
Sent from my Nexus 7 using xda premium
I got my son a 32GB nexus 7 for Christmas but it didn't turn out very well. Right out of the box it wouldn't turn on. No big deal I thought, i'll just plug in the charger and let it charge for a while. 2 hours later I try to power it up again. No luck. nothing happening at all. So now its 1:30 AM on christmas morning and i'm still messing with this thing. Hold power for 30 seconds, nothing. Hold power and Volume + to get into recovery, nothing. So back on the charger it goes. 7am. Still dead, nothing happening. Back on the charger. Kid's not happy that his new tech toy isn't working. So around 10 AM I'm standing there talking to my wife while holding the power button down for what seemed like 2 minutes and I look down and see the Nexus "X".... Holy cow, its alive. So we let it start up and dive right into setup. It rebooted 2 times while trying to setup. Third time we make it all the way through and get started downloading some apps. All updates applied up to 4.2 and I thought we were in the clear. So off my kid goes playing angry birds and Navy fighter happy as can be.... Yep, crashed again and was not able to power it back up again. So its in the box headed back to buydig.com I guess this one was a real lemon.
Did some looking around and couldn't find much that relates to my problem. It seems it was just my turn to get the lemon.
combattalon2 said:
I got my son a 32GB nexus 7 for Christmas but it didn't turn out very well. Right out of the box it wouldn't turn on. No big deal I thought, i'll just plug in the charger and let it charge for a while. 2 hours later I try to power it up again. No luck. nothing happening at all. So now its 1:30 AM on christmas morning and i'm still messing with this thing. Hold power for 30 seconds, nothing. Hold power and Volume + to get into recovery, nothing. So back on the charger it goes. 7am. Still dead, nothing happening. Back on the charger. Kid's not happy that his new tech toy isn't working. So around 10 AM I'm standing there talking to my wife while holding the power button down for what seemed like 2 minutes and I look down and see the Nexus "X".... Holy cow, its alive. So we let it start up and dive right into setup. It rebooted 2 times while trying to setup. Third time we make it all the way through and get started downloading some apps. All updates applied up to 4.2 and I thought we were in the clear. So off my kid goes playing angry birds and Navy fighter happy as can be.... Yep, crashed again and was not able to power it back up again. So its in the box headed back to buydig.com I guess this one was a real lemon.
Did some looking around and couldn't find much that relates to my problem. It seems it was just my turn to get the lemon.
Click to expand...
Click to collapse
I got mine from Buydig as well and have had no problems with it at all...
I feel bad for your son. That really sucks... Pretty awesome dad to get him the big 7 and not the cheaper one lol
Sent from my Nexus 7 using Tapatalk HD
You could take the back cover off and see if the battery connector is connected properly.
Sent from my Nexus 7 using xda premium
Gizmoe said:
You could take the back cover off and see if the battery connector is connected properly.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How is this accomplished without damage so I can send it back with no issues?
Edit- Nevermind, found the iFixit video.
combattalon2 said:
How is this accomplished without damage so I can send it back with no issues?
Edit- Nevermind, found the iFixit video.
Click to expand...
Click to collapse
If you have to call support to send it back, DO NOT tell them you opened it to check the batt connector as they insist this will void your warranty. Just a heads-up.
just do not tell them you did anything to it. they should give you a rull replacement
i also got a nexus 7 from parents for christmas and am loving it, hopefully he understands it is just a mistake and this is still a high quality product
I had multiple Nexus 7's and so far not one has had any issues.
Sent from my iPhone using Tapatalk
Status?
Sent from my Nexus 7 using xda app-developers app
zPacKRat said:
Status?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes
Sent from my PantechP9070 using xda premium
Original returned to buy dig.com. got a 32gb from staples and all is well. Never opened the case on the first N7 so I can't tell you what was wrong. After playing with the new one though, the original had screen issues. No charge animation when plugged in.
Ok so i've had a number of issues with my Atrix HD but i refuse to get a new phone. About 2 months ago the lcd (not the outer glass) broke and while replacing it i may have damaged the battery (slightly). My phone wouldnt turn on for about 2 weeks and one day , POOF, it turns on. All was good for a month till i dropped it and it just turned off. 2 weeks later we're here and after mass looping and rebooting i get it to turn on only to find out it turns off when i take it off the charger. Can someone please help me fix this? is there hope for my phone? or should i try getting a new battery and replacing it with my current one?
THANK YOU!
Open up the phone and check the battery connections. By dropping your atrix that could easily shake something up or break a connection somewhere. Just check all the connections in the phone. YouTube can show you how to open up your atrix, there is also a screen replacement guide in atrix HD general that'll show you how to open the phone correctly.
Sent from my MB886 using Tapatalk 4
Okay I did what you said and i think i got it to work without the charger. Thank you so much!
Glad to help.
Sent from my MB886 using Tapatalk 4
Yesterday afternoon I had found a micro hdmi in some cords I had laying around and out of pure curiosity I plugged it into my laptop to see if it would recognize my kindle . For some reason. A few moments after plugging it in the Damn kindle shut off and it will not start back up. I know for a rack it was at 100% charge when it happened so I don't think it to be the battery. I'm afraid it my have fried something more important? I have tried to let it sit plugged in but no change has occurred. I looked around the mother board and found nothing that looks like a problem. Is there anything that the community could suggest to resolve this issue? I just got this system secondhand and was beginning to fall in love with it until this had happened... Please tell me there is hope
Its been 2 days withou a reply
so after 2 days of waiting on some sort of advice, I have open my Kindle back up again and think I have found a very small resistor possibly? that looks to be damaged. a number beside it would be l600. I'm not skilled enough to be able to solder it back on so now I am in search of a 32 gig motherboard at a cheap value Place. I plan to time he sees them into an Android tablet so I do not need to be able to register with Amazon but the only one I can find has been posted for quite some time now and seems a little shady. Anyone advice on way to get cheap but reliable Kindle parts
grrr i see 84 veiws but not a single comment
I love xda and had hoped anyone could have helped revive my kindle but it seems as though nobody has ever had this problem and that would probably be why those thread is still open... I hope so done else gets help of they ever run into this issue so I will keep it up but it seems I will just be tossing my kindle in the burn barrel. That's the only fire I seen from the kindle thus far...