yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] onthehole:
Nah, they are great definitely. This is just uncanny though. edit: i am pretty sure it is something I am doing wrong. who knows.

Edit: just to be clear. I 100% figured out my GPS issues after 3 months of turmoil. Had to ruu, then factory reset with stock recovery. I then logged into my Google account and used the stock Rom for a day, enabling high accuracy in location settings and using navigation for the whole day. Nav started working pretty well after about an hour. Later in the day I was able to flash a new Rom and navigation has remained solid ever since. I am now able to use all of the the big three kernels without issue now. Thank you for the wonderful development you do for our device.

I can't even tell you how many paths I've gone down (topntp, messing with every setting on the phone, touching every kernel and Rom possible. Wipe this wipe that, GPS status, pulling the SIM card. So relwived to have this solved.)
[Verizon HTC One (M7)] nbelshaw:
Jabra cruiser2 has A2DP but no call audio. Also my Jawbone Era (1st gen Era) won't work for call audio but will on A2DP. Yet my Era by Jawbone (latest model) does both.... Any ideas? Other kernels I have tried have the exact opposite problem. Cruiser2 and old model Era work but not latest Era by jawbone. All work for media playback however. Thanks for the hard work
[Verizon HTC One (M7)] brymaster5000:
What version, sense or aosp? A log would go a long way to if you can grab one.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] nbelshaw:
Just a logcat after an attempted call with each? Or would you need all the pairing info as well? Sense (4.4.3) NuSense 8.0.
[Verizon HTC One (M7)] brymaster5000:
Out of curiosity, does the blue tooth issue happen on other roms with this kernel. Nusense uses different binaries and driver configurations than what this kernel is set up for. If you can replicate your issue on other roms (ie stock, etc.) definitely send me a log cat. If not, then you'll have to pick the lesser of the evils (one headset working and the other not).

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] nbelshaw:
Been on NuSense since the beginning but latest version broke my current headset (Era by jawbone) for phone calls. I tried your kernel and it fixed my one headset and broke the other two. So yes I was picking the lesser of two evils but wondered if the Bluetooth profiles were a kernel thing or a ROM thing. I have been told that different roms (including official stock roms will have some but not all the profiles for all headsets and BT speakerphones.

Mostly just curious. Would love them all to work as they did on previous versions of NuSense vzw base (6.8 I believe) but I can get by...
[Verizon HTC One (M7)] brymaster5000:
Thanks for the feedback. Any chance you could try another rom with this kernel to check? If it doesn't work, I'd love a logcat. Thanks.

---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------

On a separate note:

Update to the Old gestures sense kernel: tweaked sensitivity of doubletap to wake (hopefully eliminates the need - sometimes - to double tap it three times). OP links are updated to 10-16.

PS - I am testing AOSP first thing tomorrow morning. I have lots added including wake gestures....just need to test.
[Verizon HTC One (M7)] brymaster5000:
Alright people, from here on out it will be performance updates to the aosp kernel. I added a bit of performance stuff, but more importantly, touch wake stuff. Enjoy:

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

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
How's it running? Anyone flash the aosp kernel yet?

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] kiko3:
I am on aosp kernel and everything is ok but i have some strange behaviour with power button. When i press power button to wake device screen turn on and then off. Now i am using volume buttons to wake device.
[Verizon HTC One (M7)] jukiewalsh:
Happened to me for awhile too but it stopped now. If you hold the power button until the reboot menu comes up the screen will stay on and just click outside of the menu and unlock your phone regularly.
[Verizon HTC One (M7)] brymaster5000:
I'll work on that in the next release.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
Reportedly all fixed. Power key should wake screen and stay awake now. New kernel in the OP. Let me know how it goes guys.

That's all for tonight - lots going on. I will get to some more tweaks soon though.
[Verizon HTC One (M7)] bmeek:
I am unable to turn on WiFi with the new aosp kernel and the current cm11 nightly.
[Verizon HTC One (M7)] brymaster5000:
Thanks, also got report I broke volume buttons. I'll try to fix it...this is why I hate CM and what they've done to the kernel.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] SynisterWolf:
I'm not seeing the Wi-Fi bug, ive toggled mine a couple of times now. i do have the volume button bug.

I am also not on the nightly, i am on he M11 snapshot. I did notice in the code review that they did change wifi drivers:

http://review.cyanogenmod.org/#/c/74730/
[Verizon HTC One (M7)] brymaster5000:
That is the reason for WiFi. I will need to patch in those changes from upstream. However, I'll keep two versions for those not willing to go to nightly just yet. And when nightly changes make it into a release I'll have the one.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
Thanks for the donation Michael!

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
So...running checklist of things to work on:

- volume and power button hiccups

- Wi-Fi upstream patch for nightlies

- low power module

And obviously the rest of the crap I haven't grabbed yet from the sense kernel.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] SynisterWolf:
You're doing LPM! I <3 you
[Verizon HTC One (M7)] brymaster5000:
I'm abandoning the aosp kernel. I've tried for the past week and a half to get that stupid power button wake issue fixed and I'm losing interest since I don't use aosp...

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] thewahlrus:
I see you posted over on the unsense thread your kernel works with it, but the screen shot looks like a more recent version than the one in this thread. Am I just missing the link somewhere? I like this kernel, I've used it in the past and want to try it on unsense. Thanks.
[Verizon HTC One (M7)] santod040:
I think you're confusing - Buck vs. Bry & m7 vs. m8

This is an m7 thread, the UnSense thread he posted in, is for the m8.
[Verizon HTC One (M7)] thewahlrus:
Oh snap. Tapatalk. I need to unsubscribe to some old threads. Thanks.

Fun fact, this kernel works on m8. No wonder it wouldn't go above 1.9 GHz.
[Verizon HTC One (M7)] brymaster5000:
Added GPE 4.4.4 links for a kernel I last built on 8/26. Has all the goodies - if people think it's good, I will update it.
[Verizon HTC One (M7)] SynisterWolf:
CM cough cough.

guess i get to switch.
[Verizon HTC One (M7)] atsoca:
So this would be newer than the 10/16 build?
[Verizon HTC One (M7)] brymaster5000:
This is for gpe, not aosp.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] atsoca:
My bad sorry

How is hawk?
[Verizon HTC One (M7)] brymaster5000:
No worries. Not sure, laying low I guess.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
I added a stock sense 4.4.3 kernel with only the wake features added. I enabled the advanced TCP congestion options as it doesn't add anything - just enables the user to pick them. And I built the kernel with Linaro 4.9.2 toolchain for optimizations. This was a request in [MENTION=2586080]andybones[/MENTION] bonestock thread - so here it is. Enjoy and let me know of problems or requests.
[Verizon HTC One (M7)] atsoca:
Will any of your kernel's work with santods new art ROM?

Also is Bluetooth kernel or ROM Dependant? I'm having an issue with Bluetooth on mentioned ROM

Thanx
[Verizon HTC One (M7)] brymaster5000:
GPE 4.4.4? It should work fine. The bluetooth thing is actually both the kernel and the ROM. Kernel needs the right driver stuff, and the ROM needs the right binaries and such. I am not sure how they will work as there are so many different configurations and each of us do things slightly differently. Try it out and let me know how it goes.

---------- Post added at 11:36 PM ---------- Previous post was at 11:16 PM ----------

New AOSP kernel in the OP. Wifi works - fixed a config that got goofed up some how when CM changed drivers.

Lunar-AOSP_kernel-11_08_2014
[Verizon HTC One (M7)] SynisterWolf:
For those that have the power button problem. Till bry can figure out what CM did I found that if you disable power menu on lock screen then just long press power button it will work correctly. I will still work with the guys and test till the bug is gone.
[Verizon HTC One (M7)] Rain__:
Thanks for your continued work on the AOSP kernel, I really appreciate it! I flashed the new kernel on Buckmarble's Vanilla AOSP ROM and it has been great so far. Only thing is the pesky power button issue, but that is manageable. I was having some weird issues with overclocking (underclocking, actually -- The CPU would always clock to ~1.7GHz even if something less was set as the max) on the kernel that is currently built into the ROM, but that is resolved with this!

I found that long pressing the power button works as well. Double-tapping to wake also gets around the problem as well, but double-tapping to wake has always been a bit finicky for me on the One. Has CM fixed this in their kernel?
[Verizon HTC One (M7)] keith7120:
I'm using the Elite_m7_Kernel-11_08_2014 with wake up only and it seems I have to tap up to 3 times to wake. I'm using the latest viper rom 7.0.1.
[Verizon HTC One (M7)] brymaster5000:
Yeah...same here on sense. I think it's a sensitivity issue with the m7 in general. I've played around with the sensitivities at a code level, which helped, but did not resolve completely. I could try higher values....just dont want it to be too sensitive that just moving the phone around in your palm wakes it up...

