yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] lifeisfun:
Did you figure out how to replicate that problem?

Friend had the same problem couple times in December and it haven't happened since.

This was on stock rom, then he flashed Frank and your kernel.
[Nexus 6  Original Android Development] flar2:
I can't replicate it exactly. It seems to happen a lot after the phone has been idle for a long time. First thing in the morning, especiially. Also seems to happen more often with temperature changes, which I have all the time in this brutal northern climate where I live. When I try to use it on the bus in the morning, sometime it literally happens every minute or so.

It also happens very frequently on the elementalx governor and on the franco modified conservative. If I switch to interactive it happens less often.

It produces debugging output in the kernel logs, but I have not had time to trace through them. Even if I did, the mdss driver is so complex that I probably wouldn't be able to fix it myself. There may be updates from CAF, but haven't looked.

Even if it could be fixed in software, it definitely originates from weak hardware and is definitely getting worse. So I defintiely have to get the phone replaced or repaired.
[Nexus 6  Original Android Development] lifeisfun:
Thanks for those tips, we share the same city as you so I'll tell him to try cool his baby down :laugh:

That won't be big problem this year!
[Nexus 6  Original Android Development] my95z34:
Hey flar2, I just switched from the N5 to the N6 and of course first thing I did was download EX. But, as a rom maintainer I crack flash and I miss the express version. I haven't read ANY of this thread, so forgive me if it's been addressed, but is there a chance of getting an express version? I did a quick search but didn't see anything specific.

TIA!
[Nexus 6  Original Android Development] danarama:
You can install express via the elementalx app
[Nexus 6  Original Android Development] my95z34:
Damnit. I r dum. Lol. Thanks!
[Nexus 6  Original Android Development] stumpy352:
Hmmm
[Nexus 6  Original Android Development] tltwelve:
why is everybody moving over to Franco kernel?
[Nexus 6  Original Android Development] simms22:
whos everybody? im who is important to me, what others use does not matter nor bother me.
[Nexus 6  Original Android Development] drawde40599:
Because flar2 hasn't updated in a week so this kernel must be old and outdated . Doesn't matter that it runs great . . o_O ! Some people can't just flash a ROM or a kernel and just enjoy there device .
[Nexus 6  Original Android Development] dtroup64:
If you're looking for everybody over in the Franco thread... you'll miss me too. EX24 right here! :)
[Nexus 6  Original Android Development] lifeisfun:
Well, that did it, cooling the phone down will replicate the problem for him reliably.

That's crazy that there is so many problems with this device :(
[Nexus 6  Original Android Development] Remoteconcern:
I have the same issue as flar, but not as bad. Bizarrely mine is almost unusable with elementalx governor and yet the problem is almost non existent with a kernel using mpdecision. I don't think I could even get a return as they wouldn't ever see the problem.
[Nexus 6  Original Android Development] flar2:
Using mpdecision helps because it keeps the cpu frequency from moving around (stays at touchboost). Elementalx gov drops down to 300MHz very quickly, and that seems to aggravate it.

But yes, I really don't like this device. I've had problems right from the get go. And the app I'm working on this week causes an obscure crash on this device, but works perfectly on the four other devices I've tested it on.
[Nexus 6  Original Android Development] slyguy2000:
I count my blessings when I can at least get it to a stable point. Bare min, Bluetooth audio and phone, GPS, internet, battery life... In that order, all need to work, all day, every day. This device does it 99.95% of the time. But hasn't bricked out yet, so I am hopeful it will get better. Your work makes a world of difference! Most stable my device has ever been! THANKS!
[Nexus 6  Original Android Development] stumpy352:
[MENTION=4684315]flar2[/MENTION] do we have this system wide torch fix I've been hearing about. I want to upgrade my ROM (chroma) but some people are reporting systemui crashes on other kernels.
[Nexus 6  Original Android Development] simms22:
system wide torch fix? huh?? torch/flashlight works fine here, no errors as well. but it works on every kernel :confused:
[Nexus 6  Original Android Development] stumpy352:
Was some fix for cm theme manager and torch crashing. Some aosp & cm based ROMs have implemented it, but it needs kernel support. Not sure if its already in this kernel or not is all. Trying to get a link for the patch commit now.
[Nexus 6  Original Android Development] simms22:
ahhh.. thats for explaining it, as i had no idea.
[Nexus 6  Original Android Development] stumpy352:
ROM dev gave me a link, but just takes me straight to Franco's git. Can't seem to find the commit. Maybe [MENTION=4684315]flar2[/MENTION] knows what its about. Or perhaps its already included.
[Nexus 6  Original Android Development] nextelbuddy:
I'm just for this kernel to be updated with the sensor_Ind fix that lean kernel and Franco kernel have currently.
[Nexus 6  Original Android Development] kratos313:
I'm going to try this kernel out. Is there any recommendation on settings to get good battery life? I'm stock rooted, I've tried lean,faux,Franco with stock settings and it wasn't a good experience.
[Nexus 6  Original Android Development] DroidIt!:
I just go with ElX gov, max the CPU at 1.9 GHz, cap the GPU at 500 and leave everything else alone and get great battery life for my usage. [emoji106]
[Nexus 6  Original Android Development] drawde40599:
Use the default settings for a couple days before you change anything . I think you'll find you won't really need mess with anything .

