yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] carlos67:
I reckon this kernel is stable enough to come out of beta. I'm loving using it. It's by far the best version so far. Don't think it can be improved.

It's just supersmooth with very good battery life. Very few kernels manage that double feat.

Flar, your a genius man.

Edit: only minor issue I'm having is sometimes (not always), after hanging up a call the screen dims down by itself. I usually have it set to level 3 but it dims down to level 1 and has to be put back to 3. Kernel or Viper Rom bug, I dunno???
[One (M7) Original Android Development] Sneakyghost:
It's not just a feeling. My phone never gets as hot as with navigation unless I run a complete stock system where it's continuously too warm.

Navigation lets the lower part become so hot I can barely touch it anymore. It's better during winter though I'd guess (this phone hasn't seen a winter yet lol). :D

Mobile post
[One (M7) Original Android Development] bldysurgeon:
hi .i use your twin kernels alternativly on my htc one and in more than one occasion i recomended them for htc viper one rom.they are both exelent,,,, now can i know the change log or the update of the beta vergins to start testing both of them one at the time?

thnx
[One (M7) Original Android Development] bfdream:
Hi, I want to report some problems using 3.2 beta:

1. My touch screen suddenly stopped response this morning, I can only reboot to fix it. But I cannot repeat that.

2. I set no vibration in Aroma, but sometimes when I sweep2sleep, I can feel vibration. This happens randomly, but several times.

My kernel is set no OC, no UV, GPU OC, sweep2wake, logo2menu, pocket detection, restore 3-dot menu.
[One (M7) Original Android Development] Smoothface:
Yeah the heavy use of radios both cellular and GPS really make the phone warm up. Other than that the phone will stay at decent temperatures.
[One (M7) Original Android Development] flar2:
RE: hot phone while navigating

I think it's just because of a) the gps radio + mobile data + the nav application and b) the default thermal settings of the kernel allow it to get hotter than the stock thermal.

1. That was probably random

2. The vibration is the button press vibration, sometimes one of the buttons registers and it vibrates.
[One (M7) Original Android Development] popokrew:
[MENTION=4684315]flar2[/MENTION] any thoughts on this? Posted in the viper thread but they think it's kernel related.
[One (M7) Original Android Development] flar2:
I changed the sweep2wake logic quite a bit. Now most of the time it won't go to the home screen when you sweep to sleep, your last app will still be open. This depends on how fast you sweep. If you sweep slowly, the home button will still register, and when you wake the phone again, your homescreen will be showing.

I made doubletap2wake a wee bit easier to activate.

The ondemand governor was broken, you guys are sharp for catching that.

There is now an option for the simple GPU governor in Aroma and I added the command to start install-recovery.sh to the ramdisk.

Download:

ElementalX-m7-3.3

Changes:

-sweep2wake fixes

-doubletap2wake fixes

-ondemand GPU governor fixed

-Makefile optimizations

-install-recovery.sh command added to ramdisk

-simple GPU governor installer option
[One (M7) Original Android Development] flar2:
I don't think it's kernel related. I've never experienced this problem myself, and if I'm not mistaken, I've seen this problem mentioned in various ROM threads quite a bit. Maybe something to do with firmware, I don't know.
[One (M7) Original Android Development] popokrew:
What else can I do to troubleshoot this besides a wipe?
[One (M7) Original Android Development] flar2:
Find a way to replicate it consistently, then try it with the stock kernel.
[One (M7) Original Android Development] MrKudinGTO:
Hah, I knew something's really fishy about the ondemand governor. Though I did a reboot after choosing it, clock speed still stuck at 200mHz. :rolleyes: But, oh well, let see how it goes on v3.3. Hehe. :p

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] baadnewz:
I see, anyway during install i selected run cool for cpu throttling .
[One (M7) Original Android Development] cee43ja1:
Great. A new one to flash. :p

