yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] hamdir:
[MENTION=4684315]flar2[/MENTION] I've been jumping between 2.2, 2.4 and 2.7

I can confirm two things, on both 2.2 and 2.4, they are unable to playback a video recorded in 60fps by this phone in the gallery, they stutter and hitch a lot, but thankfully it plays it fine like stock kernel on 2.7, I tried back and forth a dozen times to confirm it

However with 2.7 I'm still getting the GPU 200mhz sticky problem after kernel install despite GPU OC being set at 1 in the config file! However I can raise it successfully to 450 using faux123 kernel, I uninstalled all my kernel apps and rebooted the GPU gets stuck at 200 again

I also have a suggestion, can you do a 400mhz step along the 450mhz one? Right now its either 320 or 450, maybe there is an internal kernel call trying to set it to 400 and when it doesn't find it, it drops all the way to 200?
[One (M7) Original Android Development] donmarkoni:
Concerning GPU freq not sticking... It just happened to me with v2.70b6.

Actually, none of the settings stick (checking it with Trickster and manually in appropriate files). Non-sticking are ones changed from default, BLN, DT2W, L2W, L2M, and GPU freq that is stuck at 200, which is not default. :eek:

Tried few things like renaming 99elementalx to 98elementalx under /etc/init.d, reordering commands in it (GPU OC before fstrim), but just changing sleep 10 to 20 or more fixed it. Strange... :confused:
[One (M7) Original Android Development] __:
First: Thank you for still working on it, to make it run as it is intended to.

Had never experienced any stuttering.

But in 2.7 I notice the temperature of the device rising, though I set all values in aroma to the lowest and extra cool.

Any idea?

Thank you for your willingness to keep working.

XDA and our phones are living on Developers like you.

kind regards
[One (M7) Original Android Development] cee43ja1:
I thought I was the only one going crazy over the GPU clock but [MENTION=2977387]donmarkoni[/MENTION] and his sleep 20 suggestion actually fixed it! I tried [MENTION=4684315]flar2[/MENTION] suggestion of sleep 15 first, but it still locked at 200. max_gpuclk shows 450, and after benching with antutu, gputime_in_state shows activity with 450, 320 and 200.
[One (M7) Original Android Development] :
Re,

Flar2, thanks for your work and your support ;)

A little beer or a coffee (or what you want :D) : Paypal transaction number: 40480490FU773261R ;)

:)
[One (M7) Original Android Development] Infliciton:
I just got a speeding ticket!

2.7 flys!

ViperOne + 2.7! Wreckshop! :)
[One (M7) Original Android Development] poondog:
confirmed the video playback! I didn't realise it was Kernel related but I guess it is

What I did notice was that having a 800mhz min clock (max was 1350) stopped the stuttering, obviously running it at a higher freq

These videos were taken with the camera app, with the fast video (720p 60fps or something)

Rom was trickdroid 8.0 but no problems on kernel 2.7

As for gpu I guess it can be set in the aroma only, for 400 or 450

Or the init.d script
[One (M7) Original Android Development] hamdir:
Do u mean sleep in the display settings? Waw
[One (M7) Original Android Development] cee43ja1:
In the 99elementalx script fount in the /system/etc/init.d folder. Near the bottom, before the GPU settings, there will be a "sleep 10" line. Changing it to "sleep 20" and rebooting fixes it.

However, it will not stick if you do a dalvik cache erase in recovery; it requires a reboot after the system is booted.
[One (M7) Original Android Development] mwilky:
Nope itl be the command sleep 20 in the script file, you probably remember on one x we had to sleep 60 before we could set things at boot
[One (M7) Original Android Development] tiny4579:
Sorry but power saver mode reduces CPU only when it's on and even then only when CPU is actually selected in power saver. Otherwise nothing changes. This is no different than having fast charge as an option. Basically what [MENTION=4684315]flar2[/MENTION] is saying he can fix power saver so its optional CPU reduction functionality works.
[One (M7) Original Android Development] hamdir:
Yup sleep 20 worked now the settings stick and 60fps videos are now finally playing smooth as butter, 2.7 was all worth it
[One (M7) Original Android Development] evilmastr:
Well said and true. It won't affect anyone who doesn't use it.

T9'd from my black HTC One M7
[One (M7) Original Android Development] donmarkoni:
Yes, yes, you are both right, but...

