Hello,
I apologize in advance for my English.
I'm using nexus 6, stock 7.1.1 no root, no unlock bootloader ....
The problem is that my cpu2,3 is still running at 100% frequency.
I tried flash, factory reset ... nothing helps.
Before that, I had a root and I played with thermal config so that the kernels did not turn off at 40% of the battery.
I'm running now stock and the kernels behave like this ...
Please help, I'm quite desperate, my battery is gone, my phone is hot.
I discovered that this usually happens when the battery falls to about 35%, the two cores turn off, and when I charge the kernels are connected but the frequency is still 2649mhz.
Do you have an old battery?
You might try resetting the bootloader logs and see if that gives you any relief.
1) Power off your phone
2) Press and simultaneously hold the Power and Volume Down buttons putting the phone in fastboot mode
3) Use the Volume buttons and scroll through the menu until you see "Bootloader logs"
4) Press and hold the power key for 7+ seconds until the phone reboots normally
5) On boot, fully charge the battery
If you see some improvement as a result of those steps, consider replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Hello,
the battery is one month old.
This bug started after I tried different rom and kernels .... I tried also to change the BCL and wrote in a set of thermal engine.
Now, even after the flash stock rom these things happen, with a load of 0% and a frequency of 2649mhz.
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
I apologize for writing English through the translator
It's possible it's still the battery. But I'm not certain what the following means;
zip545 said:
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
Click to expand...
Click to collapse
Are you still on 5.1.1?
If that is right, then the thing to do is update to the last stock release. The easiest way to do that is probably using ADB sideload with a factory full OTA.
You can also fastboot flash the full factory image (confusing I know, but full factory and full OTA are different).
The instructions on each of those google sites are good. On the second one, where you would be fastboot flashing, the N6 is an older device so when 2 possible commands are suggested, use the one indicated as for older devices.
Also, instead of installing the full Android SDK, you could use Minimal ADB and Fastboot.
This thread should help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I tried this procedure about 5x ...
I do not know anymore so I'm writing to you where you have more experience ...
I was on 5.1.1 and flash ota update helped adb on 7.1.1 and so far everything goes well. I will check if the processor does not go all the way to 2649mhz.
As I say it all started by trying out rom, different kernels and editing a set of thermal engine .....
Is it possible that full factory image does not return all files ???
I have a screenshot but I can not send it here because I'm new.
If you did a full return to stock after trying the kernels you mention, all of those changes are gone.
When you flash a kernel, it's the same as the boot image. So when you sideload or fastboot flash the stock ROM, the boot image is returned to stock and your previous changes are gone.
I'm wondering if you had matched the kernels to the ROM version you were running. If you flashed a 7.x kernel on a 5.1.1 ROM, that might cause the trouble you had.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I did some searching to refresh my memory. It's been a long while since 5.x [emoji6]
If all of your maxed cpu problems occurred while you were running 5.1.1, then I think it's likely a DNS bug that was around back then may have been the root cause of your problems.
If you still experience the cpu problems on 7.1, then it's not likely due to that bug.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I probably wrote it wrong ....
I used android 7.1.1, no 5.1.1
I installed the lineage os14.1, I changed the thermal engine file so that two cores did not shut down at 40% of the battery.
I also installed the script to turn off the BLC which is here on the forum.
Then I installed the stock 7.1.1 and did the same, it did not work so I installed the Elementalx kernel.
Then I installed the factory image 7.1.1 and you noticed that the 2.3 core is ON 2649mhz! This was done even when the battery was 100%, 80% .....
Nothing helped, factroy reset, installing factory image ... just nothing
Then I installed stock 5.1.1 and everything worked out!
On stock 5.1.1 the processor was driving normally, then I factorydled again factory 7.1.1 and again the CPU kernels went nonstop to 2649mhz.
Now it seems that the processor is running normally, I am in the testing phase 7.1.1.
Related
I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.
Octa_core said:
I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.
Click to expand...
Click to collapse
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?
anmolkakkar said:
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?
Click to expand...
Click to collapse
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.
Octa_core said:
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.
Click to expand...
Click to collapse
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?
anmolkakkar said:
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?
Click to expand...
Click to collapse
Like I said, I have been doing full stock installs, meaning everything is wiped off and I always set everything up from scratch, no backups.
I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads
Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!
madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome
I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.
I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.
peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks
AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it
Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237
Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!
I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
Hey guys.
So i have downloaded Ressurection Remix for Shamu 7.1.2
It just so happens my Baseband is 7.1.1 and i have to update it to 7.1.2 to match my Rom.
I'm saying this because i have some issues with calling, i've seen a video with my exact problem saying its the baseband.
So the problem is.. the LATEST nexus 6 firmware is 7.1.1 (N6F27M, Oct 2017).
For the new 7.1.2 i need 7.1.2 (NJH47F, Aug 2017).
This version appears ONLY on Pixel models firmwares on google dev.
Should i just download the pixel one and install it on my nexus 6?
The hardware of the Pixels are completely different. What you're seeking to do is not possible, and worse, if you could install the radio firmware it could do irrevocable damage to the Nexus 6.
Strephon Alkhalikoi said:
The hardware of the Pixels are completely different. What you're seeking to do is not possible, and worse, if you could install the radio firmware it could do irrevocable damage to the Nexus 6.
Click to expand...
Click to collapse
Thanks for your reply.
So what should i do now?
I can't imagine that any radio version would be a problem. They are independent of OS and backwards/forward compatible.
Maybe just try the baseband cache eraser in the flashable radio thread.
Else try booting to safe mode (you will lose your settings) and see if the problems still exist. If it works in safe mode, then there is an app or setting causing the problem.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I can't imagine that any radio version would be a problem. They are independent of OS and backwards/forward compatible.
Maybe just try the baseband cache eraser in the flashable radio thread.
Else try booting to safe mode (you will lose your settings) and see if the problems still exist. If it works in safe mode, then there is an app or setting causing the problem.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Well then, i am suspecting its the Viper4Android and dolby.
Safe mode didn't help.
Neither did erasing viper or dolby..
I ended up reflashing once again.. so its fine for now but i haven't installed any mods yet. Just the EXkernel.
Is there any program that can make a Restore Point? so if i'd like to restore, it will revert any changes to the system and also remove the added applications to the restore point date?
Titanium back can sure backup, but i didn't see a restore option.
Yes TiBu can restore. Check the menu.
But that's not what I would do. Assuming you have TWRP recovery installed, just create a backup there. It's referred to as a nandroid. If you're using a stock recovery, then check out FlashFire.
Always test a backup before relying on it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Yes TiBu can restore. Check the menu.
But that's not what I would do. Assuming you have TWRP recovery installed, just create a backup there. It's referred to as a nandroid. If you're using a stock recovery, then check out FlashFire.
Always test a backup before relying on it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
I sure do have TWRP.
Does the backup on TWRP act as a restore point? or just the same as TitaniumBackup just changing the apps back to what they were without removing all that has been added later on and without reverting system files?
A nandroid creates image files of whichever partitions you have selected to back up. It is basically a snapshot of the partition. So if you backup system, boot (kernel) and data as part of the backup then add a new app or change a system setting, you will be able to restore the backup and return to the state before the changes. You will lose all changes that occurred after the backup.
I strongly suggest you do some in depth reading about backups and practice backing up then restoring before going much further in your custom ROM/kernel journey. The effort you put in now will save you heartache in the future. There is a TWRP thread here on xda. There are loads of threads on xda (for example) geared to help develop a basic understanding of these concepts.
FlashFire is an on device method of making backups (linked in earlier post) and is similar to but not the same as doing it in recovery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I can't imagine that any radio version would be a problem. They are independent of OS and backwards/forward compatible.
Click to expand...
Click to collapse
They're not hardware independent however. Each baseband is designed with a particular device in mind, which is why what he wanted to try won't work. It would be like me trying to upgrade my roommate's Moto X Style with the Nexus 6 baseband.
If installing a radio from a completely different device were possible, that would extend the lives of these devices even farther than our developers here are already capable of.
Strephon Alkhalikoi said:
They're not hardware independent however.
Click to expand...
Click to collapse
Fair enough clarification, some noob might misread the conversation. But I don't think I even suggested that using a different device's firmware was appropriate. Just that the version was independent of the OS. OP was looking for a 7.1.2 radio and it's just not the issue.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Fair enough clarification, some noob might misread the conversation. But I don't think I even suggested that using a different device's firmware was appropriate. Just that the version was independent of the OS. OP was looking for a 7.1.2 radio and it's just not the issue.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
I actually did understand yet the comment could mislead.
Anyways I ended up installing 7.1.1 radio, works great!
Never imagined how much impact the Radio/Modem has on the cell network performance...
I downloaded all 3 latest ones, Oh wow..
One gave me 35-40Mbs download speed with 3Mbs upload, the second one gave me 35-40Mbs download with 10Mbs Upload!
The third one? 5-10Mbs download with.. 1Mbs upload..
All from the exact same spot, about the same time, exact same server, exact same cell tower.
Which one did you use?
shadowcore said:
Which one did you use?
Click to expand...
Click to collapse
I have got mine here:
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Flashable in recovery, pretty amazing.
Which one I used doesn't matter because it's very dependent on your own area and cell towers.
So you should download all 3 and test one by one which one gives you the best results.
hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all
Tenzinjamyang said:
hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all
Click to expand...
Click to collapse
Let me know the rom names ?
ragulhm said:
Let me know the rom names ?
Click to expand...
Click to collapse
aosip and nitrogen
You might try ABC ROM or Beltz. Both are in the Android Builders Collective thread.
If you still have reboot problems with either of those ROMs, I would wonder if your battery has been replaced.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
I'm not the least bit sure the above is necessary. Without question you should be on the newest bootloader before going to oreo, but returning completely to stock, then rooting, which just gets overwritten by flashing a custom ROM seems excessive.
If you are that nervous about doing an upgrade, then I strongly recommend NOT using a toolkit. Toolkits are great, until something goes wrong and because you're automating the process you'll have no idea what went wrong. Particularly on N6, it is so easy to just use ADB/Fastboot. Those drivers have to be installed anyway for a toolkit to work so you're not gaining anything.
If you follow that advice, please make sure you back up EVERYTHING since the method is directing you to wipe your storage (user data). Of course, if you follow proper return to stock instructions, you'll wipe internal storage (user data) as a function of the -w fastboot switch.
IMHO, it's a mistake to link directly to a factory image release. Here is the factory image page, complete with instructions and checksums for the files. You should ALWAYS verify checksums before flashing a file. The file linked above is the last one listed (newest) in the shamu grouping.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
fkfmfz said:
before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
Click to expand...
Click to collapse
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours
Tenzinjamyang said:
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours
Click to expand...
Click to collapse
There are many reasons this could happen. An app, a theme, an old battery.
Look to get a log right after the reboot,
adb shell cat /proc/last_kmsg
adb logcat > crash.txt (look for a shutdown thread)
adb shell cat pstore/last_kmsg/serial logs
or if you are running a theme/substratum, remove it for now to see if the problem improves.
If you have mods like custom kernel, exposed, viper, remove them to see if the problem improves.
Delete bootloader logs by rebooting to bootloader, scroll through with volume buttons until reach bootloader log entry, long press power until the phone reboots and immediately fully charge. If the problem improves, it's likely due to the age of your battery.
Try booting to safe mode and see if the problem comes back. Safe mode will not only the minimum necessary for the device to run. It eliminates apps for the most part.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well
HueyT said:
Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well
Click to expand...
Click to collapse
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.
Tenzinjamyang said:
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.
Click to expand...
Click to collapse
No? This is a nexus 6 thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.
Strephon Alkhalikoi said:
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.
Click to expand...
Click to collapse
I've not had reboots on either Beltz or ABC. Though I have been running ABC pretty much since it was built for shamu.
Back before I replaced my battery, especially towards the end, it would reboot when even when it was plugged in. At its worst, plugging-in would crash the phone.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I've not had reboots on either Beltz or ABCBack
Click to expand...
Click to collapse
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.
NLBeev said:
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.
Click to expand...
Click to collapse
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery, esp. when it's hours into use.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery....
Click to expand...
Click to collapse
Because my 'once a day reboot' happens in the afternoon I will check the battery charge % when it happens.
But it's a soft reboot; same as when substratum.
I keep an eye on the battery and also on substratum.
I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?
EAK128 said:
I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?
Click to expand...
Click to collapse
Kernel settings maybe? If possible, run the problematic ROM while on charger and see if it reboots.
@NLBeev, I agree that a soft reboot sounds more like theme, or maybe app. I can tell you that I've been running ABC Oreo for N6 since its release. I've been dirty flashing (deleting substratum theme first) each time until last week when I clean flashed.
I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help. You can store a larger file that way.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
....I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help.
Click to expand...
Click to collapse
Use my N6 daily
I am suspecting 3 things: battery, substratum and the powersave option of Ex kernel.
It's now evening here and no soft reboot yet.