yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] postfatal:
Can you put all the updates in the OP please, it's really annoying to have to scroll through pages to compare changelogs/ versions.

Other than that fantastic Kernel.
[One (M7) Original Android Development] dgtiii:
Look on page 277. 3.1 is a beta, so not in the OP yet
[One (M7) Original Android Development] flar2:
Sorry, I just don't want them spread too widely yet. I've been experimenting a lot lately and I don't want 1000 people downloading it just in case :)
[One (M7) Original Android Development] Luisit0:
Dunno why anyone would wanna go back to ondemand gov for gpu, simple runs so much better!!

EDIT: Also, would someone care to explain what tcp congestion control is? I kinda researched it but couldn't really understand how it functions on phones... Finally, is there a wiki or something where I could read up on the different options available? They're so many and I just dunno what the differences are and the names (westwood, cubic,...) don't really help XD
[One (M7) Original Android Development] MrKudinGTO:
Of course they got their own reason for that. Like me, simple governor gives me a bit more heat when using the phone. Probably because the governor is a bit aggresive compared to ondemand. And to be honest, I don't really feel that much difference on both governors. :)

And [MENTION=4684315]flar2[/MENTION], thanks for pointing out the solution for the ondemand problem. Didn't expect that it's that easy to fix. Just reboot. lol silly me :p

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] Luisit0:
Hmm, well at least for me I've experienced no stutter at all, whereas before applying simple gov I would experience very rare, occasional stutters.. Well, that's just me, though :)
[One (M7) Original Android Development] flar2:
I think I've fixed the problem of sweep2wake not working, while keeping the protections against accidental wakes and screenshots that I added in the past couple versions.

Download:

ElementalX-m7-3.2

Changes:

-fix sweep2wake bugs
[One (M7) Original Android Development] threetwentyfizzle:
S2W working flawlessly now. Good stuff. Changing GPU governor to simple makes homescreen and app drawer smoother for me too. Thanks for the update as always Flar! Will try to donate something real soon, trying to pay for a wedding so will try to throw a few beers your way as soon as I can! :thumbup::thumbup:
[One (M7) Original Android Development] Unoath:
Working Great! Thank you as usual! :)

Ok re-downloading.
[One (M7) Original Android Development] flar2:
Actually, the sweep2wake problem is still there :(

I've just re-uploaded the file with a fix. If you downloaded it before this time, download it again.
[One (M7) Original Android Development] postfatal:
Ah, totally understand.

Could I get some more info on what the changes to mpdecision actually are to tweak it more towards battery/performance? Is it just optimization? Similarly whats the new "screen of max frequency", is it just a way of setting within the actual config files of the Kernel things that are normally set with CPU controller apps?
[One (M7) Original Android Development] Unoath:
The update to S2W seems to be working better now flar2. :)

Cant wait to see what else u have in store for us! :D
[One (M7) Original Android Development] Johnny424:
Seems smoother to me to using simple as oposed to on-demand. App drawer close especially .. will test more tommorow. Thanks for all your hard work flar...:D
[One (M7) Original Android Development] FangorX:
I think the mpdecision tweaks simply change the threshold for setting additional cores online and offline, kind of like setting the CPU governor up_threshold but for cores instead of frequency. At least that's what it looks like it's doing in the elementalx init.d script.

As for the screen off max freq, it's basically self-explanatory. When the screen is off it automatically limits the max frequency to the specified value. It's much better than using an app like SetCPU because the max frequency file.doesn't have to be changed every time the screen turns off or on, and nothing has to run in the background.
[One (M7) Original Android Development] kazemitsui:
how does Simple vs OnDemand gov for gpu compare. most explanations of governors are for cpu. Thanks!
[One (M7) Original Android Development] carlos67:
Very impressed with this kernel

Early impressions with 3.2 are very good :eek:. Using MPDecision=performance / simple GPU governor [MENTION=1034050]450[/MENTION]MHz with laziness=7 and ramp =1 / Intellidemand with FIOPS / CPU 1.9GHz / 384 Max screen off / 2048 Read ahead / eMMC entropy disabled /

Phone is beautifully smooth, possibly the smoothest android experience to date and that includes Samsung s2,s3 & s4. Running Nova launcher prime 2.1.1 with all the bloat frozen like maps etc etc. Zero lag/stutter even when pushing it hard.

Excellent work [MENTION=4684315]flar2[/MENTION]. Very happy with this kernel on viper Rom 1.2.1

