So, I had a day 1 v20 that began randomly rebooting back in december. Thought it was a hardware issue and finally got around to replacing it the other day. Now, after getting the replacement v20 set up on a custom rom (AICP) I'm seeing random reboots again. I've tried every single custom rom available for the h918 and they all experience reboots. When i've asked about the issue in the threads it seems as if I'm the only one. It appears to be a custom-rom only problem that apparently no one else is experiencing? The kernel panics are being caused by the modem, and it started happening when I upgraded to the 10j base. This replacement also came with 10j. Am I just super unlucky with two duds or is there really something going on here?
TLDR; Anyone else with a h918 with 10j bootloader/modem running custom roms and seeing random reboots?
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Biff627 said:
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Click to expand...
Click to collapse
Have always left kernel stock.
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Biff627 said:
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Click to expand...
Click to collapse
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
trobertson said:
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
Click to expand...
Click to collapse
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Biff627 said:
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Click to expand...
Click to collapse
The phone came with stock 10j.. flashing this wouldn't change anything.
trobertson said:
The phone came with stock 10j.. flashing this wouldn't change anything.
Click to expand...
Click to collapse
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Biff627 said:
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Click to expand...
Click to collapse
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
trobertson said:
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
Click to expand...
Click to collapse
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Biff627 said:
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Click to expand...
Click to collapse
Aicp, rr, cm-remix, stock Lineage.
trobertson said:
Aicp, rr, cm-remix, stock Lineage.
Click to expand...
Click to collapse
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Biff627 said:
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Click to expand...
Click to collapse
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j as most custom ROM users are still running 10d firmware
trobertson said:
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j
Click to expand...
Click to collapse
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Biff627 said:
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Click to expand...
Click to collapse
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
trobertson said:
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
Click to expand...
Click to collapse
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Biff627 said:
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Click to expand...
Click to collapse
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
trobertson said:
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
Click to expand...
Click to collapse
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
Not a Samsung fan. Especially with KNOX. I buy phones first based on the chances of development producing workable custom ROMs and second based on hardware features.
Back to the main topic: I just managed to flash the 10i modem alone so we'll see what happens. I'm working on extracting the 10d modem as well.
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
UPDATE: Flashing the 10i modem made no difference, still having random reboots (although they seem less frequent), I will try the 10d modem once I find a way to extract it from the TOT files posted on this forum.
Related
on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.
So I am on H91810q and I have kept root through the upgrades. Am I still able to flash another rom like LineageOS or am I stuck with stock since I upgraded so far?
Try it -- it isn't going to break your phone
Probably isn't going to run to well on new firmware though. Most of the heavy development was done on much older firmware, and those parts haven't been updated.
-- Brian
runningnak3d said:
Try it -- it isn't going to break your phone
Probably isn't going to run to well on new firmware though. Most of the heavy development was done on much older firmware, and those parts haven't been updated.
-- Brian
Click to expand...
Click to collapse
I'm thinking a TWRP Full Backup of the stock rom and wipe and flash LineageOS. In theory do you think I would be able to restore stock if something doesn't go right?
Yes. When you install LOS or a LOS based ROM the only thing that gets flashed is boot and system. Both of those are backed up by TWRP.
-- Brian
runningnak3d said:
Yes. When you install LOS or a LOS based ROM the only thing that gets flashed is boot and system. Both of those are backed up by TWRP.
-- Brian
Click to expand...
Click to collapse
Well I just flashed LOS and I can see the screen flashing on and off but no boot. Any other suggestions? Am I stuck with the stock rom which I am gettings sick of...
Nope, you can't downgrade. Unless someone picks up development on current firmware, you can only use stock.
Not the answer I was looking for lol...
jrosetto said:
Not the answer I was looking for lol...
Click to expand...
Click to collapse
I know this isn't a custom rom but you're like me and on rooted Q, I use to not enjoy stock due to not being able to customize the phone how I liked but the instabilities in the camera and bluetooth and battery life made me appreciate the stock/stock based roms for the V20 and I actually PREFER a fully functional camera nd awesome audio recorder than inferior apps. But! Askermk2000's kernel is COMPATIBLE with rooted 10q, I am using it and it has honestly breathed new life into my phome for sure and since we don't have many rom options at the moment at least throw this kernel on your stock 10q rom and enjoy it! Here's the thread
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Gytole said:
I know this isn't a custom rom but you're like me and on rooted Q, I use to not enjoy stock due to not being able to customize the phone how I liked but the instabilities in the camera and bluetooth and battery life made me appreciate the stock/stock based roms for the V20 and I actually PREFER a fully functional camera nd awesome audio recorder than inferior apps. But! Askermk2000's kernel is COMPATIBLE with rooted 10q, I am using it and it has honestly breathed new life into my phome for sure and since we don't have many rom options at the moment at least throw this kernel on your stock 10q rom and enjoy it! Here's the thread
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Click to expand...
Click to collapse
Thanks for the suggestion, I'll check it out.
I posted the same thread a week ago and got no help. My moto x has a problem that whatever rom i flash it just stays open for a few minutes then restarts so it's unusable. Please any suggestion is needed as this is my daily driver
Philo0o said:
I posted the same thread a week ago and got no help. My moto x has a problem that whatever rom i flash it just stays open for a few minutes then restarts so it's unusable. Please any suggestion is needed as this is my daily driver
Click to expand...
Click to collapse
What do you mean by it just stays open. Do you mean it never boots? Like a bootloop? If so, search 7.0 ROMs bootloop, you'll find the solution, tons of threads on the help and q&a here. But if you don't mean what I just explained then could you clarify?
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Philo0o said:
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Click to expand...
Click to collapse
If I were you I would flash back to stock and make sure you you don't have a hardware problem, If nothing else it's a chance to start over. I haven't gone to custom roms for these reasons, mine is my daily driver to and I can't afford to get caught without it.
Philo0o said:
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Click to expand...
Click to collapse
No worries. Yeah I don't know what the issue could be, could be a ROM issue, it's weird though, but like the poster above me, it could be hardware failure and flashing stock would be a good way to find out.
I would love to go back to stock but how? All the tutorials are very hard for me to follow can you guide me to an easy one or tell me how?
Philo0o said:
I would love to go back to stock but how? All the tutorials are very hard for me to follow can you guide me to an easy one or tell me how?
Click to expand...
Click to collapse
I agree that they are a little hard to follow, I looked at them myself and it looks like the quickest way would be to go back to 6.0 and upgrade back to 7. But someone else could correct me on that.
For future reference, it's best to always twrp backup your stock rom before doing any kind of major changes especially custom roms. That way you can always fall back to original if something goes wrong.
tbkrazeey said:
I agree that they are a little hard to follow, I looked at them myself and it looks like the quickest way would be to go back to 6.0 and upgrade back to 7. But someone else could correct me on that.
For future reference, it's best to always twrp backup your stock rom before doing any kind of major changes especially custom roms. That way you can always fall back to original if something goes wrong.
Click to expand...
Click to collapse
I would go back to stock 6.0, if he hasn't upgraded to 7.0, I'll do some digging, find good guides, and post them here in a bit @Philo0o!
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Spencervb256 said:
I would go back to stock 6.0, if he hasn't upgraded to 7.0, I'll do some digging, find good guides, and post them here in a bit @Philo0o!
Click to expand...
Click to collapse
I think I might also do a twrp backup of my 7.0 and make it public, but it will take me a couple of days before I can factory reset. There doesn't seem to be any stock 7.0 backups around on xda.
Philo0o said:
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Click to expand...
Click to collapse
That's good news actually, there's a lot more stuff around for 6.0.
Philo0o said:
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Click to expand...
Click to collapse
Alright if you wanna go the custom ROM route, don't update to stock 7.0, not many custom ROMs work with it's new firmware. I'll get you a guide to go back to stock 6.0 then!
Edit: Alright @Philo0o, here's a good page with all the firmware links for your phone, and the commands to flash the firmware are there for you. Let me know if you have any questions about that.
Also, when your ROMs aren't working, what are you doing to try again? what I mean is you could try a full data format in twrp. Not just a wipe of data, system, etc.. A full format isn't quite like going back to stock, but it may help if there are leftovers somewhere causing issues if that makes sense.
so if you wanna try a full format, backup your internal storage to a computer, or to an sd card, and then format, and then you will have a clean slate, move what you need back over to your phone and voila!
Ill look through that tutorial, and whenever i flash a rom i do a full a wipe
Philo0o said:
Ill look through that tutorial, and whenever i flash a rom i do a full a wipe
Click to expand...
Click to collapse
Alright, then yeah look through that tutorial. If the issue isn't there on stock, but is on custom ROMs, try asking in those threads
Anyone have anything similar happen?
On OOS 10.5.13 rooted with Magisk stable 20.4.
Tested on several kernels, same results.
A reboot fixes this temporarily but eventually will go back to max. Any help would be appreciated!
What kernel are you using?
What ROM?
Are you in performance mode?
dladz said:
What kernel are you using?
What ROM?
Are you in performance mode?
Click to expand...
Click to collapse
Currently on blu_spark, also happens on Kiri, and Franken
Running stock OOS
No performance mode enabled
rickysidhu_ said:
Anyone have anything similar happen?
On OOS 10.5.13 rooted with Magisk stable 20.4.
Tested on several kernels, same results.
A reboot fixes this temporarily but eventually will go back to max. Any help would be appreciated!
Click to expand...
Click to collapse
For how long stuck on this frequency?
Just flash stock boot img
rickysidhu_ said:
Currently on blu_spark, also happens on Kiri, and Franken
Running stock OOS
No performance mode enabled
Click to expand...
Click to collapse
So it's not going to be anything to do with the ROM. I'm on 10.5.12 UK which is the same as 13 in your region.
Honestly, I'm on xXx and rooted.
Just don't flash the kernel tweaks..
Just go with the stock kernel.. performance seems to be the emphasis on all of the custom kernels yet battery doesn't..
This is a side effect of it..
The reason it's been inherited between kernels is because there are values or even a few changes which haven't reverted.
You may even need to reinstall the OS. Unless you can isolate the changes causing it..just saying. Maybe quicker.
cultofluna said:
For how long stuck on this frequency?
Just flash stock boot img
Click to expand...
Click to collapse
It stays stuck permanently. Rebooting helps for a short while but then it goes back.
Yeah I haven't tried stock yet but something tells me it's not kernel related, but possibly some app or module.
dladz said:
So it's not going to be anything to do with the ROM. I'm on 10.5.12 UK which is the same as 13 in your region.
Honestly, I'm on xXx and rooted.
Just don't flash the kernel tweaks..
Just go with the stock kernel.. performance seems to be the emphasis on all of the custom kernels yet battery doesn't..
This is a side effect of it..
The reason it's been inherited between kernels is because there are values or even a few changes which haven't reverted.
You may even need to reinstall the OS. Unless you can isolate the changes causing it..just saying. Maybe quicker.
Click to expand...
Click to collapse
I don't have any kernel tweaks installed, just a couple of Magisk modules like systemless hosts for AdAway, fonts, and BusyBox.
Having trouble isolating the issue so I may need to wipe and start fresh. Just thought maybe a user here had a similar experience and could tell me what caused it for them so I can fix it myself.
Appreciate the responses!
Welcome mate, tbh though I don't shouldn't say you need a kernel for performance.
Maybe battery life but tbh the stock kernel does a decent enough job..if you do wipe, I wouldn't bother with custom kernels.
The performance is defined there already.
dladz said:
Welcome mate, tbh though I don't shouldn't say you need a kernel for performance.
Maybe battery life but tbh the stock kernel does a decent enough job..if you do wipe, I wouldn't bother with custom kernels.
The performance is defined there already.
Click to expand...
Click to collapse
Yeah I just try to find a more lightweight kernel where OnePlus' debugging is removed. Maybe the difference is not noticeable in performance/day to day use so I guess for me it's more of a OCD thing lol
I mainly only like high brightness mode in terms of kernel features. Otherwise I get about the same battery results with every kernel, which is 11%-15% drain per hour.
As for this CPU issue, it's been flawless all day. I'm trying my hardest to stress test the device to see what exactly triggers it. If it remains fine throughout the night and by morning, I guess I saved myself a couple of hours for wiping and getting my setup back!
Will keep this thread posted if I ever manage to find the culprit.
Did you end up finding the culprit? I'm facing the exact same problem. I'm on stock 10.5.13 global, stock kernel. Rooted with magisk 20.4, No mods except for youtube vanced and adaway. Any help is appreciate Ed.
fuukinguy said:
Did you end up finding the culprit? I'm facing the exact same problem. I'm on stock 10.5.13 global, stock kernel. Rooted with magisk 20.4, No mods except for youtube vanced and adaway. Any help is appreciate Ed.
Click to expand...
Click to collapse
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
rickysidhu_ said:
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
Click to expand...
Click to collapse
I flashed omega kernel like you suggested, and the problem just went away. It's been three days now with omega and everything has been great so far. Thanks again!
rickysidhu_ said:
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
Click to expand...
Click to collapse
Which app you used to check the cpu cores?
Sent from my IN2023 using Tapatalk
aygul12345 said:
Which app you used to check the cpu cores?
Click to expand...
Click to collapse
EX Kernel Manager.
Issue came back just last night...frustrating. Noticed battery life was going fast, might need to factory reset at this point.
rickysidhu_ said:
EX Kernel Manager.
Issue came back just last night...frustrating. Noticed battery life was going fast, might need to factory reset at this point.
Click to expand...
Click to collapse
Mine hasn't come back yet, everything is still good thankfully. I'm still on omega. I just can't wrap my brain around this one. And no one else seem to be experiencing this problem.. I searched high and low on this forum, believe me. You and I are the only ones reporting this so far i think.
fuukinguy said:
Mine hasn't come back yet, everything is still good thankfully. I'm still on omega. I just can't wrap my brain around this one. And no one else seem to be experiencing this problem.. I searched high and low on this forum, believe me. You and I are the only ones reporting this so far i think.
Click to expand...
Click to collapse
Yup, seems like it.
Might bite the bullet and reset this thing when I get some time this week.
Update on this issue:
Ended up factory resetting shortly after I originally posted this and everything is working as normal!
Switched to the Pixel 5 though, so will not be keeping an eye on this thread any longer. If anyone else experiences this, seems like a factory reset will do the trick if all else fails! Just install everything back one by one to ensure it's not an app or mod causing it.