I think I will not bother posting any more on that subject, as flar2 already found a best path for his development, and cause people just don't read what is written, but what they want it to be. :(
[One (M7) Original Android Development] evilmastr:
Don't be scared. If it works, it works. Have some faith! That quote really doesn't say much about what the possible drawbacks may be - if any.

T9'd from my black HTC One M7
[One (M7) Original Android Development] carlos67:
Ok, time for my obs.

If you want your phone to be like greased lightning, and I mean ragging it to death without a single, single hint of any lag anywhere. I mean the perfect Android experience, try these settings, just out of curiosity before going back to your battery saver settings.

1. Stock CPU clocks (384~1728) with 50Mv UC on 384MHz only.

2. MPDecision off

3. Intellidemand governor with noop scheduler

4. Sampling rate 10000/up threshold 65

5. GPU 450MHz with performance governor. (make sure you set sleep to 20 instead of 10 in the init.d script and reboot)

6. Readahead size 2048

7. Stock minfree settings

With these settings I simply cannot get it to lag anywhere. It becomes the fastest phone I have ever used and goes beyond even the purest butter. This is the Android you dream of.

However! guys, nothing in life is free right? It will consume more battery!

But for me I only go on my phone in short bursts throughout the day for perhaps 10 minutes or so, so for me personally with my pattern of use, battery life is a secondary consideration. A flawlessly smooth UI is where the game is. I have mild OCD and seeing lag/stutter disturbs me and makes me feel like I have an inferior phone. These settings will show you how Android should have been all along. With these settings I challenge each and every one of you to find any lag/stutter anywhere.

Try it! You can always go back (but I bet you don't ;))
[One (M7) Original Android Development] iElvis:
DO NOT turn off MPDecision with this kernel. You can't turn it off unless the kernel has something to replace it with. Otherwise, you're going to have all four cores awake all the time, in addition to other problems. There are kernels that support turning it off, but this isn't one of them. That's likely what's responsible for most of your battery drain.
[One (M7) Original Android Development] c5satellite2:
Flar, s2w needs some tweaking. Ever since the kernel was switched over to the new base, s2w has been quite unruly. Wakes up in my pocket all the time and wakes up when I take it out of my pocket over half the time. I never had this problem on the 4.1.2 elementalX kernel or with elementalX on my HOXL. I know at least one other person commented on screenshots being taken while the phone was in their pocket, this has been happening to me also, and with the case I have on it is impossible the power button is being pressed. I have tried pocket detection, and s2w doesn't work the majority of the time to wake the phone when it is dark. I have had s2w without pocket detection on this phone and the HOXL without issue for over a year. I am only having issues with it since the new 4.2.2 kernel base.
[One (M7) Original Android Development] smartanks:
Just want to confirm , while installing 2.7 , do you guys also see the version listed as 2.6 in aroma?
[One (M7) Original Android Development] dgtiii:
Yes. Change log in Aroma is for 2.6, but you are flashing 2.7
[One (M7) Original Android Development] FangorX:
I don't understand why people turn MPdecision off and sacrifice half their battery life to get slightly better performance. I accidentally had MPdecision turned off when I tried this kernel due to trying Faux's kernel previously, and the battery life was terrible until I figured out the culprit. Battery life is a lot more practical than a smoother UI.
[One (M7) Original Android Development] godofwar424:
I dont understand what crap people have on their phones for MP Decision being enabled to cause lag.. Its stupid, MP Decision doesn't cause any lag for me at all!

On a random somewhat related note, [MENTION=4684315]flar2[/MENTION] is there any chance of the hotplug system found on the TeamSeven kernels? When I was running AOSP I was using it and found the ability to control the hotplugging method extremely useful, especially when I was camping for a couple of nights and wanted my phone to be responsive but control when cores activate ect.
[One (M7) Original Android Development] __:
sorry

Seems to be a rom related Issue. :o

I will report later, after testing.

thanks

kind regards
[One (M7) Original Android Development] flar2:
Do you happen to have volume button wake enabled? It's enabled by default on some ROMs and is way too sensitive. Every time I picked up my phone it was on. In combination with the capacitive buttons, it will also take a screenshot. Beyond that, I haven't actually changed the s2w code in a long time and it's been working well for me at least.

I think I know of a way to prevent screenshots. Any power event + the home button while the screen is on can trigger a screenshot.
[One (M7) Original Android Development] flar2:
I began work on a hotplug driver early on, but didn't continue because I find mpdecision to work well. I haven't examined its behaviour too much since the 4.2.2 update. It has changed since, and if I find it's not working as well as before, this may be something I revisit.

Which brings me to the problem with powersaving mode. I took a quick look at why powersave wasn't lowering the CPU to 1134, and it's because the frequency limiting in powersaving mode depends on thermald. I have thermald disabled, so it doesn't lower the frequency. This seems to have changed since 4.1.2.
[One (M7) Original Android Development] godofwar424:
I see, I found that although MP-Decision works very well, the manual control offered in the Hotplugging for TeamSeven AOSP Kernel made things a bit better, if you wanted battery life you could just raise all the thresholds that cores would require before turning on ect. As well as choosing how many cores are active upon touch inputs and even set the maximum allowed frequency while the screen is off.

Just be nice to have the option, but no pressure or rush or anything, just a suggestion.

PS. Back on your kernels and Sense, LOVING IT! Latest 2.7 beta is very impressive!
[One (M7) Original Android Development] __:
experiences

Good afternoon [MENTION=4684315]flar2[/MENTION],

as you already know I am on InsertCoin. And I do not use volume button wake at all. But taking screenshots via touch buttons and/or logo and/or screen is working! :confused:

The thing with the screenshot is very interesting! Would be nice if you could control this feature. :D

With the following settings in AROMA:

s2w,

proximity check,

l2m,

all values to the lowest,

extra cool,

no double tap to wake,

no logo hold to wake

I got it working, when I held my device in landscape I swiped the whole finger (not just the fingertip) from the bottom of the device over the touch buttons and the screen to the top of the device.

Could someone confirm this, please?

kind regards
[One (M7) Original Android Development] Beremus:
I was wondering, does the hotplug from franco (N4) could be merged to the One? I had a N4 before and his hotplug was terrific.

EDIT1: I hope powersave will be fixed soon! :)
[One (M7) Original Android Development] jerrylzy:
From flar's description, powersaver may never work as long as htc & qualcomm's thermal daemon is disabled.

