yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] mattisfaction:
These are my stats, seconds before the phone shut down.

It's in landscape because I had no time to turn the phone to portrait as it literally died on me, was watching tvcatchup at the time.

Again, very impressive job done by everyone that has helped to bring this experience to the HTC one.
[One (M7) Original Android Development] sosolid4u09:
Flashed this kernel on my pacman 4.3rom.

my home button doesn't work anymore. Just brings up a menu. Is this kernel not compatible with pacman?
[One (M7) Original Android Development] LiquidSolstice:
You flashed the wrong version. There are two versions. One where the Logo is mapped to Home, and one where the Logo is mapped to Menu. You want the BACK_MENU_HOME one.
[One (M7) Original Android Development] sosolid4u09:
Thank you! That sorted it
[One (M7) Original Android Development] LiquidSolstice:
EDIT: Edited for derp.

For further information, Neocortex was previously a Samsung user an old school HTC user, Because he's used to how the button layout used to be, he wants to give people a choice, so he offers a version of each kernel with that button layout in mind.

You however will almost always want the Back Menu Home variant of the kernel.
[One (M7) Original Android Development] n3ocort3x:
Hehe I never used Samsung. HTC since my first Android but I always had 3 buttons and menu on right :) desire.. Desire Z.. Onex and now they removed my beloved 3rd button :D

noNeedForAsig
[One (M7) Original Android Development] SecUpwN:
Samsung sucks balls. HTC rocks! :)
[One (M7) Original Android Development] jthatch12:
That's an ignorant statement. Samsung is decent, I don't agree with their recent decision making hence I own this phone. Prior I owned and developed for the Galaxy S2. Which is a very solid phone still I might add.
[One (M7) Original Android Development] LiquidSolstice:
Although I would never use such infantile language to describe any company (Be it Apple, Samsung, Sony, etc etc), in my honest opinion, the Galaxy S2 was the last of the solidly built phones, and was also the last time Samsung truly innovated in the mobile sector.
[One (M7) Original Android Development] hypocritelecteur:
Is there a reason that the only GPU settings are an aggressive overclock (487mhz) or an aggressive underclock (320mhz)? I'd really prefer a stock 400, highest 450. But really, why does anyone feel the need to burn out the hardware of the fastest phone on the market?

Is this a kernel decision or a trickster mod error?
[One (M7) Original Android Development] jthatch12:
I absolutely agree. This is the reason I went with the HTC One over the S4. It was honestly a no brainer. I'm tired of Samsung's gimmicky features. They need to make solid phones before they can advance the features. Plus the S4 just looks overall larger then the One. Sorry for taking the thread off topic. Nice kernel, I'll be pulling the sources soon and whipping up my own version!
[One (M7) Original Android Development] LiquidSolstice:
GPU clocking doesn't work the way you think it does. If I wanted to, I could run at 487MHz and forcibly max it out 24/7 by using the Performance GPU governor and I could guarantee there would be much more than a few minutes difference in battery life and absolutely no heat difference either.

Please don't generalize if you are unsure. We're not "burning out" our phones and there's nothing "aggressive" about this kernel.
[One (M7) Original Android Development] hypocritelecteur:
I've been overclocking computers and mobile devices for almost twenty years. I've been in software and web design for ten. I know how a governor works--if you're done being arrogant can you answer the question? I'm assuming that the only options available are that aggressive overclock and the aggressive underclock--and no matter what you claim, a clock spectrum of over 40% is aggressive--but you were too busy being smug to actually answer.

I know that 487 does not mean a constant burn at 487. I also know that when I use CPU intensive processes, the temperature gets much higher than I am comfortable with with at a clock ceiling of 487. 450 is tolerable.

There's absolutely no application on the platform that requires more than the default 400 though (or even all of that 400), and setting the max that high just means that the GPU governor cranks it too high when its under pressure. If the overclock is mandatory with this kernel then its not the kernel for me, its a kernel for benchmark junkies that prioritize the wrong things which is a shame because its arguably the most well designed and feature complete kernel available. And adding one more notch on the settings belt is a quick fix.
[One (M7) Original Android Development] n3ocort3x:
Tomorrow's kernel update will include Ondemand governor from n7 baseline + all from cm until tomorrow. I must admit the Ondemand gov does an nice job so far :D (with some small adjustments)

