yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] ffejy462:
Nuke it! (or toggled option in kernel adiutor)

mxpe 6.0
[X Style (Pure) Android Development] lucianogm:
Did someone try to install this kernel on a custom ROM? I just want to know if it's possible :)
[X Style (Pure) Android Development] Mejilan:
I'm on stock MM now, but I used to use it with TruPure ROM versions 2.4 and 2.5 before I reverted back to stock.

No issues at all.
[X Style (Pure) Android Development] pizzlewizzle:
i think by Custom ROM they mean CM Based... TruPure is based off stock
[X Style (Pure) Android Development] hbar98:
[MENTION=2400758]dirtyhank[/MENTION]

I'm not sure this is still a good TCP, but I've wondered if Remy could be added? It was an interesting thing a couple years ago, and it looks like it is still being updated.

MITs page on Remy: http://web.mit.edu/remy/

Remy GitHub: https://github.com/keithw/remy
[X Style (Pure) Android Development] YankInDaSouth:
Not I ... I vote nuke!
[X Style (Pure) Android Development] Cowbell_Guy:
Ditto!
[X Style (Pure) Android Development] Mejilan:
I don't use a folio case, but it'd be a shame to lose that as an option for those that do use one, or are considering using one.

As a former LG G4 owner, I can confirm that DT2W was always a bit finicky on that device.

At least for the first few months I used mine, until it inexplicably failed to power on and boot up one morning.
[X Style (Pure) Android Development] Cowbell_Guy:
Im considering installing the new TruePure Rom (with this Kernel built in!!). I'm assuming that is the most current version?
[X Style (Pure) Android Development] dirtyhank:
Yes, latest released version (0.6).
[X Style (Pure) Android Development] pradeepvizz:
Was wondering if your d2tw solution would hinder the camera/flashlight shortcut.. Just a thought...
[X Style (Pure) Android Development] dirtyhank:
Nope, chop and twist gestures work fine. The only thing not compatible with DT2W/S2W is Moto Display. If DT2W/S2W is enabled and you try to unlock the device while Moto Display is on bad things happen. I hope I'll be able to find a workaround but for the time being you can't have both enabled at the same time :(
[X Style (Pure) Android Development] dirtyhank:
I haven't been able to fix all DT2W SNAFUs but after all this is about testing new stuff and living on the edge so here we go:

v0.7 (2016-02-21)

Hotplug thresholds tuned to keep BIG cores offline more often

KEXEC Hardboot (MultiROM support)

Patched cdrom code (full DriveDroid support)

DoubleTap2Wake/Sweep2Wake/Sweep2Sleep (HIGHLY EXPERIMENTAL)

IMPORTANT NOTES ON DT2W/S2W (READ CAREFULLY)

Current implementation is far from stable, use at your own risk. If it works for you great, if it doesn't, disable it and wait patiently for future releases.

It is disabled by default, you can enable it with Kernel Adiutor (or any similar kernel control app). But wait, not yet, keep reading.

Right now

it is NOT compatible with Moto Display

. Disable Moto Display BEFORE enabling DT2W/S2W or bad things will happen. You've been warned.

When device goes into suspend mode DT2W will most likely miss first tap. So you'll probably have to tap three times (this is caused by Moto Sensor Hub, haven't been able to fix it yet).

Backlight might go into low power mode upon unlock. When this happens you'll have to reboot to fix it. This is an unlikely issue and I haven't been able to reproduce it consistently (just a couple of random occurrences), if you happen to face it I'd be very grateful if you could help me find a way to reproduce it.

While DT2W is quite finicky I've found S2W works pretty well. Just make sure you do a full left to right sweep (see this video).
[X Style (Pure) Android Development] Ghost9867:
i'm flashing it

Let you know if everythinks work or not :D

edit: double tap work but it's more like a triple tap to wake ahahaha

