Related
I have the LG V20 (vs995, Verizon). My flashlight stopped working. As did the flash for my camera. So I was like ok, I'll reboot. And I did.
After the reboot, the camera flash worked for the first photo. Then it doesn't turn on until I reboot again. And it won't turn on when I use the flashlight. It's the same result with 3rd party flashlight and camera apps too.
Has anyone else had this issue and more importantly if you have, how did you solve it?
Also, I have not updated the system software ever...
Sent from my VS995 using XDA-Developers mobile app
Yup, same issue here. After the 13a system update (January 2017), the flashlight/flash stopped working. If I restart the V20, the flashlight will work -- precisely once. After the first use, it stops working again. Since the flashlight app (the LG V20 onboard app) works ONCE with a restart, this strikes me as most likely a 'droid software bug related to the V20. Anyone over at LG paying attention to this annoying bug?
V20guy said:
Yup, same issue here. After the 13a system update (January 2017), the flashlight/flash stopped working. If I restart the V20, the flashlight will work -- precisely once. After the first use, it stops working again. Since the flashlight app (the LG V20 onboard app) works ONCE with a restart, this strikes me as most likely a 'droid software bug related to the V20. Anyone over at LG paying attention to this annoying bug?
Click to expand...
Click to collapse
Try this:
In settings/apps select the camera. Force stop it. Then select storage. Clear data. This should clear cache also.
Shut the phone down. Pull battery. Put battery back in and reboot.
This has worked on other phones.
androiddiego said:
Try this:
In settings/apps select the camera. Force stop it. Then select storage. Clear data. This should clear cache also.
Shut the phone down. Pull battery. Put battery back in and reboot.
This has worked on other phones.
Click to expand...
Click to collapse
Thanks, but no joy. Forced stop to Camera; cleared data/cache. Powered LGV20 off, pulled battery. Reinserted battery, restarted. SAME RESULT. Flashlight worked ONCE. Then stopped working.
FYI, the bloom is really off what I thought would be a great phone. The speakers on the first one (from Verizon) blew up completely after the attempted and failed install of the 'droid 13a "security" update. I had the phone for not more than 90 days. Opted to replace it with a certified reconditioned LG V20 under warranty replacement. Now the flash and flashlight have failed due to 'droid update bugs after maybe 2 weeks. Nothing (!!) should be this complicated. Now what? Replacement phone #2?
V20guy said:
Thanks, but no joy. Forced stop to Camera; cleared data/cache. Powered LGV20 off, pulled battery. Reinserted battery, restarted. SAME RESULT. Flashlight worked ONCE. Then stopped working.
FYI, the bloom is really off what I thought would be a great phone. The speakers on the first one (from Verizon) blew up completely after the attempted and failed install of the 'droid 13a "security" update. I had the phone for not more than 90 days. Opted to replace it with a certified reconditioned LG V20 under warranty replacement. Now the flash and flashlight have failed due to 'droid update bugs after maybe 2 weeks. Nothing (!!) should be this complicated. Now what? Replacement phone #2?
Click to expand...
Click to collapse
Sounds like a Verizon issue possibly. I'm on TMO and haven't heard of anyone having this problem. And the OP is on Verizon also.
Verizon is known to screw up updates when they add their own stuff and it breaks other stuff . I remember when the HTC thunderbolt got an update and people who took it would get random reboots I believe. Call Verizon and ask for one of their tech people and talk with them about the issue. Then hopefully they can get Verizon programmers to come out with a patch. I would just wait as getting another phone won't fix the issue.
Sent from my LG-H910 using Tapatalk
same my phone is LG V20 (H910) AT&T
my phone is LG V20 (H910) AT&T .After the reboot, the camera flash worked for the first photo. Then it doesn't turn on.the flashlight/flash stopped working. until I reboot again. Very crazy. until today still like this. also I restart fastoary .but same same flash only working one time .who can help me how to do. thanks.
Gravemoss42 said:
I have the LG V20 (vs995, Verizon). My flashlight stopped working. As did the flash for my camera. So I was like ok, I'll reboot. And I did.
After the reboot, the camera flash worked for the first photo. Then it doesn't turn on until I reboot again. And it won't turn on when I use the flashlight. It's the same result with 3rd party flashlight and camera apps too.
Has anyone else had this issue and more importantly if you have, how did you solve it?
Also, I have not updated the system software ever...
Click to expand...
Click to collapse
I'm having same issue ... But my flashlight does work
...just tapped out with a thumb or 2, please don't mind the abbreviations and grammatical faults.
Guys, I had the same issue on a US996, but I returned it and got an H990DS, it's easier. But you could also try flashing a new KDZ.
Resolved... Go to settings, application manager, camera, press turn off, then click storage, clear all storage. This should fix it.
...just tapped out with a thumb or 2, please don't mind the abbreviations and grammatical faults.
filmerz said:
Resolved... Go to settings, application manager, camera, press turn off, then click storage, clear all storage. This should fix it.
...just tapped out with a thumb or 2, please don't mind the abbreviations and grammatical faults.
Click to expand...
Click to collapse
I have the same v20 variant and problem but your solution didnt work theres no problem when using third camera apps though, and i realize the flash doesnt work when i use the narrow lens only
Hello. I got exact same issue with my LG V20 VS995. The flashlight only works once after restart, no matter if you using camera or just flashlight. I've tried with factory reset, camera data clean up, even firmware downgrade but the problem is still there. Did you find any solution?
LG V20 Flashlifght after oreo not working
After I read all comment and i have tried everything....
No solution yet...
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.
So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd
Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.
ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.
Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.
Had my PH-1 for 3 months, today was the first freeze up of the phone, was stuck with home screen on and displayed.
Had to reboot by holding small button and Volume down. When phone rebooted it came up with the Android laying on its back with the open stomach hatch, had to reboot a 2nd time. Then had options like from Safe Mode, pushed small button below Volume to perform a regular restart.
Found my battery was running down quickly from a full overnight recharge. Looked at the Battery settings and it showed the camera was on top at 29% after about 5 hours WTH?? I did use the camera and this is what I was trying to use when the phone was frozen, but once the phone was rebooted, I snapped like 5 pictures and then I was pretty sure I closed the camera App. I tend to always try to close/kill all open Apps that I am not using.
So not sure what happened or why, just wanted to put this out there so others can read and may respond if this is a common problem due to some update or incompatibility.
Seems there may be a conflict with the latest Camera software and phone OS??
I had my phone freeze again today when I went to take a picture. This is an intermittent issue because I took quite a few pictures this morning without a problem. Then later this afternoon I took a single picture then wanted to take a 2nd and realized the phone was frozen.
Had to reboot the phone, seems to have cleared up for now?
I just noticed that the camera App just updated 6 hours ago on my phone. This was AFTER the 2nd freeze during camera usage.
Currently my phone is running Android stock 7.1.1 and the updated camera App is 0.1.095.007.
It is possible the latest camera App update has solved the freezing problem?
Will wait and update this thread in about a week about how things are working.
Just wanted to update this thread on phone freeze.
Seems that the problem may have been with a prior camera update. I had the phone freeze 2 times, shortly after the 2nd freeze the camera App was updated and since Camera App 0.1.095.007 was deployed I have not had any more problems with the phone freezing.
So hopefully I can say the Essential group was aware of the problem and release a very quick solution.
Still loving the Essentinal phone, would like more camera features, but I guess this will come with time.
Best part is I only charge phone every 2 days the way I use it. Have run Waze for over 3 1/2 hours multiple times with fresh charge and no external power and battery is still slightly over 50%.
So a new camera update version 0.1.097.006 was released and my phone was updated late yesterday or last night.
No problems since the last camera update that came out a few days after the update that caused the phone to lock up. Seems we are back to the same routine.
Used my phone to take a few pictures this afternoon, and guess what, phone locked up again after I took a few pictures and make an outing phone call right after taking the pictures. Put phone back on power after taking the pictures and making the call, I guess the camera App was still open in the background. Looked down and my phone display was on the camera App. Tried to close the App, no go. Unplugged the phone from power and the yellow power LED was still lit and the phone was non responsive.
Held down the power and volume down button to restart the phone.
Expect and hope an update the camera App is released soon to solve this issue. I have faith that the Essential team will resolve this quickly.
I have a Motorola Moto E4 XT1768.
Last year I rooted it and installed TWRP. I haven't been able to install OTA updates since.
More recently I replaced the screen with a 3rd party replacement. It seemed to work okay at first, but now there have been unresponsive areas on the screen. However, in TWRP this issue seems to vanish, making me guess it's somehow a software problem. Also of note, I accidentally destroyed the fingerprint reader in the process.
I tried to do a basic factory recovery. It didn't fix the screen problems and it introduced an issue where many apps crash immediately on startup. Clearing data and cache hasn't helped those apps. Last night I used the RSD Lite Mac Linux script to attempt to flash back to unrooted stock. (Supposedly works the same as RSD Lite on Windows). I used flashfile from XT1768_PERRY_RETAIL_7.1.1_NPQS26.69-64-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet. I got a lot of "bad key" errors but it also seemed to take, only now I'm also getting a black screen that says "bad key" at times, and the startup error screen (lettng it sit for a minute takes it into the OS though.) The screen issue and app crash issues are unchanged.
I'm lost on what to do here, and also don't know if the screen issue being tied to the OS even makes any sense. Is getting it back to basic functionality a lost cause? I realize it's a cheap phone but it was fine for my needs and I don't like buying new phones all the time, for both eco/waste and budget reasons.