Wanted to share some info on ICS tweaking/tuning based on the following page.
http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/
I've implemented all of them and my ROM is super smooth and fast. Would be interested to see how others do with them.
Extract from site...
Here are just a couple of tweaks to smoothen one's UI experience in Android 4.0 Ice Cream Sandwich. (Remember these changes won't apply without a reboot and you will need a rooted device).
Improve UI frame rate and touch response:
On dual core devices:
In build.prop (found in/system/) set (It's probably already there under #Common Display Settings, just increase the value):
Code:
windowsmgr.max_events_per_sec=240
On single core devices either of the following are recommended:
Code:
windowsmgr.max_events_per_sec=120
or
Code:
windowsmgr.max_events_per_sec=150
240 seems to work fine on single core devices as well. You should probably try different values and see which one works best.
Disable kernel error logging:
Add this anywhere in build.prop -
Code:
ro.kernel.android.checkjni=0
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
Enable tile rendering:
(does not apply to Galaxy Nexus)
Whether this will work largely depends on the device and the chip it is using. If you are using a Snapdragon/Adreno based device, as far as I know, tile rendering has not been fixed yet.
For others, you might as well give it a shot (either that or it's already enabled like it is on the Galaxy Nexus.) The worst that can happen is messed up homescreen icon/widget rendering, which can be fixed easily by reverting the change. Tile rendering is a more efficient form of GPU composition, and boosts performance since each frame is split into tiles.
Add or change the following in build.prop:
Code:
debug.enabletr=true
Qualcomm specific tweaks:
Many recent ROMs will already have these but the following settings are recommended under #Qualcomm display settings in build.prop.
Code:
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
com.qc.hardware=true
Improve Scrolling FPS:
I don't actually know the best value for this, I guess try anything from 4000-8000 and see what happens. However, it adjusts how SurfaceFlinger handles scrolling input and can potentially improve FPS:
Add or adjust the following in build.prop
Code:
ro.max.fling_velocity=4000
Really Really Nice Find.
I implemented these into the build prop of MHX Superlite and now it runs even faster then before.
Would definitely recommend developers implement these if they haven't already.
I had most of the these build.prop edits since the release of my ROM! Its great too see an article! But ya i have those!
tehee said:
Really Really Nice Find.
I implemented these into the build prop of MHX Superlite and now it runs even faster then before.
Would definitely recommend developers implement these if they haven't already.
Click to expand...
Click to collapse
Instead of many different flavors of ROMs, this is really something I would like to see.
+1 to this and stuff like this into MHX's rom.
I have seen a few other tweaks and stuff but honestly I'm usually too lazy or incompitent to go in and bother to apply them myself. but I'd really like to see this in 4.3 of mhxs rom.
One thing I've noticed time and time again is that a lot of the scripts included in custom ROMs don't actually work. I'm not pointing fingers or anything. One thing I always do is read the scripts in init.d and then try to run them from an adb shell. You'll see errors and what-not if binaries are missing, directories don't exist, or worse yet multiple scripts with the same stuff, or even conflicts between scripts, etc. Makes my head spin from a troubleshooting perspective. Check build.prop for dupe entries as well. Sometimes you might think you set something only to have something towards the end supersede it.
Regardless, these tweaks make my launcher (Nova) ultra smooth. The EGL mod, I noticed, is exactly how Qualcomm packed their binaries. e.g. no CPU-level rendering.
appdroid said:
I had most of the these build.prop edits since the release of my ROM! Its great too see an article! But ya i have those!
Click to expand...
Click to collapse
I can see that, Antutu was showing me 6500! Not too shabby!!
. If you are using a Snapdragon/Adreno based device, as far as I know, tile rendering has not been fixed yet.
Does this mean this tweak wont work on the skyrocket? or it isnt yet on the skyrocket and i should do it?
InstigatorX said:
Improve UI frame rate and touch response:
On dual core devices:
In build.prop (found in/system/) set (It's probably already there under #Common Display Settings, just increase the value):
Code:
windowsmgr.max_events_per_sec=240
On single core devices either of the following are recommended:
Code:
windowsmgr.max_events_per_sec=120
or
Code:
windowsmgr.max_events_per_sec=150
240 seems to work fine on single core devices as well. You should probably try different values and see which one works best.
Click to expand...
Click to collapse
None of that is in my build.prop file...
If it's not in my system, can I safely add it ? I'm running Smooth ICE v3.1.
Yes
Sent from my SAMSUNG-SGH-I727 using xda premium
bdbx18 said:
If it's not in my system, can I safely add it ? I'm running Smooth ICE v3.1.
Click to expand...
Click to collapse
Yes. Sorry for the double post. Fat fingers.
Sent from my SAMSUNG-SGH-I727 using xda premium
check out this thread. i wonder if any of these can be added as well?
http://forum.xda-developers.com/showthread.php?t=1563239
---------- Post added at 09:27 PM ---------- Previous post was at 09:07 PM ----------
so i tried some of these. must have done an edit wrong in the build.prop. i added another qualcomm specific string i found and things went bad quickly.
phone reboots past the splash screen, but the screen goes dark and does not turn on, even though adb can still see it
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
pushing the original build.prop does nothing
clearing everything from the phone did not work, and after that it would hang at the spash screen and adb would not recognize.
now it will no longer charge from the kernel, the battery icon pops up for a second and immediately disappears and the screen stays black. the only sign of life is a series of 4-5 buzzes when holding down the power button. button recovery no longer works. download mode does though if you get lucky with the right timing.
---------- Post added at 10:04 PM ---------- Previous post was at 09:30 PM ----------
i dont know what i did, but i really messed something up. got lucky and odin'd back to ICS leak.
i guess just be careful when messing around with this. i thought just pushing the original build.prop back to the device would work, but I was wrong.
orlandoxpolice said:
check out this thread. i wonder if any of these can be added as well?
http://forum.xda-developers.com/showthread.php?t=1563239
---------- Post added at 09:27 PM ---------- Previous post was at 09:07 PM ----------
so i tried some of these. must have done an edit wrong in the build.prop. i added another qualcomm specific string i found and things went bad quickly.
phone reboots past the splash screen, but the screen goes dark and does not turn on, even though adb can still see it
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
pushing the original build.prop does nothing
clearing everything from the phone did not work, and after that it would hang at the spash screen and adb would not recognize.
now it will no longer charge from the kernel, the battery icon pops up for a second and immediately disappears and the screen stays black. the only sign of life is a series of 4-5 buzzes when holding down the power button. button recovery no longer works. download mode does though if you get lucky with the right timing.
---------- Post added at 10:04 PM ---------- Previous post was at 09:30 PM ----------
i dont know what i did, but i really messed something up. got lucky and odin'd back to ICS leak.
i guess just be careful when messing around with this. i thought just pushing the original build.prop back to the device would work, but I was wrong.
Click to expand...
Click to collapse
Yeah, editing the build.prop can be tricky. Never had what happened to you specifically, though. Here's link to my build.prop if u want use. Works well for me.
https://www.sugarsync.com/pf/D7693548_724_777039871
Sent from my SAMSUNG-SGH-I727 using xda premium
How come android doesn't have a registry? Something like how wm used to have.
[ ICS-Leak 4.0.3] SkYrOcKeT
WhatzinyourphonE said:
How come android doesn't have a registry? Something like how wm used to have.
[ ICS-Leak 4.0.3] SkYrOcKeT
Click to expand...
Click to collapse
Linux doesn't have registry by design so that's why android doesn't have it. They will never have it, it's the way that the OS is designed, everything is in files inside.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I added a debug.qc.hardware=true line as well as defining a min and max surface flinger and I'm pretty sure that effed it up.
Sent from my SAMSUNG-SGH-I727 using xda premium
not to sound stupid.
What do I add the the build.prop if these fields are not there?
tjsooley said:
not to sound stupid.
What do I add the the build.prop if these fields are not there?
Click to expand...
Click to collapse
If you open up build.prop you will see lines of code like these:
windowsmgr.max_events_per_sec=120
You change the value (true/false or number) so that it works differently or add a new line.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1236732
Presbycusis said:
If you open up build.prop you will see lines of code like these:
windowsmgr.max_events_per_sec=120
You change the value (true/false or number) so that it works differently or add a new line.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1236732
Click to expand...
Click to collapse
the thing is I dont have any of the lines in my build prop
MicroNotes​Android 2.1+​
Hello people!
I am new to XDA so first i would like to say Hi.
MicroNotes is my first android app/widget that i have made and so i would like some feedback.
DESCRIPTION
From planing out your daily schedule to writing a to do list for the day, MicroNotes for Android is your #1 Notepad app for your Android device.
FEATURES
-Multiple line notes, good for making lists
-Works on android Gingerbread(2.1) - android Ice-cream Sandwich(4.0.4)
-Updated almost daily
-Looks good on all types of devices (Android 2.1 - 4.1)
-No bugs
-Simple
-Dose not need a internet connection
Lots more to come!
Check out my portfolio at: http://besieger.ensocms.com
INFORMATION
This is a widget not an app, when you place the widget on your screen you will be taken to a app like screen where you can type your note and save it.
Should you need to edit your note simple tap the existing note on the screen and edit then press save to save the changes.
Any one interested in trying it here is a link: Link
If there is anything wrong with my post please let me know so i can change it
Thanks for your times guys,Josh
"wrighting" should be spelled writing.
I'd like to know more: when you click the widget, does it open the main app or does the keyboard appear on the launcher screen?
Also, is there a main app in the first place (since you're just saying "widget")?
---------- Post added at 11:48 PM ---------- Previous post was at 11:37 PM ----------
Ok, installed it. It's only a widget (make sure it's installed to the phone memory). Simple to use, simple interface, non existent loading times. Clicking the widget opens a screen where you can change the note. Some themes/transparency would be nice, other than that, it does what it says it does.
GermainZ said:
"wrighting" should be spelled writing.
I'd like to know more: when you click the widget, does it open the main app or does the keyboard appear on the launcher screen?
Also, is there a main app in the first place (since you're just saying "widget")?
---------- Post added at 11:48 PM ---------- Previous post was at 11:37 PM ----------
Ok, installed it. It's only a widget (make sure it's installed to the phone memory). Simple to use, simple interface, non existent loading times. Clicking the widget opens a screen where you can change the note. Some themes/transparency would be nice, other than that, it does what it says it does.
Click to expand...
Click to collapse
thanks for looking at my app, what do you mean by add themes?
besieger1 said:
thanks for looking at my app, what do you mean by add themes?
Click to expand...
Click to collapse
Different background/text colors, perhaps optional rounded corners, etc.
I installed ViperDHD (not sure if that's relevant or not) and it's working perfect, absolutely no complaints. There's only 1 minor annoyance and I'm sure its user error but.. I can't figure out how to set my wallpaper to portrait mode only. It currently tries to set all my wallpapers to work in both portrait and landscape which prevents me from getting the wallpaper I want. How can I get my phone to show only the portrait box when adding a wallpaper? I've never ran into this problem on any other rom. Is it a limitation of Sense 4? Thanks!
In case someone else runs into this problem someone in the DesireHD thread suggested a app called "Picspeed". It added the ability to set wallpaper in different configurations.
Hi All,
This is Tamilmani Mohan, i am beginning in Android development. I want to implement vertical infinite image scroll effect in android app. We are referred the Expedia app.
In Expedia , Images are scroll infinitely both left and right side. I don't know how to implement this type of effect in Android .
Could you please any one help me in this issue ?
Is there any sample , please update me. It will helpful to me.
Thanks
Tamilmani Mohan
Go to developer.android website to learn the basics first, of using xml and xml ids firstly.
after you learn the basics just drag and drop imagescroll to your xml file, set it to verticle.
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
Go to developer.android website to learn the basics first, of using xml and xml ids firstly.
after you learn the basics just drag and drop imagescroll to your xml file, set it to verticle.
Post your model & display type number
Mine is ta1121
Display is novatek 06
Location India
sameermehta2 said:
Post your model & display type number
Mine is ta1121
Display is novatek 06
Location India
Click to expand...
Click to collapse
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
sameermehta2 said:
Post your model & display type number
Mine is ta1121
Display is novatek 06
Location India
Click to expand...
Click to collapse
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
I have also the same model which you have.
humanzqzr said:
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
I have also the same model which you have.
Click to expand...
Click to collapse
Yes if you asking the settings( gear icon next to edit button/pencil,) toggle from notification bar swipe down,it's dark when pulled down in dark theme,the gear is white/grey but all is dark in background
humanzqzr said:
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
Hi sameer, just a off topic question. Does your quick settings page has black background when you select dark theme in display settings?
I have also the same model which you have.
Click to expand...
Click to collapse
Try and use any simple dark wallpaper ,set the theme to dark ,restart the phone and see,don't use the wallpaper from the wallpaper app that is downloaded when you select them,just for checking purpose ,on my set all is well
This Phone has VERY SERIOUS SCREEN Problem ,
Mine got cracked in under 10 Hrs from 1 feet fall .,.This is not even Corning glass 1 ,,
I have used CG3 devices and all or them are way stronger than this ... Logged the call for replacment
Ut doesn't even have gorrila glass. And huge notch. Every other thing is looking perfect
avi_loveindia said:
This Phone has VERY SERIOUS SCREEN Problem ,
Mine got cracked in under 10 Hrs from 1 feet fall .,.This is not even Corning glass 1 ,,
I have used CG3 devices and all or them are way stronger than this ... Logged the call for replacment
Click to expand...
Click to collapse
It has NEG (Nipon Electronic Glass) protection which is good enough. And you should know that even GG is not almighty and it can break easily if the phone falls in "the right way". I've broken a GG3 by pushing my phone from a coffee table on tiles without any protection. It hit the corner and two long lines appeared.
You were just unlucky.
Sent from my Mi A1 using Tapatalk