yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] xxsoulxx:
Hi thank you for you work, could you please put additional USB-OTG support inside your Kernel, with tbalden Kernel my DSLR is working with stock Kernel not, did you change something in this Kernel on OTG ? :)
[One (M7) Original Android Development] the_scotsman:
Is anyone else seeing the screen "flicker" when unlocking (swiping the unlock bar up)? I get it every time I unlock. Not sure if it's the ROM (Trickdroid) or the kernel.

But it's REALLY annoying :eek:
[One (M7) Original Android Development] flar2:
Yes, I disabled the USB whitelist. I haven't hooked up my DSLR yet to test, but I think it should work.

I'm still on stock ROM and I'm not seeing that. Keep me posted if you find a cause. That's definitely something I don't want to see.
[One (M7) Original Android Development] flar2:
I haven't looked into OTG at all on this phone. On my other phone (One XL), HTC disabled OTG altogether on ICS, then they enabled it on Jelly Bean. Who knows why HTC limits the functionality of their phones. It probably has something to do with power consumption though.
[One (M7) Original Android Development] tfouto:
Well people should be able to choose i guess.
[One (M7) Original Android Development] c-prodigo:
Thanks flar kernel is working perfectly,... On AT&T one clean Rom...
[One (M7) Original Android Development] kzakaria:
The fastest kernel ever.

+100000000000

THE FASTEST KERNEL EVER.

I have everything maxed out (2.16, 480, Ultra) UV'ed everything (384MHz @ 750mV, 2.1GHz@ 1187.5mV). super fast, cold, and stable.

[MENTION=4684315]flar2[/MENTION] THANK YOU
[One (M7) Original Android Development] biohaufen:
Can you add another CPU clock (1510 MHz), please ? It's the stock max clock of the Snapdragon S4 Pro :)

Gesendet von meinem HTC One mit Tapatalk 2
[One (M7) Original Android Development] flar2:
1566 is not close enough? This is entirely different beast than the S4

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

Anyone trying the 480 gpu oc? I'm curious to know if it's working. For me, benchmarks were lower than stock, but it could just be my chip.
[One (M7) Original Android Development] biohaufen:
I tried the 480 MHz GPU OC, but benchmark scores were really bad...

Gesendet von meinem HTC One mit Tapatalk 2
[One (M7) Original Android Development] oned:
Can u make an Antutu test plz, it FC's every time here... (renovate nightly's) with 2.1 cpu and 450 gpu, stock voltage

Thx

HTC One'd
[One (M7) Original Android Development] Lenunited:
Having trouble installing this kernel.

Get some missing file/folder error on aroma.
[One (M7) Original Android Development] flar2:
That means you're overclocked too high

I know about this and I'll fix it later tonight.
[One (M7) Original Android Development] jlevy73:
[MENTION=298610]Flar[/MENTION]: This is really a great kernel. Everything on it is working perfectly and battery life is excellent. Here's hoping Code Aurora releases some patches that the HTC source did not include.
[One (M7) Original Android Development] flar2:
This one has a few changes under the hood rather than obvious features. I'm just applying tweaks gradually to see if any problems arise.

