yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] matjmonk:
Flar,

has anyone mentioned any problems with version 1.56 of the ElementalX Kernel app? I am seeing a problem when I go into the GPU -> Advanced Color Control where I can enter a value in the first field but after that the app appears to stop taking inputs from the keyboard. The sliders still work and I can delete what is in a field, just not input a new value with the keyboard. I've tried rebooting and clearing cache/dalvik as well as clearing the App data but nothing seems to help. But the kernel itself is simply awesome and gets better with each update!!

Thanks for any assistance.
[Nexus 6  Original Android Development] flar2:
I didn't add anything becaue it is available through sysfs already, but I can't remember the path at the moment. Maybe someone else can remember

You are right, I'll fix that for the next update. For some reason the focus behaves differently on this phone compared to my others. Weird.
[Nexus 6  Original Android Development] jamiethemorris:
Found it, it's /sys/module/clock_krait_8974/parameters/table_name.

My pvs bin is 13, which I think is pretty damn good. I seem to have won the silicon lottery with my 5960X as well, luck is on my side this year :)
[Nexus 6  Original Android Development] simms22:
no, wrong. thats not your pvs bin number. your pvs bin is located in /proc/cpu/msm_acpu_pvs/
[Nexus 6  Original Android Development] jamiethemorris:
Oh cool, thanks. My pvs bin is 10. Still not too shabby.
[Nexus 6  Original Android Development] teddy sheringam:
Thanks...
[Nexus 6  Original Android Development] Lancez:
Rocking 1.05 on latest LVY47H
[Nexus 6  Original Android Development] danarama:
Still getting a lot of post-phone call BSOD even on LP 5.1. I don't think its kernel related but what else could it be?
[Nexus 6  Original Android Development] toknitup420:
Screen protector? Or maybe the ROM your on.
[Nexus 6  Original Android Development] danarama:
No screen protector, any/every ROM.
[Nexus 6  Original Android Development] flar2:
No idea. I haven't had a single reboot since updating to 5.1 (not that I had them pre-5.1), and others haven't reported them either. I am quite certain the kernel is completely stable.

Do you have any logs? Maybe it's some specific setting or app that you use.

Also, if you're using the s2wphonecalldisabler and/or wake gestures apps, uninstall them.
[Nexus 6  Original Android Development] danarama:
No it's not a reboot. Its when a call ends, the screen doesn't come back on. So I can't hang up ... It eventually comes back after lots or pressing power or pretending I'm going to hard reset.
[Nexus 6  Original Android Development] toknitup420:
That's weird. Have you tried the proximity sensor fix from here.

http://xdaforums.com/showthread.php?t=3069031
[Nexus 6  Original Android Development] danarama:
No.I'll have a look. Thanks..
[Nexus 6  Original Android Development] pantmunu:
The phone not waking up issue . how often is it happening. Just wanted to make sure.
[Nexus 6  Original Android Development] DroidIt!:
Hey [MENTION=2872010]rootSU[/MENTION] No problems on my side with ElX .28 and any Shamu SlimLP build. My dialer always functions properly. Any battery saver apps that might kick in after the screen has been off for awhile that might make the phone go into a deeper state than intended during a phone call. Maybe also look at uv if you do it or maybe max/min cpu speeds while screen is off? I know you're aware of all this stuff, maybe just missed something simple? :)
[Nexus 6  Original Android Development] danarama:
Yeah I've got none of that.

Sometimes its like the screen times out even though its off with prox...and simple press of power wakes... Other times, lots of presses...and nothing. Until eventually something.
[Nexus 6  Original Android Development] simms22:
are you undervolting at all???
[Nexus 6  Original Android Development] danarama:
No. Stock voltage, no screen off Limit.

I don't think its kernel related - I only posted here as I was talking with [MENTION=4684315]flar2[/MENTION] about my issues in general and he was advising to go to 5.1.

I should probably stop talking about it.
[Nexus 6  Original Android Development] DroidIt!:
Nah :) Maybe do an XDA search for 5.1 dialer problems or in whatever ROM you're using...again trying to hit easy stuff. Do you remember if it did it on stock 5.1?
[Nexus 6  Original Android Development] danarama:
Never used stock. It did it on 5.0.2 too. Not always. It just started happening when all the instabilities started to happen.

Not related but before ex, 26, everything was good.
[Nexus 6  Original Android Development] Casper34:
[MENTION=2872010]rootSU[/MENTION]

