yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] flar2:
All changes after 0.10 are development of custom wake gestures.

The kernel supports faux sound

However, it does not work with Sprint or Verizon. It works with all other variants, including the 2.5GHz Asian model.
[One (M8) Original Android Development] beats4x:
They are both set to 0. I dirty flashed the rom and everything works as it should on stock. I tried editing those two files, with r/w enabled of course, and did a reboot after. The files did not change. Thanks for your help [MENTION=4684315]flar2[/MENTION], it's much appreciated. Your kernels are on all of my devices, and quite a few family members and friends. Your work is fantastic.

Sent from my m8
[One (M8) Original Android Development] flar2:
If they are set to 0, that's why they aren't working. Make sure there is no other app trying to change those settings and that elementalx is installed properly.

Those files are "virtual" files that are repopulated every boot.

You need to reflash the kernel if you reflash the rom or you will be missing essential files, including the boot script that enables the custom gestures (among other things)
[One (M8) Original Android Development] lukes91:
hi @flar2!

i just got my dot view cover and gestures don't always work... i found that they work after i open and close the case very fast, before the screen turns on, but only for a couple of tries... if the screen turns on, they don't work anymore and i have to do the same trick as before..

i've also tried to reboot the device and the behaviour is the same...

just a report :)

p.s. on Viper rom here :)

edit: without the cover everything is fine :good:
[One (M8) Original Android Development] flar2:
Can you walk me through the exact steps to reproduce?

My dot view case is a piece of cardboard with a magnet from my fridge
[One (M8) Original Android Development] lukes91:
sure :)

well, i put the cover, then i flashed your kernel (i had .14 before and i had the same issue, if this can help)

i rebooted and everything was fine... then i tried the cover and after playing with it it stopped lighting up holes... i opened it and the screen showed up: everything was fine; but when i closed the cover gestures didn't work anymore... i opened it a little and left it go before the screen was turned on, and gestures worked fine, but only for a couple of tries (infact they work from 1 to 5 times every tim, but this number seems to be completely random)... if i do the same fast open-close trick everything is fine again for 1-5 times, but then the issue appears again..

i hope i've been clear, please ask me if you need testing/more explanations :)
[One (M8) Original Android Development] flar2:
Thanks, I will try this when I get home tonight.
[One (M8) Original Android Development] lukes91:
after some more testing, i found out that when the screen turns on and i close the cover again, screen turns off and actually after some seconds (let's say 20-30 seconds) gestures work again (randomly / i have to perform gesture more than once sometimes) but again they stop working after 1-5 tries...

in aroma installer i left the stock motion gestures...

hope those infos can help you :)
[One (M8) Original Android Development] flar2:
Let me ask you another question:

Do you have pocket detection enabled or disabled? And if you leave the cover open, and do the gestures on the screen, is the pocket detection working right away, or does it take 5 to 10 seconds to start working?

If so, it could be the same problem as a couple others, the sensors are not being initialized properly at boot. I am trying to find a solution to make it work on every configuration.
[One (M8) Original Android Development] lukes91:
it was 0, and even dt2w and haptic feedback were 0... now i set them to 1/1/20 and i'm rebooting... i'll tell you if this fixes...

edit: this way it's better, dt2w work almost 50 % of the times... pocket protection is fine... now i'll try to revert dt2w to 0 and check if other gestures work... give me a moment...

edit 2: the other gestures work again both with and without cover, but this way o have the same issue i had before...

edit 3: (always with cover, without everything is fine) when dt2w stops working after mostly 5 times, if i swipe down and activate voice control gesture, then dt2w gesture works again for about 5 times; if dt2w doesn't work since first try, then swipe down doesn't fix the issue... need other infos?
[One (M8) Original Android Development] flar2:
So, even with dt2w set to 0, doubletap still works sometimes with the cover on?

If so, I think there me be some conflicts between the stock gestures and the custom gestures. This is helpful, I;ll test when I get home and might have more questions then.
[One (M8) Original Android Development] lukes91:
yes, right, it works for the first few tries..

my gestures in venom tweaks are all set to default, if this can help...
[One (M8) Original Android Development] BadAzDB:
How's the battery life on this Kernel. My battery hasn't been the best lately and I'm thinking about flashing this
[One (M8) Original Android Development] Snah001:
@flar2

