Related
Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App
spirosbond said:
Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App
Click to expand...
Click to collapse
Not 100% sure but freq is minimum as it can be. And if cpu is not used no metter is freq 10000MHZ or 300Mhz it uses almost the same power. But when cpu is in use freq is important to power usage. Freq management is good not because it lowers freq but because it lets use lower freq on things that is not require hi freq. so it saves LITTLE LITTLE BIT of power. In idle mode (deep sleep) no meter what freq is.
But i still don't understand the need of governor. It's good only in cases where you overclock cpu but if don't - i don't see why it should be used.
PS Use app called CPU SPY it shows on what freq your cpu is being used and how much of the time.
Thanks! I use CPU SPY and it says tha about 60% or more is in deep sleep, 15%-25% is at 768 and the rest higher, which seems to be a good thing. But my phone still lasts for about 10-15 hours with normal use.
So i thought that maybe my min 768 frequency drain a lot of battery.
To clear things up a bit I use latest oxigen rom+latest franco kernel+zram+Juwe ram script...
Actually deep-sleep state is a special state supported by your phone MCU. In this state, a lot of functionality (therefore a lot of logical gates) are disabled thus MCU consumes very low power compared to normal functioning states. The thing about a CPU/MCU is when it is running even if there are no work to do no code to process, it has to run some command. While idle it must run NOOP (no-operand / no operation) command or do something equally unnecessary like counting a not required number. But in deep sleep mode, MCU actually stops working except for core functions to keep your phone going on.
Think about it this way, in a normal working state, CPUs most basic functionality is to read a command from memory, execute it and proceed to the next command to continue. Thus, in an operating system or a single purpose embedded software, CPU/MCU has to execute a "do nothing" command when you have no job to give it. But even a "do nothing" command need all of the MCU/CPU resources to be kept readily available. If you're sure that you have absolutely no job for your MCU/CPU to do, what you can do is to tell it to go and sleep fr a while until you wake it up again. In sleep, MCU/CPU can shut down a lot of its support systems like math processing, external memory access, graphics related functions (if any), even IO outputs. Depending on your CPU/MCU, this means until an interrupt occurs or a special sub system wakes it up, most of the sub-systems within your MCU/CPU thus may be millions of transistors will not be working so, your CPU/MCU will not consume as much power.
In layman's terms, deep-sleep state is a special state that shut down most of your MCU in your phone, thus while crippling it by removing its ability to function, making sure that it doesn't consumes much power. So OS (Android) (with the help of some additional hardware) controls when your MCU will sleep and under what circumstances it will wake. So it shuts down the engine -so to speak- when you're not using it for long terms and saving fuel rather than leaving your car on idle.
Hope this helps..
Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...
I get about two days of battery life. I use Oxygen without any modifications. CPU is min. 245 (or something like that with 200, I dunno now) and max. is 800. Wifi is always on when I am home.
Try installing Oxygen-r1 and use it with a full battery, do not change anything and do not install too many apps. There will be apps that just won't stop running (like BBC or CNN app), I do not install those. Then you will see how long your battery lasts. If you just write some messages throughout the day and call somebody for 1-3 hours you should get about 2 days.
Then install your apps and test it again - maybe your apps are the problem.
spirosbond said:
Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...
Click to expand...
Click to collapse
Look not at cpu spy but in battery usage to find out what drains your battery. And i can tell All roms are kinda lame in terms of battery, except CM7. In deep sleep it takes about 7% of battery in 10hours. I tried all roms but non of them was so efficient. But latest franco kernel (which i think even more improves cm7 rom) does not support cm7 right now, so i've attached older version if you would like to test cm7+franco kernel.
With normal usage of 50 sms and 30minutes of calls and sometimes wi-fi to download few apps and 20minutes on easy games my battery lats about 18hours. Whan only sms it lasts 30hours. depends how long lcd is on
Well, I'm not an expert on smart phone OSes but I'm an expert on embedded systems and micro controllers. If the designers are not really stupid (which I'm sure they are not) all the peripherals gets suspended when the main CPU goes to deep sleep mode. So, it is almost impossible for the phone to consume much power in deep sleep state. Most likely your phone consumes that power the rest of the time when it is not in sleep mode. I agree with Tommixoft, you should use battery usage info rather than CPU spy to find what drains your battery. Also, here is a quick check list about what consumes power :
1. Screen, especially when it is brightly lit
2. GSM network (Even when you're not talking to phone, GPRS/Edge/3G network communications drains almost as much power)
3. Wireless network
4. GPS
As an additional note, if your phone is not going to sleep mode regularly try to uninstall applications that have "prevent phone from sleeping" security setting.
Hope this helps, and of course there are a lot of more experienced people in the forum that knows about the details of the kernel so they might provide additional info.
Regards,
---------- Post added at 05:15 PM ---------- Previous post was at 05:10 PM ----------
Oh I forgot to tell the MOST important thing, 768MHz is way too high a value to set as minimal frequency. Try to set it 245. I use 122 MHz and it work pretty well. Don't forget, when you need the CPU power, the governor will provide it for you.
Hi guys.
Edit : I am running fully stock, non-rooted and OTA updated Kit Kat 4.4.2
I noticed that a high Android OS usage and wake lock (in my case) comes from the cpu Governor locking all cores to 2.0-2.3 GHz despite nothing happening on the phone. I checked this using the system monitor tool. I have screenshots added.
The problem is that I can't see what apps are causing the governor to never make the other 3 cores go offline. When I check "Top apps" everything is at 0% cpu usage. What is causing the cores to never go offline and stay locked at 2.0GHz+ and drain battery?? It is only when this happens that I get high Android OS usage. A reboot fixes it, but it happens randomly. When I feel that my battery is draining badly, I check my cpu in system monitor and see all cores online even when idle. I just don't get it.
I'm thinking it may have something to do with dashclock/BBS or some combination, as every time this happens, the BBS add on in dashclock shows 0% drain (so it seems broken when it happens).
Please help!
Sent from my SM-N9005 using xda app-developers app
EddieN said:
I noticed that a high Android OS usage and wake lock (in my case) comes from the cpu Governor locking all cores to 2.0-2.3 GHz despite nothing happening on the phone. I checked this using the system monitor tool. I have screenshots added.
Click to expand...
Click to collapse
Hello. Have you found a solution to this problem? I thing I have something silmilar, although in my case the IDLE cores stay at 300MHz and they do not enter offline as they should. I have a rooted phone with original 4.4.2 firmware and Xposed framework installed, but it doesn't seem to be a problem (the cores get stuck after some time).
this is caused by samsungs dvfs (google it for more information). just download and enable the dvfs disabler module from xposed framework
I have xposed enabled, dvfs disabler its enabled.
My minimum 300mhz became 1.19-2ghz, so cpu is stuck.. Onlu one core usually. I find out one app that does that, camera. I enter camera app then exit, cpu minimum core is 1.95ghz and stay there always, till restart.
What rom do you have? I'm on xxuend3
And on what governor? I'm on interactive.
And usually if you move cpu minimum /maximum sliders, cpu became unstuck.
So you have few cores stuck, move sliders up and down and stuck became unstuck
Regarding the top apps not showing, I've found the usage reporting on the device to be entirely broken.
I've had it report, in 6 seperate apps, that Android was using 25%... whilst I'd been playing Oh Edo! Towns for 6 hours straight. It listed that game, which is quite heavy, as 2%.
No way in hell that's accurate.
25% in deep sleep, yes. There's nothing else running, so 25% of 1% per hour for idle processes makes sense. But not during gaming.
Sent from my SM-N9005 using Tapatalk 2
Hello! About 1 day works well for me on the phone, then the middle two seeds get stuck 1,9MHz. Only a restart helps ...
Kernel bugs??
Im on skyhigh kernel. On this one cpu wont stuck.
I found that Camera app makes cpu stuck at maximum clock, like 2.2 or more. The fix, restart phone or use cpu sliders and move them a bit, then cpu became unstuck. Use android tuner, faux, etc for moving cpu clock sliding
Note 3 rooted knox 1, my last Samsuck crap. I want freedom. Stay away from Samsuck!
I found an small annoyance. When i wake up the phone i see an lag... Sometimes its about 5sec,sometimes lower or more. How can i fix this? Tried to raise cpu clock on touch... The same
Note 3 rooted knox 1, my last Samsuck crap. I want freedom. Stay away from Samsuck!
It seems my Nexus 4 (mako) is experiencing hardware issues. Long story short, I've ruled out software problems (returned it to complete stock), and from my testing, it seems that the crash happens whenever the battery experiences high power draw.
Slightly longer story:
When the problem started, the phone was still usable either when using it while plugged into the charger, or when using it underclocked (to half the MHz) on powersave governor. Also when the phone is off, I could only start it while it's plugged in, presumably because the underclock is not yet set during boot thus there is high power draw. Now the problem gotten worse to the point that I can't even start up the phone while it's plugged into a charger. It even crashes when trying to show the battery charging animation when the phone is off and being charged.
Despite all of this, I can use the phone's TWRP recovery without a problem (even when not plugged in). Flashing things with it, and accessing the internal storage through MTP works fine. This gives me hope that perhaps if I can get my hands on a kernel that is underclocked (to half the MHz or less) and perhaps also on powersave governor by default, perhaps I can still use the phone. I just really need it to survive another week. That's when I'll be able to get another phone. .
Could someone, anyone, please provide me a kernel that is underclocked (to half the MHz or less) and using powersave governor by default? That would help me tremendously (or rather, is my last hope), and hopefully is not too much work for kernel devs. Again, I just need my phone to work for one more week.
//*EDIT* The next phone I'm planning to buy is out of stock for another 2 extra weeks.//
Djalaal said:
It seems my Nexus 4 (mako) is experiencing hardware issues. Long story short, I've ruled out software problems (returned it to complete stock), and from my testing, it seems that the crash happens whenever the battery experiences high power draw.
Slightly longer story:
When the problem started, the phone was still usable either when using it while plugged into the charger, or when using it underclocked (to half the MHz) on powersave governor. Also when the phone is off, I could only start it while it's plugged in, presumably because the underclock is not yet set during boot thus there is high power draw. Now the problem gotten worse to the point that I can't even start up the phone while it's plugged into a charger. It even crashes when trying to show the battery charging animation when the phone is off and being charged.
Despite all of this, I can use the phone's TWRP recovery without a problem (even when not plugged in). Flashing things with it, and accessing the internal storage through MTP works fine. This gives me hope that perhaps if I can get my hands on a kernel that is underclocked (to half the MHz or less) and perhaps also on powersave governor by default, perhaps I can still use the phone. I just really need it to survive another week. That's when I'll be able to get another phone. .
Could someone, anyone, please provide me a kernel that is underclocked (to half the MHz or less) and using powersave governor by default? That would help me tremendously (or rather, is my last hope), and hopefully is not too much work for kernel devs. Again, I just need my phone to work for one more week.
Click to expand...
Click to collapse
Don't totally count on this but I can try to get you something.
zaclimon said:
Don't totally count on this but I can try to get you something.
Click to expand...
Click to collapse
I practically have nothing at this point, so anything is welcome. Appreciate the effort.
Hi,
I'm experiencing some problems when using Android Auto. I think that my device is overheating.
Maps becomes very slow after about 30 minutes driving. Sometimes the phone is going very hot and is unresponsive during few minutes. I checked the cpu temp after a drive today and got values close to 60c. I'm running LOS 14.1 right now. I was using CM 13 previously and the heating issue wasn't so huge.
So I wonder if anyone else is running Android Auto successfully on this device ?
update : I disabled thermal throttling using Kernel Aduitor. Android Auto is running perfectly fine now. Phone is heating a lot (80c for CPU but 25c for battery) What is the thermal throttling ? Is it a kernel feature ? Is it the same as thermald ? Is it tunable ?
marcjero said:
Hi,
I'm experiencing some problems when using Android Auto. I think that my device is overheating.
Maps becomes very slow after about 30 minutes driving. Sometimes the phone is going very hot and is unresponsive during few minutes. I checked the cpu temp after a drive today and got values close to 60c. I'm running LOS 14.1 right now. I was using CM 13 previously and the heating issue wasn't so huge.
So I wonder if anyone else is running Android Auto successfully on this device ?
update : I disabled thermal throttling using Kernel Aduitor. Android Auto is running perfectly fine now. Phone is heating a lot (80c for CPU but 25c for battery) What is the thermal throttling ? Is it a kernel feature ? Is it the same as thermald ? Is it tunable ?
Click to expand...
Click to collapse
I would be careful with turning that off. Thermal throttling basically checks how hot your phone's internal components get, and when they reach a dangerous level it forces the device to slow down.
Turning it off means that your device WILL work at hotter temps, but you risk damaging the CPU, screen, battery, etc.
The reason the phone was getting slow is due to 1. the screen being on all the time, 2. the GPS constantly updating.
The N4 wasnt meant for such tasks, so it overheats.
One solution: get a mount that sits on top of the airvents, so that cool air blows over it.
HubrisRev5 said:
I would be careful with turning that off. Thermal throttling basically checks how hot your phone's internal components get, and when they reach a dangerous level it forces the device to slow down.
Turning it off means that your device WILL work at hotter temps, but you risk damaging the CPU, screen, battery, etc.
The reason the phone was getting slow is due to 1. the screen being on all the time, 2. the GPS constantly updating.
The N4 wasnt meant for such tasks, so it overheats.
One solution: get a mount that sits on top of the airvents, so that cool air blows over it.
Click to expand...
Click to collapse
Well the screen is off with Android Auto. But of course the GPS is working. The battery temp stays low at about 25c. The screen is not hot. Only the back of the phone (the upper part close the camera) is getting hot. Thermald is still active and there is still a protection against battery overheating.
I really think that the Lineage kernel is too much aggressive regarding thermal throttling. I tried other kernels but unfortunately they slow down clocks too much when the screen goes off.
marcjero said:
Well the screen is off with Android Auto. But of course the GPS is working. The battery temp stays low at about 25c. The screen is not hot. Only the back of the phone (the upper part close the camera) is getting hot. Thermald is still active and there is still a protection against battery overheating.
I really think that the Lineage kernel is too much aggressive regarding thermal throttling. I tried other kernels but unfortunately they slow down clocks too much when the screen goes off.
Click to expand...
Click to collapse
Btw, there are some stupid gadgets you can buy on aliexpress to help with this issue. Like this weird phone stand with a fan behind it, https://www.aliexpress.com/item/Portable-3-in-1-Holder-Stand-Radiator-Mobile-Phone-Rings-Holder-2000-mA-Bracket-Power-Bank/32824399237.html?ws_ab_test=searchweb0_0,searchweb201602_3_10152_10065_10151_10068_10130_10344_10345_10547_10342_10343_10340_10341_10548_10192_10541_10540_10190_10307_10301_10303_10060_10155_10154_10056_10055_10539_10538_10537_10536_10059_10534_10533_100031_10103_10102_10142_10107_10324_10325_10084_10083_10179_10312_10313_10184_10314_10073,searchweb201603_25,ppcSwitch_2&btsid=ee6398e3-e7a6-4bd7-938c-34f6e0cdef52&algo_expid=21d9a156-0a93-470d-acbc-d807892ce6e8-0&algo_pvid=21d9a156-0a93-470d-acbc-d807892ce6e8 or just buy a holder than fits over the airvents in your car https://www.aliexpress.com/item/Anker-Air-Vent-Magnetic-Car-Mount-Highly-Adjustable-Phone-Holder-for-iPhone-SE-6-6s-7/32824593598.html?ws_ab_test=searchweb0_0,searchweb201602_3_10152_10065_10151_10068_10130_10344_10345_10547_10342_10343_10340_10341_10548_10192_10541_10540_10190_10307_10301_10303_10060_10155_10154_10056_10055_10539_10538_10537_10536_10059_10534_10533_100031_10103_10102_10142_10107_10324_10325_10084_10083_10179_10312_10313_10184_10314_10073-10102_10000902,searchweb201603_25,ppcSwitch_2&btsid=d12c851e-a69b-48e1-b282-0733c26584ae&algo_expid=ab74c295-fb60-418d-9e32-5e32f75bd993-0&algo_pvid=ab74c295-fb60-418d-9e32-5e32f75bd993
Yep, I have the same issue. I was originally using slickrom stable release, then switched to weeklies and the issue showed up. Slickroms is based on lineage, so switched to lineageos and I've been seeing the same problem. Haven't found a solution to this problem (using Android auto with nexus 4 and lineageos).
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
EDIT 1: after some more testing You can go upto MAX 1600MHz (Your mileage may vary)
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
streetsmart999 said:
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
Click to expand...
Click to collapse
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Kukl said:
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Click to expand...
Click to collapse
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
streetsmart999 said:
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Click to expand...
Click to collapse
I try it immediately, I hope it works!
Thank you very much
Kukl said:
I try it immediately, I hope it works!
Thank you very much
Click to expand...
Click to collapse
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
streetsmart999 said:
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
Click to expand...
Click to collapse
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Kukl said:
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Click to expand...
Click to collapse
Humm... Anyway @1600 mine died at 30% .. So made it 1500 and past below 18% and Still running. So I guess 1500 is max I can go
Also Before coming this conclusion: I did the fowling
Charge 100%
Delete Batterystats.bin
Run this command from adb "adb shell dumpsys batterystats --reset"
And then Changed the CPU max (Please NOTE , Select "On Boot" to keep the same parameters). Once u change the CPU settings .. Reboot and see .. if its keeping the same settings.
Many thanks. I tried all of the the things you tried and setting the cpu max frequency is the only thing that worked.
I could get away with seeing it to 1600.
Deleting batterystats.bin does nothing https://www.xda-developers.com/goog...-battery-stats-does-not-improve-battery-life/
Now with a new battery, PureNexus Rom and your amazing fix my Nexus 10 is a thing of beauty again.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO..
Click to expand...
Click to collapse
Streetmart you absolute legend. I'd never thought I'd see the day my Nexus 10 would drain down to zero again. I tried 1600, then 1500, to no avail; then I said screw it I'll just go down to 1200 (with little hope of it working).
It feels so weird to actually have an internet “solution” work. I'm super happy. I didn't want to buy another tablet. I love this one and it worka perfect for what I use it for.
Thank you! :good::highfive:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Icetech3 said:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Click to expand...
Click to collapse
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Hez0 said:
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Click to expand...
Click to collapse
What a difference... i installed that a few days ago, and i haven't used my N10 much but on standby it's still at 99% usually it would be WAY lower.. i think that program did more than just lower the max cpu a little.. don't care though. the N10 lives on!!
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
I'm currently running at 1600 with this guy modified kernel and wow, besides no more suddenly shutdowns it runs very smoothly, it reminds me the pre-marshmallow age of this tablet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
Where are you finding these control settings to change?
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Der_Graf said:
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Click to expand...
Click to collapse
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
If i reduce the CPU speed from 1700MHz to 1200MHz I get to go down to 20% instead the N10 shutting down abruptly at just 30%
I do have a spare battery in the fridge for later on. Once I open up the N10, I'll see if there is a capacitor or two, that could replaced in the power supply area to possibly fix the issue.
Note:
1. On second full charge since lowering the CPU to 1200MHz the battery got down to 14% & I have decided to charge it instead of letting it die at some point at a lower percentage
2. I should have mentioned earlier, that I still use the original N10 battery & plan to replace the original battery with a new aftermarket battery later on if I need to.
3. I use the N10 in an air-conditioned room for no longer, than half an hour at a time only browsing & reading articles with a short 10min video from YouTube.
4. Before lowering the CPU clock from 1700MHz to 1200MHz, the tablet consistently has shut down abruptly, at 27-30% battery level to my dismay.
5. Tried complete battery drain / cache reset to 0% in Recovery mode & then fully charging it while shut down 3 times without success.
6. So far lowering the CPU clock has made a difference & for prof now I am evaluating the N10 battery capacity with AccuBattery.
7. I charge my devices at around 20-25% or higher up to 80% to prolong battery life using apk's to stop charging or alert me.
I have switched to the UNOFFICIAL Resurrection Remix for Nexus 10 (ResurrectionRemix-M-v5.7.4-20161208-manta) MM ROM after rooting my N10 (Danke schön Corinna ) & had to update the baked in Kernel Adiutor.
Installing from APKMirror the "Kernel Adiutor (ROOT) 0.9.73 beta (Android 4.0.3+)" has allowed me to lower CPU MAX Frequency and have it stick after BOOT!
com.grarak.kerneladiutor_0.9.73_beta-241_minAPI15(nodpi)_apkmirror.com
Ottoman Mint said:
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
Click to expand...
Click to collapse
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Der_Graf said:
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Click to expand...
Click to collapse
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Ottoman Mint said:
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Click to expand...
Click to collapse
Sometimes it shuts down at 20% and other times it won't. I'm almost pretty sure it doesn't have anything to do with advanced power settings or any kind of internal power settings with the kernel. There are no thermal configurations on this device and they don't add any drivers for it or support for it until much later versions. Heat seems to play a role especially down here Florida when outside. So far in my experience it's most likely to shut down at 20% if it's too hot and not likely to do so if it's been idle for a bit or not plugged in.
Sent from my Samsung Nexus 10 using XDA Labs