yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Note 3 Chicago:
Just a great kernel. Great smoothness, great performance, great battery life. Donated. Thanks for working so hard on this [MENTION=2400758]dirtyhank[/MENTION]!
[X Style (Pure) Android Development] jsmith8858:
Can you give details where/how this is enabled? I've searched in the app for like 20 minutes, opening every setting I could find, and did not see anything about LED Control in Kernel Auditor. (Using kernel v0.7)
[X Style (Pure) Android Development] suhridkhan:
You are right. I did the same and could not find it. I don't think Kernel Adiutor has this settings. Someone in another thread mentioned that EX Kernel Manager has this option, but you need to buy that. I am willing to purchase, if someone can confirm that it indeed has this setting.
[X Style (Pure) Android Development] Kir6y:
Yes, there is a option for LED.
[X Style (Pure) Android Development] dirtyhank:
You can change the LED trigger from EXKM but keep in mind functionality is pretty limited. You can make things like blink LED when charging or when battery is charged but not much else. If you want to use it for notifications I don't think it'll work out of the box.
[X Style (Pure) Android Development] suhridkhan:
Thanks for your responses. I am going to try AOSP roms for the next few days. Although the battery is not as good as stock but I can use the led for notification.
[X Style (Pure) Android Development] danny39:
Anybody else having EX Kernel Manager display like this?

It just has NA for some options and won't let me edit them.
[X Style (Pure) Android Development] countryfolk07:
It's because the cores aren't active. They are plugged off. If you want to change parameters, frequencies, etc. just change the governor to performance, make the changes, then back to interactive or whatever you had it at.
[X Style (Pure) Android Development] zohar_ml:
I'm trying to install the kernel but keep getting:

zip signature verification failed.

Download 0.7 3 times now. tested the md5. using twrp 3.0.0.1 on XT1575

What did I do wrong?

Zohar
[X Style (Pure) Android Development] kadopt:
Check file size. Downloaded file may be incomplete or corrupt.
[X Style (Pure) Android Development] ffejy462:
I had to turn of chrome data saver so files would download properly. It'd stop at 45k or so every time.

mxpe 6.0
[X Style (Pure) Android Development] zohar_ml:
Ive download in my pc on the last try and tested the md5, so for 100% i have the correct data in the zip file
[X Style (Pure) Android Development] Kir6y:
I can use my Notification Light on my Moto X Pure through Root and Paid Version of Light Flow. Moto Display and IPS is a headache

---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------

What AOSP are you thinking about using. I tried TruPureXMM but I had Wifi issues.
[X Style (Pure) Android Development] Ghost9867:
i only set the scheduler to noop and the governor was already set on interactive and i don't made the underclock
[X Style (Pure) Android Development] Grafidio:
If I am on trupure 2.4 which img do I download and flash? I'm on EU version

(Basically just a bit confused why there's a trupure folder)
[X Style (Pure) Android Development] dirtyhank:
The trupure folder is a test version for trupure. It appears to work, give it a go a let us know ;)
[X Style (Pure) Android Development] patt2k:
Yes it works.
[X Style (Pure) Android Development] krohme:
Trupure version working well on stock rom, will test this for few days & see how it goes.

I wasn't satisfied with battery life on stock kernel, lollipop & kitkat were definitely better imho.

Looking forward to updates - especially any more governors to play about with, thanks for the kernel :beer:
[X Style (Pure) Android Development] Grafidio:
Right before flashing the img it says partition to flash, boot or recovery?
[X Style (Pure) Android Development] tombepa:
Truepure working here. On 2.4. Phone seems to be running cooler. Nice!
[X Style (Pure) Android Development] lafester:
So are you flashing a boot img or recovery img?
[X Style (Pure) Android Development] Grafidio:
I picked boot lol, it seems to have worked :)
[X Style (Pure) Android Development] patt2k:
yep for future just re read it to yourself :D you ain't flashing recovery ;) you are flashing kernel so it will be boot :D:good:
[X Style (Pure) Android Development] WelcomeToTheSkye:
Seems to be working great on TruPureXMM 2.4 I seem to be nothing a slightly shorter boot time as well seems to be working better then Vadim's kernal
[X Style (Pure) Android Development] guraki:
Did you change any settings?
[X Style (Pure) Android Development] Schrotty35:
Is the img in the trupure folder for XT1572 too?
[X Style (Pure) Android Development] Ghost9867:
yes i flashed it on 72 and it's work
[X Style (Pure) Android Development] dirtyhank:
Yep, TP uses same kernel for both devices so that boot.img should work on either one.
[X Style (Pure) Android Development] Shishir Singhal:
Wifi doesn't work after flashing this kernel xt1572 dual sim variant stock rom. Any solutions??
[X Style (Pure) Android Development] Ghost9867:
wow guys this kernel is awesome i made a full day and i have 56% of battery life

