Related
Anyone else experiencing this? In the 24 hours I've been using my nexus 10, this has happened at least 10 times. All of a sudden the device becomes unresponsiv, the screen dims until it turns off, and the only way to get the device back on is holding down the power key multiple times until it boots back up. Needless to say, quite frustrating. Otherwise, love this device.
Anyone else experiencing this?
Sent from my Nexus 10 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1998496
Sent from my Galaxy Nexus using Tapatalk 2
Not quite sure how one loves a device that forces you to reboot ten times in the last 24 hrs. It's like buying a new Honda and loving it even though it stalls ten times a day.
Too many people apparently buy their device to adoringly stare at like a trophy or a collectors item than actually use.
Those all seem like pretty legitimate apps to me. This would suck but I would suggest deleting one app and using the tablet till it happens then rinse repeat till you find the offending program.
Try the secret magic spell: a full wipe
Sent from my GT-N7100 using xda app-developers app
Add me to the list of people with random freezes and reboots. It's happened to me 3 times since I've gotten the tablet a few days ago, and I was using a different app each time. I suspect it's an OS bug rather than an app that's causing it. It's a little disheartening that Google let their new flagship 10" device get released with such a bug. Hopefully they release an OTA update sooner rather than later.
For the record, I rooted using the flashable CWM SuperSU file - I did not use the toolkit.
I have had my 16gb 10 now for almost a week - currently stock and non rooted. No problems whatsoever and I have been working it pretty hard.
Mine has frozen 2-3 times in the past few days. No idea why either. Audio continues to play, and the device responds to button use, but the display stops altogether.
Sent from my Nexus 10 using Tapatalk HD
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
ralphconrad91 said:
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
Click to expand...
Click to collapse
In another thread someone said it slowed the issue but didn't stop it.
Sent from my Nexus 4 using Tapatalk 2
Thanks man, now I'm debating if I should just get the transformer infinity. I really don't need root that much because I only use my tablet for school...
Sent from my Nexus 10 using xda app-developers app
Happened to me several times as well. Last time the screen went black (not off) and the tablet was extremely hot, to the point of burning my hand when I touched it! Seems it was stuck that way for several hours and didn't reboot itself.
I've been having random rebooting and freezes since getting this tablet i've replaced it three times already so i'm tired of calling google about it don't even think they have a solution because we've been waiting since November for them to fix this problem so i decide to turn off location and took HD widgets out and so far my tablet has not frozen or rebooted in two weeks it been working really well hope it continues to perform this way.
Chrome has major stability issues as far as I can tell. It crashes very frequently and causes a complete system lock-up when it does. I've resorted to Firefox. To me, this is absurd on a core first party app. Google: get your act together on Chrome.
I recently noticed this issue and have been reading what a lot of others here have had to say and so far it seems to be related to wifi. I would bet it's a software / kernel / driver issue because others have reported not having the problem before the latest update.
If I think about it, I probably had the lockup/reboot happen once before now and I can't really tell you what I was doing at the time. But I thought nothing of it. I have however found a way to force it to happen. All it takes is a large download (1gig'ish) in uTorrent, the download works fine for about 10 minutes and then the tablet either just restarts, or it first becomes unresponsive to input (screen or buttons) but is still functioning, followed by a hard lock up that can only be fixed with a forced power off.
It may be a buffer issue, or memory leak, I've been able to prolong the lockup by throttling the uTorrent download speed and minimizing the number of active apps running. As suggested in other threads I've disabled location discovery and it may have bought me a little more time but if so it's not much. I can't tell if it's because of the amount of constant data flow coming in, or the number of active connections to different seeders, or more likely a combination of the 2. I can also say that if I attempt to browse the web with either chrome or Dolphin while downloading in uTorrent the freeze or reset happens much quicker.
So for now I'm hoping that in the next update they resolve the issue and will just use my pc for torrent downloading.
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Turning off the location services and uninstalling HD widgets sorta worked for me... I still get random reboots though but mostly when I'm using Chrome. Google should have just left the stock android browser and made Chrome optional.
Sent from my Nexus 10 using xda app-developers app
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Thanks, ya that had crossed my mind but wasn't sure which defect to post it to so thanks for the link.
HELP!!
I am experiencing the same problem.
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Nope, the problem was submitted to Google months ago and is listed to only receive medium priority. A total system failure that affects every single Nexus device is only given medium priority. Makes me ponder what in glory be would be considered high priority. Maybe if the tablet reached out and kicked you in the balls whenever you looked away from it
Anyone else having the issue where the touch screen is overly sensitive making typing or swyoing nearly impossible? Makes it hard to control movement of pages via browser.
Sent from my VS980 4G using xda app-developers app
ready5 said:
Anyone else having the issue where the touch screen is overly sensitive making typing or swyoing nearly impossible? Makes it hard to control movement of pages via browser.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
I have noticed that my AT&T G2 is a bit too sensitive to my touches as well. It's not a big deal but it's a little bit annoying sometimes.
Maybe don't drink so much coffee?
Haven't had this issue...
Sent from my Nexus 7 using Tapatalk 2
Starting to think I should report this as defective because I went to test store model...not nearly as bad
Sent from my VS980 4G using xda app-developers app
Same issue with Verizon model for me. Not that common but very annoying when I do notice it.
I fixed it by wiping the screen with a micro fiber cloth and doing a full factory reset. I don't know which one fixed it. It works perfectly now. Using an AT&T G2.
I've been looking for a way to fix the over-sensitivity on the vzw device. The screen will seem to scroll extremely fast out of nowhere.
I thought it was just me. When I'm texting sometimes it will put two or three of the same letter in a row from just one touch. VZW model
Occasionally experiencing something of this nature on my VZW phone as well. Not frequent, though.
Having this same issue right now. I feel like it started happening after last week's software update (verizon).
Sent from my LG G2 using Tapatalk 4.
I had the same issue when scrolling thru the screens using Zedge to look for notifications and ringtones. It was a big pain in the butt.
has anyone figured this out? I literally can't use a browser because when I try to scroll, it just zooms in. so annoying
On the phone with a vzw rep at technical support now... She said that they don't have any reports of that on a mass scale. I told her that it doesn't happen all the time and she said that it was probably a fluke... Whatever! Obviously this isn't just a problem on my phone..
It doesn't happen mass scale because most people won't address or report the issue. Just bad on verizon for not testing
sensitive touch
I have the very same issue with the touch sensitivity, obviously since i have found this thread. I find that by turning the screen of then back on it tends to reset it. I just wish i didn't have to do it so often. I would rather not factory reset my phone being how it was already a pain to make the transfer of data in the first place. Plus in theory, the reset shouldn't work being that it came of the production line this way. No amount of resets will change the outcome of the hardware that was installed, until production fixes it for the next line. But if others have found solid longer lasting methods, minus tge reset, I'm willing to test them til i simply get tired of itand replace it.
I am on Verizon and get it occasionally. I just turn the screen off and back on, and that has corrected it every time so far. Not too annoying yet, but if it gets worse I'll try getting it switched out.
I'm guessing this is a software issue, but it only happens to me while web browsing
romeyjdogg said:
I'm guessing this is a software issue, but it only happens to me while web browsing
Click to expand...
Click to collapse
It only happens to me on xda forums lol
Quite honestly this whole phone seems to lag and have some sort of bugs here and there, very disappointed so far. The Note 2 is calling me.
Sent from my LG-D801 using Tapatalk 4
romeyjdogg said:
I'm guessing this is a software issue, but it only happens to me while web browsing
Click to expand...
Click to collapse
When mine does it it happens on any Web page and I tried on both chrome and Firefox and it still happened.
There's a thread on the regular Z5 forum discussing this:
http://forum.xda-developers.com/xperia-z5/help/fingerprint-hardware-available-t3354800
Just a warning to everyone. This happened to me today. A reboot fixed it, but it sounds like once it starts, it keeps happening. I can't think of any rhyme or reason for this, but the one thing that seems constant is that all these people have unlocked bootloader and most are using Xposed
Edit: this actually may be due to marshmallow and doze
Well....now i know why.....?
I was actually wondering why was it sometimes not available, thanks for the info.
Sent from my E5823 using XDA-Developers mobile app
Actually,
The more i read about it, the more it seems like it might be a problem with Doze mode of marshmallow. Nexus 6p and 5x users are experiencing this too, and some people believe it's doze. I went into my doze settings and undozed the 3 items in there that were related to fingerprint. Hopefully that is it.
ksc6000 said:
Actually,
The more i read about it, the more it seems like it might be a problem with Doze mode of marshmallow. Nexus 6p and 5x users are experiencing this too, and some people believe it's doze. I went into my doze settings and undozed the 3 items in there that were related to fingerprint. Hopefully that is it.
Click to expand...
Click to collapse
You may be right, i'll check with my phone if it's related to Doze, thabks for the info.
Sent from my E5823 using XDA-Developers mobile app
I have my bootloader unlocked, but I'm not rooted (can't figure out how to do it properly on this phone!) and I don't have Xposed installed, but I still have this issue. The fingerprint sensor will just randomly stop working. When the problem occurs, it says "fingerprint hardware unavailable" on the lock screen. I've just decided not to use the fingerprint sensor at all until this issue is resolved (if it ever will be).
I have to say, I'm really disappointed about the whole DRM thing. If I had known what exactly was going to happen with this phone I never would have unlocked the bootloader....
On lollipop using xposed for a while now and never an issue with fingerprint scanner.
dgrasley said:
I have my bootloader unlocked, but I'm not rooted (can't figure out how to do it properly on this phone!) and I don't have Xposed installed, but I still have this issue. The fingerprint sensor will just randomly stop working. When the problem occurs, it says "fingerprint hardware unavailable" on the lock screen. I've just decided not to use the fingerprint sensor at all until this issue is resolved (if it ever will be).
I have to say, I'm really disappointed about the whole DRM thing. If I had known what exactly was going to happen with this phone I never would have unlocked the bootloader....
Click to expand...
Click to collapse
are you on marshmallow? And if so have you white listed the three things that are related to fingerprint in battery optimization? If you'd like I can also help you with Rooting
I've had this happen once on my Z5C after 5 days uptime. It only happened after I upgraded to MM (185), unlocked bootloader, and rooted. No xposed. Reboot solved the problem at the time. Have yet to see it again, it's been a few days now.
ksc6000 said:
are you on marshmallow? And if so have you white listed the three things that are related to fingerprint in battery optimization? If you'd like I can also help you with Rooting
Click to expand...
Click to collapse
Yeah, I'm on MM.
I didn't even think about whitelisting the fingerprint scanner. I'll give that a shot.
As far as rooting, I would appreciate your help. I've rooted and flashed my last three phones without a problem. I must be missing some step along the way.
Tell me how you rooted yours.
ksc6000 said:
are you on marshmallow? And if so have you white listed the three things that are related to fingerprint in battery optimization? If you'd like I can also help you with Rooting
Click to expand...
Click to collapse
So, I sat down here and had another go at it. Got it rooted in 5 minutes. I'm not sure what I was doing wrong before...
Thanks again for your offer to help.
Cheers
camaro322hp said:
I've had this happen once on my Z5C after 5 days uptime. It only happened after I upgraded to MM (185), unlocked bootloader, and rooted. No xposed. Reboot solved the problem at the time. Have yet to see it again, it's been a few days now.
Click to expand...
Click to collapse
After 4 more days uptime, it happened again. Nothing out of the ordinary triggered it, except it was probably sitting untouched for about 1 hour, then when I picked it up again, I got the fingerprint hardware not available message.
I've now added the 3 fingerprint apps to the non-optimized list in case it's doze related.
I have the same issue, I'm making a switch to ZombieKernel (Zombie-b6) and will see if the issue persists.
camaro322hp said:
After 4 more days uptime, it happened again. Nothing out of the ordinary triggered it, except it was probably sitting untouched for about 1 hour, then when I picked it up again, I got the fingerprint hardware not available message.
I've now added the 3 fingerprint apps to the non-optimized list in case it's doze related.
Click to expand...
Click to collapse
I have been experiencing this even with the apps undozed. I would love to hear some feedback about this.
Sent from my E5823 using XDA-Developers mobile app
Kallu609 said:
I have been experiencing this even with the apps undozed. I would love to hear some feedback about this.
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm going on 4 days uptime now after un-dozing the appropriate apps, still working. However, after your observations, I am expecting mine to fail again. I will update this post or the Z5 post when/if it does.
There must be something unique to a small subset of our phones that is causing this to happen, since there is not a huge outcry of people complaining about this. I've wondered if it was the unlocking bootloader/rooting process that caused this somehow, but it still seems like there are not enough people complaining about this to be caused from that. One thing I am running that most others may not be is Android Wear. Anyone else experiencing this using Android Wear?
camaro322hp said:
I'm going on 4 days uptime now after un-dozing the appropriate apps, still working. However, after your observations, I am expecting mine to fail again. I will update this post or the Z5 post when/if it does.
There must be something unique to a small subset of our phones that is causing this to happen, since there is not a huge outcry of people complaining about this. I've wondered if it was the unlocking bootloader/rooting process that caused this somehow, but it still seems like there are not enough people complaining about this to be caused from that. One thing I am running that most others may not be is Android Wear. Anyone else experiencing this using Android Wear?
Click to expand...
Click to collapse
No android wear here. It has only happened me once after undozing, which was like 3-5 days ago, so it's nothing too bad. Before it was at least daily.
Sent from my E5823 using XDA-Developers mobile app
What are the 3 items u undozed ?
I only find 2 ?
jans1982 said:
What are the 3 items u undozed ?
I only find 2 ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66477142&postcount=19
Hi guys,
Due to an issue with a button I got a brand new Z5C.
I've flashed .185 on it, it's still locked and unrooted of course.
Got fingerprint hardware is not available today, it seems to be an kernel issue and not BL unlock issue.
Edit: I had a chat with Sony Support (mostly to give them the message to fix .185) and she suggested a software repair with Xperia compagnon, did that, now I'm still on .185 but I completely lost my fingerprint manager. I'm manually going back to .163 now and hope that will fix the issue.
Edit 2: Never mind what I said, it seems my hardware is malfunctioning, I can't get it back online anymore, I'm returning it for warranty.
Is anyone having difficulty unlocking the phone with fingerprint sensor?
It used to work like 95% of the time, but now I can barely get it to work.
Not sure what changed... maybe since the last software update?
Mine works perfectly, like 98 or 99% hitted. x720, 18s official.
Almost 100% for me.
Try to configure again.
Sent from my LEX720 using XDA Labs
Thanks! Must be the changes to my skin when I traveled out of the country to a very different climate. It's working much better now that I'm back. Weird...
My Oneplus 8 Pro arrived yesterday and I am immediately having issues with the fingerprint sensor.
The FPS enrolls just fine with no issues and then immediately after the setup it works when tested, a few minutes later though it just will not work at all. I have removed and re-added 3 times now with no change, the screen looks clean and there is no factory fit screen protector on this thing
Anybody else? Unsure if this is a hardware or software issue and really would rather not have to return it.
arsenal74 said:
My Oneplus 8 Pro arrived yesterday and I am immediately having issues with the fingerprint sensor.
The FPS enrolls just fine with no issues and then immediately after the setup it works when tested, a few minutes later though it just will not work at all. I have removed and re-added 3 times now with no change, the screen looks clean and there is no factory fit screen protector on this thing
Anybody else? Unsure if this is a hardware or software issue and really would rather not have to return it.
Click to expand...
Click to collapse
Works OK for me. It's not very accurate though and only picks up the correct print about 30% of the time. The 7pro was better.
Sent from my IN2023 using Tapatalk
arsenal74 said:
My Oneplus 8 Pro arrived yesterday and I am immediately having issues with the fingerprint sensor.
The FPS enrolls just fine with no issues and then immediately after the setup it works when tested, a few minutes later though it just will not work at all. I have removed and re-added 3 times now with no change, the screen looks clean and there is no factory fit screen protector on this thing
Anybody else? Unsure if this is a hardware or software issue and really would rather not have to return it.
Click to expand...
Click to collapse
I saw a video recently that suggested the scanner got better with time and, to some extent, learnt the more it was used. I'm not sure if it's placebo affect but I've certainly found that to be the case. It was rubbish to start with but has become more efficient.
Batfink33 said:
Works OK for me. It's not very accurate though and only picks up the correct print about 30% of the time. The 7pro was better.
Sent from my IN2023 using Tapatalk
Click to expand...
Click to collapse
I have also noticed that when it works it does not feel that fast either.
Strange thing is, I just had to log in using my pin and the FPS worked just fine for Lastpass but then again would not work to open the phone.