yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] biffsmash:
Hi

Does anyone actually know whether the proximity sensor issues are caused by Rom, Kernel, or even if they are hardware issues? I'm on 2.4 of this kernel and still having the exact same proximity sensor issues as I had with every other Rom and kernel :'(

Considering going back to stock 4.1.2 so I don't have to keep flashing every time a supposed fix comes out as none of them work

Cheers
[One (M7) Original Android Development] alexdiaz:
I can confirm that 2.6 runs a bit smoother than 2.4.

Stock freqs, no uv.
[One (M7) Original Android Development] DeSaint2:
Did you not once after install or did you reboot a second time like it says in aroma?
[One (M7) Original Android Development] flar2:
What exactly is the problem?
[One (M7) Original Android Development] poondog:
It rebooted itself twice lol I assumed that was it

I'll try again though thanks

Sent from my Ice Cold Nexus 7
[One (M7) Original Android Development] DeSaint2:
No problem. I just installed rebooted twice and trickster shows gpu 400. It always shows 200 on first boot. Second boot puts it to the right level.

Edit: can confirm capacitive keys goes to sleep during calls now. Thx flar amazing work yet again.
[One (M7) Original Android Development] poondog:
Must be the reason cheers :)

Sent from my Ice Cold NEXUS 7
[One (M7) Original Android Development] hamdir:
[MENTION=4684315]flar2[/MENTION] actually i just tried 2.6 and my GPU is stuck at 200mhz, even after reboot, very bad scores in GFX bench

update: the problem isn't there in 2.4
[One (M7) Original Android Development] flar2:
Yes, I know. For some reason the init.d script is not setting the max.

I will fix this later, for now you have to set it to 450 manually.
[One (M7) Original Android Development] hamdir:
in faux app it doesnt see the clocks

in trickster you can set it to 450 but it reverts back to 200
[One (M7) Original Android Development] evilmastr:
You can change it with trickster mod until flar fixes it. :)

T9'd from my black HTC One M7
[One (M7) Original Android Development] flar2:
You can probably just re-run /etc/init.d/99elementalx to set it. Or open the sysfs entry and set it manually (max_gpuclk or seomthing like that)
[One (M7) Original Android Development] hamdir:
im fine ill stick to 2.4 until 2.6 is out of beta :)

never had the stutter thing, or is it specific gaming?
[One (M7) Original Android Development] biffsmash:
Hey Flar. Basicall during a call, sometimes the screen won't go off when you put it up to your ear, and other times, when the call is ongoing and you take the phone away from your ear the screen won't light back up even when you press power button.

I have had to restart my phone after a few calls as the screen stays dark.

I'm not sure what I'm doing wrong although I'm sure it's something I'm doing wrong.

Appreciate to replying to me directly :)
[One (M7) Original Android Development] DeSaint2:
The people complaining of stutters are talking about in the general Ui mostly.
[One (M7) Original Android Development] hamdir:
never had it on 2.2, it's buttery smooth

not seeing any on 2.4 so far
[One (M7) Original Android Development] jlevy73:
I'm sure I'm missing the obvious, but where is 2.6 posted. Spent 20 minutes searching to no avail.
[One (M7) Original Android Development] rnrstar:
http://xdaforums.com/showthread.php?p=43604690
[One (M7) Original Android Development] arhung:
I have difficult in choosing kernel, bulletproof or elementalx? Seem both of them are the best...
[One (M7) Original Android Development] Skizzy034:
Will choosing cool or extra cool thermal options in Aroma make the device feel and run cooler?
[One (M7) Original Android Development] flar2:
They're talking about when you flick to scroll a web page or something, there will be a slight stutter occasionally. I never even noticed it, but I use Boat Browser, which I've always found a bit choppy compared to other browsers and it never bothered me.

Game performance should be same as always.

I've never had this problem. I haven't followed all the different firmware versions out there (If my phone works, I never flash new firmware), could be related to firmware version or something.

I don't know if it will feel cooler to the touch in general use, but it won't get as hot under load.

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

Also, could a few people try the 3-dot menu options in 2.6 beta, I have new scripts but haven't had the time to test them really.

