I just flashed Oxygen 2.3.2 (with Oxygen stock kernel) and it has a handy device sub menu where you have some control over back light notification (back light timeout and blinking)
BLN mod is not installed according to the BLN control app, and NStools shows the same. I'd assume this means the mod is not implemented into the kernel.
NSTools does however have a sub menu entitled 'CMLed' which I can acsess (with back light timeout and blinking options, same as in the Oxygen devices menu). And this is what I'm wondering...
Whats the difference between CMLed and BLN? Are they separate implementations of the same idea?
Sorry for the long winded post, hopefully someone can clear this up for me.
caffeinegum said:
I just flashed Oxygen 2.3.2 (with Oxygen stock kernel) and it has a handy device sub menu where you have some control over back light notification (back light timeout and blinking)
BLN mod is not installed according to the BLN control app, and NStools shows the same. I'd assume this means the mod is not implemented into the kernel.
NSTools does however have a sub menu entitled 'CMLed' which I can acsess (with back light timeout and blinking options, same as in the Oxygen devices menu). And this is what I'm wondering...
Whats the difference between CMLed and BLN? Are they separate implementations of the same idea?
Sorry for the long winded post, hopefully someone can clear this up for me.
Click to expand...
Click to collapse
I have been wondering the same thing.
BLN is the original backlight notification, made by Neldar.
CMLed was made by Cyanogenmod team not too long ago.
They're pretty much the same in terms of usage though.
So we can customize the blinking and everything with cmled? I'll have to give it a try..
Sent from my Nexus S using Tapatalk
I wrote down 2 pages and hit post but xda logged me out and now I'm really, let's say it, mad
Hello everyone.
Shorter version:
CM7
Pros:
1. Amazing battery life.
2. More options and settings (after all it is cm).
3. Nicer user interface.
4. Flash player 11 for arm6 is working perfectly.
5. No bloatware.
6. Fast enough and stable (not one fc so far).
Cons:
1. Front cam. Although back one is working fine it would be nice to have a front one as well. Minor issue though, I don't use it anyway.
2. Fm Radio is always turning my bluetooth on when I start it and use it. Don't know if it is supposed to do that but it is a real battery drain and I don't want to use 3rd party apps if that is even possible. This is a minor issue since I don't use it often.
3. Led notification turns green at 90% and more when charging and my phone tricked me to unplug quite a few times Also a minor issue.
4. Default automatic brightness is just terrible. I know that they can be modified through cm settings>display>automatic backlight but I am not sure what values to enter to get the best and optimum results. I just cannot get them quite right.
So, to conclude. Cm7 is just great and really ready for daily use. I only need to set up the automatic backlight properly and this is where I need your help. If anyone knows the best values for these settings, please, write them down in this or the original cm7 thread.
Best wishes
I've set the status bar notification for backlight to 25/50/75/100. I feel that these values suit every possible condition.
Alex C. said:
I've set the status bar notification for backlight to 25/50/75/100. I feel that these values suit every possible condition.
Click to expand...
Click to collapse
Hi Alex, you must have misunderstood me. I'm not talking about those settings. I don't want to adjust brightness manually. I'm talking about window length, reset threshold, sample interval and custom light sensor levels so my phone can automatically adjust brightness. These can be found in cyanogen settings>display>automatic backlight
Regards
Ah, ok then.. Unfortunately I did not have the patience required to set/tweak them.
Is there a way to increase vibration intensity on the moto g? Ever since i updated to 4.4.4 i barely feel the phone vibrating in my pocket.
Is there a xposed module/app/kernel that allows for this change?
thanks in advance
Yeah indeed, had the same once.
Flash aero kernel or one of your preference such as faux's, experience or something and set your vibration levels on the controller app - aero kernel, trickster, performance control, fauxclock, whichever.
hey thanks, i'm currently on xperience kernel using faux123 kernel controller. I can't find the vibration option though
alkspo said:
hey thanks, i'm currently on xperience kernel using faux123 kernel controller. I can't find the vibration option though
Click to expand...
Click to collapse
It should be there somewhere; vibration strength or something. I know aero kernel and aero control has it.
i just asked the kernel dev and apparently this feature isn't available on stock moto roms, as a file that is modifed for vibration intensity isnt ezxistant
Sent from my XT1032 using XDA Free mobile app
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
Features
You get all those well known features of a custom kernel, like usual sets of IOScheds and governors, tweaks optimizations. However I will be only mentioning the key ones:
Wake Gestures - Double Tap, Sweep Up, Down, Left, Right, Diagonals, Draw 'L' and 'V'
Music Mode - Control Music without even unlocking the device.
Pocket Mode - Turns off wake gestures when it detects it in pocket to save battery
ZD Charger Control - Full control over USB charging currents.
ThunderSonic Engine - An unique, customizable sound control driver written by @varun.chitre15 for MSM8930 boards.
Dynamic Fsync 1.6 - This feature does not need any introduction, however it is now more optimized to run when screen is off, while halt when screen is on.
Overclock to 1.5Ghz, Underclock to 188Mhz
Permissive SELinux in kernel.
Uses live Ramdisk patching during flashing, so need not worry about ROMs on which you are flashing on.
Compatibility
Android 4.4 based ROMs - Theoretically yes, testers needed for confirmation.
Android 5.x based ROMs - Theoretically yes, testers needed for confirmation.
Android 6.0 based ROMs - Yes and confirmed by me working on CM13.
Installation Instructions
Download and put zip in phone.
Go to recovery and flash it. No need of wiping anything. And the zip will flash appropriate files depending on your system.
Reboot & Enjoy.
Notes
Toolchain used - GCC 4.8 by Google for stability.
Source - https://github.com/TeamButter/zd_taoshan
Downloads - Here
Recommended App
Presenting my very own app to control wake gestures. Find it here - ZD Kernel Control
F.A.Q
For which phone will it work? Sony Xperia L with above ROMs.
Do I need to have Unlocked BootLoader? Yes
Credits
thewisenerd - For bringing up new DT2W for XL, and many other stuff.
varun.chitre15 - For bringing LP to XL, CAF Kernel for LP, ThunderZap Kernel, ThunderZap Control App and many more.
showp1984 - For original DT2W driver.
Video Walkthrough
Hey great work, I thought varun chitre was going to surprise us but you beat him to it. Anyways I think its a really good start. Good job and thanks to anyone else who was involved in the development of this.
adil089 said:
Hey great work, I thought varun chitre was going to surprise us but you beat him to it. Anyways I think its a really good start. Good job and thanks to anyone else who was involved in the development of this.
Click to expand...
Click to collapse
I do not intend to compete with anyone. Just we 2 (me and twn) are on our own. I am a fan of this thing, so I thought of adding the same (with twn's full support of course).
Download link updated
Download link updated. Kernel now available as fully flashable zip.
Do let me how good/bad dt2w works.
so this is varuns caf kernel +dt2w ? any other changes or just that?
really important to me:
does this dt2w function make the phone avoid deep sleep mode?
Lemme quickly answer that last question: no.
How this works? irq_wake.
How does your phone switch on when your phone is in deep sleep and you press the power button? It's because though there is deep sleep, there's still power being routed to those buttons since you want to get those 'interrupt's (viz: key presses).
Similarly, that's what we do with the touch panel: in your device's case, cyttsp3. We don't allow the touch panel to 'sleep', viz. Power is always routed to the touch panel. So, battery drains because the touch panel is always turned on, and not because the phone doesn't go to deep sleep.
P.S. if your touch panel has a 'low power mode' of sorts, that could be used to slightly lower power consumption, thus 'slightly' reducing battery consumption.
thewisenerd said:
Lemme quickly answer that last question: no.
How this works? irq_wake.
How does your phone switch on when your phone is in deep sleep and you press the power button? It's because though there is deep sleep, there's still power being routed to those buttons since you want to get those 'interrupt's (viz: key presses).
Similarly, that's what we do with the touch panel: in your device's case, cyttsp3. We don't allow the touch panel to 'sleep', viz. Power is always routed to the touch panel. So, battery drains because the touch panel is always turned on, and not because the phone doesn't go to deep sleep.
P.S. if your touch panel has a 'low power mode' of sorts, that could be used to slightly lower power consumption, thus 'slightly' reducing battery consumption.
Click to expand...
Click to collapse
really love this detailed answer
Sent from my C2105 using XDA Free mobile app
@corphish awesome work !!
@thewisenerd @corphish
It works even if you tap it once(Which shouldn't happen AFAIK and it accidently unlocks too :/). It is functional though I can provide you logs if you need to find the issue.
Navneet Suresh said:
@thewisenerd @corphish
It works even if you tap it once(Which shouldn't happen AFAIK and it accidently unlocks too :/). It is functional though I can provide you logs if you need to find the issue.
Click to expand...
Click to collapse
Its a known thing. We both know about it and its mentioned in the bugs.
We are still trying to resolve this.
And thanks for offering help
corphish said:
Its a known thing. We both know about it and its mentioned in the bugs.
We are still trying to resolve this.
And thanks for offering help
Click to expand...
Click to collapse
Sorry my bad :/ I didn't bat an eye on the bug list :/
corphish said:
This kernel will only work on CyanogenMod 12.1, and not on CyanogenMod 12.0.
Click to expand...
Click to collapse
This may be a stupid question but will this work on any 5.1 rom or only cm12.1?
primemonitor said:
[/LIST]
This may be a stupid question but will this work on any 5.1 rom or only cm12.1?
Click to expand...
Click to collapse
Should work on any ROM based on Android 5.1.
Best Kernel
The kernel just works. Did not find any issues with battery drain till now.
Thanks @corphish for this awesome stuff. Making me feel like using 1+1
Phone didn't go into deep sleep for me after flashing the kernel. I've attached screenshots showing the same. Problem persisted even after turning off dt2w. Tried clearing cache too, didn't work.
Tap2wake worked exactly as expected, even with single tap, as you already said.
primemonitor said:
Phone didn't go into deep sleep for me after flashing the kernel. I've attached screenshots showing the same. Problem persisted even after turning off dt2w. Tried clearing cache too, didn't work.
Tap2wake worked exactly as expected, even with single tap, as you already said.
Click to expand...
Click to collapse
Yes I can confirm that it doesn't go to deepsleep. @corphish need some logs to find out what is causing it ??
primemonitor said:
Phone didn't go into deep sleep for me after flashing the kernel. I've attached screenshots showing the same. Problem persisted even after turning off dt2w. Tried clearing cache too, didn't work.
Tap2wake worked exactly as expected, even with single tap, as you already said.
Click to expand...
Click to collapse
Navneet Suresh said:
Yes I can confirm that it doesn't go to deepsleep. @corphish need some logs to find out what is causing it ??
Click to expand...
Click to collapse
It won't get into deep sleep state. Perks of the wake gesture (not only for us but for any phone). So as a side-effect, battery performance is reduced.
corphish said:
It won't get into deep sleep state. Perks of the wake gesture (not only for us but for any phone). So as a side-effect, battery performance is reduced.
Click to expand...
Click to collapse
not necessarily.
the device should go into deep sleep regardless since the two (touch panel staying awake && device going to sleep) aren't correlated.
something is wrong, i guess. wrt. irq handling.
@thewisenerd so according to you the phone should enter deepsleep mode ?? It contradicts to what @corphish said just above your post ?? You can PM me with test builds I would love to help you with testing (if needed)
Update 1.2
Here comes update 1.2
Changelog
SingleTap2Wake should be reduced, though, is not fully eliminated.
Changed LED colurs while booting to distinguish kernel. Light Blue for normal boot, light green in recovery.
Download Link updated in OP.
About Recover Key Combo issue - I have realised why recovery key combo is broken, but cannot do much about it. In short, the situation be like, DoubleTap2Wake or Recovery Key Combo.
Also this is the last release for Android 5.1, before Varun outs another beta. Reason : Frequent BSoDs.
Hi guys, how i can change the vibration intensity on my op6 (rooted)? In the settings is set to High but for me is too low
Best regards
you cannot change vibration intensity, even custom kernel cannot completely disable this nonsense !!
I am highly upset with this retarded Oneplus policy !!
Very soft vibration even on "high". I wish it could be modified. So no kernel will help this? Can OP do anything about it in an OTA? Seems crazy that this is something so small, yet so important, and OP overlooked it.
Clean slate kernel has some options