I recently changed the battery in my LG G2 d800. Followed specific guidelines, made sure all connections were replaced properly etc. Upon using the phone with the new battery I realize that everytime I attempt to take a picture using the phone's flash, the light flashes and the phone shuts off in a way that resembles the battery being disconnected. It's basically same sometimes when I try making calls, the phone I would hear a ring once, then the phone shuts off. I tried flashing some other ROM to see if it was a software issue but the problem still persists. Is there anyone with any knowledge on how to solve this problem?
Related
I have a weird problem where my cruise is randomly turning off?
When I go to turn it back on, it says that got at least 90% battery.
Anyone else have this? Any known causes/fixes?
Your not the only one. I too have the same problem running WM6.1 HTC's Image. Not real sure what is causing it, but it really is random. I don't believe its a battery problem.
Sometimes I do think it may be a contact issue with the SIM Card.
Have the same. Sometimes it shows low battery alert after turning on. And sometimes it's even hard to turn it on. The same was on WM 6.0., now on 6.1. Replacing the motherboard did't help neither
Same for me after HTC 6.1 ROM upgrade
and to compound the problem, the stupid thing lost my diary and contacts lists this morning. Really regret upgrading, and now looking for anon-WM device.
I had the same problem, I resolve hard reseting the device and reinstalling all the app.
Change the battery
After unlocking my phone with ChevronWP7 and now my screen goes black during a call and is unusable. The connection is fine, but its like my proximity sensor is doing its job even when the phone is away from my face. I checked and there is nothing physically blocking my sensor. I have to wait for the other person to hang up, then my phone shows the lock screen. I did a reboot but this didn't fix the problem. I don't know if this is device specific but I'm running an HTC HD7 without the software update. Here's everything I did after the unlock:
Prevent my phone from relocking:
http://forum.xda-developers.com/showthread.php?t=913748
Change my theme color:
http://forum.xda-developers.com/showthread.php?t=929017
And lastly installed a couple custom ringtones.
Unfortunately, I can't say after what step this started happening as I didn't get a call until I was all done.
Anyways, If anyone as had this same issue or a possible way to fix it without a hard reset, I'd sure appreciate some help.
Thanks,
JT
the problem is in your sensor.....it's hardware related problem and have nothing to do with software, use your warranty to fix it
Hello!
My oneplus one is having this issue for a while now, When I plug it in and lock the device, there is a 60~70% chance that the display stays on but its just blank, I have to unlock it and lock it again to fix it.
Recently this also started happening when it was not charging and the screen would often stay on causing massive battery drain :/
This happens on every single rom all the way from CM11S up to CM13 and also oxygen os,...
Does anyone know what the problem is?
Thanks,
Noahvt
I have the same problem since I can remember, also looking for an answer.
I have a similar issue. Sometimes the screen stays on, but is dimmed. A simple double press of the power button resolves it (turn on full, turn off screen) but its mildly irritating. I have only noticed it since being on sultanxdas cm12 ROM. I had an issue with a notification LED app not working since a recent ROM update so uninstalled it. Maybe the issue was related to that app as I cant remember the issue occurring since I uninstalled it a few days ago.
Hi there,
I'm experiencing massive issues with the Nexus 5 of my wife. Everything is basically broken
It started 2 days ago, the phone start rebooting without reason and heating a lot. Applications sometimes hang for a long time, or the screen stays black with only the notification bar displayed.
Wifi is never able to connect, even though the welcome screen is able to display available wifi. On the welcome screen after a fresh flash, nothing happen when I enter the WIFI password and try to connect. Only the "ignore" button is available, as if I have done nothing.
LTE connectivity seems to work, but I have removed the SIM card for further testing, so it's hard to say.
Parameters screen sometimes works, sometimes won't. Battery consumption screen never works.
The phone is never able to shutdown properly, it hangs forever on the shutdown loading circle; I always have to hard-reboot.
I changed the battery (I had a spare one ordered few days before the problem occurs just to see if it improves the battery life), with no luck.
When I opened the phone to change the battery, it is clear the heat come from the CPU.
I tried (I wiped everything each time in between):
- factory reset
- flash a stock rom from Google website (MMB29K)
- flash latest Cyanogenmod rom (ZNH0EAO2NM)
I have the same issues with any of those 3 roms. I captured some logs while running MMB29K and ZNH0EAO2NM:
Stock (MMB29K) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3M28tM2xjTmJKa28
Cyanogenmod (ZNH0EAO2NM) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3TVUtTmExZDBLUms
The only state where the phone is stable is when TWRP is booted, which is not so useful...
I'm thinking of a hardware issue, but is there anything else I can try? What do you think?
Thanks a lot!
Nobody?
I said the same thing in another post. The fact that flashing different ROMs with the same issues kinda point to hardware problem. I'd guess something fried on the motherboard and it's causing weird behavior. Funny thing, the other post also reported wifi not connecting issues, so I'm thinking there is something that breaks in older Nexus 5 phones that cause wifi issues along with other random reboot problems.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.