yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] tbalden:
CM 2.3.6c1 installer update

Changelog:

- added ramdisk injection method from AnyKernel installer, should fix battery issue (don't forget to have the stock cm/aosp kernel boot.img back on the device before installing this flashable!)

Installer:

http://d-h.st/C1E

And merry x-mas folks...
[One (M7) Original Android Development] dog77k:
New kernel fixed battery issues for me. Thanks.
[One (M7) Original Android Development] eng.stk:
merry x-mas mate ;)
[One (M7) Original Android Development] benmeroff:
Thanks!

That did it, thanks so much tbalden!
[One (M7) Original Android Development] kamilmirza:
can someone explain how to flash 2.3.6c1?

I have flashed this and battery meter is working fine but I'm missing governors
[One (M7) Original Android Development] tbalden:
What kind of governors do you miss?

Cpu governors are the ones that stock cm kernel provides.

If you need additional tweaks checkout [MENTION=4635674]n3ocort3x[/MENTION] aosp kernel thread.

This one is a lean one with the features detailed in the OP
[One (M7) Original Android Development] kamilmirza:
oops sorry silly me :D
[One (M7) Original Android Development] tbalden:
CM 2.3.6c3 update

Changelog:

Version 2.3.6c3 - Dec 22

- Fix regression in pocket detection (detection didn't work in suspended state, probably since first version here in this thread)

- Fix accidental screen off happening immediately after flick wake

Installer:

http://d-h.st/5aH

And merry x-mas again... :)

EDIT: bumped to c3, fixing accidental screen off happening immediately after flick wake, which i detected right after releasing 2.3.6c2 :)
[One (M7) Original Android Development] Toxicoblivion:
Link to the last update for cm10.2?
[One (M7) Original Android Development] tbalden:
Look for that in n3o's teamsevenaosp kernel thread. This was only released for cm11
[One (M7) Original Android Development] dseries60:
This kernel works perfectly on the new AOKP 4.4.2. Thanks for a great kernel tbalden!
[One (M7) Original Android Development] tbalden:
Good to know thanks for the feedback
[One (M7) Original Android Development] perfectslim:
I'm going to try this on ProBAM to compare with n3ocort3x's kernels
[One (M7) Original Android Development] dbaler:
Got a random reboot, running paranoid Android here's a log. My wake options are double take to wake. And flick to screen off. My 384 mhz was undervolted to 875 https://www.dropbox.com/s/wojq0dz9h9uuukm/last_kmsg3
[One (M7) Original Android Development] perfectslim:
It works perfect on ProBAM 1.2.1, and AOSP Teamseven's kernel doesn't work.
[One (M7) Original Android Development] echo511:
Reporting in: Installed 2.3.6c3 onto OneDroid Beta15 (which was installed following full-wipe).

Everything is running A-OK! No issues on flashing, no oddities while using it all as a daily-driver.

Excellent kernel! Thanks for the hard work on it!!
[One (M7) Original Android Development] eng.stk:
[MENTION=3088420]tbalden[/MENTION] New commits to cm11 m7ul kernel mate :fingers-crossed:
[One (M7) Original Android Development] 7sen:
Unlock gestures features included in this kernel :confused: :rolleyes:
[One (M7) Original Android Development] dog77k:
This kernel seems to still have the issue with changing the processor frequency, as described at the top of page 14 of the CM thread. This was fixed a few nightlies ago for the stock CM11 kernel, using the solution (or some form of it) at the bottom of that same page. Could the same fix be implemented for this kernel?
[One (M7) Original Android Development] Keasby:
Great Kernel development again!

But...

My Doubletab2Wake won't work with SlimKat 4.4.2 beta 2.1.

Need logcat?

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] EnIXmA:
Does this kernel have the k-exec hard boot patch for multirom's hack?

If not, could you please include it in your next build.

Thnx
[One (M7) Original Android Development] eng.stk:
k-exec would be nice, also new commits had been merged, hope [MENTION=3088420]tbalden[/MENTION] can take a look :good:
[One (M7) Original Android Development] zotac1907:
This bug occurs also on my HTC with newest CM11 Nightly and v2.3.6c3 of the kernel.
[One (M7) Original Android Development] dog77k:
Yeah, it's been around for a while now.

