PLEASE DON'T TRY THIS FIX! If you are experiencing any touch screen irregularities, then it IS HARDWARE related. Use the warranty of the phone and either request a new device, or get a different device. Ignore the remainder of this post and the thread.
Sorry if this is very long and boring, but saying it all now saves everyone from saying it later
There is a massive problem that the Z1 suffers from, an erratic touch screen.
Some people have the problem, whilst others don't. I am one of the unlucky owners of a Z1 which has this problem :crying:
People report that the screen registers an input, then shortly losses the input and then regains it, making web browsing difficult as anything you scroll by could be clicked by accident.
I suffer from that and then some. If I use the phone for a prolonged period of time (usually 20 minutes), the screen will register my input at completely different places to where my finger actually is!
This makes normal use almost impossible since you have no control as to where it will register your input.
Oddly enough, locking the phone for a few seconds (just long enough so that the phone falls into deep sleep) then waking it again makes the problem disappear temporarily. It does start doing it again eventually. This happens regardless of phone temperature. This also proves that the issue isn't hardware related, as if it was then it should be doing this all the time, regardless of anything.
Trying to do a clean install fails to fix the issue (at least for me), and even the highly anticipated KitKat update failed to address the issue, despite them claiming that KitKat will fix it (it didn't work for me).
NOW comes the possible solution. Since I know that this could not be a hardware issue, there must be a way to fix it via the software.
I researched a lot and found something that could fix the issue.
I'm saying this now. I don't guarantee that this will fix the problem, but trying won't hurt anyone
I didn't do a nandroid backup (I'm on 4.4.2 = no system mount in recovery), but if you feel uncomfortable with this, then by all means make one
You will need the following:
Root
Terminal Emulator
Any file explorer with root access
External microSD Card
Any stock/stock based Sony ROM (try the fix on other custom ROMS if you want. No harm in trying, cough NANDROID IS YOUR FRIEND )
1: Open up the Terminal Emulator
2: Type in "su" with no inverted commas.
3: Type in the following command: touch /sdcard1/Calibration.ini
There must be a space between "touch" and "/".
If done right, you should get no response (no message at all, just back to "[email protected]:/ #"
4: Enter and after that, shutdown the phone. Whilst it is booting, do not touch the screen. You can safely touch the screen after it is done booting (when you can see the UI). You can also reboot it instead of shutting it down, but I found that a proper shutdown works better (your mileage may very).
5: Goto a file explorer and delete the "Calibration.ini" file. This will prevent the phone from calibrating the screen after every reboot (not needed since it has just been calibrated).
6: All done :highfive:
Now, test the phone properly and see if the problem is gone.
If you have the time and patience, I recommend setting the screen timeout to 30 minutes and using the phone without letting the screen turn off. If it doesn't do anything strange in that time, then you can safely assume that the problem is gone for good :highfive:
Ever since I did this, the problem has ceased to be. It has gone and met its maker
Hopefully you will have the same results
Even if it didn't work, there was no harm in trying
Good luck! :good:
Note: For the app that does the same thing as this method, see post #2
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment TouchRecalibrate.apk
Daelyn said:
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment 2645905
Click to expand...
Click to collapse
Those which you posted are not exactly the ones I discovered.
That would be this thread:
http://forum.xda-developers.com/showthread.php?t=1960416
I knew about that app also, but I don't want to risk using it. I think that the manual method is better since it can work on any phone (or at least I think every phone)
That app may only be developed for a specific device and using it on other devices sounds like trouble to me.
Either way, the manual method worked for me. I severely doubted it would work but it did. I tested the phone for at least 1 hour straight without letting the display turn off. Game after game I ran, battery drained by at least 18% and there was not a sign that the screen was going to bugger out again
I even set the screen timeout to 30 minutes just to make sure it won't sleep.
Still no sign of the problem, 5 hours later
I haven't rebooted it yet. I don't know if it will come back once a reboot has happened...
Seems to be working
I did your method and also changed the touch filter level from 2 to 5 as mentioned in another thread. I havent had the issue since, not sure if it was your method or his or a combination of the 2, but really glad its gone. Thanks a million.
Daelyn said:
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment 2645905
Click to expand...
Click to collapse
I tried the apk...for me it works fine for now... Will have to wait and see if it continues
Sent from my C6903 using XDA Premium 4 mobile app
Tried the method using terminal emulator and it seems the method has fix the problem,,
But i need to test again further..
Thankyou
Gesendet von meinem C6903 mit Tapatalk
I'm trying it with cm... I'll report in some days. But thank you allready
Tried the method. Touch sensor on the edge of the screen still seems quite buggy from time to time. Everything else seems to show some improvement. Will try a bit longer and report back.
Sent from my C6902 using xda premium
I'm tyring this fix on my Z1 flashed RomAur 6.1, and working fine.
Touch response is very sharp and fix touch problem.
Many Thanks!
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
[Fenix] said:
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
Click to expand...
Click to collapse
Space is missing after "touch"...
touch /sdcard1/calibration.ini
You forgot the space
Sent from my C6902 using xda premium
The app seems to invoke online calibration. Works fine here and I feel improvement. Of course it could be placebo.
I will try to disassemble the app when I got the time. I want to know what it does and how it does it.
Sent from my C6903 using Tapatalk
Please Delete, already answered.
Please Delete, already answered.
[Fenix] said:
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
Click to expand...
Click to collapse
you could also try the APK in the other post... i tried that and it worked for me
The app has definitely worked for me. I would mostly notice the bug when scrolling in the Falcon Twitter app - tweets would open accidentally all the time, it hasn't happened once since using the app.
R: Potential Xperia Z1 touch screen fix (please test)
Josh.L.Wang said:
touch /sdcard1/calibration.ini
You forgot the space
Sent from my C6902 using xda premium
Click to expand...
Click to collapse
RyokoN said:
Space is missing after "touch"...
Click to expand...
Click to collapse
lol maybe i'm blind
Thanks for the help it works
I'm very glad to see that people are having positive results with the terminal method and even the application that was linked earlier
Doubted that the application world work
I have to add this though. After testing a bit more, the problem hasn't come back. However, I did discover that wiping cache and delvik will make the problem come back again with a vengeance. So, I did the fix again and what do you know? Problem is gone again
One last thing. Every time the phone boots up with the Calibration.ini file, you might get different results with regards to calibration. I recommend that once you are contempt with the outcome of the calibration, DELETE THE FILE ASAP!
Also, shutdown the phone instead of rebooting it
Have fun
D395267 said:
I'm very glad to see that people are having positive results with the terminal method and even the application that was linked earlier
Doubted that the application world work
I have to add this though. After testing a bit more, the problem hasn't come back. However, I did discover that wiping cache and delvik will make the problem come back again with a vengeance. So, I did the fix again and what do you know? Problem is gone again
One last thing. Every time the phone boots up with the Calibration.ini file, you might get different results with regards to calibration. I recommend that once you are contempt with the outcome of the calibration, DELETE THE FILE ASAP!
Also, shutdown the phone instead of rebooting it
Have fun
Click to expand...
Click to collapse
I have not had any problems since using the app.. I have rebooted quite a few times and all is still good...
So nice to actually being able to use swipe keyboard without problems
We owe ye
Sent from my C6903 using XDA Premium 4 mobile app
New poll is up!
I bid you all good day
Related
My arc is locked but its auto rebooting...
Sent from my LT15i using XDA App
How very informative... great thread!
Juspus said:
My arc is locked but its auto rebooting...
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
More info?
when does it auto reboot?
Does it get hot?
did you try "Factory data reset"?
Juspus said:
My arc is locked but its auto rebooting...
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Did you possibly flash new firmware and that happened? You need to give us some more details.
Well it sometimes just randomly reboots...
Sent from my LT15i using XDA App
I did not do anything with it no new firmware nothing abd it doesnt get hot it reboots especialy when I am listening to music.
Sent from my LT15i using XDA App
Juspus said:
I did not do anything with it no new firmware nothing abd it doesnt get hot it reboots especialy when I am listening to music.
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
I don't got problems with listening to music, maybe some app is messing your phone. if you can't find the problem do a "Factory data reset", if this doesn't help you can bring the phone back and get a new one. It can always be a faulty phone.
My Arc sometimes reboots on me too but not randomly. It's always when it's doing something that maxes the CPU and I switch between apps simultaneously. It's quite annoying, no doubt. My old Desire never did this.
Hoping for a future fw update!
I'm on my third week with my arc and it never randomly rebooted.
Sent from my LT15i using XDA Premium App
2 weeks in and 2 reboots once during a call and once using google navigation
Sent from my LT15i using Tapatalk
It's being reported in the SE forum as well. You don't notice the reboot unless u put your phone within your view the whole day. Thats when you will notice the random reboots.
commodoor said:
I'm on my third week with my arc and it never randomly rebooted.
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
try ddfw, I ensure you will get one.
I even encountered one when the screen was off and it's doing nothing
Golgo said:
My Arc sometimes reboots on me too but not randomly. It's always when it's doing something that maxes the CPU and I switch between apps simultaneously. It's quite annoying, no doubt. My old Desire never did this.
Hoping for a future fw update!
Click to expand...
Click to collapse
this happen to me too,is this software/hardware fault??
tyrand3 said:
this happen to me too,is this software/hardware fault??
Click to expand...
Click to collapse
I'm pretty confident its caused by buggy software and not broken hardware.
Looking forward to flashing some custom roms and kernels to get around this and up the perfomance
15 times
my arc have randomly rebooted at least 15 times in the past 3 days. it's so annoying. what's that thing with stuffing tissue paper on the back does it work?
i've reflashed mines twice now, and done reset to factory default on top of that after the second flash for good measure, and it's still rebooting when it feels like it. i uninstalled a weather widget, and i got almost 5 hours of constant uptime. i'm about to reflash it again and not install anything, maybe just battery monitor so i can tell how many hours/minutes i can get before it reboots again.
i read about the battery fit, and i have tried various things to try and see if that was the issue, but nothing physical seems to make it reboot, and like some others, i have seen it reboot when the lcd is off and the phone isn't doing anything.
i'd really like to be able to use this arc!
mine just had the first random reboot...first I thought that the battery was all drained out but then realised after switching it back on that it was at 20%...
the phone was on idle, locked...weird!!!
Just had my first random reboot after a months use, was using google nav while charging from the cigarette lighter. Quite annoying as i was trying to find my way somewhere and suddenly realised i hadnt had any instructions for a while. The phone had gotten quite hot - i think google nav must work it pretty hard.
zanndoth said:
You don't notice the reboot unless u put your phone within your view the whole day.
Click to expand...
Click to collapse
If you use the home button to switch between recent apps a lot (i do) then it's pretty obvious if your phone's been rebooted as the recently used apps list is empty, so i'm fairly sure this is the first time my phone's rebooted on its own.
Random reboot here, too. ^^
I was typing an email with Google Mail app (with wifi and mobile data connection turned off, actually), when the screen became all coarse and broken (does anyone remember old DOS games crashes? ^^) and then it rebootet. Everything fine afterwards except for my email, which was gone.
cherryfish said:
Random reboot here, too. ^^
I was typing an email with Google Mail app (with wifi and mobile data connection turned off, actually), when the screen became all coarse and broken (does anyone remember old DOS games crashes? ^^) and then it rebootet. Everything fine afterwards except for my email, which was gone.
Click to expand...
Click to collapse
Happened to me once... exactly as you described except I was retrieving email at that time, not typing or touching the screen at all.
I bought a gnex 2 days ago and have some weird issue. Occassionally, when unlocking the phone, the phone stops responding for 30-45 seconds, reboots itself and is sending me a bugreport. The report can be found in the link below. Also, there is a screenshot saved every time thta happens, however the screenshot is only the lock screen.
After the reboot the phone becomes a bit slow when switching between applications, after I manually reboot once more it works flawlessly again.
The android version is the stock 4.1.1 JellyBean. The phone is rooted.
Note: I had the same issue with my Nexus S before, but I thought its because its a lot slower.
Bug report link:
https://docs.google.com/open?id=0B_FOxKiTQcvbZEdGMDUwUEJtRWM
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
I bought a gnex 2 days ago and have some weird issue. Occassionally, when unlocking the phone, the phone stops responding for 30-45 seconds, reboots itself and is sending me a bugreport. The report can be found in the link below. Also, there is a screenshot saved every time thta happens, however the screenshot is only the lock screen.
After the reboot the phone becomes a bit slow when switching between applications, after I manually reboot once more it works flawlessly again.
The android version is the stock 4.1.1 JellyBean. The phone is rooted.
Note: I had the same issue with my Nexus S before, but I thought its because its a lot slower.
Bug report link:
https://docs.google.com/open?id=0B_FOxKiTQcvbZEdGMDUwUEJtRWM
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Have you done a factory reset?
I would say one of your apps is causing this.
That is my idea aswell (since I imported my apps via Ti backup from my nexus s - only the user apps, without data), the issue is that I really dont have the time to test 1by1and actully all I apps that I have installed are apps I use aswell, so I figured someone here might figure out what exactly causes this from the crash log i supplied.
Sent from my Galaxy Nexus using Tapatalk 2
well, i'm not sure but:
i see a bunch of errors after
Code:
------ ducati trace1 (/d/remoteproc/omap-rproc.1/trace1: 2012-09-28 00:30:19) ------
searched a bit around, found this: http://omappedia.org/wiki/Category:RPMsg
Maybe you could try flashing ICS? binaries are probably different, and although I'm not sure it would solve anything, but it's worth a try.
edit: does your device get hot rapidly?
bk201doesntexist said:
well, i'm not sure but:
i see a bunch of errors after
Code:
------ ducati trace1 (/d/remoteproc/omap-rproc.1/trace1: 2012-09-28 00:30:19) ------
searched a bit around, found this: http://omappedia.org/wiki/Category:RPMsg
Maybe you could try flashing ICS? binaries are probably different, and although I'm not sure it would solve anything, but it's worth a try.
edit: does your device get hot rapidly?
Click to expand...
Click to collapse
Usually between 30-36°C (i saw 36 only once so far)so I guess it doesnt get hot.
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
Usually between 30-36°C (i saw 36 only once so far)so I guess it doesnt get hot.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
okay. try flashing ICS, see where that leads you.
follow this guide if you need instructions.
Also try factory reset with no apps import from TI and see how you do for a few hours.
Sent from my Galaxy Nexus using xda app-developers app
Update: another weird thing (it might br the cause of the problem), if i happen to press all 3 hard keys (vol up + down+power) while the phone is turned on i get the same thing as described above.
Could anyone try to reproduce this?
Sent from my Galaxy Nexus using Tapatalk 2
Found the cause of the problem: its the su binary from Superuser 3.2 RC.
The solution is to swap to either SuperSU or Superuser 3.1.3.
The problem does occur oy when all 3 hard keys are pressed, however it will not crash if a other binary is present (instead of the 3.2 one) in case of the other versions the bug still occjrs (bugreport appears) and the su log shows a lot of su rewuests by "shell", anyway no syst reset or slow response happens.
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
Found the cause of the problem: its the su binary from Superuser 3.2 RC.
The solution is to swap to either SuperSU or Superuser 3.1.3.
The problem does occur oy when all 3 hard keys are pressed, however it will not crash if a other binary is present (instead of the 3.2 one) in case of the other versions the bug still occjrs (bugreport appears) and the su log shows a lot of su rewuests by "shell", anyway no syst reset or slow response happens.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
great, you solved it. thanks for sharing. thumbs up for this thread. could you please edit the title to include tag "[SOLVED]"?
sent from my i9250
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Hi, what's your eMMC version? Maybe buggy memory, try looking at other threads.
Отправлено с моего Galaxy Nexus через Tapatalk
Have you tried different batteries?
GeeNex | Carbon nightlies | Rubiks
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Djalaal said:
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Click to expand...
Click to collapse
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
krugdenis said:
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
Click to expand...
Click to collapse
Well, I am planning to root again. I want to switch back to CyanogenMod 10.1. Lagfix app isn't needed if you can use -discard mount option right? How to use either, if let's say I'm on CyanogenMod. This is also the first time I hear of lagfix and discard mount... :/
Btw, the app i used to check my eMMC Type said that my chip is ok. No brickbug. Are you sure it's buggy?
http://code.google.com/p/android/issues/detail?id=39154
Отправлено с моего Galaxy Nexus через Tapatalk
I might be wrong here, but from what I've read at the link and other xda posts (http://forum.xda-developers.com/showthread.php?t=2029246), the V3U00M chip is not buggy (in the sense that it's stable for rooting and using the -discard command), but it does give slowdowns. I do have horrible slowdowns, so thanks for that solution I didn't know existed. However, this doesn't solve my random reboot problem at all...
No one else got any solid way to find out the source of the problem?
BUMP
Djalaal said:
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Click to expand...
Click to collapse
Same as you man...
I'm seriously considering throwing my phone to the garbage. I don't like iPhones, but google is really pushing me into it with this crappy piece of phone. Is so frustrating to have these rebooting issues, I've tried everything, from wipe to factory reset, back to stock, flash custom ROMS and KERNELS, turning location access off, uninstalling all apps/widgets that might interfere, and every single "solution" it's out there, and STILL I'M HAVING THESE DAMN REBOOTS!
Now it's even worse, I can't even transfer files to my phone anymore because, guess what... IT REBOOTS! everytime I transfer ANY KIND of file.
The only thing that seems to work for a while is reformatting and start from scratch. I've done that like 3 times already. But still after a few weeks the issue reapears... i'm really mad about this, and no one seems to care. Not Google and not even Samsung.
The only interesting thing that i found around the internet is this guy's findings
plus.google.com/113601948978986762347/posts/2ALASEC1dG2
I read the log on my phone and matches to his... but now the thing is, what do i do with this information? I'm not a programmer o something like that.
Any ideas?
I think your board is faulty. Even so, have you tried disabling SR and raising voltages across the board? Trimming eMMC? Omapflash?
a manta wrote this.
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
elcampeondelrodeo said:
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the reply guys!
mrgnex said:
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
bpyazel said:
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
elcampeondelrodeo said:
Thanks for the reply guys!
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
Click to expand...
Click to collapse
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
elcampeondelrodeo said:
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
Click to expand...
Click to collapse
Well if it keeps rebooting you can try to over volt. Maybe that helps.
Sent from my Galaxy Nexus using XDA Premium HD app
OK I'll try that! Thanks for your help man!
Sent from my Galaxy Nexus using xda app-developers app
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Ameer Shimoga said:
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Click to expand...
Click to collapse
How do you fix it when it happens? Do you have to restart? Does the touch fail or does the tablet freeze?
Honestly not very sure what you could do, besides maybe trying a factory reset? That would work if a software problem.
What about cleaning it and removing any screen plastic guard.
U can say it freezes then I have to restart it. This is happening after two factory resets.
Sent from my Xperia U using XDA Free mobile app
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
mdamaged said:
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
Click to expand...
Click to collapse
OK I'll try..
Sent from my Xperia U using XDA Free mobile app
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
nebhead said:
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
Click to expand...
Click to collapse
Look 2 posts up from yours.
mdamaged said:
Look 2 posts up from yours.
Click to expand...
Click to collapse
Oops - I looked at the link to the hardware fix, but not the firmware fix. Thanks, I'll give this a try first.
Firmware fix above seems to have alleviated the issue for me. At least I haven't seen the issue over the last several days, which is good news. Hopefully that holds up over the long term. :good:
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)