noNeedForAsig
[One (M7) Original Android Development] thekalby:
Using Logo2Menu, but having a light problem. I have it set in CM 10 that pressing menu opens multitasking, and holding it opens the menu. For some reason though, holding the HTC button does nothing with this kernel. Anybody else having this problem?

Additionally, there is a slight delay between hitting the htc button, and multitasking opening up, that I dont get with other kernels.
[One (M7) Original Android Development] mj084:
[MENTION=4635674]n3ocort3x[/MENTION]

Ondemand for CPU or GPU? ;)
[One (M7) Original Android Development] Chezbel:
Support for Logo2Menu and similar options were removed from CM10 about a month ago. If you build your own ROM you have to add back some changes that CM removed.

Or you can try a modified ROM that has this support, for example see LorD ClockaN's Home Brew. It's CM10.2 with some minimal, but nice changes

http://xdaforums.com/showthread.php?t=2414819

EDIT: Sorry, I think I misread your question...
[One (M7) Original Android Development] thekalby:
I know, thats exactly what Im running now, and I set it to have an action when i touch the log, and one where i gold it down, however the holding down one doesnt work. Additionally, the Htc logo is a drop slow to react to my touch, the vibration is slightly delayed, along with the opening of multitasking, which is what i set it too. Any ideas? I love this kernel, but i hate the way it handles logo2menu. Any way to build one that somehow puts in the logo2menu from the kernel he provides?
[One (M7) Original Android Development] LiquidSolstice:
No, there's no need to spin me stories about how amazing your "tech skillz" are. I've seen your posts before, you're generally more interested in explaining to the world why you're right about something rather than thinking about it. It doesn't matter what I say, you're dead-set on your opinion that no one needs 487, and that only "benchmark junkies" use it.

Tell you what, stop being a condescending git; we don't give a damn what makes you "comfortable". If you're smart enough to know how governers work, you're smart enough to know how to manually set the GPU clock and force it to set on boot (with apps or modifying your init.d scripts yourself, which some of us do actually do). But the fact that you think a GPU clock is "mandatory" makes me wonder if you really know what you're talking about...

Your essay of a post proves little more than the fact that you simply want everyone to know how outrages you are about the GPU frequencies of this kernel. I have conclusive proof that I achieve better framerates on everything from the user interface to apps to the games I play. I am ridiculously anal about UI framerates, and the higher clock speed makes a very noticeable difference.

You don't need to play the game if you don't how its played. And honestly, I don't give a damn whether or not you use this kernel, it's not my job to sell it to you. Just don't group me in with your condescending bull**** of "benchmark junkies" because the last time I used a benchmark app was back when I had an HTC Hero.

