Here you go guys. You wanted a new discussion thread for all to do with Siyah ICS kernel v3.0 Betas.
So here you have it. Feel free to discuss any problems you may have or any issues, post your benchmarks, your battery results and anything you want to discuss keep it here.
Now you have your thread lets get posting
LINKS:
*Link to the development thread of Siyah v3.0beta6
http://forum.xda-developers.com/showthread.php?t=1555259
*Link to Droidphiles thread regarding info about latest Siyah kernel and ExTweaks app
http://forum.xda-developers.com/showthread.php?t=1369817
*Link to Gokhanmoral's blog and download site:
http://www.gokhanmoral.com/
Results for Siyah / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on ICS XXLPQ ROM (Modem: XXLPQ).
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
I just flashed SiyahKernel v3.0beta6 and added its results - only mixed usage battery test is missing.
Here are my current results:
Benchmarks
Quadrant Standard 2.0 (best of 3 runs)
Siyah v3.0beta6: 4166
Siyah v3.0beta5: 4156
Stock XXLPQ kernel: 4063
Siyah v3.0beta3: 3983
Siyah v3.0beta4: 3953
NenaMark2 (best of 3 runs)
Stock XILA2 kernel: 54,3
Stock XWLA4 kernel: 54,2
Siyah v3.0beta6: 52,0
Stock XXLPQ kernel: 51,3
Siyah v3.0beta5: 50,4
Siyah v3.0beta3: 50,3
Siyah v3.0beta4: 50,0
Stock XWKK5 kernel: 47,8
Stock XWKK2 kernel: 47,6
Stock XWKL1 kernel: 38,1
Vellamo (best of 2 runs)
Siyah v3.0beta6: 1273
Stock XXLPQ kernel: 1247
Stock XILA2 kernel: 1225
Stock XWLA4 kernel: 1216
Siyah v3.0beta3: 1174
Stock XWKL1 kernel: 1173
Stock XWKK5 kernel: 1160
Siyah v3.0beta5: 1138
Siyah v3.0beta4: 1081
Stock XWKK2 kernel: 1080
Linpack (best of 10 runs): Single / Multi thread
Stock XWLA4 kernel: 57.816 / 93.548
Stock XILA2 kernel: 57.302 / 91.667
Stock XXLPQ kernel: 48.208 / 80.013
Siyah v3.0beta3: 47.390 / 78.816
Siyah v3.0beta4: 47.633 / 77.370
Siyah v3.0beta6: 47.850 / 76.702
Siyah v3.0beta5: 47.150 / 75.800
CF-Bench (best of 2 runs): Native / Java / Overall score
Stock XWLA4 kernel: 11396 / 3539 / 6681
Siyah v3.0beta6: 11144 / 3359 / 6473
Stock XILA2 kernel: 11285 / 3187 / 6426
Siyah v3.0beta4: 11135 / 3265 / 6413
Stock XXLPQ kernel: 10862 / 3044 / 6171
Siyah v3.0beta3: 10716 / 2906 / 6030
Siyah v3.0beta5: 10529 / 2790 / 5885
AnTuTu (1st run)
Siyah v3.0beta6: 6136
Stock XILA2 kernel: 6110
Stock XXLPQ kernel: 6075
Stock XWLA4 kernel: 6009
Siyah v3.0beta4: 5654
Siyah v3.0beta5: 5593
Siyah v3.0beta3: 5414
Click to expand...
Click to collapse
Battery stats
Night use (wifi, synch, Talk and Skype on)
XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
Siyah v3.0beta5: Battery loss of 1,05% per hour, Awake: 8,4%, Deep sleep: 90%
Siyah v3.0beta4: Battery loss of 1,08% per hour, Awake: 7,8%, Deep sleep: 91%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
Siyah v3.0beta3: Battery loss of 1,14% per hour, Awake: 8,1%, Deep sleep: 91%
Siyah v3.0beta6: Battery loss of 1,19% per hour, Awake: 8,6%, Deep sleep: 90%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Mixed (day and night) usage (*)
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
Siyah v3.0beta5: Battery loss of 2,45% per hour, Wifi: 89,9%, Awake: 19,6%, Deep sleep: 80%, Screen: 9,9% => loss*(1-screen): 2,21%
Siyah v3.0beta3: Battery loss of 2,45% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 9,7% => loss*(1-screen): 2,21%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
Siyah v3.0beta4: Battery loss of 2,50% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,4% => loss*(1-screen): 2,24%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery loss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
Click to expand...
Click to collapse
Very good initiative.
Thank you.
Subscribed.
thanks for opening this thread ,
USB OTG problem with Siyah-v3.0b6
Hello,
I have posted this message in another thread related to Siyah kernels, but I think it is better suited here.
First I should say I am very happy with Gokhanmoral's outstanding work. Thanks a lot!!
I just flashed yesterday Siyah-v3.0b6-CWM kernel + CM9 ROM (update-cm-9-20120322-NIGHTLY-galaxys2-signed.zip). I noticed that USB HID devices (like mouse, keyboard or other custom USB devices) are not working anymore. They are not listed when I run the terminal command "lsusb", so I believe they are not recognized.
This was a known issue caused when Samsung introduced whitelists for the USB OTG support.
I was using Siyah-v2.5.2-CWM kernel + Android 2.3.5 and the USB devices were recognized and working correctly. I think the compilation modifications for USB OTG were not included in the last release. I have not been able to post in the developers area this issue. Can someone post this message so that Gokhanmoral can received this feedback?
regards,
Saul
I am not a big fan of too much Kernel tweaks, neither benchmarking. Further, I do think settings are most of the time device related, and it can leave to misfunction when adapting someone else settings.
But as many users are asking, I will just throw here my settings. Nothing spectacular, as I prefer going slowly, step by step.
I don't play game neither watch video, just call, textmessage, google read, browse internet and tapatalk.
Only use Extweaks.
CPU : second core loads above 55% and disbaled below 40%. I think I can further about using less the 2nd core.
Min Freq below second core is not turned on : 100000 KHZ
GPU Freq step : 160,267,267
GPU Voltage levels : 900,1000,1000 mV
Screen : ToucheMove sensitivity : 2 pixel. One of the best tweak according to me
CPU Govenor/scheduler : Lulzactive with cfq.
Everything else is by default
EDIT : more precise settings
CPU : second core loads above 65% and disbaled below 40%.
want to get a higher hot plug sampling interval than the 100 jiffies default, but the app can't save higher numbers. Don't know why.
Min Freq below second core is not turned on : 70000 KHZ
CPU Smooth Scaling Settings are all to 2 (default). It is only for ON DEMAND and CONSERVATIVE governors.
GPU Freq step : 160,200,267
GPU Voltage levels : 900,1000,1000 mV
GPU Thresholds : 85%,70%,85%,65% (Can't understand too much, so leave default)
Screen : ToucheMove sensitivity : 2 pixel. One of the best tweak according to me
CPU Govenor/scheduler : Lulzactive with cfq.
MISC : disabled Android Logger (don't need any log file) and Auto-root : my device is already rooted, so redondant.
keep up the good job dude!
Beta 7 was just released! Flashed it without any issues. Obviously, there were some fixes related to USB, because with Beta 6 (and Stock ROM), adb did not list my device nor did MTP work. Now both things are working fine.
I have been with the Kernel Siyah long time for my S2 is the best.
I have a small problem is that everytime I connect the phone to the PC the melodies are unconfigured default to its original state, would not be bad fix in future versions. Although not a fault record, if that is annoying ...
Sorry for my English, I use google translator
Ap0calipsis said:
I have been with the Kernel Siyah long time for my S2 is the best.
I have a small problem is that everytime I connect the phone to the PC the melodies are unconfigured default to its original state, would not be bad fix in future versions. Although not a fault record, if that is annoying ...
Sorry for my English, I use google translator
Click to expand...
Click to collapse
your english is fine. If you are talking about songs then maybe try either sorting them in a folder or playlists. Not sure what could be the problem as the kernel would not mess with anything regarding melodies or whatever you are talking about my friend.
@All first post now has been updated with a link to GM's personal blog site were you can find changelogs for the latest betas and download links to them
Results for Siyah / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on ICS XXLPQ ROM (Modem: XXLPQ).
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
I just flashed SiyahKernel v3.0beta7, done some benchmarks and added its results.
Here are my current results:
Benchmarks
Quadrant Standard 2.0 (best of 3 runs)
Siyah v3.0beta6: 4166
Siyah v3.0beta5: 4156
Stock XXLPQ kernel: 4063
Siyah v3.0beta7: 4060
Siyah v3.0beta3: 3983
Siyah v3.0beta4: 3953
NenaMark2 (best of 3 runs)
Stock XILA2 kernel: 54,3
Stock XWLA4 kernel: 54,2
Siyah v3.0beta7: 52,2
Siyah v3.0beta6: 52,0
Stock XXLPQ kernel: 51,3
Siyah v3.0beta5: 50,4
Siyah v3.0beta3: 50,3
Siyah v3.0beta4: 50,0
Stock XWKK5 kernel: 47,8
Stock XWKK2 kernel: 47,6
Stock XWKL1 kernel: 38,1
Vellamo (best of 2 runs)
Siyah v3.0beta6: 1273
Siyah v3.0beta7: 1255
Stock XXLPQ kernel: 1247
Stock XILA2 kernel: 1225
Stock XWLA4 kernel: 1216
Siyah v3.0beta3: 1174
Stock XWKL1 kernel: 1173
Stock XWKK5 kernel: 1160
Siyah v3.0beta5: 1138
Siyah v3.0beta4: 1081
Stock XWKK2 kernel: 1080
Linpack (best of 10 runs): Single / Multi thread
Stock XWLA4 kernel: 57.816 / 93.548
Stock XILA2 kernel: 57.302 / 91.667
Stock XXLPQ kernel: 48.208 / 80.013
Siyah v3.0beta7: 47.363 / 79.597
Siyah v3.0beta3: 47.390 / 78.816
Siyah v3.0beta4: 47.633 / 77.370
Siyah v3.0beta6: 47.850 / 76.702
Siyah v3.0beta5: 47.150 / 75.800
CF-Bench (best of 2 runs): Native / Java / Overall score
Siyah v3.0beta7: 11246 / 3638 / 6681
Stock XWLA4 kernel: 11396 / 3539 / 6681
Siyah v3.0beta6: 11144 / 3359 / 6473
Stock XILA2 kernel: 11285 / 3187 / 6426
Siyah v3.0beta4: 11135 / 3265 / 6413
Stock XXLPQ kernel: 10862 / 3044 / 6171
Siyah v3.0beta3: 10716 / 2906 / 6030
Siyah v3.0beta5: 10529 / 2790 / 5885
AnTuTu (1st run)
Siyah v3.0beta6: 6136
Siyah v3.0beta7: 6122
Stock XILA2 kernel: 6110
Stock XXLPQ kernel: 6075
Stock XWLA4 kernel: 6009
Siyah v3.0beta4: 5654
Siyah v3.0beta5: 5593
Siyah v3.0beta3: 5414
Click to expand...
Click to collapse
Battery stats
Night use (wifi, synch, Talk and Skype on)
XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
Siyah v3.0beta5: Battery loss of 1,05% per hour, Awake: 8,4%, Deep sleep: 90%
Siyah v3.0beta4: Battery loss of 1,08% per hour, Awake: 7,8%, Deep sleep: 91%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
Siyah v3.0beta3: Battery loss of 1,14% per hour, Awake: 8,1%, Deep sleep: 91%
Siyah v3.0beta6: Battery loss of 1,19% per hour, Awake: 8,6%, Deep sleep: 90%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Mixed (day and night) usage (*)
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
Siyah v3.0beta5: Battery loss of 2,45% per hour, Wifi: 89,9%, Awake: 19,6%, Deep sleep: 80%, Screen: 9,9% => loss*(1-screen): 2,21%
Siyah v3.0beta3: Battery loss of 2,45% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 9,7% => loss*(1-screen): 2,21%
Siyah v3.0beta6: Battery loss of 2,48% per hour, Wifi: 100%, Awake: 20,7%, Deep sleep: 79%, Screen: 10,6% => loss*(1-screen): 2,22%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
Siyah v3.0beta4: Battery loss of 2,50% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,4% => loss*(1-screen): 2,24%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery loss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
Click to expand...
Click to collapse
SiyahKernel v3.0beta7 seems to be very good.
I am curious about its battery savings.
Will update my results here as soon as my tests are finished.
Hi all
I am using Cyanogen mod 9 nightlies built 270312 on siyah kernal 3.7 beta. Just found out that my battery is draining fast due to kernal or mod. I m pasting the bss log for kernal as its eating the Max share
GSam Labs - Badass Battery Monitor - Export Data
Kernel
Mar 27, 2012 6:08:03 PM
Usage Details
CPU Usage: 14m 30s
Included Packages
Included Processes
loop28
loop29
loop26
loop27
loop7
loop6
irq/353-k3g
vold
loop5
file-storage
loop4
loop24
loop25
loop22
loop8
loop23
loop2
irq/359-max8997
bdi-default
loop15
loop16
loop17
loop18
debuggerd
loop19
kworker/u:22
kworker/u:21
kworker/u:20
loop10
kworker/u:26
kworker/u:25
loop12
kworker/u:24
loop13
kworker/u:23
loop14
kworker/u:27
kworker/u:28
dhd_watchdog
jbd2/mmcblk0p10
kswapd0
irq/356-mxt224_
/init
flush-179:24
flush-179:0
khubd
dhd_dpc
sync_supers
jbd2/mmcblk0p7-
kworker/u:4
kworker/u:3
loop39
kworker/u:6
loop38
kworker/u:5
loop37
kworker/u:8
kworker/u:7
kworker/u:9
loop32
loop31
loop30
kworker/0:0
kworker/u:0
loop36
kworker/0:1
loop35
kworker/u:2
kworker/0:2
loop34
kworker/0:3
kworker/u:1
loop33
loop50
sh
ueventd
loop49
loop48
loop41
loop43
loop42
loop45
loop44
loop47
installd
loop46
ksoftirqd/0
mmcqd/1
loop59
loop57
loop56
mmcqd/0
adbd
netd
loop54
loop53
watchdog/0
loop51
zygote
kworker/u:19
kworker/u:18
kworker/u:17
kworker/u:16
kworker/u:10
kworker/u:11
kworker/u:14
kworker/u:15
kworker/u:12
kworker/u:13
Sent from my GT-I9100 using XDA
Made a quick video showing the CWMR that comes with Siyah 3.X
BUG External sd not mounting from android
BUG External sd not mounting from android
i mean that there is no [root]/mnt/emmc link to the sd card
i also cant connect to the pc (debug, normal (i know this is disabled) & the mentioned app)
if these are fixed i will use it for my ics.
i am a returning user, used the android 2.3.6 version before and i am very satisfied the the performance an batt. life of that version.
I use antutu cpu master and have problem ... Phone freeze and than restart. Ics samsung bild LP3 and siyah kernel v3.0beta7. Someone else have this problem? Somehow,i returned cpu on 1200 ... All work ok;now.
Sent from my GT-I9100 using Tapatalk
Results for Siyah / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on ICS XWLP3 „Frankenstein“ ROM (Modem: XXLPR).
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
I changed my base ROM to XWLP3 and re-tested SiyahKernel v3.0beta5.
Here are my current results:
Benchmarks
Quadrant Standard 2.0 (best of 3 runs)
Siyah v3.0beta5: 4241
Siyah v3.0beta6 (XXLPQ): 4166
Siyah v3.0beta5 (XXLPQ): 4156
Stock XWLP3 kernel: 4153
Stock XXLPQ kernel: 4063
NenaMark2 (best of 3 runs)
Stock XILA2 kernel: 54,3
Stock XWLA4 kernel: 54,2
Siyah v3.0beta6 (XXLPQ): 52,0
Stock XWLP3 kernel: 51,9
Stock XXLPQ kernel: 51,3
Siyah v3.0beta5 (XXLPQ): 50,4
Siyah v3.0beta5: 50,3
Stock XWKK5 kernel: 47,8
Stock XWKK2 kernel: 47,6
Stock XWKL1 kernel: 38,1
Vellamo (best of 2 runs)
Siyah v3.0beta5: 1296
Stock XWLP3 kernel: 1285
Siyah v3.0beta6 (XXLPQ): 1273
Stock XXLPQ kernel: 1247
Stock XILA2 kernel: 1225
Stock XWLA4 kernel: 1216
Stock XWKL1 kernel: 1173
Stock XWKK5 kernel: 1160
Siyah v3.0beta5 (XXLPQ): 1138
Stock XWKK2 kernel: 1080
Linpack (best of 10 runs): Single / Multi thread
Stock XWLA4 kernel: 57.816 / 93.548
Stock XILA2 kernel: 57.302 / 91.667
Siyah v3.0beta5: 48.015 / 80.317
Stock XWLP3 kernel: 48.015 / 80.317
Stock XXLPQ kernel: 48.208 / 80.013
Siyah v3.0beta6 (XXLPQ): 47.850 / 76.702
Siyah v3.0beta5 (XXLPQ): 47.150 / 75.800
CF-Bench (best of 2 runs): Native / Java / Overall score
Stock XWLA4 kernel: 11396 / 3539 / 6681
Siyah v3.0beta5: 11113 / 3386 / 6476
Siyah v3.0beta6 (XXLPQ): 11144 / 3359 / 6473
Stock XILA2 kernel: 11285 / 3187 / 6426
Stock XWLP3 kernel: 10795 / 3212 / 6245
Stock XXLPQ kernel: 10862 / 3044 / 6171
Siyah v3.0beta5 (XXLPQ): 10529 / 2790 / 5885
AnTuTu (1st run)
Siyah v3.0beta6 (XXLPQ): 6136
Stock XILA2 kernel: 6110
Stock XWLP3 kernel: 6109
Stock XXLPQ kernel: 6075
Siyah v3.0beta5: 6009
Stock XWLA4 kernel: 6009
Siyah v3.0beta5 (XXLPQ): 5593
Click to expand...
Click to collapse
Battery stats
Night use (wifi, synch, Talk and Skype on)
XWLP3: Battery loss of 0,89% per hour, Awake: 6,6%, Deep sleep: 93%
XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
Siyah v3.0beta5: Battery loss of 0,95% per hour, Awake: 7,4%, Deep sleep: 90%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
Siyah v3.0beta5 (XXLPQ): Battery loss of 1,05% per hour, Awake: 8,4%, Deep sleep: 90%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
Siyah v3.0beta6 (XXLPQ): Battery loss of 1,19% per hour, Awake: 8,6%, Deep sleep: 90%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Mixed (day and night) usage (*)
XWLP3: Battery loss of 1,91% per hour, Wifi: 89,1%, Awake: 16,9%, Deep sleep: 83%, Screen: 10,3% => loss*(1-screen): 1,71%
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
Siyah v3.0beta5: Battery loss of 2,32% per hour, Wifi: 91,2%, Awake: 16,7%, Deep sleep: 83%, Screen: 9,7% => loss*(1-screen): 2,09%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
Siyah v3.0beta5 (XXLPQ): Battery loss of 2,45% per hour, Wifi: 89,9%, Awake: 19,6%, Deep sleep: 80%, Screen: 9,9% => loss*(1-screen): 2,21%
Siyah v3.0beta6 (XXLPQ): Battery loss of 2,48% per hour, Wifi: 100%, Awake: 20,7%, Deep sleep: 79%, Screen: 10,6% => loss*(1-screen): 2,22%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery lss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
Click to expand...
Click to collapse
SiyahKernel v3.0beta5 performs a little better on XWLP3 ROM than on XXLPQ on my phone.
New ICS stock kernels seem to be kind of "battery optimized" compared to the older GB kernels.
So, it is harder to get better battery life for custom kernels - at least without UC/UV/etc..
Will re-test SiyahKernel v3.0beta6 on XWLP3 and post my results as soon as my tests are finished.
Results for Siyah / SpeedMod / N.E.A.K. / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on ICS XWLP3 „Frankenstein“ ROM.
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For SiyahKernel and N.E.A.K., as there are many, many configurable settings, I have changed nothing - just default settings.
I flashed SiyahKernel v3.1beta1 and added its results.
Here are my current results:
Benchmarks
Quadrant Standard 2.0 (best of 3 runs)
SpeedMod K3-7: 4326
N.E.A.K. v2.0.2: 4324
SpeedMod K3-5: 4290
Siyah v3.0beta5: 4241
Stock XWLP3 kernel: 4153
Stock XXLPS kernel: 4100
Stock XXLPQ kernel: 4063
Stock XWLP4 kernel: 4046
Siyah v3.1beta1: 3889
Siyah v3.0.1: 3767
NenaMark2 (best of 3 runs)
Stock XILA2 kernel: 54,3
Stock XWLA4 kernel: 54,2
Siyah v3.1beta1: 52,5
SpeedMod K3-7: 52,3
SpeedMod K3-5: 52,3
Siyah v3.0.1: 52,1
Stock XWLP3 kernel: 51,9
Stock XXLPQ kernel: 51,3
N.E.A.K. v2.0.2: 51,2
Stock XXLPS kernel: 50,9
Stock XWLP4 kernel: 50,8
Siyah v3.0beta5: 50,3
Stock XWKK5 kernel: 47,8
Stock XWKK2 kernel: 47,6
Stock XWKL1 kernel: 38,1
Vellamo (best of 2 runs)
Stock XXLPS kernel: 1303
Siyah v3.0beta5: 1296
Stock XWLP3 kernel: 1285
Siyah v3.1beta1: 1281
Siyah v3.0.1: 1269
SpeedMod K3-5: 1254
Stock XXLPQ kernel: 1247
Stock XILA2 kernel: 1225
Stock XWLA4 kernel: 1216
N.E.A.K. v2.0.2: 1188
Stock XWKL1 kernel: 1173
Stock XWKK5 kernel: 1160
SpeedMod K3-7: 1145
Stock XWLP4 kernel: 1133
Stock XWKK2 kernel: 1080
Linpack (best of 10 runs): Single / Multi thread
Stock XWLA4 kernel: 57.816 / 93.548
Stock XILA2 kernel: 57.302 / 91.667
N.E.A.K. v2.0.2: 48.070 / 82.317
Stock XXLPS kernel: 47.203 / 80.586
Siyah v3.1beta1: 48.125 / 80.548
Siyah v3.0beta5: 48.015 / 80.317
Stock XWLP3 kernel: 48.015 / 80.317
Siyah v3.0.1: 47.823 / 80.089
Stock XXLPQ kernel: 48.208 / 80.013
SpeedMod K3-7: 47.687 / 79.975
Stock XWLP4 kernel: 47.660 / 79.635
SpeedMod K3-5: 47.552 / 79.298
CF-Bench (best of 2 runs): Native / Java / Overall score
Stock XWLA4 kernel: 11396 / 3539 / 6681
SpeedMod K3-7: 11334 / 3394 / 6570
Siyah v3.0.1: 11094 / 3545 / 6564
Siyah v3.0beta5: 11113 / 3386 / 6476
Siyah v3.1beta1: 11030 / 3382 / 6441
Stock XILA2 kernel: 11285 / 3187 / 6426
Stock XWLP4 kernel: 10997 / 3338 / 6401
SpeedMod K3-5: 10980 / 3247 / 6340
N.E.A.K. v2.0.2: 11085 / 3503 / 6535
Stock XWLP3 kernel: 10795 / 3212 / 6245
Stock XXLPS kernel: 10791 / 3160 / 6212
Stock XXLPQ kernel: 10862 / 3044 / 6171
AnTuTu (1st run)
Siyah v3.1beta1: 6362
Siyah v3.0.1: 6287
Stock XILA2 kernel: 6110
Stock XWLP3 kernel: 6109
Stock XXLPQ kernel: 6075
Siyah v3.0beta5: 6009
Stock XWLA4 kernel: 6009
Stock XWLP4 kernel: 5941
Stock XXLPS kernel: 5912
N.E.A.K. v2.0.2: 4914
SpeedMod K3-7: 4670
SpeedMod K3-5: 4643
Click to expand...
Click to collapse
Battery stats
Night use (wifi, synch, Talk and Skype on)
XWLP3: Battery loss of 0,89% per hour, Awake: 6,6%, Deep sleep: 93%
SpeedMod K3-5: Battery loss of 0,92% per hour, Awake: 6,8%, Deep sleep: 92%
XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
SpeedMod K3-7: Battery loss of 0,95% per hour, Awake: 7,2%, Deep sleep: 91%
Siyah v3.0beta5: Battery loss of 0,95% per hour, Awake: 7,4%, Deep sleep: 90%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
XWLP4: Battery loss of 1,01% per hour, Awake: 7,7%, Deep sleep: 91%
N.E.A.K. v2.0.2: Battery loss of 1,02% per hour, Awake: 7,2%, Deep sleep: 92%
Siyah v3.1beta1: Battery loss of 1,03% per hour, Awake: 7,2%, Deep sleep: 92%
XXLPS: Battery loss of 1,05% per hour, Awake: 7,6%, Deep sleep: 91%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Mixed (day and night) usage (*)
XWLP3: Battery loss of 1,91% per hour, Wifi: 89,1%, Awake: 16,9%, Deep sleep: 83%, Screen: 10,3% => loss*(1-screen): 1,71%
XXLPS: Battery loss of 1,94% per hour, Wifi: 100%, Awake: 18,0%, Deep sleep: 81%, Screen: 11,5% => loss*(1-screen): 1,72%
SpeedMod K3-7: Battery loss of 2,12% per hour, Wifi: 100%, Awake: 18,1%, Deep sleep: 81%, Screen: 11,3% => loss*(1-screen): 1,88%
Siyah v3.1beta1: Battery loss of 2,17% per hour, Wifi: 100%, Awake: 16,1%, Deep sleep: 83%, Screen: 9,0% => loss*(1-screen): 1,97%
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
Siyah v3.0beta5: Battery loss of 2,32% per hour, Wifi: 91,2%, Awake: 16,7%, Deep sleep: 83%, Screen: 9,7% => loss*(1-screen): 2,09%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
SpeedMod K3-5: Battery loss of 2,56% per hour, Wifi: 100%, Awake: 17,8%, Deep sleep: 82%, Screen: 10,8% => loss*(1-screen): 2,28%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery loss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
Click to expand...
Click to collapse
SiyahKernel v3.1beta1 is very stable and smooth with good battery savings on my phone.
Will definitely come back to test newer versions of this great kernel.
Maybe with a new "base" ROM.
Very solid kernel, only one problem with Wescrip's Res Remix v1.3 - The front facing camera keeps getting a fc.
AOKP + Siyah v3
I am running and I777 (on an I777) version of AOKP and when I flash Siyah Kernel v3.0.1 the data usage monitoring stops functioning properly. It works fine with the CM9 kernel that is built into the ROM.
Has anyone experienced this issue with Siyah v3 on AOKP or other ROMs?
Thanks =]
Results for SpeedMod / Phenomenal / Siyah / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on ICS XWLP8 „Frankenstein“ ROM.
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For all kernels, I have changed nothing - just default settings.
I flashed SiyahKernel v3.1 and added its results.
Here are my current results:
Benchmarks
Quadrant Standard 2.0 (best of 3 runs)
Phenomenal 5.0: 4303
SpeedMod K3-11: 4295
Phenomenal 5.1: 4181
Stock XWLP3 kernel: 4153
Stock XWLP7 kernel: 4131
Stock XXLPS kernel: 4100
Siyah v3.1: 4099
Stock XWLP8 kernel: 4074
Stock XXLPQ kernel: 4063
Stock XWLP4 kernel: 4046
NenaMark2 (best of 3 runs)
Stock XILA2 kernel: 54,3
Stock XWLA4 kernel: 54,2
SpeedMod K3-11: 52,2
Siyah v3.1: 52,0
Stock XWLP7 kernel: 52,0
Stock XWLP8 kernel: 51,9
Stock XWLP3 kernel: 51,9
Stock XXLPQ kernel: 51,3
Stock XXLPS kernel: 50,9
Stock XWLP4 kernel: 50,8
Stock XWKK5 kernel: 47,8
Stock XWKK2 kernel: 47,6
Phenomenal 5.0: 42,1
Stock XWKL1 kernel: 38,1
Phenomenal 5.1: 34,2
Vellamo (best of 2 runs)
Stock XXLPS kernel: 1303
Stock XWLP3 kernel: 1285
Stock XWLP8 kernel: 1281
Stock XWLP7 kernel: 1270
Siyah v3.1: 1256
SpeedMod K3-11: 1252
Stock XXLPQ kernel: 1247
Phenomenal 5.0: 1234
Stock XILA2 kernel: 1225
Stock XWLA4 kernel: 1216
Stock XWKL1 kernel: 1173
Phenomenal 5.1: 1170
Stock XWKK5 kernel: 1160
Stock XWLP4 kernel: 1133
Stock XWKK2 kernel: 1080
Linpack (best of 10 runs): Single / Multi thread
Stock XWLA4 kernel: 57.816 / 93.548
Stock XILA2 kernel: 57.302 / 91.667
Stock XXLPS kernel: 47.203 / 80.586
SpeedMod K3-11: 47.177 / 80.432
Stock XWLP3 kernel: 48.015 / 80.317
Stock XWLP8 kernel: 48.152 / 80.203
Phenomenal 5.0: 47.498 / 80.203
Stock XXLPQ kernel: 48.208 / 80.013
Phenomenal 5.1: 47.606 / 79.748
Stock XWLP4 kernel: 47.660 / 79.635
Stock XWLP7 kernel: 48.125 / 79.112
Siyah v3.1: 48.015 / 78.159
CF-Bench (best of 2 runs): Native / Java / Overall score
Phenomenal 5.1: 11343 / 3656 / 6730
Stock XWLA4 kernel: 11396 / 3539 / 6681
SpeedMod K3-11: 11211 / 3395 / 6521
Phenomenal 5.0: 11038 / 3462 / 6492
Stock XILA2 kernel: 11285 / 3187 / 6426
Stock XWLP4 kernel: 10997 / 3338 / 6401
Stock XWLP8 kernel: 10968 / 3335 / 6388
Stock XWLP3 kernel: 10795 / 3212 / 6245
Stock XXLPS kernel: 10791 / 3160 / 6212
Stock XXLPQ kernel: 10862 / 3044 / 6171
Siyah v3.1: 10617 / 3131 / 6125
Stock XWLP7 kernel: 10354 / 2901 / 5882
AnTuTu (1st run)
Stock XWLP8 kernel: 6201
Stock XILA2 kernel: 6110
Stock XWLP3 kernel: 6109
Siyah v3.1: 6082
Stock XXLPQ kernel: 6075
Stock XWLA4 kernel: 6009
Stock XWLP4 kernel: 5941
Stock XXLPS kernel: 5912
Stock XWLP7 kernel: 5496
Phenomenal 5.1: 4907
SpeedMod K3-11: 4827
Phenomenal 5.0: 4805
Click to expand...
Click to collapse
Battery stats
Night use (wifi, synch, Talk and Skype on)
Phenomenal 5.1 Extreme: Battery loss of 0,77% per hour, Awake: 6,7%, Deep sleep: 93%
XWLP3: Battery loss of 0,89% per hour, Awake: 6,6%, Deep sleep: 93%
Siyah v3.1: Battery loss of 0,90% per hour, Awake: 6,9%, Deep sleep: 93%
XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
XWLP7: Battery loss of 0,96% per hour, Awake: 6,8%, Deep sleep: 90%
SpeedMod K3-11: Battery loss of 0,98% per hour, Awake: 6,7%, Deep sleep: 93%
XWLP4: Battery loss of 1,01% per hour, Awake: 7,7%, Deep sleep: 91%
XWLP8: Battery loss of 1,02% per hour, Awake: 7,6%, Deep sleep: 92%
XXLPS: Battery loss of 1,05% per hour, Awake: 7,6%, Deep sleep: 91%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Mixed (day and night) usage (*)
Phenomenal 5.1 Extreme: Battery loss of 1,73% per hour, Wifi: 100%, Awake: 18,5%, Deep sleep: 81%, Screen: 10,5% => loss*(1-screen): 1,55%
XWLP3: Battery loss of 1,91% per hour, Wifi: 89,1%, Awake: 16,9%, Deep sleep: 83%, Screen: 10,3% => loss*(1-screen): 1,71%
XXLPS: Battery loss of 1,94% per hour, Wifi: 100%, Awake: 18,0%, Deep sleep: 81%, Screen: 11,5% => loss*(1-screen): 1,72%
SpeedMod K3-11: Battery loss of 2,08% per hour, Wifi: 100%, Awake: 18,8%, Deep sleep: 81%, Screen: 11,3% => loss*(1-screen): 1,84%
Siyah v3.1: Battery loss of 2,10% per hour, Wifi: 100%, Awake: 18,5%, Deep sleep: 81%, Screen: 9,9% => loss*(1-screen): 1,89%
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
XWLP7: Battery loss of 2,31% per hour, Wifi: 75,8%, Awake: 17,3%, Deep sleep: 82%, Screen: 9,7% => loss*(1-screen): 2,09%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
XWLP8: Battery loss of 2,54% per hour, Wifi: 100%, Awake: 20,1%, Deep sleep: 79%, Screen: 10,9% => loss*(1-screen): 2,26%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery loss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
Click to expand...
Click to collapse
SiyahKernel v3.1 is very stable and smooth on my phone.
With default settings, I have some problems with the touch sensivity: Some clicks/tabs are interpreted as swipes.
Maybe I am too nervous when running SiyahKernel.
Battery savings are good - even on completely default settings (no UV/UC).
Well done gokhanmoral !
Related
I run taboonay 2.0 with the thor 3.3 kernel.
I use setcpu with the following profiles:
Default: 216-1200
Charging: 1200-1472
Screen off: 216-608
Battery < 50%: 216-1000
Battery < 20%: 216-912
Speed-voltages:
216-730
312-760
456-825
608-900
760-900
816-900
912-900
1000-900
1200-950
1336-1000
1408-1050
1472-1100
Ihave not done stress testing on 456-816.
（Unofficial）Kernel Setting（battery,lagfree）（project T kernel and deathly kernel）
Project T kernel:
CPU:TheSSJactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:cubic
Deathly kernel:
CPU:yankactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:westwood
hope you guys have better battery life
angus63631 said:
Project T kernel:
CPU:TheSSJactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:cubic
Deathly kernel:
CPU:yankactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:westwood
hope you guys have better battery life
Click to expand...
Click to collapse
Exactly how much more battery life are we talking about here?
angus63631 said:
Project T kernel:
CPU:TheSSJactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:cubic
Deathly kernel:
CPU:yankactive（touch boost freq:1250000）
eMMC I/O:sio（battery）/zen（performance） cache:1024
sdcard I/O:fiops cache:512
zram: off（battery）/500mb（performance）
TCP:westwood
hope you guys have better battery life
Click to expand...
Click to collapse
Please share the SOT
followed t kernel setting. cheers.
Anyone can share step by step how to set the kernel?
Step 1 - install Kernel Adiutor from the Play Store (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor)
Step 2: Run Kernel Adiutor and adjust settings as above
Sent from my Golden Zenfone 2
I am testing.
Can OP share SOT?
Trying it out. Thanks!
Not much difference for me. I tested for 2 days. SOT also 4 hours plus which same as default settings and usage.
Anyway, thanks so much for sharing.
I thought it may be a good idea for folks to list what ROM / Kernel they are using and details on its stability. Since we have different versions of our phones and kernels / Rom combos I thought listing the details on what each of us use may help others.
Here is my best (or most stable) setup so far:
ROM: CM 12.1 Build 20160104
Phone: 6045I
TWRP VERSION: TWRP-2.8.7.1-test2
KERNEL: ARDE OC (But not OC'd right now)
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: XPOSED / FM RADIO / CM CAMERA MOD
SCHEDULER: Noop
GOVERNOR: Interactive
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 29,000
BATTERY LIFE: Excellent
Notes: This is my fallback daily driver build. This is what I have as my go-to TWRP backup. The battery life is even better than stock. For Xposed I use Greenify / BootManager / Burnt Toast / Xposed GEL Settings
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
ROM: PAC ROM 01.02.2016
Phone: 6045I
TWRP VERSION: TWRP-2.8.7.1-test2
KERNEL: ARDE
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: None
SCHEDULER: ROW
GOVERNOR: Interactive
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 31,000
BATTERY LIFE: Great
Notes: Only 1 day of use so far but battery life is very good. No reboots so far. Used the non OC ARDE kernel with no mods.
-With both the CM and PAC ROM I tend to flash the ROM then the ARDE kernel before the first boot.
Merged with OP
Phone: 6045Y
TWRP VERSION: TWRP-2.8.7.0
ROM: DCZ 1.03 - my perosnal rom based upon i806 firmware from 22.october.2015
KERNEL: ARDE OC @1,6 both clusters
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: personal mods (build.prop, LCD density, launcher mods, framework mods...)
SCHEDULER: flops (512kB read ahead)
GOVERNOR: Interactive both clusters
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 37,000
BATTERY LIFE: 3,5-5,0 based upon how long i play two dots (which is insane battery eater even the game is so simple. It eats about 20% battery after one hour). right now i am on 4hours SoT and 30% battery left.
Phone: 6045Y
TWRP VERSION: TWRP-2.8.7.0
ROM: CM 12.1 Build 20160128
KERNEL: New Kernel
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: no mods installed
SCHEDULER: Noop
GOVERNOR: Interactive
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 29,000
BATTERY LIFE: Good
Phone: 6045Y
TWRP VERSION: TWRP-2.8.7.0
ROM: CM 12.1 Build 04.01.2016
KERNEL: Arde Kernel
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: camera mods, xposed, alcatel camera, snapdragon camera..
SCHEDULER: Noop
GOVERNOR: Interactive
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 29,000
BATTERY LIFE: Almost like stock, i manage to get 5h SOT.
Phone: 6045I
TWRP: 2.8.7.0
ROM: DCZRom i806
Kernel: Arde OC
GAPPS: Open
REBOOTS: O
MODS: camera mod, Xposed
SCHEDULER: Deadline 1024k
GOVERNOR: Impulse on both
AnTuTu: ~33K
BATTERY LIFE: great?
Phone: 6045Y
TWRP VERSION: TWRP-3.0.0.0
ROM: MoKee
KERNEL: STOCK
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: XPOSED / CAMERA MOTO G
SCHEDULER: Noop
GOVERNOR: Interactive
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 29,000
BATTERY LIFE: Excellent
DallasCZ said:
Phone: 6045Y
TWRP VERSION: TWRP-2.8.7.0
ROM: DCZ 1.03 - my perosnal rom based upon i806 firmware from 22.october.2015
KERNEL: ARDE OC @1,6 both clusters
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: personal mods (build.prop, LCD density, launcher mods, framework mods...)
SCHEDULER: flops (512kB read ahead)
GOVERNOR: Interactive both clusters
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 37,000
BATTERY LIFE: 3,5-5,0 based upon how long i play two dots (which is insane battery eater even the game is so simple. It eats about 20% battery after one hour). right now i am on 4hours SoT and 30% battery left.
Click to expand...
Click to collapse
Please provide link to the firmware. I from Holland and I have also 6045y and my score in antutu is 28k... Little to slow. Please help.. Thank you
LucasNoob said:
Please provide link to the firmware. I from Holland and I have also 6045y and my score in antutu is 28k... Little to slow. Please help.. Thank you
Click to expand...
Click to collapse
ROM-6045-i806-dcz-stock-oc-kernel-root
DallasCZ said:
Phone: 6045Y
TWRP VERSION: TWRP-2.8.7.0
ROM: DCZ 1.03 - my perosnal rom based upon i806 firmware from 22.october.2015
KERNEL: ARDE OC @1,6 both clusters
GAPPS: Open Gapps arm64 - Nano
REBOOTS PER DAY: 0
MODS INSTALLED: personal mods (build.prop, LCD density, launcher mods, framework mods...)
SCHEDULER: flops (512kB read ahead)
GOVERNOR: Interactive both clusters
OTHER KERNEL TWEAKS: None
ATuTu SCORE: Usually about 37,000
BATTERY LIFE: 3,5-5,0 based upon how long i play two dots (which is insane battery eater even the game is so simple. It eats about 20% battery after one hour). right now i am on 4hours SoT and 30% battery left.
Click to expand...
Click to collapse
DallasCZ said:
ROM-6045-i806-dcz-stock-oc-kernel-root
Click to expand...
Click to collapse
This is same as yours?.. Or I must something modify or add to get 37k in antutu.. Can I install it via custom recovery 2.8 using bootloader and fast commands? Thank you so much for answering my question.
LucasNoob said:
This is same as yours?.. Or I must something modify or add to get 37k in antutu.. Can I install it via custom recovery 2.8 using bootloader and fast commands? Thank you so much for answering my question.
Click to expand...
Click to collapse
please read the threa dand ask questions there, because this thread is not about this.
DallasCZ said:
ROM-6045-i806-dcz-stock-oc-kernel-root
Click to expand...
Click to collapse
Hello I tried to flash new kernel but I get message can't flash... But if I only tried to load kernel to memory via bootloader it works fine for me no problem... Do you know what is wrong and I can't flash oc kernel.... Final Stock Oc? Thank you
LucasNoob said:
Hello I tried to flash new kernel but I get message can't flash... But if I only tried to load kernel to memory via bootloader it works fine for me no problem... Do you know what is wrong and I can't flash oc kernel.... Final Stock Oc? Thank you
Click to expand...
Click to collapse
please write to the desired dcz thread and not here. what new kernel?
There are a few topics discussing battery life in general but it's a bit difficult to find basic information as described below.
Discuss battery-life in this thread: Battery life discussion here
Template:
Model number:
SoT(Screen on time): ## hours, ## minutes
Time on battery: ## hours, ## minutes
Battery charge:
Firmware:
Android version:
Kernel:
Primary use:
Model number: SM-920F
SoT(Screen on time): 2 hours, 50 minutes
Time on battery: 17 hours, 2 minutes
Battery charge: 38%
Firmware: Xtrestolite Deo-Mod 3.0 FINAL
Android version: 6.0.1
Kernel: Hacker Kernel V14
Primary use: Browsing, Instagram and Snapchat
Model number: g920fd
SoT(Screen on time): ## 5 hours, ## 15 minutes
Time on battery: ## 20 hours, ## 11 minutes
Battery charge: 7 %
Firmware: stock last germany
Android version:6.0.1
Kernel: terminator - alexis
Primary use:coc-clash royale-chrome-telegram
choosing between Galaxy S6 and Nexus 5X, which one would you reccomend for battery life? Nexus 5x gives to me 2:30 maximux (probably 3 if not used much) of sot
I've got both and I don't know which one to keep for myself...
Model number: G920F
SoT(Screen on time): 2 hours, 3 minutes
Time on battery: 21 hours, 47 minutes
Battery charge: 36%
Firmware: Stock Rom BTU PF1
Android version: 6.0.1
Kernel: Arter v20
Primary use: Texting, Browsing, WhatsApp
physwizz a10 battery saver v2.3
Based on a105fn source code
@physwizz
-OneUI or GSI (Q or R)
-Most securities disabled
-new CPU Governors added: now has conservative, ondemand, userspace, powersave, interactive, performance.
-SE linux enforcing
-CPU underclocked
-Big: 312 - 1560
-Little: 343 - 1352
-Extended battery life
-Works with Magisk 19.3 - 21.4
-Spectrum support enabled
- MTP enabled
If you experience lagging remove animations from settings and use Spectrum or HKtweaks
If you want performance choose a different kernel.
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
Excellent Battery performance with no lags
this is works for a105g ?
TypeZSketcher said:
this is works for a105g ?
Click to expand...
Click to collapse
yes it does