I think kernel based thermal control is much more important than a fully functioned powersaver.

So flar, if powersaver works at the expense of custom thermal control, just let it be and concentrate on other nice features.

We've been anticipating the greatest release since elementalx:)

Thank you for making our phones fantastic:D
[One (M7) Original Android Development] skulldreamz:
I agree 100% the user of their phone can control when to charge it (car, portable charger, etc...) but we can't control the tempature as easy as it is to plug in a charger. I really hope the whole power save issue gets dropped so you can concentrate on the incredible features that this kernal was going in before this fiasco happened
[One (M7) Original Android Development] smartanks:
I guess this might be related to 2.7 being a beta version .. but after every manual reboot of the phone, when the phone comes back up to lockscreen, it hot reboots automatically... this happens once or twice after which it boots up completely and doesn't crash or have any issues .
[One (M7) Original Android Development] donmarkoni:
I hope you had a good night sleep after making fun of me yesterday. :p
[One (M7) Original Android Development] iElvis:
Try wiping cache and dalvik again. If that doesn't work, flash bulletproof and see if the issue recurs. If not, recreate it and get a logcat.
[One (M7) Original Android Development] smartanks:
well this is only happening in 2.7 .. never had this with any prior release .. will get a logcat for analysis
[One (M7) Original Android Development] c5satellite2:
No volume to wake here, just s2w. Never had an issue prior, always behaved properly.
[One (M7) Original Android Development] nev310:
Every time I reboot s2wake turns off. Also power saving mode doesn't not work for me. It works on bulletproof
[One (M7) Original Android Development] MrKudinGTO:
Sigh... Read a couple of post/page back. There's already tons of discussion on powersave mode and flar is already aware of it.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] flar2:
This doesn't sound like a kernel issue. There is something making Android crash, like a bad setting, or corruption. Assuming you have already tried to reinstall the kernel with safe settings (eg: no overclock or undervolt) I would do a full wipe and reinstall.

Kernel problems cause hard reboots, and I'm very sure that 2.7 is perfectly stable.
[One (M7) Original Android Development] edgarf28:
v.2.7 beta running perfectly here, with 1836 Mhz OC and 450 Mhz GPU OC, and UV of 825 voltage.