---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------

Do you have that Wlock issue ? From what I'm reading most people don't even have the issue .
[Nexus 6  Original Android Development] stumpy352:
I'm getting it every time I make a phone call now. Have to reboot after every call.
[Nexus 6  Original Android Development] drawde40599:
Ya That's what I read that "they" have tracked it down to (phone) , so ya everyone's going to get it after a phone call but Most devices wont hold it on as battery draining Wlock , it shuts down on its own . Nether of my N6's have the issue . Happy about that !
[Nexus 6  Original Android Development] cfrank38:
Hy flar you told us that your worst problem is now time ? Or your nexus 6/is failing and you can't develop at the moment. We all hope that your problems with the nexus 6 will be solved soon
[Nexus 6  Original Android Development] flar2:
Both are problems. I'm going to stay up really late tonight and do the update.

That cm torch fix is probably not needed, as EX uses the existing ramdisk.

I will be adding the ability to toggle sensor_Ind in both the app and the kernel. The app might be a few more days, as I have several things to fix/add for various devices.
[Nexus 6  Original Android Development] nextelbuddy:
Yes, and looking over it the nexus 6 subreddit you will see many people in that section also have this issue. with that many people in such a small sampling having the issue, I can only imagine how many people out there have it and dont even know what the heck is going on. imagine how many people getting this phone and just thinking "man this phone stinks i have to keep turbo charging it because it drains so fast.. it must be the screen" but they dont use reddit or XDA and just keep on thinking the phone is a battery hog and never report it.

i've been able to consistently replicate the sensor_ind issue with hangouts.. in hangouts just receive a message and NOT reply to it. swipe the notification away and leave it there OR type a reply back but do not send it... leave it in draft mode.. go to your home screen and put screen to sleep for a few min. open CPU spy and see that its been stuck @ 300mhz for the entire time.

even if its not hangouts and you have ambient and adaptive display DISABLED, sensor_ind still triggers and you have to go TOGGLE adaptive and ambient display ON and OFF to get sensor_ind to go away.

thats how I have been getting around it and have been using CPUSPY religously. anytime i notice my battery indicator going down faster than normal i check CPUSPU for deep sleep and just go check hangouts or toggle adaptive and ambient display.

im using LEAN kernel now and havent had the issue since it has the wakelock "fix"

i like elemental kernel for its beautiful app and am just waiting for it to get updated :)
[Nexus 6  Original Android Development] flar2:
Update!!!

I added the ability to disable the sensor_ind wakelock from imoseyon. Default is to disable it, as it seems to be a bug (ie, does not need to be on). There is an installer option for it, and I will add it to the EX app as well.

I also reduced the wlan wakelock a little. I actually had this commit early on, but didn't add it back when I rebased last month. I don't want to reduce too much or disable this one, as I've had a small number of users complain of wifi problems on other devices from these types of hacks. Besides, idle drain is generally pretty good as-is (personally I see 0.3 to 0.4% per hour overnight), so I don't think the other wakelocks are problematic. The sensor_ind needed attention, it's a special case affecting some more than others.