Again the 3rd (4th actually) core got stuck at max freq using hangouts.

Attached the Kmsg and logcat I saved with Viper bug report.

Let me know if you can find something that point to what goes wrong.

https://drive.google.com/file/d/0B4tNrq8mGo0yRW5CY0RMMGp4T2M/edit?usp=sharing

https://drive.google.com/file/d/0B4tNrq8mGo0ybkU3RjctbzRweE0/edit?usp=sharing
[One (M8) Original Android Development] guyd:
I have seen some mentions that Hangouts might be one possible cause of this happening. I've removed Hangouts from my device

long

ago, and I've never seen the Cores "freak out" or get stuck at a high frequency. I can't say for sure that what it is, but I can say that I've not experienced this problem.

---------- Post added at 01:11 PM ---------- Previous post was at 01:08 PM ----------

That's why I think that an app has gone rouge for the people that experience this. I've seen Hangouts mentioned a few times as a possibility.
[One (M8) Original Android Development] itzsnookums:
I ended up doing a full wipe, no cores freaking out, but I'm running at 2.3 and interactive
[One (M8) Original Android Development] guyd:
+1

Nice work flar!
[One (M8) Original Android Development] martinnr:
New on Kernel stuff

Dear fellows

I just flashed this kernel in my phone, I have it for less than a day and first thing I notice is that the battery is lasting longer than before. This is the first time I change the kernel, I always use only stock kernels that comes with ARHD.

Actually I would like to get more juice from this kernel so I will gently ask you guys how I can get more from this kernel? some tips or advises around?

Im running ARHD 5.0, S-OFF, SCID and ElementalX 0.10 (installed with default options)

Thks in advance
[One (M8) Original Android Development] kfasheldon:
.. Same I have been experiencing with stock from .13, dotview gesture seem to die , takes 20 secs plus to live again and seem less responsive, using .15 with option for no motion and been OK all day except slow to respond to dotview double taps .. Takes a few taps, also case open screen on does not work after boot for some while
[One (M8) Original Android Development] Forsaked:
Vodafone DE M8 with PVS 11 here.
[One (M8) Original Android Development] Freak07:
M8 with pvs 14 here.

I was on renovate and when I attempted to boot after installing kernel 0.4 with stock frequency, stock voltage and all three options checked my phone did not pass to the boot animation... It would simply go to a black screen after the splash screen. Tried to reflash the rom but it reboot while the actual flashing process in aroma, both with and without full wipe. That resulted in the exact same behaviour as described above. Only a full wipe and installing the virtous rom brought it back to boot. But then I did not have WiFi at all. So I wiped everything again and installed renovate and it booted ok. Installed kernel 0.4 with -20 uv, and s2s + fastcharge. Now everything is back working so far.

WiFi and external 64gb exfat sd works. Thanks!! [MENTION=4684315]flar2[/MENTION] do you know what happenend to me or have an idea?
[One (M8) Original Android Development] Jarheadflip:
How can i find pvs bin on my phone sorry for the stupid question still learning
[One (M8) Original Android Development] Freak07:
-Your PVS bin can be found by looking in /data/local/tmp/elementalx.log

or by typing this in terminal: cat /sys/module/clock_krait_8974/parameters/pvs_number
[One (M8) Original Android Development] Jarheadflip:
Thank you
[One (M8) Original Android Development] dark2099:
Just going to throw this out there, first time I flashed 0.4, no wifi working, but did undervolt by 20mV, and didn't wipe cache/dalvik after flashing, this time around, flashed with out undervolting, wiped cache/dalvik after, and wifi worked. Going to guess maybe more a undervolting issue than wiping cache/dalvik, but figured I post what worked.
[One (M8) Original Android Development] digitaldazz:
PVS 12 Vodafone UK M8.

Did a full wipe now wifi working, went off whilst restoring apps and rebooted twice to get it back on ?

ARHD 3.4
[One (M8) Original Android Development] flar2:
This device is going to be a huge headache for development. Everything has to line up perfectly to work.

You need the crypto modules for paid apps, a symbolic link fro wlan.ko to pronto/pronto_wlan.ko for WiFi and the closed source texfat driver for exfat support.