I was calibrating the battery since I felt that it wasn't reading properly, but with all the updates being posted, looks like it has to wait a bit. 2 hours screen-on, 13h 35m on battery. On 3.2, intellidemand/fiops/broken ondemand GPU, 1.2ghz max.
[One (M7) Original Android Development] bfdream:
I think I have disabled all vibration. Could you please show me which button is registered and vibrates? I am a little confused.
[One (M7) Original Android Development] sensationfan623:
[MENTION=4684315]flar2[/MENTION] hey I have one quick question: In your 2.4 kernel I can't use my car charger to its full potential. It thinks I'm using a 1.1 volt charger or something. On the HTC stock kernel it uses the advertised 2.1v. Is that in your new beta kernel?
[One (M7) Original Android Development] threetwentyfizzle:
On demand GPU working golden, the scaling isnt as aggresive and kernel is running just as smooth. Liking the s2w fix, sweeping to sleep bugged a bit in the past I'm glad it doesnt revert to my homescreen as I'm swiping. Thanks Flar!
[One (M7) Original Android Development] evo9mrjr:
Any tips on the gpu sticking to200mhz on how to get it back to 450
[One (M7) Original Android Development] zboq:
Hey flar2, I have noticed that simple gpu governor causes freq to jump between 320 and 450 while actually doing nothing. I was just looking how it works in trickster mod and noticed that. I think it wasn't doing it in 3.2 but I will flash it back and check that later.

Wysłane z mojego HTC One
[One (M7) Original Android Development] evilmastr:
Happy to report that 3.2 is yet another great version :)

T9'd from my black HTC One M7
[One (M7) Original Android Development] Unoath:
New version 3.3 is running awesome so far. Still doing some tweaking here and there and its still running golden! Great work flar2 :)
[One (M7) Original Android Development] snake4fun:
Hi,

is it possible to share your twaeks here?
[One (M7) Original Android Development] Unoath:
Yeah sure. Right now I am using Trickster MOD and liking my Screen off Max set to 702000. With CPU Governor set to ondemand.with my GPU on Simple. I am still trying some things within those settings to see what works best.
[One (M7) Original Android Development] aamitabh28:
Version 3.3 working great so far !

3.1 had awesome battery life .. will check 3.3 and report back

Thanks !!
[One (M7) Original Android Development] MrCupra:
3.3 is running great.

Keep up the good work :good:
[One (M7) Original Android Development] gianton:
With intellidemand/mpdecision on only 2 freqs used the min and max. Back to ondemand/mpdecision on where 4 freqs used.

3.3 working great with viperone Rom, thanks flar2!
[One (M7) Original Android Development] semool:
GPU ondemand working great again with 3.3 :)

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] Huubs:
I'm satisfied :D

Version 2.4, no personal tweaks. Rom is insertcoin 3.0-7.
[One (M7) Original Android Development] erto90:
64h? WTH:eek:

All left at defalt in kernel?
[One (M7) Original Android Development] flar2:
How's the new sweep2wake working?
[One (M7) Original Android Development] Pointlol:
I thought it was great as it was already, but yeah the addition of preventing the home button being pressed is pretty neat, works fine. Thanks!
[One (M7) Original Android Development] evilmastr:
So far, so good! Never seen the home screen pop up :)

