Alright, coming from WM way back to an iPaq, as soon as I got an android I got task killers, especially as I watched my memory go down to like 40 megs.
After reading I am deciding to remove any (excluding ZDBox) task killers that I have, and see if Android really does manage memory well.
I have to admit that when I did notice my launcher running slow, I would kill tasks and it would pick back up. Anyways....
I have one question - I am running Juice Defender, that doesn't kill tasks, just manages wifi, and the radio, right? Its ok to keep that going?
I am running a rooted TB with BAMF SoaB with GoLauncher as my home.
Any input on this would be appreciated!
JuiceDefender does no task killing, just deals w/networking as you said. The only reason a task kller would be necessary is a misbehaved app that wakes up often and burns processor cycles - Android reclaims memory when needed (a built in task killer, if you will). If you have a less-than-popular app, it might have such a problem, but popular apps get enough scrutiny that they should not be burning cycles and should not need to be killed.
That helps me, thx.
I completely agree for juice defender. It helps on "saving your battery", not on managing app on background.
You could try Advanced Task Killer. it's a good one. I used it on my I9000 when i had a Gingerbread rom and it worked great
v6supercharger,no need for taskkiller..
Sent from my LT18i
rashid.fairus said:
v6supercharger,no need for taskkiller..
Sent from my LT18i
Click to expand...
Click to collapse
So I have read your post about this v6supercharger (wouldn't mind a real one for my truck, another post)
You indicate its easy, but I have zero knowledge about this kind of stuff. I will be going over the instillation instructions, but want to be sure that if I screw something up in the setup, It will be easy (battery pull) to start over?
Also, I am running a rooted phone with a CPU speed setting, and have overclocked it to 1400, will this V6 do the same, or is it a completely different setup?
jerrya said:
So I have read your post about this v6supercharger (wouldn't mind a real one for my truck, another post)
You indicate its easy, but I have zero knowledge about this kind of stuff. I will be going over the instillation instructions, but want to be sure that if I screw something up in the setup, It will be easy (battery pull) to start over?
Also, I am running a rooted phone with a CPU speed setting, and have overclocked it to 1400, will this V6 do the same, or is it a completely different setup?
Click to expand...
Click to collapse
at the first time it maybe cause a bootloop(stuck),so pull out battery and boot again,so better not run it on boot,if its working(no bootloop) then you can set it to run on boot so you have permanent setup,and you can unsupercharger if you dont like it,it doesnt touch your clock speed,it just playing with ram and out of memory things,dont worry bout setting it,it will suggest for you..
http://forum.xda-developers.com/showthread.php?t=991276
Sent from my LT18i
Thanks, I will give it a go Monday, thats my best time when I have all day without distractions. Will report when I get done with it.
jerrya said:
Thanks, I will give it a go Monday, thats my best time when I have all day without distractions. Will report when I get done with it.
Click to expand...
Click to collapse
good luck,and make sure you made a backup..
Sent from my LT18i
Related
Firstly, sorry for posting a noob like annoying thread like this but I wanted to get opinions.
I'm off to Download festival tomorrow! So I'm hoping to install a ROM which has a very good battery life, turn off syncing, mobile network and pretty much everything else and try and get a decent way through the weekend with my phone.
Any suggestions on which ROM I should rely on for this weekend?
I would test some out myself but I am leaving tomorrow morning I don't really have much time.
Any opinions would be greatly appreciated!
Vanillaeclair 3.3 RC3 for me miminum 2 days working )
ITMASTER said:
Vanillaeclair 3.3 RC3 for me miminum 2 days working )
Click to expand...
Click to collapse
gotta agree vanillaeclair is one of the best ive used.. running for 8 hours today and only 2% down.. i know percentages are a bit deceptive im pretty shure it'll last me a few day.. although i dont use data, use wifi all the time
Put Juice Defender on too
Never used Juicedefender before, will it help at all if I just keep Wifi/Data/Sync off all the time anyway?
Just to support VanillaEclair 3.3
I've been running a hell of a lot of different rom's for months now and VanillaEclair has been fantastic for battery life since 3.0
Don't forget to install overclock widget so that you can underclock it when it's sleeping etc.
I also use 'Process Manager' which you can set to auto-kill background apps. Every little helps.
EDIT- oh, and keeping wifi/sync/data off will help a hell of a lot
Right I've gone with VanillaEclair then.
I've turned off syncing/mobile data/everything and I've used SetCPU to change max down to 518mhz.
I've never really been into using Task Killers so I am a bit concerned about using one. I already purchased Advanced Task Manager a while ago so I could use that. What kind of autokill frequency do you use and does it really make a difference? I see Task Killers as another thing running in the background..
I called Verizon today regarding my battery life (at work which I started today I get sh*tty reception which kills my battery in 4 to 5 hours--usually last a full 12-14 hours pretty perfectly). The rep that I talked to quickly realized that I knew what I was talking about tech-wise and thankfully didn't treat me like an idiot.
She said something that got my attention though: she said HTC recently (as in the past few days) released something to Verizon reps saying that Task Killing apps actually interfere with the system and code in a way that drains battery *more* on the Thunderbolt than any other device thus far.
Anyone else heard of something like this or have a reason why it would do this?
*edit* I'm looking for like a dev answer to this... How it interferes with the system? I've seen the threads that explain how it messes with the Activity code but it seemed like it was more than that for the Thunderbolt.
Haven't gone a full day with ATK uninstalled but I'll try tomorrow and see how it goes.
swimminsurfer256 said:
I called Verizon today regarding my battery life (at work which I started today I get sh*tty reception which kills my battery in 4 to 5 hours--usually last a full 12-14 hours pretty perfectly). The rep that I talked to quickly realized that I knew what I was talking about tech-wise and thankfully didn't treat me like an idiot.
She said something that got my attention though: she said HTC recently (as in the past few days) released something to Verizon reps saying that Task Killing apps actually interfere with the system and code in a way that drains battery *more* on the Thunderbolt than any other device thus far.
Anyone else heard of something like this or have a reason why it would do this?
*edit* I'm looking for like a dev answer to this... How it interferes with the system? I've seen the threads that explain how it messes with the Activity code but it seemed like it was more than that for the Thunderbolt.
Haven't gone a full day with ATK uninstalled but I'll try tomorrow and see how it goes.
Click to expand...
Click to collapse
they told me the same thing but not about the battery drain, just that it screws with the system
but on other phones (droid 1) they highly recommend using task killers.
obviously two different phones/companies, but still you'd think they say dont use them for all phones, not just certain phones, because most people feel they are useless.
But it hasn't screwed up anything that i've noticed, and my battery has actually improved since day one, so i think it depends on your phone. And i dont think my improvement is from task killers, i'm rooted and i think custom kernels and roms have helped increased battery life.
Id say whatever works for you do it, and dont worry about the task killers ruining you phone, but if you find out they are then dont use them.
good luck
I would guess that they'd negatively impact performance. The only reason you'd need a task killer is if you were on a 1.5-6 device. In all later version, tasks are managed natively as part of the core os.
One problem is with people using them to auto-kill apps far too aggressively. If you're constantly killing apps that are constantly re-launching (such as clock/weather/SMS/MMS/news/widgets/etc that tend to stay resident), you're going to end up up using a lot more processor time, and thus battery life, than if you just let the apps sit idle.
I heard that its because Android 2.2+ automatically restarts apps that you close and then it uses more memory to restart each time it is killed. There is a built in task killer in the phone anyways. No need for a secondary killer. But from my personal experience: yes I got worse battery life with task killer than without it. Although on my Droid x it was the opposite. Must depend on the phone
Sent from my ADR6400L using XDA Premium App
Trevlo said:
I heard that its because Android 2.2+ automatically restarts apps that you close and then it uses more memory to restart each time it is killed. There is a built in task killer in the phone anyways. No need for a secondary killer. But from my personal experience: yes I got worse battery life with task killer than without it. Although on my Droid x it was the opposite. Must depend on the phone
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Your explanation is off a bit but you get a C+ for the spirit of it.
In short, Android use your free memory to cache programs into using spare resources. ATK then removes these apps from this free memory, making it free again. Android then uses your free memory to cache programs. Then ATK. Then Android. Etc... See the problem? Slows down your system and wastes battery doing it. You are correct in that there is a built-in memory-freeing system that does this really when it's needed. There are ways to influence how aggressively it frees memory up.
The reason it helped with your Droid X was because of how pathetic Blur was. With custom roms that removed most of Blur, ATK hurt a lot there as well.
Sent from my ADR6400L using XDA App
Jaxidian said:
Your explanation is off a bit but you get a C+ for the spirit of it.
In short, Android use your free memory to cache programs into using spare resources. ATK then removes these apps from this free memory, making it free again. Android then uses your free memory to cache programs. Then ATK. Then Android. Etc... See the problem? Slows down your system and wastes battery doing it. You are correct in that there is a built-in memory-freeing system that does this really when it's needed. There are ways to influence how aggressively it frees memory up.
The reason it helped with your Droid X was because of how pathetic Blur was. With custom roms that removed most of Blur, ATK hurt a lot there as well.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
+1 thank you... didn't feel like explaining all that
one thing to add for all you wondering...ram will use the same amount of power whether it is full or empty so don't' worry about using up all your ram...the android os will kill off apps and caches as needed to keep you running fast and efficient. our batteries life sucks because we use our phones so much or because (like me) we run beta software with bugs.
i've tested numerous times and sitting idle overnight (about 8 hours) on 4g OR WIFI, i will lose between 4 and 6 percent.
Quit muddying up the dev section! This has nothing to do with DEV!
This should probably be in the general section, and yes active task killers will ruin your battery life, if you have it uninstall it. The only way you should ever force close running apps is with the app management built into the android system and thats only for rogue apps that never stop running.
Jaxidian said:
Your explanation is off a bit but you get a C+ for the spirit of it.
In short, Android use your free memory to cache programs into using spare resources. ATK then removes these apps from this free memory, making it free again. Android then uses your free memory to cache programs. Then ATK. Then Android. Etc... See the problem? Slows down your system and wastes battery doing it. You are correct in that there is a built-in memory-freeing system that does this really when it's needed. There are ways to influence how aggressively it frees memory up.
The reason it helped with your Droid X was because of how pathetic Blur was. With custom roms that removed most of Blur, ATK hurt a lot there as well.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
on droid x wit blur atk still hurt battery life. only worked on eclair.
One thing that I have encountered in supporting VZW technical issues, in addition to battery life, over-aggressive task killers, if not configured properly, can kill necessary apps. People call cause their alarm clock didn't go off, they didn't get text messages for 30 min to an hour, etc. Some of these programs *need* to run in the background.
Yeah from what I understand its not the phone but the os. On eclair task killers helped out . But froyo and gingerbread both take care of all of that in the back ground and using tk's affects the way the two os's are working. I was told all of this back on my Captivate and at the time I was hooked on task killers and Froyo leaks were just coming out. My batt life sucked and a dev some probably know , Designingears , explained all this to me and omg it was hard for me to take in and delete advanced task killer lol. But I did and have never looked back and it definitely improved my batt life. Now every now and then you just get a stubborn run away app that the os just can't stop, can't remember the app but theres a couple out there that take care of this and there not task killers. Me, I just reboot my phone every now and then and all is well .
Sent From My HTC Inspire 4G @ 1.5Ghz | [ROM] CoreDroid HD GB 2.3.3 V6.6
so from what I've learned being in the business for 6+ years. The task killers kill everything where android needs certain things to run so your system doesn't lag. That being said a lot of the manufacturer are including a task killer in there new roms to over come this issue. Example the new droid x 2 has a new task killer app. Motorola was the first to say to Verizon no task killing apps and now HTC follows. Wont surprise me with the gingerbread updates to android phones if you see more companies build task killers into their roms. I stopped using a task killer last week and battery life has increased. Just my thoughts and opinion.
bhowell423 said:
so from what I've learned being in the business for 6+ years. The task killers kill everything where android needs certain things to run so your system doesn't lag. That being said a lot of the manufacturer are including a task killer in there new roms to over come this issue. Example the new droid x 2 has a new task killer app. Motorola was the first to say to Verizon no task killing apps and now HTC follows. Wont surprise me with the gingerbread updates to android phones if you see more companies build task killers into their roms. I stopped using a task killer last week and battery life has increased. Just my thoughts and opinion.
Click to expand...
Click to collapse
I second that. When I bought my Thunderbolt the clown at the store told me to put a task killer on it. I did that it killed the battery...On Perfect Strom 1.4 I am getting over 10 hours with out a task killer. Not scientific but I consider 10 hours good for battery life on this phone
Day 1 when I bought the TB a HTC rep was in the VZ store and he was saying same thing then about task killers worsening battery life and performance
RandomlyWatts said:
I would guess that they'd negatively impact performance. The only reason you'd need a task killer is if you were on a 1.5-6 device. In all later version, tasks are managed natively as part of the core os.
Click to expand...
Click to collapse
exactly.. froyo and GB do the task management job well.. when I had my droid 1 running 2.0, i compared with and without a task killer, and battery life improved a little when I did use task killer. But then with froyo and above, it would actually make it worse to use one..
Me thinks that the phone processes is set up to where a simple task manger can kill them, thus messing with some essential processes. Which in turn, would make the phone have to use a little bit more juice to start the processes back up over and over.
Just my .02 o.o
Sent from my ADR6400L using XDA App
Atk initially "sounds" good because most of us use to windows OS. Atk would/could be of use if droids ran windows... Droid is based off Linux and if you read up on how Linux operates, there is no need to constantly kill apps when it doesn't draw on system performance while in the background. Where the problem is, is that some apps have permissions to chill in the background and by killing them and the system brings them back up, just to be killed again. Not gonna drag thus on because I'm typing on my phone, but atk's aren't necessary.
Sent from my ADR6400L using XDA Premium App
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol
Just got the rezound. I installed advanced task killer and normally it says 10+ apps are running, even ones i dont ever open. ill kill everything and they seem to open right back up. so pretty much when ever i app kill eveyrthing i get about 11+ apps killed. doesnt seem normal..
the apps it randomly opens are like pandora, block buster, slacker. ect..
LOL @ advanced task killer.
Sent from my ADR6425LVW using xda premium
That was going to be my first question. Why in the world are running that program?
I find ATK really helps save battery life a lot.
phio said:
LOL @ advanced task killer.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
EmerikL said:
That was going to be my first question. Why in the world are running that program?
Click to expand...
Click to collapse
+1 : D : D
Sent from my E10i using xda premium
what is so wrong with ATK?
iv been using it since my 1st android phone (htc hero) and its been amazing.
Jacrushar said:
I find ATK really helps save battery life a lot.
Click to expand...
Click to collapse
Take two placebos, and call us in the morning.
Warrior 3000 said:
what is so wrong with ATK?
iv been using it since my 1st android phone (htc hero) and its been amazing.
Click to expand...
Click to collapse
Back then it was necessary. But since what, Froyo, it hasn't been.
so what should i use?
The built in task manager.
Sent from my ADR6425LVW using xda premium
Or just let it do its own thing.
Sent from my ADR6425LVW using XDA Premium.
Don't need a task manager on Gingerbread and beyond. Just let everything be.
Don't even use a task manager, Android deals with apps in it's own ways, if you force kill them with a task killer, they'll be right back, ATK causes system instability.
Also, the 10+ apps are most likely bloatware and apps you installed that are scheduled to send/receive info intermittently, forcing the app to constantly open in the background for that purpose.
Sent from the resounding Rezound
These threads always make me angry because the people who post "ATK IS WORTHLESS" are just as ignorant as those who think ATK is a requirement.
99/100, ATK won't be necessary these days. Android has built in task management. ATK is really something that store reps were trained on because task management in Eclair was pretty horrible.
Think about it like this. Those 10+ apps are being shut down, then using extra CPU cycles to start up every time you kill them! That's going to kill battery faster than letting them live.
Since Froyo and beyond (meaning Gingerbread, Honeycomb, and Ice Cream Sandwich), ATK is essentially unnecessary. You can uninstall it and won't notice much of a difference most of the time. They've done studies and found on some devices, ATK will either improve battery or hurt battery by +/- 5 minutes (in other words, no battery improvement except possibly a negligible 5 minutes on average for a couple of devices). Search for the article on Droid Life if you're interested.
With that being said, ATK can still be useful. Did Angry Birds crash freeze on you and is causing your system to run slowly? ATK kill it. Is Facebook completely stuck because it's trying to find your location and you have 0 GPS signal? ATK kill it. Is Currents sucking up your battery because it's trying to download on a weak data signal? ATK kill it.
I haven't had ATK installed in a while, but what I do have is Watch Dog. Watch Dog allows you to set a CPU threshold. When certain apps start sucking on your CPU for extended amounts of time, it pops up an alert. From there, you can Ignore it, White List it, or Kill it. This way you're not just killing tasks for the sake of killing tasks.
If anyone is experiencing this problem, I hope the following steps may help.
I would like to express my appreciation to XDA members, who have commended and helped out with this. Credits go to @LordManhattan and @abuihsan . Many thanks for your help.
1/ Do a re-flash: I always thought my device was a c6802, after I flashed c6833, it helped.
2/ Do a factory reset/ Cache wipe/ Dalvik Wipe/ in recovery or in the phone settings.
3/ Install SD-Maid and clean the mess from the programs, also take a look at APPCONTROL to see which is running. You can freeze it here.
4/ Install Performance control to Underclock your CPU. Believe me, 1.7Ghz is far too enough for all the tasks you need.
5/ Use more pwerful tool, like Titanium Backup to stop all the backgound-running apps. You just need to leave the one which were in GREEN color.
6/ Use Wakelock Detector to see which apps get your phone out of deepsleep. Mostly they are Facebook and Messenger. My advice: Disable Facebook notice and if you don't use chat quite often, don't install facebook messenger.
Hope these help.
Personally I had tried a lot of methods, including checking the processes and re-insert the memory card but no such helps. Therefore, if you need any advice or any comments, feel free to send me an PM or reply here, I will gladly help you out, like what the community had helped me our of my situation.
Hi everyone,
Recently I just bought a ZU from a local vendor here. It runs 4.2.2 with no problem. However, I want to get rid of the *new system update* and I also want to use the xperia Themes, I decided to upgrade to 4.3.
My phone model is C6802, and I chose the file here : http://forum.xda-developers.com/showthread.php?t=2453921
The upgrade went through fast and smooth, as I had experienced in many Sony devices.
However, after getting to 4.3, I had noticed some problems as follow:
+ Heat: Device heats up very fast, even left alone. Just imagine you have the phone on 100% battery lying on your table, a moment later it heats up and the battery drops dramatically.
+ Battery drop: Just as mentioned above, the battery drops quickly. I do not expect extreme battery life on this device, but since 4.3, it is too low, I can barely make it to 6 hours without doing anything consuming battery.
+ Process: When checking the battery, I notice that most of the process that takes up battery is Android OS, which nearly 50-60%. I use the phone frequently to answer SMS and call, sometimes play games. I think that the most used applications should be the bad-ass screen?
I am running on the 14.2.A.0.290 with R4B.
Anyone had experienced this problem before, or know a solution to fix? Will clearing the Dalvik Cache help? I had re-flash several times but the problem is still there.
Many thanks in advance.
Click to expand...
Click to collapse
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
Sent from my iPad mini using Tapatalk HD
fjevel said:
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note:
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
First of all, thanks for your reply and suggestion.
I had tried to flash the roms multiple times, but the problem still exists. Furthermore, I even flash back to 4.2.2 and the problem is still there. The phone heats up slowly and battery runs out pretty fast.
I had installed the Wakelock Detector on my device and I will update the situation tomorrow, I will leave it there for a night and see the status tomorrow.
Did you wipe after updating? I had the same issue when i updated to 4.3.
Correct me if I'm wrong, but as long as he's been downgraded to 4.2.2 again, he'd have to wipe. At least that is how it was on my Xperia Z.
-KJ
this might not be related, but I've been noticing much worse battery life today than normal! i normally only drop about 50% in 24 hours, but today I've dropped 30% in just a few hours. Android OS seems to be doing it...
no real heat issue tho, maybe slightly warmer from whatever the OS is doing, but nothing too major. running stock rooted 4.3
had that on my Xperia Z on a 4.1 or 4.2 build (dunno which one). Sounds strange, but simply turning off the sync fixed the problem, give it a try :laugh:.
Hope it also helps on your XZU.
LordManhattan said:
Did you wipe after updating? I had the same issue when i updated to 4.3.
Click to expand...
Click to collapse
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
justsomebody said:
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
Click to expand...
Click to collapse
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app. I use GREENIFY and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
abuihsan said:
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app.and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
Click to expand...
Click to collapse
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
justsomebody said:
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
Click to expand...
Click to collapse
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
abuihsan said:
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
Click to expand...
Click to collapse
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
justsomebody said:
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
Click to expand...
Click to collapse
The thing is, you don't need a task killer/cleaner app. It was useful way back on Android 2.1/2.3, but you shouldn't use it at all on 4.0+. You're actually making things worse.
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
ij0rgei said:
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
LordManhattan said:
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
Click to expand...
Click to collapse
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
ij0rgei said:
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
Click to expand...
Click to collapse
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
LordManhattan said:
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
Click to expand...
Click to collapse
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
ij0rgei said:
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
LordManhattan said:
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
Click to expand...
Click to collapse
ok. so I haven't done anything at all to remedy the situation. I figured I'd ask about it before messing it up myself. I upgraded to .290 via pcc. it updated fine with no errors. once it was done updating, it was hot and battery was diminished. I had seen on another thread that most people had that happened so I didn't see it as an issue, just a side effect of the update process.
I have been checking back to see if anyone was having heating issues with 4.3 after the update and didn't hear about it until I had seen this thread. the OP stated he flashed .290 on his 6802 and is rooted. I am not, so I wasn't sure if the steps he was taking were the same given my 6833 being completely stock.
Sent from my C6833 using xda app-developers app