HTC does not provide the source code for the Wi-Fi driver, the exfat driver, nor the moc_crypto modules. I also cannot get my compiled dtb image to boot. I have to pull it from the stock kernel. It must be signed or something.
[One (M8) Original Android Development] djkinetic:
That doesnt sound like fun.
[One (M8) Original Android Development] guyd:
I have confidence in your work flar!
[One (M8) Original Android Development] navalynt:
You have been doing an excellent job my friend. It might take some time but when you get it perfected the feeling of accomplishment will be worth the effort!

Besides, if it were easy would it be nearly as fun? :)
[One (M8) Original Android Development] HolyAngel:
As v1rk said your kernel's are working perfectly on SD GPE and SD Rogers and Dev edition.. Haven't tested international or at&t ROM yet but so far so good man, you're doing great!
[One (M8) Original Android Development] flar2:
The kernel is working perfectly for me too. I'm not sure why some people are having trouble, other than the complexity of everything. I guess what I'm saying is, there are too many things that can go wrong on this phone and it's going to be difficult to get keep track of all these things as time goes on. Just wait till we have several bases floating around with incompatibilities. Right now we're just lucky that the source HTC has released actually works on the latest base. I suspect that won't be the case for long. Hopefully HTC will prove me wrong.

The other possibility is the recoveries are still a little buggy, a couple times the installation just stopped for me. Perhaps something is not getting copied over correctly. I would suggest trying to reinstall if it doesn't work the first time.

******************************************

Does anyone have any idea how to fix the dtb images that are generated when you build the kernel? I've tried everything I know, and they will not boot for me (I use the dtb image extracted from the stock boot.img and it works). I wonder if they are signed or something? I've looked through the binaries and can't see anything, and I've even tried grafting the stock dtb with the ones I compiled, no dice. It just goes straight to fastboot.
[One (M8) Original Android Development] flar2:
I installed the kernel on Stock Sense, Viper, ARHD and Stock GPE - all 100% working
[One (M8) Original Android Development] topjohnwu:
Hello flar, the kernel is quite great and s2w is marvelous.

The little problem is that every time I swipe from right to left to turn off the screen, recent apps will open and it's quite annoying. Is this normal??

Tnx a lot!!!
[One (M8) Original Android Development] navalynt:
I tried again myself, and this time it worked. The only difference was that this time I manually wiped Cache and Dalvik-Cache before rebooting.
[One (M8) Original Android Development] flar2:
That doesn't happen for me. Even if I have an app open, when I turn the screen back on, the app is still open (ie, the home and back buttons were not activated)
[One (M8) Original Android Development] topjohnwu:
I found the trick: I can't start from the recent app button. I have to start from the left corner of the recent app button :)
[One (M8) Original Android Development] HolyAngel:
Or try starting from the end of the navbar(empty space on the right of the recent key) works perfectly for me that way.
[One (M8) Original Android Development] nunyabiziz:
Is USB fastcharge the same as this new HTC quick charge? If it is then it isn't working on the Sense kernel
[One (M8) Original Android Development] shawn0223:
I've been having a lot battery drain the past couple days, everyday it shows kernel being the highest drain, can someone tell what's up that. I attached a screenshot. Under clocked to 1.7 and under volted 45

edit: forgot to mention im on v.10 GPE version.
[One (M8) Original Android Development] guyd:
If your new to custom kernels and tweaking the options, I would recommend you install it will all the default options. It's optimized nicely for the average user.
[One (M8) Original Android Development] martinnr:
Yeh, thks for your answer! so far it seems its quite stable and pretty well optimized, I was just wondering if there are mods or apps designed to take advantage of such excellent kernel.

One thing I notice is as soon I flashed and booted, is the fact that a few apps appear to be not working with a weird message stating "this app is not installed", think is they were fully functional apps before I flash the Kernel. One of those were XDA App. When I tried to install again a error message poped up. Finally I un-mount the External SD card and re-install them with no prob.
[One (M8) Original Android Development] Shebee:
Yeah, I had that too, I just restarted and it worked again, many had the same problem when updating to 4.4 on galaxy devices.
[One (M8) Original Android Development] martinnr:
I see, mine is HTC so there is another brand/model with the same issue, good thing it´s not some critical ****.
[One (M8) Original Android Development] waz675:
V. 14 sleeps like a baby for me. 6 hours sleep it still displayed 100% and now 99% an hour after I first used the phone for a tiny bit in the morning.
[One (M8) Original Android Development] itzsnookums:
The standby time is perfect its when you turn the screen on the battery goes all the hell.....
[One (M8) Original Android Development] flar2:
I have a dot view case to test with (temporarily at least, I'm going to return it in a couple days, it doesn't fit properly with my tempered glass screen protector)