T9'd from my black HTC One M7
[One (M7) Original Android Development] B-Man2005:
elemental beta still has i little stuttering issue ... hard to see but its there :(

flar could you make a performance edition ?

same as bulletproof kernel scheduler settings but with enhenced l2 cache freq and overclocking ??

thanks
[One (M7) Original Android Development] tiho5:
No such thing here. Can you post your settings. CPU/GPU Governor etc. Or you are on default settings?
[One (M7) Original Android Development] ttocs99:
I think the new beta is workin like a treat upto now no issues so far even with max screen off :thumbup:
[One (M7) Original Android Development] kazemitsui:
its working better than that one version 3.1 or whatever, the new implementation of no home button didnt really affect me since i use the LongHTC2sleep

Im sure its cause i flashed it 3 times or what not over the course of 2 hrs. but my battery life went from 3pm to 7pm (65%-0) on wifi auto sync on

barely used my phone since it was work hours...

but just saying i was like dafuq haha 65% gone in 4hrs... with no usage. this one the first time. but like i said its probably cause i flashed it 3 times in 2hrs to see the difference between simple and ondemand for gpu.

hopefully the next charge is better!
[One (M7) Original Android Development] PantsOnFire:
Sweep2wake is working like a charm in latest beta.

Have an different, odd bug with the keyboard typing sounds, however. Not sure if this is a known bug or ongoing issue, but the audio for the keyboard clicks gets progressively louder as I type. The first few letters I type will be silent, and then it will get progressively louder until it actually exceeds the volume levels I have set in the keyboard settings. I prefer to have a barely audible click, just enough that I can hear it but not loud enough that others are disturbed or even notice it.
[One (M7) Original Android Development] tiho5:
Thanks for the support!

I cleaned my build.prop of all # Softkeybar

qemu.hw.mainkeys records and it seems better.

But I still have this "system isn't responding" at the end of some of the reboots.

After some time of observation, I think this happens when you set higher CPU in the Aroma installer.

The higher I set CPU, the more this tends to happen. I don't know if I'm right, but this sure seems so. Something with this and Viper may be? Because I see that some people are running their phones normally OC'ed at more than 2000 Mhz.

Also when the CPU in Aroma is set to more than 2052Mhz, app drawer and home are missing some shortcut icons or some of the widgets are not there after boot. They're simply not loaded. So to fix this I go to Venom Tweaks and tap fix widgets in Advanced tab.

I'm at 1994 Mhz in venom tweaks, but the CPU runs at the value set in the Aroma installer before the system is completely loaded and the scripts run. So some errors happen may be :)

You've done some tricky thing here I guess. :)

It works better, but double tap on home button would often lock the phone. I guess this has to do with the S2sleep changes may be. Does anybody have the same happen?
[One (M7) Original Android Development] B-Man2005:
standard settings

its really hard to see for someone not looking for something like that ... but i see things like that
[One (M7) Original Android Development] flar2:
I still don't know why you're getting that system not responding thing. If it ever happens to me I'll try to get some logs. It doesn't have to do with the kernel or cpu frequency though, it's something to do with system settings.

Regarding sweep2wake: Yes, if you can manage to doubletap the home button super fast it will sleep the phone. I set it by default so it's very unlikely to do that. You must be faster than me, by default, if the home button is pressed for about 0.0024 seconds or less, it's considered a possible sweep2sleep event.

There is a setting that you can adjust for this: /sys/android_touch/button_timeout

Setting it to 0 disables this feature, max is 15, and the default is 6.

Higher values are less likely to register a home press when you sweep2sleep, but more likely to mistake a home doubletap as sweep2sleep.

Lower values are more likely to register a home press when you sweep2sleep, but less likely to mistake a doubletap of home as sweep2sleep.
[One (M7) Original Android Development] Johnny424:
All good here..with simple governor everything seems very smooth. Thank you sir :D
[One (M7) Original Android Development] los318:
Same here. Stock settings, GPU 450 and Simple Gov, no sweep actions enabled. Smooth.
[One (M7) Original Android Development] arhung:
Can anyone share settings with on-demand gov. or any settings with fauxclock? thx
[One (M7) Original Android Development] jlevy73:
Very smooth [MENTION=4684315]flar2[/MENTION] not one ounce of micro-stutter ever. I like the new S2W, very responsive. Great kernel!
[One (M7) Original Android Development] SleemLDJ:
Use this. Works wonders for me.
[One (M7) Original Android Development] arhung:
Great! Gonna have a try
[One (M7) Original Android Development] los318:
[MENTION=4684315]flar2[/MENTION] I'm not sure exactly what happened but wow. My phone is way super smooth on 3.3. Thanks!!
[One (M7) Original Android Development] Batskoning:
This is my battery time with this kernel :)

I have no stats because BBS set it to last boot because of flashen the 3.2 update :)

Things that i did in these 33 hours with my phone:

*Viber calling (30 min.)

*Checking news+Facebook on Blinkfeed and FB app (couple of times)

*Reading the news on a newsapp (nu.nl)

*Most of the time whatsapp

*Ah i also watched a few youtube clips with my dad yesterday evening

*Euhmm, Flashing the ElementalX update..

Good Job Mike :)
[One (M7) Original Android Development] killman2659:
After reading all these comments about how fast this makes the device, i flashed ARHD GE 2.0 and then ElementalX 3.3. I'll make it simple and to the point, my phone has never been this fast. ;)
[One (M7) Original Android Development] ihamid:
I have been trying to install your kernal on viper 1.2.1. After the setting selection when installation starts the phone restarts before installation completes. Having the same issue even when installing bullet proof. Any idea what the issue may be?
[One (M7) Original Android Development] Giblet-dono:
not viper ;)

Running it on viper right now..

What recovery are you using?

I installed using teh ;latest twrp 2.6.0.1 whihc works perfectly, maybe thats the problem
[One (M7) Original Android Development] PantsOnFire:
Flashed 3.3 beta today and it seems to have fixed this issue. Super smooth to boot.
[One (M7) Original Android Development] BBs19:
Lastest Beta really works amazing :) Everything is running extremely smooth..