p.s. is everyone else having 1100MB free Ram with no apps running? My Ram usage shows 1100/1550 free:eek:

p.p.s. Intellidemand up threshold=65 and sampling rate =10000
[One (M7) Original Android Development] Luisit0:
as far as i know (someone correct me if im wrong) ondemand scales as it sees necessary depending on what the gpu is being used for. it basically runs stock frequency on basic things like scrolling, opening folders, etc... and then topping at highest frequency when opening gpu intensive apps or running graphic intensive games, and then going back to minimum freq when innactive; simple tops at maximum for whatever u do that requires use of gpu, therefor always providing smooth performance as it will always be at max freq when running, and then scaling back down as intensity of running process declines.

---------- Post added at 03:04 AM ---------- Previous post was at 03:02 AM ----------

Excuse my ignorance, but how do u edit "laziness, ramp and eMMC entropy"?? And would u recommend ur very set up for someone that plays many gpu/cpu intensive games and wants the smoothest experience? Thnx in advanced!
[One (M7) Original Android Development] kazemitsui:
Btw [MENTION=4684315]flar2[/MENTION] I really love the new aroma config. its much better rather than having a new page for each option! Great work dude.

Question for those who flash the kernel with disabled 3 button mapping.

I know in 4.2.2 as everyone else knows... that "Home" can now be long tap for menu. and in apps like "Play Store" there is now that 3dot menu in the top right corner.

If you select "disable 3 dot menu" in Aroma do those dots disappear in play store?
[One (M7) Original Android Development] Luisit0:
Nope, only the ugly ass black bar that appears on apps like facebook. The 3-dot one remains on apps that have em, like Play Store.
[One (M7) Original Android Development] sweetnsour:
I believe you can do that in the "fauxclock" app.
[One (M7) Original Android Development] kazemitsui:
ah ok thanks. well i just leave it on in kernel and if you set up the home for long tap to menu in settings its gone anyways. just wondered why we still need that option when HTC kind of solved that issue.
[One (M7) Original Android Development] Luisit0:
hmm i see, so would this app replace trickster mod? cause for $5 it better do it all, else I'll just ignore those 3 changes

EDIT: nvm, just checked it out on the Play Store.. looks like im kissing trickster mod bye bye

---------- Post added at 03:14 AM ---------- Previous post was at 03:13 AM ----------

+1 on that one
[One (M7) Original Android Development] carlos67:
You can tweak them all till your hearts content with Fauxclock (what I use) or Trickster MOD.

The settings that I posted are for pure performance with no regard to battery life. Having said that, the battery life I am finding surprisingly reasonable. Last night after leaving the phone for 10 hours in standby, I lost 3% and CPU Spy reported 99% deep sleep. With these settings, the phone will perform very smoothly when in use but be just as battery aware when screen off.
[One (M7) Original Android Development] Luisit0:
Thanks for replying! I decided to install faux123 cause it has so many options and more than trickster, so it's worth the $5. I also set ur same set up but im not oc'd to 1.9ghz, still im already finding it as smooth as the first day i got my One (if not smoother!) so its definitely working! as far as battery life, ill see how it goes in the passing days :)
[One (M7) Original Android Development] evilmastr:
The three dot buttons actually disappears in some apps. Wordfeud is one of them.

Edit: Just checked, play store doesn't have a button either.

T9'd from my black HTC One M7
[One (M7) Original Android Development] MrCupra:
Is the simple governor active or do you have to select it manually?

I'm using systemtuner, so I can't see it. I think :rolleyes:
[One (M7) Original Android Development] Luisit0:
yeah i noticed this later on, reflashed kernel to set logo2menu (forgot to do it before) and accidentally selected to remove 3-dot so i entered play store now and its gone... sh*t i kinda remember it staying though, or maybe im confusing the 3-dot removal tweak from viperone... i rlly dnt remember :/

tl;dr ur right, 3-dot's gone on most apps

---------- Post added at 04:55 AM ---------- Previous post was at 04:54 AM ----------

u gotta set it manually, u can use trickster mod (free) or faux123 ($5, worth every penny)...
[One (M7) Original Android Development] kazemitsui:
you guys know what im talking about right? Cause i know before in ElementalX and with 4.2.2 and ARHD 12 i think

