Search This thread

rlorange

Senior Member
Nov 5, 2010
4,307
2,242
Melbourne
Not necessarily, because it can still jump to 1000 immediately, but when it falls it will fall like what you described meaning spend more time on higher clock speeds but not straight to 200 mhz. Also when switching clock speed cpu consumes more battery.

Not necessarily either. You are assuming ondemand behaviour with tuned lulzactive you CAN get even frequency use. Changing clock speed is irrelevant according to ACTUAL measurements.

This is a scientific exercise in myth busting. 100mhz consuming more than 200 as well as extra step switching consuming more are theories which have been floating around for long enough that everyone just accepted it as fact.

Sent from my GT-I9100 using xda premium
 

Doeyourthing

Senior Member
Feb 18, 2010
441
107
Netherlands
latest version

Latest version 3.2 (final) is given me a headache. On the phone backside around the camera is getting to hot. never got this before. Phone keep hanging after reboot.
Going back between version b6 en b8. At least b6 was great.
 

Bene2k11

Senior Member
Aug 25, 2011
145
44
Mhh, just updated to 3.2, using my old settings the phone gets hot and facebook is very sluggish... :/

(ondemand, 100-800mhz, UV, noop)
Edit: just like magic everything is smooth now, without doing anything. :D
 
Last edited:

Lady_Chloe

Senior Member
Apr 29, 2012
71
13
I have a question about the battery level. I have noticed that with this kernel, I can drain the battery to 78% for example, leave it be during the night and when I wake up in the morning, I have 79% of battery left. Indeed, when I look at the battery graph, it looks like it was increasing for some time after I switched the screen off. This happens during the day as well, there are "dents" in the graph when I look at it. This did not happen with the stock cf-root kernel. Should I calibrate the battery or is this normal?

Sent from my GT-I9100 using XDA
 

slekkas

Senior Member
Oct 25, 2007
686
113
Battery drain is massive on new rc2. Just from reading the last couple of pages I've lost 2% in 2 minutes. Using 3g on latest cm9. Had similar drain on rc1 too. Is this happening to anyone else?

I'm with wanamlite 11.5 with siyah 3.2rc2 and battery is great. 22 hours with 4 hours screen on. Wifi and 3g on.

Sent from my GT-I9100 using Tapatalk 2
 

sam razzy

Senior Member
Oct 12, 2011
3,755
596
Ma sweet home
If ppl as a massive battery drain problem... then please allow the battery to take one two charging cycle... battery life is superb on 3.2rc2

Sent from my GT-I9100 using Tapatalk 2
 

shawnaye

Senior Member
Sep 28, 2011
1,477
454
Not necessarily either. You are assuming ondemand behaviour with tuned lulzactive you CAN get even frequency use. Changing clock speed is irrelevant according to ACTUAL measurements.

This is a scientific exercise in myth busting. 100mhz consuming more than 200 as well as extra step switching consuming more are theories which have been floating around for long enough that everyone just accepted it as fact.

Sent from my GT-I9100 using xda premium

Hmm my cpu is still unevenly distributed.. Still hanging alot at 1000.

Sent from my GT-I9100 using XDA
 

confusedmuse

Senior Member
Dec 31, 2011
484
199
Speyer
I have a question about the battery level. I have noticed that with this kernel, I can drain the battery to 78% for example, leave it be during the night and when I wake up in the morning, I have 79% of battery left. Indeed, when I look at the battery graph, it looks like it was increasing for some time after I switched the screen off. This happens during the day as well, there are "dents" in the graph when I look at it. This did not happen with the stock cf-root kernel. Should I calibrate the battery or is this normal?

Sent from my GT-I9100 using XDA

You all shouldn't care too much about the battery gauge. It's an assumption based on the measured voltage. If you get 4 hours or more screen-on time and 2-4 days standby everything is fine.
 
Last edited:

olifee

Senior Member
Sep 12, 2011
239
166
OnePlus 6
right. thank you.
I was removing ntfs-3g from the payload to make the kernel smaller (to go back to LZO) most of you need readonly access and it will be provided by using kernel's internal ntfs support. and I will also make the battery default 35. then I will upload 3.2.1
Nice idea ;).
You could also save a lot of space by stripping the ntfs-3g-binary (shrank by half the size, down to 400k after xz -9e), might be useful for the other binaries still left ;).
 

gokhanmoral

