Add these in build.prop
Code:
##Tweaks##
#Battery Mods
persist.sys.shutdown.mode=hibernate
persist.radio.add_power_save=1
wifi.supplicant_scan_interval=220
ro.ril.disable.power.collapse=1
ro.config.hw_fast_dormancy=1
ro.semc.enable.fast_dormancy=true
ro.config.hw_quickpoweron=true
ro.mot.eri.losalert.delay=1000
ro.config.hw_power_saving=1
pm.sleep_mode=1
ro.ril.sensor.sleep.control=1
power_supply.wakeup=enable
ro.config.hw_power_saving=true
#Dalvik and Kernel Mods
persist.android.strictmode=0
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
ro.compcache.default=0
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=true
dalvik.vm.jmiopts=forcecopy
debug.kill_allocating_task=0
ro.ext4fs=1
ro.setupwizard.mode=DISABLED
dalvik.vm.heaputilization=0.25
dalvik.vm.heaptargetutilization=0.75
#Disable USB Debugging PopUp
persist.adb.notify=0
#Allow to free more ram
persist.sys.purgeable_assets=1
#Smoother video watching
video.accelerate.hw=1
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
#Better internet browsing & download speed
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
#Zram Mods
persist.service.zram=0
ro.zram.default=0
#UI Tweaks
persist.sys.ui.hw=1
view.scroll_friction=10
debug.composition.type=gpu
debug.performance.tuning=1
#Misc
persist.sys.gmaps_hack=1
debug.sf.ddms=0
ro.warmboot.capability=1
logcat.live=disable
#Force launcher into memory
ro.HOME_APP_ADJ=1
##Tweak Library by CrazyGamerGR##
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits
thx leather.face for init.d scripts
thx Xpid3r
in the Mod_1 this lines my tweaks included too:
Code:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
And in the Mod_2 this lines my tweaks included too:
Code:
net.tcp.buffersize.default=6144,87380,110208,6144, 16384,110208
net.tcp.buffersize.wifi=262144,524288,1048576,2621 44,524288,1048576
net.tcp.buffersize.lte=262144,524288,3145728,26214 4,524288,3145728
net.tcp.buffersize.hsdpa=6144,262144,1048576,6144, 262144,1048576
net.tcp.buffersize.evdo_b=6144,262144,1048576,6144 ,262144,1048576
net.tcp.buffersize.umts=6144,87380,110208,6144,163 84,110208
net.tcp.buffersize.hspa=6144,87380,262144,6144,163 84,262144
net.tcp.buffersize.gprs=6144,8760,11680,6144,8760, 11680
net.tcp.buffersize.edge=6144,26280,35040,6144,1638 4,35040
thx leather.face and Xpid3r!Download link https://www.androidfilehost.com/?w=files&flid=25851
most of those build.prop lines wont do anything for the n6.
simms22 said:
most of those build.prop lines wont do anything for the n6.
Click to expand...
Click to collapse
worth a try^^
CrazyGamerGR said:
worth a try^^
Click to expand...
Click to collapse
for me, not really, i know better. ive been messing with my android build.prop since 2008. but there are those that will try just about anything :silly:
simms22 said:
for me, not really, i know better. ive been messing with my android build.prop since 2008. but there are those that will try just about anything :silly:
Click to expand...
Click to collapse
me i was a flashcholic since 2010,and i deving on a lot of smartphones so crazy much,finnaly i m not a programmer but a confectioner ofc u know more than me i m not an owner of nexus 6 yet but maybe soon i ll be
simms22 said:
most of those build.prop lines wont do anything for the n6.
Click to expand...
Click to collapse
Speak for yourself. I changed those dalvik values and my phone is already Butter Smooth and at or very close to Beast Battery.
crachel said:
Speak for yourself. I changed those dalvik values and my phone is already Butter Smooth and at or very close to Beast Battery.
Click to expand...
Click to collapse
these tweaks are balanced and any1 got better battery life and butter smooth,i tested all so much times with my teamm8s and other ppl
crachel said:
Speak for yourself. I changed those dalvik values and my phone is already Butter Smooth and at or very close to Beast Battery.
Click to expand...
Click to collapse
we arent using dalvik on our nexus 6, we use art. and my n6 is butter smooth without. maybe placebo? and define "best" battery.. 3 hour sot? 4 hour, 5 hour, 6+ hours sot?
crachel said:
Speak for yourself. I changed those dalvik values and my phone is already Butter Smooth and at or very close to Beast Battery.
Click to expand...
Click to collapse
This made me laugh really hard, thank you
Sent from my Nexus 6 using XDA Free mobile app
crachel said:
Speak for yourself. I changed those dalvik values and my phone is already Butter Smooth and at or very close to Beast Battery.
Click to expand...
Click to collapse
Made my day :laugh:
I usually keep to myself these days, but these "tweaks"... omg.
they are some tweaks why so much raging...
CrazyGamerGR said:
they are some tweaks why so much raging...
Click to expand...
Click to collapse
Because they don't work on the Nexus 6 but you continue to mislead other users on that they work for the placebo effect.
As simms22 already pointed out.. the Nexus 6 (and other devices running Lollipop) use Android RunTime (ART), Dalvik is not existent in Lollipop.
If they do work as you claim, provide evidence and proof to backup your claims. Otherwise, people are just taking your "word" for it.
I want to see video evidence that these tweaks do more than fcuk all.
P.S. Dalvik like others have said doors not exist on lollipop so how can you tweak something which does not exist?
You may as well sell snake oil for all these tweaks are worth.
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Does not doors.
im going to jump in and defend the op.. at one point these "tweaks" were good to go. problem is that its probably still good, on much older devices, or non nexus devices. at least some of the tweaks, not all of them, for sure. like if i had a samsung phone, many would probably be good. but the op doesnt own a nexus, so he just didnt know.
simms22 said:
im going to jump in and defend the op.. at one point these "tweaks" were good to go. problem is that its probably still good, on much older devices, or non nexus devices. at least some of the tweaks, not all of them, for sure. like if i had a samsung phone, many would probably be good. but the op doesnt own a nexus, so he just didnt know.
Click to expand...
Click to collapse
on my nexus 4 never used tweaks and never tested my tweaks i used clean cm ,but on my nexus s i used them and i can tell it in older device u can see some different but maybe is a mind thing who knows,nexus 6 is a powerfull device no need boost but i post them here if any1 wonna test them to test them.
Some of these tweaks were good in 4.1-4.4.4 ROMS, but with 5.0 they are now useless.
CrazyGamerGR said:
on my nexus 4 never used tweaks and never tested my tweaks i used clean cm ,but on my nexus s i used them and i can tell it in older device u can see some different but maybe is a mind thing who knows,nexus 6 is a powerfull device no need boost but i post them here if any1 wonna test them to test them.
Click to expand...
Click to collapse
on older devices, yea, youll see a slight difference. but the differences are there. on newer devices, even if there are differences its too hard to actually tell.
simms22 said:
on older devices, yea, youll see a slight difference. but the differences are there. on newer devices, even if there are differences its too hard to actually tell.
Click to expand...
Click to collapse
ofc yeh me too i m on LP with my s5, art give good faster things and is not needed and not chance to change to dalvik to try them ,just for test i post these here to an 64 bit device
Related
Look at this here, guys. It's a device by HTC called Elixir sporting what seems to be Android OS 3.0:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Actually, if you know better, you know it's not true. All you need to do is edit the build.prop in /system and your phone name/version will show whatever you want.
This is just so you can be informed that version names/numbers/revisions, etc, can all be spoofed very easily.
Spread the word. Take anything related to "new android release" with a grain, a big grain, of salt.
http://twitpic.com/zemrr
I've come back to the future to show you this
Why would 3.0 start with a E if eclair already has one.
Ace42 said:
Why would 3.0 start with a E if eclair already has one.
Click to expand...
Click to collapse
Itches... must... explain.....
Although it's fake, you're looking for logic behind it. Anyway, let's pretend it were a real release, the version name is never shown (in stock builds anyway), instead, you see the version number (3.0 for froyo) and device model (Elixir). So Elixir would refer to the name of the fictional device (1.0 is to 3.0 as Dream is to Elixir?) by HTC.
jubeh said:
Itches... must... explain.....
Although it's fake, you're looking for logic behind it. Anyway, let's pretend it were a real release, the version name is never shown (in stock builds anyway), instead, you see the version number (3.0 for froyo) and device model (Elixir). So Elixir would refer to the name of the fictional device (1.0 is to 3.0 as Dream is to Elixir?) by HTC.
Click to expand...
Click to collapse
I see they are still using the 26I radio in .9 versions from now..... and in 14.96 versions from now. Hey, wait...
http://www.boygeniusreport.com/2010/01/23/htc-supersonic-get-its-screen-shot/
sitimber said:
http://www.boygeniusreport.com/2010/01/23/htc-supersonic-get-its-screen-shot/
Click to expand...
Click to collapse
that's why i posted this, I saw that and am simply appalled by what people will believe
jubeh said:
that's why i posted this, I saw that and am simply appalled by what people will believe
Click to expand...
Click to collapse
What exactly do we edit because this is what I see;
Code:
# begin build properties
ro.build.version.sdk=7
ro.build.version.release=2.1
ro.build.version.codename=REL
ro.build.type=user
ro.build.user=shade
ro.build.host=toxygene
ro.build.tags=ota-rel-keys,test-keys
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
ro.config.sync=yes
net.bt.name=Android
Try looking in the build.trout.prop, change what it says next to ro.device.model (or something similar)
All you need is love!
G1BRICKED said:
All you need is love!
Click to expand...
Click to collapse
Unfortunately no, you also need air, food and water.
G1BRICKED said:
All you need is love!
Click to expand...
Click to collapse
+1 to that
what a waste of space and time...
i think we all know the potential of photoshop which is way easier to fake things like this...
im just curious that a senior member started this senseless thread....
skarboy said:
what a waste of space and time...
i think we all know the potential of photoshop which is way easier to fake things like this...
im just curious that a senior member started this senseless thread....
Click to expand...
Click to collapse
did you even read the thread? the purpose of creating the thread was to show people how easy it is to fake things and to illustrate the importance of doing some fact-checking before you post threads about new builds or rumors.
and actually, it takes longer in photoshop to edit these things than it does to edit the prop, flash and take a ddms screenshot. unless you dont mind the photoshop job looking like an obvious fake that was done by a rank amateur.
kusotare said:
did you even read the thread? the purpose of creating the thread was to show people how easy it is to fake things and to illustrate the importance of doing some fact-checking before you post threads about new builds or rumors.
and actually, it takes longer in photoshop to edit these things than it does to edit the prop, flash and take a ddms screenshot. unless you dont mind the photoshop job looking like an obvious fake that was done by a rank amateur.
Click to expand...
Click to collapse
No need to reflash. Much easier than that. Edit the build.prop, put it back, reboot, and ddms that sh*t
skarboy said:
what a waste of space and time...
i think we all know the potential of photoshop which is way easier to fake things like this...
im just curious that a senior member started this senseless thread....
Click to expand...
Click to collapse
What a waste of space and time...
i think we all know that Junior Members do not compare to our infinite knowledge of the Android Operating System and we should not bother our selves to ponder about the posts of these foos! Word dog!
G1BRICKED said:
What a waste of space and time...
i think we all know that Junior Members do not compare to our infinite knowledge of the Android Operating System and we should not bother our selves to ponder about the posts of these foos! Word dog!
Click to expand...
Click to collapse
Some do, one that pops in my head at the moment is N_commander, you know the one who got camera working in eclair
Shiz he's still a junior. That guys a mother loving genius!
G1BRICKED said:
Shiz he's still a junior. That guys a mother loving genius!
Click to expand...
Click to collapse
Well when he got the drivers he was, not sure about now
Wait?! 3.0! Where do I dl this at? Does it work on my Nexus One?
Get my 345 quadrant standard benchmark out from the 800 range and up to par and ill happily donate you $10
Since 1.9.0 is based on the 2.2.2 releases I think that Steve probably considers that the 345 performance fix.
Truaim said:
Get my 345 quadrant standard benchmark out from the 800 range and up to par and ill happily donate you $10
Click to expand...
Click to collapse
Not Android Development
Please post in the correct Forums
Moving to General
lufc said:
Not Android Development
Please post in the correct Forums
Moving to General
Click to expand...
Click to collapse
Thanks. Anyone?
Substituting the Stage launcher with something else - ADW or LauncherPro - will help. Or simply migrate to StreakDroid 1.9.0.
Sent from my Dell Streak using XDA App
.cruiser said:
Substituting the Stage launcher with something else - ADW or LauncherPro - will help. Or simply migrate to StreakDroid 1.9.0.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
The whole point of asking for a 345 fix is that streakdroid wont stabilize and I like the new ui, or id be on 318.
Truaim said:
Get my 345 quadrant standard benchmark out from the 800 range and up to par and ill happily donate you $10
Click to expand...
Click to collapse
+1 I would donate!
Truaim said:
The whole point of asking for a 345 fix is that streakdroid wont stabilize and I like the new ui, or id be on 318.
Click to expand...
Click to collapse
Won't stabilize? Been using 1.9.0 since it came out with zero issues. Flashed back to stock 318 then did factory reset them flashed to streakdroid. Streakdroid runs great.
Dell Streak powered by Streakdroid 1.9.0
Spectre51 said:
Won't stabilize? Been using 1.9.0 since it came out with zero issues. Flashed back to stock 318 then did factory reset them flashed to streakdroid. Streakdroid runs great.
Dell Streak powered by Streakdroid 1.9.0
Click to expand...
Click to collapse
I guess that's awesome for you. Useless for the 25% of people that it doesn't work for. Again, looking for a 345 perfmod, not how much you love the Stevester.
Spectre51 said:
Won't stabilize? Been using 1.9.0 since it came out with zero issues. Flashed back to stock 318 then did factory reset them flashed to streakdroid. Streakdroid runs great.
Dell Streak powered by Streakdroid 1.9.0
Click to expand...
Click to collapse
I was on 345 before flashing 1.9.0 and really liked the new Stage UI. I subscribed to the Stage Video Widget service so I could buy, rent, and download movies. Now on 1.9.0, I can't get the Stage Video Widget to work. I think it requires the roxionow.apk to operate and it appears missing from the build. If I put the .apk from 345 onto 1.9.0 it will list the movies and info, but won't play trailers, movies, or download purchases. Also, some of my purchased apps from the market are missing when on 1.9.0. I'm back on 345 and everything is working. I'm hoping these issues will get sorted with the next StreakDroid update. Nothing is as fast and smooth as DJ_Steve's ROM's, but it would be nice to have a 345 perfmod to fall back on. I gladly donate to DJ_Steve's work and will continue to do so, but I would also donate for a 345 perfmod.
rsfinsrq said:
I was on 345 before flashing 1.9.0 and really liked the new Stage UI. I subscribed to the Stage Video Widget service so I could buy, rent, and download movies. Now on 1.9.0, I can't get the Stage Video Widget to work. I think it requires the roxionow.apk to operate and it appears missing from the build. If I put the .apk from 345 onto 1.9.0 it will list the movies and info, but won't play trailers, movies, or download purchases. Also, some of my purchased apps from the market are missing when on 1.9.0. I'm back on 345 and everything is working. I'm hoping these issues will get sorted with the next StreakDroid update. Nothing is as fast and smooth as DJ_Steve's ROM's, but it would be nice to have a 345 perfmod to fall back on. I gladly donate to DJ_Steve's work and will continue to do so, but I would also donate for a 345 perfmod.
Click to expand...
Click to collapse
Agreed. I wish streakdroid would work for me, but it doesnt lol. The happy medium for me is simply the fix for 345.
Sent from my Dell Streak using XDA App
$10 from me
$10 from me for performance fix on 345!
Last night I sneaked out of bed when my wife fell asleep and decided to explore 1.9.0.zip and found the following entries were added from the original build.prop of 345.
debug.sf.hw=1 (original =0)
dalvik.vm.heapsize=64m (original is =40)
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.hsupa.category=5
# other edits
ro.sf.lcd_density=160
wifi.supplicant_scan_interval=120
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
these were also added
ro.build.APP_RSS_WIDGET=1
ro.build.FEATURE_STAGE_UI=1
also I was able to dig this from the 1.9 zip
install/kor/perfmod/01data2ext (is this the perfmod we are looking for? if it is, how are we going to apply/install it? and where?)
honestly, I have no idea what these entries/files are. I have no knowledge whatsoever about android or any other platform and have no formal education/training on computers. So if there is anyone out there who can feel us calling for help to do some perfmod for 345, thanks in advance.
By the way, I edited my build.prop and added all those using root explorer, streak is still up and running. however, quadrant fell from 800 to 567, however, it feels and looks faster when using it. I don't know how is that but that how i think streak performs after editing the build.prop.
Try it at your own risk! I am not responsible for what may happen to your baby.
Edit:
It is now back to 819 on quadrant after rebooting twice and much smoother and have stronger wifi signal i believe.
$20 for 345/347 perf mod
I'd donate $20 for a 345/347 performance fix!
debug.sf.hw=1 (original =0)
Click to expand...
Click to collapse
Turns on hardware acceleration for the launcher/other processes (by default it's all done by the cpu instead of accelerated by the gpu)
dalvik.vm.heapsize=64m (original is =40)
Click to expand...
Click to collapse
Increases the heap size so apps can ask for larger chunks of memory(?)
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.hsupa.category=5
Click to expand...
Click to collapse
supposedly increases performence of 3g (i think it's snake oil since the original post suggesting it doesnt know what it does exactly? Just my opinion until someone does hard comparisons)
# other edits
ro.sf.lcd_density=160
Click to expand...
Click to collapse
this is stock value
wifi.supplicant_scan_interval=120
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
Click to expand...
Click to collapse
first two are somewhat self-explaniatory, last one is because dj_steve is in UK and that's his date formatting (if you use US160 it matches stock format)
these were also added
ro.build.APP_RSS_WIDGET=1
ro.build.FEATURE_STAGE_UI=1
Click to expand...
Click to collapse
Dont know offhand
I have been researching how to modify the boot.img...If i get things figured out I'll share for free
rsfinsrq said:
I'd donate $20 for a 345/347 performance fix!
Click to expand...
Click to collapse
R u guys finding 345 slow ? I am not talking abt benchmark numbers. Go by real time usage
What is the perf fix for ?
I have been using 345 for past 3-4 days and did not meet with any issues. i really mean any.
yes stock 345 gets noticebly slow. takes a few seconds sometimes just to open thing in a app which the app is already running.
paul89 said:
yes stock 345 gets noticebly slow. takes a few seconds sometimes just to open thing in a app which the app is already running.
Click to expand...
Click to collapse
Agreed. A modification to increase speed and smooth out lag would be great! All else seems to be fine on this ROM.
I've increased the performance on my 345 install using a tool from the market place.
***I bear no consequence if you misuse this tool, and you mess up your Streak!***
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I broke 900 using quadrant on my phone after some of these tweaks. Not bad for a stock image if you ask me.
Hello Captivators (shameless kang from Tegrak), happy hump day! This is TalonMTD, for CM7 and MIUI (and potentially other MTD based ROMs). This kernel has nearly all of the features of TalonDEV--and more coming sooner than later. Lets get straight into it!
Code:
Features
[LIST]
[*]Overclock up to 1440MHz/Undervolt for all frequencies (having only 5 frequencies undervolted seems most stable)
[*]Nexus S Framebuffer
[*]Voodoo Color v2 (No yellow tint!)
[*]Voodoo Sound v10
[*]Based on Linux kernel 2.6.35.13
[*]GPU overclock
[*]GPU Tweaks
[*]Bonus Governors: InteractiveX, Smartass, Conservative governor compiled as a module (not enableable yet)
[*]Bonus Schedulers: SIO, V(R), BFQ2r1, CFQ with tweaks
[*]Undervolted ADC and RAM
[*]Disabled Userspace governor
[*]Kangsterizer’s LED notifications
[*]Asynchronous I/O support
[*]Logcat compiled as a module, must be enabled via ‘logcat-on’
[*]Lowmemorykiller tweaks by kodos96
[*]Jhash3
[*]RAM tweaks
[*]Readahead tweaks
[*]Kernel HZ set at 250
[*]Disabled kernel printk for less overhead
[*]KTLO (Keep the Lights On)
[*]Samsung ARM fix
[*]16.25 lbs. of ext4 fixes
[/LIST]
Code:
#include <std/disclaimer.h>
/*
* While this build is heavily optimized, it is also capable of pushing your Captivate
* much harder. I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the current economic crisis. Please do some
* research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modificiations, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You can download it here...
0.0.3: http://dl.dropbox.com/u/9426310/TalonCaptivate-0.0.3.zip
0.0.2: http://dl.dropbox.com/u/9426310/TalonCaptivate-0.0.2.zip
0.0.1: http://dl.darkirc.info/public/talonmtd/TalonMTDCaptivate-0.0.1.zip
Source code: http://existz.darkirc.info/git/?p=kernel/talonmtd.git
Join us on freenode, channel #suckerpunch for support.
Many thanks to my co-devs eXistZ, kodos96, and zacharias.maladroit/zachy_md. (original Talon thread here: http://forum.xda-developers.com/showthread.php?t=1050206)
Huge thanks to
Supercurio
Teamhacksung
morfic
netarchy
TheEscapist
TK-Glitch
kangsterizer
And a great big final thanks to my testers, the great folks who put up with me breaking stuff and putting up a new build every 5 minutes, the guys who pushed me to greater heights to get stuff done:
Shoman94
Vivified (the great motivator)
Thegodsquirrel
Abee_13
lownox
Wanna say thanks? Buy me a root beer, and/or hit thanks.
My breath smells like normal breath.
0.0.3 (Maintenance Upgrade)
TONS AND TONS of ext4 fixes (more info here: http://existz.darkirc.info/git/?p=kernel/talonmtd.git;a=shortlog)
Minor upstream fixes including call volume tweak
0.0.2
Improved USB signal quality
OndemandX governor (offers sleep power consumption improvements over ondemand, not ready for the big time yet. Seems to cause 3D choppiness.)
Fixed enable_conservative script (released separately, coming soon)
Upstream DVFS fixes
Many more ARM fixes (for more information visit http://existz.darkirc.info/git/?p=kernel/talonmtd.git;a=shortlog and take a look at the ARM fixes)
Low power mode support (buggy)
Upstream touchkey tweak to prevent accidental button pushing
BUMPED OVERCLOCK VOLTAGES--People were reporting serious instability, so I bumped the voltages. This should fix the majority of issues.
init.d cleaning script from zacharias.maladroit
Major tweaks from Infuse to help with CPU scaling above 1000 MHz
ytt3r said:
This post isn't actually doing anything right now, so here's a picture of a kitten.
Click to expand...
Click to collapse
Do you have a duck on your face!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ytt3r has a duck on his face!!!
Nice job running awesome.
EDIT: This Kernel is what we needed here in MIUI land and I thank you on grabbing the reigns when we threw it at you.
Great job on incorporating the goods before releasing!
yay
10 char
I love you can't wait to test this.
Edit: what time zone midnight? Lolol
Sent from my i897 running MIUI 1.8.12 with NEO-12 test kernel.
Great to see Talon forks in CM7/MIUI. My 100% support for this.
Edit: Any plans for this to support i9000 as well?
lownox said:
Mine. Lol lol lol
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Running TalonMTD. See how fast it is?!
pikachu01 said:
Great to see Talon forks in CM7/MIUI. My 100% support for this.
Edit: Any plans for this to support i9000 as well?
Click to expand...
Click to collapse
Absolutely. I don't know when, but it'll be soon.
CM7/miui+talonmtd= dont blink or you might miss the transition
I have a question;
I liked CM7 until the battery drain made it near difficult to use; will using this Talon kernel possibly fix the drain issue? If so, then I'm going to consider switching back.
Can I ask what problems Gingerbread bootloaders cause?
RCDuke said:
I have a question;
I liked CM7 until the battery drain made it near difficult to use; will using this Talon kernel possibly fix the drain issue? If so, then I'm going to consider switching back.
Click to expand...
Click to collapse
Short answer--No. Long answer, while the kernel can not fix battery life completely, it can do something for it. Your problems won't be completely fixed, but will be somewhat mitigated.
DrDrrae said:
Can I ask what problems Gingerbread bootloaders cause?
Click to expand...
Click to collapse
Mounting SD card issues. There is a fix in the works.
RCDuke said:
I have a question;
I liked CM7 until the battery drain made it near difficult to use; will using this Talon kernel possibly fix the drain issue? If so, then I'm going to consider switching back.
Click to expand...
Click to collapse
To tell you the truth I'm getting the same battery life I had with Continuum. Some people are still getting drains depending on apps being used and such. There are so many variables to consider that I could tell you. You have to try it out and see how things go. Test different kernel settings in Voltage Control .... and monitor programs used to find what the culprit may be.
DrDrrae said:
Can I ask what problems Gingerbread bootloaders cause?
Click to expand...
Click to collapse
It has always been an issue until the latest round of Kernel updates. It mainly effects external SDCARDS but Vivified had a few intermittent issues with seeing the internel SDCard. (He wasn't running this kernel at the time).
shoman94 said:
To tell you the truth I'm getting the same battery life I had with Continuum. Some people are still getting drains depending on apps being used and such. There are so many variables to consider that I could tell you. You have to try it out and see how things go. Test different kernel settings in Voltage Control .... and monitor programs used to find what the culprit may be.
Click to expand...
Click to collapse
hah... maybe i was being a little too modest
xijar said:
I love you can't wait to test this.
Edit: what time zone midnight? Lolol
Sent from my i897 running MIUI 1.8.12 with NEO-12 test kernel.
Click to expand...
Click to collapse
EST, not sure if we're 5 hours back or 4 right now
Edit: I love you too
What would happen if you use it with GB bootloaders?
Sent from my GT-I987 using XDA App
Appreciate the quick response. Definitely gonna be up late tonight playing with this.
Sent from my i897 running MIUI 1.8.12 with NEO-12 test kernel.
dngen said:
What would happen if you use it with GB bootloaders?
Sent from my GT-I987 using XDA App
Click to expand...
Click to collapse
Already answered. Please read next time
ytt3r said:
Mounting SD card issues. There is a fix in the works.
Click to expand...
Click to collapse
I know these tweaks are available and nothing new. I wanted to share my experience. When I was using remICS, I exceeded 3hours of screen on time. But when I flashed CM9 or AOKP my screen time would always be around 2 and 20 minutes. My usage of the phone def plays a role, but for the most part, I have a set number of apps I use across all roms. So I looked at remICS build prop and added the "additional tweaks" to AOKP and CM9, and battery life was NOTICEABLE BETTER.
If anyone would like to test it out, add these at the end of your build.prop, reboot to recovery, and wipe caches.
For ICS/GB:
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
debug.performance.tuning=1
debug.composition.type=hw
debug.sf.hw=1
persist.android.strictmode=0
persist.sys.use_dithering=1
persist.sys.ui.hw=true
persist.sys.purgeable_assets=1
ro.com.google.networklocation=0
ro.kernel.android.checkjni=0
ro.config.nocheckin=1
ro.vold.umsdirtyratio=20
dalvik.vm.checkjni=false
dalvik.vm.execution-mode=int:jit
video.accelerate.hw=1
windowsmgr.max_events_per_sec=240
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
For JB:
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
persist.android.strictmode=0
persist.sys.purgeable_assets=1
ro.com.google.networklocation=0
ro.kernel.android.checkjni=0
ro.config.nocheckin=1
ro.vold.umsdirtyratio=20
dalvik.vm.checkjni=false
dalvik.vm.execution-mode=int:jit
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
**There have been reports that on JB, these tweaks have increased battery drain, but it is unconfirmed. Try running stock JB rom for a couple days, then add these tweaks and see if they improve.
***Most report these work on ICS/GB very well!
Ooh ooh! I had those in my ROM!
I am just fly as hell.
Though some of those are unneeded for AOSP based ROMs.
darkierawr said:
Ooh ooh! I had those in my ROM!
I am just fly as hell.
Though some of those are unneeded for AOSP based ROMs.
Click to expand...
Click to collapse
Iirc I added them from my old ROM...
Sent from my Galaxy Nexus using Tapatalk 2
MДЯCЦSДИT said:
Iirc I added them from my old ROM...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
And then I stole them. And added new ones.
And shut up whitey.
Thanks, I kept going back to RemICS as well since it had better battery life compare to other ICS roms. I'm gonna try it out with CM9 RC2 and see if I get similar battery life.
Hey :waves like idiot:
I'm just a regular ol' "noob", who's happy to even flash CM9 (and recently RC2) this week, but that certainly doesn't mean I know much else. For example, I dutifully followed instructions to erase both my batteries' memories, only to find them die that much quicker (d'oh).
That said, where exactly do I go to enter these numbers and whatnot? And is this proven to help my stats?
TracerBullitt said:
Hey :waves like idiot:
I'm just a regular ol' "noob", who's happy to even flash CM9 (and recently RC2) this week, but that certainly doesn't mean I know much else. For example, I dutifully followed instructions to erase both my batteries' memories, only to find them die that much quicker (d'oh).
That said, where exactly do I go to enter these numbers and whatnot? And is this proven to help my stats?
Click to expand...
Click to collapse
1) Copy the strings in the OP to your clipboard.
2) Using Root Explorer (or another file editor app), go to /system folder, scroll down to find build.prop file
3) Long-press on the Open build.prop file (make sure you switched Root Explorer to "read/write" from "read only" ), select "open in text editor" in the , paste the copied strings at the end of the file, then hit menu - "save & exit"
4) Reboot and enjoy your longer battery life. Your old build.prop file should be saved as build.prop.bak if you ever choose to revert.
just pulled 1 day 30 minutes with 2hr and 48 min of screen time on Aokp.. stock kernel.
Sent from my SPH-D700 using Tapatalk 2
Could some one explain what they all do? Some seem obvious but i would like to understand & learn before i add them to my build prop
dohturdima said:
1) Copy the strings in the OP to your clipboard.
2) Using Root Explorer (or another file editor app), go to /system folder, scroll down to find build.prop file
3) Long-press on the Open build.prop file (make sure you switched Root Explorer to "read/write" from "read only" ), select "open in text editor" in the , paste the copied strings at the end of the file, then hit menu - "save & exit"
4) Reboot and enjoy your longer battery life. Your old build.prop file should be saved as build.prop.bak if you ever choose to revert.
Click to expand...
Click to collapse
I have ES Explorer so I should be good. I'll give this a shot...
Would I have to do this with each of my (three batteries) when I (eventually) switch them?
zman519 said:
Could some one explain what they all do? Some seem obvious but i would like to understand & learn before i add them to my build prop
Click to expand...
Click to collapse
http://rk00064.blogspot.com/2012/04/all-android-tweaks-to-boost-performance.html
TracerBullitt said:
Would I have to do this with each of my (three batteries) when I (eventually) switch them?
Click to expand...
Click to collapse
Need to do it once, battery swap should not matter
K, thanks. Look forward to the improvements...
Well this work on the cm10 build ?
Sent from my SPH-D700 using xda premium
Dang...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This works.
just updated my build.prop, will report back in a day or so if i see the changes.. thanks!
Did this yesterday. made a noticeable difference. Thanks!
Well these work/help The People's Rom or is it ICS only?
Sent from my SPH-D700 using xda app-developers app
vwags said:
Well these work/help The People's Rom or is it ICS only?
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
they wont hurt.. you can try and post back but TPR has good battery life as is. You'll notice these more with ICS roms.
Ya. I love the battery on TPR but I was thinking if it helps ICS that much I may never need to charge my phone again. Since it shouldn't hurt I'll give it a go.
Sent from my SPH-D700 using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a list I will do further updates on,
currently I tested all Roms with Quadrant and standard installation with minimum apps and freshly tests after installation!
Benchmark used: QUADRANT
Average of several QUADRANT tests taken and combined and put in the list!
Other Roms will be checked in the future of course too
Be patient, the Note is getting hot because of flashing
[Counter above 20? xD]
PS: Pin-Thread maybe?
You DO know that benchmarks are just a bit of pointless epeen waving, and really have bugger all to do with actual device performance, right?
FloatingFatMan said:
You DO know that benchmarks are just a bit of pointless epeen waving, and really have bugger all to do with actual device performance, right?
Click to expand...
Click to collapse
Not fully, you really can distinguish their performance with those benchmarks especially the memory and I/O and 2D.
Each Rom gives you different amount of processes at the beginning with different kernels and their performance. This creates a different kind of system everytime you install another Rom.
As you see I didn´t count nothing about battery life or stability, thats the only penalty with it!
interesting that Hypernote is the lowest, its the one rom I always go back too
ratcom said:
interesting that Hypernote is the lowest, its the one rom I always go back too
Click to expand...
Click to collapse
IDK why Hypernote was slow, but Quadrant showed me really low results!I cant remember that Hypernote was underclocked, so the process system and the kernel may be the cause...
Cue thread deletion...
Sent from my GT-N7100 using xda app-developers app
Great idea, looking forward to more roms added to the current offerings. Yes it aint scientific but its interesting nonetheless. The OP should be thanked not chastised for the work put into this so imho the naysayers should just but out and not comment unless its a genuinely helpful and constructive comment.
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
I think it would be really useful if the OP ran the test for a stock version just as a reference, an unbranded version I dare say would be best ?
Sent from my GT-N7100 using xda app-developers app
Try running quadrant back to back 5 times without any alterations or task killers and see if your scores change. And take the average, just to be scientific.
Sent from my GT-N7100 using xda app-developers app
UPDATE WITH NEW ROMS!!!!
jetsetwilly said:
Try running quadrant back to back 5 times without any alterations or task killers and see if your scores change. And take the average, just to be scientific.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Of course I am not that stupid!
I made 3-5 Tests, deactivated Mobile Data, Sync, Rotation, any processes that can be deactivated on ANY rom, installed ONLY quadrant and killed all processes before using quadrant! Then did multiple tests, MEGA WIPE after any installation of any ROM! No additional apps, except aroma chooseable things!
AGAIN for newbs: The test SHOWS only SPEED/Performance Ability, NOT battery life, NOR stability NOR functionality! Since a LOT of things can be modded directly by the user, its the best thing to know the ROM with best performance to work with. Why? You can analyze the rom's features like kernel, modding, etc.
great job with the list man. I'm quite a fan of hypernote but I'm very surprised it placed last. maybe something important for speed was removed from the hypernote rom that's why?
I think you missed my point. And here's another thread on the same bollocks.
http://forum.xda-developers.com/showthread.php?t=1916810
Sent from my GT-N7100 using xda app-developers app
Looks like a full-time job to me. So many ROMs, so many kernels, so many combinations; and, for each one, so many different other variables as have been mentioned above; e.g. indoors,outdoors, sunny, hot, cold, proximity of 3G towers towers/WIFI access points, types of movies seen, software, GPU, multi tasking, and so on This is treading a thesis, IMO.
Good idea nevertheless, although I do prefer the ARHD 5.0 with PERSEUS...now, was it 26 or 26.1?
jetsetwilly said:
I think you missed my point. And here's another thread on the same bollocks.
http://forum.xda-developers.com/showthread.php?t=1916810
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I don't think they'll ever get it...
jetsetwilly said:
Cue thread deletion...
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
+1
manuarh said:
Looks like a full-time job to me. So many ROMs, so many kernels, so many combinations; and, for each one, so many different other variables as have been mentioned above; e.g. indoors,outdoors, sunny, hot, cold, proximity of 3G towers towers/WIFI access points, types of movies seen, software, GPU, multi tasking, and so on This is treading a thesis, IMO.
Good idea nevertheless, although I do prefer the ARHD 5.0 with PERSEUS...now, was it 26 or 26.1?
Click to expand...
Click to collapse
Obviously you think too complex! Didn´t you read? I used the ROM ITSELF, the ROM's power which comes directly from the developers, such MODS and tweaks which are made by USERS don´t count, when you compare between STOCK ROM with STOCK kernel, you don´t do ANY tweaks with stock ROm to compare them with Custom Roms RIGHT?
It says CUSTOM ROM COMPARE LIST , not USER EDITED LIST with different KERNELS etc. -.-
THATS IT! There are NO big combinations ONLY different versions of the CMs to make it easy! If I would test different KERNELS I would add of course the TITLE (different kernels)
Whats so hard to understand a performance comparison?