if you select in kernel for remove 3 dot menu. the 3 dots for menu in play store that are in the top right corner actually disappeared to so you HAD to use logo2menu. I am just wondering now if you select it in ElementalX if it still makes those gone?

I tried the original option in "settings" to set LongHome2menu and LongHome2GoogleNow and the 3 dots to right corner still there, but the difference was facebook. no black bar for LongHome2menu and yes black bar for LongHome2GoogleNow
[One (M7) Original Android Development] Luisit0:
exactly the 3 dots that appear at the top, but in my case both that one and the one on settings > display, gestures & buttons also disappeared :confused:
[One (M7) Original Android Development] kazemitsui:
Did you tick "Remove 3 dot menu" in Aroma for this kernel?

I have a feeling its because of that. Thats why i stop ticking that option and leave it as "Restore" now that if you do LongHome2Menu in "Android settings"

Also i would like to know is there really a need to have "REmove 3 dot menu" now that HTC has somewhat addressed it with LongHome2Menu?
[One (M7) Original Android Development] deagleone:
The ROM checks if there is a Menu button (with elementalx u have one) so the option under Settings-> Display.... is gone

if u want your 3dot menu back, search System/build.prop for the following line....

qemu.hw.mainkeys= and edit it to "0"

or paste it to the end of build.prop

it has look like

qemu.hw.mainkeys=0

reboot, wipe cahe dalvik and done ;)
[One (M7) Original Android Development] Luisit0:
I did actually select "Restore".

---------- Post added at 05:48 AM ---------- Previous post was at 05:47 AM ----------

Will give this a go right now! I'll report in a couple of mins..

EDIT: 3 dots are back :) yeeaah!!

PS. I can't get enough of the splash screen!! lol
[One (M7) Original Android Development] kazemitsui:
hmm thats odd. But great you got it back! What version of Elemental were you using? im using 3.2
[One (M7) Original Android Development] Luisit0:
3.1, but there rlly wasnt any huge differences between the two, so yeah i agree its odd :confused:
[One (M7) Original Android Development] evilmastr:
The ondemand governor for GPU is broken in the latest beta, isn't it? It's not as smooth as earlier betas. Simple governor is smooth, but I'm worried that it drains the battery faster. Anyone know?

T9'd from my black HTC One M7
[One (M7) Original Android Development] :
Hi,

:)
[One (M7) Original Android Development] evilmastr:
Captain Smartypants is in the house!

T9'd from my black HTC One M7
[One (M7) Original Android Development] jlevy73:
Those are great settings, Carlos, thanks for sharing them.
[One (M7) Original Android Development] arhung:
how can we set max screen off in fauxclock??or is it default with 3.2??
[One (M7) Original Android Development] flar2:
It defaults to 486MHz, which is pretty good. I don't know if you can set it with fauxclock, but you can set it with Venom Tweaks if you're using Viper.

You can also change it like this:

echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq

If you didn't enable the max screen off frequency in Aroma, then the setting doesn't do anything.
[One (M7) Original Android Development] vomer:
3.2 working well so far :good:
[One (M7) Original Android Development] jerrylzy:
thermal throttling seems to be broken, I am using extra cool option and when the cpu temperature passes 56 degree the cpu freq is still 1890mhz

EDIT: Sorry it is working
[One (M7) Original Android Development] Beremus:
I tested the values for a bit, I came to a conclusion.

The max freq when screen is off should be capped at 594Mhz or 702Mhz. Why? The phone works faster without compromisng battery life. At 384 or 486, the device stays awake much longer than with a low/mdeium freq. (Its a matter of microseconds....)

So... That's what I found.
[One (M7) Original Android Development] flar2:
HTC sets max screen off to 1024MHz on stock. They use thermald to control it, which is disabled in elementalx, which is why I implemented it separately. There is definitely a tradeoff, I think I may set the default to 702 next version.
[One (M7) Original Android Development] mido3010:
Flar, the kernel is amazing but my Bluetooth keeps disconnecting every once in a while any help would be appreciated :) I am on sentinel 3.0
[One (M7) Original Android Development] Beremus:
I had a nexus devices for about a years and a half and I used my personnal modded franco.Kernel... The same situation happened there, 702Mhz was better for battery life and the phone was faster and more fluid when it cames to waking it from deep sleep.

(P.S. noob question here, a little bit too lazy to come back few 100 pages back.... Is faux123 sounds in your kernel?)
[One (M7) Original Android Development] NeidRider:
Is there a sample-elementalX.conf around somewhere?