There's so much to test and so little time, I'm probably going to assemble a beta team soon.
[One (M7) Original Android Development] Skizzy034:
What do you recommend? The default option or one of the cool ones?
[One (M7) Original Android Development] flar2:
My recommended settings are the defaults (for all settings)
[One (M7) Original Android Development] Skizzy034:
Ok thanks. It's just that my device is hitting about 110 just browsing xda and the web so I'm looking for anything to change to keep it cooler.
[One (M7) Original Android Development] smartanks:
I am not sure if i have the problem , i selected 450 mhz in aroma during install and it shows up as 450 in trickster . Are you sure you selected 400 mhz in aroma?
[One (M7) Original Android Development] DeSaint2:
Those having issues with gpu clock, did you manually wipe cache and dalvik?
[One (M7) Original Android Development] threetwentyfizzle:
After manually applying the gpu clock to 450 in trickster, all is smooth again. At the clock of 200 on the first couple boots, screen rendering was real jittery, but it has smoothed out once I put it back to 450. One thing tho, the 450 setting didn't Stick with the reboot, I had to manually go back in and change it in trickster again. anyhow, 2.6 is running pretty fluid for me atm.
[One (M7) Original Android Development] flar2:
That's very normal. The run cool option isn't going to lower it more than that, otherwise it would be throttled all the time.
[One (M7) Original Android Development] VacTacks11:
Hey hoping someone can help me.

Flashed this kernel, and it works great, but the Aroma installer doesn't recognize my finger when I try to tap on the screen. I have to navigate using the volume and power buttons, which is kind of a pain.

Has anyone else come across this? The kernel itself works just fine.

Running the Telus HTC One.

Thanks
[One (M7) Original Android Development] vikstk:
Are you using Chrome? I've found that Chrome often hogs multiple cpu cores even after page is completely loaded and no finger on the screen. Therefore phone gets hot. Stock htc browser doesn't do that - and phone stays much cooler. NY times website on Chrome is especially bad(hogging the cpu).
[One (M7) Original Android Development] threetwentyfizzle:
I ended up reverting back to 2.4. There are some "jitters" I'm still experiencing when swiping from homescreens or the app drawer and really bad in facebook. Overall, I think 2.4 is pretty darn smooth as is. Just thought I'd give my feedback for you all. My options in 2.6 were 1836 cpu, 450 gpu, 750 uv, and normal thermal throttleing.
[One (M7) Original Android Development] flar2:
I've never had any jitters or stutter swiping the app drawer or homescreens. That is probably due to other mods or ROM stuff.

Or just simply disk or memory i/o.

The only stutter I've been able to find is swiping through web pages, and it only happens sometimes. And I've tried many variations of ElementalX, Bulletproof, the stock kernel. Like I said, there are a million things that can cause a stutter. If you start obsessing over it, you will find lack of smoothness. It's literally impossible for it to be smooth 100% of the time.

I have Viper installed and I don't mess around with a lot of mods and constant flashing and it's smoother than any phone I've ever used. I don't consider this to be a problem. In any case, there's nothing I can do about it and still have all the options.
[One (M7) Original Android Development] skulldreamz:
Kernels take a while to settle. If anyone experiences a problem that is not a big deal I would wait a week at least 3-4 days and see if that problem starts to get better. In my testing problems seem to melt away with time usually

Battery improvement, lag, random reboots, etc...
[One (M7) Original Android Development] threetwentyfizzle:
It's all good flar, I was just giving my feedback on 2.6, I'm on viper, and I think it may have something to do with the initial gpu setting that I have to change with trickster that is causing that jitter. My app drawer and blink feed are not transparent either, as I know transparency causes issues. When I reverted to 2.4 the jitter was gone. To elaborate, the app icons in the app drawer start to become shaky when scrolling, and the smoothness is gone. And the images in BlinkFeed are experiencing the same effect when swiping horizontally from the homescreen to it or when scrolling vertically. It's very smooth on 2.4 and don't experience any of those visual glitches. If there is any settings to try in 2.6 I would be more than happy to test for you and report back.
[One (M7) Original Android Development] dgtiii:
flar2,