From the CM changelog, it looks like they worked on the cpu frequency code for the 1-15 nightly, but this issue still exists with this kernel.
[One (M7) Original Android Development] dog77k:
I just installed the 1-22 nightly and this kernel and the frequency change issue is fixed! It looks like the cm maintainers had done some more work on the cpu freq code for the 1-20 nightly.

:thumbup:
[One (M7) Original Android Development] tbalden:
thanks for the heads-up. I'll try to catch up with the upstream m7 kernel changes when i get some time. Anyway lucky for now that it seems to resolve with framework/rom changes.
[One (M7) Original Android Development] zotac1907:
On my One it isn't solved yet with newest nightly and latest stable build of this kernel..
[One (M7) Original Android Development] the.emilio:
Any chance of being able to get this on the sprint variant? I know some kernels for Sense were able to be ported by changing the mounting points..
[One (M7) Original Android Development] bobtentpeg:
Looks like this kernel + some audio changes in the newest CM nightly cause breakage of both mic and headset.
[One (M7) Original Android Development] tiny4579:
Yep. That's due to the kernel change in cm to a common msm8960 based kernel. The kernel will need to be rebased on the msm8960 kernel for proper audio routing.
[One (M7) Original Android Development] tbalden:
Kernel update:

Merged with upstream

Installer 2.3.6c4:

http://d-h.st/3yP

Please test and report back
[One (M7) Original Android Development] Alef_0:
With CM11 didn't work :(

Sound on call issue
[One (M7) Original Android Development] tbalden:
Ok, I'll need a full rebase..

Thanks for reporting
[One (M7) Original Android Development] MacLaughlin:
Long Logo press to wake doesn't seem to work properly. Need to press several times till it works.
[One (M7) Original Android Development] tiny4579:
Is that with the new test kernel? Someone thought the fix broke the temporary fixes people were using.
[One (M7) Original Android Development] MacLaughlin:
Yes indeed
[One (M7) Original Android Development] oo0:
same happens for backbutton. sometimes it just ain't work, only onscreen control helps.
[One (M7) Original Android Development] tbalden:
Don't expect a rebase soon. I don't have much time on hand, and i plan to wait some time till the new msm8960 kernel settles

Edit: found some time, see below ;)
[One (M7) Original Android Development] tbalden:
CM-11.0 Installer update

Changelog:

- Rebased to msm8960 common kernel for latest Nightlies, use with latest nightlies only (01/26 or before is NOT compatible)

- All features of Stable Edition except Button Light Notification (will get to it later)

Installer:

http://d-h.st/mj3
[One (M7) Original Android Development] xero110:
Thanks for the update. Seems to be working great. The only thing I've found is that 'Remove 3 dot menu' does not work. I'm not sure if it's the kernel or the fact that CM has removed the option to do so.
[One (M7) Original Android Development] tiny4579:
Cm doesn't have a 3 dot menu bar.This option can be ignored.
[One (M7) Original Android Development] dseries60:
Tbalden, you Sir are amazing. Your latest kernel update resolved the no sound issue I was having on the latest nightly from vanir. Thanks so much for all your efforts for our HTC one!
[One (M7) Original Android Development] oo0:
+1
[One (M7) Original Android Development] tbalden:
CM-11.0 Installer update

Changelog:

- still new msm8960 base

- All features of Stable Edition now:

- added back Button light notif

- fixed up CIFS mounting

Installer 2.3.6c6:

http://d-h.st/HUZ
[One (M7) Original Android Development] oo0:
working great with PACMAN 4.4.2 Alpha.
[One (M7) Original Android Development] tbalden:
Great, thanks for the feedback
[One (M7) Original Android Development] TiiXiboy:
This looks awesome. I'm going to try this today, can't wait to use tap2wake :D
[One (M7) Original Android Development] tbalden:
Minor update 2.3.6c7

-Change:

make pocket detection more effective (lowering the nearness detection threshold)

In many cases it woke up in my leather case. On AOSP roms the new kernel base (msm8960) the proximity sensor seems to be less sensitive, so i added a low threshold to avoid accidental wakes. Seems to work much better, if not perfect. 90% of the cases it didnt wake now in my belt clip leather case.

Installer:

http://d-h.st/cDh
[One (M7) Original Android Development] popy2006:
Hey tbalden. THX for The great kernel. I am using dt2w, is there a way to get it fullscreen Working. Thx

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] tbalden:
No, there's no such thing in this kernel yet. I'll consider adding a bigger area for tap as an option in installer... I think it's giving too much possibility to wake the phone accidentally, but as an optional thing I'll add it to the to do list.
[One (M7) Original Android Development] TiesB:
I'm having major graphical glitches and the CPU doesn't sleep. Is this a known problem or did I do something wrong?