I also fixed the installer (I think -- I can't possibly test every combination). I removed the 480 GPU overclock. I don't think it works well. Besides, the 450 MHz step gives a noticeable improvement and we start to pay the price in heat for minimal gain going beyond that.

Download:

ElementalX-m7-0.6

Changes

-remove GPU overclock to 480MHz

-disable gentle fair sleepers

-Improve scalability via 'CPU buddies'

-avoid loadavg moire

-a few other minor tweaks

-fix installer
[One (M7) Original Android Development] aussie1234:
OC-CPU App

Can someone please recommend a good app to manage the OC of the CPU and GPU of the HTC One?

Thanks

Aussie
[One (M7) Original Android Development] the_scotsman:
I use Trickster MOD. I've never had an issue with it, plus it's very customisable and still easy to use.
[One (M7) Original Android Development] gianton:
I don't have that issue, currently at 39c while browsing/tapatalking with ambient temp at 27c. Using simple gov 384/1890MHz -50mV rest stock on ARHD 12.1
[One (M7) Original Android Development] randykzc:
Flashed 3.1 ...simple governor is working.. but still prefered ondemand..

[MENTION=4684315]flar2[/MENTION]

For intellidemand, I notice there is the powersave_bias in your script elementalx.conf as well as in trickster mod..

Which one should I change for this powersave_bias? In the script or trickster?
[One (M7) Original Android Development] lolpos:
+1

i went back to ondemand
[One (M7) Original Android Development] evilmastr:
3.0 is smoother than 3.1 with the same settings. Noticeable when opening app drawer for example.

L2M, S2W, S2S, No screen off freq, 1.1 ghz, 450 mhz

T9'd from my black HTC One M7
[One (M7) Original Android Development] FangorX:
Simple governor makes a difference for me especially on the home screen. Thank you [MENTION=4684315]flar2[/MENTION] for adding it!!!

The laziness and ramp threshold don't stick. I find laziness should be set to 0 as it has no noticeable effect and increases power use.

Edit: Never mind they do stick with Trickster Mod donate version. Anyone trying simple should set laziness to zero and ramp threshold to 6000 or 7000
[One (M7) Original Android Development] MrKudinGTO:
But also one thing that I realised, in this v3.1 (atleast in my case), ondemand GPU governor is like, not giving optimal performance. I found that the GPU clock reading stays like 200mHz, while simple governor ramp up GPU clock to 450mHz on UI change (ie: scrolling and stuff). Used trickster mod app to examine this. And tested it on gaming, (I'll take the Minion Rush game in this situation.) simple governor gives me a magnificent FPS in the game. While ondemand like, capped the FPS to, let's say around 15 in my guess. Anyone else can examine these problems too? I might be just me though.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] semool:
Yes scrolling in app drawer or blinkfeed is smoother in 3.0

But with simple GPU Governour the Smoothness come back in 3.1 :)

I use Battery Optimize for mpdecision in Aroma for 3.0 and 3.1.

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] FangorX:
You guys are right, ondemand is broken in 3.1. It stays at 200MHz all the time which is why everyone is saying its slower. I guess flar2 will have to remove simple at least for now since it seems to cause problems
[One (M7) Original Android Development] MrKudinGTO:
Yes, this'll explain my situation above. :)

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] tiho5:
Yeah, it doesn't have a connection with this.

But I still get the same system not responding messages many of the times I reboot. Also now with the 3.1

Am I the only one?
[One (M7) Original Android Development] poondog:
I got no problems, with the enhancer thing on
[One (M7) Original Android Development] tiho5:
That's what I'm saying. I had an assumption that it may have something to do with this, but I wasn't right. Because with our without that setting I have that system not responding message...

Some other reported it also, I think all are on Viper and it's still unclear for me why it's happening.
[One (M7) Original Android Development] poondog:
Well fwiw I am facing no problems on renovate :)
[One (M7) Original Android Development] tiho5:
:)

It's only occasional. Started happening with the last 2 versions 30 & 31 I think. Once booted it's perfectly OK.

Love both the ROM and the kernel.:)
[One (M7) Original Android Development] demisb:
Thanx for this awesome kernel and your continuing work on it!

I donated a little something for you : 48N52559NW348073U

Keep up the great work man!

Verstuurd van mijn Nexus 10 met Tapatalk
[One (M7) Original Android Development] herwegan:
thanks a lot [MENTION=4684315]flar2[/MENTION] for your great work! :good: really good kernel :)
[One (M7) Original Android Development] threetwentyfizzle:
I agree, I noticed the jittery effect when scrolling the app drawer and swiping thru homescreens and BlinkFeed like I did on 2.6. 3.0 was really smooth overall. Must be the gpu clock not ramping up?
[One (M7) Original Android Development] FangorX:
On 3.1 the ondemand GPU governor is broken so it stays at 200MHz. If you switch to the simple governor it will be smooth though.

Edit: after more thought, I think ondemand just seems broken to me because simple is so much better.
[One (M7) Original Android Development] donmarkoni:
Guys, guys, what are you talking about? :eek:

Nothing is broken

. ;)

Here you go...

CPU locked @ 2106MHz, MP-Decision OFF, ondemand, deadline, GPU @ 450 ondemand/simple/performance

Every configuration done twice, cooled by AC. :D Screenshots out of order, try guessing which is which. ;)

I see nothing broken here, just a standard deviation. :cool:
[One (M7) Original Android Development] jerrylzy:
I found 3.1 to be a lot cooler than any other elementalx in the past. I played rr3 for about 20 minutes, and the battery temperature was so incredible that it did not pass 40 degree.

CPU 1134mhz on-demand stock mpdecision

GPU 450mhz simple laziness 5 threshold 6