Are you sure you don't have high performance mode enabled?

Another combo that might use more battery is simple_ondemand + gboost.
[One (M8) Original Android Development] Venomtester:
I too was having battery drain issues. I knew it wasn't the kernel so I figured that it would be in the flashing. I used recovery switcher to flash twrp again, installed elemental and wiped caches. Rapid battery drain is no longer an issue. Something you guys may want to try to see if it will fix your problem too.
[One (M8) Original Android Development] aamitabh28:
I have this problem also. It is very weird..
[One (M8) Original Android Development] jlevy73:
My kernel usage is at 4.4%. Try rebooting your device.
[One (M8) Original Android Development] aamitabh28:
Have tried rebooting,wiping cache and dalvik cache,dirty flashing rom and kernel again.

On viper 1.6
[One (M8) Original Android Development] Johnny424:
The culprit for me whenever I do have a rando day of crap battery is Google services. Kinda like no matter how much Google related stuff you disable it will still do it's thing from time to time, stand by for me with this kernel is usually less then 1% an hour .. I'm happy with that..
[One (M8) Original Android Development] waz675:
Yeah, I installed the google services apk 'that appeared' the other day, on the weekend IIRC, and my abnormal drain so far appears to be gone.

Time will tell of course.

---------- Post added at 02:40 PM ---------- Previous post was at 02:32 PM ----------

As flar and others mentioned, you might need to look at your phone setup, either software and/or apps. Roughly 1%/hour with me listening to music for a couple of hours since I got home.

I haven't used my phone as much as usual seeing as I was on my motorbike for half of my awake time but the usage for the screen time plus music with the screen off is getting almost as good as I had the my G2. It's typically at, 7 hours SOT for the G2 but this phone seems infinitely smoother and quicker even though the G2 was not shabby at all!

Edit, forgot my screenshot from a minute ago!
[One (M8) Original Android Development] waz675:
Latest Google services http://www.tusfiles.net/vo0i46z0lrbb
[One (M8) Original Android Development] Hedi86:
A Question :

What is the ''best'' maximum vCore vor the M8 ? i am at 990mv @ 2.5GHz

i want get more GHz, but don't know what is a good vCore :)

thx ;)
[One (M8) Original Android Development] steve1996:
My m8 is running very stable at these voltages
[One (M8) Original Android Development] Hedi86:
Not stable is the question, the question is, what is the maximum voltage.

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Original Android Development] -juanito-:
Can you post pic for all voltages ?
[One (M8) Original Android Development] starbase64:
Hi,

my cpu is pvs 1 and not stable at this voltage table, max is -25mV.

regards

starbase64
[One (M8) Original Android Development] Galaxysm:
I got a question...would this kernel work with venom Rom?
[One (M8) Original Android Development] dukat0s:
Yes ofc
[One (M8) Original Android Development] flar2:
I have to look it up to know for exactly, but I think I set the limit to 1200 or 1250.
[One (M8) Original Android Development] Snah001:
@ flar2.

Did you find some time to look at my logs?

Sent from my Asus Infinity TF700 with Dock
[One (M8) Original Android Development] CrazyCypher:
flashed 0.15 but swipe left/right doesnt change if I change it in Toolbox. I selected "open app messages" when swipe, but I still get the blinkfeed :/
[One (M8) Original Android Development] flar2:
Just quickly, but did not see anything that stood out. Are you using stock frequencies, or over/under clocking?

That's a toobox/ROM issue. If the gesture causes any action at all, the kernel has done its part.

This is what the kernel does:

-sets the touchscreen to respond to touches during sleep

-recognizes gestures

-sends a message to the system, telling it what gesture was performed

After this, it's up to userspace what happens next.
[One (M8) Original Android Development] hasan_abeer:
@ mr flar2