The other major change is Wake Gesture support, for an app I will release later tonight. Some of you may remember the wake gestures idea from other devices, where xposed modules (Sense Toolbox by Mikanoshi and Wake Gestures by C3C076) worked with the kernel for gesture customization. I've created an app based on the wake gestures xposed module by [MENTION=5008415]C3C076[/MENTION]. I'll post a link.

And finally, you can adjust the vibration to stock levels again (using the EX app).

Download:

ElementalX-N6-0.25 (beta)

Changelog:

-add Wake Gestures support

-allow stock vibration level

-sensor_ind wakelock toggle

-update installer

-reduce wlan wakelock

-wake gestures: remove debug output

-increase default max screen off frequency
[Nexus 6  Original Android Development] flyinj54:
The element x governor really runs great on your kernel. I think it's the fastest governor I've ever tried. You can literally feel the difference will running that governor. Highly impressed. Thanks for the update rocking it now
[Nexus 6  Original Android Development] flar2:
As promised, the Wake Gestures app

http://xdaforums.com/android/apps-games/app-wake-gestures-t3030399
[Nexus 6  Original Android Development] daftlush:
I switched over for a bit when flar started ripping out code / drivers. Figured it was a good time to see what's going on with Franco. Might as well experiment around if flar is testing here. Now I'm kinda circling around lean and the f2fs omni one. I really want to test f2fs with omni but I don't want to leave the stock ROM for aosp till all of the aosp kinks are worked out.

Damn flar, new gesture app looks great. Super excited here.
[Nexus 6  Original Android Development] tiernan22:
Running DU. 0.25 feels as quick as anything else out there. Default settings except for fiops. Looking forward to seeing the battery life. It's good to come back home.
[Nexus 6  Original Android Development] x0nar:
Hi. Just Installed 0.25. I'm getting System UI FC's from the very beginning I installed it. ROM is Ressurection Remix 5.3.4
[Nexus 6  Original Android Development] drawde40599:
Try clearing caches , factory reset or post some logs
[Nexus 6  Original Android Development] x0nar:
Never Mind. I already Installed Blisspop and it seems to be working fine
[Nexus 6  Original Android Development] poczynek:
Oh man I love that!

Just a question about the wakelock toggle, I can't find a way to toggle it off in the elementalx app? ?
[Nexus 6  Original Android Development] drawde40599:
Check out the changlog on previous page
[Nexus 6  Original Android Development] poczynek:
I read the change log but can't find the toggle in the elementalx app.
[Nexus 6  Original Android Development] drawde40599:
It says he added toggle to kernel and will add to app also ( its not added to app yet )
[Nexus 6  Original Android Development] poczynek:
Yes sorry he did say it would be added in a few days. Thanks.
[Nexus 6  Original Android Development] drawde40599:
Bfq came up as default after installing 25 and clearing the app , is that default now ?

Edit : just cleared the app agn now deadline came up as default after reboot .

Also if I change min gpu to 300 , cores 1&2 get stuck at "1700 " and they never drop back down to 300 unless I change GPU back to 240

Stock ROM , that's it, no mods
[Nexus 6  Original Android Development] D-m-x:
Slight Off Topic:

Has anyone tried Updating via the App with TWRP 2.8.5.0? For me the Script didn't work, i had to install it manually.
[Nexus 6  Original Android Development] stokholm:
Yeah, worked fine for me. But I did use the custom install.
[Nexus 6  Original Android Development] inzaghi75:
Do we need the s2w phone disabler with the last kernel?
[Nexus 6  Original Android Development] flar2:
Its in the installer options. Will be in the app when I update it

It's because of gboost. Its forcing gaming mode.

If you have s2w enabled, then yes.
[Nexus 6  Original Android Development] drawde40599:
default scheduler

[MENTION=4684315]flar2[/MENTION]

So used to using kernel with stock settings I forgot about Gboost . Thanks

Whats the default scheduler Noop right ?

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