IO scheduler FIOPS

UV 100mv

Extra cool
[One (M7) Original Android Development] jaythenut:
hi mate i found that if you turn off c2 and c3 you get better battery life give it a go;)
[One (M7) Original Android Development] MrKudinGTO:
Have you test out gaming using ondemand GPU governor? I bet you don't. :rolleyes:

Also, try and get some GPU clock readings while your GPU is on that governor. See if it's ever go more than 200mHz.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] josemedina:
hopefully I am in the right thread for this.

I used this kernel on viper and it worked wonderfully. but with viper i was getting low benchmark scores and a lot of lag.

three days ago i flashed the google edition rom and everything was fine. 20 minutes ago I flashed this kernel, rebooted twice, then opened antutu and as soon as I clicked start test the screen shut off and I am bricked. no led on charger, no capacitive lights, no vibration, nothing.

any ideas is there a way to unbrick this phone? can i take it to tmobile and play dumb?

Thank you for any suggestions.
[One (M7) Original Android Development] donmarkoni:
No. Why would I? Are you implying that GPU would stay @ 200MHz?

BTW, I don't play games on my phone. I have PC for that.
[One (M7) Original Android Development] semool:
Its only a Benchmark!! for Score Junkies.

Important is the live feeling while scrolling in Tapatalk,app drawer blinkfeed ....

And that is definitely not so smooth at GPU ondemand as with 3.0.
[One (M7) Original Android Development] milesjohnson:
Hey guys im on Viper 1.2.1 and actually just got faux's kernel and applied his recommended settings. installed it last night so im waiting to see how my battery goes but what kernel would you recommend for best battery
[One (M7) Original Android Development] MrKudinGTO:
.... Yes. I, and might be a couple of users here who're using v3.1 atm, believes that ondemand GPU governor in this version is broken. The clock reading stays @ 200mHz. Hence the low FPS result in a couple of games like Minion Rush compared to simple governor. Something IS broken I believe. :)

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] Rumball:
Something tells me you are on the wrong forum...
[One (M7) Original Android Development] donmarkoni:
Just ran Epic Citadel and 3DMark as I didn't before on this device... It's awesome. :D

And, of course, GPU ran @ 450MHz. I don't know what are you taking me for, ignorant?

Benchmarks are made for referencing. System with high benchmark score will run demanding games much better then system with low score, assuming benchmark and game are not broken and using HW at it's fullest.

I would not say it is not so smooth, but it is a subjective opinion. No need for arguing about it. Simple governor has more aggressive ramping up. After you try it, ondemand seems broken. ;)

You believe. And you said yourself: something. Why do some people blame kernel instantly? :confused:

And I just explained why it looks broken. Effect of using simple governor.

Ondemand always behaved like that. I have never seen it ramp-up running GUI only. Why would it? It's so easy.

Imagine your PC's graphic card ramping frequency and fan while you are just on desktop, opening folders, copying files, browsing pictures... Well, even while watching videos, high end graphics only ramps up a little bit.

And this is a powerful phone.
[One (M7) Original Android Development] Batskoning:
Hey All,

For more smoothness, is it better to check or uncheck 'Disable HW overlays' in Dev.Options?

Thanx in Advance
[One (M7) Original Android Development] Luisit0:
OMFG!! [MENTION=4684315]flar2[/MENTION] u did it again!! Simple gov with GPU OC'd to 450mhz, stock CPU 1.7ghz freq, fiops and intellidemand, westwood tcp, Gangstar Vegas barely lags!! This means ur kernel is a beast because even on stock kernel it lags pretty often.. RR3 is a deligt to play too!! I'M LOVING v3.1!!!!
[One (M7) Original Android Development] godfirst:
I say disable it! Most older apps will have it automatically enabled and if not just enable it for older apps that seem to be lagging.
[One (M7) Original Android Development] DeSaint2:
Hold the light sensor under a bright light and try again.
[One (M7) Original Android Development] semool:
I dont blame this kernel, i LOVE this Kernel. He is still in Development so Bugs come and go with every Version...NO PROBLEM.

But you have to see that this Bug is no Imagination :D

It has nothing todo with using simple gov and then ondemand.

I have flashed from 3.0 to 3.1 and it was not smooth. Back to 3.0, all good (3.0 has no simple gov).

Again 3.1, not smooth, change to simple gov and it was smooth.

conclusion:

Something is different with ondemand GPU Gov in 3.1.
[One (M7) Original Android Development] MrKudinGTO:
On ondemand governor? Well that's good for you. :) And, what? Ignorant? What makes you think of that lol. That's funny. I'm just asking that maybe you could take some reading on your own device and see if you got into the same situation. Why would 'ignorant' be involve in this situation? Silly boy. :rolleyes:

And to this, do I look like I'm blaming the kernel entirely? Cause I think I'm not. ;) FYI, I use ARHD ROM which is using full and all time GPU rendering for the UI and apps, so as you have to take note, GPU is most likely always used in this ROM. I have been trying ElementalX since v0.x if I remember it correctly. On the last v2.x, I have been stalking the GPU clock speed and I can say, on Ondemand governor, clock speed would ramp up, say like to 320mHz a bit even just by scrolling the UI or anything like that. And of course, using an app would defenitely take more resources from the GPU. (Higher clock speed for instance.) And yes, one more time I would say, on Ondemand governor. But not in this v3.1, clock speed just stays at 200mHz no matter how much you push the UI or using graphics intensive apps. Sometimes I can even feel and see the micro stutters on UI transition (homescreen, app drawer) when using Ondemand, but I can easily get rid of that by using simple governor. Therefore, as I came in this thread, I'm just actually 'reporting', and asking if anybody else are getting the same situation, not blaming the kernel. I highly appreciated this great kernel by [MENTION=4684315]flar2[/MENTION]. The best kernel I've ever used. So I ask for your kindness, do not easily judging someone this or that without any further investigation. Everyone has their own way of using the device, so not all people would found the same problem and not everybody would really care about the problem. And I see nothing wrong in reporting or stating any problem found as the dev could do some search by himself to confirm. :)

Cheers.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] josemedina:
i tried that as well as power + volume up and down for 90 secs, tried with usb hooked up, nothing. computer doesnt even see it when i plug it in.

however, I took it to tmobile, and they warrantied it. so, new htc one in 2 weeks (currently on back order)

appreciate the response though. love the phone, elemental x, and viper rom. should have never switched to the google and started playing again.

anyway, thanks for the work on this kernel Flar, its stupendous!!!
[One (M7) Original Android Development] SleemLDJ:
How do you set these? With an app or there are all options for it from aroma
[One (M7) Original Android Development] FangorX:
Install Trickster Mod from play store. It allows you to control nearly every kernel setting.
[One (M7) Original Android Development] Batskoning:
Yes :) i see under IOSCHED Readahead Size @ 256, for better performance should i change it to 2048..?

And eMMC Entropy Contribution: Off or On..?

It says disable for better performance.. Also with Elemantalx or only with faux kernel..?
[One (M7) Original Android Development] donmarkoni:
Listen, kid, I was using computers before you were born, and had cell phone few years before you went to elementary school, but you really don't need to believe that, or whatever I say...

I did those tests to help, standing on my desk, freezing my fingers off, holding phone up under AC. You showed me that I really shouldn't bother next time. :(

I'm tired and won't argue any more, so you do as you please. Good night.
[One (M7) Original Android Development] MrKudinGTO:
Wow, then you must be a very expert man. Congrats, good to know that. :)

Well, pardon me for making you feel that way. I didn't mean to create any argument or stuff, I'm just giving out my thoughts and opinions as well as reporting out what I'm facing right now. No offence. :D

Cheers mate. Have a good sleep. Don't let the bug bites you. ;)

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] NJGSII:
Where are you guys finding the simple governor? I've downloaded 3.1, 3 times after it was re-uploaded and it still isn't there.
[One (M7) Original Android Development] threetwentyfizzle:
Come on guys lets keep it civil here and not turn this thread into a sh*t flinging contest. I think Flar knows enough from our feedback to know what to look for.
[One (M7) Original Android Development] MrKudinGTO:
Here, in Trickster Mod app.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] NJGSII:
Oh, so it for the gpu only? It just showed up as you had it on my One.

Did not know that. Thanks!
[One (M7) Original Android Development] MrKudinGTO:
Yes, it's a GPU governor. :) Anytime mate. :thumbup:

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] SleemLDJ:
Guys help. Where are y'all downloading 3.1 from?
[One (M7) Original Android Development] MrKudinGTO:
On page 277.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] SleemLDJ:
Thanks. Does it support mpdecision off? I couldnt find any ref to it on the first page.
[One (M7) Original Android Development] MrKudinGTO:
As far as I know, it does. Haven't really look into that though.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] Batskoning:
I think it's on by default.. :) It's better to leave it there i guess.?
[One (M7) Original Android Development] SleemLDJ:
I think it's better as well. It's just that trikstermod app says some cpu or gpu settings might not stick if it's on.

