Related
Hello guys,
I have some issues while using the latest 4.4.2 DN3 ROMs. Before installing DN3 4.2 I flashed MJ5 bootloader, and it was running for a couple of weeks fine, then the phone started to freeze and reboot several times a day. I thought DN3 v5+ would fix these freezes and reboots but it was no good. I was really disappointed, as I really liked the look and feel of DN3. Now I'm using Revolution HD 31, it's stable (more or less, a couple of freezes and reboots for two weeks) and fast, but I really liked the looks of the latest DN3...
So the question is - what can I do to avoid these freezes and reboots and will upgrading the bootloader to a newer one will help me?
I don't think bootloader has anything to do with it. I was on MJ5 with 4.3 creikelo and NEVER had a reboot or force close. DN3 just freezes after 1-3 days. I had the same experience. It started getting laggy, or better said, the CPU was doing something, hence the lag, and then it just restarted by itself. And I did clean install. It is enough to reat the DN3 topic and see how many people have problems with it - and most still consider it the best ROM... I just went away to another ROM, and will post results in a week hope it doesn't behave the same as DN3
Thanks for the reply!
What ROM did you install? Is it stable?
I had a problem with mj5, my phone froze on the boot and i had to reinstall the ROM.
I think mj5 is for 4.4.2 ROMs, is a older bootloader.
brainstormer911 said:
Thanks for the reply!
What ROM did you install? Is it stable?
Click to expand...
Click to collapse
I tried JellyKat 6.7, but seems I have same issue... at first it was getting high CPU usage after a day or two, then phone became so overloaded it reacted to nothing and I had to pull battery out. Then all of a sudden I started getting SOFT reboots (that means only from the point of boot animation, no samsung screen) and I installed Xposed module Samsung Crash Fix and will see if it helps... I dunno, I am begining to believe there's something wrong with all 4.4.2 ROMs Because I never ever had FC, crash or reboot with 4.3 Criskelo....
So, I've had the premium for almost 3 weeks now. On the second day it crashed whilst I was listening to music +browsing in chrome. Thr screen turned inky and then turned off. Since then I haven't had anything similar happen, but I have had 1 or 2 reboots. Are these signs something could be wrong with my phone? I have like a week to get a replacement. It's rev 2, other than this I have no complaints.
Try to remove cach in recovery mode, maybe that will fix your problem. If not let me know
This has been happening to me as well and actually results in boot loops. Since I have Liveboot, I can see the dmesg output. It says "Failed to start system services. Invalid abi: ABI" or something like that. I'm RomAur so maybe that has something to do with it?
It has happened to me 3 times this week. Also RomAur 1.1. It seems to happen when i am heavy multitasking, definitely related to chrome I think.
I'm completely stock... I use chrome as my main browser. The last time it happened it froze on wake whilst it was charging... The first time I was listening to music and doing something else which I can't recall. The phone has 3gb of ram so I don't really clear my recent apps as often as I did on my S4. It happens once a week on average for me. Cache wipe didn't do anything.
You could've easily gotten a faulty device. A but load of hardware issues can do that and I would advice you to do a factory reset, update to the latest F/W (flash it if not available in ur region), see if it happens again and if it does - get a replacement
Gd luck
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
TheImmutable said:
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
Click to expand...
Click to collapse
exactly like that on my z5 . when i flash the xposed uninstaller , it doesnt randomly reboot, but when i flash xposed , it does.i was thinking of flashing .200 ftf and then flashing xposed from the beggining (before i install any apps ) to see if it helps , but you said you did it??
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.
Since the last few updates, even on a fresh install with nothing installed. My LineageOS in Alioth has been using 7% to 11% /hr of battery on a fresh install with no extra apps added. Tried doing a clean install, reset to factory, even tried reseting battery stats. Sadly cant do anything about it and I'm not being able to go back to versions I knew worked OK (19.1-20220723 for example since i dont have an img to use and lineage page only have the latest).
Most battery, about 55% is consumed by Kernel. Has anyone had the same issue?
Not sure what else to do and really don't want to go back to MIUI.
I got similar issues a few Updates back, it was related to some Magisk modules I used. After removing them the battery drain stopped.
Try getting the logcat output and see if something is reported there.
Also make sure you are using the right firmware.
Thanks for the advice Boracho, but this is happening on a 100% clean install. Not even gapps on it.
Did clean installs of both OS and recovery versions 19.1-20220917, 19.1-20221001 and 9.1-20221008... all had the same problem. Finally remembered I had 19.1-20220723 in a pendrive. Installed it. Works just fine. Battery problem is gone.
Disabled auto updates. The end.