Database Users

Alarm woes with CM 5.0

Since no one replied to this message in the official CM 5.0 thread. I have decided to create a new thread and hope to find a solution to this problem.
My alarm clock would stop working randomly ever since I flashed to CM 5.0, from Beta 4 to 5..2, the problem persists. If i set an alarm that is about one hour from now, it would go off. But the real alarm I need which is supposed to go off at 8 am in the morning never goes off. Anyone had similar problems? I read Cyanogen's warning about the alarm clock problem. But seems he's just trying to remind you to reset your alarm after flashing to CM. Unluckily, I've reset my alarm numerous times and it never goes off in the morning.
Anyone can give me a hand? Thanks in advance! Overall, CM is a great ROM which gives me the option to use open vpn, which is vital for me since I'm living in China behind the GFW.

Are you by chance using any taskillers?

I do use a task-killer program. But I always keep the clock app on while i'm sleeping to try to make sure the alarm goes off on time. But it never does in the morning.

Don't use task killers on the N1, there really is no need.

cyanogen said:
Don't use task killers on the N1, there really is no need.
Click to expand...
Click to collapse
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.

Paul22000 said:
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Click to expand...
Click to collapse
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.

cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Click to expand...
Click to collapse
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?

Paul22000 said:
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Click to expand...
Click to collapse
I think there is likely one or two specific misbehaving applications that are giving you trouble, rather than the way the system works as a whole, thats all.

I think what Cyanogen is saying is that android does not handle running processes the way other os's do They have a lifecycle that is non-obvious to someone just looking at a process list. If you insist on killing tasks outside of the activity/service lifecycle they you _will_ get service failures (like the alarm clock) its up to you what you value more.

I have not installed any sort of task manager (outside what's in astro but I don't use it) and never see any noticeable slow down.

Anyway - back on topic.
Yes I have the same issue, never had it before.
Since flashine 5.0.2 my alarm doesn't work in the morning.

The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
Click to expand...
Click to collapse

I would have to agree with Cyanogen on this one. When I first got my N1, I looked towards task killers to help alleviate slowdown, but in the end, I think it's just the placebo effect in a way; you did something to try to solve the problem, and so therefore you perceive a difference.
In other words, task killers aren't needed on this beast of a phone. As for battery life (if that's an issue), look into SetCpu.

Thanks for the reply Cyanogen. I think not using task-killer, or at least not killing the clock app got my alarm working this morning. But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data. When I'm on wifi at home, I don't worry about that. Thanks again.

Same problem. Don't use taskkillers, flashed last CM last night and didn't wake up on time this morning - alarm didn't work, thought I checked that clock icon was on place on notification bar

amwayorlando said:
But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data.
Click to expand...
Click to collapse
Have you thought about using something like APNDroid or Toggle Data, to just switch off the cell data when you don't want to use it?

Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).

bofslime said:
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
Click to expand...
Click to collapse
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel

wesbalmer said:
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
Click to expand...
Click to collapse
This has basically been discussed into the ground. In my eye's, its a fight vs what I like to call "Windows XP mentality", and that there was benefit on phones like the G1. With the copious amounts of memory on the N1 and droid, they cause way more harm, and immeasurable good (if any).
Summary thread: http://forum.xda-developers.com/showthread.php?t=627836
I've linked to quotes from others.
Threads/posts of interest: http://forum.xda-developers.com/showthread.php?p=5494890#post5494890
And: http://forum.xda-developers.com/showthread.php?p=5298630#post5298630

Well, this discussion is very interesting, but lets return to our problem with non-working alarm.

auto killer preset or custom settings

Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.

I use either the aggressive or custom depending on the Rom honestly. DC ROMS= Aggressive. FRESH ROMS= strict. and all others = custom
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

I have the damagecontrol rom and I dont know if it came with auto killer or what...I restored my titanium backup and all i know is i dont have it now...is there an apk floating around for it?

Try the market

I thought it was a custom xda application. I didn't see it in
the market.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?

I used either the aggressive or strick on Fresh 2.0d. So far everything is running the smooth and fast. This the way HTC hero should have come out of the box.

What does each preset do? Is this for speed or battery life or both?

