Related
I was looking at the build prop and noticed the VM heap in honeycomb is 256mb. Now I only know a llittle about the VM heap but doesn't that seem a little high? Could this contribute to the launcher getting kicked out of memory so often, it seems its always redrawing the home screen
I have been running mine that high to get lwp's to work on gingerbread ROMS, it also helped the honey sdk ports that are out there. Something changed a while back I think.
Sent from my HTC Glacier using XDA App
Legacystar said:
I was looking at the build prop and noticed the VM heap in honeycomb is 256mb. Now I only know a llittle about the VM heap but doesn't that seem a little high? Could this contribute to the launcher getting kicked out of memory so often, it seems its always redrawing the home screen
Click to expand...
Click to collapse
256MB is the absolute maximum any one process can allocate. Initial heap size is only 5MB and it looks like there is a limit of 48MB in the dynamic increase above the initial allocation. Actually, not quite sure how the 48MB and 256MB parameters work exactly. Maybe someone more knowledgeable can chime in.
Yes, I'd like to know more too. I used 396mb for a week with no issues on my mytouch 4g. It was 24mb in the stock build.
Sent from my HTC Glacier using XDA App
Hello, I would like to know is there some tips and tricks for wildfire. Like roms or apps that would increase performance or quality of picture, Something like that. Every single tip is welcome. Id like to have "all out" for my wildfire, you know
Thanks already!
I just installed a custom theme from on this forum, making my icons and menus etc look way nicer. Don't use the live wallpapers but just a picture, it will make the phone a lot more fluent.
Overclock the phone and let it underclock when it is in standby (supported by ROMs like CM7) to increase performance and battery life (possibly).
Use as little widgets as possible to increase battery life, ...
Pretty standard, but that already helps a lot
Like the above poster said; overclocking the Wildfire helps a lot and gets rid of most speed issues.
Sent from my HTC Wildfire using XDA Premium App
how to overclock my wildfire CM 7.1-rc?? and use which rom
fsjarral said:
how to overclock my wildfire CM 7.1-rc?? and use which rom
Click to expand...
Click to collapse
It already has OC kernel included by default. Just go to Settings > Cyanogenmod Settings > Performance Settings > CPU Settings and set the speed there.
SaQ93 said:
Hello, I would like to know is there some tips and tricks for wildfire. Like roms or apps that would increase performance or quality of picture, Something like that. Every single tip is welcome. Id like to have "all out" for my wildfire, you know
Thanks already!
Click to expand...
Click to collapse
Advance task kiler is the best...which will allow you to close those usless app that are running in the background
remember to ignore the apps that are usually use by you,when using task killer
Kill all running apps just will slower your phone
Change the VM head size to highiest when you are gaming
I noticed this juts few days ago and did this on all my family's Nexus S.
Install Chainfire3d
from the market and then open the app and tap to install the driver. I used the normal method not the advanced. Don't set any other settings after your phone reboots. You can if you want to but a lot of aps won't work with those settings.
What this app does is it installs an intermediate open GL driver between the apps and phone GPU driver to give you better performance.
Just figured I'll share it with everyone. It really made a difference for me on ICS speed. The way I see it it should be baked it to all ICS ROMs.
isnt this just used for games?
that's why its called chainfire3D
the whole point is to trick proprietary games "apps" into thinking you have GPU that you don't
so you are able to play tegra adreno..ect games on other devices
dont think its works on anything other than games so i don't se how its helping make overall ICS faster.
ICS is already using our sgx540 just fine
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Thank you for pointing out this tweak. I too was under the impression that chainfire was just for games.
Both tapatalk and the browser feel much smoother.
Thanks
Sent from my Nexus S using Tapatalk
obsanity said:
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Click to expand...
Click to collapse
im eating my words sorry i was under impression was games only
im trying now you're right things are even smoother now thanks for the tip
As advertised. Nice find obsanity, it does make things noticeably smoother on general.
Noticed speed improvements thank you man
Nexus S - CyberGR Hybrid ICS (5), Matrix Kernel (15)
Chainfire dev recommends disabling all driver settings unless being used by a specific applications, per his xda thread:
" I strongly advise that when you are NOT using Chainfire3D for something specific, you disable all the options. This is better for system performance."
Anyone know why? Is he talking about the non-default options?
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Harbb said:
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Click to expand...
Click to collapse
That's what I was thinking as well. Thanks.
I'm installing this now... Have you guys noticed any decline in battery life?
Hopefully not :3
Does anyone know if this has the same downside as forcing gpu acceleration in the developer setting? I remember reading the Googler's post on G+ on how it increased the memory overhead by 8mb per app, reducing the memory available for other apps and processes.
Sent from my Nexus S using Tapatalk
It doesn't force GPU rendering. Alot of the Android UI is already using GPU rendering, using this intermediate driver just somehow makes it more fluid.
Trying it now, though I don't notice much improvements in scrolling.
I use force GPU setting on my phone. With the live OC in Matr1x at 111% (max my phone can handle) it does make a bit of difference in UI. But this Chainfire3D driver makes the most difference for me.
Also, in case you are on a ROM which doesn't let you change min memory settings, I'm using MinFreeManager which is a small app that just does that. The default settings which it comes built in are for GB but you can just change them manually. I don't touch the top 3 and just tweak the bottom 3. I'm currently on:
14,19,24,32,64,128
Does it effect battery drain?
Will this eat more battery juice?
Highly doubt it, and so far havn't noticed anything particularly different on my end. You can uninstall it anyway if it does cause trouble (though might be wise to perform a nandroid backup while initially installing).
Thx man, now trying it!!
Greetzz Jojoost
Sent from my Nexus S using XDA App
What are the additional features in the pro version?
What are the additional features in the pro version?
They are not described in the market.
Anti-Aliasing features and per-app settings are the main features in the pro version. More info here.
Hello
Can someone kindly tell me what difference does enabling GPU UI rendering make? From the name I can understand that the UI will be rendered using the GPU and not the CPU. But what are the advantages/disadvantages of this? What changes can I expect upon enabling it? And how does it, if at all, affect battery life?
Thanks in advance =)
Most of the apps now use GPU rendering (app packages for ICS, etc). Some apps don't(old apps). Force GPU UI rendering switch forces those apps to use GPU.
Pro. much smoother UI in apps that don't enable GPU rendering by default.
Con. Some visual bug may appear on some apps.
and what about battery life?
gannjunior said:
and what about battery life?
Click to expand...
Click to collapse
Theory 1; since the GPU is having some work right next to CPU it is an additional burden to battery to feed them both
Theory 2; Since they share the load they both can run at lower clocks so this means less voltage needed. Less voltage means less energy consumed.
So I guess there is no exact way to measure but nowadays most of the apps are already using that option default so it must be a good thing. At least the device does not have to run the CPU at max speed and heat up.
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
mohnim said:
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Read this:
Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.
Basically, using hardware overlays can reduce CPU usage by quite a bit
Click to expand...
Click to collapse
Source: http://rootzwiki.com/topic/28977-disable-hardware-overlays/#entry778564
thanks for the explanation
gannjunior said:
thanks for the explanation
Click to expand...
Click to collapse
Not to be "that guy", but there's a button for that.
So I recently changed over to the nexus 4, and I say, it is AMAZING. I just got to the point where the SGS just didnt cut it anymore. It has hung in there for a long time, but its starting to become under-powered for new versions of Android.
So in this guide, I am going to show you how to speed up your Galaxy S, and push it to its max performance.
You will need a custom kernel like Semaphore. I made this guide with no regard to battery life, but i did avoid using un-necessary power.
1. Live OC
- This increases the Bus, Ram and GPU speeds.
- This is very good because information can only be transferred as fast as the bus can transfer it. So if your CPU is fast, but your bus is to slow, it creates a bottle neck. So upping bus speed as well as CPU/GPU/Ram speeds can drastically increase performance.
- Find settings that are stable for your phone. For me this was 123%.
- Note that this will change the CPU clock speed choices that you have. Normal.
Click to expand...
Click to collapse
2. CPU Clock Speed / Governor
- Increasing Clock Speeds allow your processor to calculate more per second, therefore increasing performance.
- Start by finding the maximum frequency that your device is capable of handling, while still keeping stability. For me, this is 1400MHZ.
- Set lowest clock speed to 200 or 400. 200 is the best all-round, and actually uses less power than 100MHZ due to faster race to idle. I use 400 for performance.
- Use a snappy governor. Min/max is great, it is what i use.
- For more battery. lulzactive, ondemand, and smartass are all good.
- Enable smooth UI tweak.
Click to expand...
Click to collapse
3. RAM settings / management.
A. MOAR RAM.
- The Galaxy S has very limited ram, so we must make the best of it.
- It has 500mb, but some is allocated for the camera and GPU, so we only get ~400 in the end.
- Use the Bigmem option. Around 400mb, but breaks 720p recording. Its a good sacrifice.
- Also, Un-install any apps that you are not using! This can free up cache space and leave it for important processes. Go to settings/running/caches for more info.
- Go to settings/developer options/background process limit, and set this to keep more ram free. I use 3.
Click to expand...
Click to collapse
B. Enabling Swap
- Enabling swap allows the kernel to use specially allocated memory (on your SD card) to store cached pages that aren't currently being used, instead of storing them in RAM.
- Frees RAM for foreground or heavy processes.
- Make sure you use a fast SD card, and do not set the swappiness to high, both of these can slow your phone down.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
4. CM Performance Settings.
- Setting these properly can also increase performance on your device. It will not create any instabilities.
- I/O schedulers are all very similar. I personally prefer SIO, CFQ, or VR
- Under Memory management, Allow purging of assets and enable Kernel same page merging. Both use more clock cycles, but free needed RAM.
- Avoid ZRAM. Performance gain is not enough for the number of clock cycles needed to compress and decompress the RAM.
- Enable 16 bit transparency. Lighter load on the system when drawing graphics, and has never causes visual artifacts for me.
- Disable surface dithering. One less thing for your device to do, equals more performance.
Click to expand...
Click to collapse
5. Animation Scales (not necessary)
- This simply makes your device LOOK faster buy increasing the speed of the animations.
- Go to developer options and find Window Animations scale, Transition Animation Scale, and Animator Duration Scale.
- Turn them all to 0.5 for a faster UI.
Click to expand...
Click to collapse
Questions? Feel free.
But OC my phone will make my phone die faster yea?
Because I afraid to destroyed my phone
Sent from my GT-I9000 using xda app-developers app
It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium
AlwaysDroid said:
It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think even less, Ive never heard of anyone suffering at anything from oc anything.
This is an amazing guide and it has everything explained in one place thank you!
Sent from my GT-I9000 using xda app-developers app
Where/how do you enable swap?
good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom
beardedwonder said:
Where/how do you enable swap?
Click to expand...
Click to collapse
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835
friartuckme said:
good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom
Click to expand...
Click to collapse
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!
AlwaysDroid said:
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835
Click to expand...
Click to collapse
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.
beardedwonder said:
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.
Click to expand...
Click to collapse
I'm abit out of the loop. I used devil kernel and it had it. I know cyancore kernel has it!
Sent from my Nexus 4 using xda premium
AlwaysDroid said:
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!
Click to expand...
Click to collapse
very true,i agree