[/COLOR [MENTION=4684315]flar2[/MENTION]

So used to using kernel with stock settings I forgot about Gboost . Thanks

Whats the default scheduler, Noop right ?
[Nexus 6  Original Android Development] flar2:
I think cfq is stock and noop is EX default
[Nexus 6  Original Android Development] PDP///M:
Two quick questions. Is this kernel permissive? Anyone have xposed framework working with this kernel?
[Nexus 6  Original Android Development] flar2:
I don't do anything to make it permissive, but if you flash it over a permissive kernel it will probably be permissive.
[Nexus 6  Original Android Development] danarama:
Yes if you flash it over the latest lk beta, the ramdisk requirement for selinux permissive remain. However for me, the kernel being permissive is not enough for me with xposed and many others. Have a look in the general forum as we have thread with some things to try including init.d scripts, which I have working with xposed.
[Nexus 6  Original Android Development] D-m-x:
This is Off Topic, but yes i have it working. Go to Nexus 6 General Section and look for an Xposed Issues Topic, there's your solution.
[Nexus 6  Original Android Development] nEUTRon666:
May i ask that this is for:

-sensor_ind wakelock toggle

What is this wakelock and why can it be toggled ?
[Nexus 6  Original Android Development] drawde40599:
No one knows exactly what it is or how its triggered . But short answer , it gets stuck on for some users and kills there battery. custom kernels are now disabling it with no bad side effects besides better battery . Toggle is an option because if you dont have the issue why shut it off ... I don't have the issue so I left it on .

You can try googling it but its all pretty much guessing what's going on ATM
[Nexus 6  Original Android Development] poczynek:
I have the elementalx app and love it. Very configurable and beautifully designed. Had it since it was released.

However the new xposed module means that you need the kernel to be permissive. So I am using an init.d script that makes it permissive on boot. However this is resetting all of my elementalx settings. What can I do?
[Nexus 6  Original Android Development] danarama:
Doesn't reset mine...
[Nexus 6  Original Android Development] poczynek:
Weird! Just rebooted again and all reset to default.
[Nexus 6  Original Android Development] danarama:
Weird indeed.
[Nexus 6  Original Android Development] stumpy352:
Are you checking the set on boot?
[Nexus 6  Original Android Development] poczynek:
Yep.
[Nexus 6  Original Android Development] danarama:
Is it all settings being reset or just some? Some settings reset after a crash reboot. How are you rebooting? Normally or via xposed?
[Nexus 6  Original Android Development] poczynek:
Yes all settings. Rebooting through power menu. Trying to think if another init.d script is coming over the top? Can that happen?
[Nexus 6  Original Android Development] danarama:
What's in your init.d?
[Nexus 6  Original Android Development] poczynek:
See below
[Nexus 6  Original Android Development] danarama:
Just normal stuff.
[Nexus 6  Original Android Development] flar2:
Maybe you have something preventing the app from applying the settings at boot. Or another app is running its settings after.
[Nexus 6  Original Android Development] flar2:
I'm guessing we need to have an option for permissive selinux due to xposed?
[Nexus 6  Original Android Development] danarama:
Its up to you. Some phones haven't required selinux to be permissive, some phones have been able to use an app to set selinux as permissive...

For me, even using lean kernel with permissive, it was not enough. setenforce is executed too late. There is an unofficial build that sets it earlier though, but init.d is sufficient for me...

Thing is though, xposed is alpha right now. We don't know long term what the requirements will be. I wouldn't recommend doing anything you don't want to do based on that, particularly as there are workarounds at the moment and we don't know the future requirements
[Nexus 6  Original Android Development] drawde40599:
[MENTION=4684315]flar2[/MENTION] coming from other kernels reflash of ROM still not necessary or it is now ?
[Nexus 6  Original Android Development] danarama:
All depends on the other kernels
[Nexus 6  Original Android Development] nEUTRon666:
Thanks for explaining. Since i didn't have any battery drain it seems i don't have it either. I cannot find the toggle in the elementalX app, how can i toggle it then?
[Nexus 6  Original Android Development] drawde40599:
Ya it dosent seem to effect a whole lot of people but enough it is a issue, u can see if you have the wlock with a app like GSam battery or bbs . He hasn't added it to the app yet , so during install on or off is the only option ATM .
[Nexus 6  Original Android Development] nEUTRon666:
I shouldn't choose express while installing, all the time :P Again, thanks.
[Nexus 6  Original Android Development] jaythenut:
or just install this https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en_GB
[Nexus 6  Original Android Development] danarama:
You did read the nexus 6 general thread? This won't work for everyone as I mentioned a few posts back.
[Nexus 6  Original Android Development] jaythenut:
Really, worked fine for me :p
[Nexus 6  Original Android Development] danarama:
Doesn't work for almost all nexus 6 users haha. In fact you're the first I've seen
[Nexus 6  Original Android Development] jaythenut:
Yeah works fine:D
[Nexus 6  Original Android Development] danarama:
Lucky you. What's that screenshot prove though?
[Nexus 6  Original Android Development] tealio:
I'm not getting this wake lock. Is there any drawback to leaving this toggle on? I left it on when I updated, and haven't noticed anything acting weird. It seems logical to me that disabling something I don't have shouldn't be an issue, but I just wanted to check.
[Nexus 6  Original Android Development] danarama:
No issues here so far, though I don't make many calls..
[Nexus 6  Original Android Development] flar2:
There doesn't seem to be any harm either way.

Its on by default ( stock behavior)
[Nexus 6  Original Android Development] DroidIt!:
Hey [MENTION=4684315]flar2[/MENTION]. Well, I for one would appreciate if you added the permissive stuffs to allow for xposed. I tried all 3 methods in the Nexus 6 general thread, not willing to try the 4th :), and I can't get the xposed to survive a reboot. I always have to soft reboot. Normally that wouldn't be a problem, but one of the modules in order to be activated, needs a hard reboot, so no matter what I do I can't use a couple modules. I don't use xposed for much but really do like the modules I do use. If you don't wanna do it just yet, that's fine, just my vote and two cents :)
[Nexus 6  Original Android Development] danarama:
Try the 4th. You can flash elemental straight on top and should still work.
[Nexus 6  Original Android Development] flar2:
I can add a permissive option. I already had to do it on my HTC kernels when lollipop was released.
[Nexus 6  Original Android Development] danarama:
How easy is it to give it a higher priority during boot? LK had to release a special version to do just this.
[Nexus 6  Original Android Development] flar2:
Very easy, I'll release a new version later today.
[Nexus 6  Original Android Development] danarama:
Cool thanks.
[Nexus 6  Original Android Development] DroidIt!:
Agree with [MENTION=2872010]rootSU[/MENTION]. Thank you! :)
[Nexus 6  Original Android Development] stumpy352:
I asked for this a month ago, foreseeing the need for it on lollipop. Unfortunately, at the time, I was flamed outta here like I'd said a dirty word.