flammenwurfer said:
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
Click to expand...
Click to collapse
Damn. I wish Homerun Battle 3D would run great for me. Problem is I get crummy service at work and with it going in and out of 1x and EVDO, causes the game to lag.
I have noticed sometimes on first opening HRB, it force closes but it always opens the second time.

james33440 said:
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
Click to expand...
Click to collapse
i'm running aosp 1.6 from gbhil and i used custom autokiller settings.
the way i see it they made these phones with all this ram may as well use it, what good is it to have all this free ram?
1536,3072,4096 (all default) then hidden app is 7680. content provider is 8960 and empty app is 10240. i normally run around 40-45 free ram thats about where i like it. the phone still runs fine all the way down to 20mb free but any less than that it starts going downhill.
so, im MB my settings are 30 then 35 then 40. runs great!

yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.

flammenwurfer said:
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
Click to expand...
Click to collapse
Well, mine actually lags on offline play too. As long as the phone isnt switching back and forth, it runs smooth.

How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail

vedwed said:
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
Click to expand...
Click to collapse
Using command prompt (adb)
adb shell
# rm Autokiller.apk

troyboytn said:
Using command prompt (adb)
adb shell
# rm Autokiller.apk
Click to expand...
Click to collapse
Ohh thanks much appreciated.
I did not try that way, I figured if it couldn't be done in freshkitchen then it was just built into the rom. Thanks much again

Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.

Sawawa said:
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Click to expand...
Click to collapse
Autokiller does have a built in task killer but its real use is to tweak memory settings at boot and then shuts itself down (so Android can take care of the rest). So, in reality it is not really a task killer per say.

Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.

Sawawa said:
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Click to expand...
Click to collapse
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that

Jus10o said:
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Click to expand...
Click to collapse
Either way it should be a choice made by the USER not someone who decides what I need or do not need on my phone. What I choose to have running or not running, there is no need for this garbage for the average joe who just wants something that does not look and feel like Sprint garbage. If its such a great and useful thing put it on the market and let users have a choice.

Android.process.acore draining EVO battery fast

I've got two HTC Evo's. One lasts for 24+ hours on a single charge, the other lasts 3-4 hours tops. They are both have been running Fresh 0.3 until yesterday. I upgraded one to 0.5 and the other will remain at 0.3 until today. The one still running 0.3 has terrible battery life. I've been running system panel on both and saw that Android.process.acore has kept the CPU ramped up for hours on end, the battery is always 40C+ and when I checked on it this morning it had been streaming 200kbps of data nonstop through the night. There are no market apps installed on this phone except for Advanced Task Killer, GScript Lite, and System Panel. There are no apps installed from untrusted sources.
Anyone know what Android.process.acore does exactly, and why it would be streaming data all night long? System and System Processes also have much higher CPU utilization on this phone as well. I've tried reinstalling Fresh, rebooting the phone, killing absolutely every task ATK will let me, etc and nothing seems to stop the flow of current. Any help would be greatly appreciated.
This happened with the stock software as well. One phone always lasted longer than the other. However, I'll let you know if Fresh 0.5 changes anything.
Thanks everyone.

I upgraded 2 days ago. My phone was always stock. Yesterday I took lots of video, like 15 mins or more, and battery, and GPS, and Google sky. A friend of mine invited me to his boat and we were on the river for almost an hour. The battery was still on the green side. I definitely noticed some battery improvement after the software upgrade. When I watched the video on the computer I learned the hard way that there are not vertical HDTVs.

Streaming data all night?
We may just have the first Android Trojan lol.
Sent from my Evo 4G

ejittles I think what you're seeing is a sync-loop, likely with facebook or exchange. This was supposedly one of the things addressed in the recent OTA update.
Try removing and re-adding any accounts you're synced with, disabling background data, etc.

scriptx said:
ejittles I think what you're seeing is a sync-loop, likely with facebook or exchange. This was supposedly one of the things addressed in the recent OTA update.
Try removing and re-adding any accounts you're synced with, disabling background data, etc.
Click to expand...
Click to collapse
Brilliant Scriptx, I'll bet that is exactly what it is. I'm guessing its the exchange server. I will give that a try when I get access to that phone tonight. Will keep you posted. Thanks a ton.