Thanks for the feedback.
[Verizon HTC One (M7)] Rain__:
Interesting... So it seems after flashing the latest AOSP kernel mentioned above phone calls no longer function. I don't hear it ringing when waiting for the other end, when the other end picks up, they can't hear me and I cannot hear them... completely silent. Likewise, when I receive a phone call, the phone rings properly but is completely silent when I answer... other end can't hear me and I cannot hear them. Any ideas? If not, is there somewhere I can download flashable zip of an older version (maybe the version that is currently in Buckmarble's AOSP ROM?). I don't make many phone calls, but it's kind of a necessary feature... :p (I made a backup before flashing, so reverting is not the end of the world -- an older flashable zip would be a bit easier though)

In the mean time, any way I can diagnose this further? Any information that could pose useful? I've already tried rebooting a few times, clearing cache, ect. Nothing has fixed it.
[Verizon HTC One (M7)] brymaster5000:
You're actually the second user to report this, which makes me think it's not firmware. I may have to sync up with CM. They have a couple of commits that I haven't merged yet.

Sent from my Lunar Ecliptic One.
[Verizon HTC One (M7)] brymaster5000:
CM users: try this one on for size

Elite-AOSP_kernel-11_12_2014

I merged in upstream patches from the CM repo, tweaked some stuff to get the power button back to normal. I reverted some of my initial attempts to get the wake features in there and threw in a different version that [MENTION=1331268]santod040[/MENTION] used in his Liquid kernel (so thanks are due to him for that piece). I might try to go back to the version of the wake features I had - as I like them better than the one I just patched in...but for now shtuff works.

So this means - sound for incall audio should work:fingers-crossed:, power button is back to normal
[Verizon HTC One (M7)] shine_118:
I flashed 11-8 sense Kernel on NusenseSIX 8.0 and found kernel verizon is “Unavilable”. What's reason？Love the pure sense kernel with wake gesture，Thanks Brymaster5000 hard work.
[Verizon HTC One (M7)] brymaster5000:
What does it say in trickster or another kernel app? I just realized I never added a name to it...so the kernel app should show it as built by me however.

Sent from my One.
[Verizon HTC One (M7)] peteangi:
I had the exact same thing happen with Viper 7.0.1 and Kangaroo Kernel. I restored a recent backup, but it didn't fix it. Installed a different ROM and now everything works. Not sure where the problem was or exactly what fixed it. I hadn't touched the kernel or ROM for a while so I don't know what changed to cause the calls to go silent.
[Verizon HTC One (M7)] brymaster5000:
Has anyone tried the latest aosp update? How's it running?

Sent from my One.
[Verizon HTC One (M7)] bc13:
I will try it later today. Thanks for all your work bry, I have been using your stuff since dinc2 days and you always go good work! Thanks again!
[Verizon HTC One (M7)] Rain__:
Whoops! I thought I was subscribed to this thread, apparently I wasn't and I never got a notification about the updated kernel.

I just gave it a shot though. The power button issue is resolved (or, it at least functions the way it should -- no need to hold down or anything to wake). I still had no sound in calls though. Like before, I tested outbound and inbound calls. For outbound: No ringing, can't hear the other end, and they can't hear me; for inbound: Phone rings normally (as expected), can't hear the other end, and they can't hear me. Seems like the speaker (the up-to-the-ear speaker) & microphone simply don't function. I forgot to test putting the phone into speaker mode before restoring the pre-flash backup (which does seem to resolve the issue, so its definitely something to do with the kernel). [MENTION=4597571]bc13[/MENTION] Are you getting the same in-call results?

Is there anything specific you want tested to help narrow this down? I haven't tried seeing if its throwing anything on ADB; I'll check later tonight if I get a chance.
[Verizon HTC One (M7)] brymaster5000:
Thanks for letting me know. Here's my thought: cm added/changed a config in their latest build for vzw. If you can do this command and post the file I'll check it out: adb pull /proc/config.gz

Thanks.

Sent from my One.
[Verizon HTC One (M7)] Rain__:
PM'd it to you.
[Verizon HTC One (M7)] brymaster5000:
Thanks, as soon as I get home I'll look.

Sent from my One.
[Verizon HTC One (M7)] brymaster5000:
Can anyone reproduce the no in-call audio on any CM based ROM's? If not, I will chalk it up to the fact that my AOSP kernel is not meant for Buck's ROM. My kernel is built from CM sources, and his ROM is built from straight m7 files. CM messed around with the m7 files big time when they went to a common msm8960 kernel. Another reason to not use my kernel on his ROM, is because he already includes a custom kernel in it....which is essentially the same kernel that you are getting here.