Flash the prox fix file. I had the same issue, even though I have a screen protector, it does not cover the sensor. After I flashed the fix, all has been good.

Sent from my Nexus 6
[Nexus 6  Original Android Development] danarama:
Yep am going to. Just not til tomorrow
[Nexus 6  Original Android Development] DroidIt!:
Kind of a long shot, but I'm assuming in your switch to 5.1 you flashed the new radio? If not you might try that though strange thing when I flashed the 5.1 radio, I believe it was from the "I" factory image, I couldn't receive calls. Switched back to the 5.0.2 radio and all's good again.
[Nexus 6  Original Android Development] simms22:
and you still havent? if not, you should, as there definitely is an improvement!

edit.. it seems you did 5.1, but are still having the issue.
[Nexus 6  Original Android Development] Admiral2145:
My phone isn't deep sleeping... What app should I get to find out why? Running meanpop 2.10 with this kernel.
[Nexus 6  Original Android Development] Lancez:
Better battery state, and I'm having same wake lock issue with stock 47H. It's the damn system update service, compliment of Google!
[Nexus 6  Original Android Development] Admiral2145:
Is there a way to fix it?
[Nexus 6  Original Android Development] Lancez:
Not that I know of. Old tricks don't work on newest play service anymore. You'll have this wake lock on any kernels even with stock one. Let's hope that Google will fix this soon.
[Nexus 6  Original Android Development] simms22:
im on play services 7.0.99, and my nexus 6 is sleeping like a baby. i didnt do anything to make it sleep..
[Nexus 6  Original Android Development] Lancez:
You meant I've been working too hard to get "laid"? lol

I'll give it a try.
[Nexus 6  Original Android Development] Admiral2145:
Your running 1.04 any reason why your not running the latest kernel?

My play store is 5.3.6
[Nexus 6  Original Android Development] simms22:
i dont remember the change in 1.05, but i remember it wasnt important.

edit.. ok, i looked, and i was right! it added multirom support, and i dont use multirom :angel:

my play store is also 5.3.6
[Nexus 6  Original Android Development] Lancez:
Well, deep sleep is back! Yeah......

[MENTION=2997316]Admiral2145[/MENTION], see attachment ;p
[Nexus 6  Original Android Development] simms22:
there you go.. :)
[Nexus 6  Original Android Development] wrongway213:
I'm curious, I've seen your settings all over and know they work well for many people. I see you raise thermal throttling from 70 all the way to 95. I've noticed if I raise thermal throttling on many kernels, this included, to 80 or even 90, it performs better than at 70. However, it seems 70 is the default on basically all kernels I've found. This makes me wonder if there's good reason for 70 in particular. I've been asking around and so far I've heard running the CPU at high temps can be damaging, which I figured, but no real specifics, let alone device specifics. Do you know anything of the risk of running at say 90, or even only 80 instead of 70? I quite prefer it at 90 (80 would even do much better than 70) but I haven't been able to find information on whether it's safe, let alone good, for my phone thus far. If you're able to either offer any guidance or point me to somewhere I can read up on my own, I'd very much appreciate it.
[Nexus 6  Original Android Development] simms22:
i usually just disable it. if i raise it, then its in the high nineties. but it doesnt matter, its usually the same thing. anyways, on all the other nexus, it was very easy to get the phone to 100C, or thermal shutdown. on the n6, its extremely hard! the hottest ive gotten it, while trying to get it hot, was only 83C. so i dont think its possible to get it over 70C with normal use, and keep it at that temp sustained over a longer period of time. most kernels its 70C because stock thermal throttle is at 70C, or 65C.

if you keep your phone over 80C for long periods, over 15 minutes or more, its possible that it mught recieve some kind of damage, but i dont see a way for that to happen in normal use. to try to force it might even be extremely hard.

anyways, i raise or disable thermal throttle because the heat doesnt bug me, and i really dont feel my devices(any) would be damaged. but the final temperature phase remains active, thermal shutdown. at 100C your device will automatically either shutdown or cool off. i havent hit that on the n6 yet, but my n4 and n5 have hit 100C literately hundreds of times.

---------- Post added at 06:23 PM ---------- Previous post was at 06:05 PM ----------

honestly, i dont think any information even exists that i can share. lol :)
[Nexus 6  Original Android Development] paychex:
I wouldn't call 21% deep sleep sleeping like a baby.