I want to run the kernel, but am unable to use the aroma-installer (i.e. I've bootet the boot.img, the necessary files in /system have been copied from the zip).

With a "default"-config-file I could configure the kernel by editing the file...
[One (M7) Original Android Development] bLubhimselF:
tried 3.2, too but battery drains much faster like on 2.7...same settings... and for me... sweep2wake wont work reliable. im on viperone tmobile germany.
[One (M7) Original Android Development] iElvis:
You have to give the kernel time to settle in. I find that i get higher battery drain right after flashing a new kernel, but things settle down later.
[One (M7) Original Android Development] bLubhimselF:
okay thanks :) but.. what is to do because of sweep2wake? any idea?
[One (M7) Original Android Development] FangorX:
Guys, look at these battery stats - I seriously think my battery is uncalibrated or something. Literally 0% drain over 8 hours! And that's with auto sync on and wifi set to always on while asleep.

I know it's too early to draw any real conclusions about battery life, but it's looking promising.
[One (M7) Original Android Development] iElvis:
Don't know. S2W is working fine for me.
[One (M7) Original Android Development] donmarkoni:
Here you go, it's preset to my likings, but you'll manage, as you obviously know what you are doing. ;)
[One (M7) Original Android Development] Beremus:
Trickster Mod settings doesn't stick even with the Donation key... How can I achieve this?
[One (M7) Original Android Development] tiho5:
Did you enable "set at boot" in options?
[One (M7) Original Android Development] Beremus:
I feel dumb at this moment.
[One (M7) Original Android Development] semool:
Hmmm this dont work for me. Ondemand GPU is not smooth. Not after reboot and not after deinstalling Trickster Mod and reinstall kernel.

But simple Gov works realy great :D

Maybe its a Rom thing? I use ARHD with all the time GPU Rendering.

But the old Versions without the simple Gov works great and smooth.
[One (M7) Original Android Development] evilmastr:
I have the same problem and I'm using Trickdroid 8.0. Simple governor works, ondemand is always lagging.

T9'd from my black HTC One M7
[One (M7) Original Android Development] Dangermous79:
Yea I agree S2W takes 3 or 4 attempts now. Apart from that everything else is perfect great battery life and performance. Keep up the good work.
[One (M7) Original Android Development] FitAmp:
GPU is still being set at 200 max. I used trickstermod to set it back to 450 and it worked.
[One (M7) Original Android Development] iElvis:
Also, when you flash a new kernel, you may need to go to back in there and check it again. Happened to me.
[One (M7) Original Android Development] tiho5:
[MENTION=4684315]flar2[/MENTION]

I'm still getting "system is not responding" when I reboot. This happens since version 3.0 I think with about a third of the reboots I make.

Last time I had to hard reboot 3 times to load the ROM...

Someone else reported this here also and I think you're also on Viper.

Do you have this from time to time too and do you gave any advise how can I stop this from happening?

I love this kernel and hate to have this. It just stops me from enjoying it completely :D
[One (M7) Original Android Development] DSC05:
I recommend to fix permissions (this helped me on Viper one). If this doesn't help I would dirty flash the Rom again. It has definitely nothing to do with the kernel. It's a viper one issue.
[One (M7) Original Android Development] flar2:
I had it happen two times from flashing different combinations of l2m and remove/restore 3dot menu. I don't know why it happens exactly, because I can't replicate it. But it only happens after installation, I just re-install and it's fine.
[One (M7) Original Android Development] flar2:
I had it happen two times from flashing different combinations of l2m and remove/restore 3dot menu. I don't know why it happens exactly, because I can't replicate it. But it only happens after installation, I just re-intall and it's fine.

I think it's something to do with all the Venom Tweaks settings not syncing up with build prop and other changes from removing/restoring the 3 dot menu.
[One (M7) Original Android Development] Sneakyghost:
Hey flar2,

just updated to your 3.1 release and find it seems to be running well.

The new Aroma option to disable HTC color enhancement sounds interesting. Didn't enable it yet though. New discovery? You have a positive impression with that?

I need to feedback one thing from the 2.7 beta still though: i was navigating again with it today and the phone again didn't get enough juice to sustain battery or even charge it. The charger is some OEM 1500 ma/h model. So i guess its still not working right even though the phone doesnt complain about third party chargers anymore.