If it does occur on other CM based ROM's (ie all except for Bucks), then I would like a logcat of the event, and the config.gz file. Thanks.
[Verizon HTC One (M7)] santod040:
Might also ask those with said issue, to post a fastboot getvar all for you, to be certain they are using the latest firmware.

Biggest cause of no in-call audio is outdated firmware.

Not saying other stuff may not come in to play.

Just that the firmware should be verified first, so they don't have you chasing your own tail. :)
[Verizon HTC One (M7)] Rain__:
Not sure about others who have reported the issue, but I can confirm that I'm on the latest firmware/radio/ect.
[Verizon HTC One (M7)] santod040:
As long as you are sure, then that's great! :good:

Just throwing it out there.

Too often I hear what you said and after getting them to post or send their info, find they in fact were not.

This happens more then you would think...not just on this device.
[Verizon HTC One (M7)] Rain__:
Yea, I can imagine. I just figured I'd let [MENTION=4428185]brymaster5000[/MENTION] know before he (potentially) asked. :laugh:
[Verizon HTC One (M7)] buckmarble:
Stop flashing the cm based kernel on my vanilla ROM. My vanilla ROM is a totally different configuration. Use only the kernel included in the ROM. Besides, all the features bry is adding to the cm kernel are already in my included kernel. This is an official statement of incompatibility. Please do not post issues with the cm based kernel flashed on my vanilla ROM.
[Verizon HTC One (M7)] brymaster5000:
Update for CM-11 kernel. Merged in some stuff from the upstream CM repo. Nothing major, just an update to stay...well...updated. Link is in the OP.

PS - CM12 kernel is currently building.
[Verizon HTC One (M7)] aaronpw0621:
Has this been updated for Santods L-build ??
[Verizon HTC One (M7)] brymaster5000:
Yes, check the new thread for it!
[Verizon HTC One (M7)] c_raethke:
I've been away from the ROM scene for a while, so let me know if I'm missing something obvious here.

Can't seem to get this to flash; I am running santod's stock 4.4.3 rom, I install the zip through TWRP and it says "Installing Elite_Lunar_Kernel-10_04_2014-gest-stkclk.zip", goes through the process, script succeeded; I reboot and it lists the kernel (in settings and Trickster) as:

3.4.10-g6b945e7

and@ABM103 #1

SMP PREEMPT

Official

Is what I should be seeing? I don't see wake options, etc in Trickster either.
[Verizon HTC One (M7)] santod040:
Check my stock thread for the insecure kernel in post 2 I believe.

You'll need to flash that first before you can install a custom kernel.

Look for: m7vzw-5.28.605.2-InsecureKernel_w-Modules.zip
[Verizon HTC One (M7)] keith7120:
I'm using the 11/8 kernel with wake only and several weeks later as in yesterday, my phone calls all of a sudden stopped working. I'm using viper 7.0.1. The last thing I did before the phone calls stopped working (can't hear the caller, they can't hear me) was install mixcloud a music streaming app. Once I realized the calls were no longer working, I uninstalled the mix cloud app. and rebooted. That didn't fix it. I reinstalled the kernel, that didn't fix it. So I reflashed(dirty) viper 7.0.1 and my phone calls started working. I'm afraid to reinstall mix-cloud although it could have been a coincidence?
[Verizon HTC One (M7)] brymaster5000:
Yeah that's a tough one to debug. Viper uses a LOT of tweaks.... And then throwing a custom kernel and an app on top of it. My suggestion would be to take a log cat of the event if it happens again.
[Verizon HTC One (M7)] peteangi:
I was running Viper and loved it, so much customization! Then one random day I could not hear phone calls, nor could they hear me. I restored a backup, but that didn't fix it. Not sure if it is something in Viper or not, but just wanted to say it has happened to me as well. At the time I was running the kangaroo kernel. I flashed a different ROM and calls worked perfectly. I kinda miss Viper, but I have to use my phone for calls!