Yes. Leave the Google crap alone. Use app oops if an app (ie Facebook) is causing trouble. That's all I do. Everything syncing and after a work day I'm still sitting at 70-80% deep sleep
[Nexus 6  Original Android Development] simms22:
with the way i was using the phone at that moment, it went to deep sleep as soon as i turned off the screen. it was behaving exactly like it should, and not any worse. that for me is sleeping like a baby. a baby isnt going to sleep when you are actively playing with it, but will as soon as you stop. anyways, besides that its only been keeping check for 24 minutes and 34 seconds :p
[Nexus 6  Original Android Development] YankInDaSouth:
Pretty sure this is by design of the ROM dev ...
[Nexus 6  Original Android Development] simms22:
na. no rom designer would ever make the mistake of developing a rom that wouldnt let the phone into deep sleep. the issie is because of google play services.
[Nexus 6  Original Android Development] YankInDaSouth:
You're probably right, just thought I remembered seeing something regarding it the ROM thread
[Nexus 6  Original Android Development] simms22:
its the same issue that many n6 users are experiencing right now, and n5 users as well. there are ways to temporarily fix it, but the permanent fix is for the rom developer to fix. the rom im using fixed it, terminus.
[Nexus 6  Original Android Development] Admiral2145:
Finally got it to sleep... Switched to chroma
[Nexus 6  Original Android Development] simms22:
yup, croma uses the se fix as terminus :)
[Nexus 6  Original Android Development] drawde40599:
What's the issue ? I have two N6' s both on stock ROM one on ElementalX , both updated to latest Play services and Market . I've never seen deep sleep issues .
[Nexus 6  Original Android Development] simms22:
last week and the week before i did. google play services was preventing the cpu frim going into deep sleep, unless you did one of the "fixes", until reboot when it wouldnt sleep again. my n5 also suffered a bit from it. but now both n5 and 6 sleep fine. ill be honest though, i didnt really see any battery issues, like many have.
[Nexus 6  Original Android Development] drawde40599:
I reboot every morning but didn't notice anything . Being a android user since basicly Day one I've kinda learned some days will be better than others , so even if something was wrong if it dosent happen day after day I probably wouldn't notice anyways :P .
[Nexus 6  Original Android Development] simms22:
the only reason i noticed was because others were complaining. i noticed that it just wasnt sleeping, but maybe i saw ½ hour less sot. others really complained because their bayteries got hit hard, not me. anyways, if you have the disable services app, you can enable SystemUpdateServices in google play services, which would put your device to sleep right away. but had to do it after every reboot. clearing the data from google play services would also let my device sleep. anyways, i reboot at least once a day as well :)
[Nexus 6  Original Android Development] mrsweet1991:
Is it possible to not have encryption enabled for faster read and writes?
[Nexus 6  Original Android Development] simms22:
yes, you have to reformat your storage first :)
[Nexus 6  Original Android Development] mrsweet1991:
Thanks Simms 2, I wiped everything (including things in advanced options in twrp) so I was pretty much semi bricked. Anyway got that sorted and managed to flash Chroma, gapps, su and Elementalx in one go however its encrypted. What did I do wrong ? :)
[Nexus 6  Original Android Development] bmwh0r3:
If you formatted everything, I'm not sure why you'd still be encrypted. Are you sure? Look under security. It should say encrypt phone... Not "encrypted."
[Nexus 6  Original Android Development] mrsweet1991:
I enabled a 3033 overclock in the install using recovery but when I open the Elementalx app 2265 is the most I get, in the CPU options 3033 is there but when I select it the over clock won't change. Any ideas?
[Nexus 6  Original Android Development] simms22:
;)

http://xdaforums.com/showpost.php?p=59922264&postcount=15
[Nexus 6  Original Android Development] c@p:
You must use "format data" button in TWRP and apply this with "yes" not "wipe". Wiping does not remove encryption.

Tapatalked with Nexus 6
[Nexus 6  Original Android Development] mrsweet1991:
Hi mate,