Antutu score of: 25994 on stock GE ROM, Highest score i've ever got! :laugh:
[One (M7) Original Android Development] Kay2daCee:
I'm on stock cpu, stock gpu but 750 uv and it is really smooth. running a bit warmer than 2.4 but it doesn't matter
[One (M7) Original Android Development] iElvis:
Easily the best I've ever managed. OC to 1944, GPU 450, intellidemand/fiops.
[One (M7) Original Android Development] c5satellite2:
Putting my finger across the capacitive back and home and swiping up woke it up and took a screenshot. Something is definitely out if wack.
[One (M7) Original Android Development] smartanks:
Well i guess you are right , i just went back to stock kernel and still facing the issue, somethings gone wrong in these couple of days , didnt notice it before i flashed 2.7. i think i broke something unintentionally
[One (M7) Original Android Development] jerrylzy:
I got better result with 1890 & 450 running hot thermal config. Maybe it's so hot that your cpu freq is throttled.
[One (M7) Original Android Development] iElvis:
Maybe, but 25800 to 26300 is not a meaningful difference with Antutu. I've had bigger differences just rerunning the same test.

When I've been throttled, the results dropped in half.
[One (M7) Original Android Development] DeSaint2:
Can confirm. That must be what was happening to me. Pocket detection must have failed for some reason and then came back into contact with my leg(which with as hot as it is here could set of capacitive keys) causing it to take a screenshot. Or in my case 22 before having to hard reboot my phone.
[One (M7) Original Android Development] c5satellite2:
25000 and over is where you want to be. 27000 is definitely the top end of where we can get with OC and hot thermal. 25k-26k is perfect without pushing it too hard.
[One (M7) Original Android Development] qqwe123:
My ext 500gb doesnt work otg. I had stickmount installed. Pls help. Thanks
[One (M7) Original Android Development] c5satellite2:
What type of external? Does it have it's own power supply or is it USB powered?
[One (M7) Original Android Development] NJGSII:
So that's why it wasn't working for me. No big deal, but the funny thing was that I was at the MLB the Home Run Derby the other night bragging about how the power save mode was really helping the battery life. Well it now turns out that it was the optimizations of this kernel that made the battery life awesome.

Props to you, Turge for awesome work.
[One (M7) Original Android Development] qqwe123:
Usb powered. 500gb seagate expansion
[One (M7) Original Android Development] c5satellite2:
You just answered your question. USB powered.

Try a USB flash drive
[One (M7) Original Android Development] skulldreamz:
Make sure your recovery supports otg USB. I use 2.4 w/ cwm 6.0.3.3 and I have a Seagate external that mounts fine. Some times you have to have the ext USB drive plugged in before you boot into recovery and then it will mount. But mine mounts fine even if I plug it in after I boot into recovery and tap mount external sdcard. Hope that helped...
[One (M7) Original Android Development] jerrylzy:
Hi, flar2! I edited ramdisk to enable thermal daemon, and now powersaver works fine.
[One (M7) Original Android Development] qqwe123:
Usb flash drive works fine.

I have also the latest cwmt.
[One (M7) Original Android Development] air2k57:
Thanks for the awesome kernel, very much fast! Is it me or is the max output of the speakers lower with it?
[One (M7) Original Android Development] Visentinel:
Ok this post might seem strange A. because im a hardcore techy and likely wont have my phone for more than 18 months and B. im saying to a bunch of hardcore techys who unlikely care about this... But i feel i must mention it anyway :laugh:

I think its a bad idea with the HTC One specifically to use Hot thermal profile and + Overclock to much producing heat because i have looked at the iFixit guide and other teardowns of this phone and the battery is so far wedged deep into the guts of the phone its virtually impossible to ever change the battery and also if you look at the position of the battery is pretty much pressed up against the mainboard.

Point is guys, heat is a LI batteries worst enemy, your going to shorten the lifespan of the battery allot heating the poor bugger up so much, im OCed a little but im going with very cool profile and let it throttle if it needs to, basically i can get a short burst of screaming performance for 5 to 10 minutes which is usually how i use the phone during the day anyway unless im not working that day then yeah i use it allot, but the thermal setting will prevent much heat build up.