I would also appreciate this as an option. Not only is it required for xposed, but for Viper4android also. There will likely be tons more root apps that require it too.

Perhaps a better method though, would be to find out from the devs at xposed and v4a which policies need adjustment & just make those permissive, thus not opening security right up for the sake of a few things?
[Nexus 6  Original Android Development] danarama:
V4a hasn't been updated so its possible they don't know yet. That requirement may change
[Nexus 6  Original Android Development] stumpy352:
V4a was updated yesterday. Permissive selinux still required unfortunately.
[Nexus 6  Original Android Development] danarama:
Got a link please?
[Nexus 6  Original Android Development] stumpy352:
You can update it in app. Takes you to a web page with 2 downloads. Choose the 4.x version.
[Nexus 6  Original Android Development] flar2:
I'm still not big on the idea of selinux permissive. The difference with xposed is a) tons of people use it and b) that it needs to be done earlier in the boot process, whereas other things work with a simple setenforce 0 command. Also, for v4a, I think you are correct that a supolicy statement could work rather than setting selinux to permissive. Xposed gets so deep in the system I'm not sure that will be possible. But I don't use xposed or v4a, so I'm not totally sure what's involved.
[Nexus 6  Original Android Development] antiochasylum:
I don't use v4a, just xposed. So for me using the work around is a pain but it's working.

It's not worth it to leave elemental just get permissive.

So make the option or not, I'm not going anywhere.
[Nexus 6  Original Android Development] dvdivx:
Is it possible just to set it using the installer so whomever wants it set permissive by default can do so?
[Nexus 6  Original Android Development] biggofer:
I have an idea what selinux is but not really . So i guess I don't understand , this and all kernels need to downgrade security so users can add a few tweaks to there Roms ? And is setting selinux to permissive something that's just done at boot and it goes back to "normal" after boot or we would be stuck using the downgrade?