Yes its all done now :)
[Nexus 6  Original Android Development] henrybravo:
Hi [MENTION=4684315]flar2[/MENTION], I've been using your kernels and elementalx app for years on the HTC One m7, m8, and now on the Nexus 6. I consider you the "double tap to wake" guy because you've always been good about implementing pocket sensing and stuff like that (I'm using your Wake Gestures app on the N6). DT2W always worked pretty well on the HTC devices, but I've noticed it's relatively hit-or-miss on the Nexus 6 once the phone has been off for more than a few minutes. It seems that about half the time I have to repeatedly double tap to get the phone to wake up and sometimes it doesn't work at all. Just curious if you're seeing the same issue, or if you know of any tricks to get it to work more reliably like on the HTC devices.
[Nexus 6  Original Android Development] purian23:
Honestly his wake gesture stuff really rocks! It's more of the Nexus 6 in my opinion that doesn't handle these commands as well as other devices. I believe flar2 has stated this as well.

For the most time I'm very pleased with the multiple wake options and don't really have any troubles. Hope this helps in a round about way!
[Nexus 6  Original Android Development] henrybravo:
Thanks for the input. Yeah I figured it was the Nexus 6 hardware since it's not a native DT2W device and the problem happens on every ROM and kernel I've tried, but just wanted to check to see if there were any known workarounds that help.
[Nexus 6  Original Android Development] HumpDdumpD:
I'm not sure if it still applies, but I know setting at least one direction on s2w makes the dt2w run like 10 times better. This was a while back, but I still set it for good measure.
[Nexus 6  Original Android Development] danarama:
Does anyone know where the dt2w settings are written to and has anyone managed to manage with tasker?
[Nexus 6  Original Android Development] marcp39:
[MENTION=4684315]flar2[/MENTION]

I just would like to know if it would be possible to have UMS support with LL or is it impossible ?
[Nexus 6  Original Android Development] Admiral2145:
Is there anything in this kernel that will kill apps while screen is off? Or is it a rom issue?
[Nexus 6  Original Android Development] jamiethemorris:
I can't tell if I'm getting random reboots or accidentally pressing the power button in my pocket. Anyone know why I can't get a last_kmesg with syslog? It's grayed out. May be an app issue.

Edit: apparently my ROM doesn't have last_kmsg? Is that a thing?
[Nexus 6  Original Android Development] Casper34:
Dont know about the kmesg things but......

Do you have ambient display turned on? I did at one point and I would change Sirius channel, open apps, and such.

Sent from my Nexus 6
[Nexus 6  Original Android Development] jamiethemorris:
No, I have it turned off.
[Nexus 6  Original Android Development] Casper34:
OK. It was just a thought. Another........ are you overclocked to the Max? If so, tune back the frequency.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Lancez:
not that i know of. check your settings, in developer.
[Nexus 6  Original Android Development] PunishedSnake:
What's the sot stock vs elemental?
[Nexus 6  Original Android Development] drawde40599:
Almost identical , they both get me between 5-6 hours SoT , I can't say one is better than the other for battery. But i can say performance is definitely better on ElementalX .

I tried all available kernels for this device and none of them really gave me any better battery , a couple gave worse actually .

This is my experience
[Nexus 6  Original Android Development] jamiethemorris:
No, I enabled the overclocked settings in aroma so I had the option but I have it set to the stock frequencies with trickster.
[Nexus 6  Original Android Development] danarama:
Does anyone know please?
[Nexus 6  Original Android Development] flar2:
All the wake stuff is in /sys/android_touch. The one you want is:

/sys/android_touch/doubletap2wake

Sorry for the late reply...I've been very busy this week.
[Nexus 6  Original Android Development] danarama:
Thanks very much.

And no problem.
[Nexus 6  Original Android Development] ANDR01DN00B:
Anyone else having problems when using the proximity sensor to detect whether to wake the device or not? It seems to wake with dt2w despite me having it in my pocket.

Thanks.
[Nexus 6  Original Android Development] tealio:
Are you using the Wake Gestures app or do you just have it enabled thru the installer?

I was having that issue when not using the app. The app, however, was causing reboots, so I just quit using dt2w.

I don't know if the app has been fixed...
[Nexus 6  Original Android Development] flar2:
Perhaps try the proximity fix posted somewhere in the forum.

I can't really do anything to fix the wake gestures app. All I do is call the proximity sensor the normal way like any other app.
[Nexus 6  Original Android Development] kornklown69:
hope they have a kernel upgrade with 5.1.1

https://plus.google.com/+ArtemRussakovskii/posts/V8JQoUPaqsB
[Nexus 6  Original Android Development] Lancez:
I don't think the kernel will be different. 5.1.1 is supposed to fix memory leak.
[Nexus 6  Original Android Development] blinqipa:
Dunno if developer [MENTION=4684315]flar2[/MENTION] accepts requests , but I found this feature http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344 to be pretty useful , if not so secure. Between sorry if it irritates the developer to request a feature .
[Nexus 6  Original Android Development] drawde40599:
This is a stock LG feature . I don't know if he will add or not but there is a App that dose this same thing in PlayStore , I remember useing it on my N5
[Nexus 6  Original Android Development] danarama:
How well did it work? What about native pattern lock?
[Nexus 6  Original Android Development] drawde40599:
Honestly I can't really remember, but now that I think about it , it may have stopped working when Google broke "injecting " into stock kernel . so would have been very early builds for the N5 . I can't find it in my previous installed app list in the market , so I think its history.
[Nexus 6  Original Android Development] funcrusher:
No, Yank is right when it comes to this particular ROM. It doesn't deep sleep because of how blinking LED is configured to work.
[Nexus 6  Original Android Development] simms22:
that blows.. id stay far away from that rom then.
[Nexus 6  Original Android Development] cfrank38:
Hy flar chroma is using in the latest release many sepolicy changes. I'm not sure if its save to install your kernel because they put a warning that we loose all sepolicy changes installing other kernel
[Nexus 6  Original Android Development] flar2:
You can install EX on any ROM because it uses the existing ramdisk. The selinux stuff is in ram disk
[Nexus 6  Original Android Development] cfrank38:
Thank s
[Nexus 6  Original Android Development] mwebb34:
I'm on blisspop 5.0.2 with the new radio and bootloader. Will this kernel work for me on this setup?
[Nexus 6  Original Android Development] drawde40599:
Yep , You need to use Build 28 though . You can't use current 5.1 builds . And using the wrong radio and BL may or may not give you issues .
[Nexus 6  Original Android Development] Lancez:
It's better to use 5.0.2's bootloader, the 5.1's bootloder may give you problems. And what is the point of using 5.1's radio coz 5.0.2 dose not support VoLTE anyway.
[Nexus 6  Original Android Development] Johnny424:
anyone else having any trouble getting selinux permissive to survive a reboot? each time I reboot it doesn't enforce and breaks viper and play music.. I can get permissive to survive reboot with the selinux app though..any certain log that may help flar?
[Nexus 6  Original Android Development] stumpy352:
No problems here. I'm not using the app & viper works fine. Maybe the app is conflicting. I would uninstall it and reflash the kernel.
[Nexus 6  Original Android Development] drawde40599:
I agree . But you can't go back to older bootloader's from 5.1 BL . Fastboot will fail . He should just update fully ...
[Nexus 6  Original Android Development] mwebb34:
Yeah I found that out after flashing it,then tried to make a call while on the internet. Were could I find the old radio and bootloader zip..thanks for the lesson.
[Nexus 6  Original Android Development] simms22:
volte has absolutely nothing to do with wifi/internet calling. volte is voice over lte, and nothing more.
[Nexus 6  Original Android Development] Johnny424:
thanks for your feedback.. but I have unistalled and reinstalled kernel, viper and ROM with and without viper before hand and for what ever reason selinux won't enforce permiss unless I use the app.
[Nexus 6  Original Android Development] simms22:
you installed the kernel via recovery? you specifically chose selinux to be permissive in the setup while flashing? you have to, so itll boot peemissive, or you have to enable it afyer noot via kernel or app.
[Nexus 6  Original Android Development] Johnny424:
yeah. reinstalled the kernel several times each time selecting the selinux option enable in installer. but it won't enable once booted.. I appreciate the help guys

gotta be specific to my setup if no one else is having the issue.. not a big deal to enable with the app
[Nexus 6  Original Android Development] mwebb34:
Understood....

---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------

If I wipe data factory reset then re-flash bisspop 5.0.2 will that return my radio and bootloader back to original, 5.0.2 or 5.0.1 instead of 5.1
[Nexus 6  Original Android Development] simms22:
no. roms on a nexus dont touch your radio nor bootloader. all a factory reset does is clear user data.
[Nexus 6  Original Android Development] tealio:
You can pull the radio and boot loader from the factory images and flash them individually. Never done it myself.

Safest bet is to backup your data, flash factory image, flash your ROM, then restore your data.

There's probably a better way to do this, but I know that's safe. While it may not be the smartest way, it has worked for me in the past.

EDIT: Grammar and Typos