And since I have way more respect for an actual contributing member like Neocortex than I do you, welcome to my ignore list :)
[One (M7) Original Android Development] LiquidSolstice:
Anyways, now that that's out of the way and I don't have to address someone complaining about how a kernel is too high on the performance end, I must say Neo, whatever you did to the last build seems to be making a fairly decent difference for me in terms of battery life.
[One (M7) Original Android Development] Chezbel:
I guess the reaction and vibration from the logo touch is slightly delayed compared to the back and home keys (it's never bothered me), but keep in mind that back and home are physical buttons that are not part of the touchscreen. The logo "key" has to be detected by having the kernel look at the X and Y touch position to decide if that is a menu press.

As for building, I use the base CM10.2 with 3 or 4 modified files that allow logo2menu. I also changed my repo to grab [MENTION=4635674]n3ocort3x[/MENTION] kernel source and

changed my board configuration to use that kernel instead of the default CM10.2 kernel. Since I'm not at home I can't be more specific right now.
[One (M7) Original Android Development] mynameisjon:
Neo, is there any chance at all that you'll look into incorporating dual boot features into your kernel?
[One (M7) Original Android Development] hypocritelecteur:
Wowzers. And my name is hypocritelecteur....

I never said anything about leet tech skills, nor did I ever insult you. I'm mildly competent and have a long history in IT. I've said that your posts come across as smug and dismissive and do not answer the question. And yes, I have run into you before and if you look over our love letters, every time I ask a question you pop in to say "your question doesn't matter, here's why you don't want what you think you want," and I say: hey dude stop being smug and condescending and answer the question. Then this happens.

This only happens with you dude. Think on that. And please, answer a question and don't assume the asker is an idiot or do not respond at all. Only you care about your opinion of me.

That is the one and only thing I object to about you, unfortunately it doesn't seem like there's much else. Every time I try to get information you jump in and act smug while evading anything like a real answer. It's very frustrating. Thanks for the essay about me though--really reinforces how much I talk about myself. Once again, a series of responses attacking the person instead of addressing the issue.

Please try harder. All I wanted was some info, not to be insulted and the conversation derailed. A simple "no" would have concluded our interaction--and this should be the goal of all of our interactions for the sake of everyone else here. Then I could move on or continue tinker. Without your snide guidance.
[One (M7) Original Android Development] Chezbel:
[MENTION=5228347]hypocritelecteur[/MENTION] / [MENTION=788951]LiquidSolstice[/MENTION]

Whatever the issue is, real or perceived, maybe you can at least agree to ignore each other? I'm sure you both have a lot you can add to this thread and as this is one of the "nice" threads I would hate to see it fall apart like so many other XDA threads have done.
[One (M7) Original Android Development] n3ocort3x:
MOD CLEAN IT UP PLEASE (I dont even read this, those times are over) thanks
[One (M7) Original Android Development] hypocritelecteur:
Agreed.
[One (M7) Original Android Development] thekalby:
My only point is this delay does not exist in any other kernel. Additionally you have not addressed why long holding the logo does not work. Is there any way to remove the logo2menu file, and replace it with one from another kernel? Would that somehow fix my issue?
[One (M7) Original Android Development] Chezbel:
Sorry I don't know
[One (M7) Original Android Development] oc2:
Hey

Is it possible to integrate ECO MODE in this kernel for activation in TricksterMod?
[One (M7) Original Android Development] LiquidSolstice:
Battery's doing great. Even with my GPU clocked at 487 with the performance governor, I'm averaging 23-24 hours of battery life with my usage. It's wonderful. Thanks!
[One (M7) Original Android Development] mattisfaction:
Exactly mate..

why would you want eco mode? :eek:
[One (M7) Original Android Development] oc2:
Yes, battery time is not bad! but this kernel has more potential.

But i don't need 487 MHz, 400 is also fine for me, i'm not a Gamer.

On 4.2.2 with Aux Kernel my One runs 50 hrs with 3 hrs display-on.

With 400Mhz and Eco Mode i think this kernel will have an amazing battery time.
[One (M7) Original Android Development] mattisfaction:
I appreciate what you're saying mate.. performance ain't got everyone. Obviously you won't be able to down the gpu step, but you could try setting your own eco mode profile in trickster, downing your clock speed and your voltage.
[One (M7) Original Android Development] LiquidSolstice:
The 487 also heavily benefits the overall UI framerate. It might not be something that you're concerned about it, but you should definitely keep it in mind.
[One (M7) Original Android Development] n3ocort3x:
OP updated to v45 (dont wonder i skipped v44 public)

Changelog as always in OP
[One (M7) Original Android Development] hypocritelecteur:
Android does not require an overclocked adreno and a quad core processor overclocked to 2ghz to run the UI smoothly.

Optimizing is great.

The mobile equivalent of a two foot spoiler is not. Especially in the name of UI performance! You're installing NOS under a claim to improve commuter travel.

Eco mode and 400mhz setting would be awesome and it sounds like there are a few folks that miss it!
[One (M7) Original Android Development] erbse:
Could you write some more details or send a picture which shows the screen on time,

wlan, mobile standby drain and so on...

i got a htc one and switched after 1 - 2 days to cm and this kernel and so i haven't

an idea what is a bad, normal or good battery life ...

At the moment i think the standby drain is too high, specially if wlan is on.

BTW: big thx @ teaMseven for the kernel !

thx
[One (M7) Original Android Development] mattisfaction:
How much screen on time do you have mate, is your phone in standby all day, do you use it? ;).

I get and have posted pics about 18hrs normal usage and 10 if screen on is up at four and a half hours, posted pics a few pages back
[One (M7) Original Android Development] SecUpwN:
[MENTION=4635674]n3ocort3x[/MENTION], I love your kernel, but would you PLEASE add a short description to each download link? Since 4 releases I keep downloading the wrong one before grabbing the correct file. Thanks ahead.
[One (M7) Original Android Development] n3ocort3x:
Have u ever seen how often the the SoC spends time on all 4 cores? Or have a feeling how much more battery is consumed compared? Or aren't u aware that u can realize Eco mode by urself with hotplug control that is already in kernel? Just set the right values.