Hi sir I hope that you help finding a solution for call recording feature..because disoration sound problem in all call recorder app in the market....especially when the other party of a certain call is loud....Mr skvalex try to find a solution but not succeeded...he didn't find a way to update the audio sorce ....I advised to contact him in order to share development information and. We will. Find a solution so.....I'm sorry for my bad English language writing.....rgrds sir.

Note in skvalex thread(About distortion on LG Nexus 5, HTC One (M8), SGS4 and other qualcomm based devices: http://xdaforums.com/showthread.php?p=51845810

)

At this post http://xdaforums.com/showpost.php?p=51845810&postcount=3252
[One (M8) Original Android Development] tiho5:
I just flashed ver 0.15 on Viper 1.6.0

Used Mode 2 and Mode 3 + pocket detection enabled in both cases

For mode 3 I have the same result as before on ver 0.14:

A. Some gestures not selected:

* Although I didn't select some of the gestures in Aroma (swipe down, left and right) they all still work on the second or third swipe

* After unlocking the phone by any gesture (double tap or swipe up), proximity on calls doesn't work for the first few calls. Then it is ok.

* vol buttons launch camera was selected, but didn't work

B. All gestures selected:

* After unlocking the phone by any gesture, proximity on calls doesn't work for the first few calls. Then it is ok.

* vol buttons launch camera was selected, but worked in may be 1 out of 10 times

For mode 2 I had this behavior:

A. Some gestures not selected:

* Although I didn't select some of the gestures in Aroma (swipe down, left and right) they still work on the second or third swipe

* Proximity on calls was working every time only when I used swipe up gesture to unlock. All the other gestures (double tap which was checked and swipe down, swipe left and swipe right which weren’t checked) resulted in proximity on calls not working for the first few calls

B. All gestures selected:

* Proximity on calls was working better now: every time when I used swipe up, swipe left and swipe right gestures to unlock. Using double tap and swipe down in most times resulted in proximity on calls not working for the first few calls.

So selecting all gestures is better.

All Gestures are set to default in Venom Tweaks and tried tuning them on/off in system settings (for mode 3), but no change.

I am sorry that my feedback isn’t positive, but I can't report much improved behavior at this stage. I hope that further testing will eventually nail this. I don’t know if there’s something that I am doing wrong and if there’s any advice it will be appreciated. It took me a lot of time to test and carefully describe everything so that it can hopefully be useful.
[One (M8) Original Android Development] donmarkoni:
[MENTION=2676284]tiho5[/MENTION]

tl;dr ;)

J/K, but you know that. Thanks for testing. :)
[One (M8) Original Android Development] Snah001:
I don't UC or OC and use only stock frequencies.

But I did some testing with hangouts on my Asus Tf700 tablet and there it did the same. At least 1 core get stuck at max frequency.

So it is probably hangouts causing it.

Sent from my Asus Infinity TF700 with Dock
[One (M8) Original Android Development] flar2:
Where the unselected gestures work on the second or third try is actually registering as a double tap. I'll just make doubletap a little more restrictive.

I think the other stuff is related to startup. If I can find a way for all of this to be initialized in the correct order it will work for everyone (as everything is working 100% for me)

Please try this and report back: reboot your phone, when it comes back on, start using it right away, so the screen doesn't go off. Keep the screen on until it's fully booted ( give it a couple minutes). Then turn off the screen and turn it back on again. See if everything works after that.

Next reboot, try leaving the phone alone for a few minutes till fully booted and then try everything out. See if this works.

I can get mine to "not work" by turning the screen off and on right after the homescreen first appears.
[One (M8) Original Android Development] tiho5:
That could be the case, yes. Pretty good conclusion.

It will have to be next occasion I have free time because:

A. I'm too low on time usually

B. I would risk that [MENTION=2977387]donmarkoni[/MENTION] will joke with me again if I make 2 posts as long as my other one

Sorry, I am very tired. You mean right after boot?
[One (M8) Original Android Development] flar2:
Yea right after boot.

You don't have to make detailed posts, just whether it works or not. If it's working, it will work perfectly, otherwise it's not working.
[One (M8) Original Android Development] tiho5:
I guess it'll be OK if I test one scenario only - the one I'd like to use - mode 3.

I tested the others as I felt it would be a bit selfish to post "here's what I wanted and it wasn't working for me". So decided to get more information here, which resulted in more text to be written
[One (M8) Original Android Development] flar2:
And thank you for taking the time to do that :)