Related
I am getting this several times a week. It lives on the Sony charger dock but quite often will not wake and has to be reset o get it to work. I even get this when it's flashing that I have notifications.
Sent from my HTC One X using Tapatalk 2
descb600f said:
I am getting this several times a week. It lives on the Sony charger dock but quite often will not wake and has to be reset o get it to work. I even get this when it's flashing that I have notifications.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Me too, since one week
Did you mean restart?, I do get the issue has well due to something in the background was ignoring the lockscreen or something but you can force power off.
Sent from my Sony Tablet S using xda premium
No I have to put a paperclip into the reset hole for a few seconds before anything happens. Don't seem to lose any settings but it does then restart
Sent from my HTC One X using Tapatalk 2
descb600f said:
No I have to put a paperclip into the reset hole for a few seconds before anything happens. Don't seem to lose any settings but it does then restart
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Did you try a force power off (Hold power for a while)?
Sent from my Sony Tablet S using xda premium
Yep it will not turn off or on, only thing that seems to work is paperclip into the reset hole
Sent from my HTC One X using Tapatalk 2
what firmware are you on and are you rooted?
Completely standard and on the latest version. No updates available when I check.
Sent from my HTC One X using Tapatalk 2
if possible i would consider sending it back for repair.
i'm not sure that there is anything you could do your self to fix the problem at the moment.
my xperia tab has smiler issue like not responding to wake directly and might take longer some times but eventually does wake, without needing to be reset.
have you tried to run it completely stock?
without any adjustment to settings or adding accounts just like it's fresh out of the box.
Seems Sony know something about irony. Picked up the tablet tonight and there was an update waiting for me. We'll see how this version goes
Sent from my HTC One X using Tapatalk 2
All seems fine since update
Sent from my HTC One X using Tapatalk 2
mines been doing this ever since i did the latest stock update. i have to reset with a pin everyday now just to get it to come back on if its been left for too long
Last update defiantly fixed mine.
Android Version 4.0.3 (release 5a)
Kernel Version 2.6.39.4 [email protected]#1
Build number TISU0033410
Sent from my HTC One X using Tapatalk 2
Anyone else experiencing issues with the sensitivity of the back button? I noticed that if the back button is pressed closer to the left of the point versus solidly in the center of the button, no touch is registered. Previous Android phones seemed to have a slightly larger touch area, but on the One touches have to be pretty precise. I find myself having to hit back multiple times to complete the task.
Sent from my HTC One using xda app-developers app
kyndacrazy said:
Anyone else experiencing issues with the sensitivity of the back button? I noticed that if the back button is pressed closer to the left of the point versus solidly in the center of the button, no touch is registered. Previous Android phones seemed to have a slightly larger touch area, but on the One touches have to be pretty precise. I find myself having to hit back multiple times to complete the task.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah there quite a few threads about the sensitivity of the buttons and screens here and on the international forum. I think an update came out for international that addresses these issues.
Sent from my HTC One using Tapatalk 2
godfirst said:
Yeah there quite a few threads about the sensitivity of the buttons and screens here and on the international forum. I think an update came out for international that addresses these issues.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Let's hope that it moves through the ATT lab quickly.
Sent from my HTC One using xda app-developers app
This seems to be a huge problem effecting all variants:
http://forum.xda-developers.com/showthread.php?p=40573865#post40573865
Rumor has it the Taiwan variant received an update that fixed it, althogh I'm not convinced it's not a hardware defect.
m03sizlak said:
This seems to be a huge problem effecting all variants:
http://forum.xda-developers.com/showthread.php?p=40573865#post40573865
Rumor has it the Taiwan variant received an update that fixed it, althogh I'm not convinced it's not a hardware defect.
Click to expand...
Click to collapse
Can confirm after trying a international Rom the issue was fixed. So it's a software issue.
Sent from my HTC One using Tapatalk 2
Hey guys check this out.
I'm lucky to get 3.5 hours screen on time at the minute.
Thinking about downgrading to .256 because I didn't have the problem then, what do you think
J
Sent from my C6833 using xda app-developers app
Looks like it's fast dormancy that's raping your battery. What's fast dormancy? Read here. Check if your carrier supports it. If they don't, disable it.
Or you can simply check out this video
Yeah I've looked online, never had this problem in the firmware before, so thinking about downgrading.
And to disable It, I'll have to root :/ how would one go about doing that? Going through root explorer or?
Plus, I'm thinking If I root it, I should make a TA backup If I decide to flash anything. How would one go by doing that?
Thanks J
Sent from my C6833 using xda app-developers app
JackHanAnLG said:
Yeah I've looked online, never had this problem in the firmware before, so thinking about downgrading.
And to disable It, I'll have to root :/ how would one go about doing that? Going through root explorer or?
Plus, I'm thinking If I root it, I should make a TA backup If I decide to flash anything. How would one go by doing that?
Thanks J
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
Ehh.. I wouldn't go through all of that just to change one tiny thing. It's actually just simpler to downgrade or upgrade, depending on the build you're on now. I personally like 290 and I have never had any issues with it. I'm not running it now though (GPe), but it's a good one. I read that 136 has some issues.
Sent from my C6806_GPe using Tapatalk
I had a few bugs in .290 and I'm currently on .136 the latest with this problem.
If I Downgrade will I lose my IMEI like I see most people do ?
Thanks
J
Sent from my C6833 using xda app-developers app
Read my downgrade guide to keep imei
Sent from my Xperia Z Ultra using Tapatalk
I also have noticed a substantial increase in the wakeups on .136.
And I rarely am off Wi-Fi, if at all, and according to the FD theory mentioned as the possible culprit, that wouldn't be what is increasing my wakeups.
Very strange.
we have stamina for it.
hassanmahmood said:
I also have noticed a substantial increase in the wakeups on .136.
And I rarely am off Wi-Fi, if at all, and according to the FD theory mentioned as the possible culprit, that wouldn't be what is increasing my wakeups.
Very strange.
Click to expand...
Click to collapse
Yup, and FD only applies to 3G, so it can't and won't happen if your on 2G, 4G or WiFi.
Sent from my C6806_GPe using Tapatalk
I took a screenshot of this beauty last night. Almost half a MILLION wakelocks, LOL (the one at the bottom)! Not having any battery issues though. I'm currently on the GPe ROM.
Sent from my C6806_GPe using Tapatalk
That's interesting...
Sent from my Nexus 7 using xda app-developers app
LordManhattan said:
Yup, and FD only applies to 3G, so it can't and won't happen if your on 2G, 4G or WiFi.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Im going to need to get a 4g sim from my carrier, last time I tried they sent Another 3g sim
Sent from my Nexus 7 using xda app-developers app
Too bad, after one whole day and night with 2.5 hours SoT, now it's still 55+%
Extreme battery savings measure:
STAMINA
Tasker
Greenify
Done. Three days without charging.
I searched for it but apparently found nothing... you know when you go in settings, About Phone, and click multiple times on "Android Version" (on 4.4.2)?
Well, on other devices (on 4.4.2 too) when clicking on it, it appears a big "K", and then clicking on it you get the Kit Kat red screen.
Why is a big "1" appearing instead of the "K" on our device?
Sent from my C6833 using Tapatalk
Maybe it signifies Z1 :/ just what i think.
I personally see no connection with anything
Sent from my C6802 using XDA Premium 4 mobile app
Yup, I've also noticed this, and I have no idea why.
Sent from my Desire HD using Tapatalk
It's nice to find out I'm not the only one puzzled by this... and it's also nice that nobody knows the reason of that one... XD
Sent from my C6833 using Tapatalk
I tried to Google a little bit about it, but it's incredible hard to find anything about it since it's near impossible to search for "Android easter egg 1 instead of K". That won't work, so I've concluded that the internet is stupid.
Sent from my Desire HD using Tapatalk
Click on the "1" then it takes you this
Sent from my C6833 using xda app-developers app
MrJai said:
Click on the "1" then it takes you this
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
Yup, but the thing is; it should be a K and not 1.
Sent from my Desire HD using Tapatalk
Maybe it's their 1 St release of 4.4.2
Sent from my C6833 using xda app-developers app
LordManhattan said:
I tried to Google a little bit about it, but it's incredible hard to find anything about it since it's near impossible to search for "Android easter egg 1 instead of K". That won't work, so I've concluded that the internet is stupid.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I may have found something.
Someone in other forums found out that since the "K" appears on Nexuses, the build number is the culprit, since it has the format KOT49N, beginning with a "K"; our build number begins with a "1" (14.3.A.0.681), and the Moto X has a similar format, so we both get a "1" instead of the "K".
I'm not rooted at the moment, is someone willing to try changing the build.prop number with a beginning "X" to see what happens?
Sent from my C6833 using Tapatalk
fastest83 said:
I may have found something.
Someone in other forums found out that since the "K" appears on Nexuses, the build number is the culprit, since it has the format KOT49N, beginning with a "K"; our build number begins with a "1" (14.3.A.0.681), and the Moto X has a similar format, so we both get a "1" instead of the "K".
I'm not rooted at the moment, is someone willing to try changing the build.prop number with a beginning "X" to see what happens?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Interesting. I'm still waiting for my ZU, which should arrive today, so I'll probably take a look at it later.
Edit: Just checked my Desire HD which is running custom CM11, and I didn't see this one coming
Sent from my Desire HD using Tapatalk
Battle on who is more capable of searching through Google: LordManhattan 0 - fastest83 1.
I'm gonna put this in my resumee.
Sent from my C6833 using Tapatalk
fastest83 said:
Battle on who is more capable of searching through Google: LordManhattan 0 - fastest83 1.
I'm gonna put this in my resumee.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Stop the music! Those two screens pops up if i tap the "CM version", but if i tap the Android version, i'm getting the "K" We need another phone with KK to double check
LordManhattan said:
Stop the music! Those two screens pops up if i tap the "CM version", but if i tap the Android version, i'm getting the "K" We need another phone with KK to double check
Click to expand...
Click to collapse
Too late. I'm already admitted at the MIT.
Sent from my C6833 using Tapatalk
fastest83 said:
Too late. I'm already admitted at the MIT.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Damn it. Fine, I'll let you have this one
Sent from my C6833 using Tapatalk
Will it be a 2 wit the 2nd kitkat update
So, randomly my vibrate just stops working randomly for the phone and then suddenly works again. I just updated my firmware and it just started happening recently. I'm assuming it's the software but any ideas what I can do?
Sent from my D6503 using Tapatalk
Lostatsea23 said:
So, randomly my vibrate just stops working randomly for the phone and then suddenly works again. I just updated my firmware and it just started happening recently. I'm assuming it's the software but any ideas what I can do?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
I seem to have the same issue
I think its a hardware fault or at least with my case it is. its happened across 3 different firmwares and i have found that shaking or hitting my phone actually fixes it, this proves to me few possible
For you id recommend flashing a new firmware one more time and seeing if it shows up again, if it does then it is defiantly a hardware issue
Ill be sending my Z2 back
Details for others (about my device):
Camera lense is off centre
Gap at the top right
Gap at the bottom left
Audio jack doesent look right + very small gap
Random vibration loss
Sent from my D6503 using XDA Premium 4 mobile app
Envious_Data said:
I seem to have the same issue
I think its a hardware fault or at least with my case it is. its happened across 3 different firmwares and i have found that shaking or hitting my phone actually fixes it, this proves to me few possible
For you id recommend flashing a new firmware one more time and seeing if it shows up again, if it does then it is defiantly a hardware issue
Ill be sending my Z2 back
Details for others (about my device):
Camera lense is off centre
Gap at the top right
Gap at the bottom left
Audio jack doesent look right + very small gap
Random vibration loss
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did it and shaking it helped as well but idk if that's a placebo because it hasn't done it since I flashed a new kernel and rom on the phone... So there's that lol. I also have a tiny gap on the bottom left but it's barely noticeable in fact I didn't notice it until you pointed it out. I love the phone and not gonna use my square trade warranty for it just yet
Sent from my D6503 using Tapatalk
Lostatsea23 said:
Mine did it and shaking it helped as well but idk if that's a placebo because it hasn't done it since I flashed a new kernel and rom on the phone... So there's that lol. I also have a tiny gap on the bottom left but it's barely noticeable in fact I didn't notice it until you pointed it out. I love the phone and not gonna use my square trade warranty for it just yet
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
if the vibration issue shows up again then you know its a hardware issue, its better to have something working but not something faulty, faulyt things just kill them selfs more
And im with you, I love the phone more than my old phone, i realy dont want to send it back, i just want to play games @60fps but unfortionately it is a problem that is affecting the user (thats me )
ive had alot of other issues
here are some more i forgot to list
No heating with camera but majour heating just doing random tasks:
Camera apears to take photos in a very red hue
There is a Gap on the top left of the screen too
some others, too tired to think
Same problem here with the haptic feedback. It happens cuts out now and again while typing but seems to start working again on its own after a few more presses.
Not overly bothered as am very happy with the phone otherwise so won't return it to the manufacturers until it packs in completely within my warranty period.
I have got slight gaps on the screen on the bottom left and top right and maybe a slight off centre rear camera but if I hadn't known to look for these I wouldn't and don't really see them as a problem.
Sent from my D6503 using Tapatalk
Agreed, I don't think it's a hardware problem to be honest so we will see what happens when it gets updated a little more as I've seen some people with this problem.
Sent from my D6503 using Tapatalk
Hmm did it again today, don't know what to do at this point since I imported this phone... I don't know if it's hardware or software honestly
Sent from my D6503 using Tapatalk
Lostatsea23 said:
Hmm did it again today, don't know what to do at this point since I imported this phone... I don't know if it's hardware or software honestly
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Probably hardware if it does it across firmwares
My issue is definatly conformed hardware, yours too, you should check
Sent from my D6503 using XDA Premium 4 mobile app
Envious_Data said:
Probably hardware if it does it across firmwares
My issue is definatly conformed hardware, yours too, you should check
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah if I shake it it goes away but It could be voltage output that's making it worse or something, I heard the motor is actually easy to access and replace so if it comes to that I could to that possibly. I haven't factory reset it at all and I upgraded my firmware and it's worse then the one I had on stock... Odd to see so many people with this issue though.
Sent from my D6503 using Tapatalk
Lostatsea23 said:
Yeah if I shake it it goes away but It could be voltage output that's making it worse or something, I heard the motor is actually easy to access and replace so if it comes to that I could to that possibly. I haven't factory reset it at all and I upgraded my firmware and it's worse then the one I had on stock... Odd to see so many people with this issue though.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
It could be a manufacturing bug, some types of robots need to be taught how to do their job and can realy eadilu guess the rest
This doesent seem to be a batch spesific issue
Sent from my D6503 using XDA Premium 4 mobile app
No it seems like a lot of people to having this issue as far as I know. I'm gonna just deal with it for a while if I have to... Coming from the m8 which had even more quality control issues and going through like 5 of those.. Kind of tiring lol and I guess you can't strive for perfection although this should be fixed... Maybe someone can call Sony and chime in and let us know exactly what's going on and if they're aware of this issue.
Sent from my D6503 using Tapatalk
Lostatsea23 said:
No it seems like a lot of people to having this issue as far as I know. I'm gonna just deal with it for a while if I have to... Coming from the m8 which had even more quality control issues and going through like 5 of those.. Kind of tiring lol and I guess you can't strive for perfection although this should be fixed... Maybe someone can call Sony and chime in and let us know exactly what's going on and if they're aware of this issue.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
They are awear of the issue,.ive heard current production devices have little issues
This is an odd thing from sony to have such issues, xperias always have problems, but not as bad as this aparently
Sent from my D6503 using XDA Premium 4 mobile app