i have only 2h of SOT but it's some 3g and some wifi and this is the best battery life that i ever had in this phone

Thanks you soo much for this kernel i have ambient display enambled
[X Style (Pure) Android Development] dirtyhank:
If you can provide stock boot.img I might be able to do something
[X Style (Pure) Android Development] dirtyhank:
Ok guys, testing time. Before I push it to the OP I need your opinions on v0.2. Changes are:

Update to linux kernel v3.10.94 (thanks to Nimrodsv)

Underclocking (down to 302MHz)

https://www.mediafire.com/folder/7wddfrxcbc9md/v0.2

If you're systemless rooted keep in mind you'll need to flash the ZIP again. For those testing on TruPure use the XT1575 image.
[X Style (Pure) Android Development] Ghost9867:
sorry i can't try it

i'm testing the first version right know
[X Style (Pure) Android Development] suhridkhan:
I am using bliss rom since yesterday. Very fast and quite stable. No issues except poor battery life.
[X Style (Pure) Android Development] pradeepvizz:
Sorry about that, didn't notice which app had the option
[X Style (Pure) Android Development] zohar_ml:
Also no luck with 0.6
[X Style (Pure) Android Development] danny39:
Here's the zip I flashed of the kernel and it worked fine

https://www.dropbox.com/s/20tll4pjg1vclf0/frankenclark-0.7.zip?dl=0

---------- Post added at 06:26 PM ---------- Previous post was at 06:18 PM ----------

I think there's a setting in TWRP to turn off zip signature verification, give that a shot
[X Style (Pure) Android Development] ffejy462:
Fyi. You can screenshot in recovery.

for example

mxpe 6.0
[X Style (Pure) Android Development] zohar_ml:
Thanks!

Yes, it has that option in settings.

Set it to off and installed.

Now I even have swipe to off!!
[X Style (Pure) Android Development] Grafidio:
Sweep2wake is working pretty well, any way of setting a small vibration for when it works, like haptic feedback?
[X Style (Pure) Android Development] Sheetzie03:
You want it to vibrate to show you woke up the device with s2w, not sure why you would want this.

I would say no but I could be wrong.
[X Style (Pure) Android Development] Grafidio:
Yeah it's just satisfying :)
[X Style (Pure) Android Development] dirtyhank:
I've been busting my a** all week trying to fix the infamous "dimmed screen" bug and unfortunately I haven't been able to fix it for good (see technical explanation below). The good news is I've found a way to mitigate the symptoms, so the screen shouldn't get stuck in a dimmed state anymore. Before I push it the OP I'd like some feedback, if you happened to hit the bug please flash this updated version and let me know how it works for you:

https://www.androidfilehost.com/?fid=24421527759889877

For the technical inclined let me go into more detail about the bug: Moto Sensor Hub uses the I2C bus to exchange data from all sensors with the system, and so they do many other devices, among which are the touchscreen and the backlight controller. It turns out that under very heavy bus traffic situations (exactly the kind that happens when you try to wake the device and the touchscreen, Moto Sensor Hub and the backlight controller are talking) some bogus messages enter the bus, and one of this messages gets the backlight controller into a weird low power mode. I honestly don't know the source of these bogus messages yet but at least I think I've managed to instruct the backlight controller to make sure it's in a normal mode before turning the backlight on. We'll see about that :)

Many thanks to [MENTION=3472611]dottat[/MENTION] for the thorough testing and feedback.
[X Style (Pure) Android Development] newHere:):
Thank you very much for the awesome kernel! :)

Just wondering if trying to solve the issue with DT2W and Moto display together is on your list...

Of course I'm not asking for ETA...

Thanks again! :)
[X Style (Pure) Android Development] dirtyhank:
Sure, I'll give it a try but I'm not sure it'll be possible to have them working simultaneously. The most promising approach, in my opinion, would be disabling DT2W/S2W temporarily during the few seconds Moto Display is on. After all, you don't need DT2W/S2W then since you can unlock the device from Moto Display.
[X Style (Pure) Android Development] vimal_jakmola:
Now the 7.1 is the best all of its predecessors now we can excess the usb direct in file explorer
[X Style (Pure) Android Development] newHere:):
Thank you very much! :)