Swipe to wake work evry time for now
[X Style (Pure) Android Development] unitz0mbie:
works grea the 2t2w is working with 3 taps. but its working, and honestly an extra tap its so fast u wont even notice, its just about getting used to it. i have a question, i noticed in misc controls there is an option for power suspend mode, what is it? and what is the best option
[X Style (Pure) Android Development] dirtyhank:
Powersuspend is a driver used by DT2W to be aware of screen on/off events. Better leave it in default mode (hybrid).
[X Style (Pure) Android Development] unitz0mbie:
does it cause battery drain?
[X Style (Pure) Android Development] dirtyhank:
Haven't noticed increased battery drain during testing. In fact, I lose 2-3% overnight with DT2W enabled, and that's total, I don't think DT2W alone accounts for more than 1%. That's pretty good for a screen this size IMHO.

But I'm interested in how it works for you guys, battery-wise.
[X Style (Pure) Android Development] Prazaar:
My wifi is dead on 0.7

Gesendet von meinem XT1572 mit Tapatalk
[X Style (Pure) Android Development] sir-harlekin:
Can this be tested on any cm13 based rom?
[X Style (Pure) Android Development] dirtyhank:
Nope, this is for stock-based ROMs.
[X Style (Pure) Android Development] sir-harlekin:
This is indeed a pity because there seems to be no development for cm13 kernels. Choosing between cm13 roms and DT2W....is hard.
[X Style (Pure) Android Development] dirtyhank:
Make sure root is working
[X Style (Pure) Android Development] kadopt:
Working fine, after a while (probably deep sleep) it needs three taps but it's ok because the power button appreciates anyway! Thanks!
[X Style (Pure) Android Development] Hashbang173:
I could easily compile this kernel for AICP and/or CM13 with the stock toolchain if you want. I can also compile it with a custom toolchain with more effort.
[X Style (Pure) Android Development] sir-harlekin:
Well for sure i wont hold you back...this would be awesome. I thank you in advance for many other people as well i guess :)

If custom toolchain is an option i would vote for it.
[X Style (Pure) Android Development] suhridkhan:
DT2W working great. Coming from LG G4 I am used to 3/4 taps to wake. And since S2W works with 100% accuracy, I am using that more often.

This would be a big big plus for the people who love aosp roms. I hope the developer doesn't mind letting us use his codes. Or, the developer himself can extend his work on the AOSP sides.
[X Style (Pure) Android Development] ffonegod:
Both DT2W and S2w works perfectly.. Actually I don't have to do 3 taps.. Just 2 and it's incredibly fast as well.. BTW I disable moto display as u said.. Great work [MENTION=2400758]dirtyhank[/MENTION]
[X Style (Pure) Android Development] dirtyhank:
Besides the toolchain what other changes are needed to make it work on CM13?
[X Style (Pure) Android Development] tiis:
Yes, please compile it for AICP! :)
[X Style (Pure) Android Development] Hashbang173:
I think some changes will need to be made to the defconfig. For cm based ROMs, the wlan driver is built into the kernel. BFQ is also used. There might be more changes but those are off the top of my head.
[X Style (Pure) Android Development] YankInDaSouth:
LOVE having DT2W again! Great job [MENTION=2400758]dirtyhank[/MENTION]!
[X Style (Pure) Android Development] dirtyhank:
Thanks. I'm afraid I don't have the time to install CM13 and do all the testing but if someone can help out and give it go I'll incorporate the changes in future releases :)
[X Style (Pure) Android Development] sir-harlekin:
This would be awesome!!

Maybe is Hashbang releases a test version you can implement the necessary changes.
[X Style (Pure) Android Development] guraki:
How do we disable moto display?
[X Style (Pure) Android Development] YankInDaSouth:
I used Titanium Backup ... Searched for "moto", scrolled until I found moto display and froze it.
[X Style (Pure) Android Development] jason2678:
Anyone know if this is necessary, or if just turning moto display off in the moto app is sufficient?
[X Style (Pure) Android Development] YankInDaSouth:
Not sure ... But I'm having no issue with DT2W/S2W or Ambient Display. All working great!
[X Style (Pure) Android Development] ffejy462:
I apologize, but I keep reading your handle/screen name wrong. My eyes keep putting the first two words together. Totally changes the meaning. Lol☺