I could not agree more. Thank you for all of your work on this great kernel. The One is my first Android phone, coming from years of owning iphones, and I could not be happier. Also running Viper, and by far this is the smoothest phone experience I've had. I was smooth on ElementalX 2.2, 2.3, 2.4, and again on 2.6 - I really do not see this micro stutter issue. Not saying it's not there, I just do not recognize it. I think there are so many variables between UV and OC combinations that not every issue is going to be repeatable for everyone. For example, I was having issues with DoubleTap2Wake, running 1728 while UV to 7.25. The phone seemed to run fine, I actually thought Viper was interfering somehow with DoubleTap2Wake. Then it dawned on me, I raised UV to the default value, and have had no issues since. My point is that every phone is different, and it really takes a lot of testing on the user's part to get everything functioning just right. An improper UV/OC setting can cause weird issues, even if it looks like the phone is handling it.

I for one am good on 2.6, just need the init.d settings sticking when you get to it. Thanks again for this awesome kernel sir!
[One (M7) Original Android Development] flar2:
I've never seen blinkfeed or the app drawer stutter at all on any of the roms or kernels I've tried.

It's not that I don't believe you, I just don't think it's related to the kernel. The fact that you're seeing a difference moving from one kernel to another does not necessarily mean it's the cause. There are just many, many things that could cause that. For example, background processes or things being kicked out of memory that have to be read from the disk again. To test kind of stuff you really need to use each kernel for a few days. Sometimes I feel like I get a bad reboot, where things just aren't right. Then I reboot again and it's fine (when I'm testing stuff, I sometimes reboot dozens of times a day).
[One (M7) Original Android Development] EnIXmA:
My phone is getting really hot while on data with the new experimental build, It stays cool while on wifi. Any one else experiencing this as well?

thnx
[One (M7) Original Android Development] threetwentyfizzle:
Yea I think I should give it some time to settle in. Sorry if I seem like I am knocking the update, I'm just giving my impressions on it to help further the development on it. I think I'll try it again later tonight and give it a few days and report back. In no way am I dissing this kernel, I am a loyal elementalx user since the one xl, and know you don't release anything that is short of stable :thumbup:
[One (M7) Original Android Development] flar2:
No worries. You might as well just wait for 2.6.1 or 2.7 (haven't decided yet how much I'm going to do). I have to at least fix that problem with the GPU maxing at 200MHz
[One (M7) Original Android Development] FangorX:
[MENTION=4684315]flar2[/MENTION] I don't know why so many people mention this stutter to be honest. I didn't even notice it until I read about it in the thread, and even now it doesn't bother me. I think most of the stutter is either due to other mods or just the app itself, or maybe the ROM. Even the stock kernel stutters sometimes and the only time I have ever seem this phone never stutter is when I set the governor to performance and disable MPdecision (maybe a different governor like interactive would help?). Android just lags sometimes. I don't really care if it gets fixed, either way the kernel is amazing and the smoothness is more than acceptable, especially considering that you don't have the source code..

I bet some of the microstuttering will be fixed in the future with newer sources from HTC
[One (M7) Original Android Development] flar2:
I wouldn't even call it lag. We're spoiled because this device is so responsive. I think we're just noticing when it's not 100% smooth. I can't even stand to use my tablet anymore.
[One (M7) Original Android Development] Tabtoub:
I bought this device mostly for its lag free experience, I watched many reviews and hands on videos and almost every reviewer mention the amazing smoothness and the fact that it NEVER lags, and then when I bought it I wasn't disappointed because it was true, the phone flies..

After trying some custom roms, I now ended up by reverting to stock rom with only a custom kernel (bulletproof, this kernel is amazing) and the lagfree experience is back, the phone is flying and it's a pure joy to use it :D

That's why I cannot tolerate any lag/stutter anymore ;)
[One (M7) Original Android Development] donmarkoni:
One beta tester here, if needed. :D

3-dot menu key removal working fine, no repeated entries. :good:
[One (M7) Original Android Development] kazemitsui:
i would have to agree with you on that [MENTION=4684315]flar2[/MENTION] ! my nexus 7 when I first got it a half year ago was a major upgrade on my then current phone the NexusOne. But now that I have my One... its like N7 if only you could be as smooth and responsive as the phone haha

BTW has anyone tried playing Pocket League Soccer 2... this game lags on "High" settings with the One, but on my tablet its flawless. I tried it on other friend's phones and my brother's S3 it lags on high too.. wtf
[One (M7) Original Android Development] DeSaint2:
I'll beta test for Ya flar. Usually updated to your newest as soon as it's up or when I wake up lol.

---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------

Not been optimized for s600 most likely. Or more specifically adreno 320.
[One (M7) Original Android Development] kazemitsui:
Bah thats just dumb haha. Now I just need someone on an S4 to say it lags and that should confirm it is not optimized right?!
[One (M7) Original Android Development] DeSaint2:
Correct, as long as it is adreno 320 so s4pro soc or s600
[One (M7) Original Android Development] Balikesirli:
[MENTION=4684315]flar2[/MENTION]:

Can you add 320Mhz GPU and CPU governers in aroma, please? :)
[One (M7) Original Android Development] iElvis:
Don't know about GPU, but flar has already stated that he won't add CPU underclocking as it does nothing and degrades performance.
[One (M7) Original Android Development] shree.cse:
Afaik 320 is the min value for cpu.
[One (M7) Original Android Development] flar2:
CPU min is 384