HELLO
scriptx said:
ejittles I think what you're seeing is a sync-loop, likely with facebook or exchange. This was supposedly one of the things addressed in the recent OTA update.
Try removing and re-adding any accounts you're synced with, disabling background data, etc.
Click to expand...
Click to collapse
im with Him i also use shortcuts to turn on and off the internet (mobile) and i also use airplane mode when i don't what any one to call me my battery lasted MORE than 19hr and 31 min and i was using it downloding app, giving files, i saw some videos well you know the thing that you do when you brag about your phone. i am in the ARMY, so alot of people were looking at my iphonekiller (EVO) and wile some friends with evo battery already gone.... mine lasted 19:31 y lasted 24 before some sleep XD ( i have no ATK not needed for battery life)

Do you have a lot of contacts? On my Evo I have my personal gmail which only has a few hundred. On my Hero I have my developer account linked up which has thousands. During sync it isn't uncommon to see:
Code:
SyncManager(): canceling and rescheduling sync because it ran too long.
It will do this over and over and over again non-stop until it finally goes through. Secondly as was already mentioned is something like Facebook/Twitter/Friendstream. I personally only have twitter setup (and I use the official Twitter app for that) but again while testing on the Hero I found that the way Friendstream (and possibly facebook overall, and peep too but I'm not sure) gets updates is it checks the current status on EVERY SINGLE contact of yours. This of course is a huge battery drain.
The reason that I make the comparison with the Hero by the way is the software is basically identical. They are definitely forked off the same branch at HTC. So any problems on the Hero are likely the same on the Evo. The reason I don't have answers for you from the Evo side is because I use it as my personal phone and I don't have much on it.
You may also want to see this post: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
There is a chance that your phone keeps killing off background processes while they are trying to do stuff, so then they turn around and run again, then get killed again, and again. Automated task killers are the devil. The only way I recommend using a task killer is the same way you would use task manager or top in linux. Just to kill off the random zombie process that may be causing you issues.

flipzmode said:
You may also want to see this post: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
There is a chance that your phone keeps killing off background processes while they are trying to do stuff, so then they turn around and run again, then get killed again, and again. Automated task killers are the devil. The only way I recommend using a task killer is the same way you would use task manager or top in linux. Just to kill off the random zombie process that may be causing you issues.
Click to expand...
Click to collapse
Flipz,
First of all thanks for the great work on Fresh Evo. Secondly, I only use ATK at startup to kill any processes that are set to start on boot that I don't care about. It's not set to autokill or to start automatically. I kill ATK when I kill everything else.
I think it has to be friendstream because I only have a handful of facebook contacts and the other phone has over 300 facebook contacts to deal with. Thanks for pointing me in this direction. I'll have facebook turned off on that phone and see if that makes the difference.
That particular phone is only set to receive email via exchange while mine syncs all of my work stuff via exchange so I don't think that is the problem. That just makes me suspect friendstream even more.
*EDIT* Also, I hope that ATK sends a sigterm to these processes and not a sigkill? Or is that not an option w/ the VM? I'm not too familiar with the internals on android atm. Haven't had time to play with anything due to work.

ejittles said:
I only use ATK at startup to kill any processes that are set to start on boot that I don't care about.
Click to expand...
Click to collapse
Do yourself a favor and go grab Autostarts (autostarts not autostart) from the market instead. It will be the best $0.85 you've ever spent on an app. It lets you control every single onEvent trigger in Android, preventing the applications from starting in the first place.

flipzmode said:
Do yourself a favor and go grab Autostarts (autostarts not autostart) from the market instead. It will be the best $0.85 you've ever spent on an app. It lets you control every single onEvent trigger in Android, preventing the applications from starting in the first place.
Click to expand...
Click to collapse
haha did you do that conversion for me from EUR to $ or is there a way to set a currency in the market app? Downloading it now. Thank you sir! The Evo has a great community here on XDA and I look forward to contributing when things settle down at work in the next few months.

ejittles said:
haha did you do that conversion for me from EUR to $ or is there a way to set a currency in the market app? Downloading it now. Thank you sir! The Evo has a great community here on XDA and I look forward to contributing when things settle down at work in the next few months.
Click to expand...
Click to collapse
I'm just smart. haha j/p. When you actually click on buy in the app it will show you the USD price. That's where I grabbed it from. I did buy it for my Hero over 6 months ago just so I could deconstruct it though and I knew it was under $1. lol

Fresh 0.5.3 and the disabling of friendstream has the second phone performing great. Battery lasts 24+ hours now. I suspect it was friendstream. Thanks for the help.

I had this exact same issue and with system panel's help I was able to determine that Facebook for Sense was causing the problem. I turned off FB's auto-update and the problem went away completely. After the OTA, I am able to turn auto-update back on without issue.

started to get laggy

When I loaded my phone up like my N1 it started to get really laggy so I download minfree and setcpu and now it's a bit better
the stock linpack for me was 5.9 and when used setcpu and put it on ondemand it went up to 9.1
Samsung hurry up with Android 2.2 PLZ

are you using any profiles or special set of rules that you could share?

SetCPU will constantly crash and restart the phone, not completely it seems but I uninstalled and got a refund.

siberslug said:
When I loaded my phone up like my N1 it started to get really laggy so I download minfree and setcpu and now it's a bit better
the stock linpack for me was 5.9 and when used setcpu and put it on ondemand it went up to 9.1
Samsung hurry up with Android 2.2 PLZ
Click to expand...
Click to collapse
My Vibrant is stock with all my apps loaded, and my linpack scores are in the 8's.

same here linpack in 8.1-8.4 and quadrant around 890.
Not yet rooted, two widgets, live wallpaper, 20 additional apps.

heygrl said:
SetCPU will constantly crash and restart the phone, not completely it seems but I uninstalled and got a refund.
Click to expand...
Click to collapse
Did you have it set to ondemand? The dev has stated that it works on the Galaxy phones if it's set to conservative. I've had it running on conservative for at least 4 hours now with no reboots. http://forum.xda-developers.com/showthread.php?t=727006

jblade1000 said:
are you using any profiles or special set of rules that you could share?
Click to expand...
Click to collapse
I had it on ondemand but every time the screen was off for more than 10 min the screen would not come back on.
I uninstalled it and everything was fine, then I reinstalled it and left it on conservative but adjusted the speed to 400 min -1000 Max 20-100% and 100 min -400 Max 0-20% and it works fine.
I also notice that this phone runs way more apps in the background than a N1, the N1 runs 28-35 apps in the background before the system starts shutting things down and this phone runs 50+, the last time I counted after bootup it was at 59.
So I started using an app I bought like 1 year ago, Taskiller Pro and set it up for autokill when screen is turn off and my phone works great.

SykesAT said:
same here linpack in 8.1-8.4 and quadrant around 890.
Not yet rooted, two widgets, live wallpaper, 20 additional apps.
Click to expand...
Click to collapse
Linpack 8.4
Quadrant 806

siberslug said:
I had it on ondemand but every time the screen was off for more than 10 min the screen would not come back on.
I uninstalled it and everything was fine, then I reinstalled it and left it on conservative but adjusted the speed to 400 min -1000 Max 20-100% and 100 min -400 Max 0-20% and it works fine.
I also notice that this phone runs way more apps in the background than a N1, the N1 runs 28-35 apps in the background before the system starts shutting things down and this phone runs 50+, the last time I counted after bootup it was at 59.
So I started using an app I bought like 1 year ago, Taskiller Pro and set it up for autokill when screen is turn off and my phone works great.
Click to expand...
Click to collapse
great, thanks for the advice!

Yesterday and continuing to today my Vibrant has really started struggling. I have tried a couple of different task manager's and task killers and it is still very slow. I have also uninstalled setCPU and still nothing has changed...

jblade1000 said:
great, thanks for the advice!
Click to expand...
Click to collapse
No problem

zenlakin said:
Yesterday and continuing to today my Vibrant has really started struggling. I have tried a couple of different task manager's and task killers and it is still very slow. I have also uninstalled setCPU and still nothing has changed...
Click to expand...
Click to collapse
Find out how many apps are running after a reboot and find out what services each of those apps are accessing.
If you see a game or say a pic editor that is accessing a service it does not need like gps or anything like that delete it and find something similar.
I'm finding that these apps that are accessing parts of the phone they do not need and sending your personal info to the developer and when you get a bunch of these types of apps it puts a huge strain on your phone.
Also download a task manager that kills your selected apps when the screen turns off, just remember to setup an ignore list and include all the systems services and launcher in that list or your phone will freak out.

heygrl said:
SetCPU will constantly crash and restart the phone, not completely it seems but I uninstalled and got a refund.
Click to expand...
Click to collapse
You know SetCPU is a free download on the XDA forums right lol
The one on the market is the Donate version so you basically donated to Iforgethisnamewhomadesetcpu and then took back your donation heh.

It wouldn't install for me so I decided to try it. It's only $2

I'm on day 3 and haven't gotten any lag yet....

Started seeing lags as well
The G1 was very laggy. This phone has no reason to be. It started out great as stock. But once I loaded up my normal apps, it's just started getting very sluggish. It does it in fits and starts - except for certain actions like going to the settings page of the Dolphin browser and exiting the Dolphin browser, or getting the task list of . Those are always sluggish. I also switched the 2GB Micro SD card to a 4GB class 4 MicroSD card and transferred Avatar to it. It has nothing else on it.
I'm going to start deleting software one by one and see what's causing this. But I'm not sure if it's any one software or just the fact that I have some 37 apps loaded.

i am having lag specifically with the stock email app for my exchange account.
my inbox will take sometimes about 5 to 10 seconds to load (shows black screen) and then many messages will be blank for them to load which is typically about 5 seconds.
randomly, some messages load fine. big or small.
in a related issue, i have had various events on this phone completely crash it and the os started over/home screen reloaded.

I stopped using a task killer and I've stopped having issues.

os2baba said:
The G1 was very laggy. This phone has no reason to be. It started out great as stock. But once I loaded up my normal apps, it's just started getting very sluggish. It does it in fits and starts - except for certain actions like going to the settings page of the Dolphin browser and exiting the Dolphin browser, or getting the task list of . Those are always sluggish. I also switched the 2GB Micro SD card to a 4GB class 4 MicroSD card and transferred Avatar to it. It has nothing else on it.
I'm going to start deleting software one by one and see what's causing this. But I'm not sure if it's any one software or just the fact that I have some 37 apps loaded.
Click to expand...
Click to collapse
My G1 (albeit with a custom rom and no bloat) was actually more responsive than the Vibrant I used in a T-Mobile store. Which is kinda funny because the guy working there was like "Hey how come your G1 is faster".
And then I went into the internet browser and my G1 performance fell to **** when scrolling through pages.
On topic: Try clearing your cache with the likes of CacheCleaner. It usually helps my G1's performance, dunno what it'll do to the Vibrant.

heygrl said:
I stopped using a task killer and I've stopped having issues.
Click to expand...
Click to collapse
What task killer were you talking about ?
I use Taskiller and Minfree and my phone will not even work without them.
If you don't set Taskiller up properly it will cause more problems than you have, YOU HAVE TO setup the ignore list on ALL system apps and services or your phone will go nuts.

SetCPU and Autokiller

Hey all,
Sorry if this has been answered/asked already, but is there a way you can prevent SetCPU from getting killed by AutoKiller? I have the autokill-profile in AutoKiller set to "Default", but the system assigns SetCPU an OOM value of 11-14, which is the highest value for getting killed (essentially regarding it as extremely non-important). How does one PERMANENTLY set SetCPU on the "Do-Not-Kill List"?
Thanks in advance.
PS: I'm running KaosFroyo v35-1 and so I can't uninstall Autokiller.

Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo

Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
Lol...funny stuff
As for OP you can uninstall autokiller if you want too...just look up how to remove apps through adb or terminal on phone.

Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.

"Practically" is not what he asked for. What he asked for is a permanent solution.

tyler1524 said:
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
Click to expand...
Click to collapse
That only works for about 3 minutes, until the system automatically increases the OOM value back to like 12 or 13.

I don't understand... even when I have it set to system default, after a while, it still kills it. So that means, even if I were to uninstall Autokiller, the SetCPU would still be killed after a while?

Doesnt matter if its killed. Its android, itll come right back

Nikolai2.1 said:
Doesnt matter if its killed. Its android, itll come right back
Click to expand...
Click to collapse
That's the problem. SetCPU doesn't.

Acrono said:
That's the problem. SetCPU doesn't.
Click to expand...
Click to collapse
I check my processes constanly and i dont see it going away. Maybe im wrong

Maybe Autokiller is correctly determining that SetCPU is consuming more power and Country cycles than its providing. I've certainly found that to be the case with Kaos Froyo
-------------------------------------
Sent via the XDA Tapatalk App

I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
-------------------------------------
Sent via the XDA Tapatalk App

Nikolai2.1 said:
I check my processes constanly and i dont see it going away. Maybe im wrong
Click to expand...
Click to collapse
It's always killed after 10-15 minutes, even on the default setting. If I set it to aggressive, immediately after it goes into the background, it's killed within a matter of seconds.

paulbonner said:
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
Click to expand...
Click to collapse
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....

Acrono said:
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Click to expand...
Click to collapse
Ocd to 710 by default
Edit: I've had the best results ditching setcpu and using the collin_ph script, just btw

I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict

The real and best answer I have for the first post (and what I do, and advise everyone I am around to do)
Stop using Autokiller.
Android does a great job killing processes.
Most users use 4-5 apps constantly throughout the day, and if the few most commonly used ones stay in memory more often than not, the phone is FASTER, as a result of calling up apps instead of having to completely relaunch them every time.
YES, using autokiller to adjust your memory settings can help if you are normally running process-intense apps in the background (like I sometimes run a VNC for work that will chew up some processor time if I just hit 'home' when I'm done instead of killing the task, or sometimes a small game that you figured was not in memory anymore, is still chewing up processor time).
BUT
That is what, and only what, I use a task killer for. I open up Free Advanced Task Manager, kill my background process that I don't want running, and move on with life.
9 days out of 10, I don't use a task killer, and I NEVER use auto killer.
If you want to keep your phone faster than not, use 'back' to get out of apps instead of pushing 'home'. Unless 'back' is mapped to something in the app (like for some apps), back will end the process rather than leave it running.
I could write ten pages on why to not use autokiller, but a lot of guys who are a lot smarter than me will swear by it. I just find it slowing down my phone by forcing me to re-launch things like Handcent SMS, my Web Browser, and Google Voice, when I'd rather have those things stay running in the background. They don't chew up much processor time just sitting in the 'background', and my phone is WAY faster if it takes 1 second to open up each app instead of 3-6 seconds (because autokiller made my phone already automatically kill the task).
Good luck with your decision, sir.
And if you're using xtrSense, you can just set up your GScript to overclock how you want (mine's at 806800), and if you're using Froyo ROMs, you can use the battery tweak. SetCPU isn't that useful for most of these ROMs, since the methods of overclocking by collin_ph's battery tweak and xtrSense's GScript are faster and more efficient, and don't require a background process like SetCPU to be running.
But that's just my opinion. I hope it helps.

I use System Panel to basically monitor my memory instead of just relying on Autokiller to manage them for me. I also found that the way I use my phone, similar to the way pkopelek mentions, a few select apps a day, my free memory stays fairly close to what it did with autokiller installed. Average around 40-60 and if I kill a few off, up to 90-100.
One thing I have noticed is that System Panel comes with a cpu scale and shows your clock speed. With no SetCPU installed my CPU will drop down to 245 and then bounce around and finally settling back to 245 then the cycle starts again. With Collins tweak I get the same response. However, with SetCPU installed my CPU will clock down to 245 and sit there until I touch the screen. I have to believe that SetCPU is doing something that collin's isn't. Now the only way I can get it to behave this way is if I change the advanced parameters.
just my 2 cents.....

When I used AutoKiller and SetCPU (I used both between May and August) before I started using xtrSENSE v4.x, I never had a problem with SetCPU quitting working under any ROM, including any Froyo that was out at the time.
I only mean that perhaps the problem isn't between SetCPU and AutoKiller. Maybe it is the ROM??? Just guessing here.

Nikolai2.1 said:
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
Click to expand...
Click to collapse
I'm using this: http://forum.xda-developers.com/showthread.php?t=685594 and the value is ALWAYS above 9. I've never had it down that low except when I temporarily add it to the ignore list (it falls out after about 5 minutes).