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
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?
Just a small quick and dirty app that let you change some of the GTA3 default settings.
Original settings are backed up to (GTA3 Folder)/files/GTA3/gta3.gtsettingslauncher.set. If the app completely fails or you want to use the original settings after uninstalling the app, just copy this file back to (...)/gta3.set.
When your gta3.set is missing, please start the game and go to the display options. Change some settings and then hit "restore defaults". Then try again and start the settings app.
If there is still no settings file, get one from this forum (e.g. http://forum.xda-developers.com/showpost.php?p=20950484&postcount=29) or google. After launching the game with the downloaded settings file go to the in-game display settings an click "restore defaults". That should fix some problems with screen width and height.
Available Settings:
Shadows: On/Off
Lighting: On/Off
Resolution: High/Low
Rendering Distance: 18 Steps
Blur: On/Off *
* Blur is not working for me. The setting is always disabled when starting the game. Maybe it is working on other devices (Tegra?).
Currently only tested on I9100 with GTA3 German. Please let me know if it is working or not.
Changes:
2012/01/03 - v1.4:
catch more exceptions
changed launcher, it now hopefully will find the target more often
2012/01/02 - v1.3:
added another external_sd path (now searching in "/mnt/sdcard/external_sd/Android/data/", "/mnt/sdcard/Android/data/", "/mnt/sdcard/external_sd/data/" for package)
2011/12/31 - v1.2:
added launcher icon
added blur setting (which might have no effect)
changed namespace - please uninstall the old version manually. I used an example package found on the internet as skeleton and forgot to change it, sry
2011/12/29 - v1.1:
added external_sd to search path
Make sure to download the LATEST version.
Thankyou excellent work dev,works great.
My device is zte skate
And at 900Mhz on Atomic 2.5 rom,
Chainfire reduce texture size and quality,
With this app you have created,
It is running good now.
I just get instant force close when trying to run this. I was looking to try the lower resolution for performance increase.
I'm using a rooted vibrant (t959), with a custom 2.2 rom
kxlling said:
I just get instant force close when trying to run this. I was looking to try the lower resolution for performance increase.
I'm using a rooted vibrant (t959), with a custom 2.2 rom
Click to expand...
Click to collapse
Can you please post the full path to the original gta3.set? I think the path can't be found.
hacksteak25 said:
Can you please post the full path to the original gta3.set? I think the path can't be found.
Click to expand...
Click to collapse
http://i2.photobucket.com/albums/y8/kxlling/2011-12-29_130706.png
The path is in that screen shot.
Added "external_sd" to search path. Please try again with the new version.
+ 1
Works great now, thanks for the fix. Almost lag free now. Thanks!
thanks for sharing, i hope this is worked on my device
Works perfect on the HTC Desire HD! Thank you! :>
Sent from my loved HTC Desire [email protected] <3
Works perfect on my Sensation! Thank you!
I've attached two screenshots. One with defaultsettings and one with tweaked settings.
I get forced close also on zte blade (orange san fran)
But the game runs any ideas?
arnookie said:
I get forced close also on zte blade (orange san fran)
But the game runs any ideas?
Click to expand...
Click to collapse
When does it crash? Right after starting the settings app or when you try to "Save and Start"?
Can you please also post the path to your gta3.set? Maybe it is a path problem again.
Awesome!
Work perfectly on Xperia play!
It crashes just after starting app.
I fixed it I had to download and copy the file called gta3.set into the correct folder as no file of that name was in the data folder. After I did that the patcher worked fine. :O)
Seems some phones don't create the gta3.set file. Maybe you could include one with the patch or make it auto generate one for people like me. Thanks for the patch. ;0)
Awesome app. I was wondering though, is it possible to integrate more features/mods in the app?
Theres a post on the main page of xda showing mods, also another thread in this same section for gta mods like lamborghini/audi/VW cars, coca cola machines, better texture packs, etc. That would be crazy if you can add those features so we have a all in one mod app for the gta game and can apply them without much messing around. Hopefully that would even help more people add more content to make the game experience even better.
This worked great on my Asus Transformer!
I was surprised to find out the default settings were set so low. Even on my Tegra 2 device. It looks SO much better now.
Thanks for this - works great on my Desire Hd and Haipad M7S - draw distance on low means I can have the effects on and it runs fine on the Desire!
where should i paste this file?anywhere in my sdcard?anyone?plss..
edit: got it work..thanks OP.. ^^
Added a launcher icon and the blur setting. Bluring is not working on my i9100 (it is just disabled by the game while launching), but maybe it will work on other chipsets.
Download is appended to first post.
MicroNotesAndroid 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.
Hello! Recently,i checked phone name OnePlus One. One of the things which i like at it,is that gesture which launch camera by drawing letter "C" while screen is off.I will like to see this feature in kernel for our device.Let me explain my idea:
1.Implement gestures in kernel (gestures while screen is off).
2.Make a "section" in Novathor Settings named "Gestures".If is possible,in this section will be great options like these:
a) Choose a gesture: we draw it (only letters).
b) Assign to that gesture an action: we choose that action (actions like: launch an app,put alarm off/on etc. or even support for Tasker).
I know that:
-this feature will drain some more battery,but personally i dont care about +/- some mins.
-is hard to do these.
-you developers have a life and you are busy,but if you have free time,maybe you accept my "challenge".I think a feature like this,will give all Galaxy S Advance users a better experience.Thank you to all developers which done and still doing awesome things for our beloved phone and i hope we can see this feature one day.
If you will do it,please let us know
Up... I just want make sure that all developers saw it
Kernels for KK
There is only 1 kernel for kitkat and that to for AOSP rom
Please provide with more kernels for kitkat for more custom roms
and please do take care for the BATTERY LIFE
krazzykuldeep said:
There is only 1 kernel for kitkat and that to for AOSP rom
Please provide with more kernels for kitkat for more custom roms
and please do take care for the BATTERY LIFE
Click to expand...
Click to collapse
Please, tell us why you need a wide choice of different kernels..
Toni5830 said:
Please, tell us why you need a wide choice of different kernels..
Click to expand...
Click to collapse
Because the stock kernel drains the battery a lot and the custom kernel (for KK) is only available for AOSP rom and i use carbon rom
Toni5830 said:
Please, tell us why you need a wide choice of different kernels..
Click to expand...
Click to collapse
Why not ? Another kernel means another people, another people means another ideas.
@mkaluza : Maybe you are interested in this.
krazzykuldeep said:
Because the stock kernel drains the battery a lot and the custom kernel (for KK) is only available for AOSP rom and i use carbon rom
Click to expand...
Click to collapse
Are you sure it's because of the kernel? I installed Carbon once and I like most of it except that it had a bug in surface flinger that caused it to spin and drain battery, so I dropped it. Connect the cable, log in with adb, turn the screen of and start top is you see surface flinger taking more than a few % of cpu time than it has this bug. Anyway - I use Vanir now and it's near perfect, even on stock kernel. Once we figure out the problem with wifi, you can also use my custom kernel - just follow this thread
http://forum.xda-developers.com/galaxy-s-advance/orig-development/kernel-mk-kernel-t2978377
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
King ov Hell said:
Why not ? Another kernel means another people, another people means another ideas.
Click to expand...
Click to collapse
This mostly means more mess... More unfinished, unstable kernels and a total chaos for a newcommer who just wants a stable non oem fw/kernel.... That's what I always found when I came to xda after some break and with no time to do a Phd on this stuff and it always ended up the same way (that is building my own kernel and a lost week of time :/) There's too little cooperation and coordination betweend devs, but that's a completely different story.
---------- Post added at 05:09 PM ---------- Previous post was at 04:48 PM ----------
Force said:
Hello! Recently,i checked phone name OnePlus One. One of the things which i like at it,is that gesture which launch camera by drawing letter "C" while screen is off.I will like to see this feature in kernel for our device.Let me explain my idea:
1.Implement gestures in kernel (gestures while screen is off).
2.Make a "section" in Novathor Settings named "Gestures".If is possible,in this section will be great options like these:
a) Choose a gesture: we draw it (only letters).
b) Assign to that gesture an action: we choose that action (actions like: launch an app,put alarm off/on etc. or even support for Tasker).
I know that:
-this feature will drain some more battery,but personally i dont care about +/- some mins.
-is hard to do these.
-you developers have a life and you are busy,but if you have free time,maybe you accept my "challenge".I think a feature like this,will give all Galaxy S Advance users a better experience.Thank you to all developers which done and still doing awesome things for our beloved phone and i hope we can see this feature one day.
If you will do it,please let us know
Click to expand...
Click to collapse
I'm not interested. For me it's just a gimmick worth more as a marketing feature than a usability thing. Though - if it's on OnePlus than probably implementation of this can be found somewhere in CM sources.
Anyway, my pc can't build aosp, so even if I wanted, I couldn't. I'm busy with project zen and this will keep me busy for another 6-12 months (because I want to do it well and try to push it to aosp kernel), and if I ever get a life, this period will get even longer ;P
And you know - it's open source, which means that if you want it - do it Most things that most devs in OS world do is because _they_ need it, and if they have time and mood,they package it up, so that others can benefit as well. But in real life most things that have a wish list, also have a price list - that's just the way it is.
Hello guys,
Here is a simple video to show benchmark scores in Antutu between four devices:
- Nexus 7 2013: CleanROM 3.5 (Kitkat 4.4.4), ElementalX kernel
- Moto G Gpe: Stock rooted 4.4.2 Google play edition, stock kernel
- Xperia S: Stock 4.1.2, stock kernel
- Nexus 5: Stock 4.4.3, stock kernel
Link: http://www.youtube.com/watch?v=e8Q7PORuxi0
Thanks for watching !
Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
n01z said:
Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Well thank you !
Nice score :good:
lulu14150 said:
Well thank you !
Nice score :good:
Click to expand...
Click to collapse
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
n01z said:
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Thank you for sharing your configuration !
My Nexus 7 2013 configuration:
- ElementalX Kernel (1,7GHz CPU, 490MHz GPU and a small undervolt --> Perferct for daily use)
- Rom CleanROM (just with Forced GPU 2D rendering in Developer Options)
Score between 26k and 27k