I've read a few things about not using Task Killers on the DHD as its not required, just done a little experiment though.
Did a Quadrant score on my DHD i'm running Leedroid 1.2 with standard Kernel.
My quadrant score was 1508... (after it being on and used all day)...
Downloaded Advanced task killer from the market ran it killed all the apps running let the system settle so that scrolling was smooth etc ran quadrant again and got 1959.
Does this actually mean anything ?
I'm not having any issue's with my phone just curious to see what the difference was...
Doesn't mean a bean. I hit 3000 in quadrant, no task killer. Just in Aeroplane Mode (proper spelling) for the test.
Android 2.2 handles tasks & memory very well, chances are "killed" apps will just restart themselves anyway. Especially if they are widgets on you home screens.
EDIT: Link to quadrant scores --> http://forum.xda-developers.com/showthread.php?t=815517
Related
So with putting some different roms together with different OC kernels, and testing the overclock settings here's what i've got;
Teamfenix 1.7.1 (not 1.8)
OC kernel 768 CM espresso 2.3
or
Tester 960 kernel set at about 787.2
i'm using a task killer as well ( i dont care what anyone says... with eclair or froyo, task killers do help speed and numbers as long as you kill the right things. )
So after flashing these 2 options, pick your choice between the two kernels, i personally like the 768, its got great speed, great battery life, and don't have to worry about breaking SU.
so search for those, download them and heres some proofs of numbers about what you're looking to get.
javolin13 said:
So with putting some different roms together with different OC kernels, and testing the overclock settings here's what i've got;
Teamfenix 1.7.1 (not 1.8)
OC kernel 768 CM espresso 2.3
or
Tester 960 kernel set at about 787.2
i'm using a task killer as well ( i dont care what anyone says... with eclair or froyo, task killers do help speed and numbers as long as you kill the right things. )
So after flashing these 2 options, pick your choice between the two kernels, i personally like the 768, its got great speed, great battery life, and don't have to worry about breaking SU.
so search for those, download them and heres some proofs of numbers about what you're looking to get.
Click to expand...
Click to collapse
Im not surprised that you got close to the N1, considering the only differences is the screen res and cpu, both phones are using an adreno gpu.
Ace42 said:
Im not surprised that you got close to the N1, considering the only differences is the screen res and cpu, both phones are using an adreno gpu.
Click to expand...
Click to collapse
yeah, i just wish there was some software end update for the GPU, that would be nice too
Hey there,
I went through a lot of trouble to get my HTC Magic (32B) working really well,
just wanna share this for people who have issues with the phone's performance as well.
I've tried many things, including a swap partition (on a fast SD-Card) as well as compcache.
Turns out, disabling both did the trick. It FINALLY went from unusable to fast and enjoyable!
My current rom:
Cyanogenmod 6.1.0 RC1
Settings->Cyanogenmod-->Performance:
Compcache DISABLED
JIT Enabled (I noticed an increase in CPU Power with the linpack benchmark,
but it still seems underpowered at 3.3 mflops)
Dithering Disabled
Keep Home App in Cache Enabled
Keep MMS-App in Cache Enabled
VM Heap 16m
Also I am using SetCPU to overclock to 576mhz at the moment(feels like the battery is draining faster).
Another thing I did was to reduce number of Homescreens in ADWLauncher down to 3, since thats 'nuff for me.
Hope this helps someone out there, as I was about to shatter my phone into a million pieces :O
On a sidenote: How many mflops do you get with your Magic?
I have the same findings There was a point when swap, overclock, apps2SD, and compcache all would make a major speed-up on your phone, but the CM6.1RC and the nightlies that shortly preceded it have given me the best performance in my magic's history with all of it turned off.
My phone is configured very similar to yours. I went up to vm24 to smooth out how heavier applications run. I left JIT on despite the theoretical drawbacks because I notice no performance hit and it makes a difference on fractal rendering apps (I'm indifferent to benchmarks).
The CM forums seem to be in a bit of turmoil atm because people are slowing down their phones by applying mods that genuinely sped it up in the past.
But for the first time I can be widget-heavy, always go straight back to home, use window animations, never have choppy music (even when using navigation), use alternate keyboards with no performance hit, and even run a good few live wallpapers. All with unprecedented battery life? Not sure what CM did but he/they sure did it right.
One thing - overclocking your CPU will better your benchtest results but I think you'll surprise yourself by leaving it stock, and even (gasp!) underclocking it. CPU clockrate is one of many possible bottlenecks and considering the 1.5 and 1.6 official roms were capped at 384 (or 352 I can't remember), I doubt it is the culprit of possible slowdowns. I run at 384 almost all of the time and have noticed no side effect except for extreme battery life and added stability (615 gives me reboots). The only differences I've seen overclocking make are in fractal rendering apps and benchtests but Pandas vs. Ninjas and Raging Thunder rock at 384.
glad to see I'm not alone with this
I can still see the phone running out of ram when alot is going on, but its ok.
I'll try your suggestion and underclock the phone.
Another small tweak I just found:
under mobile network settings there is an option "only use 2G", which is checked by default. turning this off improved my connection speed (obviously).
but again this comes at the cost of battery-life.
I downloaded both apps to overclock my X. the unstableapps version made my X reboot constantly no matter what I set it at. Now I'm trying the JRummy16 app. I set it at 1.45 at medium voltage. No reboots, however, while playing a simple game, it hesitates and skips and jumps around. Also, I ran a quadrant benchmark 4 times and never scored over a 1400. My X running the newest Apex Rom scores over 1500 all the time. Any help with this app would be appreciated, or is it just a waste of time?
I can tell you right now JRummy's app is a keeper. However, Quadrant should be completely be disregarded immediately. Quadrant scores are a terrible way to judge anything. This has been discussed so many times I don't feel like saying it again but a short rundown is that their are so many tweaks that can change that number so drastically without an actual effect on performance.
Sent from my DROIDX using XDA App
But what about what I said about the game? Seems funny that it would start doing that after I overclock it.. Shouldn't that improve performance while playing a game or while running any other application?
and btw, i'm on here everyday multiple times and have never seen any major discussions about quadrant benchmark scores.. (other than the hundreds of people using it to brag about their X's all the time)
Your phone doesn't like that speed apparently so either go to high voltage or go down to like 1.30 and see what happens. I have found out that my phone likes 1.15 low voltage the best.
Just sounds like that speed is too high for your phone. Mine's best at 1.35. The x comes with 1ghz stock because it's stable on all phones. Some can handle more, some can't. You just gotta find your sweet spot.
Sent from my DROIDX using Tapatalk
brandon2x said:
I downloaded both apps to overclock my X. the unstableapps version made my X reboot constantly no matter what I set it at. Now I'm trying the JRummy16 app. I set it at 1.45 at medium voltage. No reboots, however, while playing a simple game, it hesitates and skips and jumps around. Also, I ran a quadrant benchmark 4 times and never scored over a 1400. My X running the newest Apex Rom scores over 1500 all the time. Any help with this app would be appreciated, or is it just a waste of time?
Click to expand...
Click to collapse
First of all, 1.45 is way too over clocking. I haven't seen too many Droid X that's stable at 1.45ghz. My recomemdation is to drop it down to 1.2 or 1.3 ghz. Mine is most stable at 1.2ghz low voltage. My other recomendation is to install Autokiller and have it preset at Extream or Ultimate. It keeps enough memory freed up at all times to run apps with out freezing your phone. Autokiller will make your phone snappier and smoother. At least from my experience.
Even though most people say that quadrant score is Not relevent in real life, I feel thats score has some truth to it. My Quad score stock ranges any where from 1250 to 1400. When I over clock it to 1.2 ghz low voltage (MY CURRENT SETTING), score ranges from 1500 to 1600 or some times even little higher. When I over clock to 1.3 ghz, score improves again. It scores as high as 1700+ which I'm sure means some thing.
Be careful when u running any auto task killers. Linux, androids base, has always handled processes well and managed ram well. If this was wm we would be having a different discussion. As for quadrant score I guess its an alright tool to compare ur settings on your phone bit a comparison better two different phone is not reliable at all. But actual phone performance regardless of the benchmark is always best, I normally run at 900 ghz at 45-46 vsel and the phone flies on gummyjar and rubix
Sent from my DROIDX using XDA App
ok, well 2 days on 1.25 medium voltage and its great, so thanks all...
mfinlay04 said:
Be careful when u running any auto task killers. Linux, androids base, has always handled processes well and managed ram well. If this was wm we would be having a different discussion. As for quadrant score I guess its an alright tool to compare ur settings on your phone bit a comparison better two different phone is not reliable at all. But actual phone performance regardless of the benchmark is always best, I normally run at 900 ghz at 45-46 vsel and the phone flies on gummyjar and rubix
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
That's what I was told also. That Android manages Ram well how ever when I was running Widget Locker, LP along with other apps including games, my phone would freeze or delay on me. When I check the RAM, it was going as low as 25MB available. Ever since I preset the AutoKiller to Ultimate, my phone shows over 150MB available and phone has been running really smooth with NO frezzing or delay.
Autokiller is not the same as a task killer. It assists android's internal memory management system. It just tweaks it to your liking, just like all the other mods and hacks you do to your phone.
Sent from my DROIDX using Tapatalk
Hello,
two days ago i changed the size of my Vm-heap to 32mb. I was curious after i read in some posts that this could affect the performance of resource-intensiv apps. As i am using navigon-navigation a lot i had to give it a try...
After ive changed it and rebootet the device, navigon works MUCH better then before, track calculation is much faster and the app is much more responsive and running fluent. The difference is highly noticeable. For other apps like my browser i experiecend the same.
I read that the downside of it is that it is possible that apps could be moved out of memory because some other apps now use more ram and so the jumping between apps could be more time intensive. But i have noticed no slow down at all.
(Wildfire is not a fast phone, but i think 384 mb ram is really good for that kind of phone, some other phones like galaxy ace have only 287 RAM with better cpu)
My experience is that a lot of apps running much better know, and for me its a absolute performance enhancement, I would even go so far that i would say it was the best performance-enhacement after overclocking the device. So if you are running resource-intensive apps (like navigation browsing) you should definitely give it a try.
Whats your experience with that ? Ever changed the vm heap size? Noticed differences??
Cheers.
im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx
darkstep said:
im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx
Click to expand...
Click to collapse
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.
Nhs666 said:
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.
Click to expand...
Click to collapse
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Sent from my HTC Wildfire using XDA App
ErwinP said:
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Click to expand...
Click to collapse
I didn't want to implicate that the ringing lag is about the low freq., but i noticed that with such low freq's the phone is not so responsive when pulling suddenly the notificationbar, get it out of standby and such things. Never noticed something like that??
I was testing about it too. i settled with 32mb heap size, which i've found to be the best practice. Anything lower would make apps like navigon or opera lag, anything higher, would give me force closes on apps for some reason.
I also tried to experiment with compcache, with the following settings "disabled, 18%, 26%" and i think 26% makes my wildfire a bit snappier, although it might be just a placebo effect, because there's no difference in quadrant/linpack benchmarks.
why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.
Nhs666 said:
why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.
Click to expand...
Click to collapse
I have to agree with you Whatever makes my phone "feeling" snappier and faster is good enough in my eyes!
You should really check Juwes Ram optimization thread in the Android development section for some serious performance gain. I flashed it yesterday in CM 7.1 Nightly 144 and the responsiveness boost is quite noticeable.
i agree the synthetic benchmarks are not that important its the daily use performance that mater to me
I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire
vijaykirann said:
I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire
Click to expand...
Click to collapse
Hmm i have a swap partition already made just in case and i might try it, but in theory a swap partition (even worse if it's a file) is much slower than the compressed cache due to the SD Speed limitations, unless we are discussing about class 10 cards.
anyone ?
Take a screen shot of all the installed apps in ur list and also take a screenshot of the ram usage ... Let's see who conserves well .... Mention the task killers ....
Sent from my GT-I9082 using XDA Premium 4 mobile app
I wouldnt recommend "adding" a Task Killer. Better tweak Android's native one to you likings using any of many Tweakers, or manually do so via Build.prop. It has been stated than Android OS does a great job at this. Task Killers will more likely lag the device and eat up resources/battery.
- Paul
Task killer was actually useful back in Froyo days... Back then Android's memory management isn't that great and very prone to lags (I remember my old Froyo phone)
But seriously... we're now at version 4.4.x, no longer 2.2.x... Android has become more and more efficient and even now Kitkat runs on a 512MB RAM device.
If you worry about background apps taking CPU cycles or keeping the device at wakelocks.... Greenify helps... but the ultimate solution is to hunt down the app and uninstall it. It's obvious that the app dev did a horrible job.
+1
I agree...I use Greenify and it helps a lot, airdroid, and even camaras work in the background. I've debloated my Grand, Seeder, done some minor build.prop tweaks (manually): fling speeds, max events, etc, and I have no complaints. Many of those "tweaks" out there, is more 'Snake Oil' than anything else.
naufalhadyan said:
Task killer was actually useful back in Froyo days... Back then Android's memory management isn't that great and very prone to lags (I remember my old Froyo phone)
But seriously... we're now at version 4.4.x, no longer 2.2.x... Android has become more and more efficient and even now Kitkat runs on a 512MB RAM device.
If you worry about background apps taking CPU cycles or keeping the device at wakelocks.... Greenify helps... but the ultimate solution is to hunt down the app and uninstall it. It's obvious that the app dev did a horrible job.
Click to expand...
Click to collapse