Database Info

[Q] Phone Suddenly hanged and now donesnt work properly

Hello Guys,
Tuesday night i kept my phone on charging, next morning the phone didnt repond on the wake button, tried several times no help, removed the battery and restarted the device but it took it around 30 minutes to boot up, but the touch screen didnt worked at all, i tried to format the phone via bootloader (after pulling the battery)on first try no result same issue..non working touch screen, after formatting again it started workign smoothy, but i am again facing the same issue today, phone wont start up, and same issue with non working touch scrren.... cant even pickup an calls.... Need you help on it.. I m on Stock rom 2.3.5 with Sense 3.0 overlay non rooted.. and help or i need to go to gallery to resolve the issue

Hi Zeus,
Firstly - Never, ever pull the battery!!!
There - over and done with. Pulling the battery runs a high risk of causing permanent damage to the eMMC chip. You should (I have never locked up my phone so badly that this doesn't work) hold down the Power, Vol+ and Vol- buttons until the phone shuts down on its own.
You say your phone is no-rooted? I guess that means that you have not run any kind of mod on it, obtained S-OFF or anything else and the phone is, basically, as you bought it? If so then I would recommend that you simply go via HTC or your service provider to obtain a replacement.
If you have not felt the need before now to unock/root your phone then now is not really the ideal time to start doing so if you have a warranty still.

zeus.lny said:
Hello Guys,
Tuesday night i kept my phone on charging, next morning the phone didnt repond on the wake button, tried several times no help, removed the battery and restarted the device but it took it around 30 minutes to boot up, but the touch screen didnt worked at all, i tried to format the phone via bootloader (after pulling the battery)on first try no result same issue..non working touch screen, after formatting again it started workign smoothy, but i am again facing the same issue today, phone wont start up, and same issue with non working touch scrren.... cant even pickup an calls.... Need you help on it.. I m on Stock rom 2.3.5 with Sense 3.0 overlay non rooted.. and help or i need to go to gallery to resolve the issue
Click to expand...
Click to collapse
If you are in Mumbai (as on ur profile) , You can visit the HTC Support Centre @ Borivali (Thakkar Mall, near Borivali Station) - http://www.htc.com/in/help/service-center/
Please Note : They will most probably repair the phone (I don't think they replace the phones here in India after the initial 15 days period in which u can claim the Dead on Arrival policy).

Thanks for all the Suggestions,
Have read all the issues regarding emmc chip being fried on Desire S, but being out of town for some day, didnt had any choice but to try, however i let the battery drain completely yest.. recharged the phone to full and then booted again.. and its working fine as of now (didnt worked earlier).. without any issues from last 5 hrs.. lets see how it holds, havent yet installed any of apps yet.. guess will wait for another day or two to see the software fails again to hold.
went borivali, but its not yet started (confirmed with customer care of HTC) still being completed..
but yes.. will visit the Dadar branch if any issue arrises afterwards

Glad to hear its working fine as of now.
Btw , regarding the Borivali Service Centre . . I have been there last month & it is well up & running !

Been there on Friday evening at around 6 but it was closed....then I inquired on customer care which told me its non functional as of now... Will check tomm....
The phones working f9 now...no issues in past 2 days...hope it holds
Sent from my HTC Desire S using XDA App

Guys, I have seen this kind of problem with one of my colleagues phone (Not Desire S but Wildfire S). The reason was (assumed) pretty weird though, it was because of some electrical problem. Whenever he would charge his phone at home - it would start having this kind of problem, but when he charged it at office or through his PC - the problem would vanish!
Although I am not sure if yours is the same case.... but then could be..
Another thing: I got my phone's mobo replace free of cost from HTC (Salora) when it was under warranty even though it was S-Off, Rooted - so I think HTC is a bit lenient in India

The issue it seems has vanished, no issues as of now..no hangups or freezes and yes....both the time the issue arised when the phone was in charging.
Sent from my HTC Desire S using XDA App

[Q] Touchscreen Issues

I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.

This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.

I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet

I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.

I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:

I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet

Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.

There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.

2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.

So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk

Don't know what else to do to repair my phone

Ever since installing Lollipop my phone hasn't been the same. I've used cyanogen, slimkat, etc and they all start to present problems within a week from installation.
And forget about lollipop 5 or 5.0.1 , it begins to crash from the first moment.
Is there a way to do a hard erase and manually install things? *when I install things android images, I use ADB and the flash-all command.

Revert back to kitkat for now until the bugs are fixed?

It does not work. All kit kat images start to "degenerate" after a week from installation. It's really strange.

Then it must have to do something with your configuration (maybe an app that goes rogue or something). Don't forget that factory images completely restore your device and that this state has been well tested for several weeks / months

Just experienced a similar problem.
My Nexus 5 32GB was clean flashed with various ROM's and every now and again the phone would just freeze, maybe for 2-3 seconds at a time and then all of a sudden catch up with itself and carry on working fine until the next freeze. Usually the freezes would occur when using Chrome but it did freeze using other apps I had.
Anyhow, on Sunday night I went to bed as usual and put the Nexus 5 on charge (it had about 27% left) - woke up Monday morning to a dead Nexus 5.
Battery still gets warm to touch when charging it but the phone is dead. No red light, nothing. No charging screen animation.
Google are sending me another Nexus 5 out - which will probably go bad too as I tried to remove the battery cover after reading about unplugging the battery to kick the phone back to life. No doubt Google will now say I have no warranty as I've attempted to remove the back cover (unsuccessfully as it looked like it was going to snap the tabs off) - however the phone now has marks around the cover where I tried to open it up.
Oh the fun!
My previous phone, the Nexus 5 16GB died a couple times with the red flashing LED problem, but I managed to get it working twice by unplugging the battery. My newer Nexus 5 32GB is only 3 months old and it is dead.
If my refurb Nexus 5 dies I am moving away from the Nexus line as my faith in this brand is depleting very quickly.
The only Nexus I've not had any problems with was the Nexus S. My Nexus 4 earpiece was very distorted and crackly, plus the screen always looked yellow.
Really bugs me to say it too - as the Nexus is a perfect solution to the pure experience enthusiast. But from my recent experience with a dead Nexus 5 for no reason my overall experience of the whole experience is an experience and half.

Sounds like it might be a hardware memory chip issue. Starts off good and slowly deteriorates into a bootloop.

lolcakes203 said:
Sounds like it might be a hardware memory chip issue. Starts off good and slowly deteriorates into a bootloop.
Click to expand...
Click to collapse
That would suck but yes I suspect my problem is hardware related.
Every thing worked great before lollipop though.

Try safe mode, also go stock whatever and a different kernel. I've been lucky with mine but noticing battery drain with lollipop.
Sent from my Nexus 5 using XDA Free mobile app

[Q] Random reboots after screen replacement of Nexus 5, twice

I need your help, please.
Last year I broke my Nexus 5 screen.
After replacing the LCD (original) I encountered random reboots every day.
I took it back to the store, they replaced the screen again and the random reboots disappeared.
About a year later, 2 weeks ago, I broke the screen again
Took it to a different store and paid again for the original LCD replacement.
**Surprisingly, random reboots are back!**
My phone randomly reboots itself maybe 3-4 times a day, sometimes it won't turn on until I press the power button for about 10 seconds, and then it starts "optimizing apps" for a few minutes.
I tried clearing the cache, reinstalling kernels, factory reset, wiped everything and reverted to a blank new ROM, problem persists.
I also tried tapping the device, playing with the power button etc... nothing, it doesn't seem to be related.
I went back to the store, but I couldn't even show the problem, as the reboots only happen randomally and there's no way to initiate it.
He didn't agree to replace the screen again, and advised me to buy a new battery (which I didn't)
The technician seems like a nice guy, I don't think he is trying to rip me off.
He is the store owner so replacing the screen will go straight from his pocket, and he's really convinced that the random reboots has anything to do with the screen replacement.
On the other hand, the alternative is me paying again for a screen replacement, which I really don't want to, as paying for two screen replacement is almost like buying a new phone :/
My questions are:
1. How is it possible that the same problem happened twice? Maybe there is something wrong with my phone that is not related to the screen?
2. Any ideas how can I reproduce the reboots manually? so at least I can make him believe that there is a problem.
3. What do you think I should do? I really need a working phone and not excited about paying again.
Thank you!

[Q] heat damaging phone?

I'm having several issues with my AT&T LG G3 (stock ROM) and I'm not sure if they're related or what the next steps should be for troubleshooting. Here's the timeline of issues:
Over the last couple of months my LG G3 and the battery has been getting really hot to the point the phone is unbearable in my pocket. I usually restart it and the temperature goes down (until it eventually goes back up hours later under normal usage). (NOTE: I got a notification only once during this time saying charging is disabled due to high phone temperature)
Suddenly today bluetooth and wifi won't turn on and they both give an error saying "connection not allowed" (cellular and gps works fine). I restart the phone, problem exists. Disabled battery saver mode/feature, problem exists. Booted into safe mode, problem exists.
Now when toggling the wifi and bluetooth button in settings the phone freezes temporarily, restarts and then freezes at the AT&T logo booting screen. Holding the power button for 10 seconds doesn't restart it/power it off - only pulling the battery out, waiting a couple of minutes and putting it back in does it power up (it does not power back on if I put the battery back in immediately). Then it gets to the LG logo booting screen (sometimes the AT&T logo screen), but restarts itself 2 or 3 times before finally booting into Android.
So, software problem (Android having issues talking to the bluetooth and wifi radio or corrupt system files)? Hardware problem where the excessive heat over the last couple months have caused damage to the bluetooth and/or wifi radio or some other components? Or maybe its the battery is damaged by the heat and now it gives bad voltage, amperage, etc. to the phone?
Any kind of help would be appreciated.
Thanks

sounds like a hardware issue to me. How long have you had the phone? Have you tried connecting your phone to a power outlet and seeing if the issue persists?

rquiett said:
sounds like a hardware issue to me. How long have you had the phone? Have you tried connecting your phone to a power outlet and seeing if the issue persists?
Click to expand...
Click to collapse
I just went into the AT&T device support center and they replaced it since it was still under their 1 year warranty. I can say for sure it's a hardware or software issue and not a damaged battery issue as the battery is in the new unit (actually "certified like new") and it's working fine (battery life is much better too). I wish I tried a factory reset to narrow it down further but I felt I was annoying the AT&T techs and just wanted to leave (they did me a favor of giving me a replacement phone on the spot, but I wanted to troubleshoot the old phone further being the persistent nerd that I am, LOL).
So if you have any of these issues, I recommend backing up your phone and factory reset it. If the issues persist then it's likely a hardware issue and needs to be replaced.
Hopefully that helps someone.

What really is the prob...
DiGiTY said:
I just went into the AT&T device support center and they replaced it since it was still under their 1 year warranty. I can say for sure it's a hardware or software issue and not a damaged battery issue as the battery is in the new unit (actually "certified like new") and it's working fine (battery life is much better too). I wish I tried a factory reset to narrow it down further but I felt I was annoying the AT&T techs and just wanted to leave (they did me a favor of giving me a replacement phone on the spot, but I wanted to troubleshoot the old phone further being the persistent nerd that I am, LOL).
So if you have any of these issues, I recommend backing up your phone and factory reset it. If the issues persist then it's likely a hardware issue and needs to be replaced.
Hopefully that helps someone.
Click to expand...
Click to collapse
They over clocked the CPU too much to make up for lost speed from all there bloat wear. Solution....only run there apps....or root. I tell ya,,arrg.....Mine was getting so hot it was uuncomfy on my ear. Way to go Driod, google and At&t

I received a supposedly "new" unlocked LG G3 D850 1 week ago. I wanted to ensure it worked before I loaded my stuff so I didn't put a SIM in for the first 5 days. It had a wifi problem in the first 10 minutes, but then wifi worked for several days while the phone just sat there and I checked weather and news occasionally. I needed to test with my SIM before the return period expired and I ran into a small problem there. That got resolved but neither wifi nor bluetooth have worked since then. "Connection Not Allowed". I see it's a VERY common problem for many LG phones. If this is a new phone, how can it be heat damaged already? I think it's defective hardware or a software bug. I haven't even loaded any new apps on the phone - it's completely AT&T stock. I will probably return it and pick a different brand.