Sounds good :)
[X Style (Pure) Android Development] zohar_ml:
0.7.1 fixed my ambient light.

Had problem of dark screen with 0.7.

Now I dont have it any more.

Is there any exposed setting to jump strait to the home screen after S2W?
[X Style (Pure) Android Development] unitz0mbie:
anyone have color control installed? or what are ur rbg, contrast and brightness settings?
[X Style (Pure) Android Development] dirtyhank:
Nope, you'd have to disable screen lock in security settings.
[X Style (Pure) Android Development] sir-harlekin:
Is it possible to add wake gestures from flar2?

And can you name the terminal command to enable/disable DT2W?
[X Style (Pure) Android Development] kadopt:
[MENTION=2400758]dirtyhank[/MENTION]

0.7.1 is ok so far regarding to s2w.

Do you think you could provide some network related kernel modules like cifs, nfs, etc, either baked in the kernel or standalone? Thanks.
[X Style (Pure) Android Development] Cowbell_Guy:
Can anyone recommend a "balanced" profile for Kernal adiutor?

I'm loving the performance profile on 7.1, although it is crushing my battery. Similarly, I'd like a little bit more out of my phone than the battery saving profile gives, and I'm not smart enough to really understand the otimum way to tweak things, etc. I mainly just do web browsing, email, etc, no gaming on my phone.
[X Style (Pure) Android Development] dirtyhank:
Enable:

echo 1 > /sys/android_touch/doubletap2wake
echo 1 > /sys/android_touch/sweep2wake

If you run the commands when screen is off they won't be in effect until you turn it on and off again.
[X Style (Pure) Android Development] dirtyhank:
I don't like to fatten the kernel more than necessary but I'll see if they can be included as loadable modules.
[X Style (Pure) Android Development] dirtyhank:
Check the OP again ;)
[X Style (Pure) Android Development] krohme:
@ dirtyhank - many thanks for your work here, very impressive the way this kernel has developed :thumbup:
[X Style (Pure) Android Development] newHere:):
+1

And also thanks for being very responsive to user's requests :)
[X Style (Pure) Android Development] Cowbell_Guy:
Nice! Thanks! I'll roll with this one for a while. I must say though, I loved me that blueactive governer in the performance profile
[X Style (Pure) Android Development] Ghost9867:
sorry for the question but this kernel will work on aosp based rom ?
[X Style (Pure) Android Development] kadopt:
No, Hashbang was trying to make one though.
[X Style (Pure) Android Development] gpz1100:
@DH, any thoughts on which takes more processing power (cpu)/battery to achieve, the tap or swipe to wake?

My thinking is the latter is it takes a longer duration of interaction with the screen.

Btw, big difference in temps from the stock optimized kernel and this in the TruepureXMM 2.6.2 rom.

No lockups or reboots, but i'm still debating dropping the cpu speeds back to stock (1.4 & 1.8). Battery operated mobile device and overclocking doesn't add up to me :) Perhaps a similar result can be achieved by tweaking other parameters rather than bumping up the cpu speed?
[X Style (Pure) Android Development] saidmsb:
Great work dev

been my daily driver for long time..can you add voltage controls ?pls?
[X Style (Pure) Android Development] countryfolk07:
If you use kernel adiutor you should have voltage control.
[X Style (Pure) Android Development] saidmsb:
The option is there but i can't change anything
[X Style (Pure) Android Development] dirtyhank:
They are both very similar in terms of complexity. Use whichever you like the most and disable the other, there's a tiny overhead when both are enabled at the same time (basically both handlers try to make sense of the input registered by the touchscreen).
[X Style (Pure) Android Development] dirtyhank:
Right now voltage is "read-only". Honestly, I don't think there's much room for undervolting, this CPU is pretty picky.
[X Style (Pure) Android Development] gpz1100:
I prefer the double tap, but am having a strange issue. If the phone is in my pocket for an extended time, double tap/swipe doesn't appear to wake, nor does the power button.

I'm using the 0.7.1 kernel with the performance settings in kernel auditor.

I am using amplify to limit several google location wakelocks and alarms.Aside from that everything else is stock.

Is there a particular service/wakelock that this function relies on that should not be limited in anyway?
[X Style (Pure) Android Development] dirtyhank:
I'm using Amplify too and never experienced this issue. Maybe you went too far with it? I just blocked the longest running wakelocks tagged as "Safe to Limit".