There are a few ways:

Titanium backup

Settings, apps, moto display, disable (if grayed out, use other method)

Using a root enabled file explorer, navigate to /system/app or /system/priv-app folder and change extension from apk to bak. Reboot

Or if you're on TrupureXMM, reflash rom, choose ambient display rather than moto in aroma.

Edit: turn off in moto display app

mxpe 6.0
[X Style (Pure) Android Development] YankInDaSouth:
LOL! Yeah, I realized that afterwards ... Kinda like it though, gives ya something to think about ?
[X Style (Pure) Android Development] dirtyhank:
Open the Moto app, click the star in the top right corner, select Display and set to Off.

That works for me.
[X Style (Pure) Android Development] ffejy462:
Lol sometimes the easiest way is overlooked.

mxpe 6.0
[X Style (Pure) Android Development] Ghost9867:
This would be awesome

Please do it i love aicp but it have some lag sometime and i think that with this kernel the ROM will be awesome
[X Style (Pure) Android Development] Hashbang173:
So I'm trying an inline build with the defconfig changes I mentioned. Right now I'm stuck at: ERROR: modpost: Found 1 section mismatch(es).
[X Style (Pure) Android Development] Ghost9867:
I hope that you will fix this error
[X Style (Pure) Android Development] dottat:
Flashed this kernel solely for dt2wake and it's working well enough for me with zero issues or side effects. So damned nice to have this feature again.

Edit. [MENTION=2400758]dirtyhank[/MENTION] Lol. I waited hours to post this and the next time I woke the phone (using power button no doubt) I'm stuck with a dimmer than normal phone. I can manually adjust to bright but it's as if autobrightness measurements from the ambient light sensor aren't being applied. I noticed on previous wakeups it seemed to step up brightness depending on ambient light so when this happened I disabled to adaptive brightness under display settings and boom....back to normal levels.

Hope this helps your insanity man and thanks again for even making this possible.

Upon further testing I used a very bright flashlight with adaptive display enabled (still in the funky state) and found it had no problem making the screen bright as crap. Take the light away and it slides back down to dim.

I'm going to leave it in this state with adaptive display off in case you want anything from it.
[X Style (Pure) Android Development] Hashbang173:
So I got around to fixing the error. I replaced the zImage in the frankenclark zip with the one I compiled, haven't got a chance to test it yet. If this doesn't work, I guess I'll have to look into replacing the modules as well.

If you want to test, flash the zip over the stock AICP or CM kernel

https://www.androidfilehost.com/?fid=24421527759884755
[X Style (Pure) Android Development] humor2008:
I use multi rom and the AICP rom as main rom , if the rom have kexec patched is "stock" ? I flash this patch and reboot then stuck on the first screen.
[X Style (Pure) Android Development] jason2678:
moto display on 0.7

[MENTION=2400758]dirtyhank[/MENTION] - Thanks so much for picking up the kexec hardboot commits. I've got stock as a primary rom running alongside aicp now. Very nice.

Quick question. I've kept up with the recent posts about disabling sensors and I read the disclaimer about d2tw not playing nice with moto display. I've been careful not to enable both at the same time. Since switching to Frankenclark 0.7 I get "AOD not supported on this device" when I try to turn on moto display, and it doesn't seem to work at all. Just wanted to check if this is exptected; I didn't get that impression from the discussion on disabling sensors.

I'm running stock MM (not TruPure). Logs attached in case its helpful.
[X Style (Pure) Android Development] sir-harlekin:
Stuck at Moto boot logo without the phone even vibrating.
[X Style (Pure) Android Development] newHere:):
Awesome!