Let's see how the battery is with this new beta. With v2.4 i had overheat problems and bad battery life compared to stock kernel and all that even though i used stock clocks for cpu/gpu and extra cool thermal throttling.(Tested using 2 different roms.)
[One (M7) Original Android Development] bpdev:
When thermal throttling occurs what does it downclock the cpu/gpu too?
[One (M7) Original Android Development] carlos67:
Iv'e installed lots of kernels in my time for different devices. Some from great developers like Hacre, Hardcore, Andreilux (perseus kernel), Gokhanmoral (Siyah kernel) etc etc. I have never before seen such a happy, contented user base as with this ElementalX 3.2 or 3.3. I'm nobodies fanboy, but I've gotta say, this kernel is the dogs bollocks.

Best kernel I've ever used in 3 years! Great attentive, active developer also.

I'm off before I get even more carried away with myself :o

p.s. to anyone pondering installing this kernel. DO IT!!!!!
[One (M7) Original Android Development] erto90:
Someone can tell me if sweep2wake drain battery on newer versions?
[One (M7) Original Android Development] tyraelasd:
Hi Hi,

I'm installing ElementalX and it's been like 5 minutes on the aroma installer on 0% trying to install it, pretty strange. I'm a little afraid of doing something, like pressing power+ volume down. Anyone knows what to do??
[One (M7) Original Android Development] mcrane1981:
Just gone back to 3.2 as I was having the issue with 3.3 where wifi keeps saying it's turning on without actually activating! I thought this was eradicated since 4.1.2?
[One (M7) Original Android Development] skulldreamz:
If it hasn't started installing anything you can just hold down power till it reboots. That's happened to me n I felt like you but I just held down power till it rebooted...
[One (M7) Original Android Development] cee43ja1:
Is there a way to make the settings stick? I have it set to 0, but after a reboot it goes back to 6.
[One (M7) Original Android Development] tyraelasd:
Yes just did that before I came back to xda. Thanks for your help anyway.
[One (M7) Original Android Development] djbenny1:
i am also having real difficulty installing this

every time i finally get to the "install" stage, it simply gets to either 0% or 10% then reboots without installing.

i've tried TWRP, CWM and CWM touch recoveries and its the same for all.

any ideas?

also ive tried sideloading and installing from sdcard but both have same result
[One (M7) Original Android Development] flar2:
For install problems, try wiping cache first. Or reboot to bootloader and type "fastboot erase cache"

If it still fails, send me a copy of /tmp/recovery.log
[One (M7) Original Android Development] djbenny1:
just tried both of those and still exactly the same :s

will send you through reovery.log now!
[One (M7) Original Android Development] WTFunk:
Hey flar, I'm a fan of your kernels.

I just had a screenshot taken while wiping the screen with my shirt. It also happened again while double tapping the home button as I type. I'm leaving a link to a log in case there's anything to fix. I'm running trickdroid 8.0. on elemental 3.3. D2W and S2W enabled. Anything else you need let me know.

The D2W is a little too sensitive as mentioned previously. I find myself shutting the screen off while trying to go into recents.

Thanks again for all the work put in.

http://db.tt/S1IOtYoQ
[One (M7) Original Android Development] tyraelasd:
Well I just installed it again after the 0% thing. Didn't erase cache this time and it worked, pay attention to the ElementalX logo that should show up before the aroma installer goes on, that's gonna tell you you're right, well at least when it appeared it worked :) . Try to keep everything as stock as possible on aroma installer as well.
[One (M7) Original Android Development] djbenny1:
glad you got it to work but im having no luck here at all

im basically just spamming the installer now hoping that one slips through.

i've tried completely stock settings and changing loads of stuff but it's always the same... either 0% or 10% then reboot.
[One (M7) Original Android Development] tyraelasd:
Tried re-downloading the kernel zip? Sounds kinda basic I reckon but it could be that.

Are you trying with beta 3.3?
[One (M7) Original Android Development] djbenny1:
just redownloaded and tried again, still the same lol.

yea, beta

meh i give up for the night

hopefully flar2 can figure it out from my recovery log and ill get it working tomorrow
[One (M7) Original Android Development] cee43ja1:
Try reflashing your recovery. CWM Touch 6.0.3.2 always worked for me, although I have not updated to 2.17/2.24 firmware, and I don't plan to.
[One (M7) Original Android Development] Luisit0:
[MENTION=4684315]flar2[/MENTION]