Retired Senior Recognized Developer
Mar 16, 2006
3,744
25,415
48
Ankara
www.isyam.bilkent.edu.tr
Nice idea ;).
You could also save a lot of space by stripping the ntfs-3g-binary (shrank by half the size, down to 400k after xz -9e), might be useful for the other binaries still left ;).

really? I never tried to strip it, I thought it would already be stripped :)
anyway.. it's already removed.
kernel's inbuilt ntfs support works good enough for read-only access.
and people who need read/write support are generally advanced enough to run some scripts to mount it.
 
  • Like
Reactions: Crescendo Xenomorph

mrbuzz1967

Senior Member
Jun 17, 2010
446
50
grantham
Battery drain is massive on new rc2. Just from reading the last couple of pages I've lost 2% in 2 minutes. Using 3g on latest cm9. Had similar drain on rc1 too. Is this happening to anyone else?

me too. using rohit miui with all default settings apart from bln enabled. already done 1 charge cycle and at the moment about 1% a minute, same as you.
 

wallaceff

Senior Member
Aug 10, 2006
260
43
gokhanmoral:

Not sure if you saw my earlier post, but it seems when installing a rom to the second rom that includes a script to wipe the dalvik cache, the dalvik cache on the PRIMARY rom also gets wiped?

I didn't see any comment on the updates about this. I like to play with different roms at the moment, and its a pain. Any chance of a fix (if its not too complicated)?

I have CM9 on primary and Epsylon secondary (as an example).
 

olifee

Senior Member
Sep 12, 2011
239
166
OnePlus 6
really? I never tried to strip it, I thought it would already be stripped :)
anyway.. it's already removed.
kernel's inbuilt ntfs support works good enough for read-only access.
and people who need read/write support are generally advanced enough to run some scripts to mount it.
You're right, read access is by far sufficient and less error prone for the normal users ;).

I only noticed it by chance just a few minutes ago using the file-command (sadly not installed by default on many debian-based OS's). A small debian-arm-chroot on my laptop made stripping it really easy then, this is really helpful to try out binaries and even do a quick compile before trying them on the phone :).

Busybox appears to be stripped already, so sadly no further gains ;).
 

kwerdenker

Senior Member
Apr 1, 2010
1,451
2,533
Probably the Zooper Forums
Following the motto often found in teams "Whoever has the idea, has to do the work" I did a little snooping around to figure out the pseudo-color BLN stuff and I think I got it.

I began by finding the API to allow apps to set the LED color, which is part of the standard Notification-class and then tracing it's way through the different layers to the kernel hand-off point. For anyone interested to follow my steps: NotificationManagerService.java -> LightsService.java -> com_android_server_LightsService.cpp. From there it out of the framework and into libhardware/liblights. liblights is the hand-off point between OS and kernel and here it gets interesting.

The notifcations are handed down from the OS using the struct light_state_t ( defined in libhardware/include/lights.h), which has the color property. In our implementation of light.c, this property is largely ignored. On other platforms (I used msm7k as an comparison), you can see this property is used to feed the different brightness values to the corresponding LEDs. If you look at that lights.c implementation, you can also see they have three single LED interfaces for the different colors rather than one RGB interface. This would explain why you only know about the one parameter, gokhan.

Now, the conclusion from all this is:
1) liblight definitely needs to be patched to actually use the RGB values from the notifications
2) We need a way to let the kernel know these values. Either the kernel implements a new interface to accept the full RGB value/the three single colors as a parameter and then does the mapping internally or liblight decodes and maps the colors and then writes a selection value to the notification interface which then uses that value to display the selected effect. The first version is probably the preferable way but I admit to know too little about the kernelside to estimate the complexity of this.

I hope this helps you gokhan to figure things out. If you need me to provide you with more infos or if I can assist in some other way, just let me know :)
 
Last edited:

bernard134

Senior Member
Mar 5, 2010
905
120
Singapore
i don't know why but when finish flashing siyah kernel v3.2, my phone Amoled display will show line of greyish color at the right side of the screen from top to bottom when displaying any grey color. It very obvious when i pull down the notification bar, because its grey, no issue with other color like black, white and all others. Also happen when i flash N.E.A.K kernel, but i tried CF-Root kernel no such issue.

any one encounter this issue?
 

Canadoc

Senior Member
Nov 29, 2010
1,828
133
Samsung Galaxy S23 Ultra
OK I have a favour here. MY first priority is great battery life and second responsiveness. I do not care for BLN. I am currently on Wanamlite 11.5.
I have the free version of extweaks. So my question is :

