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
Related
qhsusb_dload is all I get. Buttons no work. Doesn't vibe or anything. Soft reset doesn't work. Any help or am I screwed. I flashed overcome 8.9 wiped prior and wiped dalvik after the reboot and black screen since.
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm really sorry but your device is done. The skyrocket people haven't been able to fix this yet by using a jig or qualcomm tools.
Reading and researching is really important. You can't flash any p73xx rom to the i957, it will brick.
This is exactly why I have tried to get a separate forum for the i957, but that hasn't worked yet.
Hope you are under warranty or that is an expensive mistake.
Sent from my SAMSUNG-SGH-I727 using xda premium
I did the exact same thing you did. It is very confusing (Well not really, I just did'nt take my time to read). I was exhausted because I was very happy to have my new skyrocket and new lte tab. I researched and researched. I rooted, installed custom rom and kernel on my skyrocket. I then rooted my tablet and it was great. I then installed a custom rom for a 7300 on my i957 and Boom, gone. Luckily I was within my 30 day return policy. Everything in my home is either jailbroken, rooted, homebrewed, w/e. so I have somewhat experience.
But the combination of tiredness, excitedness, and what ever else comes along with getting new gadgets, I didn't pay attention and blew up my tablet.
Even with my experience and never bricking anything before, I bricked my tablet. I took it back to the store and making believe I never even heard about rooting, jailbreaking, homebrewing; the sales people tried starting it up and eventually they couldn't get it to start up. I got a new tablet, I told them I left the tablet charging overnight and left it charging when I went to work, because I forgot to disconnect it. When I got home from work it just didn't turn on.
Eventually they gave me a new tablet and said do not charge it for more than 8 hours. They said I was the first customer to ever return this tablet because it was defective (This tablet is a beast). I told them sure I learned my lesson.
When I went home, I rooted it lol and installed the oc kernel. Remember there are no roms for the 4g model.
Before I went back to the store where I purchased my phone&tablet, I found that there is a youtube store that fixes bricked phones and tablets (He has videos of him fixing them) but when I emailed him, he said their program does not support in unbricking the lte tablet. This was about a month ago so you can check to see if they support it now. I think to unbrick phones it was like 50-100 dollars (I forgot)
You are not alone, I made the same dumb mistake. Never do important stuff when you are tired or excited or anxious. Sorry man, good luck.
I may have put this in the wrong area it was late last night and I was frustrated. I tried putting a 7300 ROM on a 7300. I didn't try anything fancy lol. But I appreciate the responsses. You think I'll be able to take it back and see what they can do? Maybe they'll exchange it as if it was a defect? I'll take it there today. See if they will exchange.lesson learned for me. Lesson being wait for updates from Samsung. As slow as they are. Lol thanks for the input if anyone has the capability to fix this
Hit me up.
Sent from my SAMSUNG-SGH-I727 using xda premium
A 7300 rom on a 7300 should only soft brick. Can you get into download or recovery?
Sent from my SAMSUNG-SGH-I727 using xda premium
If you try to turn on your tablet and your screen turns on you can try to install the stock rom through odin again and it will work. There is a thread in this forums that explains how. If it is off and you turn it on and ABSOLUTELY NOTHING happens and it just stays with the black screen, no vibration or anything then it is hard bricked.
If it is hard bricked you can try to take it back and act dumb, not sure how long ago you purchased the tablet. If you are still within the 30 days you should be good because the sales people I took my tablet to did not have the machine to see how many times my device was flashed. If you are outside the 30 days they will tell you to send it to a samsung repair dealer (which I think they will see how many times the device has been flashed). Once you rooted your tablet it voids the warranty and they either do not have to fix it or will charge you an amount equal to your tablet. I did hear of cases where people with rooted tablets just returned it and they fixed it for free. I guess it dpeneds on anything else in life (How lucky are you?)
Yes you did put your question on the right place since this is for all the 8.9 tablets. (Thats the problem I came across with, I wish they make two forums for both tablets because they are in fact different.
Posting from my mobile so I didn't read your post again.
It is extremely rare but sometimes this can happen. Did you have repartition checked in Odin? If so that's bad.
There is something called qpst - qualcomm product support tools - that people are trying to get to work to fix hard bricks.
Sent from my SAMSUNG-SGH-I727 using xda premium
No prob man. I'll look that up. I'm gonna seems it in to Samsung see if they can fix it. It's under warranty. Anyone done this before?
Sent from my SGH-I727 using xda premium
mobiletechvideos now has support for hard bricked tabs! finally! just sent the payment today and i will send out my tab once i get home from work. ill keep yall posted on how it goes.
here is the link: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-jtag-brick-repair/
Thanks for updating us.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
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.
So my dad picked up a Nexus 7 16GB about a month ago, and he didn't decide to root it or make any modifications to the system. He kept it in a case at all times, so i know its not a hardware problem, unless its the battery. We did open it up to check the battery, and it was all in place. The device will not boot, no matter what we do. When connected to the computer, it will not be recognized unless the power button is held for 10 seconds, and it will try to install an 'APX' driver. I looked into getting the universal naked driver for 'APX' but it installed it as a ASUS Transformer Prime. Im leaning towards sending it in to Google to get it fixed/replaced, but i wanted to know if there was anything I could do to fix this. All help is greatly appreciated, and thanks in advance.
legofan623 said:
So my dad picked up a Nexus 7 16GB about a month ago, and he didn't decide to root it or make any modifications to the system. He kept it in a case at all times, so i know its not a hardware problem, unless its the battery. We did open it up to check the battery, and it was all in place. The device will not boot, no matter what we do. When connected to the computer, it will not be recognized unless the power button is held for 10 seconds, and it will try to install an 'APX' driver. I looked into getting the universal naked driver for 'APX' but it installed it as a ASUS Transformer Prime. Im leaning towards sending it in to Google to get it fixed/replaced, but i wanted to know if there was anything I could do to fix this. All help is greatly appreciated, and thanks in advance.
Click to expand...
Click to collapse
can you get it into the bootloader? power on holding the power button and volume down button at the same time(hold for about 5 seconds or so).
simms22 said:
can you get it into the bootloader? power on holding the power button and volume down button at the same time(hold for about 5 seconds or so).
Click to expand...
Click to collapse
I tried that, and there is still nothing on the powerless screen.
Nothing shows up on the screen? Perhaps the LCD connector has become detached? Just a guess.
Call Google tell them it just stopped working and get a new one
Sent from my Nexus 7 using xda app-developers app
IRX120 said:
Nothing shows up on the screen? Perhaps the LCD connector has become detached? Just a guess.
Call Google tell them it just stopped working and get a new one
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thats what I decided to do, thanks for the help though.
Apx mode= shredded bootloader
legofan623 said:
so i know its not a hardware problem
Click to expand...
Click to collapse
Actually, this sounds exactly like a hardware problem.
Google is very good with defective product replacement you should be fine.
Sent from my Nexus 7 using xda app-developers app
My power-up is very finicky. Keep tapping the power button. Do so holding down the button for various durations of time. You should be able to get the little guy to turn back on with patience. It took me about ten minutes worth of multiple attempts a few days ago.
Sent from my Nexus 7 using xda premium
I got into the house today, after a long day at work. Decided I'll put my phone on charge. I'm that type of guy that likes his phone to always be towardsthe 90% when it comes battery, barely happens though . So I left it on charge whilst I went into the shower. I came out, and I tried entering my password, which was the "pattern lock." I would press the power button to do so, and a few times, the screen turned around. So I tried entering it, and it wouldn't take no feedback. So, I locked it again, by the use of the silver power button, and this time it came up the right way round, thankfully. When I entered my pin again, it took the feedback but didn't progress. I recently got this phone, and it's been a few weeks since I've made the purchase. As it clearly seems, it wouldn't unlock, so I decided to switch my phone on and off. Guess what?
The phone was fricking on the "Please wait, Shutting Down" notification. So I waited and waited till I got fed up. It lasted around an hour. I was really furious, and was about to call my carrier service (Orange/EE) when it was pointed out to me they'll end up giving you a refurbished model rather than a brand new one. I looked up on the internet, and it wasn't anywhere. At this point I tried the solutions of PRESSING THE RED BUTTON NEXT TO THE SIM CARD TRAY or PRESSING THE VOLUME DOWN AND POWER BUTTON TOGETHER. Those simply didn;'t work. I couldn't even boot into safe mode on my phone. So I went on the PC in order to Restore my phone. Maybe that was the last hope. As soon as I plugged the phone into the PC, via the cable, the phone finally reboots and works.
Right now, I'm worried, that this may occur in the future. I hope it doesn't because maybe next time this fix may not work. That's the worry. So, could someone kindly explain to me what exactly happened? Please?
-Haleem.
I honestly have no idea what exactly happend to your phone, and I doubt anyone does. From my experience the current Z1 firmware isn't the most stable though. I've had a few times where my phone would randomly freeze while I was using the phone. What always worked for me was get a paperclip out and press & HOLD the red button next to the sim tray until you feel a few vibrations. (3 iirc) Then I turn the phone on and everything is fine again.
It's no workaround but if I were you I wouldn't worry too much. Just wait until Sony brings out the 4.3 or 4.4 update and hope they fixed the problems. Until then, keep a paperclip in your pocket.
Always press the red button, i call it emergency button or redboot, whatever...when it comes to that matter.haha! B1nny is right maybe it's about the firmware...firmware mulfunction sometimes..
sent from future!
Volume up and power does the same thing without the need for a paperclip to be on hand
Sent from my C6903 using XDA Premium 4 mobile app
Haleem98 said:
... I was really furious, and was about to call my carrier service (Orange/EE) when it was pointed out to me they'll end up giving you a refurbished model rather than a brand new one...
Click to expand...
Click to collapse
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
bogdan wst said:
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
B1nny said:
I honestly have no idea what exactly happend to your phone, and I doubt anyone does. From my experience the current Z1 firmware isn't the most stable though. I've had a few times where my phone would randomly freeze while I was using the phone. What always worked for me was get a paperclip out and press & HOLD the red button next to the sim tray until you feel a few vibrations. (3 iirc) Then I turn the phone on and everything is fine again.
It's no workaround but if I were you I wouldn't worry too much. Just wait until Sony brings out the 4.3 or 4.4 update and hope they fixed the problems. Until then, keep a paperclip in your pocket.
Click to expand...
Click to collapse
Thanks for the advice. And thanks to everyone else too. 4.3 should bre released this month, if everything goes well, for the Z, Z ULTRA and Z1. Not sure about other devices, however in January we should see the release of KitKat, which I'm looking forward to seeing.#
PS. With the Red Button, I pressed it but nothing happened. I probably didn't push it all the way, or didn't hold it down long enough. I just pressed it once, and then left it.
bogdan wst said:
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's good to know! Here, I'm not sure what materials they use to fix the phone, however I do know for sure they don't give you a brand new phone. That sucks. Where you from btw?
What makes you say January for kit kat, Sony have said no such thing, just that kit kat had been promised with no eta
Sent from my C6903 using XDA Premium 4 mobile app
Yeah, it wouldn't make much sense at all to release kitkat in January and 4.3 in December. It's just 4 weeks in between and if everybody knew that 4.4 is coming so soon, hardly anyone would go through the hassle of updating and then again. At least I wouldn't and wait until 4.4.
Therefore, Sony will either release 4.4. straight away or later and skip 4.3 or release 4.3 in December and 4.4. in March or something. I assume the latter will be the case.
Haleem98 said:
That's good to know! Here, I'm not sure what materials they use to fix the phone, however I do know for sure they don't give you a brand new phone. That sucks. Where you from btw?
Click to expand...
Click to collapse
I live in Romania (Eastern Europe).
Sent from my C6903 using XDA Premium 4 mobile app
I've had a strange bug since I got the phone that I'm wondering if anyone else has seen (don't think it is hardware).
I can reproduce it every morning after I wake up. Conditions are as follows:
Phone is on the clock daydream while charging. I use Sleep As Android as my alarm. Every morning when my alarm is going off and I reach for my phone half of the screen is not working and or black.
I just had a recurrence of this in the xda app after I lost wifi connection and was exciting a thread (pressing the back button) during the handoff to LTE. Easy fix is to just hit the power button to turn the screen off then turn it back on. Works right away.
Anyone seen or read about anything similar?
Thanks!
I made a post earlier about screen touch issues and this is one of mine as well. I can't reproduce it like you can but the right half of the screen just drops off to touch.
Have you seen the half (or third) of the screen go completely black? Seriously Wtf. I've only had it happen probably 4 times.... Comes back on immediately and worms as expected if I press the power button twice.
EmperorX said:
Have you seen the half (or third) of the screen go completely black? Seriously Wtf. I've only had it happen probably 4 times.... Comes back on immediately and worms as expected if I press the power button twice.
Click to expand...
Click to collapse
Sounds like you have the ATT model which was recalled for that very reason.
http://www.droid-life.com/2014/11/2...p-nexus-6-inventory-back-due-to-software-bug/
hsj1906 said:
Sounds like you have the ATT model which was recalled for that very reason.
http://www.droid-life.com/2014/11/2...p-nexus-6-inventory-back-due-to-software-bug/
Click to expand...
Click to collapse
Picked it up from tmobile on Wed morning.
Also, those issues seem different from what I read.. Screen is *completely* black and they get stuck. Mine works fine 100% except when I wake up with the prior conditions (over night, phone is on clock daydream, dimmed and I am woke up with Sleep As Android alarm). It has only happened once in any other circumstance. Also, my phone updated to LRX21O upon first boot.
At this point I can't tell if it is software or hardware... Not sure how tmobile handles this as I bought directly from them (no insurance as of yet) or if I go straight to Motorola?
I just wish I could conclusively rule out a hardware issue.
I'm having a similar issue. It seems to definitely be intermittent though. Also, I've only experienced it when my phone is in landscape mode. It goes back to normal when I flip it to portrait mode.
Did you ever find anything else out about the issue OP?
trustinhate said:
I'm having a similar issue. It seems to definitely be intermittent though. Also, I've only experienced it when my phone is in landscape mode. It goes back to normal when I flip it to portrait mode.
Did you ever find anything else out about the issue OP?
Click to expand...
Click to collapse
Nothing other than what is in here. Still happens to me, though much less frequently. Hoping the 5.1 update rumored for Feb solves some of the quirks.
I honestly think this is a hardware issue of some sort. I had my original Nexus 6 for weeks and throughout heavy usage, I never had any issues. The first day I received a replacement device from Google, half of my screen would freeze/go black when in landscape watching videos, playing games, and sometimes even browsing the web. This was with 100% stock ROM and kernel without root (which rules out that being an issue). I tried reflashing the stock image and the issue still persists.
I contacted the GPS customer service last night and ordered another replacement device. This is issue is certainly specific to this phone, my first device was used heavily and this never happened even once.
I am convinced it is hardware as well.
I am experiencing the same issue with my phone and opened a ticket with Google yesterday and I want mine replaced. It's not just the Nexus 6 that's suffering from this as some Droid Turbo users are experiencing it as well.
lianw said:
I am convinced it is hardware as well.
I am experiencing the same issue with my phone and opened a ticket with Google yesterday and I want mine replaced. It's not just the Nexus 6 that's suffering from this as some Droid Turbo users are experiencing it as well.
Click to expand...
Click to collapse
Same thing here. Tmobile 64 GB nexus 6. Bought mine from T Mobile, but they don't have a replacement to send me, so I contacted Motorola, and they sent me a new one that arrives tomorrow. I hope the same thing doesn't happen with this one.
Sent from my Nexus 6 using XDA Free mobile app
Look on the positive side of things, 50% less battery drain due to screen usage...
I still think this is, in my case, specifically software. Other people have reported different issues that are most likely hardware, don't think mine is. Also it has only happened two or three times in the past month, seems to with screen on and rotation occurring at the same time, though I can't confirm or repro reliably.
Well, just had my replacement processed over the phone. Only potential issue is that they said it may be a refurbished device. Anyone know how/if there is a way to tell??
I am not sure if this is somehow related-but my first Nexus 6 I got from t-mobile was working fine and on the second day of owning it the touch screen stopped working! I mean it won't register any touch whatsoever! The phone was just charging and I just used it like 30min ago....tried rebooting, resetting-nothing helped-went to a t-mobile store and replaced with a new one. The second one works...for now. The strange part is that they were no issues-it worked flawlessly and all of a sudden just stopped responding to touch.
I have never experienced issues like this with any smartphone in my life-I have owned android smartphones ever since the G1 was released...
Sleeepy2 said:
Well, just had my replacement processed over the phone. Only potential issue is that they said it may be a refurbished device. Anyone know how/if there is a way to tell??
Click to expand...
Click to collapse
T mobile didn't have any available devices to send me, so I contacted Moto. Moto sent me a brand new phone.Build date is December 16th. So far no problems, but I just got it today. I'll report back if anything goes wrong.
Sent from my Nexus 6 using XDA Free mobile app
NastyNeil said:
T mobile didn't have any available devices to send me, so I contacted Moto. Moto sent me a brand new phone.Build date is December 16th. So far no problems, but I just got it today. I'll report back if anything goes wrong.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do you see the Build date?
Sleeepy2 said:
Where do you see the Build date?
Click to expand...
Click to collapse
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
NastyNeil said:
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanx :good:
NastyNeil said:
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Can you post a picture of where? I don't see any dates listed on the box.
On the bottom right just before SeQ#
But a better way to check is to boot into the bootloader/fastboot hit valume down until you see barcode then push power.
For me the date it shows is 1 day before the date on the box. The box says 2014-11-16 bootloader says 2014-11-15.