The only issue I am having with this kernel (as mentioned on the last page right now on the bulletproof thread, since I had it with bulletproof too) is with the proximity sensor. Right now I'm on 2.24.401.1 firmware and running the stock rooted 2.24.401.1 Rom with elementalx 3.2 kernel, the one with fixed simple gov. My issue is, when I'm in a call, the sensor works fine as long as I'm always on a bright, illuminated room. As soon as I enter a room with not as much but still very visible light conditions, the sensor starts acting up. What I mean by acting up is, the sensor seems to recognize this change in light as the action of me putting the phone to my ear and turns off the screen. Sometimes it comes back on, sometimes I just have to walk up to a more illuminated room or put it under a light bulb so the screen will come on. It's kind of painful cause it also happens at night... ie. Say I get a call and go outside to talk, I get a message and want to check it, I move the phone away from my ear, but the screen stays off and won't come on no matter how many times I press the power button... This has actually happened pretty often, today a couple of minutes ago it just happened (that's why I remembered to post about it). But, as I said, as long as I'm on a bright room with good light, it's perfect. If I walk into a room with the light conditions of maybe an indoor office or a basement (where it's a bit dark but still illuminated enough to see well), or go outside when it's night with the moon shining down, it acts up and turns off the screen and doesn't turn it back on 'till it's solely under a bright light. Other than that, this kernel is an effin beast!!
[One (M7) Original Android Development] wmg316:
Have you tried to see if you get the problem with other kernels? Stock? TeaMSeven's? The reason I ask is because I had almost the same exact issue you were having on my Dev Edition One. I too thought it was the kernel, but it happened on all kernels I tried (proximity sensor going haywire during calls moving between different lighted areas causing screen to go dark). It also happened on all ROMs I tried...even stock RUU. I was unable to determine the cause and got so frustrated I went and bought the AT&T variant of the One and haven't had that issue at all! Long story short...HTC now has my Dev Edition for warranty repair since my 30 day return policy was up with Lets Talk where I purchased it.
[One (M7) Original Android Development] flar2:
I've tried to make this happen and can't.

Perhaps it's a firmware issue? I have the original firmware. Is there any advantage to flashing the new firmware?

Or is it something to do with the 2.24 ROM? I'm still using Viper, based on 2.19.

Has HTC changed the sensor hardware?

Have you tried this with tbalden's kernel?

What I would need to understand the problem is logcat and dmesg output when this happens. Not sure if it would be possible to fix though.
[One (M7) Original Android Development] Luisit0:
Well the only benefit for me on the new firmware is the added sensitivity of the capacitive keys, which I strongly needed since it was hard to make a long press as it would almost always read it as a short press. It happened originally on Viper, and I thought it was cause of the proximity fix tweak but it also happened with the tweak turned off. So I decided to try stock and, well, it's happening. As far as I know there was indeed a new proximity sensor update along with the 2.24.401.1 firmware, and on stock kernel it works flawlessly even on a dark room. I have not tried tbalden's kernel as I always found elementalx and bulletproof much better with battery life, but I guess I'll give em a try aswell and let u know the results. Finally, if u need a logcat I can download aLogcat and get u one. How would I have to do it? Start running the logcat, try and replicate the issue and then stop it, save it and post it here?

EDIT: One last thing, this does not happen always as sometimes it acts normally as it should. Just now I placed a call and went downstairs outside (its 11pm here) and the sensor is working perfectly fine. Though, a couple of minutes before posting it wasn't, and a couple of hours ago (it was around 5 to 6pm) it was doing the very same thing I described. It doesn't happen always, but when it does, it doesn't go away 'till it decides to go away.
[One (M7) Original Android Development] wmg316:
[MENTION=4684315]flar2[/MENTION]. In my very similar case, it was not the firmware, nor the ROM base. It happened to me on the Dev Edition stock ROM, 1.44 hboot, 1.54 hboot, 1.19 base Viper ROM, 2.24 base WCX ROM. Also on all kernels I tried. Your kernel is the only option for me...and as I mentioned in my previous post I bought another One and this problem hasn't occurred on this phone. I really think mine was a hardware issue...hence it is in for warranty repair/replacement.

On another note, the double tap home button is really sensitive on your last beta...sometimes putting phone to sleep.