Can someone recommend settings adjustments in EXTweaks that would provide me with the best battery life that would not sacrifice responsiveness in any significant way?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1352
    please leave non-dev related posts here: http://xdaforums.com/showthread.php?t=1658647

    siyahkernel-ics-wide1.png

    Features:
    • based on JB sources
    • DISABLED CAP_ERASE (No superbrick bug)
    • All-in-1kernel because it supports CM9, CM10, Samsung, MIUI and Boot-to-Gecko (B2G) ROMs with a single kernel image. (no Sense4all support)
    • Dual booting support for all supported ROM types. See droidphile's post for Dual Booting FAQ
    • Custom CWM touch recovery with swipe gestures and double-tap selection
    • 6-steps CPU freq
    • 5-step GPU frequency levels. VPLL Mode to have additional frequency steps. defaults frequencies: 66-108-166-267-330.
    • Auto-root. You can also remove root via STweaks app and install it without rebooting your phone again. Auto-root can be disabled as well.
    • CPU Overclock/Undervolt support (we have two interfaces for that. both of them are defacto standard)
    • Tweakable vitalij's value (set to 5 as default)
    • Adjustable touchpad led brightness
    • Fixed fuelalert wakelocks
    • You can completely disable android logger using STweaks app
    • Faster charging for misc and USB modes. There are 3 modes (AC, Misc, USB) and normally last two of them support only slow charging. You can have charging speed of AC by increasing it (especially user while charging in car or using USB port)
    • Cpu governor optimizations
    • Gpu voltage, clock and stepcount interfaces (GPU Overclock/Undervolt)
    • Screen brightness curve settings with original panel gamma values. panel values unchanged, so you will get stock colors and will be able to use supercurio's voodoo display app when it is released. brightness modification will only change auto-brightness response.
    • BLN support both for Samsung and CM ROMs (you can use STweaks, Nstools or BLNControl app from the market to enable it)
    • Breathing or Blinking effect for BLN. (Make sure you don't enable blinking in any other BLN app) Use STweaks to select one of them.
    • Better touch sensitivity
    • Available CPU Governors: Pegasusq (default), Ondemand, Lulzactive, SmartassV2, Interactive and Conservative, Performance, Userspace, Powersave
    • CIFS as module
    • Available I/O schedulers: CFQ (default), noop, Deadline, SIO, V(R)
    • J4FS as module
    • ARM topology support (SCHED_MC)
    • Automatic EFS Backup
    • Lots of I/O tweaks and filesystem optimizations via some parts of thunderbolt scripts.
    • USB Mass Storage mode is working in CWM Touch Recovery and you can mount both internal and external sdcard as a disk drive
    • NTFS automounting for USB sticks. When you plug in an NTFS formatted USB flash it will be automatically mounted to /mnt/ntfs folder.
    • USB mouse and keyboard support
    • built-in profile support with default, battery and performance presets (you can change them in CWM Recovery). Even using everything default will save you a lot of battery juice.
    • Eargasm for headphone amplification (in STweaks) as free Voodoo Louder replacement
    • Almost everything is configurable such as scheduler features, hotplug thresholds, GPU frequencies, voltages, arm topology modes... and they are configurable via simple and free STweaks app which is embedded in the kernel and soon in Google Play & Opensource
    • Adjustable mDNIe settings
    • optional sharpness tweaks from hardcore
    • mDNIe negative effect toggle with home button (press it four times)
    • Touch gesture support by Tungstwenty. (http://xdaforums.com/showthread.php?t=1831254)
    • BLNWW (BLN Without Wakelock)
    • Slide2Wake (originally by Fluxi)

    More to come...


    Known Problems:
    • no known problems yet

    Thanks To:

    • Chainfire, Codeworkx, Arighi, Tegrak, Vitalij, Entropy512, Netarchy, koush, Creams, sk8erwitskil, hardcore, Pikachu, myfluxi, Tungstwenty
    • This part will be expanded. most of the patches I applied are coded by someone else. please remind me if I forget to give credits to anybody..

    IRC support and chat:
    Server: irc.FreeNode.net
    Channel: #siyah-kernel
    web client: http://siyah.twosx.net/ (thanks to omniwolf)
    Changelog:

    See http://www.gokhanmoral.com/ for changelog.

    You can find the sources at http://github.com/gokhanmoral/siyahkernel3
    and initramfs at http://github.com/gokhanmoral/initramfs3

    Todo:
    these are my future plans and some of them are dreams only...
    • apply chargecurrent modifications even if the cable is connected on boot
    • add optional teamwin recovery
    • make dual-boot timeout configurable
    • implement BFN (BackFlashNotification)
    • scheduling for BLN
    • organize recovery menu items
    • higher polling rate for light sensor
    • remap mouse right button to back button
    • exfat support
    • fix blnww battery drain issue (may not be possible)
    • implement dual-booting with GB+ICS ROMs
    • faster switch between first and second ROMs without needing to reboot if possible.
    ...

    298
    troubleshooting

    siyahkernel-ics-wide1.png

    READ THESE FIRST

    • Never report any bugs to CM9/CM10 threads if you use it together with SiyahKernel
    • Do not ask questions to me directly. This is a common thread, not my personal inbox. Ask your questions in the thread and do not target them to anyone.
    • Do not expect answers to all your questions. There are some questions which nobody knows the answer of.
    • Do not forget that this is a development thread. There is another thread in general section for those who wants to discuss battery life and chats. If your post does not include a feature request, bug report or suggestion it should be posted to the other thread.
    • No ETA for new version. Even if I sometimes talk about release dates those may change and they change for some good reason or because of my real-life obligations.
    • Make use of "Search this Thread -> Advanced Search"
    • Never ever discuss anything deep-sleep related in this thread. I do not make modifications to prevent sleep and 99% of deep sleep problems are application/ROM related. discuss it in general section. I do not want any positive ("this kernel sleeps like a baby") or negative ("There is a big problem with deep sleep. Please fix it") messages in my development thread.
    • If you do not provide details about your configuration and settings nobody can help you or nobody will care about your problem/bug report. The problems without details (ROM, settings, preferably the version that the problem first happened or the one that you don't experience the problem) will be ignored.
    • Never ever report any SOD issues if you are undervolting/overclocking and make sure you attach last_kmsg log. If you don't know what it is report the problem to the other thread because one more post without any useful information on dev thread will help noone including yourself.


    FAQ:

    Q: I am having some random lockups with some apps
    A: try removing root by using STweaks app and restart.

    Q: What is the difference between STweaks and ExTweaks?
    A: Both have similar functionality. ExTweak is Xan's implementation of the UCI interface (which is designed by Xan and me with the helps of AndreiLux and implemented in the kernel as open scripts by me) and STweaks is mine. I was hoping Xan would release the sources of ExTweaks (without profile support) but he changed his mind and I decided to open STweaks. Soon they will have almost identical functionality, so you can use whichever you like.

    Q: Does this kernel work on XXXXXX-ROM?
    A: If the ROM is based on Samsung Stock ICS Rom LPQ or newer, it should. Otherwise, search the thread... If you cannot find any reference to that ROM, try the kernel. You won't lose anything by trying this kernel. Worst case scenario is to reflash your previous kernel or ROM. You can backup your previous kernel with Hellcat's k-tool from the market.

    Q: Where is CM9, MIUI or Samsung ROM versions?
    A: There is only one version. Both ROMs are supported with a single kernel image.

    Q: What is the best settings?
    A: It is the one you try yourself and like.

    Q: I have just lost 20-30% battery by just rebooting/flashing the kernel. Is it a bug?
    A: No. It happens because of our fuel gauge chip which doesn't require calibration goes crazy sometimes. It is not related with kernel or ROM. Just reset fuel gauge chip using STweaks app (or remove the battery and wait 3 minutes) and then charge your phone.

    Q: BLN doesn't work.
    A: you need to enable it in stweaks or BLN app. if you have more than one app to configure bln make sure all of them use the same settings.

    Q: BLN works in test mode but it doesn't work otherwise.
    A: if test mode works you should blame the apps. Stock messaging and email apps may not support BLN and in some other applications you may need to enable notifications. Either find another application or change your ROM.

    Q: Can I use breathing effect without using BLN?
    A: for now, breathing effect only works in BLN. There is no way of using it otherwise.

    Q: I need to disable and re-enable BLN in stweaks to get it working again. What is the problem?
    A: You may have another BLN related application (BLNapp, nstools, or a script) which disables BLN after stweaks apply the setting at early boot stage. you have to either uninstall that app or enable BLN in that app as well.

    150
    closing the thread once again...

    I don't want to piss the mods again because this thread attracts too many people.
    most of them misinterpret the "this is a development thread" statement and use the thread for their self-development purposes.

    There are very few people who give useful feedback and suggestions and I talk to them over gtalk, email or PMs anyway.

    greetings :)