Hello everyone, I just recently got a G3 and it was working fine for the 1st 2 days, no issues. I was sending a text to a friend earlier today and after it sent, it completely froze. After doing a soft reset it took forever to boot up. Once it booted up, it seemed to be fine. about an hour of operation, the screen looked as if it was freezing because it wasn't recognizing any of my touches. i decide to flip the phone sideways to see if it was actually frozen but it changed to landscape just fine. Sometimes it comes back to life then goes off again shortly after, and other times, i have to soft reset. I've tried the following to no avail.
Took the phone apart and cleaned both connectors.
Re-flashing the rom.
Trying 4 other roms.
Returned to lollipop stock.
I can't figure this out for the life to me and worked my ass of to be able to buy this phone. Any help would be appreciated as I can't afford to spend any more money on it!
I also have this issue, it's been ongoing for a few weeks. There will be short periods where it can work just fine, then it just freezes up and does not register any inputs. The content on the screen continues to run as if nothing happened (videos and games keep playing). Turning the screen off, waiting a couple minutes, then turning it on can sometimes give me another minute of use until it freezes up again. Also of note, when the screen is unresponsive and I press the power, it will dim to very low levels for a few seconds before going fully black. When the screen is being responsive and I press the power, it goes straight to black, as is normal and expected. From my testing, I've concluded:
1. This issue is not app dependent. It can occur at any time, and is not caused by alarms or overlays, such as blue light filters.
2. The issue is not from the specific battery I use. I've switched out between multiple batteries and used different chargers, none seem to affect the frequency of freezes.
3. Temperature may have something to do with this. When waking the phone after it's been sitting out in the cold, there seems to be a higher likelihood that it will be unresponsive. This is not always the case, which makes concluding that the issue is hardware related difficult, but some correlation seems to exist.
4. This issue started occurring shortly before I began having the popular "SIM Card Removed" issue, which I've yet to resolve (though can sometimes get the SIM card to work)
I am running stock 6.0 D85030p AT&T. I will post here again if I figure something out, but I have been trying for weeks without much success.
Related
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
I did not have that problem for a long time, it only recently happened. In the morning the device 'froze' for the first time and did not react to any input without the screen turning on.
I took out the battery to restart and everything seemed fine. But later on it happened while I was using the device, certain pixels moved out of place (like a green pixel distortion) and the device froze. Screen turned off soon after. Taking out the battery was the only option.
Now, this is either battery or some other hardware flaw. After restart the battery had been hit with a 20% drop.
Might the device act up by some charging problems? When I am charging the device, I can feel the electric 'buzz' from the docking connectors (the three golden circles).
Also, when it is not charging, I cannot detect it myself, but if I take a strand of hair, the end of it 'sticks' lightly to the screen (and to the docking connector) if I put it close there. I fear like there's some manufacturing flaw there that broke loose.
The device has not dropped once, nor has had any other physical damage happen to it.
Has anyone else had the same symptoms happen?
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
I found this issue (or one very much like it) at code.google.com here:
http://code.google.com/p/android/issues/detail?id=22748
jss42 said:
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
Click to expand...
Click to collapse
Thank you. I thought it was different from Sleep of Death since the initial symptoms were different from weeks ago when I read that thread, but now reading it this seems correct. This thread can be merged or removed, I'll post in the other thread. Thanks again!
I've had that too, couple days ago using Facebook everything just froze. The keyboard went all buggy and green pixels everywhere. The back of the phone started to warm up phone wouldn't respond in any way.
Tried everything I could try, only option was to pull the battery, once that happened phone wouldn't turn back on!
I gave the phone 5 mins to rest before putting battery back in then it turned on.
My heart was pounding I thought my phone had died!
Thankfully it hasn't happened since
Sent from my Galaxy Nexus using xda premium
It's happened to me multiple times. Less since I turned off the EQ in the Music app, but it's still happening.
Once it happened with the device just sitting there with Tapatalk displaying a list of posts. I wasn't even interacting with it.
I think it's a OS or driver problem and will be fixed in an OTA.
happened to me once, although when it happened I was already pretty low on battery, about 20% left, maybe less.
I was in a settings menu for some app, I can't remember which. But I had the keyboard up, and the green pixels hit, froze, unfroze, green pixels again, froze, and then shut off.
it would not turn on via the power button, so I quickly pulled the batt and put it back after 30 secs or so and powered it up. Batt did not drop any lower than it was, and it worked fine. Plugged it in, recharged overnight, and has been fine ever since.
I'm running 4.0.1 and I don't have anything but apps made by Google on the phone at the moment.
never rooted or unlocked bootloader.
Hopefully 4.0.2 or 4.0.3 fixes this
i realize now that there's no support for 720P AC3 .MKV files on the Nexus yet, but every time i tried the phone would lock up and i'd have to do a battery pull. other then that, i notice if i have Google Music running and attempt to do something else(multi-task) the phone will also lock up.. but then it will reboot on it's own. i also get lag regularly switching views/menus or going from portait/landscape. additionally, the browser(regardless of which one i use) will occasionally just freeze & close by itself.. usually if i try to do a secure login on a site. i will also sometimes get FC's(have seen them for launcher pro & android keyboard)
I just recently got a T217S from Sprint, had it about 2 weeks, running all stock, 4.42 Android. Ran fine the first week, then I noticed that the screen would start to flicker. Doesn't change colors, just flickers. Playing with the brightness can sometimes cause it to stop temporarily, but it starts again almost immediately. The level of brightness doesn't make a difference, neither does any applications I'm running. I've rebooted it into safe mode and without even touching it, it started flickering less than 30 seconds after booting. I've google the heck out of this and it doesn't seem to be a hardware issue, but an Android problem. I would like to avoid a factor reset if I can, especially until I get solid proof that it would FIX the problem. So far, no one can even tell me WHY it's doing it.
HELP???
Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!
Same situation. This thing is a lemon!
Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk
One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.
My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.
Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.
Weird thing happened to my lg suddenly
1) Touchscreen totaly unresposnive
2) Pressing power button brings up the power options with a huge delay (about 5 seconds), cant choose any of the power options because touchscreen doesn't respond to touch.
3) Hard restarting the phone with battery out, reboot takes forever (around 7 minutes) end up on the login screen with error codes "service is disabled" and "process system isn't responding", cant choose to terminate the option because touchscreen still is not responsive.
4) Did a forced factory reset. The reset menu seemed fluid and the reset itself seemed fluid enough, but when i got the setup the phone screen (get started screen) i was hit again with the "process system isn't responding" error. Also the huge lag of the OS and power button delay came back. Touchscreen also didn't work
Tried to take out sim and sd card, same result.
Funny thing: screen flipping is totaly fluid and flips on the fly.
update: The touchscreen suddenly started responding, but after about 4 seconds it became unresponsive again. Seems to be a hardware related problem.
After some extensive search i finally found a forum where similar symptoms exist:Google: "screen_becomes_unresponsive_after_5_10_seconds_of"
Gonna open her up and try the foil trick when i have time.
I can't really say but my original G3, from 2014, started behaving similarly last August. Screen was fine but I believe the emmc was failing. I remember going through batteries while trying to get the phone to boot fully. It would get so far and then restart itself. Before it got that serious there were errors, unresponsiveness, and lag.
Did full wipes, reformats, flashed different ROMs, to no avail. With older ROMs (Lollipop f.i.) the phone would constantly power off during boot. Always had to pull and reinsert battery. With newer ROMs it was better in that I got reboots instead. After awhile the phone would shut off or reboot even in TWRP.
Eventually I administered last rites. It had a good run.
LG G3 D851, AOSP-CAF 6.0.1, NanoDroid, MultiROM, XDA Legacy
Yeah i guess so, i assume the problems mostly came because of the overheating issues over the years, just like gpu has, constant temp changes on demand. I wonder would a oven trick to the logic board do something useful?
I baked my old gtx 780 and it has been running like a champ for almost 5 months now (Y)
Anyway i noticed that if i put my G3 in the freezer for about 10mins, the phone is alot longer responsive then just mere 5 seconds. Maximum i got was about 3 minutes lol. Guess i gotta carry a mini freezer with me from now on...
Update: After doing a 10minute bake @ 185C to the motherboard, the phone has been working fine. Will let you know if this problem comes back. If not then the bake did the trick.