I am on one of the latest Omni nightlies and just flashed this kernel.

Thanks in advance :)
[One (M7) Original Android Development] tbalden:
I don't think omni is using msm8960 kernel base. So flash 2.3.6c3, the last version that is based on m7 separate kernel. Otherwise you might have issues, just like you described
[One (M7) Original Android Development] TiesB:
Aah alright, that makes perfect sense. Will try. Thanks a lot, also for your work!
[One (M7) Original Android Development] dseries60:
c7 works perfectly on latest vanir. Thanks tbalden!
[One (M7) Original Android Development] Alef_0:
Me too. TNX
[One (M7) Original Android Development] popy2006:
Ok tnx, would be nice to see the feature :)

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] tiny4579:
If you implement it can you use the same sysfs as flar2 to prevent conflicting interfaces making app support trickier? I prefer uniformity among sys interfaces. The code doesn't have to be the same though.
[One (M7) Original Android Development] dbaler:
Does anyone know if the latest kernel works with the latest Paranoid?
[One (M7) Original Android Development] kamilmirza:
it should :)

try it and report back :)
[One (M7) Original Android Development] tiny4579:
Only if they switched to the new kernel base. I'm guessing not. If you flash it and paranoid is using the m7 kernel you won't have audio in calls due to naming differences between the two kernels and device audio drivers.
[One (M7) Original Android Development] dbaler:
Ah, so that's why my calls weren't working, I flashed the sti kernel with the latest paranoid and was wondering why my calls weren't working. From that I assume this kerenel will work.
[One (M7) Original Android Development] Spoofy:
Working with CM11, the only kernal currently rebased properly.

Sweep2wake is quite buggy compared to STI.

Keep up the great work!
[One (M7) Original Android Development] oo0:
i can be wrong, but seems like double tap to wake was easier to perform on earlier 2.3.6 builds. hard to wake the device with first two taps) is it possible to lower threshold a bit? or it was my wrong impression?
[One (M7) Original Android Development] sharonbw:
Very happy with this kernel (2013/12/22) on CM11 (2014/01/23)!

I couldn't live without logo2menu (I don't understand why it's not an option on the phone or at least in every Rom and kernel lol). I'm also enjoying flip2wake and flip2sleep however I'm finding the wake is much more difficult to perform. This might be on purpose - I don't want my phone too easy to wake up - but I'm finding it a little frustrating. Sleep always happens on first flick but wake is inconsistent and sometimes impossible. Am I doing it wrong? I assume it is the same action for both...

P.s. Since the 2 previous posts mention similar difficulties I'm thinking perhaps same sensitivity to wake setting even though different actions?

Sent from my GT-p511x
[One (M7) Original Android Development] Powereh:
Yeah STI Kernel is still built off the old stuff, I realised this on Saturday when my friend tried to call me haha. The Dev has rebased it since but not released it.

Anyhow to the question this kernel works fine with Paranoid, The only issue I really have is that when I press power the screen doesn't instantly turn on like old versions of this kernel & STI Kernel.

Don't know what that issue may be or how to sort it out though.
[One (M7) Original Android Development] tbalden:
The slow screen on issue is an issue on the new common kernel, stock cm, at last it was an issue the time I forked. Will check upstream tho..
[One (M7) Original Android Development] tbalden:
It's related to the new kernel base. Seems to sleep "deeper" which is good on battery but makes wake stuff less reliable
[One (M7) Original Android Development] Powereh:
Thanks, I don't really keep up with most changelogs. But at least it isn't something I'm imagining :)
[One (M7) Original Android Development] Spoofy:
Thanks Tbalden,

I don't think I noticed the issue as much on the CPUQUIET version of this Kernel @ http://xdaforums.com/showthread.php?t=2236121

Is there any chance you could rebase that Kernel it is the best Kernel in XDA no other can compare. Plus, deep sleep is far from needed with the new governor!

Regards
[One (M7) Original Android Development] tbalden:
Update 2.3.6c8

Merging upstream governor changes (ondemand/conservative) - it seems to be waking slightly quicker here using Ondemand

Installer:

http://d-h.st/qeS
[One (M7) Original Android Development] oo0:
thank you very much once again! waking is better now.
[One (M7) Original Android Development] sharonbw:
+1

Sent from my GT-p511x
[One (M7) Original Android Development] sharonbw:
Whoops!!! Latest Kernel changes improved the issues I had with flip2wake but broke my phone! I placed a call which went through but party could not hear me. :( Reversion to 1/22 kernel fixed.

Sent from my GT-p511x
[One (M7) Original Android Development] tiny4579:
You need to use the latest cm build. It won't work right with older cm builds and some other roms.
[One (M7) Original Android Development] kamilmirza:
[MENTION=3088420]tbalden[/MENTION] thanks for the latest build :good:

everything thing is super smooth but can you make ondemand governor less aggressive for battery life :fingers-crossed:

i barely make 4 hours screen-on with light usage (facebook whatsapp messaging etc) with ondemand :silly:

or add smartmax :D that would really swell :laugh:
[One (M7) Original Android Development] sharonbw:
Oh, of course. However, I've been reading about kernel and radio issues with latest though so I'm ok with what I have for now.

Question: does anyone know off the top of their head which combination of CM11 and TeaMSeven predates the wake delay?

Sent from my GT-p511x
[One (M7) Original Android Development] Pons:
I don't know the numbers, but it's the one when it was the m7 kernel, before the msm8960 merge. And then the corresponding CM build before CM merged into the msm8960 kernel.
[One (M7) Original Android Development] Spoofy:
Exactly what I am after, if your on older CM builds you can use the incredible CPUQUIET version with smartmax that I linked earlier.
[One (M7) Original Android Development] kamilmirza:
you mean neo's kernel?
[One (M7) Original Android Development] Spoofy:
Yeah, that's the best IMHO.
[One (M7) Original Android Development] kamilmirza:
I have tried that but BLN doesn't work for me on neo's kernel :(
[One (M7) Original Android Development] n3ocort3x:
[MENTION=3088420]tbalden[/MENTION]

my friend, i wasnt aware u already working on a CM11 version :) i just saw today as i was browsing the forums (normally i go into subsciptions). I played last week with the new msm8960 Kernel but no matter what i did i couldnt get s2w stuff to work. merged fine, compiled fine, didnt work :p U having any success with this so far ?? i saw u already merged some stuff :)
[One (M7) Original Android Development] tbalden:
yes, everything smooth and sailing :)

this is what you will need to make it switch screen on:

https://github.com/tbalden/android_...mmit/91aff49fdf8d6238267966a35891f2744a0a89b0

or you can try to use the pm8xxx pwr key input device too instead of the gpio_event device.
[One (M7) Original Android Development] n3ocort3x:
Hats of Master tb :) u saved me a lot of time. I ditched it after a few hours but that's great news indeed :) long time not heard time for a small chit chat in gtalk this weekend :)
[One (M7) Original Android Development] tbalden:
Took me some headscratching before I realized the diff in the board files :) also I didn't notice the kconfig that its using the pm8xxx pwr key driver instead until Flemmard mentioned it. :)
[One (M7) Original Android Development] n3ocort3x:
Yeah its quite tricky... i played the last days with hammerhead kernel and run into some issues but everything is sorted out now :) now onto m7 again. Many thanks for teaching me another leasson master tb. Great to see u working on CM11 :)
[One (M7) Original Android Development] matmaneyre:
Hi all. Maybe someone can help me...?

I'm on Pro.BAM (CM11) and I was looking for a decent kernel. I've tried STi which seems to do most of what I wanted, except overall performance isn't great. I flashed this one and performance is much better, but for whatever reason, none of the wake options are working. I really got used to DT2W with Bulletproof (Sense) so I was looking for something with similar capabilities on CM11. Also, Fast Charge doesn't seem to be working for me either. I'm still (slowly) discharging while plugged in to USB.

Any help would be greatly appreciated. I really like the ROM, but without a decent kernel that ticks all the boxes, it can't be my daily driver. Thanks in advance if you can help.

EDIT>> Never mind...I flashed n3ocort3x's AOSP v54 and it all seems to be working as I hoped. Thanks! :good:
[One (M7) Original Android Development] n3ocort3x:
[MENTION=3088420]tbalden[/MENTION]

i just try to investigate why s2w is slow on msm8960 kernel source, i know it might be useless but i compared old and new one with kmsg:

old -> fast s2w: http://pastebin.com/nZcmAzuZ

new -> slow s2w: http://pastebin.com/pHWJvbSW

maybe the key is somewhere in board file or power ??
[One (M7) Original Android Development] tbalden:
I was trying to check what causes the long unblank time (over 800msec), reverting some stuff to the m7 like framebuffer dev and some panel stuff, it didn't help unfortunately.. I'd say maybe some sync point is holding the unblank on the common kernel, but no clue exactly what's being waited for
[One (M7) Original Android Development] tiny4579:
This is an issue on evita as well. It might help to see when it started for them and see if we can link it to a change. You might be on to something with the sync point.

So I checked the fix in the m7 kernel and basically everything done to fix it there is already in place here in the msm8960 common kernel so as Intervigil said in irc it's something else.
[One (M7) Original Android Development] tbalden:
[MENTION=3500210]tiny4579[/MENTION]

What commit was the fix in the m7 kernel, can you point me to that patch?
[One (M7) Original Android Development] tiny4579:
http://review.cyanogenmod.org/#/c/49546

If you look at patch set 2 that seems to be the fix. I looked at the display file in the new kernel and everything seems to match up with the patch set 2 change for m7-display.
[One (M7) Original Android Development] tiny4579:
I'm guessing that commit I link didn't do any good since the display stuff seems to already be in the common kernel. Also, there were other wake related commits also merged at or around September 2, 2013.

This should give you a starting point:

http://review.cyanogenmod.org/#/q/s...rnel_htc_m7+branch:cm-10.2,n,002780dd0000c1bf
[One (M7) Original Android Development] Spoofy:
[MENTION=3088420]tbalden[/MENTION] guys I came across an interesting post on the CM11 thread about narrowing down the wake issues have a look at http://xdaforums.com/showthread.php?p=50194775

Thanks!
[One (M7) Original Android Development] tiny4579:
[MENTION=3088420]tbalden[/MENTION],

The wake delay on power on has been resolved in CM's msm8960 kernel, Excessive delay is down to ~200ms now and it turns on almost instantly.

I also want to see if thers's a way to improve the tuning of the ondemand governor to make it more like stock and remain smooth without sacrificing battery by readily jumping to the max frequency.
[One (M7) Original Android Development] tiny4579:
I have ported ondemand from GPE - see https://github.com/tiny4579/android...mmit/672a3a7afef4ed4cfff60dd550d6ef875af1d69c

The only problem is I had to disable interactive to get it to build, so this is not quite ideal for merging into the mainline kernel.
[Nexus 5 Q&A, Help & Troubleshooting] andrewt328:
Have LTE but YouTube videos take a while to buffer. Any suggestions
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] xfive420:
I was wondering what people do for flashlight capability on their phones. Which app/widget do you use? How do you access it? How quickly can you get to it when you need it? Maybe it's just me, but I like having access to a light quickly and easily.

I've gone through a few methods:

1. First I was using the assistive light widget on my home screen because it has virtually no delay and a very built-in look to it, but it's just too dim and the brightness cannot be adjusted. And to use it, I have to get to my home screen first.

2. I started using the smart flashlight widget, which uses the full brightness capabilities of the camera flash LED. It also looks nice but has a slightly longer delay than the assistive light. Still, it's just a widget and to use it I first have to turn on the display, swipe to unlock the phone, and then click the widget.

3. I wanted faster access, so I tried using a home screen widget. Tiny Flashlight + LED has one, but that still requires turning on the screen, swiping (1 or more screens) to the flashlight widget, and then clicking on a full-screen button. Still not very speedy or efficient, and I'm not a fan of the "multiple widgets" lock screen anyway.

4. Just now I set things up using Tasker, which allows you to automate a flashlight using the TeslaLED tasker plugin. Basically I set it up so that when the lockscreen is visible, the TeslaLED flashlight is toggled by shaking the phone. So far it seems pretty efficient but I'm a little concerned it will misfire on me.

It would be cool to turn on the flashlight with a combination of hardware buttons, or have a toggle button as one of the quick apps on the lock screen, but I don't think either of those options are possible.

So for anyone else who likes quick access to their flashlight, what do you do?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] c-mack:
With the screen off I use the long volume up toggle from wanam. With the screen on I use the stock widget.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Agent:
Wanam for sure. Of course you need root. Without root I've used both the assisting light and smart flashlight.