H901 Lockup/Freeze Diagnosis - LG V10 Q&A, Help & Troubleshooting

I have 2 year old H901 that freezes, reboots, and sometimes refuses to boot. I need some diagnosis assistance, especially audit tool recommendations. Nothing stands out in logcat, but I don't know what to look for.
Miscellaneous facts:
-H901 at 30c. Bootloader unlocked, TWRP installed, and rooted with Magisk.
-Motherboard replaced in April under extended warranty due to bootloop.
-Added arctic silver, fresh thermal pads, and upgraded/rooted after received.
-Noticed that, with headphones, left ear would have static. After sound stopped, the static would persist with clicking (~3 per second) for several seconds. Turning off HiFi DAC eliminated this problem. Replacing the headphone jack had no effect. (Faulty DAC chip? Related issue?)
Problem:
-About a week ago, my H901 started freezing freeze. Sometimes I pulled the battery. Sometimes it reboots on it's own.
-If it reboots on it's own, it freezes after booting on the lockscreen (notification bar says "Service Disabled"). Pulling the battery allows a normal boot...sometimes.
-After a few freezes, the phone would not boot even after battery pu;; (stuck on LG logo) unless I went into TWRP and cleared the cache and ART cache.
Suspicions:
-Could a bad battery cause this? Both of my extended battery have a very slight bulge, but seem to hold normal life for their age. May try only using OEM batteries.
-Could it be a problem with the sound hardware? If I remember correctly, I have always been using sound when this happened. One time, it was during a youtube video and, upon freezing, it blasted a loud solid tone until reboot.
-Could it be caused by software? I haven't installed anything new, but this did seem to start happening after receiving the update notification for 30d.
-Could this be a thermal issue? Temps are usually 30-40c, highest I've seen is 48c.

Run in safe mode for awhile when not in busy/working hour see if it still reboots, fingerprint won't work after reboot. I hate to point this out but if the problem persist after factory reset , it could be hardware issues

Related

Please help! HTC HD2 keeps rebooting (soft reseting) out of it own

