Related
the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.
PTMensah said:
the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.
Click to expand...
Click to collapse
Is your phone in warranty?
can you give us some basic information? such like rom & kernel version, wether you rooted and ade using cputuningtools or something like that.
if you are under stock rom(original samsung & all further updates over kies) and u have done nothing unnormally so far i would recommend use the warranty too; )
Sent from my GT-I9003 using XDA
thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging
PTMensah said:
thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging
Click to expand...
Click to collapse
I had the same issue. I got my touch panel replaced by the Samsung guys. That's why I was asking whether your phone is under warranty or not.
Sent from my SIII looking SL
....
...
I'm more on XDA than FB...
Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.
Skander1998 said:
Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.
Click to expand...
Click to collapse
Agree. :good:
I'll wait for a few weeks or till the phone is usable for the kernel 3.0. :fingers-crossed:
If not then no other option but create a Rs.5000 hole in my pocket. :crying:
Same case with me... Bought the i9003 March 2011.
I'm on DDKP3 and around the same time as the OP, my touchscreen started to act strange... responsive only when charger is plugged in. Tried factory reset, but problem came back after some hours!
If this is a product-wide issue, then I guess sammy should replace it for free, even if it's out of warranty... too busy to go to the nearest service cenrter, will check later.
Till then, please keep me updated how it goes for you.
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
Just wondering, if a reflash of DDKP3 via ODIN or any custom ROM would solve the issue... please suggest.
I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium
^^^ So what do you suggest?
agnivo007 said:
^^^ So what do you suggest?
Click to expand...
Click to collapse
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium
Same problem!!!
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.
Possible solution !!!
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...
Flashing the ROM does not solve the problem
neetinnagap said:
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.
Click to expand...
Click to collapse
I've sent the phone to the samsung guys who have flashed the phone twice but the problem still persists.
PLs keep us updated
agnivo007 said:
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...
Click to expand...
Click to collapse
Thanks.
Pls keep us updated
Problem Solved!!
Thanks to agnivo007.
I guess the climate is the only reason. I used his method to heat up my phone a little bit by charging it enough. Than it started working fine. No problems since then. Lets see.
ephraim033 said:
I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.
Skander1998 said:
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.
Click to expand...
Click to collapse
ephraim033 said:
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Sent from my GT-I9100 using xda premium
Touch Screen non-responsive Problem
I had the same issue and when i dismantlement the thing, came across a small batter. could this be the reason? Cos while charging this battery is not used but when running with battery, this small dry typed batter can be in use.
Found Any Solution
Could any 1 find a solution for this matter?
If so pls. update. Mine is still there.
I can't get rid of it.
Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.
A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.
zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.
Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse
So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.
same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?
zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??
semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.
Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?
Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it
I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.
Rma
Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.
Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message.
Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery !
Here's a list of things I tried and that didn't do anything:
Try to cancel the shutdown somehow
Booting the tablet multiple times
Factory Reset
Also, I can't seem to use it with my computer since, well, that damn shutdown on startup.
So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames.
And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.)
I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign !
And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop.
EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay
EDIT 2: The message is:
Power Off
Shutting Down...
WavingStory said:
Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message.
Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery !
Here's a list of things I tried and that didn't do anything:
Try to cancel the shutdown somehow
Booting the tablet multiple times
Factory Reset
Also, I can't seem to use it with my computer since, well, that damn shutdown on startup.
So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames.
And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.)
I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign !
And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop.
EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay
EDIT 2: The message is:
Power Off
Shutting Down...
Click to expand...
Click to collapse
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
NaminatoR1254jaime.sier said:
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
Click to expand...
Click to collapse
So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ?
EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ?
EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird.
WavingStory said:
So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ?
EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ?
EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird.
Click to expand...
Click to collapse
Very weird. Must be defective. Did you try reflashing stock images via fastboot? (I've never done it, fyi)
NaminatoR1254jaime.sier said:
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
Click to expand...
Click to collapse
Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ?
WavingStory said:
Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ?
Click to expand...
Click to collapse
I have the same problem. I've tried flashing the recovery 2.1 files, sideloaded the 2.2 ota, etc. The last thing i'm going to try is wiping the system with trwp then installing the 2.1 recovery again.
-that did not work. I have initiated the RMA process.
Anyone has some instruction how to safely open a NVIDIA Shield Tablet ? I woud love to check if some hardware went off so I can rebuild it.
EDIT: Wait, it can't be hardware... It just can't ! Why ? Well... simply because right now i'm in TWRP recovery, everything is working exept... oh wait... CPU temperature is going crazy. 429491929 C... yep... I don't think that's right.
Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY !
Bad thing, it's the CPU thermometer, it has gone crazy.
So, I installed you know, that TWRP recovery, and I checked the CPU temperature.
Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang.
CPU: 429491899 C.
That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet.
So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat !
EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me !
WavingStory said:
Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY !
Bad thing, it's the CPU thermometer, it has gone crazy.
So, I installed you know, that TWRP recovery, and I checked the CPU temperature.
Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang.
CPU: 429491899 C.
That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet.
So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat !
EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me !
Click to expand...
Click to collapse
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
NaminatoR1254jaime.sier said:
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
Click to expand...
Click to collapse
Well, I would have taken a picture, but I have nothing to capture pictures with... so.. yeah. Else I would have taken photos, it's pretty safe to open it by the way.
If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model...
Sent from my SHIELD Tablet using XDA Free mobile app
NaminatoR1254jaime.sier said:
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
Click to expand...
Click to collapse
An Droid said:
If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Nope, it's a sort of small bar near the camera, just on the top of it, it's made of some steel I think !
2 questions
I'm having the same problem. I already have opened the cover based on how you described it.
1. I can't find the thermometer and what kind of fix should I do with it?
2. How did you install TWRP when the device couldn't even boot properly.
Thanks
---------- Post added at 06:39 PM ---------- Previous post was at 06:01 PM ----------
I blindedly pushed some components back (dangerous) and decided to put back the cover. I rebooted and yeah, it booted properly! However,after a few minutes it auto shut down again. So I guess the theory that it's about the CPu thermometer might be true.
The question is, where is it really located and what should be it's position? Thanks.
Finally Fixed!
After several sessions of tinkering the unknown components of the hardware, I finally decided to take it to the next level. So I carefully removed the electrical tape covering the perimeter of the battery. Lo and behold - there's a white wire that is loose and I've determined its correct connection through its length.
Since I didnt have a soldering iron and I'm too afraid to use it should I have one, I used brute force connection via electric tape. I peeled more skin to secure conductivity.
Apparently, it's the connection to the CPu thermometer. When it is unlinked, it should register as weirdly high value, triggering hard reset. During the boot up and initialization, the firmware takes note of the value. After studying the behaviour of the problem, apparently the firmware in the chip also occasionally checks the temperature esp when an app is launched. This explained why I couldn't boot at the beginning or if ever boot was successful, antutu causes shut down. So as a solution, I made sure the contact between that freaking white wire and the solder placement on the board MUST be secure.
I'm using my fixed shield tablet to post here Btw. Apparently it has become faster. Antutu is 55,000. But charging the battery seems slow. I must have accidentally messed up something with the battery.
Boy I love my Shield tablet!
Thanks many many times!!
It fall down of the carpet and later that evening I noticed that it s off.
thanks the happenstance that TWRP shows the CPU Temperature it was fast located.
so I was able to search for.. and finally xda did it again..
Thanks all of you
Same problem
Well, my tablet got the same problem
Here some pictures, can you tell me where is the temeprature sensor?
Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located.
First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps.
SalehCoder said:
Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located.
First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps.
Click to expand...
Click to collapse
wow ... excellent post. this also solved my restart problem. thank you very much.
interesting side-fact: this only affected stock images. all alternative roms (bliss, etc. ...) started fine ...
I've got this exact problem as well but even after soldering this white wire, it keeps shutting down..
Edit: after some more attempts, I got a new temp: 92c. But I still got shut downs.. So I managed to switch it back to that weird 42516516161 etc temperature and now it wont turn off with the Custom Rom Bliss Pop.
I had the same issue. The device started to shut down by itself, sometimes right after boot. Luckily I stumbled to this thread while googling for the issue. Then I verified the problem by installing cpu-z and watching the temperature while waiting for the device to power off. Indeed, just before powering off the sensor jumped to -46 C. So with your help I found the culprit and soldered it back. No shutdowns ever since!
Hi, I replaced myself the screen (preassembled screen+digitizer+frame). After the replacement everything worked perfectly for like two hours when i rebooted it, from then on it is extremely laggy and stutters from boot animation, and when I press the power button (or when the screen shuts down), the phone itself shut down. In bootloader it doesn't seem to have problems.
I checked every connection inside the device (I've disassembled ad reassembled it several times).. thinking of a software problem, I've flashed marshmallow stock rom frist, and kitkat 4.4.4 then... but it's the same with any factory image.
Maybe I damaged something on the mainboard?
I also made a video to explain the problem:
with a lot of patience I set up a google account and downloaded cpu-z to see if maybe temperature sensor where giving wrong information to the system, but they're fine and everything seems to work propely aside from the stutter.
thanks to anyone who will help me, I'm almost giving up
RedMaio said:
Hi, I replaced myself the screen (preassembled screen+digitizer+frame). After the replacement everything worked perfectly for like two hours when i rebooted it, from then on it is extremely laggy and stutters from boot animation, and when I press the power button (or when the screen shuts down), the phone itself shut down. In bootloader it doesn't seem to have problems.
I checked every connection inside the device (I've disassembled ad reassembled it several times).. thinking of a software problem, I've flashed marshmallow stock rom frist, and kitkat 4.4.4 then... but it's the same with any factory image.
Maybe I damaged something on the mainboard?
I also made a video to explain the problem:
with a lot of patience I set up a google account and downloaded cpu-z to see if maybe temperature sensor where giving wrong information to the system, but they're fine and everything seems to work propely aside from the stutter.
thanks to anyone who will help me, I'm almost giving up
Click to expand...
Click to collapse
It's probably touch lag from the new screen, u probably got a bad one, contact who sold it to u, get a new one
Sent from my Nexus 6 using Tapatalk
soupysoup said:
It's probably touch lag from the new screen, u probably got a bad one, contact who sold it to u, get a new one
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I thought of that, but the fact that the haptic feedback (like the one you have entering app drawer, or returning home) is perfectly sync without lags made me think the touch was ok... and even twrp recovery was working smoothly (coudn't show in the video since I factory flashed kitkat)
RedMaio said:
I thought of that, but the fact that the haptic feedback (like the one you have entering app drawer, or returning home) is perfectly sync without lags made me think the touch was ok... and even twrp recovery was working smoothly (coudn't show in the video since I factory flashed kitkat)
Click to expand...
Click to collapse
What about stock Marshmallow?
Sent from my Nexus 6 using Tapatalk
soupysoup said:
What about stock Marshmallow?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
with 6.0 shuts down after boot animation (and reproduces it stuttered like the kitkat one in the video).
Right after the screen replacement, stock marshmallow was working fine for a while
That's very strange indeed, OK so try this, go into developer setting and check disable HW overlays, and check force GPU rendering, this will make the phone use the GPU for UI stuff, possibly fixing ur studdar, let me kno
Sent from my Nexus 6 using Tapatalk
soupysoup said:
That's very strange indeed, OK so try this, go into developer setting and check disable HW overlays, and check force GPU rendering, this will make the phone use the GPU for UI stuff, possibly fixing ur studdar, let me kno
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, I've just tried... can't tell any differences.
I was thinking that the main way to solve this could be to investigate on the fact that turning off the display (both with power button or by itself after 30sec), shuts down the entire device. Could this be an hardware failure? (maybe generated by a physical damage that I caused)
thank you BTW
RedMaio said:
OK, I've just tried... can't tell any differences.
I was thinking that the main way to solve this could be to investigate on the fact that turning off the display (both with power button or by itself after 30sec), shuts down the entire device. Could this be an hardware failure? (maybe generated by a physical damage that I caused)
thank you BTW
Click to expand...
Click to collapse
That's very weird, what did u replace, and how did u do the replace, did u do the frame as well, and when u took the batt out did it come out easy it did u fight with it, I've heard cases of this happening, and other issues caused by damaging the battery during a fix
PS, no problem man, I know exactly how u feel lol
Sent from my Nexus 6 using Tapatalk
soupysoup said:
That's very weird, what did u replace, and how did u do the replace, did u do the frame as well, and when u took the batt out did it come out easy it did u fight with it, I've heard cases of this happening, and other issues caused by damaging the battery during a fix
PS, no problem man, I know exactly how u feel lol
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I bought a pre-assembled frame-display-touch. The battery came out easily even if I slightly forced it in the bottom. Anyway before replacement the battery was completely discharged... it has been completely discharged for almost two months since I broke the lcd in September. Left the phone disassembled on the desk for two days. After reassemble I plugged in a 2A Samsung charger to fill it up... initially everything was working properly, made a few photos with both cameras to check, a call and some random checks.. still on charge. On the second call I made, the microphone stopped working, so was the third... turned off the device, back on and everything was messed up like it is now.
Well a battery failure could actually make sense...
Inviato dal mio SM-T805 utilizzando Tapatalk
hey i have exactly the same problem with my nexus 5, i haven't opened it neither changed battery or screen but i'm suffering the same issue since a few days ago. have you managed to find a fix?. in my case it just started to do that suddenly. as in the video is totally unusable, i reinstalled latest stock firmware throught the recovery menu but with no luck, everything is ultra slow now
RedMaio said:
I bought a pre-assembled frame-display-touch. The battery came out easily even if I slightly forced it in the bottom. Anyway before replacement the battery was completely discharged... it has been completely discharged for almost two months since I broke the lcd in September. Left the phone disassembled on the desk for two days. After reassemble I plugged in a 2A Samsung charger to fill it up... initially everything was working properly, made a few photos with both cameras to check, a call and some random checks.. still on charge. On the second call I made, the microphone stopped working, so was the third... turned off the device, back on and everything was messed up like it is now.
Well a battery failure could actually make sense...
Inviato dal mio SM-T805 utilizzando Tapatalk
Click to expand...
Click to collapse
pyroxine said:
hey i have exactly the same problem with my nexus 5, i haven't opened it neither changed battery or screen but i'm suffering the same issue since a few days ago. have you managed to find a fix?. in my case it just started to do that suddenly. as in the video is totally unusable, i reinstalled latest stock firmware throught the recovery menu but with no luck, everything is ultra slow now
Click to expand...
Click to collapse
I didn't fix it eventually... but from my experience in fixing PCs, I believe that it could actually be a power issue related to either the battery or some power circuit.
If you've nothing to lose and some dollars to spend, you could try a new battery and see if it works!