Related
Guys,
Browsing the web I stumbled up on to this article:
It describes how you are able to get a good performance out of your Hero, Hence that it's just a experiment so not sure if it will work!
http://www.majicware.com/HTC-Hero-Speed-Issues-Experimenting?vzWMwp
I'm going to post updates as I will test it.
The article actually sounds quite interesting...I've also noticed that killing tasks doesnt necessarily get rid of some of the lag (although I dont have that much lag to begin with).
I think I'll give this a try for a couple of days too.
Well lets keep us posted on this case. I will give a update tomorrow.
I'll see if that works for me =)
sounds promising =D
thanks for sharing
ill give it a try!
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
I have been using the Hero for a few days. On day one I hated it, it was so slow. Then I started using Taskiller to kill tasks like weather, clock, mail, peep etc that are running in the background. Not much help. In fact, it seemed the more frequent that I killed these tasks, the slower my Hero ran.
After a few days of use, I realized the trick to speed up the Hero (or android in general) is DO NOT kill tasks unless you are running our of memory. By running out of memory, I mean really out of memory. My Hero is using 160MB memory right now, which may seems a lot, but it is running very smoothly. Killing some tasks reducing memory usage to, say 90MB, wont' really speed it up. Unlike Windows Mobile, as long as your memory usage is not 99% and have memory left for additional apps to open, just leave it. Remember the Hero has 288MB memory, 100 MB is already reserved for the OS to run, and android memory management will kill unnecessary tasks for you when you run out of memory anyway.
Now, the important part. Do not kill tasks manually too frequently. You have to understand when does the Hero slow down: when it is fetching data. If you use an HTC widget, do NOT kill the relevant app that the widget requires it run in the background. For example, if you used the HTC music widget, don't kill the music app running in the background. If you killed it, you would notice a very significant lag when you go from another page to the page with the music widget. This is because the music widget is trying to open the music app and access the music on your micro SD. Once it is done, the music app will just become idle until you start playing music and there is no more lag. But if you killed it, the widget had to open the app every time you reach that page after killing the app. This causes lag.
The same go for the twitter widget. If you killed Peep running in the background, you will notice a lag when you go the page with the twitter widget. This is because the twitter widget is starting up Peep again and has to connect to your twitter account to check for new stuff. But if you leave Peep running, it will do so only at the regular time interval that you set.
I am now running the HTC clock widget, music widget, bookmark widget, twitter widget and full of stuff on all of my 7 pages home screen. I have clock, weather, music, peep, mail and many other apps running in the background. My Hero run very smoothly.
I hope this helps.
Hmmm... Well, I think it is pretty obvious and common sense that the apps used for active widgets should surely not be killed. For the others, I find that I am better off killing them. Even if this should not be the case, and the effect only "psychological", I still fail to see what would be a benefit of not killing the applications.
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
've stopped obsessively killing Apps...running smoothly. Android Dev video posted on similar thread reassured me that the OS is meant to take care of all that anyhow
phel21 said:
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
Click to expand...
Click to collapse
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
I like the timeliness of the Android store; and I'm suffering with dodgy apps too - my Hero currently won't last overnight on standby - but it's still miles better than the iPhone nonsense
Well I stopped using the task manager to kill apps for a couple of days....but there is no real speedup and its just the same.
BUT it also means that its pointless to kill the tasks to begin with since it didn't make a difference either (like other people are now saying). If anything, the browser and apps like people/contacts load up faster beacause they are still somewhere in the background (I used to always constantly kill these apps).
The part about not suspending the phone straight away has made a slight difference. Before, when I turned the screen on I constantly had a lag especially sliding the screen left and right and going to the messages page. But if I let it go into standby by itself, when I wake up the phone, it barely stutters (and if it does, its only for like a split second on the first slide).
...if only there was a shortcut to just lock the screen....
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
...if only there was a shortcut to just lock the screen....
Click to expand...
Click to collapse
Aren't there apps for locking in the market?
don't know will this speed up things and to whom it may apply, but until today i never ran my Stocks app, seeing as i don't care about stocks so i opened it, opened settings and found out it was set to update every 1h with 4 preset stock somethings....so those not using it might also wanna check that the thing is switched to Manually, one less task that shows up for no reason :/
Tone-Fu said:
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
Aren't there apps for locking in the market?
Click to expand...
Click to collapse
I've only come across the likes of lock 2.0 but I thought that was an alternative lockscreen...
cdmackay said:
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
Click to expand...
Click to collapse
Apple's problem is politics. I wasn't hinting towards any such subjective valuation for Android. What I'd like is a clear set of technical requirements (example: an application that auto-starts during boot even without necessary configuration data should not be accepted), and a site back-end with numerous emulators that runs applications through their paces to obtain performance/power/network rating before they are made available for download. Extensive testing would require manual configuration, test and monitoring, but even some simple automated tests could sort out the worst offenders. Ratings should be displayed with application descriptions on the site, and would also work as a simple form of tech feedback to developers about things they may need to improve.
good points.
I've since discovered that any app that registers to receive async alarms will be started at boot, even though it doesn't necessarily need to be. not really a problem, but the cause of a lot of processes running at boot for no obvious reason.
Hi Guys,
I'm Adam Saunders, author of the original article.
Just a thanks to everyone that is also trying the experiment. So far I've had a lot more positive results from people than negative, so the hunch is somewhere on the right track.
I was going to try and find an exact reason as to why killing tasks repeatingly will slow the device down. It's been said its the way that Android kills apps but saves the state, so the process isn't actually running, and by killing that off, the orphaned state is possibly the problem. Sounds feasibly, but not read anything official to back up that claim.
Confirmed, it's been three days since I stopped killing the processes and any lagging (which was very slight for me in the first place) is gone. Thanks for the tip, Adam!
So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...
Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.
Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.
I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.
so nothing on the OC for 2.1 yet?
bump
I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.
on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying
O.S.K. byebye command is msmvkeyb_toggle=off
OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.
When I got my desire it was stable and fast the more I put on it the slower it gets . I've tried numerous task killers and some of them screw the phone up . On one thread someone suggested leaving the phone to manage its own background programs . What does everyone thing is it better with no task manager ?
-------------------------------------
Sent via the XDA Tapatalk App
My personal choice is to leave taskiller off the desire. I put a taskiller on and almost immedietly the phone started acting wierd eventually getting into some sort of loop rebooting itself. After many reboots it eventually gave me enough time to uninstall the taskiller. Obviously that was the problem as it has never repeated itself since. My phone runs fine without it.
I really cannot understand why people use task killers. As I have said before if you are a real expert and you have a badly behaved program that you have to use you might just have to use of a task killer.
If you are not a real expert or are even asking the question don't use one. You will almost certainly end up with worse performance and decreased battery life.
I have 60 plus applications on my Desire and don't suffer any slowdowns or other problems. There is just no need for task killers/managers. This is NOT windows!
Android has a built in task killer. It's pretty good and IMHO difficult to improve on.
Kill Task Killers!!
Agree with others, you only need it to kill a rogue app without reset.
I have around 100 apps and the only semi-slowdown I can feel is by putting complex widgets and live wallpapers together. Otherwise I've tried some of these task killers and even killing all the 20-30 processes 'frozen' or active in the background had no effect.
Still I keep it in order to kill those badly designed applications that have some glitches in going back to the main screen or rarely get stuck.
I would think that if you experience some problems they are not related to the quantity of applications open in background, but rather by a single one that has some design flaw.
andycted said:
I have around 100 apps and the only semi-slowdown I can feel is by putting complex widgets and live wallpapers together. Otherwise I've tried some of these task killers and even killing all the 20-30 processes 'frozen' or active in the background had no effect.
Still I keep it in order to kill those badly designed applications that have some glitches in going back to the main screen or rarely get stuck.
I would think that if you experience some problems they are not related to the quantity of applications open in background, but rather by a single one that has some design flaw.
Click to expand...
Click to collapse
Well said.
The trouble is people use a task killer when they don't have a problem. They just kill apps. without a clue what they are doing.
I repeat don't use a task killer until you really have too.
and what about battery life?is too many running apps affecting battery?
polystirenman said:
and what about battery life?is too many running apps affecting battery?
Click to expand...
Click to collapse
Doesn't affect battery at all. Almost all apps. are suspended in the background when you move away from them. Task killers are the major cause of poor battery performance as killed apps. then have to be reloaded instead of resumed. Try switching between say six applications, and using them, with and without task killing. I bet you will see a massive performance gain without the task killer.
polystirenman said:
and what about battery life?is too many running apps affecting battery?
Click to expand...
Click to collapse
If an application keeps going in the background in some way/service it's because it's meant to be, like an updating rss feed reader, a live wallpaper, an email client pulling mail from the server, widgets or music player streaming/playing music. If you don't want those to run in the background you obviously should set them not to update, remove them from the desktop, stop them manually, etc.
Otherwise every other application you open and then leave when you switch to another application, gets stopped and 'frozen' in the state it had so that when you switch back to it or reopen it, you find it in the same state, giving you the impression of having been running in the background (but it didn't).
It's a smart way to combine the speed of single-running applications in dumb iphones and the flexibility of more complex os like WinMo. It's also apparently the same way as WP7 will work.
Like mentioned above by killing processes you mostly cause disruption in the pre-ordered way they work and probably cause more battery usage since they have to restart from scratch for the most part. More importantly real-time monitoring of processes and auto-killing them is most likely eating battery a lot since every real time monitoring does that, like many real time battery widgets and such.
Ok.thx for answers guys.i am geting rid of task killer right now.
Same here .. I'm a techie on most things obviously not Android must try harder !
Must admit did complete hard reset yesterday got rid of task killer after first posts phone seems more stable
-------------------------------------
Sent via the XDA Tapatalk App
I have a task killer, but only for killing appliactions which aren't written good and causes some lag or they don't want to close..
I just looked at the comments on the Advanced Task Killer (free, high in the list in the Market).
I wanted to believe you guys here at XDA. But I went trough the comments on that ATK and 95% was 4 to 5 stars. All with reply's like:
"must have app"
"should be included in Android"
"doubled my battery life"
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
I myself have been using that ATK for a while, killing only some things that don't close (like games,Facebook or Twitter, etc...)... battery life is still not as good as I would like it to be, but I only have had my Desire for a week.
Are you guys REALLY sure that stopping to use ATK will improve battery life?
XDA mark said:
I just looked at the comments on the Advanced Task Killer (free, high in the list in the Market).
I wanted to believe you guys here at XDA. But I went trough the comments on that ATK and 95% was 4 to 5 stars. All with reply's like:
"must have app"
"should be included in Android"
"doubled my battery life"
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
I myself have been using that ATK for a while, killing only some things that don't close (like games,Facebook or Twitter, etc...)... battery life is still not as good as I would like it to be, but I only have had my Desire for a week.
Are you guys REALLY sure that stopping to use ATK will improve battery life?
Click to expand...
Click to collapse
Read this article:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
it's the placebo effect. A While ago there was a thread on a winmo forum for a new overclocking application. It had tons of "amazing", "must have", "goes way faster", comments, it became incredibly popular. then the developer made public the fact that it was a social experiment and the application did absolutely nothing other than having a nice interface for reporting fake cpu .
As said if you have a single bad-behaving application (which is very rate) only kill or rather uninstall it. Games don't run in the background, battery becomes great after one-two weeks, but still you can't expect it to run for 10 hours of continuous heavy usage. Buy a second battery if you need that
XDA mark said:
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
Click to expand...
Click to collapse
No one is saying they are lying - personally I see it more as a placebo effect, but I do understand there are certain situations where task killers come into there own. Having owned 3 Android phones though, I can say that in my case leaving Android to do its own thing works very well for me - I don't believe that it actually increases battery life significantly, but I do firmly believe it improves the overall stability of the platform.
One thing that probably should be added, is that using swap on an Android device will cause problems with Androids own internal resource management because it cannot distinguish between real memory and the virtual memory made available using swap. See here for more details. I wouldn't be at all surprised if those people who get the most "benefit" from task killers are also using swap.
Regards,
Dave
How to maximize battery life without affecting functionality? I think the answer for this question is different for most of you. It depends on how you plan to use your device, even when it’s not turned on. Keynote is that you have to get the right tools and be creative. To give you a head start, I will dump my configuration in this thread. I am able to get up to 48 hours on one charge using this configuration. If used more intensive, your results may differ from mine though.
My configuration
HTC Desire
DeFroST 2.4d
DeFroST 2.4d"]DeFroST 2.4 SVS 1267Mhz kernel
SetCPU
Setting Profiles
DeFroST 2.4d
I will stick to this ROM for this guide but I’m sure the following applies to your custom ROM as well. DeFroST is my personal favorite and I would like to use this opportunity to thank RichardTrip for all the time he puts into this ROM.
DeFroST 2.4 SVS 1267Mhz kernel
DeFroST 2.4 HAVS max 998MHz 800mV (max 998MHz) might be better at saving more energy. But my decision to pick the SVS 1267Mhz has couple of causes.
I don’t have a CPU that can run at 800mV
I’m not patient, I love to go to max speed when it’s available
I found that with my current settings, battery life is good even with the SVS kernel
As I said, it’s totally up to personal preference. If you feel you need it, flash it! There’s a 925mV kernel out there as well if you have the same issue I do with 800mV (running unstable).
SetCPU
Freely available to any XDA user. A lightweight tool that offers all the functionality we need. Other then setting the default speed, it allows us to use profiles based on things like battery charge and temperature.
Main
Profiles
In my configuration, the phone runs at full speed when the battery capacity >= 75% or if it’s charging. Then when the phone discharges, it gradually scales down the max CPU speed. More important though, I found that I don’t need to have the device running at max speed, seeping energy, when I’m not actively using it. When my display turns of, my max CPU speed will be set to 245Mhz. This is perhaps the most important setting in this configuration.
Setting Profiles
No, not Juice Defender. I don’t know why so many seem to prefer Juice Defender. It cannot be customised the way I like it and the UI gives me a headache. But then again, that’s my opinion, maybe I’m wrong
Setting profiles is once again a lightweight tool that lets you define rules by means of logic. It works like this (example):
Create a profile that enables WiFi
Create a rule Activate WiFi when the condition battery is plugged to any charger is met
I figured that I do not want to receive mail, connect to bluetooth or WiFi when I’m asleep. Also, I don’t need a constant e-mail sync at daytime. 50% sync activity is enough for me. For now, that’ll do.
Profiles
Rules
I have a lot of ideas that can still be implemented. The devs at probeez.com are working hard to implement new functionality into their app. One idea I had was to revert to 2G when the display is turned off. However, the condition display off and the action revert to 2G are not available yet.
If you agree, please let the devs know what functionality needs to be added to make their software even better. Vote on this site.
The 2G functionality has already been planned. My other suggestion, the display state, doesn’t have enough votes yet. You can find it here.
The good thing about this tool is that it will be highly customisable when more and more options are added. This fits the idea of choosing your own energy efficient settings I’m trying to promote with this topic.
Conclusion
I could elaborate my choices, but my point is to give you tips about how to address energy saving. Read this manual and be creative. Copy some of the ideas, change others. Maybe come up with new ideas so brilliant that I should add them to this post .
I’ll try to keep updating this topic with the input from you and the newly available functions in the apps.
Other Recommendations
Manual control of brightness
How could I forget? My own brightness setting is always at the lowest. Unless I'm in a very bright environment (like in the sun) and I cannot see anything on my screen. Auto brightness tends to be to bright in general. The Power Control widget can assist you in quickly switching brightness.
-prove
Use a plain black wallpaper
Although this goes further them some of you want to go, using a plain black wallpaper can save battery usage.
AMOLED: Black wallpaper = Battery saving (experiment result)
-b3ndik
great guide, will try this after I get some sleep!
I would recomend using manual control of display brightness!
prove said:
I would recomend using manual control of display brightness!
Click to expand...
Click to collapse
Added. Thank you.
Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.
b3ndik said:
Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.
Click to expand...
Click to collapse
Added to recommendations, thank you.
Personally I think this goes a bit to far for me. I like active backgrounds, like the one that reflects weather and daytime. However, it's a good idea. If someone can find the link to the detailed topic, I'll add it.
here is the link to the topic. The thread includes tests and results.
http://forum.xda-developers.com/showthread.php?t=660853
is it safe to assume that the profiles that let you enable or disable wifi are in the full paid version ?
*edit*
scratch that, just found 'setting profiles' on the market.
i did lose 2% battery life with just 5 minutes surfing ealier on ..
I have never used any additional program to control power apart from the default Android power widget. I would normally do this to preserve energy no matter which ROM or even which phone I have. It's all common sense:
- turn "2G only mode" and switch on 3G hen I actually need it (e.g. browsing heavy webpages). If you turn off the images in websites even GPRS usually does the job well.
- NEVER use 3G for regular voicecalls. It's a completely senseless way of draining battery fast.
- completely switch off any automatic syncronizations (Gmail, Facebook, Weather, etc.) and syncronize individual accounts only when I actually need it. Simply untick the "automatic synchronization" in the accounts and sync settings.
- of course wi-fi, gps are permanently off and I turn them on manually only when I need them.
- keep the display as dark as possible and no brighter than needed.
- use a solid black wallpaper which saves energy on AMOLED screens (won't make difference on regular TFT LCD). A bright wallpaper may significantly increase energy consumptions.
- forget any "Live" wallpapers.
I have read that killing tasks does not make much difference on Android 2.1 onwards. I still keep killing tasks just as a habit.
This way it adds up a bit of extra manual job but I think it's better than any of those "power control" programs that do the same thing just not as accurately as one can do manually.
well i left my phone on charge overnight and unplugged it at 8am this morning on 100% battery.
6 hours later and it's on 96% - although to be fair that's with near zero usage.
thanks for this topic, very helpfull
on this screenshot, what contains the first line with priority of 100?
http://forum.xda-developers.com/attachment.php?attachmentid=365973&stc=1&d=1279958467
thanks !
I have just implemented everything you recommended, so lets see how tomorrow goes (I can't be bothered to go drive out of my local cell towers ranges right now to see if my WiFi turns off ).
With regards to Disabling Sync, if I set it for 4 minutes out of 5 minutes (4/5) then Sync is only enabled for 1 minute out of every 5 minutes, right?
Having previously used JuiceDefender, I thought I'd give Setting Profiles a bash. First stumbling block is lack of toggling for mobile data - is that right, or have I missed something?
Was on the portal and noticed this:
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Caveats
There is a (theoretical) security risk, in that seeding /dev/random with /dev/urandom decreases the quality of the random data. In practice, the odds of this being cryptographically exploited are far lower than the odds of someone attacking the OS itself (a much simpler challenge).
This may adversely affect battery life, since it wakes every second. It does not hold a wakelock, so it shouldn't have a big impact, but let me know if you think it's causing problems. I can add a blocking read to the code so that it only executes while the screen is on. On the other hand, many of us attribute lag to lacking CPU power. Since this hack eliminates almost all lag, there is less of a need to overclock, potentially reducing battery consumption.
If you try it, let me know how it goes.
ROM builders - feel free to integrate this into your ROMs (either the .apk / application, or just the rngd binary called from init.d)!
If anyone's interested, I've launched a paid app on the Play store for non-xda users. As I add features I'll post the new versions here as a thanks to you guys (and xda community at large for being such a great resource). But if anyone's interested in the market's auto-update feature, just thought I'd mention it.
Cheers!
Click to expand...
Click to collapse
Should this help with the lag that we get on the Play?
If anyone else wants to try it heres the link to the thread:
http://forum.xda-developers.com/showthread.php?t=1987032
I tried it and it i got faster loading on some minor stuff (like contact picture loading) and apps installed on the internal memory seems to load faster, in terms of UI smoothness I don't notice any difference, because UI is smooth since the beginning
I think i may try it out although i don't see any instructions
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
BTW, somebody already posted this in the XPlay Android Dev section:
http://forum.xda-developers.com/showthread.php?t=2073382