Can't wait for DT2W to work with Moto Display! :D

[MENTION=2400758]dirtyhank[/MENTION]

Is it possible to integrate hidden LED control to kernel? :)

Something like BLN on the Galaxy S2 (But with hidden LED of course) :

http://xdaforums.com/showthread.php?t=823922

I know that there are some software solutions, but it is not as good as kernel support :)

Thank you!
[X Style (Pure) Android Development] pradeepvizz:
LED Control is already there in the kernel, you need to choose your options in Kernel Auditor.
[X Style (Pure) Android Development] newHere:):
Great to know! :)

Thank you! :D

It is not written on the "Features" section of the kernel so i missed it

Maybe it will be a good idea to add it :p
[X Style (Pure) Android Development] dirtyhank:
Did you have Moto Display and DT2W enabled at the same time even if it was for a brief moment? In any case, make sure Moto Display is disabled and reboot, sometimes if I don't boot with Moto Display already disabled weird things happen when I enable DT2W.
[X Style (Pure) Android Development] dirtyhank:
No, it's not expected. I don't get that message when I try to enable Moto Display, I'm also on stock. Weird. If you go back to v0.6 are you getting the same message?

Regarding sensors, I disabled notifications from Hall Efect sensor, but that should affect magnetic folio cases only.
[X Style (Pure) Android Development] dottat:
Moto display was the first thing I disabled when I got this phone. Never re-enabled it. The ir sensors were too sensitive and bled into the room disrupting normal ir signals.
[X Style (Pure) Android Development] dirtyhank:
Moto Display won't use the IR sensors unless you enable the "Approach for Moto Display". Please, make sure Moto Display itself is totally disabled, not just the "Approach" feature.
[X Style (Pure) Android Development] koheen:
Tired flashing 0.7 on TruPureX 2.6 and couldn't boot past boot animation
[X Style (Pure) Android Development] kadopt:
[MENTION=2400758]dirtyhank[/MENTION]

The dimmed screen happens in my device only with s2w, dt2w is ok.
[X Style (Pure) Android Development] dirtyhank:
Did you have both enabled or just S2W?
[X Style (Pure) Android Development] kadopt:
Just s2w.
[X Style (Pure) Android Development] dottat:
OK..lol to make it crystal clear. I disabled both features out of the box.
[X Style (Pure) Android Development] dirtyhank:
Ok, thanks.

This bug is a tough one to spot. I think it's some sort of race condition because it works fine most of the time but I still haven't been able to find out the sequence of events that trigger it.
[X Style (Pure) Android Development] Sheetzie03:
You are def doing something Wrong then bud.
[X Style (Pure) Android Development] noorul89:
Just installed 0.7 and TruPureXMM 2.6.2, Double tap is working for me :)
[X Style (Pure) Android Development] sbcrumb:
Same here.
[X Style (Pure) Android Development] koheen:
Really don't know what I did. I just flashed the kernel zip and it wouldn't boot
[X Style (Pure) Android Development] jason2678:
Pretty sure I have this pinned down to Multirom.

I deleted my secondary roms, flashed normal TWRP, then used it to flash back to Frankenclark 0.6. However, I forgot to flash the Multirom uninstaller. On next boot I still got the Multirom dual boot screen. My stock rom booted up normally, but moto display was still giving the AOD not supported toast message when I enabled it. After that I booted back to recovery, flashed the Multirom uninstaller, and then reflashed Frankenclark 0.6 again for good measure. With all the Multirom stuff properly removed moto display is working just fine again.

