Hey all,
I recently noticed the weird core usage of my I9505. Sometimes when I start up the phone, all core are active at the lowest frequence (even when I'm texting or something). Even after for example, a half hour deep sleep. And when I restart it, it's just using one core (when I'm just texting or something), sometimes a second, but then it goes back to using one core. Also, if it's all looking good, it can suddenly start to use 2 cores and never go back to using one. Even through and after deep sleep.
I'm running 4.3 XXUEMI8. Anyone knows if this is normal?
greetz,
swa100
By the way: I'm using greenify, so no bull**** apps are running in the background. I've also deleted all the bloatware. And sync is disabled.
Related
I wasn't sure where to put this but any help would be appreciated. Lately my phone gets extremely hot, I'm running froyo 2.2 latest built. And I'm running launcher pro home replacement replacement with only 5 screens. And I have battery indicator telling me right now that the temp of my phone is 105.1F. How do I find out which app(s) is making my phone heat up?
Try looking at what's eating your battery then go from there.
It shows my display at 86% and android system at 8% those are the highest using battery...my backlight is at 50% brightness...would Anyone recommend having that set to auto brightness?
i have my n1 set to auto and it still gets pretty hot. i have not had any issues with it over heating though so maybe give it a try. also, are you running a task killer? ive got security set to low, and it auto kills apps every 30 minutes or so. it seems to help out a bit, saves battery too.
I've had this problem since I updated to Froyo.
After a while, the data connection seems to be used -constantly-
and I really mean -constantly-, I'm also running Launcher Pro - So maybe there's something there?
As an earlier post said, the Screen appears to be the top "battery" user when looking at the battery stats (I've found these to be EXTREMELY unreliable though )
My screen is set to Auto, so I doubt that's where the problem is.
Also, in my case, it's the very bottom of the phone that gets hot (I believe that's where the antenna / actual chipset for the radio is?)
One thing I've found that "helps" so far, is to disable account sync, then re-enable it. Apparently that's what's causing an overuse of 3G for me. This only helps in some cases though.
Usually I just turn off data completely for a few seconds and re-enable it.
Any "tips" on what could be using that much data all the time (Maybe it's not even using the data, but just somehow trying to keep a single connection alive?) would be greatly appreciated. I'm honestly not sure here!
Any ways, that's what I've found out "so far".
/T0yK4T
Thanks for all the feedback and tips I will try all these things. But I agree and ever since I upgraded to froyo it gets extremely hot. And I'm running launcher pro but I tested it with the stock launcher and still gets hot....who knows....
I'm having the same issue on my nexus. I have a custom rom with stack kernel and ADWLauncher with 3 screens and brightness on auto.
What should i do?
Sent from my Nexus One using XDA App
Run System Panel, it'll show you any apps using CPU, and network stats.
Something is clearly wrong with your phones/config/cache/something, my Nexus One stays ICE COLD all of the time even with K9 mail with push IMAP, weather syncing, GPS uploading to my website every 10 minutes, etc..
Aside from being able to Wirelessly Tether my 3G connection from my Vibrant, I wanted to also control my CPU speeds. But with SET CPU, I tend to come across a particular problem. I would underclock to 100000 (min&max) with the screen off, but as a result, the screen won't turn back on and I would have to take the battery off and restart my phone. Clocking it to 400000 (both min and max) screen off leads to the same problem. Is anyone else going through the same situation? If not, what are you setting your CPU to, in regards to both screen on and off?
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
lqaddict said:
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
Click to expand...
Click to collapse
Yeah I have all my profiles set to conservative. Do you guys think it has to do with the priorities, cause I have all of them set to 100.
It could, since there is no telling how to prioritize the settings, hardware/software might get confused.
you know I just noticed I got the same issue, sort of.
I have multiple profiles setup, and one is for charging via USB 800max/100min.
If the screen is off (400max/100min), and I connect the USB cable, guess what happens, three finger salute gets it back, hmmm.
OK I got it working for those who are having the same problem as I. All I did was I made my screen off frequency 200max/100min. For both charging and battery use, I have my cpu set at 1000max/800 min. It works flawlessly and I am noticing an increaSe in battery life...
Sent from my SGH-T959 using XDA App
OverClock?
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Halieus said:
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Click to expand...
Click to collapse
we need a kernel that will enable it. its apparently not possible on the stock kernel...
I have been having the exact same freezing issue when the screen times out, I'm unable to revive the phone without pulling the battery. I have tried many different setting in Setcpu including those posted here. I finally just uninstalled it and everythings right again. Best to avoid this app for now.
Hey man i did that and i still did not work any other way to set it up.
Vibrant wont come out of Blank Screen
I used Set CPU and put it to the max 1000 and then the max on the other readings it forced closed and after the tmobile and Galaxy animations it goes to a blank screen.
Yeah, I uninstalled it after a week because it was just too unstable. I was getting freezes several times a day, which is unacceptable. Other people might have better luck, but my phone did not like it at all.
So far the only way I can get the program to work 100% is to not have any screen off profile. If I just set it to 1200 max - 200 min / conservative it works fine. Yet once I use profiles and screen off at 100, 200 or 400 it won't turn back on. Every morning it's the same thing, battery pull.
I have similar problem. As long as I am not using "Profiles" at all it is fine. Playing with profiles setting for a while, but not being able to make them 100% stable.
Another thing, if your screen does not come on, you don't have to pull the battery out. Just keep holding on/off button for 5-7 seconds, it'll reboot. It's not a complete freeze, I believe only display system (whatever it is) fails.
Stuck at Recovery Mode
Guyz,
I have firetrap sugar on Spice Mi300. Installed Set CPU.
Tried entering the recovery mode, the phone gets stuck at 1st screen with a line "Enter recovery Mode" displayed on top.
Please help.
Im using current widget to record my battery consumption during standby and normal use.
Im using SetCPU with 988max/245min for normal, and screen of 245min/max, and battery <30% at 614max/460min.
Also set Taskiller to kill all apps when I turn the screen off.
Autokiller set to optimum (40,50,60).
Turned off htc sense in WM, and boot up haret when keypad lights are on.
Recently changed my WM rom and radio from ChuckyROM lite to stock 3.14, and radio from 2.12.50.02 to 2.15.50.
Android rom is NexusHD2 v1.6.
I found that I can get my battery current to be 3-7mA at standby, but heres the problem! It will only stay at this current for a while before reverting to 40-70mA as it used to be! This is very annoying as you can tell it saps the battery like crazy. In addition when using the phone normally with wifi on I can expect 250-300mA which I think is a bit high. Playing games gets me about 400mA. These effects happen before and after getting Taskiller.
What else have I got to try!?!?!! Please help!
I've had this problem too - And i've found that switching Bluetooth off and on again will stop it for awhile.... But i'm using MDJ's S4 Kernel, and haven't seen this issue for a little while now.
The biggest issue i've always had is every minute I have 4-8mA, but every so often it'll jump to 150mA+ for a minite or so.... At first I thought it was the weather updating or email syncing, but this drain is happening completely at random....
It's got worse since using MDJ's S4 though !
Yeah I forgot to mention I was using MDJ's S4 kernel. I have exactly the same problem as you as well, the mA will jump randomly to mid 100s, I've turned auto sync off and everything!
I had the same experience with this kernel. Randomly, it would drain 160mA with brightness at min, wifi and 3g off, sync off. I'm not using any setcpu or killers. Hopefully this will be resolved with the next version.
hookguy said:
I've turned auto sync off and everything!
Click to expand...
Click to collapse
I've got sync on... But still happens with me - So can't be anything to do with syncing.
I also have 3G permanently off, but polo735 is also the same, and his still jumps up !
I first thought it was 3G, as in my house, i'm on the edge of 3G reception, and it quite often switches at random between 3G and GPRS, so I have it permanently GPRS. No difference
I've managed to get a reasonably good battery life by changing to shubcraft 2.0 and upgrading my SD card to a 16gb class 6. Previously had a 2gb now I'm getting 3-12ma on standby - not too bad.
Sent from my HTC HD2 using Tapatalk
Hi all,
I have a question about this battery life.
With the latest version of Android builds, do we really needs CeT CPU ?(http://forum.xda-developers.com/showthread.php?t=505419), Or the battery drivers allready do the same job that this Cet CPU?
And, the most important, do you know if we will need it for the Nand, which seems to be coming quite soon...?
It is claimed that you don't need set CPU for the newer builds but I still use it just in case.
Also when nand gets finished you should still use set CPU because it helps maximize the battery you've got.
Sent from my HTC Desire using Tapatalk
Yes I think that there still might be a little difference, I nearly stay the entire week end with my battery, for the first time (without using it to much)
This is a problem that has plagued every Android device I've owned. Whenever I turn the screen on to do something, the CPU usage shoots way up. These insundry background processes don't seem to be run using "nice" or "cpulimit," and so even with four cores on the Nexus 7, the GUI lags quite a bit. If there's any time apps should NOT run background processes, it's the moment that the user wakes up the device.
Has anyone addressed this problem on their tablet? Which system event would be relevant, if I wanted to use an app like "autostarts" to try and fix this?
So, as the title says, there may be a way to prevent your device from freezing due to unlocked bootloader. Here are 2 things I've discovered:
1) Most of you may already know of this: If you switch off cores 3 and 4 of your CPU in the app Kernel Adiutor you can prevent the freezing issue. However, you lose half your CPU power, and if you leave it that way for long you can't switch those cores back on for some reason, and you'll have to reboot your device(else your battery will drain out if left as is, from my experience), so it's quite a cumbersome task.
2) If you play games that require little more than average ram and CPU power(even games like hill climb) your phone won't freeze while playing. I play this game called Vainglory, and after having played for over 10 hours, I can say for sure it didn't freeze even once.
From these two things I can draw up a vague conclusion that the phone freezes when the CPU isn't doing anything much. When we switch off 2 cores, the workload increases on the CPU, this making it busy(which also leads to quick drain). Same goes for gaming.
So how do we work on that? I'm not sure. Anyone have any ideas? Maybe someone can create a kernel compatible with RR and other cm13 roms which has what's needed. Or maybe try a different CPU governor? Well, just wanted to put it out there.
I tried all what you're trying to do and I understand that. The thing is that it will freeze no matter what.
Of course you can try but don't expect too much.
Goodluck!
I am facing this same issue suddenly
there is no connection between ifwi and cpu core
paktepu said:
there is no connection between ifwi and cpu core
Click to expand...
Click to collapse
Who said there is?
Another thing I found:
When you use kernel adiutor to switch off cores 3 and 4, and use your phone normally, the instant when your phone would have frozen if it weren't for the app, is when your phone gets much slower suddenly. At this point, you'll no longer be able to switch those cores back on, and only a reboot will resolve that.
I've mentioned this so-called "method" of preventing Z5 freeze long ago. I can confirm that switching off cores 3 and 4 somehow halts the phone's urge to freeze. I could've lived with limiting my "power use" as I'm not really a fan of entrusting your phone with large tasks. However, what turned me off was that disabling either one of cores 3 and 4 also disables the camera somehow (Ring a bell, Z5 users who lose their cameras whenever their bootloaders are unlocked?)
No one really replied with certainty back then and up to now, that thread is still collecting cobwebs.
Question: is battery drain a characteristic of disabling cores? I disabled only core 4. Cores 1, 2, and 3 are up and my ROM (Lineage 14.1) runs perfectly without freezing.