Just be careful guys thats all im saying. I feel i should point this out just incase it helps our XDA Brothers and Sisters who arent aware of this design featureLimitation keep their phones healthy for the long term if they intend to keep this phone for 2 years on a contract.

There is more i can go into about prolonging battery life (battery Life as in the physical item itself no the % on the screen), but im sure you all already know them like what constitutes a charge cycle etc...

Good Luck everyone, and FLar2 i love your kernel :)
[One (M7) Original Android Development] uggies:
International version of the htc one.

sweep2sleep/wake doesn't work...

:(:( help
[One (M7) Original Android Development] HjasToneC:
seems like every wake/sleep feature doesnt work on my unlocked htc one...(using android revolution hd)

can anyone help me:(
[One (M7) Original Android Development] mikbe:
Wake functions won't work if device deep sleeps. Or it takes multiple taps/swipes to wake.

All settings default in aroma and IC 3.0.5
[One (M7) Original Android Development] Visentinel:
What he said. It's a fair tradeoff for prolonging the hardware button.

It's not that bad tho, usually longest it lags for me with logo2wake is 2-3 seconds
[One (M7) Original Android Development] erto90:
Flar, i come from an s3 and i remember there was a very good kernel,developed by AndiP

His force point was the zzmoove 0.6 governor, was really really good

Can you put an eye on it?

Kernel name is Boeffla

http://xdaforums.com/showthread.php?t=1964572&page=536

Don't know if is also because of something exinos related, but maybe works great also on snapdragon!
[One (M7) Original Android Development] Giblet-dono:
Governors have to specifically be tuned for a device. which mean that implementing the governor as is would not be a problem but it would not perform well, and it would not be battery saving..

Flar would have to tune the governor to the device which could take a LONG time, you would have to edit values and test every time.

Because it is so time consuming most developers dont bother with it very much.

Besides everyone wants a different governor.

Intellidemand for some, smartmax for others and so on...

Also to get the same battery friendliness you coudl try using the powersaver or the conservative governor already implemented in this kernel.
[One (M7) Original Android Development] erto90:
you right, was thinking about that,but not really sure;)

But as i owned really lot of phones, and every phone had different governor good for, my brain is so confused and haven't thought about every governor tune to works well with a specific device
[One (M7) Original Android Development] Giblet-dono:
You could try using SetCPU with my profiles file:

http://hostr.co/7vZuADeILuqo

It is specifically made for this kernel, and has profiles for most used apps.

Place the file on the root of your SDcard.

Go into setcpu got to profiles, select restore from sdcard

select the file

enable profiles

and see battery life improve

For me it gives me nearly 2 days of baterlife losing about 1% over night

and in the two days about 4 hours screen on time (quite dark)

Also about 3 hours of music and about 30-60 minutes of gaming.

Others can use this file and edit it as nessecary!
[One (M7) Original Android Development] akarol:
Considering how SetCPU has been around for at least 5-6 years now, I would have to go ahead and say that it IS NOT specifically made for this kernel. Neither is this kernel specifically made for it. It's just compatible with each other.
[One (M7) Original Android Development] Giblet-dono:
I think you misunderstood.

I did not say SetCPU is made for this kernel, I said:

The profiles script is specifically made for this kernel.

It uses the governors, and frequencies in this kernel.

As such it is made for this kernel..
[One (M7) Original Android Development] Pointlol:
Read carefully, he's not saying setcpu is, but that the profiles he's made are.
[One (M7) Original Android Development] iElvis:
Anything that requires power won't work OTG on its own. You need a USB y-cable and an external battery.
[One (M7) Original Android Development] threetwentyfizzle:
Been playing around with 2.7 for the last couple days. And found that setting the TCP congestion governor to Westwood with Intellidemand Cpu governor, Fiops IO scheduler and SD read ahead at 256 gives me lightning speed with ultimate smoothness. Not sure if that will give me batterywise, but will test out and report my findings. loving 2.7 Flar, ultimate butter!
[One (M7) Original Android Development] flar2:
Yes, it makes powersave work, but breaks thermal throttling (there is no throttling at all if you do this)

The only one I can reproduce is two very fast swipes from left to right sometimes takes a screenshot.

I have some stuff that will lower the chances of this happening in the next version, but it can't be totally eliminated unless you turn off the option to take a screenshot with power+home.