U will see that there is not much difference. Its well known here in xda that everyone believes everything. And especially buzzwords have high effect. I could call features with any ultra cool name and u will see this thread has a lot more posters.

noNeedForAsig
[One (M7) Original Android Development] mj084:
[MENTION=4686037]SecUpwN[/MENTION]

Why a short description? Should be all clear...

FOR CM 10.1 (JB 4.2.2 and ROMS based on it

AND

FOR CM10.2 (JB 4.3)

for each of them you can choose for yourself which keymapping you prefer...

BACK - HOME - MENU

OR

BACK - MENU - HOME

all clear now? ;)
[One (M7) Original Android Development] LiquidSolstice:
I seriously wouldn't bother. The last time I tried to reason with him, my posts were deleted and his remained.

On a much happier note, Neo, are you still building your own PAC builds here? http://tunsd.de/downloads/PAC_43/

I'm not in a position to compile them myself and somehow whatever you do specially to your own builds just seems to hit the spot. No worries if you aren't though.
[One (M7) Original Android Development] LiquidSolstice:
Not sure how much you use your phone. I'm more of a "get-in-get-out" type user, so my screen-on time with 24 hours was around 3.5 hours. Hence why I said "my usage".
[One (M7) Original Android Development] n3ocort3x:
I will. But I slowed down a bit as I have other things to do first. Why not joining our community so u are up to date?

noNeedForAsig
[One (M7) Original Android Development] LiquidSolstice:
I joined already :). I greatly enjoy watching things unfold on the page, but unfortunately, due to a major project finishing at work, I won't have enough time to really sit down and teach myself from scratch everything I need to know.

No pressure at all on those PAC builds. Seriously. They're really nice to have, but your kernel still runs wonderfully with the latest nightly. Speaking of which, it seems there were quite a few kernel merges last night. Are any of them as substantial as the GE source merge, or are they little patches that polish things up? Just curious.
[One (M7) Original Android Development] n3ocort3x:
I merged them already in in v45 most stuff is kgsl so adreno GPU :)
[One (M7) Original Android Development] n3ocort3x:
New Version with CPUQUIET Hotplug now available:

Short description: removed old known hotplug control. control is now based on load stats (recommend leaving it like this) but u can change in trickster mod to runnable threads or rq_stats. U dont need to change any values on the cpuquiet governor itself (rq_stats, load_stats, runnable). U wont find a menue for that. However, load_stats itself have a few tuning parameters which are accessible via sysfs:

sys/devices/system/cpu/cpuquiet

u will find bunch of files in it wich u are able to modify to change the behaviour of hotplug control. I will write down a howto later. I adjusted it now, based on my behaviour on phone, so it should be smooth while keeping battery friendly. I recommend leaving it as it is by now, until i wrote down a howto.

First impression: works like a charm :D extreme fast plugging while staying only that time on higher freqs when its necessary.

I take no credits for this, all my thanks go out to [MENTION=4683552]maxwen[/MENTION] who spent a lot of time to bring it to qcom devices. I only modified it to behave a bit more aggressive. more later

links will be available in OP in 5 minutes
[One (M7) Original Android Development] carlolgb:
New cpu_quiet version is pretty damn fast man.

Great Kernel!

THX!
[One (M7) Original Android Development] mj084:
Seems to be really fast!!!

For first look, feels smoother in than normal v45...

And benchmark(ok it's only benchmark) says the same...

28.580 points

settings:

CPU: 162 - 1998 MHz interactive

GPU: 487 MHz ondemand

2048 Kb Read Ahead Buffer

cfq sheduler

Big thx for this great kernel!!!
[One (M7) Original Android Development] oddlyshapedstickman:
Is there any way to turn off l2m? I use PA so I can double tap home for menu which I greatly prefer and don't want l2m due to redudencies.
[One (M7) Original Android Development] Chezbel:
Try setting /sys/android_touch/logo2menu to 0 instead of 1
[One (M7) Original Android Development] raycaster3:
CPUquiet v45 so far has increased performance while maintaining the battery life on used to from this kernel. This is obviously based on a short period of time, I like the way she's sleeping. I'm getting some flatline in there, rather than a steady (albeit VERY slow) drain. Time will tell, but initial impression is extremely positive

Update:

Looking forward to that tutorial for optimal settings. Starting to see more drain than what I had originally thought. Not bad by any means, just not as good as with the old hotplug. I'm on board to ride this thing out to see how good it will be, just reporting.

Sent from my One
[One (M7) Original Android Development] n3ocort3x:
Kernel update :D

teaMsevenAOSP_v46_CM 10.2_CPUQUIET

-no more other hotplug releases then cpuquiet

-introducing [MENTION=3088420]tbalden[/MENTION] FLICK and PICK 2 WAKE on AOSP :) many thanks my friend

