Hi all just wanted to do a comparison for battery life. I think that the biggest factor is having your display on and what kernal you use. So fill this out please so everyone can know battery life based on rom/kernal combos. :]
Samsung Fascinate
Rom: JTs V.7 DJ05
Kernal: Stupidfast 1.54
% battery remaining: 1
Standby time: 14h10m
Screen time on: 4h12m
Screen brightness setting: Auto
Setcpu: no
Settings: N/A
If you think theres any other factors to add just let me know.
I like the idea. Hopefully it is practical, so many variables. I would suggest streamlining the report a little bit, adding time spent without signal to standby, and changing SetCPU to be Extras: (only list items if you have them), live wallpaper, launcher, setcpu
Also I would add
Most used: Map 13%
Swyped from my i500.04 (bh &1129) using XDA App
Reports:
System: blackhole 2.2nf, jt 11/29 novoodoo
Extras: live wallpaper (Ocean Waves), adw, auto brightness, buzzbox news, accuweather quick, tweetdeck, google voice, goldenstorm Blackish v07 theme
Updates: Gmail (push), tweetdeck (twitter & facebook every 60 minutes), Buzzbox News (wifi every 30 minutes, vzw every 2 hours), Accuweather Quick (Default)
Report 12/3:
Display on: 5:23 (4% battery left)
standby 14:50 (28% without signal)
Most used: display 61%, standby 11%, maps 11%
Report 12/6: (Total 21:07:20)
Display on: 4:37 (8% battery left)
standby: 21:07 (17% w/o signal)
Most used: display 57%, standby 16%, idle 9% (16:30), bluetooth 6%, voice 5% (4 minutes)
Report 12/7 (Total 11:12:43 )
Display on: 5:51:47 (2% battery left)
standby: 11:12 (27% without signal)
Most used: display 69%, voice 8% (0:07:50), standby 8%, system 4%, idle 3% (5:20:56), dolphin HD 3% (0:17:22)
Report 12/8 (Total: 15:44:36)
Display on: 3:56:18 56%, (4% battery left)
standby: 15:44:29 15%, (35% without signal)
Most used: Media server 6% (0:46:30 - ran pandora a while off of speakers), System 4%, Voice 4% (0:2:40)
Thats awsome soba (gets off to try that combo now)
Ill just be stoked when we get froyo in twelve million years.
Froyo has increased battery life on my X by like a good 5 or 6 hours.
I charge my fascinate nearly twice as often
soba49 said:
Reports:
System: blackhole 2.2nf, jt 11/29 novoodoo
Extras: live wallpaper, adw, auto brightness, buzzbox news, accuweather quick, tweetdeck, google voice
Report 12/3:
Display on: 5:23 (4% battery left)
standby 14:50 (28% without signal)
Most used: display 61%, standby 11%, maps 11%
Report 12/6: (Total 21:07:20)
Display on: 4:37 (8% battery left)
standby: 21:07 (17% w/o signal)
Most used: display 57%, standby 16%, idle 9% (16:30), bluetooth 6%, voice 5% (4 minutes)
Click to expand...
Click to collapse
Hey soba would you say that Bh has bettery battery life than JT?
Well note that I am running JT's kernel. In terms of the ROM, of course I am very happy where I am, but not because I believe the battery life is superior. I did run super clean 0.5 no voodoo, but not long enough to make a proper battery life comparison. In fact, I believe comparing different installations to get a handle on battery life or perhaps some practices that might improve it is the intention of the thread.
Samsung Fascinate
Rom: JTs V.7 DJ05 with NexTheme v3.0
Kernal: 1203 Voodoo
% battery remaining: 69%
Time since unplugged (full charge): 12h 26m
Phone Idle: 11h 40m
Display on: 46m
Time without signal: 15%
Most Used: Display - 34%, Cell Standby - 34%, Phone Idle - 22%
I'm using Beautiful Widgets, set to update weather every hour, along with LauncherPro+ set to update Friends widget every hour (Twitter/Facebook). No Live wallpaper, minor gaming (maybe 10 min). Today has been a light usage day as I was busy with other stuff and had less time to play with my phone.
BlackHole 2.4 w/ DJ05, jt 1129 no voodoo:
4 hours, 1 minute display. 24 hours standby. 3% battery left. Just a rough estimate, didn't take formal report. Subjectively same battery life as 2.2 w/ IRC dj05.
ICS KERNEL TESTS - AOKP/AOSP/CM9
Netchip | Siyah | N.E.A.K | Thoravukk | Abyss | Fluxi
This thread is only intended for reference purposes to those using AOSP/AOKP/CM9 ROMS
Purpose
I conducted these tests in order to help all users of AOSP/AOKP/CM9 ROMS to have a reference base when flashing a custom kernel. In no way am I supporting you to do so and I will not be held accountable of any wrong doing resulting from your part. I know it's sounds harsh, but do not jump out there flashing kernels if you do not have the minimal knowledge about how things work. I will be posting up a few links to other informative threads in order to help everyone (a.k.a noobs) These tests are done through my own will and I spend quiet a lot of time writing these results in a presentable manner so everyone could benefit from this. If you do not like the way I do my tests or would like to share some improvements, please do so in a respectable manner. If you cannot follow this simple rule, I strongly advice you not to use this thread as a reference and I suggest you do your own test which would satisfy and meet your requirements.
How to flash a kernel?
There are different ways of flashing a kernel, but the one I use is through CWM, because I do not trust ODIN, simple as that.
Step 1: Download Kernel Cleaning Script if your coming from a different kernel and flash it before flashing the new kernel. If it's just an upgrade of the same kernel, wipe cache and dalvik before flashing.
*Using a Cleaning Script is not mandatory to flash a new kernel, it is just recommended to use it to make sure modules and such are cleaned for a fresh installation
Step 2: Flash desired kernel.
Step 3: Wipe Cache and Dalvik once kernel is done flashing.
Step 4: Reboot System.
*Hint: If you're having fc right after boot, reboot into recovery mode and try fixing permissions. It happened to me once, and after fixing permissions everything went back to normal.
How to flash back to stock kernel?
Step 1: Extract "boot.img" from ROM zip file
Step 2: Rename "boot.img" to "zImage"
Step 3: Place zImage in Internal Storage
Step 4: Use CWM app and flash "zImage" as kernel
If you're unsure of this method and do not want to try it because you're scared of doing something wrong, I'll post a flashable one for you upon request.
Kernel Cleaning Script
**Use these scripts at your own discretion**
GS2WiperV1.6
Does the following: (Bold are changes since V1.5)
1. Wipes cache+dalvik cache
2. Saves all current startup scripts to /sdcard/init.d_backup
3. Removes Voltage Control and NSTools startup scripts (only if saved as init.d, and not as a service) along with specific Siayh startup scripts from /system/etc/init.d
4. Removes old kernel-specific files (currently Void, Andoidmeda, Siyah and NEAK are cleared)
5. No longer removes modules (/system/lib/modules) as this can affect certain ROMs
6. Removes old CPU settings from /sys/devices/system/cpu
7. Removes /data/user.log
8. Re-wipes cache+dalvik cache
Samsung Ultimate Kernel Cleaning Script ICS 2.6.4
Does the following:
Formatting cache partition
Wiping Dalvik-Cache
Deleting old kernel settings files ** [only GT-i9000]
Cleaning up old Modules
Formatting cache for Security Purpose
Wiping Dalvik-Cache for Security Purpose
Cleans after Kernels:
Thoravukk KERNEL
Abyss KERNEL
CF-Root
FLUXI Kernel
N.E.A.K. Kernel
Ninphetamine
Phenomenal
RedPillKernel
SiyahKernel
SpeedMod
Void.echo
Credits to:
Hawker - My GS2 Kernel Cleaning Scripts (WIper V1.6)
buster041284 - Samsung Ultimate Kernel Cleaning Script ICS
You guys made it easy for us! Thanks for your hard work guys!
________________________________________
You don't play too many games?
You use your phone mainly for texting, calling, browsing, twitter, facebook, XDA and other small stuff?
You want to save battery?
Then here's some good battery optimized settings.
Lulzactive Settings - Battery Optimized
Governor/Scheduler: Lulzactive/VR
Lulzactive Tweaks:
inc_cpu_load: 90%
pump_up_step: 2
pump_down_step: 2
screen_off_min_step: 500MHz
up_sample_time: 28000
down_sample_time: 40000
debug_mode: 0
Voltage Tweaks:
200Mhz - 825 mV
500Mhz - 950 mV
800Mhz - 975 mV
1000Mhz - 1050 mV
1200Mhz - 1150 mV
GPU Tweaks
2 Step:
133 - 850 mV
267 - 950 mV
3 Steps
100 - 850 mV
160 - 900 mV
267 - 950 mV
Want to save even more battery:
200MHz-1000MHz
or
200MHz-800MHz
________________________________________
Currently Testing:
On Hold
Testing Soon:
Vanilla RootBox JB + Stock
Vanilla RootBox JB + Siyah
Completed Tests:
- HyDrOG3N 14.04 + N.E.A.K 2.0.2x (Completed - April 17)
- HyDrOG3N 14.04 + Thoravukk 2.28 (Completed - April 18)
- HyDrOG3N 18.04 + Siyah v3.1 rc6 (Completed - April 20)
- HyDrOG3N 18.04 + Netchip Stock Kernel (Completed - April 21)
- HyDrOG3N 18.04 + Siyah v3.1.2 (Completed - April 25)
- HyDrOG3N 27.04 + N.E.A.K 2.0.3x (Completed - May 1st)
- HyDrOG3N 27.04 + Thoravukk 2.50 (Completed May 2nd)
- HyDrOG3N 05.05 + Abyss 1.6b (Completed May 7)
- HyDrOG3N 05.05 + Fluxi XX.01 RC3 (Completed May 8)
- HyDrOG3N 12.05 + Netchip (Stock) (Completed May 14)
- HyDrOG3N 12.05 + Fluxi XX.01 RC4 (Completed - May 16)
- HyDrOG3N 12.05 + Abyss v2.0 (Completed - May 18)
Bajee Scale(ºB): (Will be implemented Soon)
0-50 = Stay away from this!
51-70 = Could be better, keep looking.
71-80 = Not bad, I like it.
81-90 = Damn, I'm impressed.
91-100= Why isn't everyone using this!
Thanks to Definitus for the scale idea.
Press Thanks If this thread was useful.
If your downloading the xxTweaker app that I translated, I'm not asking for any donations, just press thanks to show your appreciation.
Test Results - HyDrOG3N + Siyah + Fluxi
HyDrOG3NICS + Siyah + Fluxi
Test Results - HyDrOG3N 12.05 + Fluxi XX.01 RC4
Rating: 95 ºB
Fluxi ICS Kernel
Original Thread
XDA Thread
Governor/Scheduler Used: On Demand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 15 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games + Instagram
Phone died: Wednesday May 16 @ 2:21AM
Screen On Time: 6h 13min (6h15min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out)
- Data ON (Always ON)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 30 minutes talk time
- Google + (~5 mins)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Used 5-6 times)
- Osmos HD (5 mins)
- Angry Birds Space (10 mins)
- Youtube (1 Movie Trailer)
As expected, this kernel came up to the highest expectations I had. Implementation of Touch Presets is probably one of the best thing Fluxi did for this release. Bringing in new BLN/LED functions was really nice to see, but it's too bad I don't use BLN (due to wakelock) and LED fadeout is really nice but I didn't use it for this test. So for the bad things now, I had one (1) reboot.. Unfortunately true but to recomfort you guys: It was only a soft reboot. So for that reason, I couldn't post CPU SPY and BBS screenshots as they get reset after any boot. Once again, I will highly suggest this kernel to all users. I realized that after posting results for HyDrOG3N 05.05 + Fluxi XX.01 RC3, lot of users jumped in and started using Fluxi. The translated app might of helped too, who knows. But I'm glad everyone knows that Fluxi exists out there and is doing really well with battery and performance. So I'll take this time to thank Fluxi for this amazing kernel, Paradoxxx because he got swagg beyond my understanding with amazing HyDrOG3NICS releases, xator91 for opening a thread for this kernel on XDA, KS_Ho for testing out my translated xxTweaker app and finally all the subscribers of this thread.
How to install translated xxTweaker for RC4
1) Unzip file and transfer net.fluxi.xxTweaker-1-0.3.2_signed.apk to internal storage
2) Uninstall the original xxTweaker
3) Install net.fluxi.xxTweaker-1-0.3.2_signed.apk from internal storage
4) You should now have xxTweaker in English
5) Create empty file: /data/.notweaker (Should stop autoupdate)
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
Touch Presets: xxKernel Gingerbread
BLN
No BLN (But I gotta say, Breathing effect is really amazing)
Led time out: 1 second (No Fadeout effect)
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
{
"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"
}
Test Results - HyDrOG3N 05.05 + Fluxi XX.01 RC3
Rating: 95 ºB
Fluxi ICS Kernel - Original Thread Link
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 8 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games
Phone died: Tuesday May 8 @ 10:05PM
Screen On Time: 6h 12min (6h14min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- Data ON (If I receive MMS and Data is OFF, it drains battery by attempting to download MMS. So from now on, Data will be on for all my tests)
- AutoSync ON (Google Services, Twitter)*
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 45 minutes talk time
- Google + (~15 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Opened a few times)
- Draw Free
- Osmos HD
- Angry Birds Space
- Youtube (3 movie trailers)
Wow, seriously, this kernel just blew me away with its performance and battery. It's been a while since I've seen a kernel with this much of customization with it's own app. Unfortunately, this is a kernel made in Germany, so the app that comes with the kernel for customization was in German only. So I took the liberty of decompiling the apk, translating the string.xml, recompiling it and finally testing it on my phone. I omitted to translate one or two words, but the translated app works like a charm! You could download it from the first Post of this thread. Just make sure you hit Thanks when downloading. By the way, this kernel does not have lulzactive governor, so I used OnDemand for the test. For all those following all my tests, I think this might be my favorite kernel for now. I highly suggest for everyone to try this.
How to install translated xxTweaker
1)Unzip file and transfer xxtweaker_signed.apk to internal storage
2)Uninstall the original xxTweaker
3)Install xxtweaker_signed.apk from internal storage
4)You should now have xxTweaker in English
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
BLN
No BLN
Led time out: 1 second
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 18.04 + Siyah v3.1.2
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 24 @~6:30 PM
Woke up: Friday April 25 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 50 minutes talk time
- Google + (~10 mins of usage)
- Tapatalk (All day)
- Browsing (Once or twice for a few mins)
- Camera (3 Photos + 1 Video)
- Osmos HD ~20 mins
- Angry Birds Space ~10 mins
- Youtube (2 videos ~3 mins/each)
- Netflix (TV show: Lie To Me 45 mins)
Phone died: Friday April 25 @ 17:10 PM
Screen On Time: 4h 11 min (4h 20 min when phone died)
Hey guys, I've been a little busy these days, but here I am with new results. Yup much lower than the one before but I have a pretty reasonable explanation. First of all, last Siyah's test with rc6, I only had 17hours of run time and this time I had 23 hours. That's because I didn't have the opportunity to use my phone much today (except for texting and tapatalk) since I was busy with some things of my own. During my study break, I played a little bit of Osmos HD, which is a game I bought on Play Store while it was on special for 0.49$ and I gotta say, it's pretty addictive at times (Specially when you're tired of studying) But I did end up using the phone a lot more at the very end when I was really bored and started watching a show on Netflix(which drastically killed the battery). Once I was done watching the show, I received a phone call from a friend and talked for almost an hour which also decreased the battery by a few %. Overall, I am very satisfied by the amount of time this phone actually stayed on after all these usage. I don't think this time the screen time actually mattered due to the fact that it was balanced out with 23 hours of run time. Unfortunately I couldn't post up CPU Spy or BBS, because this morning I had a random fc with my camera app and the phone had to be rebooted, so CPU Spy and BBS stats were reset.. Very strange but it only occurred once. I changed two things during this test: I noticed my lulzactive settings were giving me a little bit of lag at times. It wasn't big at all, just small lag, but I didn't like that, So i switched to these lulzactive settings and it got much better. (Values changed are in red)
Lulzactive app by Tegrak (Play Store)settings:
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
*** Mounting Points haven't changed with HyDrOG3N-ICS and Siyah v3.1.2: /emmc=external /sdcard=internal ***
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart and Screen Time
Test Results - HyDrOG3N 18.04 + Siyah v3.1 rc6
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1000MHz) (100MHz/160MHz/267MHz)
CPU UV: None (under clocked CPU instead)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 19 @~9 PM
Woke up: Friday April 20 @ 9 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (150 texts +)
- ~ 35 minutes talk time (Had a phone interview + few calls)
- Google + (~15 mins of usage)
- Tapatalk (Used the most)
- Browsing (Not much today)
- Camera (2 pictures)
- Temple Run ~15 mins
- Angry Birds Space ~10 mins
- Youtube (4 videos ~3 mins/each)
Phone died: Friday April 20 @ 2:10 PM
Screen On Time: 7h 10 min (7h 13 min when phone died)
I did not expect this combination of ROM+Kernel to kill the other two, seriously didn't . Ever since there was a battery drain on previous version, I was convinced Siyah v3.1 rc6 wouldn't perform as much. As you could see in the screenshots, the hours of CPU SPY and hours of battery chart do not correspond. Why? Explanation: I turned on the Torch Light through the Power Button in order to answer a question on HyDrOG3N's thread. But after doing that, I kept having "TORCH_WAKE_LOCK" and it wouldn't go away, hence keeping my device awake. So I decided to do a "hot boot" through an app in order to conserve battery stats/cpu spy time and make that wakelock go away. Cpu Spy kept it stats, but Android's battery chart did not(but the wakelock disappeared). So in reality I had 17h44min of run time and not 17h16 as displayed. So carrying on, I did not heavily used my phone but I used it like I normally would use. I think what made the difference this time was to tweak Lulzactive. I used the Lulzactive app by Tegrak (Play Store) and tweaked it to these settings:
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
Screen off min step is 4 because of available range. That means, when screen off, cpu usage shouldn't go over 500MHz frequency step.
1400= 0
1200= 1
1000= 2
800= 3
500= 4
200= 5
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
I want tho thank Gokhanmoral for his nonstop effort in order to eliminate battery drain and I think he really achieved that with Siyah v3.1 rc6 Keep up the good work mate!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time and CPU SPY
Test Results - HyDrOG3NICS + N.E.A.K
HyDrOG3NICS + N.E.A.K + Abyss
Test Results - HyDrOG3N 12.05 + Abyss 2.0
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: AbyssPlug/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(950mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday May 17 @~2:45AM
Woke up: Monday May 17 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Friday May 18 @ 1:30 AM
Screen On Time: 5h 43min
Type of usage:
- WiFi ON (Disconnected 3 times when I went out )
- Data ON
- AutoSync ON (Google Services, Twitter, Friendcaster)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (200+ texts)
- ~ 30 minutes talk time
- Tapatalk (Used a lot)
- Twitter Usage: All day (Auto sync)
- Instagram (Used once)
- Draw Free
- Youtube (2 small clips)
This kernel was very good as I expected it would be. Due to lot of demands for me to try Abyssplug instead of Lulzactice, I decided to give it a go and it seems like this governor has the proper tweaks in order to keep performance and also save battery. So during this test, it was a regular usage of phone. There was a fair load of cpu when playing Draw Free but except that, it was minimal processes. I had to disconnect WiFi twice since I went out and I don't leave my WiFi on when I go out. So i didn't have any reboots or fc this time and it was a very pleasant and smooth experience. Only issue I had was Gmail draining my battery overnight with a 20min wakelock, but I'm sure that didnt affect the battery that much. I guess that's it for Abyss Kernel. Hope this could serve as a reference and if you got any questions about AbyssScript or anything kernel related feel free to ask.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system. You could always pull the file to your computer and edit it there if it's easier for you.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 05.05 + Abyss 1.6b
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 6 @~3AM
Woke up: Monday May 6 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Monday May 7 @ 1:35 AM
Screen On Time: 5h 24min (5h31min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out to the movies)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (200+ texts)
- ~ 25 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)
- Instagram (Used twice)
- Draw Free
- Youtube (2 movie trailers)
One of the best kernel I have tried so far. Really smooth, no reboot, no fc! I really don't care if I only got 5:24min of screen time (which is quiet a lot for some people), I had a good 22 hours of usage. The only low point with this kernel, it will give some hard time to noobs because you have to know how to use scripts, set permissions etc.. Everyone could easily learn if you put your mind to it. So it was a normal day of usage today for me, lots of texting, Tapatalk and twitter. The settings I used for Abyss are displayed below and they're really easy to be applied. If you need help setting it up, don't hesitate to post on this thread or pm me. I will do my best to answer you the fastest I can if not, there's always someone around to answer you in here.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system.
Lulzactive Settings
Lulzactive app by Tegrak - Play Store
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 27.04 + N.E.A.K 2.0.3x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday April 30 @~1 PM
Woke up: Tuesday May 1st @ 8 AM (WiFi was on throughout the night)
Usage: Regular usage + Twitter
Phone died: Tuesday May 1st @ 1:04 PM
Screen On Time: 5h 04min (5h11min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS (Used for 20 Mins)
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (150+ texts)
- ~ 20 minutes talk time
- Google + (~5-10 mins of usage)
- Google Maps Navigation (~20 mins)
- Tapatalk (Used a lot to keep track of thread)
- Twitter Usage: All day (Auto sync)
- Draw Free (~10-15 mins of usage)
Here you go guys, another test with latest HyDroG3NICS 27.04 + N.E.A.K 2.0.3x. Good results overall due to the usage throughout the day. Unfortunately, I experienced one(1) freeze when I had 13% left and as you guys know, that causes the CPU SPY and BBS stats to get erased if rebooted, so no cpu spy/bbs screenshots this time, sorry . Except that, I was satisfied with this release and how smooth scrolling was. BLN apps works but of course, it will be a wakelock, so I did not use it during the test but I tested it before I started. I modified led_timeout to 500(0.5sec) because 1000(1sec) is too long for me and also UV CPU/GPU. No more freezes with BBS and I also used NEAK Configuration app to Enable AFTR Idle Mode and Lulzactive app for my tweaking. I guess this concludes the test. If you have any questions don't hesitate to post on this thread, I will try my best to respond in a timely manner. By the way, I started using Twitter now so that's why there's 4% of twitter. If you want to follow me or ask me questions there, you guys are always welcome. @bajee11
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
Test Results - HyDrOG3N 14.04 + N.E.A.K 2.0.2x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(925mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday April 15 @~11 PM
Woke up: Monday April 16 @ 8 AM (WiFi was on throughout the night)
Usage: Used phone throughout the day but not maximal use. (Had to study for exam)
Type of usage:
- WiFi ON (except when i was in school for 3 hours: 3G was activated at that time)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of texting
- ~ 10-15 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of thread)
- Browsing
- Camera (~10-15 pictures)
Back to Bed: Tuesday April 17 @ 1 AM
Woke up: Tuesday April 17 @ 7 AM (yes only had 6 hours of sleep , kinda got used to it with exams period)
Phone died: Tuesday April 17 @ 8:40 AM
Screen On Time: 4h 45min (4h50min when phone died)
Overall, this combination of ROM+Kernel was really impressive to experiment with, performance and battery wise. Although I had some random freezes when charging the phone, but I later found out BetterBatteryStats RC2 was the cause of it. Uninstalled it, and everything worked flawlessly. N.E.A.K 2.0.3 soon to be released and promises a lot of improvements with HyDrOG3n and expected to solve freezing issue.
I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes, so whoever wants to use it, do so. HyDrOG3N-ICS is an amazing ROM and Para's enormous input and effort, made all this possible. Let's not forget Simone201 and his amazing N.E.A.K kernel, which seems to be pretty optimized with our ROM and built to save battery without sacrificing performance. So what's the moral of the story? Get your Swag On!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY.
Test Results - HyDrOG3NICS + Thoravukk + Netchip (Stock)
HyDrOG3NICS + Thoravukk + Netchip (Stock)
Test Results - HyDrOG3N 12.05 + Netchip (Stock Kernel)
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200MHz-1200MHz) (66MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 66MHz(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 13 @~11AM
Phone died: Monday May 14 @4:01 AM (Went to sleep late)
Screen On Time: 6h 25 min (~6h 28 min when phone died)
Type of usage:
- WiFi ON (During the whole test- Except when I went out)
- Data ON (Always)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting (250 texts +)
- ~ 35 minutes talk time*
- Tapatalk (Used a lot of course)
- Browsing
- Twitter
- Youtube (~10 mins)
Here's another test guys. One of the best releases of HyDrOG3NICS so far with excellent performance and battery life. Scrolling was smooth and very touch responsive. I realized that having more frequency is actually better for me (I was thinking the opposite before, Less the Better). Just like in Fluxi and Abyss, having a lot of frequency steps allows the usage of multiple steps according to the needs of the CPU. Instead of being stuck with 5 steps we now have 11 steps (Assuming your using 200-1200). But it all breaks down to the governor and how it will use those frequencies. This is where UV comes in handy, if you could lower voltage for these extra frequency steps, you could minimize battery consumption. It won't be enormous but it'll still help. This kernel is really an amazing work and the device tweaking app integrated with the system is simply amazing. Yes, there are still a few bugs, but nothing major to refrain us from using all the features. The only issue I had, was with the backlight staying on forever. But of course, that's not a big deal by now, Everyone knows how to disable them by changing values of led_timeout. So I made a few flashable scripts to change the values. They're available on OP.(Disable, 1 secoond and 3 seconds). I know this time I only had 17 hours of runtime but that's because I used a lot of data when I went outside this time, mainly for Instagram, Youtube and Browsing. I could say, I had a really busy day with my phone.
The On Demand included with stock kernel has these tweaks as default and they are very battery oriented.
On Demand Tweaks (Default):
up_threshold= 85 (You could always increase this to 90% or 95% to save even more battery, but it might lag)
sampling_rate= 100000
sampling_down_factor= 1
down_differential= 5
Hotplug enabled(Default):
loadh= 80
loadl= 30
loadh_scroff= 1000
loadl_scroff= 80
So when cpu load is more than 80% second core is activated and when cpu load goes below 30% the second core is deactivated. The other two values, I have to ask Netchip, because 1000 seems off for scren off values.
AFTR+LPA enabled (Default)
enable_mask= 3 , which stands for AFTR+LPA
If you want to save an extensive amount of battery and you're not a heavy CPU usage I suggest you underclock your CPU from 1200 to 1000 or even 800 for some. This might result in some FCs for some or even reboot, but it really depends of each person. I suggest you give it a try.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 27.04 + Thovarukk 2.50
Rating: 80 ºB
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Wednesday May 2nd @~3:30 PM
Phone died: Thursday May 3rd @3:28 AM
Screen On Time: 5h 20 min (5h 23 min when phone died)
Type of usage:
- WiFi ON
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting
- ~ 15 minutes talk time
- Google + (~10 mins of usage)
- Twitter (throughout the day)
- Tapatalk
- Youtube (3 videos of ~4mins/each)
- Draw Free (45 mins) Got carried away with this
Really good results with Thoravukk 2.50 but unfortunately I had two random reboots. I did not investigate the cause of the boot since I was too busy with other stuff these days, but it happened once when I openned Twitter and the other time, when opening BBS. The kernel itself is really stable if we do not take into consideration these reboots and still keeps up with the high standard of saving up battery. Of course, my lulzactive settings actually play a big role in battery saving but the kernel itself is not bloated with too many features which actually makes it interesting and very battery friendly. So this concludes the test, hope this helped you guys. More tests to come!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 14.04 + Thovarukk 2.28
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(925mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1125mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Tuesday April 17 @~10:30 PM
Woke up: Wednesday April 18 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (WiFi was off when i was out, 3G Activated)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting
- ~ 20 minutes talk time
- Google + (~15-20 mins of usage)
- Tapatalk
- Browsing (Several times during the day)
- Camera (~5 pictures + 2 Videos)
- Temple Run ~10 mins
- Cut The Rope ~15 mins
- Youtube (3 videos of ~4mins/each)
Phone died: Wednesday April 18 @ 8:30 PM
Screen On Time: 5h 50 min (5h 59 min when phone died)
This combination of ROM+Kernel was more impressive than the previous test I did with N.E.A.K. 2.0.2x . Only disadvantage with this kernel was to use so many frequency steps, which I find reduces battery time. (yup battery could of lasted even more if it weren't for all these frequency changes.) But this issue has been fixed in version 2.30 (released today) with the typical frequencies of 100, 200, 500, 800, 1000, 1200, 1400 and 1600. Unfortunately, I couldn't screenshot CPU SPY this time due to my carelessness: I tried testing a script on Script Manager but it froze and had to reboot phone. For that only reason, CPU SPY had a reset and results were no longer representative. Another big thanks to Para for his amazing Swag and Pingpong for his battery optimized Thoravukk Kernel.
Once again I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 18.04 + Netchip (Stock Kernel)
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (133MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 20 @~10:30 PM
Woke up: Pulled an all-nighter to study for exam (fml) (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 10 minutes talk time
- Tapatalk (Used a lot)
- Browsing (Not much)
- Youtube (20-25 videos ~3 mins/each)
- Updated new version of Facebook (Battery killer!! Update installs FB Messenger + Camera)
Phone died: Friday April 20 @4:46 PM
Screen On Time: 7h 29 min (~7h 35 min when phone died)
Trying to keep my tests representative and due to some useful feedback I received from users, I'm going to UV CPU/GPU like I did for my first two tests. (I didn't do it for Siyah, sorry guys) When I started using this kernel, I right away noticed the difference in smoothness. It's been so long I actually used the stock kernel that I even forgot how it felt like. Unfortunately, I had some issues with UV and my usual settings wouldn't work and I was getting random freezes right after boot so I had to add up +25mV for 500MHz/1200MHz. I still applied my Lulzactive app settings and I will be doing so in all my future tests as well. So now for the results: since I was studying for my exam and wasn't using my phone much, I decided to take a few breaks here and there to play games and I left YouTube ON for a long time in order to listen to music.(I have music on my phone but I needed an app that would consume battery) So as you guys read above, I didn't sleep all night... stupid me should of studied earlier instead of fooling around with my phone Lol.. But I still managed to send more than 200 text messages.(Got into a serious texting convo in the middle of the night with one of my friends )
So let's talk about screen time now.. DAMN, 7h29!! HOW DID I DO THAT? well let me tell you something: DON'T TRY THIS AT HOME! because you most probably wont reach close to 7hrs because we all use our phones differently and I get these crazy screen hours because I don't do hardcore cpu usage. As you guys could notice, most of the time, my phone joggles between 200MHz-500MHz. Other frequencies are being used as well duhh, but not as much as these two. I had some issue with deep sleep due to F#@[email protected]^% Facebook update that kept my phone awake for no reason and some how MMS as well! Well yea, I've been sending a lot of pictures through text/mms but it's weird that it actually stayed on for such a long time. But everything went back to normal after a point and MMS stopped messing with my Deep Sleep. That's right, don't mess with my Deep Sleep! Okay enough with the jokes, I guess it's time to conclude this test. A++ Loved the battery life. Those rumors were actually true: Stock is Amazing. Shock of the day: I rushed to take screenshots of my screen before walking into my examination room because my battery was at 1%!! I figured it would die during my exam of 3 hours. This beast stayed alive till I was done my exam and even let me take more screenshots, browse and post about it on this thread!!! Hats off S II, your too cool for me. Hope you enjoyed the review and if you didn't laugh at my lame jokes, I'll make sure you do in my next review
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 11 (500mhz)
Tricky stuff: GPU UV is not available through Voltage Control extreme and obviously you can't use ExTweaks. So I had to use init.d script. I used the same script I had for my led_timeout, since backlight value was only "2". That value is really useless because it feels like your phone is having a seizure everytime your trying to touch the soft keys and "Hold back to kill" does not work with that value. So I changed it to 500, and added GPU frequencies of 133/267 with 850mv/950mv. Also used Lulzactive app for tweaking. One thing I didn't check with this test: AFTR+LPA. Don't know if it's default or not. Have to check that next time.
I want tho thank Netchip for his effort and input in creating a remarkable kernel. I believe someone said he was only 12 yrs old. So Netchip, if you really are 12, FML!! You're [email protected]#$% awesome bro!! Nop, I didn't forget you Para! You guys make a nice team, seriously.. Keep up the good work!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Great work dude... I'll keep on this track.. will subscribe to this!!
Sent From Galaxy S II BEAST
U know what... even we will get another kernel with superb battery back up n more. . Coming soon.. from Dorimanx .. see my signature..
Sent From Galaxy S II BEAST
Can't wait for Siyah's results
From my calculations according to the teaser that you PM'd me, I am guessing a screen on time of around 6 hours 30 minutes
Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?
XDA mark said:
Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?
Click to expand...
Click to collapse
No i dont. I basically use a lot of fb, google+, tapatalk, youtube, browser a little and lots and lots of texting.
Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Paradoxxx said:
Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Click to expand...
Click to collapse
Thanks mate, I appreciate it!
Cool.. exactly what i was looking for..
Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...
darkgoon3r96 said:
Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...
Click to expand...
Click to collapse
Most tasks I do, do not require high amount of CPU usage, except for my games. Which I don't play that often. So a range from 200-1000 is actually enough for my usage.
Rc6 results soon?
Sent from my GT-I9100 using XDA
Dark Emotion said:
Rc6 results soon?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
its up
Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)
XDA mark said:
Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)
Click to expand...
Click to collapse
I did experience a small lag while scroling in Tapatalk, but somehow that lag wasn't there while scrolling through system settings. I figured it's because Tapatalk is a beta version. But you're right, I really tweaked it towards battery and there is that small lag which is barely noticeable. You guys could reduce the tweak towards performance/battery with this:
inc_cpu_load = 90
pump_up_step = 4
pump_down_step = 1
up_sample_time= 10000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?
darkgoon3r96 said:
Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?
Click to expand...
Click to collapse
Sansation Regular