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

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

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:rolleyes:.. 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 :P)

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#@!@^% 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.:cool: 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 :rolleyes:

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 f!@#$% 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 :D

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