GPU steps are: 200, 320 and 400 (450 if oc'd)

You can change the max_gpuclk to 320000000 if you want, but it won't make much difference because the gpu speed scales with use.

Look in the directory:

/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/

There you'll find max_gpuclk and other stuff like gputime_in_state, which shows the time spent at each frequency. Mine spends most of its time at 200.
[One (M7) Original Android Development] skulldreamz:
Very interesting... I was just looking at gputime_in_state and this was my reading>450000000-0

320000000-258

200000000-655777

20000000-0

So I guess even though I overclocked my gpu to 450 it never has even hit that decimal once during normal use of my everyday activities on my phone.
[One (M7) Original Android Development] kiroen:
Love this kernel,sweep2wake better than before
[One (M7) Original Android Development] cee43ja1:
I just checked max_gpuclk, and it was set at 200, eventhough i chose 450 in aroma. And gputime_in_state shows only activity at 200. 320 and 450 have no activity at all; straight zeros.
[One (M7) Original Android Development] flar2:
Yes, this has been discussed. In version 2.6 the script is not setting the max. I haven't had a chance to fix it yet.
[One (M7) Original Android Development] DeSaint2:
So, has anyone experienced in issue where while the phone is in the pocket, it starts taking screenshots? I actually had it really bad today. Heard it start doing it and it wouldn't stop. It took 21 screenshots before I had to manually reboot cuz every time I would get the power menu open it would take a screenshot and close the power menu. Couldn't get a logcat. Running 2.6 on arhd 12 with only modaco toolkit mod for apm
[One (M7) Original Android Development] cee43ja1:
Oops. Must have missed that post. But even with a 200mhz gpu, there aren't any stutters with the UI. GPU intensive games might take a hit.

No screenshot problem here. Sounds like the power button was being held down. Is pocket detection working for you?
[One (M7) Original Android Development] DeSaint2:
Ya but for some reason every other day it will start taking screenshots in my pocket. Only started after flashing ex. It has only done it while standing with the screen off with nothing pressing on the phone.
[One (M7) Original Android Development] donmarkoni:
Hmm... Mine is working at 450MHz. Could it be because it was set by previous version?
[One (M7) Original Android Development] flar2:
I haven't had the screenshot thing. I have s2w, dt2w and pocket detection enabled, and my phone is set to take a screenshot if you hold the power button and press home.

Can you find a way to replicate the screenshot scenario? Is it specific to 2.6, or was it happening on 2.4?

I think it's a timing issue, in computer parlance, a race condition. Sometimes the script will set it, other times it won't. On mine, since 2.6, it never sets it to 450.
[One (M7) Original Android Development] DeSaint2:
2.4 as well but I figured it had to do with the screen not going to sleep. It's random and when I'm not using it so unfortunately I can't really replicate it.
[One (M7) Original Android Development] lichti1901:
All i can say is WOW, just wow.

Never got such a nice battery time before and all over 3g!

Well done Flar2!

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] crushalot:
flar2,

Great kernel. 2.6 seems it is even better battery life than 2.4.

One small thing that seems to only happen on your kernel is that setting for ringtone and notification volumes seem to not have many steps. I use Viper and even with the default of 7 volume steps ringtone on level 1 or 2 is very LOUD. Increasing the number of volume steps by venom tweaks only makes it worse.

Also can't seem to separate different volume values for ringtone and notification, as if they are locked to be the same.