There's a wakelock for DT2W but it's very short lived (triggers upon first touch and keeps the device awake for half a second waiting for the next tap).
[X Style (Pure) Android Development] gpz1100:
We'll see. I do have some high values for some (4000 or 5000 seconds). I may just start over and get rid of amplify altogether to establish a baseline.
[X Style (Pure) Android Development] dirtyhank:
Wow, that's quite a lot, I tend to use the default 240secs on most of them. The stats show a 60/40 ratio of allowed/blocked, not a lot but noticeable nonetheless.

Have you changed cache settings? I've noticed that increasing the dirty_ratio and dirty_background_ratio (close to 90 or higher) while lowering vfs_cache_pressure (20 or lower) sometimes leads to severe slow downs.
[X Style (Pure) Android Development] gpz1100:
Negative. Left all that at default except for the changes mentioned in the OP for performance profile.

Probably a good idea to leave things for a few days to have a good baseline.
[X Style (Pure) Android Development] techware7:
Any problems with vibration strength sticking after reboot? So far is the only parameter that won't stick. 0.7.1 on stock MM here + kernel adiutor.
[X Style (Pure) Android Development] gpz1100:
For the double tap to wake, is there any possibility of implementing more granular control?

For example only respond to double taps in the lower left or right part of the screen (the half screen setting in kernel auditor has no effect). Also, control the interval between taps? I find just handling of the phone seems to trigger the double tap.
[X Style (Pure) Android Development] dirtyhank:
The full/half screen setting in Kernel Adiutor is meant for devices where the touchscreen can be partially turned on to save power. As far as I know that's not possible on this device so it doesn't matter whether you select half/full, the touchscreen will always be fully active.

Regarding the interval, right now is set at <700ms. It could be lowered if you guys think it's too long.
[X Style (Pure) Android Development] dirtyhank:
Here we go:

v0.8

Update to Linux Kernel 3.10.99

Power efficient workqueues

NTFS support