I made too many changes all at once without testing. I was excited to try out Multirom. Sorry I jumped right to blaming the kernel. Thanks for all the hard work and support.
[X Style (Pure) Android Development] dottat:
Had it occur once more today. Screen had been on and opened to google messenger. It went to sleep and I double tapped to wake and got the dim screen.
[X Style (Pure) Android Development] mrbracht:
Which led trigger is used for notifications? Or does that not exist in this kernel yet? Other than that everything is working amazing. Love this kernel
[X Style (Pure) Android Development] rehpyc:
Really enjoying this kernel along with TruePure ROM. Can't complain with being able to get 4+ SoT and 2 full days w/o a charge.
[X Style (Pure) Android Development] Kir6y:
Can anyone share there CPU kernel settings. I'm on Stock 6.0 with Kernel Adiutor. I have settings already in but would like to know what other people have (:.
[X Style (Pure) Android Development] krohme:
On the first page you'll find settings for preserving battery and for pure performance.

Personally I've kept mine close to stock settings, occasionally I use bluactive governor when I want extra power :D but I don't keep that governor active permanently, for me it drains more then interactive.
[X Style (Pure) Android Development] noorul89:
Battery endurance and smoothness using Frankenclark :

1.) Both governors to Bluactive

2.) Underclock bigs to 1536MHz, leave LITTLEs stock, Touchboost on, Temperature Throttle on

3.) Underclock GPU to 300MHz

4.) I/O is noop w/ 1024MB read-ahead both internal & SD card

5.) Entropy is read 2048 write 4096

6.) TCP Congestion on Hybla or Westwood (I like these personally but it's your choice)

7.) Fsync on

CPU Boost Interval - 0ms

Sync Threshold - Disabled

Input Interval - 300ms

Input Boost Frequency Core 1 - Disabled

Input Boost Frequency Core 2 - Disabled

Input Boost Frequency Core 3 - Disabled

Input Boost Frequency Core 4 - Disabled

Input Boost Frequency Core 5 - 1536MHz

Input Boost Frequency Core 6 - Disabled

Touch Boost - On
[X Style (Pure) Android Development] dirtyhank:
I'd really appreciate if those of you who are experiencing the "dimmed backlight on wake" bug could install this debug version of v0.7:

https://www.androidfilehost.com/?w=files&flid=50645

No changes from official v0.7, just more verbose debug messages. Whenever you hit the bug, please dump the dmesg ring buffer to a file and send it to me.

Thank you!
[X Style (Pure) Android Development] countryfolk07:
[MENTION=2400758]dirtyhank[/MENTION], why would a script run as root not be able to apply a touchboost_enable file on this kernel? Trying to run a profile as script and it fails.

See attached image. There is one more dealing with boost also.
[X Style (Pure) Android Development] dirtyhank:
Because that's not the right file. To control the touchboost freq you need to modify /sys/module/cpu_boost/parameters/input_boost_freq

For instance, if you want to enable touchboost of 1248MHz for core 0 only you would issue a command like this:

echo "0:1248000 1:0 2:0 3:0 4:0 5:0" > /sys/module/cpu_boost/parameters/input_boost_freq
[X Style (Pure) Android Development] countryfolk07:
It looks like that's already in the script. Would you have a couple minutes to look at it?

Just remove .txt, if you have time. Thank you.
[X Style (Pure) Android Development] dirtyhank:
Yep, it's already in the script:

echo 0:672000 1:672000 2:672000 3:672000 4:0 5:0 > /sys/module/cpu_boost/parameters/input_boost_freq

You can ignore the errors, or simply remove those lines if it bothers you.
[X Style (Pure) Android Development] dottat:
You just looking for the dmesg log in text format or something more specific? I have the debug kernel flashed and right now have my phone sitting in the bugged state (dimmed).
[X Style (Pure) Android Development] dirtyhank:
Plain text format is ok. Thank you.
[X Style (Pure) Android Development] dottat:
Emailed it to your gmail.
[X Style (Pure) Android Development] Kir6y:
Looks interesting. Where is the Touch Boost setting located?
[X Style (Pure) Android Development] noorul89:
In ex kernel manager I found it under cpu boost options
[X Style (Pure) Android Development] dirtyhank:
Going through the dmesg logs it's pretty obvious the Moto Sensor Hub is somewhat involved in the dimmed screen bug. I've uploaded a second debug version with a proof of concept. Basically this version disables Moto Sensor Hub when screen is off. If this works we'll be on the right track to fix it.

