Related
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Also where do I download the following Flashable zips: (there is no dowload link)
Update 5/4/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL
Update 3/26/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS
Update 3/6/12 Flashable zip for Mirage CM7.2 / ICS CM9
Update 3/2/12 Flashable zip for Mirage CM7.2 / ICS CM9 / MIUI v2.2.24
ZueKary said:
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Click to expand...
Click to collapse
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
RASTAVIPER said:
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
Click to expand...
Click to collapse
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
ZueKary said:
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
Click to expand...
Click to collapse
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
RASTAVIPER said:
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thank you
Thanks (& battery drain issue)
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
pandachilli said:
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
Click to expand...
Click to collapse
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
battery issues [PARTIAL FIXES]
ZueKary said:
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
Click to expand...
Click to collapse
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
pandachilli said:
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Click to expand...
Click to collapse
ZueKary said:
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
Interesting - if possible let us know how it goes. I'm keen to find a nice stable build, Cm7/CM9 seems like the "best of both" however, if I find out Cm7.2 has a healthier battery experience, I'm likely to switch, or prep an alternative sd just in case!
I'll update back here if I find anything more re: battery on ROM
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
ingdebso England
RASTAVIPER said:
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
RASTAVIPER said:
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wish you had posted that before. I installed 7.2 (stable) according to this link: http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html which is suppose to be based on this post: http://forum.xda-developers.com/show....php?t=1000957 with a newer image file. I did this on Friday and so far everything works wonderfully. Battery life is excellent. I think even better that when I was using the Stock and I have NOT installed any kind of battery saving app.
The only problem I keep having, which I also had with the previous installation is the status bar disappearing randomly. I get an error message "the application statusbar (process com.android.systemui) has stopped unexpectedly)". The only suggestion I have found is to wipe the card which did wipe before installing this version using "EaseUS Partition Master 9.1.1". If you have any suggestion on how to fix that issue I would feel very happy with the performance I have.
Even a tip on how to reopen the status bar without rebooting will be greatly appreciated.
pandachilli said:
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
Click to expand...
Click to collapse
My current installation is wonderful with battery life. If I can get a fix for the "the application statusbar (process com.android.systemui) has stopped unexpectedly)" error. It will be the closest to perfection I have tested so far and I had tested 3 different installations so far plus I used the stock for nearly a year.
I found the following recommendation in the link posted by RASTAVIPER (thank you!). I'm giving it a try right now. Will report tomorrow how it is working after unchecking "disable full screen".
Recommendations:
1) Regarding the status/notification bar force close issues, I recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. This also improves the app behavior especially movies and games that need full screen.
Click to expand...
Click to collapse
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
ZueKary said:
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
Click to expand...
Click to collapse
Great news - thanks for feeding back.. so you're using "[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards." ??
RE: battery - no drainage during sleep, random power off's etc?
Going to wipe my SD and start again this evening BUT...can't decide between your recommend ROM or RastsVipers's suggestion of "CM7, Mirage"
Confused.
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
satya-1998 said:
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
Click to expand...
Click to collapse
I like the handy tip of removing the phone.apk
Now can you tell me where is that thank you button? (Never mind. I found it )
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
SO... in regards to the KT-SGS4 KitKat 4.4 TouchWiz kernel, the vast majority of users seem to have no problems with it, but there ARE KNOWN issues that appear to be caused by this kernel for some users, with varying degrees of rarity. WHY certain users have these issues when others do not is not currently known, but it would be great if we could figure this out. I am HOPING this thread (and it will only be a THREAD with input from others) will help us find cures for the issues we face with this kernel.
KNOWN ISSUES:
#1. Sound skipping - This seems to be the most common issue experienced with the kernel and I actually would not call it rare. Some possible fixes for this are to: A) increase the Media/Music Min Mhz and Bluetooth Profile Mhz to around 702 Mhz or so, B) try using a different I/O Scheduler and try adjusting the Internal and External Read Ahead Buffers, C) change disable_hotplug_media from a 0 to 1.
#2. Phone freezes/locks up while charging
#3. Screen flickers when a window is open over the desktop
#4. Mobile connection/data (and possibly also GPS) loss a while after booting phone - this may be the rarest issue, but it is OBVIOUSLY the most serious. I have suffered from it personally. I contacted Ktoonsez regarding this and he denies it being a known issue since many thousands of users use his kernels and don't have this issue... I have confirmed multiple other users who DO have this issue and the only thing I see we have in common is the KT-SGS4 kernel. It appears that this issue MAY be fixable by using the "right" choice of governor and settings. The problem is that what the "right" choice of governor and settings are MAY be determined by your ROM. On stock rooted NAE with MF9 bootloader, using largely the kernel default settings, including the interactive governor, APPEARS to have cured this issue for me (as well as the freeze while charging), while using the ktoonserativeq governor or the pegasuq governor appear to have caused this issue (I am still in the process of investigating this...).
This is not meant to be in any way negative towards Ktoonsez and I certainly appreciate all the work he does to provide us kernels, but there ARE issues that some of experience and I hope this thread can help us work TOGETHER to solve them! If there are any other issue that you believe should be listed, please post them. If you have any possible cures, please post them. If you need any help, please ask. If you have any input, please post! :highfive:
I can't get his kernel to run on my phone for the life of me so I stuck with Negalite NAE Stock Kernel, but I use his kernel religiously on my wife's s3. Even using basically the same setup I still get skipping on music, phone goes unresponsive after charging a few hours. And a few others.
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)? I think the governor and adjustments are also critical in solving this problem. I've been using ondemand and somebody said interactive is also helpful. The other thing here is that it could be an issue of I/o scheduler. I've been using sio. I'm getting minimal skipping at this point. You're right that ktoonservativeq caused MAJOR skipping, even with tons of governor tweaks.
After switching to ondemand, my phone hasn't locked up while charging, but it has randomly locked up at other times. Weird.
On issue #4, I've lost data less with ondemand but it hasn't completely solved the problem. Sometimes I can toggle Airplane Mode on and off and get going again, but mostly that toggle won't even work and I have to reboot.
JesseAaronSafir said:
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)?
Click to expand...
Click to collapse
That is an interesting question, now that you mention it. I had been using ViPER4Android, probably while I was having the skipping issue, but I stopped using it in the long process of attempting to cure my mobile connection issue (I read something that made me think it could be related) and I'm actually not sure if I ever had the skipping issue without it.
Of all the issues though, this one is very common in the KT-SGS4 kernel thread, so I DOUBT (but don't know) that everyone experiencing it is using
ViPER4Android.
(Also, I THINK it skipped for me without Convolver turned on).
I haven't used v4a since I was on Negalites
elwood said:
I haven't used v4a since I was on Negalites
Click to expand...
Click to collapse
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
rsngfrce said:
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
Click to expand...
Click to collapse
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
arikdahn said:
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
Click to expand...
Click to collapse
I didn't forget it, it is issue #2!
#2. Phone freezes/locks up while charging
In my experience, the phone does NOT have to be off while it is charging to have this issue, it would happen to me when I was charging my phone with it on. Fortunately, on NAE stock rooted with MF9 bootloader, using the mostly default kernel settings with the interactive governor seems to have fixed this issue for me, as well as the mobile connection/GPS issue (knock on wood still...). I mainly just adjusted the I/0 Sceduler to noop and the Media/Music and Bluetooth Min Mhz to 702 Mhz from the stock settings. The only issue I am personally left with now is the screen flicker.
I don't think the screen being on or off relates THAT much to the music skipping issue, it skipped for me too with the screen on. Definitely I would say, using the ktoonservativeq governor with Ktoonsez' settings WILL result in music skipping... BUT, IMO, this MUST BE TAKEN INTO ACCOUNT, Ktoonsez DOES NOT HAVE OUR PHONE... how can his settings POSSIBLY be OPTIMAL for our phone? Think about that!
As far as your WiFi tethering issue, I am well aware of it personally, having read your other posts, but I don't know much about this (don't use it myself) and in another thread I was going to direct you to a link you are already aware of that didn't help. If anyone can help arikdahn with this, please jump in! :good:
I definitely had more problems with music skipping when the screen would turn off. Using ondemand or interactive with sio and 2048 read ahead caches seems to have almost completely resolved the issue for me. I'm still not sure which I/o scheduler is best.
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
rsngfrce said:
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
Click to expand...
Click to collapse
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
arikdahn said:
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
Click to expand...
Click to collapse
Hey, I'm not in any way disputing what you are saying, the point of this thread is to figure these things out! I'm certainly not presenting myself as the expert on these issues! I'm just a lucky one who seems to have mostly resolved the issues on MY phone. (BUT... I AM NO ANDROID EXPERT EITHER and will never claim to be, but I am not saying it is a limited-resources issues, what I am saying is that I believe the default settings will allow the governor to throttle down to below the level necessary to play music without skipping... I could be wrong, but that it what it looks like to me.)
Because SO MANY people APPARENTLY don't have MOST of the issues mentioned, I personally think this is highly related to which ROM you are using... though I don't know what ROM those other people are using...
DOWNGRADING TO LOLLIPOP:: --- B151 from B331
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
----
THX @skeppley
THX @Demian3112
----
Figured the above was an important surprise for some of you... OP still valid
Hello Everyone! Im new to the whole Honor 5x thing, coming from an m8 now, and before that a nexus 6, and before that a z3 then before that an S4 and before that an HTC Evo 4G LTE... Along with some minors, LG Risio, Moto E, S5...
Im just happy to say that so far I really enjoy this phone! Within the first few days of using it on Lolipop, i was getting 1d 15h type battery life which if youve looked at the phones ive mentioned so far... Really..really..wasnt what I was used to. A Day? For sure, the htc would be at 18% getting back on the charger... and it would die at 10%... with how long id had it. But... A Day was doable.
Ive been looking for a phone for SOOooOOO long now that had good enough battery to last a day at max brightness... Tweaking kernels, and Installing various ROMS (all of them per device)... Crack Flashing, as some would say. It just became a hobby... Ive noticed many weird things about the community, to those reading... let me list them now...
1. People all of the sudden(within the last 2 years?) prefer stock android over anything, regardless of what additional features are being added... Such as battery life improvements, Multitasking improvements, theme improvements, usability improvements... People like stock android... hmmm?
2. People want to be nexus so bad they will theme other UI's to death, just to make it look like stock, generic android... hmm..
3. Battery life, while a common complaint, seems to be indifferent to how frequently people update their phones.. (note: Marshmellow EMUI has a multi core battery bug, listed on XDA under mods..) or what ROM they choose (note the most popular rom being one with significantly worse battery life than stock)
4. Security improvements are completely unnecessary to the community (note the most popular rom being one that hardly supports the fingerprint sensor)
5. No matter how many bugs (even those listed in OP) people will always flock to the latest update of android. And then subtly complain to the developer about the bugs they already know about..
Such a strange mixture of people...to be sure.
However what ive noticed here, is a complete lack of readily available information, so i am hoping some of you might be able to assist me.
TL;DR
So I succeeded in downgrading my phone from MM to LP, as the battery life thing is a legit problem for me, as much as it may not be for other people. However the fingerprint sensor has been disabled, and no longer exists in the settings list... nor is it part of the startup. (confusing to be sure, you would think it would be there, and just FC when clicking on it were there to be a bug, or if the OS didnt detect the sensor or something... it should still be there yeah? If i understand how it works...
Also I cant seem to flash a B151 rom at all, being on B33...3? <- marshmellow... and im assuming at this point that means i wasnt supposed to be able to downgrade... (oops)
So i got TWRP installed (whats up with all the random errors twrp is throwing? Assuming thats normal...?) and am awaiting a BMarshmellow rom to finish... Which leads me to...
Where are the Emui ROMS? Unless its closed... but if this rom maker can do it... ?
and also, is the fix to the battery life on marshmello noticable to those of you who also care about battery life at all?
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Demian3112 said:
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Click to expand...
Click to collapse
Well there is a fix for it in the mods section that fixes battery. Finally got this phone back to functional lol..
Anyway, the fix for the moment anyway looks like it works, just has to be redone every reboot but really isn't that hard. After applying mincores mincpu 0 the big cores only light up when necessary. So far its helping a lot with battery life at least noticeably. Listented to music the whole way to work this morning and was still at 97% when I got there (I have an hour drive) , and that's using Youtube Music over 4g.. Not too shabby.
Yesterday I got to work doing the same thing on marshmallow at about 85-90 so it is doing something, and watching Kernel Auditor shows the big cores turning off when not in use. Worth checking out, applying the settings that are mentioned there don't do much im afraid, as I cant get them to stick through a reboot yet.
Currently writing an init.d script to make that happen every boot.
For now to my knowledge though it is working. Though I think lollipop was for sure better apps on screen off actually worked properly -_-; which im noticing more and more it doesn't anymore. Its more like a Doze control which is annoying because Doze is not near as good as stock lollipop control. I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know!
TL;DR
I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know! Id much rather downgrade than continue to fix marshmallow.
Though for those of you wondering, Viper|Atmos//Sony Beats the audio mod works perfectly on this phone
Just finished Init.d for Mincpus to fix the whole Big Little problem Super good stuff. Phone now booting in the big little mode you were talking about. super easy stuff.
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
skeppley said:
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
Click to expand...
Click to collapse
U need the firmware had same.. revert though dload
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
You should try CyanogenMod 13: excellent battery life, USB OTG and gyro working, much better CPU & RAM management...
FP reader is working, but you must upgrade to MM first (to update trust zone and radio firmwares).
igotlostintampa said:
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
Click to expand...
Click to collapse
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
Demian3112 said:
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Click to expand...
Click to collapse
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on your bed at night? And then never again?
As for CM13, im fairly apathetic to the topic... Not to be annoying, or rude, but ive heard the excellent battery life claim a million times about stock android, and while ive noticed its improvements over something like...say, Sense, or Touchwiz... Ive never seen it beat the z3's battery saving tool (before marshmallow), or as of the day I got this phone, Huaweis non-debloated lollipop.
Ive never seen a phone still be at 30-40%, at the end of work, the day after the day I charged. Until this phone. The Z3 would make it a little past lunch if I barely used it on day 2, but this phone played pokemon go for 2 hours the day I charged it, I spent the day listening to streaming music, browsing for various small things, watching a few youtube videos, a little navigation... And it had 40% when I left work the next day lol at 100% auto brightness. Id love to see some screen on vs idle drain comparisons between this phones CM13 and Stock, at that point, ill believe a battery claim.
It played pokemon go at 60fps and the game is a known battery/gpu hog (s7 plays slower than this phone, likely due to lack of gyroscope?)
other than some various laggy UI glitches, the phone was pretty much what id been looking for (I Prefer Miui over stock android, this phone is similar)
igotlostintampa said:
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on yuur bed at night? And then never again?
Click to expand...
Click to collapse
What buildnumber and Custom version/Cust do you have? Might be able to link you the right firmware.. twrp backup doesnt backup firmware that explains that you dont have a finger print, is the H from Honor at boot logo Red also?
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
skeppley said:
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
Click to expand...
Click to collapse
Your Reply has been added to the OP for those concerned with Downgrading. Figured it might be nice to stumble upon the directions that, after reading many posts throughout the various roms, many people might actually be looking for. Will likely try this tonight when I get home, battery is much better with the battery fix, but not as good as lolipop
Great.
Hope to help others that were stuck the same way
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Demian3112 said:
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Click to expand...
Click to collapse
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
igotlostintampa said:
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
Click to expand...
Click to collapse
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Demian3112 said:
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Click to expand...
Click to collapse
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
igotlostintampa said:
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
Click to expand...
Click to collapse
Im using Force doze app.. U can whitelist apps and as soon as you turnoff your screen it starts doze... You wont get notifications from apps you didnt whitelist until you turn it back on