-bugfixes, check git

-synced with CM

-tested and working :D

both are disabled by default. u have to enable it manually via sysfs. tb already sent tmo dev a mail with the correct paths so i thing tmo dev will implemend a switch asap.
[One (M7) Original Android Development] raycaster3:
So where are the links? Or they're not up yet?

Edit: nvrmnd the v45 link gets you v46.

Sent from my HTC One
[One (M7) Original Android Development] DroidRC1:
Sorry what is WAKE on aosp?
[One (M7) Original Android Development] poondog:
Saying that its the first AOSP kernel to have pick 2 wake :)
[One (M7) Original Android Development] Donjuanal:
Flick and Pick2Wake are new wake methods on this kernel and tbaldens sense kernel
[One (M7) Original Android Development] raycaster3:
How does one enable these features? They don't come enabled of the bat that I can tell.

Sent from my One
[One (M7) Original Android Development] tbalden:
sysfs paths respectively are:

/sys/devices/virtual/htc_g_sensor/g_sensor/flick2wake value 0-1 (off/on)

/sys/devices/virtual/htc_g_sensor/g_sensor/flick2sleep value 0-1 (off/on)

/sys/devices/virtual/htc_g_sensor/g_sensor/f2w_sensitivity value 0-1 (less sensitive/more sensitive)

/sys/devices/virtual/htc_g_sensor/g_sensor/pick2wake value 0-1 (off/on)

Also you need to have Auto Orientation - On to let the Flick2Sleep work.

I'll have a look at this dependency later (maybe today), because it's not intentional to have a dependency on Auto Orientation, but it turned out only today that it won't work without that enabled. :)
[One (M7) Original Android Development] ess.boyer:
Wow, the flick2wake/sleep is really fun! All the Android fans at work were pretty impressed with my phone this morning :)

Thanks for the great work [MENTION=3088420]tbalden[/MENTION]!
[One (M7) Original Android Development] tbalden:
:) Happy to hear that! I'm having fun too with this feature. :D
[One (M7) Original Android Development] DanRyb:
This is AWESOME!!!! My power button is definitely getting a little recessed. This is such a nicer way to wake the phone up!
[One (M7) Original Android Development] n3ocort3x:
Yep indeed.. Tb u made urself a legend with this :D exactly this is what boys want.. Play around :D :D as I told u on gtalk... Pretty cool when showing around :)

noNeedForAsig
[One (M7) Original Android Development] raycaster3:
I was there when sweep2wake made its debut on sensation and now this. So cool. I live seeing innovation.

Sent from my One
[One (M7) Original Android Development] navalynt:
I went from 2.8%/hr standby battery drain on stock CM kernel to 1.8%/hr on v45 w/o CPU QUIET and now I'm at 0.5%/hr drain with v46 w/ CPU QUIET. OUTSTANDING sir, simply outstanding!
[One (M7) Original Android Development] lbroksle:
This kernel is amazing. Thanks for all your hard work!
[One (M7) Original Android Development] dc4:
Shocked how much this kernel keeps improving, props to everyone involved. :thumbup:
[One (M7) Original Android Development] tbalden:
:D it's a fun thing! As for the future technical side, I hope next generation kernels will have the gyro sensor with kernel driver that's capable of using interrupt waking, so we can add flick2wake to new phones later. Hopefully it won't be an HTC bma250 gyroscope driver only feature, as it seems that the gyroscope is getting attention on MotoX and other new phones too, monitoring user activity. :)
[One (M7) Original Android Development] kickassdave:
Finding it impossible to set those values to 1 for f2w....

Via root browser too
[One (M7) Original Android Development] Donjuanal:
I use solid explorer and it works fine.
[One (M7) Original Android Development] dc4:
I used root explorer, I find root browser has issues with editing values and having them stick.
[One (M7) Original Android Development] formula84:
You have to make sure you are in R/W mode before you open with text editor in Root Explorer

Can't tell you how many times I missed this, open with text editor then make my changes and do save and exit, only to find my changes were not applied.
[One (M7) Original Android Development] mj084:
This method won't work here with root explorer...

Any other idea's for editing the values?