If you experience the bug and feel like testing flash it and please, report your experience. Keep in mind this will disable most sensors when screen is off, so don't flash it if you rely on those sensors for important stuff.

Thank you for your help!

EDIT: Nevermind, doesn't work, I've just hit it again, too bad.
[X Style (Pure) Android Development] Degod:
I like to try this setup... How many SOT did you get?
[X Style (Pure) Android Development] noorul89:
I get to use me phone for over two days which is way better than stock! I been using it my phone a lot during the day.. Hope this helps
[X Style (Pure) Android Development] Kir6y:
I'm using Kernel Adiutor but Im willing to buy Ex Kernel. My problem is that the settings don't stick half the time on Adiutor. Is this a kernel issue or is Ex working good for you?
[X Style (Pure) Android Development] Tech_Savvy:
It also disabled the promixity sensore while in call the screen wont turn on...
[X Style (Pure) Android Development] Hitti2:
Working great on my end. Thanks.

What is the Android cdrom thing?

Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
[X Style (Pure) Android Development] ffejy462:
Ran into some touchscreen issues today. I'd lightly tap screen and it'd register as a long press. In some apps if I tapped action bar at the top of the screen it wouldn't register at all. Dt2w stopped working altoghter on top half of the screen (full screen is selected) and even then it took several tries (was working perfectly previously) for it to work on bottom half. Reboot cleared it up, but I disabled dt2w anyway. Using original 0.7. If you'd like I can enable, and try to capture some logs if it does it again.

mxpe 6.0
[X Style (Pure) Android Development] SpasilliumNexus:
Yesterday I had a crazy 10+ hour wakelock with Play Services. Turns out it was the SystemUpdateService thing. Used Tasker to stop it and now I'm getting sweet screen on time with the battery saving settings in OP.
[X Style (Pure) Android Development] unitz0mbie:
how much more battery does the performance profile drain vs the battery one? and what profile do u guys recommend for profiles or settings, i mostly listen to music and watch videos on phone and text a lot, so i just want a fluid UI
[X Style (Pure) Android Development] Sheetzie03:
I been saying that settings don't stick in kernel auditor for weeks but almost everyone else said they didn't have the problem.. I def have this problem tho. I noticed it got updated but it didnt mention in the changelog that was fixed
[X Style (Pure) Android Development] timde9:
I dunno what's going on but I cannot set big cores above 1632mhz if I do they just get reset back down to 1632mhz anyone else run into this issue and how did you solve it if so? I'm on latest version of 0.7
[X Style (Pure) Android Development] noorul89:
I have noticed with every update to FrankenClark Kernel that some of the settings don't stick, however I have read on one of the forums that Ex Kernel is better than Kernel Auditor and my battery life has improved as I did have Kernel Auditor before. Hope this helps.
[X Style (Pure) Android Development] dirtyhank:
Basically full cdrom emulation support for DriveDroid.
[X Style (Pure) Android Development] Hitti2:
Wow. This is crazy. Emulator for Android! With support. Amazing.

Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
[X Style (Pure) Android Development] dirtyhank:
Those profiles are at opposite sides of the spectrum so there should be quite a difference. For your usage pattern I'd start with the battery profile, if you don't find it smooth enough use the GPU settings of the performance profile. If still not smooth enough tune other parameters like the performance profile. You get the drill.
[X Style (Pure) Android Development] Sheetzie03:
Exactly! As I'm trying to adjust max cpu, it automatically jumps back to 1248 no matter what I try to set it too. Other times settings don't stick. And it was just updated too. I guess Im going back to ex

Yep, def something with kernel Auditor.