[Galaxy S II General] bajee11:
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 14@~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. :D

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

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 7@~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$ :D 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 :D

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 :D

Attached below are the screenshots of Battery Chart, Screen Time and CPU SPY