Hi,
since a few weeks i've got a big problem, my phone freezes to the point where I have to hold the power button to restart it. this started happening when I was on Jellykat v6.7 but still persists after flashing stock rom.
Info:
Flashed latest bootloader
Problem persists on Jellykat and stock, with multiple and stock kernel.
Problem does not occur when running spotify in the background.
Right now I'm running stock rom (4.4.2 from sammy, flashed via odin) with stock kernel and latest bootloader.
When I restart it and check my battery stats I can see my wifi was still working when my phone did not respond, thus the device was on and I was recieving messages while the decive was not awake.
Weird thing is that it works properly when I let spotify play in the background, meaning it doesn't go into deep sleep (I think).:silly:
Right now my device works fine, but only because I have spotify playing the background 24/7 which isn't ideal in terms of battery life and such.
Any thoughts on it?
Thanks in advance!
Still no one? I guess i'll have to survive till I get the note 4 :silly:
Same here
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
silentkiller143 said:
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
Click to expand...
Click to collapse
It started on custom JellyKat ROM, weird thing is, yesterday it worked perfectly fine without spotify and today it's screwing me over again
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.
Hello there all!
I've been having this issue for a long time.
I've been using the SuperZen ROM, Custom Project T Kernel and official L Speed Mod. Sometimes I got stuck during the device's bootanimation (until this occurred really often). I tried going back to stock kernel and everything went okay, but didn't have the enough time to test some consecutive reboots/power-ons as I did flash my phone again. The issue occured ONCE without the custom kernel, but then reinstalled Prohect T and L Speed Mod.
I am now running Prism Barebone with Project T and L Speed Mod. The issue occurs very often I tried removing L Speed Mod via Emergency_Uninstaller (provided or L Speed official page)...but the issue's still there. I may try a new fresh install by only adding the custom kernel this time, but I did want to ask if anyone experiences this issue as well? I am not sure if it is a hardware issue. Everything was okay with the stock ROM (the actual stock). Please note that my phone was in service ONCE for a screen replacement. I hope that nothing bad happened during that time..
Thank you for any response!
A couple weekes ago i rooted my phone and flashed fulmics 6.9. Then 1 or 2 days later i flashed Lineage OS, but because i didnt have some of the stock apps from LG that i use (QuickMemo+ and LG camera app) i flashed fulmics rom again. I decided to root the phone and flash a custom rom because the phone started to get laggy and the battery life wasn't the best. But then i start experiencing a restart loop on the fulmics rom. I then tried to do a clean install of fulmics rom again, but because of the constant restart loop i only managed to successfully install it again while plugged on the charger. I googled for a solution and found out that it could be a battery issue. I then tried to flash Stock v30B rom but without success (because of the restart loop once again, and also the flash software kept saying that it lost connection with the phone). I then took my brothers battery (He has the same phone, LG G3 D855), and successfully flashed the stock rom (v30B), but when i put my battery again it started to restart again in loop. After some testing i found out that it only happened when the battery was about 20/40% and everytime it restared, the battery percentage wasnt correct (I got drops from ~ 40% to 5%), and if i removed the battery from the phone for a few minutes it would show incorrectly again but with more percentage (like 25% instead of 5%), i even tried to calibrate the battery but with no successfull results. I then bought a new battery (supposedly original) and from my tests the restart loop stopped, but now the battery drains on iddle like it drains while using (It went from 100% to about 70/60% until it "stabilizes"). I researched for a solution and found out that it could be background apps and installed greenify and it seems to have improved a bit but nothing significant, and enabled airplane mode after that and it improved even more, but once again, nothing significant (I still think it drains more than normal while on iddle). When i rooted and flashed the roms i was on stock v30N and never have rooted the phone before that, and tried to follow all steps correctly so i wouldnt damage anything. Currently im on stock v30N again. And i've had experience with root and rom flash before, and never had any problems. My phone is almost 2.5 years and never had any issues with it or the battery, and also im now using the same apps as before.
Is it possible that i damaged the phone somehow during the root and rom flash process? or im just unlucky with the batteries ?
Note: The tests i conducted with greenify and airplane mode only went for a couple hours (still testing right now), maybe it needs more time so i note any difference.
Sorry if i mispelled something wrong (Im Portuguese ).
Vimaraes said:
A couple weekes ago i rooted my phone and flashed fulmics 6.9. Then 1 or 2 days later i flashed Lineage OS, but because i didnt have some of the stock apps from LG that i use (QuickMemo+ and LG camera app) i flashed fulmics rom again. I decided to root the phone and flash a custom rom because the phone started to get laggy and the battery life wasn't the best. But then i start experiencing a restart loop on the fulmics rom. I then tried to do a clean install of fulmics rom again, but because of the constant restart loop i only managed to successfully install it again while plugged on the charger. I googled for a solution and found out that it could be a battery issue. I then tried to flash Stock v30B rom but without success (because of the restart loop once again, and also the flash software kept saying that it lost connection with the phone). I then took my brothers battery (He has the same phone, LG G3 D855), and successfully flashed the stock rom (v30B), but when i put my battery again it started to restart again in loop. After some testing i found out that it only happened when the battery was about 20/40% and everytime it restared, the battery percentage wasnt correct (I got drops from ~ 40% to 5%), and if i removed the battery from the phone for a few minutes it would show incorrectly again but with more percentage (like 25% instead of 5%), i even tried to calibrate the battery but with no successfull results. I then bought a new battery (supposedly original) and from my tests the restart loop stopped, but now the battery drains on iddle like it drains while using (It went from 100% to about 70/60% until it "stabilizes"). I researched for a solution and found out that it could be background apps and installed greenify and it seems to have improved a bit but nothing significant, and enabled airplane mode after that and it improved even more, but once again, nothing significant (I still think it drains more than normal while on iddle). When i rooted and flashed the roms i was on stock v30N and never have rooted the phone before that, and tried to follow all steps correctly so i wouldnt damage anything. Currently im on stock v30N again. And i've had experience with root and rom flash before, and never had any problems. My phone is almost 2.5 years and never had any issues with it or the battery, and also im now using the same apps as before.
Is it possible that i damaged the phone somehow during the root and rom flash process? or im just unlucky with the batteries ?
Note: The tests i conducted with greenify and airplane mode only went for a couple hours (still testing right now), maybe it needs more time so i note any difference.
Sorry if i mispelled something wrong (Im Portuguese ).
Click to expand...
Click to collapse
I have been testing the iddle battery life with greenify for a while now and it improved a bit, not nothing major. Any thoughts what it might be ?
Hi guys,
I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;
in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!
I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;
I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).
Nothing changed.. it appears 2-3 times per day.
Anyone of you got the same error? which could be a solution?
I had exactly the same problem, but flash rom via adb fixed that.
not experiencing any.. stock non rooted...
Kshysiek said:
I had exactly the same problem, but flash rom via adb fixed that.
Click to expand...
Click to collapse
Sounds interesting.. will try! Thx in advance
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated
Running ExperienceOS by Jamal btw, which is based on stock OB28
I have had this as well. Just keeps rebooting randomly.
Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.
I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.
Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
Sent from my ONEPLUS A3003 using Tapatalk
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
Sent from my ONEPLUS A3003 using Tapatalk
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
creezalird said:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
Click to expand...
Click to collapse
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
basvanasperdt said:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
Click to expand...
Click to collapse
Same here
Been in SuperSU for 3 days. No issues so far
Op3 ob28
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:
$ uptime
02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24
*I had not tried using super su instead.
What can we do to debug this issue? Seems like everybody is trying to guess in the dark...
---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------
If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.
Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...
Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...
Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
simpele said:
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Click to expand...
Click to collapse
strange1712 said:
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Click to expand...
Click to collapse
abhibnl said:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
Click to expand...
Click to collapse
Kshysiek said:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
Click to expand...
Click to collapse
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
candiesdoodle said:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
Click to expand...
Click to collapse
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.