I saw another viper user who was using your kernel have the same issue. Could you see if it is a bug?

Thanks
[One (M7) Original Android Development] flar2:
I just tested by setting the volume steps form 7 to 15 in Venom Tweaks and it works fine. The lower steps are very low volume.

As for the ringtone and notifications being the same slider, is it different on stock kernel? I never paid attention. If there is a difference, it's probably because this is actually based on the source for Google play edition.
[One (M7) Original Android Development] oseienoch:
Issue With ARHD 12.0

Im on the version 12 of Android Revolution HD with some Xposed tweaks applied, But with flashing all default settings on TWRP the installer just cuts off and reboots back into the Rom with the Stock kernel still present. Do the Xposed modules clash with the kernel?
[One (M7) Original Android Development] skulldreamz:
[MENTION=4684315]flar2[/MENTION] I forgot to mention that I'm on version 2.4 and same as above, 450 is not getting touched but I know you said its in version 2.6 the script is not setting the max value. So I'm wondering if you or anyone else on 2.4 can check to see if their gpu is ever reaching 450? I didn't know if the script was the same. I have opened it up yet but either way just wanted to let you know. Gaming is great anyway so this is like a placebo effect..lol Thanks man
[One (M7) Original Android Development] crushalot:
Thanks for checking. When I set to 15 steps the first few are totally muted and then when I get to 4, boom really loud and setting it higher doesn't make it any louder. (ie 4 is same level as 8, 10, 15)

I had tried a reflash earlier but it must be some other mod I am using that is causing it.

Just a bummer because all else is perfect but getting a phone call or sms is like a fireman with one of those scanners.
[One (M7) Original Android Development] iElvis:
No, I have three different Xposed modules installed, and I have no issues. Aroma is fluky. How many times have you tried it?
[One (M7) Original Android Development] oseienoch:
Around 5 times now....
[One (M7) Original Android Development] hamdir:
[MENTION=4684315]flar2[/MENTION] I found a bug mate

I use hdr in low light all the time on stock sense 4.2.2 ROM

when using stock kernel if u take hdr in pitch black or very badly lit scenes, the camera will take a moment then grab the shot

however in your kernel, same scenario will always freeze the camera app, if there is some light source in the view finder the HDR will work otherwise it will always freeze the camera

I guess it has to do with using the GE kernel source?
[One (M7) Original Android Development] c5satellite2:
Same here on ARHD 10.3 with elementalX 2.6. Never happened with prior versions of elementalX.
[One (M7) Original Android Development] razer1224:
Yup ur right

InsertCoin Themer - Kernel Dev
[One (M7) Original Android Development] flar2:
This has been known since the source came out. It's a very rare occurrence and the camera works perfectly except in that exact situation (HDR + autoflash in the dark) Probably nothing can be done about it, the camera drivers are totally undocumented
[One (M7) Original Android Development] WinterApocalypse:
Is there a way to use this kernel, but without it affecting the original button mapping settings? I always lose the option to modify the Home Button mapping in settings when installing this kernel, even if I deselect every option that affects the capacitive buttons.
[One (M7) Original Android Development] Johnny424:
Hey flar do you have any plans on adding any lower clock speeds in the future? I mean lower then 384mhz..thank you for all your work so far..:)
[One (M7) Original Android Development] flar2:
Download:

ElementalX-m7-2.7 *BETA*

This one is butter smooth. There was some problem in my code base, I had to start fresh.

Also fixes gpu stuck at 200 and has all the fixes from 2.6

I'm just leaving this as beta for now, because there are still a couple very minor things I didn't have time for.

Let me know how things go with this one.

I intend to have another release very soon, and if it works out, 2.8 will have a very cool new option.
[One (M7) Original Android Development] Skizzy034:
That temp is normal?
[One (M7) Original Android Development] flar2:
Someone posted a workaround a few pages back.

No, it won't make any difference in battery.

Yes it's normal to have temps in the 40 to 45 Celsius range. Even the stock throttling doesn't kick in that soon. Plus, it summer, isn't it like 90 degrees outside lately?
[One (M7) Original Android Development] c5satellite2:
Flar makes an important point here.

Makes it harder to shed heat and the phone is already at 90 deg+ before you turn the screen on. The jump from 70 to 90 deg ambient air temp is bigger than you would think when it comes to shedding heat.