NFS and CIFS support (you'll probably need additional user space binaries)
[X Style (Pure) Android Development] urimevs509:
"no mirrors"...
[X Style (Pure) Android Development] *.jpg:
What urimevs409 said.
[X Style (Pure) Android Development] urimevs509:
it's online now...
[X Style (Pure) Android Development] dirtyhank:
Yep, it's a Kernel Adiutor bug. It works fine with EX Kernel Manager.

BTW, I've been thinking about changing the default vibration strength. What value do you guys think would be a good one? I use myself a 60%.
[X Style (Pure) Android Development] dirtyhank:
Yep, just reuploaded it. Seems like the first upload didn't go through for some reason, weird.
[X Style (Pure) Android Development] caspersfi:
Yeah that bug has been driving me a little nuts lol. I have my vibration set to 50 or 60 percent so yeah if you would make the default value at 60 that would be awesome.

Thanks for your work.
[X Style (Pure) Android Development] techware7:
Yep, works great with EX kernel manager, however hot plug option disappeared on EX but working nicely on Adiutor. Weird...
[X Style (Pure) Android Development] dirtyhank:
Unfortunately EXKM doesn't support hotplug control :(
[X Style (Pure) Android Development] techware7:
Weird it used to have it when I tried it long ago with my Nexus 5
[X Style (Pure) Android Development] techware7:
I guess it still has it? Play store description says it does
[X Style (Pure) Android Development] dirtyhank:
Well, maybe other hotplug drivers but not the MPdecision.
[X Style (Pure) Android Development] gpz1100:
Understood. Is there a way of editing this setting without recompiling? My issue is sometimes the phone will turn on just from being picked up because fingers accidentally touched the screen just right.

I wonder if LG's implementation is to test the prox or brightness sensor to determine if phone is in pocket/purpose before acknowledging the taps as a valid wakeup sequence. Or maybe they have some other logic in place to prevent accident wakeups?

Considering the above, swipe to wake seems safer.

Does this have to with core/thread distribution? That is a any core can execute the instruction, not just the one that scheduled it?
[X Style (Pure) Android Development] dirtyhank:
Nope, the interval is hardcoded, will try to adjust for next release.

Yes, exactly. In stock kernel workqueues are tied to the CPU they were created on and so when work is scheduled it doesn't take into account whether the CPU is online or not, thus forcing some CPU to be awaken. This patch attempts to make some queues aware of CPU state, allowing work to be rescheduled to online CPUs.
[X Style (Pure) Android Development] gpz1100:
It's a difficult call to make. DT2W should not be trigger sensitive, but nor should it be difficult to use. Does the framework let you add any additional logic to it?

Edit: Thinking about it some more, I actually think increasing the delay between taps might be the right direction. Rather than a taptap to wake, it'd be more of a tap.............tap - say 1500ms.
[X Style (Pure) Android Development] kadopt:
Any mirrors? The host has no files. I wanna try cifs.

[edit]found it by using search on the host[/edit]
[X Style (Pure) Android Development] svs57:
I got msg: MotoCare crash with 0.8 kernel.

PS when screen unlock
[X Style (Pure) Android Development] SpasilliumNexus:
Check your setup. It's fine.
[X Style (Pure) Android Development] svs57:
I haven't this setting. May be because latest security update haven't come yet.
[X Style (Pure) Android Development] gpz1100:
Noticing some strange BT (bluetooth, blue tooth) behavior. Bettery battery stats is indicating it's turned on under graphs/history. In android settings, BT is set to off. Yet somehow it appears to be on?

After a reboot, according to BBS, BT stays off for about a minute, then gets tripped on.

Tried flashing the stock optimized kernel back and BT stays off.

Thoughts?

Edit: If I turn wifi off, then the BT column in BBS registers a 0 (off), so somehow this might be tied into the wifi? Also, under the either kernel, the wifi column in bbs shows a 0 (off).
[X Style (Pure) Android Development] Rocketval:
Try disabling both options in advanced position settings.
[X Style (Pure) Android Development] gpz1100:
What? What options in what advanced position settings?
[X Style (Pure) Android Development] dirtyhank:
I don't know, GSam Battery Monitor reports bluetooth state correctly. I think BBS probably relies on a sysfs/proc file I might have disabled (I tried to disable most debug/profiling stuff) and freaks out.

I'll install BBS and take a look but I don't think is a real issue, more like misreporting on BBS side.
[X Style (Pure) Android Development] BooBzi:
You can find these settings:

Settings - Location - 3dots - Scanning!
[X Style (Pure) Android Development] gpz1100:
^^Of course that's turned off.

Looking forward to dirtyhank's findings.
[X Style (Pure) Android Development] dirtyhank:
This is weird. I disabled BT but left WiFi enabled and BBS history shows 0 for both. However, the main screen is ok, WiFi time is computed while BT doesn't even show up.

For some reason BBS can't properly read WiFi and BT state within the history code.
[X Style (Pure) Android Development] gpz1100:
The two sentences seem to contradict each other. What did you mean

however

the main screen is ok if history is showing 0 for both?

I guess this is just one of those MM bugs that will take some time to resolve in current apps.
[X Style (Pure) Android Development] dirtyhank:
Main BBS screen: the one you see when you open the app.

History screen: the one you access from the Graph screen.
[X Style (Pure) Android Development] gpz1100:
^^Right, so you're saying on yours, on the history screen it's showing 0 for BT when wifi is enabled, and also on the main BBS screen there's no entry for BT. This is the expected behavior when bt is off.

On mine, it's showing 1 (for bt) and 1 (for wifi) on the history screen, but nothing on the main screen for BT (when wifi is on) and bt is off (in settings).

My goal in all of this is to figure out if there's a bonafide issue or it's just cosmetic.

I think the best way to put this to rest is to determine if BT is on through some other means such as adb shell or terminal. What commands can I use to test this?
[X Style (Pure) Android Development] dirtyhank:
Run this from a terminal:

pgrep -l wcnss_filter

If BT is on you should get something like this:

14646 /system/bin/wcnss_filter

If it's off you'll get no output.
[X Style (Pure) Android Development] gpz1100:
^^

Confirmed. No output with it off and a similar output as above with it on.

Thanks!
[X Style (Pure) Android Development] chibichuba:
How does the double tap to wake with battery? Does it leave the touchscreen on while the screen is off, or is it not yet power efficient in experimental?
[X Style (Pure) Android Development] dirtyhank:
Barely noticeable.
[X Style (Pure) Android Development] mrbracht:
I love this kernel and I love the battery life but I seem to get massive lag while. Multitasking after a while. Any help? Thank you again for this awesome kernel
[X Style (Pure) Android Development] gpz1100:
Are folks seeing a high wlan_wow_wl kernel wakelock time? I've got the usual wifi scanning options turned off, not sure what else to try?
[X Style (Pure) Android Development] Tech_Savvy:
I think Its wifi issue where if connected to a wpa2 secure wifi it constantly wakes the device... Something about a wpa 2 secure wifi hptstop does it...
[X Style (Pure) Android Development] guile50:
I have it too while opening some specific heavy apps such as Facebook or snap chat, who were supposed to be on RAM, but they load again and stutter as hell.

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] dirtyhank:
If you are a heavy multitasker enable KSM or ZRAM. Read the FAQ in post #3.