Related
*** THIS IS EXPERIMENTAL ***
Thanks to toastcfh, maejrep, AssassinsLament, Estimated Prophet, Cicatrize, joeykrim, geyes30, kpkimmel and all the others from the kernel & display cap threads who have been working tirelessly, and continue to do so. This isn't over until we can find the real cap! But I think this avenue has progressed enough for it to have its own thread, if only to give hope, since we now know both Epson and Novatek panels physically can do it!
What Doesn't Work
Nothing. Now based on the official kernel with everything working.
About This Kernel
This is just a dirty hack. We haven't yet figured out where the real cap in framerate is coming from. But until we do, this is the best we have. At least it shows the display itself can handle a higher framerate and isn't physically incapable like HTC would have us believe.
Novatek panels can now get up to 46fps pretty reliably. Run fps2d a few times.
Stdev depends on system activity. If you're going to be judging stdev, DON'T measure it immediately after booting, set your CPU throttle mode to "performance", be sure to run fps2d several times, then average those stdev numbers in your head.
The changes are now immediately applied upon boot. There is no need to cycle your display anymore.
This kernel has support for overclocking/underclocking, up to 1.119 MHz. Also includes my own undervolting and overvolting for higher speeds to increase stability.
You can get dramatically tighter stdev numbers by setting your CPU governor to "performance" in SetCPU. It seems scaling really messes with the framerate. Obviously this will drain your battery faster, as your CPU will constantly be running at full speed. Set it back to "ondemand" if you don't need it.
Some people are reporting their touchscreen grounding issues have been cured.
Support to change the T2 value on the fly [thanks to maejrep]
Support for 5 simultaneous touch points! Use Dotty (in the Market) to see it in action. It'd be cool if someone would make a simple app to demonstrate what can be done with more than the mere 2 points we are used to. People have suggested new lock types, security locks, ways to rotate things, etc. [thanks to maejrep]
Some hardware fails to accept 5 points, so a fail-safe has been added to default back to 2 points for some EVOs
AssassinsLament has created an awesome app to provide an easy way for people to change their T2 timing. Check out his app here: http://forum.xda-developers.com/showthread.php?t=716659 [thanks to AssassinsLament]
Changes to display timings are now sticky until rebooted (w/ the above app, or set manually)
What's New
v5.1.1: Using the official kernel. We've lost some fps, but we've gained camera, video, 4G, etc. 46fps is now average.
v5.1.1: Expanded user-modifiable timing settings. Change at your own risk.
v5.1.1: Audio patched [thanks Geniusdog254 and KERKEDAGAIN]
Instructions
Do a nandroid backup, and flash this over pretty much any ROM. If you have problems, you can just flash a stock boot.img again. There should never be any need to wipe anything.
IMPORTANT: This will only work with the stock bcm4329.ko! Using the newer files and flashing this kernel will result in wifi being unable to start, and vice versa. To correct this, you'll need to flash over the correct wifi files.
Changing Timing Settings
You can use the following commands from adb shell to temporarily change timing on the fly. Do it while your screen is on.
Set: echo NUMBER > /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Check: cat /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Parameters:
t2 - 245 to 1023 [Default Eclair: 437, Froyo: 432]
t3 - 0 to 7 [Default Eclair: 1, Froyo: 0]
fte - 0 to 879 [Default Eclair: 35, Froyo: 60] (Frame Tearing Effect, change this if you have tearing problems)
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Note: Certain things like the camera still don't work, since our Froyo ROMs aren't official.
Flashable ZIP - WiFi-N + 4G for all custom kernels based on toastcfh's GoDmOdE kernel (compatible with v5.2+)
Flashable ZIP - WiFi-N + 4G for stock/custom kernels (compatible with v5.1 and below)
Flashable ZIP - WiFi-N + 4G for the OTA kernel (NOT compatible with the kernel in this post)
*** REMEMBER! No one here is responsible if you damage your phone! ***
See the Evo, Droid X and Nexus One benchmarked together here: http://androidspin.com/2010/06/25/droid-x-vs-htc-evo-vs-google-nexus-one-in-benchmark-face-off
Want NenaMark1? It usually doesn't show in the Market, so get it here: http://nena.se/downloads.html
Awesome, just flashed and it is soo smooth, thank you devs.
This works great for me.
Not really related to this but my phone locks up when I change the cpu frequency with setcpu. EDIT: (How do I overvolt the phone?)
Oh and yes I do get 50hz.
Is there 2.2 support or no
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Nope I wish there was. Droid X skin + 50hz would be very cool.
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Second this question..I'm loving the EvolutionX froyo rom and would be sweet to get this baby on board with froyo.
Does this work for Epson panels too?
This works great. Touchscreen SEEMS a bit more responsive in in multitouch vis test. Grounding issue is nowhere near as bad, but still there. If you pull the same trick that everyone is doing to test grounding problem, you won't notice it at first, and very rarely will it stop sensing you finger all together, but it definitely does cut out for an instant every now and then, and I had it drop visibility where it normally does a few times for a split second.
Epic delete
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Can you zip your modified files and post them too? Source would be nice
sweteg said:
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Click to expand...
Click to collapse
This thread was made to avoid the clutter from the Godmode thread.
Thanks for the excellent dev work!
You might want to add to the first post that this kernel breaks 4G. it will turn on but not able to find any network.
Other than that, works as described
The device feels so much smoother!
Great work! I get 52 in fps2d, 680 in quadrant, and 51 in gears. I can't wait until this is completely fixed but I'm loving it and the undervolt and oc patches are awesome additions.
automatic brightness still does not work with this kernel though. At least not for me. Is it possible I have a different light sensor as no custom kernel has worked with auto brightness yet and other reports say it works just fine.
Also... fps2d spikes into 99 fps and at one point I watched it flash past 100
Definetly works
Installed the kernel and got over 50 fps on my nova panel i have hardware config 002 it runs much much smoother thanks devs for the hard work.
wow this kernel is insane, I mean FPS hack and overclock hack without force closes...wow is all I can say. Used the OC widget and it detects the oc clocks quickly.
Man if this kernel makes it to Froyo..Evo will be truly evil
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Mrtankjump said:
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Click to expand...
Click to collapse
My Evo has an Epson panel so I can't use this fix but, my understanding was that this method didn't cause the tearing like we saw from Toast's custom kernel on Epson displays, so your problem might be something else and not necessarily the fps cap being raised.
Thanks for the kernel, but I still have one big problem- my battery still will not charge with this kernel installed. It will only charge when I turn off the EVO and turn it back on. But as soon as I unplug and replug it in, it will look like it charges for 5 seconds, then the orange light shuts off and it stops charging. I've enclosed a dump of my dmesg. Can someone please take a look at this?
Evo Switch v1.1.1 NovaFreq v1.2.1
(APP NAME CHANGED TO SOMETHING MORE APPROPRIATE)
This is an Android application developed to change the panel frequency for Novatek Panels for the Sprint HTC EVO 4G, in conjunction with ffolkes' Novatek Kernel and netarchy's Kernel,
and any kernel that has maejrep's T2 Interface built in. Every device is different, and with that, those specified kernel's default settings may or may not be optimized with your device.
With this application, you can change those settings on the fly and find the best setting for your device.
[ Please use this application with extreme caution! I am not responsible for any damage this may cause to your device. ]
Requirements:
-HTC EVO 4G
-Android 2.1 +
-Any custom kernel that is built off of toastcfh's htc source
-Novatek Panel
-Root Access
Uses:
-Use as an fps frequency turbo switch for when you need extra fps.
-Use as a debugging tool to test frequencies.
-Use to keep frequency settings even beyond reboots. (new)
Settings:
-340 [Stock] is how HTC intended the EVO to be. This frequency works out to 61hz, but we are capped at 30hz.
-370 [Kernel Default] sets the panel frequency lower than stock, yet provides most around 55fps.
-250 [Stable High Freq] sets the panel frequency higher than stock, which usually gives around 40fps.
-400 [Stable Low Freq] - V2's setting.
-Favorite Setting - Find the most stable setting, and if it's not one of the listed, then "Set Favorite".
-Sticky Settings - Now you can reboot and not have to re-apply your settings!
Custom Setting:
You can put arbitrary settings here, but be warned this may mess up your screen, but usually you can reboot your phone
to change it back to default. Minimum Recommended: 250 Maximum Recommended: 999.
Please do not go lower then the minimum recommended of 250, nor higher than the maximum recommended 999.
To Do:
-Favorite Setting - So you can save the best setting for your device. 07/04/10 - Done!
Change Log:
-Changed app name from Evo Switch to NovaFreq (Novatek Frequency / Freek)
-Totally redid code, should be more optimized.
-Frequencies stick beyond a reboot
-Changed a few of the defaults
-Changed back sleep time to 500ms so the current displayed setting can update (v1.2.1)
Don't be alarmed if you see NovaFreq running in the background. To be able to sticky settings beyond a reboot, NovaFreq has to be run at boot up.
After that you can kill NovaFreq if you want, android will kill it when needed so don't worry.
Thanks To:
ffolkes, netarchy, maejrep, toastcfh, halfline, Cicitrize, geyes30, kpkimmel, joeykrim, and many others involved in trying to uncap the EVO.
Reserved...
Reserved again.
woah, this is badass. I will check it out soon
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Awesome!! This is the first time I've been able to break 30 fps! (thanks to your app!)
I'm on Froyo and the v4 had never worked, but now v4 + high frequency with your app = 40 fps.
I love you.
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Great little app, I would recommend users experiment with the values just ever so slightly for optimum performance. Using the default value of 361 netted me about 50-51 fps, whereas using 365 nets me about 54-55. Not a huge bump, but even a little bit is nice
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
timgt said:
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Click to expand...
Click to collapse
Yes, I think V2 was 400.
madunix said:
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Click to expand...
Click to collapse
Every custom kernel does not have a working camera, because we do not have the source code for it. When HTC finally releases the source code, then we will be able to fix the camera.
antiphon said:
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
Click to expand...
Click to collapse
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Well done!! Thanks
AssassinsLament said:
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Click to expand...
Click to collapse
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
antiphon said:
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
Click to expand...
Click to collapse
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
maejrep said:
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
Click to expand...
Click to collapse
Yep, that's why I had to put in a "sleep" command in my app so that the system could process the change and update the app on if the register changed or not. Thanks for the interface maejrep!
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Force close only.
apollooff320 said:
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
VoXHTC said:
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Click to expand...
Click to collapse
Sorry, maybe I forgot to change the version in the app, 1.1.1 should be the only one linked in the original post.
Sprockethead said:
Force close only.
Click to expand...
Click to collapse
Do you meet the minimal requirements on the original post? Because you have to be running a custom kernel with the T2 interface in it.
wont recognize
im not sure whats wrong, i downloaded this on my phone and it says it dosent recognize the file i downloaded
As title says :
Which one is better for underclocking your processor ?
Im running on ROM and KErnel in my signature..
Thanks in advance
Laynee1
145 views with no replies lol..
To directly answer your question SetCPU is very user friendly and very basic, if your only changing the clock speed then sure, that's the way to go.
They both have their pros and cons. SetCPU has great profiles to setup for screen off, low battery, even certain times but limited and more tedious for changing voltages. The app in itself is well built, looks tidy and super user friendly. System tuner has all the same features but less custom profile options and in *my opinion* has an ugly interface. If you have the scripting for it, under volting is very easy on system tuner also.
I've used both very extensively and for how I have my phone setup system tuner is the best, hands down.
System Tuner suits all my needs. task manager, task freezer, task advanced details, cpu freq, voltage control and many other options. I have to admit the interface isnt really friendly, but you cand get used to it in no time.
System Tuner is better than SetCpu for advanced options
u can't undervolt the sensation with setcpu.. right?
Sent from my HTC Sensation XE with Beats Audio using xda premium
Laynee1 said:
As title says :
Which one is better for underclocking your processor ?
Im running on ROM and KErnel in my signature..
Thanks in advance
Laynee1
Click to expand...
Click to collapse
System Tuner Pro is, in my opinion, the best app for tuning CPU.
I am using IC 3.4 and all is ok.
As his question remains:
Which one is better for underclocking your processor ?
vitusdoom said:
As his question remains:
Which one is better for underclocking your processor ?
Click to expand...
Click to collapse
There is no difference between the apps if you consider JUST underclocking or overclocking ... If you take it like this, they are just mere interfaces to change some values ( which you can do by using let.s say root explorer and a text editor or a terminal emulator or etc. etc. )
System Tuner is better because it incorporates many other options, like task manager, app backup tool, uv tool, autokill features, ability to freeze apps and so on.
On the other hand, SetCPU has profiles, which can change the cpu values according to some predefined scenarios.
But, if the main question is which one is better for underclocking the answer is: whichever you like
+1 for System Tuner, the only thing missing from it that I do miss is
the profile settings that SetCPU has, fingers crossed the dev will
include it in a future update. Using System Tuner has also allowed me
to get rid of a couple of other apps that i used to sort out 'autostarts'
and a seperate terminal emulator.
snowblindd said:
There is no difference between the apps if you consider JUST underclocking or overclocking ... If you take it like this, they are just mere interfaces to change some values ( which you can do by using let.s say root explorer and a text editor or a terminal emulator or etc. etc. )
System Tuner is better because it incorporates many other options, like task manager, app backup tool, uv tool, autokill features, ability to freeze apps and so on.
On the other hand, SetCPU has profiles, which can change the cpu values according to some predefined scenarios.
But, if the main question is which one is better for underclocking the answer is: whichever you like
Click to expand...
Click to collapse
lol. you didn't get me. lets just say, he's asking for underclocking. but most of them are answering about undervolting
I prefere "echo" and manually init.d scripts
System Tuner 3.0
Just to let you know System Tuner 3.0 was released some time ago and provides improved CPU handling, new GPU, Gamma, MP, thermal controls on many custom kernels and a lot of other new or improved features (entropy, fstrim to name a few).
This is now a spawn of Android Tuner, and benefits from a larger user-base, improved stability and performance.
Given the recent hoopla in the blogosphere about how iOS places higher priority on User Interface actions than Android. I was wondering what ideas can be implemented in current Android or Linux kernels to get better UI response.
Overclocking or upgrading to a faster phone is the brute force way, a smarter way would be to give higher priority to user input instead of benchmark/multitasking score numbers. I think it makes sense to give the User input highest priority because in computation timeframes, user input is rare, and considering how important smoothness affects overall perception & enjoyment of a device, it's a good idea to allow other OS background tasks to take a backseat when the User wants to do something.
I'll start the discussion with two ideas I've implemented in a kernel recently that has shown improvements in UI response.
1. Switched to using SIO (Simple IO) scheduler (similar, but slightly lower benchmarks than Noop). Main difference is SIO prevents the system from hogging resources when large amounts of data needs to be read/written. It has a timeout so UI threads has a chance to run also.
2. Switched the touchscreen driver interrupt service request from using the general events workqueue (schedule_work()) to a dedicated workqueue (queue_work()). Touchscreen generated actions get to ride in the fast lane.
Any other ideas people have?
How bout some NSA IN THAT KERNEL
via Dan swagger
Usefull links, that clear things out:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
https://plus.google.com/105051985738280261832/posts/XAZ4CeVP6DC
http://blog.crazybob.org/2011/12/truth-about-android-ios-ui-performance.html
the thing is i may be using a note but when using ICS with apps that are updated for ICS, i feel its smooth enough. the real difference is i think ios uses completely different method for scrolling i.e. the bounce function and slight delay in finger recognition. same with ios touch recognition, it just somehow is better no doubt.
btw when i was miui with bounce it definitely felt smoother but although it wasnt ios smooth.
Sent from my Galaxy Note using XDA App
The main difference between ios and android is the fact they use ram in two totally different ways. Ios handles ram in a manner to make the user interface smooth as possible all the time while android frees ram to make multitasking better. The problem that android has is changing the way android handles ram to make the interface smoother for the user. They wont be able to for a long time because they have to do a total overhaul on the whole dalvik cache type setup that android uses.
Sent from my Incredible 2 using Tapatalk
i recently started using supercharger v6 which messes around with the ram and how it should be allocated for desired operations. I don't know if it's relevant but do you think it makes a difference and which setting would get you a better scrolling experience?
I liked the supercharger when I used the Droid Eris but since I've upgraded I get more redraws than without it. I used the 768hp I think.
Sent from my Incredible 2 using Tapatalk
you could edit the ramdisk to set more of a priority to rosie.apk or whatever launcher you use...just a thought
That would be the same as locking home in memory.
Sent from my Incredible 2 using Tapatalk
shad0wboss said:
i recently started using supercharger v6 which messes around with the ram and how it should be allocated for desired operations. I don't know if it's relevant but do you think it makes a difference and which setting would get you a better scrolling experience?
Click to expand...
Click to collapse
There are a number of issues that contribute to a "sluggish experience". The supercharger v6 script mainly keeps more memory free so that switching to new apps cuts down on the garbage cleanup of older apps. One of the downsides I've noticed with more aggressive lowmemkiller settings is a lot of apps get killed in the background when they need to stay for when users want to multitask.
The hardware acceleration route has downsides too from what I've heard, it requires more RAM per app just to have it enabled.
One of the articles posted earlier has good insight. Mainly because a lot of apps share a general events queue, and developers should not have a lot of blocking code in there, but developers make mistakes. The tools available for Android to develop and tweak UI performance seems lacking at this point.
How about SIGSTOPping everything else when you touch?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
does it work with samsung i9000?
Supercharger?
Sent from my Sabotaged Droid Incredible 2.
I find that either turning off cpufreq (by using the Performance governor) or increasing the lower frequency makes things a bit more snappy. For most governors, there's a delay between CPU load and the frequency being increased. This delay is usually noticeable if the CPU load is due to me working with the interface. By increasing the min frequency to, say 800mhz on a Nexus S, this makes things a lot more snappy than the default setting of 200mhz.
Another thing that helps with the smoothness (at least for me, in ICS) is the setting that forces GPU acceleration for all apps. For example, apps these days (well twitter and Facebook) have that pull down to refresh widget from iOS. Without forcing GPU acceleration, the rotating arrow animation usually hitches quite a bit, but is smoothed out with this setting on. This setting can be found in the developer options in the settings.
Hope these help,
- chris
Turning up the min CPU can cause freezes on some peoples phone though and using the performance governor can drain the battery quick. The reason the CPU scales up the way it does before it gets to max frequency is to save battery.
Sent from my Sabotaged Droid Incredible 2.
System tuner pro has alot of tweaking options that on memory use
those that use launcher pro can find a memory usage setting in launcher pro to.
disconnecktie said:
Turning up the min CPU can cause freezes on some peoples phone though and using the performance governor can drain the battery quick. The reason the CPU scales up the way it does before it gets to max frequency is to save battery.
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
Agreed, but the whole point here was to help improve UI responsiveness. Without rearchitecting the OS, a good way is to allow the CPU (which is busy sharing its resources with non-UI work) to react more quickly is to ensure the CPU is at a higher clock rate before the UI needs it.
As for battery life, it really depends on your usage pattern. If you have a lot of background processing going on, preventing the CPU from going to sleep when idle, you may be better off scaling back the minimum cpufreq frequently. If your CPU actually goes to sleep, give scaling things up a try. A handy tool you can use to see how often the CPU is sleeping is CPU Spy. To see which apps are keeping the CPU awake, there's a program called Better Battery Stats available on XDA and market.
As for stability, I don't mean over clocking the CPU...all I'm suggesting is to increase the frequency the CPU goes to when the screen is on, but nothing much is happening. This should still keep things within safe limits.
Hope this helps,
- chris
I find the interactive governor does a very good job of ramping to max right from idle (instead of waiting even a few ms like ondemand does). It assumes coming out of idle the CPU is starved. Then scales back once demand lowers. No fancy locking to min freq when screen is off (which can stutter some background apps).
There is many thing what can be done in the code of the applications. For example once I had a really sluggish app. It turned out that while I was dragging an item in the UI, the UI needed to be relayouted, and the draw calls were simply postponed: in android (at least that was the case before ICS) the drawing of the UI is delayed while the UI thread is too busy with events and layout requests.
To find these issues it's really useful to use traceview.
Hello everyone,
I've been using the cm9 release candidate since it was released, and still can't figure out how to make it snappy (I was on Apex before, and found it much more responsive). I'm not sure which the performance/memory management settings the Nexus S can handle well (there are lots of other threads for other phones, but I'm not sure if some of the settings require better hardware), so I'd appreciate it if anybody could tell me what they've found to be good for the following options:
Performance settings:
- Surface dithering
- 16bit transparency
Memory management:
- Allow purging of assets
- Kernel samepage merging
Misc. information that may or may not be relevant:
- Using Matr1x kernel (CFS, v21.0 I think)
- Processor is running at 200/1200 most of the time, ondemand governor (same settings that used to give me great performance on Apex).
- Also tried running Supercharger script, but it didn't seem to change things as much as it usually does
- Fixing permissions didn't fix it
- Battery life seems fine
- What I mean by "unresponsive" is that the launcher takes longer than usual to redraw and is laggy switching between windows, apps often force close or take forever to start up, and the browser reacts much more slowly to pinches, swipes, etc.
Thanks!
tl;dr: CM9 users, please share your performance + memory management settings. Explanations not required, though appreciated.
niiiiick said:
Hello everyone,
I've been using the cm9 release candidate since it was released, and still can't figure out how to make it snappy (I was on Apex before, and found it much more responsive). I'm not sure which the performance/memory management settings the Nexus S can handle well (there are lots of other threads for other phones, but I'm not sure if some of the settings require better hardware), so I'd appreciate it if anybody could tell me what they've found to be good for the following options:
Performance settings:
- Surface dithering
- 16bit transparency
Memory management:
- Allow purging of assets
- Kernel samepage merging
Misc. information that may or may not be relevant:
- Using Matr1x kernel (CFS, v21.0 I think)
- Processor is running at 200/1200 most of the time, ondemand governor (same settings that used to give me great performance on Apex).
- Also tried running Supercharger script, but it didn't seem to change things as much as it usually does
- Fixing permissions didn't fix it
- Battery life seems fine
- What I mean by "unresponsive" is that the launcher takes longer than usual to redraw and is laggy switching between windows, apps often force close or take forever to start up, and the browser reacts much more slowly to pinches, swipes, etc.
Thanks!
tl;dr: CM9 users, please share your performance + memory management settings. Explanations not required, though appreciated.
Click to expand...
Click to collapse
You don't need to mess with those settings.
Besides, if your applications FC, it's likely because of:
a) instability regarding your overclock
b) instability regarding the undervolt that matr1x kernel comes with
c) the fact v21 was canned due to being judged unstable by so many, upgrade to v22
d) all of these
Cheers
If you don't know what a setting does, don't change it. Messing with the CM performance settings if you don't know what you're doing is a great way to mess your phone up.
063_XOBX said:
If you don't know what a setting does, don't change it. Messing with the CM performance settings if you don't know what you're doing is a great way to mess your phone up.
Click to expand...
Click to collapse
are you completly retarded? there doesnt happen much when you change the settings there. you are talking like the settings are just for pros and he is a kid, lol. kernel samepage merging for example just "bonding" two similiar proccesses so they dont need too much ram.
Fensterbank said:
are you completly retarded? there doesnt happen much when you change the settings there. you are talking like the settings are just for pros and he is a kid, lol. kernel samepage merging for example just "bonding" two similiar proccesses so they dont need too much ram.
Click to expand...
Click to collapse
Are you? This thread has been dead for almost 3 months. The OP had his answer. Resurrecting this thread just to argue is incredibly pointless.