I don't know what the heck is going on with my HTC HD2, but the reboots are getting quite annoying.
Furthermore i noticed it happens when i utilize the cpu heavily.
Mostly with streaming video or playing games.
Have done multiple hard resets, rom updates and even custom roms but nothing seems to work.
Sometimes my phone even reboots(soft resets) after watching 5 whole seconds of youtube
So even directly after a hard reset the problem persists.
I'm totally confused right now(because i have tried everything i could do to fix this problem).
I am thinking could it be the battery not giving enough juice for the task? overheating ? or just faulty hardware?
what do you guys think?
because i noticed that the problem is happening more frequently over time.
Edit: it rebooted even in idle a moment ago (1th time) ???
Similar issue with youtube freeze and reset
I can validate your frustration. I am having problems with my HD2 freezing up as well and doing a soft reset on it's own. So the YouTube app opens up the HTC player and then it will play a few seconds and then freeze up. I also opened an MP4 movie file and view it with the HTC player and that also froze it. Last but not least, I have TomTom and that froze it after 15 minutes last night.
I have seen some postings that Tmobile and HTC will be releasing a new rom to fix some memory leaking issues so perhaps that might be it.
It started happening about a week ago for me. Please post any solutions you might find.
I am on:
OS v.5.2.21889
Mania v.2.5.20121412.1
ROM v.2.10.531.1 WWE
Radio v. 2.08.50.08.2
I have done some trail and error, played around with coreplayer and i noticed that when i set the video quality to FLV medium quality in the buildin youtube app in coreplayer i won't reboot that quick anymore, but after a couple of seconds it will eventually still reboot. If i set quality to high quality/high bandwidth i will reboot much faster (so this let's me think about some kind of memory leak/buffer overflow).
Furthermore luckly i don't have any problems with playing mp4 videos in coreplayer, i have tested this especially because of the youtube reboots, and it will keep playing for 1,5 hour without any problems, so maybe you could try coreplayer and see if that's a solution for your mp4 problem ?
But eventually it would be nice if these problems where sorted out so that the device will work like it is supossed to be
Already tried a TASK29 and a flashing a stock ROM from your SD card?
Ye, have tried task 29 (between each roms, i do use task to make sure that the phone is empty.) and when i went back to my 1.72 stock rom i did flash it from SD, but still no luck.
this happened to me today as i was logging onto the net. it did a full master reset.
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
dfhgjkhgfeghjn
lemonspeakers said:
dfhgjkhgfeghjn
Click to expand...
Click to collapse
lol ? xD frustrated ?
thompsd said:
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
Click to expand...
Click to collapse
hmm i only got the problem while i'm watching streaming video through 3g and on usb > active sync > pc data connection / some (cpu intensive) games
with wifi no problems at all, it plays youtube for more then a hour without a reboot, and i tested it multiple times to make sure), and booting is just fine without a single hickup
thompsd said:
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
Click to expand...
Click to collapse
Hey, thank you @thompsd. This was driving me crazy on my phone. I finally took it back to a TMobile store for replacement and they put me on the phone with support before they would issue a replacement. Of course I was bewildered when they had me take out the battery and put it back in (which I had done a zillion times) and the phone suddenly worked. The person on the phone told me that it was fixed because I had to keep the battery out for at least 90 seconds. This made absolutely no sense, but it was hard to argue with success. I walked out of the store with my head hung low in shame.
Tonight, sitting in an airport lounge waiting for a flight, I noticed that my phone was hung so I pulled the battery to reset it. When I put the battery back in and started it, the phone went into the reboot loop -- displaying the boot screen for a couple of seconds and then shutting down and rebooting. I pulled the battery for 90 seconds. 120 seconds, 5 minutes. No joy. Realizing that this solution made absolutely no sense in the first place, I decided to search around again.
I found your reply in this thread and looked at my battery contacts. One of them was bent. I straightened it out, put the battery back in and the phone booted right up. Now I realize that when I was on the phone with TMobile, I must have put the battery back in that one time in such a way that inadvertently straightened the pin.
Hi all,
I have (maybe) the same problem with my HD2 i.e. when it is "doing something", well not idle, it sometimes restarts itself and then usually will not get out of the cycle of crash/reboot untill I remove the battery and wait for a few minutes before starting it again.
This is always more frequent if I am using a serious application such as sat nav. It also has only happened when the unit is connected to power, either on my desk or in the car (different power sources), but disconnecting it from the power after the cycle has started doesn't help.
I have assumed from the symptoms that it is caused by overheating and so leaving it switched off for a period allows it to cool.
I have got a return packet from Vodafone to send it for repair but I am loath to do this as it is likely to take 10 days and I suspect I might either get a recon unit back or "no fault found".
Does anyone think this could be battery related? If so I would buy a 2nd battery and test it.
Cheers, Gordon
I can confirm having the same problem.
Using BattClock (which shows a.o. the battery temperature) I was able to establish that the resets and reset loops happen once the battery temperature exceeds 31-32°C.
Contacted HTC support and received reply that the phone qualifies for repair.
PS. My wife just suggested providing me with a cooler bag, so I can enjoy reset-free phone during summer heatwave...
I had similar behavior, but it was due to the new ROM release (4/28/10). I loaded the official T-Mobile release date ROM (2/19/10) and the problem went away.
L.B.
Yesterday my battery charge got very low and shut the phone down. When I turned the phone back on without charging it kept rebooting time after time. I tried plugging the charger in but that didn't help. I took out the battery and put it back in and that still didn't help. I finally caught it when it was rebooting and pressed volume down and got the phone in bootloader to at least stop the constant rebooting. I left the phone on the charger and after about 1/2 hour I pulled the battery and put it back in and the phone was fine.
I am not wanting this to happen again. Maybe I will go back to an older ROM.
if i have some luck i will receive my phone tomorrow or the day after tomorrow.
i will let you know what has been repaired and if this solved the reboot problem.
today i received my phone back from the repair center.
The repair letter says that the display has being changed because it was not functioning anymore? (but when i sent the phone in the display was working like it should).
And the youtube problem is still there
Im having the same problem! i figure it was the battery overheating...or the rom or even probably a not compatible radio.....try to change all of these and is still restarting when ever it tries to connect to any data or internet usage. Ex. youtube, downloading of files from the internet, Remote Desktop even Microsoft My Phone still restarts.
even when i used to make/receive phone calls it would restart as soon as i picked it up to talk. but for this i had a solution witch as of now is working fine with out a problem.
if anybody else has this problem with the Receiving/making calls this should work.
1. Go to: Start/Settings/Connections
2. is the "TASK" tab choose "Manage Existing Connections"
3. In the "Modem Tab" has for options to choose from, normally is on "Auto", this was the problem. you would want to get it OFF AUTO.
4. Try all the other " voice Stream options Shown" and see witch one works for you without giving problems, and save. Im currently using "wap.voicestream.com." witch is the second option after Auto.
Well i hope this works for you guys if ur having similar problems, its actually work for me. GooD luck! hope this helps.
bitbank said:
I had similar behavior, but it was due to the new ROM release (4/28/10). I loaded the official T-Mobile release date ROM (2/19/10) and the problem went away.
L.B.
Click to expand...
Click to collapse
is it possible for me to know where can i get this ROM??
(official T-Mobile release date ROM (2/19/10).
this week i will receive my phone back for the 2th time.
Hopefully they have found the faulty component of the phone.
I will keep you informed

[Q] GS3 sound stops working after a few minutes?

Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains

Stutter After Motherboard Replacement

Hey there,
Recently, my SGS2 Motherboard(+Battery Socket) got replaced by Samsung due to several issues (very quick battery drain when low battery and crappy home button behaviour etc.) Next day, I started to experience a strange issue, significant stutter, choppiness.
The stuttering begins mostly after enabling Mobile Data, or WiFi and when below 15% battery, but launching an app can also trigger it, even when WiFi and Mobile Data are disabled. Nothing but Lock&Unlock ends the stutter. But it sometimes starts again after a while. The stutter doesn't get triggered when the phone is charging, even with very low battery.
Tried Wipe Data/Factory Reset several times, used another Battery/Adapter, updated the version and then downgraded to a version I've been using before the replacement.(JB)
Didn't try rooting/installing any ROM so far since I might send the phone back although I have a jig.
Any help would be greatly appreciated.
Bump.
get back to Samsung and ask for a new phone.Obviously a motherboard replacement wasn't enough.

[Q] HTC One M7 Strange Behaviour...

So I bought my phone from AT&T just as the new M8 was coming out (got a good deal as a result) and ever since that day its been dependable, efficient, and never lagged a single second.
But then the HTC Sense 6 ROM started to act up, opengl issues, and various bugs that drove me insane! So I switched to CM11, (btw no IR or radio or hardware encoding support on it) and all went well until about 2 weeks ago.
Suddenly my phone is sluggish at times, especially on switching applications, and the battery life went from around 10 hours average usage, to 5... Now its down to 3... Not only that but the phone is HOT!
If I even watch a Twitch stream, or YT video, or play a game, or even navigation, camera, chrome, anything with it (including listening to music), the device gets to 43 degrees C. That is with the device out in the air, passively cooling.
If I leave it on a surface, with the back covered up (like in my pocket, or watching a video in my bed) it will go past 50 C, and climb further! At one point in my car while driving, (was charging and navigating, aux was connected so i could get audio navigation through my speakers) I suddenly realized I had past my exit 5 miles back, and had to stop to check the phone...
The phone was not responding to my wake button presses, nor holding it down, it was not outputting directions, and the red LED light was softly lit (not flashing) so immediately I unconnected the charger, and aux cable. The phone still didn't respond, holding power + vol up soft resetting it worked. But what struck me most was how blooming hot it was! It was NOT in direct sunlight, nor was the display on. It practically burned my hands! I had to look up how to soft reset the phone, using my old LG Nitro HD which is my GPS tracker for my car (nifty setup btw).
Now I had an LG Nitro HD which did this sort of thing 24/7 and I could not STAND that phone, since you had to baby the device every second to keep it cool, otherwise you would need to restart.
I have seen numerous threads online about the HTC One getting toasty, and it has before for me, but NEVER THIS HOT! Also this only JUST started happening (its not related to CM11 since I had a backup of HTC's ROM and it did the same thing (in fact it was even slower x.x)
Now here is my question : is this a normal occurrence for smartphones of this age? I think its 1-2 years old... Its past the warranty I suppose (still have the card, and box btw) Is this something that I just have to deal with?
I have used the phone alot while it was charging, and left it on a charger for a long time after it was fully charged... (i thought newer phones had a disconnect for charging)
What bothers me is how suddenly the phone has become stricken with this... problem. It has only been 2 weeks, and battery life is effectively halved, and I am afraid to even USE navigation anymore (unless I hold the phone up infront of an AC vent, which I did all the way home >.< not a fun task since its a manual!)
Thanks in advance!
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure to not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Edit: if you have insurance through at&t I would go back to complete stock (get rid of tampered flag and red warranty warning included) and let them know it's freezing up. They should send you a replacement and it may help you out...
OfficialLocdoGg said:
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure you not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Click to expand...
Click to collapse
Yeah actually I just factory resetted the phone, and its absolutely normal now... Furthermore the USB speed is no longer 1mb/s and instead is back up to USB3 speeds!
BTW I did a firmware AND software factory reflash / reset.

3.5 mm jack bugs?

Recently my LG V10 T-mobile model received its sweet marshmallow update. Unfortunately I have noticed that the headphone jack is now causing some bugs on my device. Doing a reboot on my device with a pair of headphones connected will freeze the phone on the LG boot screen. Unfortunately the only way I have found to resolve the issue is remove the battery and headphones and then it boots up just fine. Occasionally I have plugged in the headphones when the screen is off and then try to wake it and encounter another frozen device.
This has been just annoying enough to me that I did a factory reset thinking maybe the drivers may have been messed up in the upgrade process? Sadly the problem still persists. Has anyone else encountered this issue? I am a confident rooter/rom flasher but was enjoying the extra T-mobile benefits in the official build. Any suggestions guys?
This is a problem since about 2 weeks after updating to 6.0. Takes four to five restarts to unfreeze. I've uninstalled TuneIn app and DacFix but it doesn't seem to be a cause. I also cleared cache and data in multiple apps related to audio.
Resetting to factory settings was going to be my next step.
There is a thread on reddit around the same issue, but no solutions yet, just reports from others.
My V10 basically bricked itself a few days after the update. I believe I had my headphones plugged in as well. Neither recovery nor download mode worked properly. I managed to boot it in a freezer tho. Shipping it back today.

Categories

Resources