(sorry, this really has nothing to do with this kernel, other than to say the problem isn't specific to this kernel)
[Verizon HTC One (M7)] atsoca:
Any updates coming for 443 sense?
[Verizon HTC One (M7)] brymaster5000:
Yes. Just have to find the time. Maybe this weekend. Maybe next week.
[Verizon HTC One (M7)] keith7120:
Found the culprit. RootCloak module that I recently added is some how affecting the phone app. RootCloak is an Xposed module that I downloaded recently. All is good now that I have uninstalled. it.
[Verizon HTC One (M7)] keith7120:
I was wrong yet again. But now I have a fix. The venom team pushed out a hotfix. There was an update to Google Play services pushed out by google that caused this nasty bug. I have just applied the patch.. You have to go to Venom Hub Addons-hotfixes.
[Verizon HTC One (M7)] brymaster5000:
Finally got around to it. Updated the sense 443 kernel. Changes are:

Optimax cpu governor

Intellimm cpu governor

ZRAM toggle that works

Kexec Hardboot

LZ4 Compression

Linaro 4.9.2 arm a15 and 03 optimizations

I have only done the non-gesture version. I will update the gesture (xposed) version tomorrow. Enjoy.
[Verizon HTC One (M7)] atsoca:
Thank you sir! Looking forward to gestures
[Verizon HTC One (M7)] brymaster5000:
Shoot. Forgot to bring my laptop to work. You can give the non xposed version a try in the meantime if you want. I got sick of xposed....which is why I prefer the original gestures. I'll get to it tonight though.
[Verizon HTC One (M7)] atsoca:
No problem bud

In actually running you release now so far so good!

Any idea if ecliptic ROM will be updated? ….. Any word from hawk?
[Verizon HTC One (M7)] brymaster5000:
Not sure about Hawk.

OP Updated with xposed gestures versions. Same changelog as the non-xposed. Enjoy. I haven't tested them but they are most likely good to go.
[Verizon HTC One (M7)] atsoca:
weird things happened today....phone just shut off once this morning and just now....non responsive it took me about 1/2 to get it back on...battery did not die

im reverting back to the last kernel to see if it does it again I will report back
[Verizon HTC One (M7)] Droidcore:
I have same problem :confused:
[Verizon HTC One (M7)] brymaster5000:
Can either of you get the last_kmsg for me? It's in the /proc/last_kmsg location. Thanks and if you can tell me your settings too: cpu freq/gov, voltage, etc. that would be great.
[Verizon HTC One (M7)] atsoca:
bry will it still be there even tho i flashed back to the old kernel
[Verizon HTC One (M7)] brymaster5000:
It will, but it regenerates when you boot up i think.
[Verizon HTC One (M7)] Droidcore:
Im sorry im use agk kernel on my primary rom,

Im use multirom,

I used oc version but stock freq- stock gov -ondemand uv -25

All normal before this version:rolleyes:
[Verizon HTC One (M7)] brymaster5000:
Okay, well if/when it happens again, grab the last_kmsg. I can't debug without it. Thanks.
[Verizon HTC One (M7)] cesium:
I've got the same reboot issue. Below is a link to the the last kmsg file I pulled, hopefully it's what you need.

https://www.dropbox.com/s/cqmeew4j4yjzgpi/(Dec-31-2014)--(2h-01m-03s-PM).txt?dl=0
[Verizon HTC One (M7)] brymaster5000:
Thanks guys. I had it too and I looked over my last kmsg. I think I know what needs to be done. I'll try to have a fix out at lunch.
[Verizon HTC One (M7)] brymaster5000:
It should. The worst you can do is try...and if it doesn't work, either flash the old kernel or restore a nandroid.

You have no idea how immune you become to flashing kernels and not having them boot correctly when you are developing. As long as you don't panic and power into boot loader, your all set. Enjoy.

Sent from my Ecliptic One.
[Verizon HTC One (M7)] mikey2487:
ok thats what i figured. just haven't flashed a kernel in what seems like ages. I'm going to give it a shot and see what happens. thanks for the heads up!
[Verizon HTC One (M7)] CatInTheHat422:
Hey Buck heads up, I'm getting a suspended page for all the links on the first post. :(
[Verizon HTC One (M7)] atsoca:
This might be a good thing
[Verizon HTC One (M7)] mikey2487:
flashed and went super well. running super buttery but was wondering doubt one thing. before flashing this never happened but now when the screen is off and then double tap the screen it wakes. any ideas about that?
[Verizon HTC One (M7)] buckmarble:
Its one of the kernel features. Read the OP
[Verizon HTC One (M7)] zetsumeikuro:
Thank you sir.
[Verizon HTC One (M7)] ccarr313:
Using this kernel with ViperOne 4.3.0

<3 much love! Works wonderfully. love the tap2wake.

keep up the awesome work!
[Verizon HTC One (M7)] atsoca:
Not asking for an eta but is there something new coming around?
[Verizon HTC One (M7)] brymaster5000:
Not much more to do with this kernel unless you have suggestions...?

Sent from my Ecliptic One.
[Verizon HTC One (M7)] atsoca:
Can it get me a bacon egg and cheese with home fries on a roll with some hot sauce?...oh wait it does that already...

Just kidding...it is amazing and thank you I guess I just want something to flash hehe

Thank you again