So wanted to check if elementalx supports off.
[One (M7) Original Android Development] Batskoning:
Check post: # 2683

This is what i could find :)
[One (M7) Original Android Development] SSS Desire:
I've reverted to 2.7 from 3.0 and 3.1 since capacitive buttons are more responsive with 2.7 for S2W, L2W and DT2W as well as I don't have any major issue with it. In 3.0 and 3.1, it's mostly a hit and miss especially after the phone falls into deep sleep.

Anyhow this is just my opinion and experience and others could be different. Keep up the good work flar and thanks for this awesomeness!
[One (M7) Original Android Development] Batskoning:
i) For battery:-

To bias ondemand towards battery saving, set high up-thresholds and higher sampling-rate. This way, governor polls less often and scales up less often.

Code:

echo "95" /sys/devices/system/cpu/cpufreq/ondemand/up_threshold

echo "120000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor

echo "5" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential

echo "10" > /sys/devices/system/cpu/cpufreq/ondemand/freq_step

Can we use this for intellidemond..? Found it in the S2 thread..
[One (M7) Original Android Development] FangorX:
I recommend using Trickster Mod instead of shell commands since its easier. You can change the settings for intellidemand to whatever you want, but not ondemand because nothing will stick. These exact commands wont do anything because they're changing ondemand's settings.
[One (M7) Original Android Development] flar2:
I think gpu ondemand is fine on 3.1 unless you choose simple governor. If you go back to it after using simple, it doesn't scale properly anymore. Reboot and it goes back to normal.

I finally figured out the situation that causes that, now I just have to fix it. I want to keep the other restrictions, because they do a pretty good job protecting against accidental screenshots and wakes.
[One (M7) Original Android Development] FangorX:
Thanks for clarifying flar2. That explains why some people were seeing problems and others weren't. The argument was getting a little out of control haha.
[One (M7) Original Android Development] popokrew:
Running ViperOne 1.2.1 with this kernel and it seems like if I'm on a call for a while (5+ min) the only way to get the screen back on is to place the proximity sensor right up to a light. Now I know that this is something all devs have been working on but is this a kernel or ROM issue? If I'm only on the call for a minute the proximity sensor works as it should.
[One (M7) Original Android Development] Batskoning:
I changed it with trickster mod :) This was a example, i only changed the values to these ones..

So it is intellidemand with these values..
[One (M7) Original Android Development] jerrylzy:
DO NOT turn off mpdecision unless there is another hotplug driver built in kernel, otherwise all cores will be online and you will suffer from extreme heat and power consumption.
[One (M7) Original Android Development] FangorX:
Wow, this is by far the smoothest I have ever seen an Android phone run. 3.1 is perfect for me so far performance-wise and the battery life is excellent as always on ElementalX. It can't get much better than this!
[One (M7) Original Android Development] kazemitsui:
Great news on the fix! for s2w. I was gonna post before I went to bed saying that s2w seems to be lacking and unresponsive sometimes in 3.1 compared to previous releases. I myself didn't have problems in 3.0, but 3.1 I definitely noticed that the s2w and logo2wake was not as great...
[One (M7) Original Android Development] michmeister:
What's the fix???

Sent from my HTC One
[One (M7) Original Android Development] kazemitsui:
he said he thinks he found it and will incorporate it into the next build. which is not out yet. so whenever that is, we just gotta wait and see
[One (M7) Original Android Development] michmeister:
Ok thanks so much for quick response.

Sent from my HTC One
[One (M7) Original Android Development] kazemitsui:
no problem hopefully its out soon! as I just kinda reverted back to using my power button on 3.1 haha
[One (M7) Original Android Development] michmeister:
Me too. :)

Sent from my HTC One
[One (M7) Original Android Development] nickabbott:
Excellent news thanks flar2. Hopefully this is the same for bulletproof as well?

Definitely keep the anti picture taking mod I had that a few times and my phone had 30+ screenshot images!!

This kernel will be perfect soon it takes time to fine tune and get there but it's great testing along the way! :)

Fun and games will begin when HTC release proper 4.2.2 sources and break / fix things all over again!!