I will test it on 3.1 tomorrow morning and get back to you on that. Also i would love to hear if other users experience it as working? Maybe its just my charger?

For me this is a really important feature as i navigate a lot and see no point in buying expensive HTC chargers.
[One (M7) Original Android Development] tiho5:
I checked build.prop and I see

# Disable Softkeybar

qemu.hw.mainkeys=1

more than 10 times at the bottom there. :)

I'll restore from NAND and check how it behaves

Thanks !
[One (M7) Original Android Development] flar2:
It used to pile up those settings, but it's supposed to delete all except one. At least that's how it works on mine.

The problem might be either having two entries with opposite settings, or no entry when one is expected.

The installer backs up your old build.prop
[One (M7) Original Android Development] Johnny424:
I have also seen that not responding message. I select okay it boots around one more time right into system..I am also running viper..never worried to much about it because it doesn't have a pattern and for me doesn't happen often..
[One (M7) Original Android Development] twerg:
flashed this kernel on my newly rooted 1.29.980.2 and all seems good except camera does not work. Tried 360 Camera too and app just crashes, maybe can not access camera modual?

It will load but shows a black screen with the option icons greyed out.

Is there some fix or is it it not compatable with rooted stock 4.1.2? I did flash the correct kernel, and did 2 reboots as insrtucted

WIll try the other kernel, bulletproof to see if fixed camera.

Cheers
[One (M7) Original Android Development] iElvis:
The camera bug was part of the 4.1.2 kernel; I can't remember if there was ever a fix.
[One (M7) Original Android Development] twerg:
Cheers. The Bulletproof kernel does not help either.

So i guess I have no option except top try another kernel, restore my backup or try a custom rom..

I can see in the change logs plenty of camera fixes, obviously not included in latest kernel.

Oh well.

Thanks
[One (M7) Original Android Development] iElvis:
It doesn't exist in the 4.2.2 kernel. You might try upgrading.

IIRC, the bug was due to missing code in the kernel source HTC released for 4.1.2, so there was no way to fix it. 4.2.2 is on new source.
[One (M7) Original Android Development] tiny4579:
You need to flash the correct elementalx or bulletproof version for your android base. Elementalx 0.11 without the camera fix should work on your base since it ends with .2.

PS. I haven't heard of a .2 base android 4.1.2 build.
[One (M7) Original Android Development] carlos67:
Just to say that it's going to take one hell of an update to get me off of this excellent, smoooooooooth 3.2 kernel.

Thanks [MENTION=4684315]flar2[/MENTION], great work. Seriously great work indeed. Take that as a compliment coming from an "OCD about lag & stutter" freak that I am. No sign of it anywhere. I put it down to the MPDecision tweaks and simple GPU added governor.

This and Viper 1.2.1 Rom is a fantastic, stable, smooth combination.
[One (M7) Original Android Development] cee43ja1:
If you're sticking to 4.1.2, delete the liboemcamera.so file inside the zip first. It's in /system/lib folder. Then flash the kernel in recovery.

On a related note to 3.2, just flashed it last night. GPU is getting set correctly now.
[One (M7) Original Android Development] Smoothface:
Every time I have gotten that message (different kernels and chargers) it is due to the phone generating too much heat. Once the phone reaches a certain temperature it cuts back the charging rate to keep from overheating. This point comes even faster when the phone is in hot weather, direct sunshine, or not being in a position where it cannot dissipate the heat.

As soon as I cool it down, charging continues on as usual.
[One (M7) Original Android Development] WinGzZ:
Hello all,

Android noob here. Been lurking around the forums trying to learn as much as I can for a few weeks now and let me start off by saying these forums are super helpful. I'm very interested in this kernel mainly for the awesome battery life everyone is raving about and the sweep2wake functionality. It seems that I need a custom rom in order to install this kernel and I was wondering which one was the most stable 4.2.2 version. I'm seeing that Viper and ARHD are the most popular here, but am having trouble deciding. All I really want to accomplish is update to 4.2.2, gain sweep2wake functionality, fix the inputs while in call, and increase battery life. Everything else can stay stock. Can anyone help me out? Thanks!
[One (M7) Original Android Development] dgtiii:
I use the VenomOne rom, which has a ton of tweaks and customization. However, I have also used the Maximus rom, and if you really only want the functions you listed, it should work very well for you.
[One (M7) Original Android Development] uronfire:
You don't have to install custom Rom to use this kernel. Works fine with stock Rom:thumbup: