Related
HD Tweak & advanced config good for hd2?
I think advance config is good but hd tweak,will this soft improve performance or do we need HD2 tweak because of hardware?
I've done it, I don't notice any improvements. But thats maybe because of the huge speed improvement.
But it's still handy for some other tweas/settings
I just found this website with a fix for the keyboard lag in the stock browser:
smartadopter Wordpress -> TIP Improve Honeycomb Browser Speed
(I am new so not allowed to post outside links )
Basically it says:
1) as url type: about:debug
2) nothing will seem to happe.n BUT new menu options are available now
3) go to menu -> settings -> debug, and uncheck OpenGL Rendering
4) no more lag!
If this already floated around this forum, sorry. But if not, or for the people (like me) who missed it, enjoy!
I have not found any drawbacks of this fix. But if anybody find/knows any drawback/problem with this, please let me know.
Ill test this but im guessing scrolling speed will suffer as that uses the OpenGL.
Sent from my HTC Desire S using XDA App
Good advice. Will try it out now.
Tested and it works great. Scrolling is not affect either by this by the looks of it. Zooming works as well.
This fix isn't working. The input lag isn't gone completely, it's less noticeble, but it's still there.
And like someone mentioned before, scrolling isn's as smooth as before. Also YouTube videos don't work.
All this fix does is turn off hardware acceleration in the browser.
Some things get better, others get worse.
sassafras
Scrolling is not as smooth but I have no problems displaying YouTube movies.
But typing is a lot easier without (or with much less) lag.
So for me OpenGL rendering will stay off until the next update.
And lose my graphic acceleration? No thank you
No drawback?! Scolling looks like a freaking slideshow with that disabled ^^
Quick question for you guys... does the keyboard lag in Dolphin HD?
Not as much as the stock browser.
henkyie said:
I have not found any drawbacks of this fix.
Click to expand...
Click to collapse
For me the drawback is very obvious ... scrolling through a thread in this forum is horribly slow without OpenGL. But the keybord works like a charm.
I think, I will stay with Opera for forums and use the stock browser for the rest with OpenGL switched on ... loading times in Opera are much slower.
Thanks for the tip though.
I notice objects on the page rendering with every swipe as I move down the page ...probably why scrolling is not as smooth.
Strangely the scrolling lag has disappeared. So now I have less typing lag and little scrolling lag.
So until the next update I am a happy camper.
The only lag in typing I have left has to do with the auto complete function of the on screen keyboard.
This warrants further study (in the words of someone famous) because I'm seeing the exact opposite effect.
I've gone back and forth between this site and another forum having a similar javascript textarea form, comparing text entry with the "Enable OpenGL Rendering" box checked and unchecked in the Debug menu. On both sites, text entry is WAAAY faster using the dock keyboard with the box CHECKED. This is using the stock browser, BTW.
If I use a virtual keyboard (Swype for tablets in my case), it's still faster with OpenGL enabled but not nearly as fast as with the dock keyboard.
There must be some other factors involved however, since this behavior is not consistent. At times the keyboard (dock and virtual) seriously lags regardless of the Debug setting.
I sure hope Google (or ASUS) can fix this issue since it's hugely frustrating when the keyboard lags badly. In a few cases, I've just given up trying to post a message and pulled out my laptop instead of fighting the browser.
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.
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Hi,
I can not make the CWM, gives error.
However I did the manual procedure:
Put a unzip file: http://forum.xda-developers.com/attachment.php?attachmentid=976632&d=1333283208 in the file folder system/lib/egl/ and deleted the libGLES_android.so from egl folder.
I changed the build.prop, as the line was not added at the end dalvik.vm.dexopt-flags=m=y,o=v,u=y and recorded.
I did restart the smartphone,'ve played but honestly I do not notice improvements.
I look forward to more opinions.
Regards,
Jorge Moreira
Won't forcing gpu rendering for all apps reduce battery life?
Sent from my ST21i
Jorge Moreira said:
Hi,
I can not make the CWM, gives error.
However I did the manual procedure:
Put a unzip file: http://forum.xda-developers.com/attachment.php?attachmentid=976632&d=1333283208 in the file folder system/lib/egl/ and deleted the libGLES_android.so from egl folder.
I changed the build.prop, as the line was not added at the end dalvik.vm.dexopt-flags=m=y,o=v,u=y and recorded.
I did restart the smartphone,'ve played but honestly I do not notice improvements.
I look forward to more opinions.
Regards,
Jorge Moreira
Click to expand...
Click to collapse
Well you are right in a way..there were no improvements in the general ui fluidity..but my claim is based on the fact that the games which I tested(dead trigger , bad piggies and offload legends) were definately smoother.Lesser stutterings
Others please try it out and post you opinions
Sent from my ST21i using xda premium
satan89 said:
Won't forcing gpu rendering for all apps reduce battery life?
Sent from my ST21i
Click to expand...
Click to collapse
I didnt notice any such thing
Sent from my ST21i using xda premium
Didn't notice any improvements.Manually unpacked and set perms, rebooted.
balboarocky said:
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Click to expand...
Click to collapse
I also have noticed slight performance boosts in my Xperia Tipo. But I'm not sure if this will have any negative effects in the smartphone, because I guess that Sony would have set down this option by default for a reason
P.D.: Yes, I'm not english and I probably I would have mistakes, but i hope for you can understand me!
edit: What i have done is enable the option in Settings -> Developer options -> Force GPU rendering
this script like supermacy?
ICS already using hardware rendering instead of software rendering for the default setting. you might feel drastic change if you're using GB based rom. however, if you're using ICS based rom you won't feel anything. anyway, if you want to do it in easier way, go to setting>developer option>force gpu for 2d rendering.
balboarocky said:
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Click to expand...
Click to collapse
Force rendering is essential only for Old apps which don't use GPU. Forcing that will be effective only for those apps.
This will cause GPU to be running all time. Basic graphic tasks are handled by CPU very well. If there are lags then System uses GPU.
There may be slight performance improvement on cost of decreased battery life. So its better to leave it unmarked.
:good:
adrenalin engine
If you really want to unlock the potential of tipo use THIS
✔ Increase touchscreen sensitivity
✔ Less RAM usage through zipalign. | World first smart zipaligning
✔ Reduced /dbdata, /data, /sdcard usage of *.db files and faster database access. | World first smart sqlite optimizing
✔ Faster disk access through remount script (noatime, disabled barrier etc) | World first smart remounting
✔ Better network throughput from TCP tweaks and 3G tweaks
✔ Tons of prop tweaks
✔ Overall Better Performance and Battery Life
✔ Less lags through LMK Tweak and Various VM Tweaks
✔ Faster SDCARD Read/Write Speed
✔ Bypass website like thepiratebay.se
NOTE: There are two different zips for stock and CM..
I have been using Stock+Adrenalin for quite sometime now. It is stable.
Hit "THANKS" if I helped you