yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

Do you think you can implement a max screen off frequency or to enable how many cores are on during screen off? Mainly wanted to see if you could implement this for an app during screen off so maybe something for the app profiles during screen off?
[Nexus 6  Original Android Development] Tzfardaya:
I seem to recall something of this nature being tried on the n5, caused some interesting glitches.... Might be able to use Tasker to do that, but haven't tried...
[Nexus 6  Original Android Development] wrongway213:
[MENTION=3292224]franciscofranco[/MENTION] Any thoughts on Imoseyon's test LK disabling the sensor_ind wakelock on a kernel level? I know I've seen you discuss the wakelock before. Imoseyon released a test version of his latest kernel that disables the sensor_ind wakelock and so far those using it are reporting no issues, Imoseyon even said he plans to implement it as an option in future normal kernel releases in the future. http://xdaforums.com/showpost.php?p=58689108&postcount=2199 just in case you're curious.. I know I can't get rid of the wakelock and it's confirmed triggered by ROM, not kernel, but apparently disabling at the kernel level is effective.
[Nexus 6  Original Android Development] paychex:
turning off a sensor doesn't sound like a good idea
[Nexus 6  Original Android Development] Tzfardaya:
Not the sensor, just the wakelock... :P or so I understand...
[Nexus 6  Original Android Development] christianrance:
Re: sensor_ind wakelock...

Is this actually causing many people issues? I'm running [MENTION=426561]scrosler[/MENTION] CleanROM 1.4 + franco r13 and here's the activity for this wakelock after 9.5hrs unplugged:

In case this matters, here are my display settings:

via my Franco'd CleanROM Nexus 6
[Nexus 6  Original Android Development] wrongway213:
Yes, it's not at all constant. Randomly it'll hold for hours and hours, I've seen it over 6 hours nonstop, not one second of deep sleep. Then reboot and all is well, maybe for hours, days or even a week.

---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------

Yes this is what I've gathered.... I don't think Imoseyon would turn off something that is dangerous to turn off.
[Nexus 6  Original Android Development] paychex:
I highly doubt you can turn it off without losing some kind of functionality
[Nexus 6  Original Android Development] wrongway213:
What I thought too... We can't find what though so I'm not sure
[Nexus 6  Original Android Development] suku_patel_22:
I have been running the test kernel for a day now. Don't see any issue. Every function is working fine.

Adaptive brightness, ambient display, auto rotate, games, sensors, GPS all work fine.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Janzen254:
What exactly is sensor_ind?
[Nexus 6  Original Android Development] Tzfardaya:
A wakelock that sporadically keeps the phone from deep sleeping... We haven't been able to tie down the exact trigger, but it seems related to the ambient/adaptive display toggles.. Hangouts may or may not be involved somehow...
[Nexus 6  Original Android Development] wrongway213:
I was trying the adaptive and ambient both on config you suggested in the N6 battery life thread and it was great for like 16 hours, then the wakelock kicked on for a little over an hour before I caught it, switched to ambient on, adaptive off and rebooted.. this one is the last config of the four I have to test. Ambient on/adaptive on, ambient off/adaptive off and ambient off/adaptive on are definitely not the solution for me. I've been using ambient on, adaptive off all day and so far only 1m 32 s of sensor_ind wakelock.. but one day is not nearly enough time to tell anything with this. If this setup doesn't fix it, as I don't even have hangouts installed I'm gonna have to try this kernel with it disabled as long as no issues have been found.
[Nexus 6  Original Android Development] lainemac:
What battery life thread are you referring to?
[Nexus 6  Original Android Development] Tzfardaya:
I run on/on, been tracking the wakelocks... Msm_hsic_host has been holding the phone awake more than sensors_ind...
[Nexus 6  Original Android Development] christianrance:
I can confirm that ambient on/adaptive off has resulted in next to (in not) 0s of wakelock by sensor_ind. I switched to this configuration just over a week ago and have consistently seen those results and I use Hangouts as my only messaging client. Prior to that sensor_ind did, sporadically, eat significant wakelock time.

via my franco'd CleanROM Nexus 6
[Nexus 6  Original Android Development] Janzen254:
I know it is a wakelock people are having. I have not checked to see if I have it. I was wondering what the exact sensor it is.
[Nexus 6  Original Android Development] Tzfardaya:
That setup is when my battery was being devoured by sensor_ind...

Which leads me to believe that there is some other trigger involved that we haven't quite narrowed down...
[Nexus 6  Original Android Development] christianrance:
Weird... Wonder if it's ROM-related then?? What are you running?

via my franco'd CleanROM Nexus 6
[Nexus 6  Original Android Development] Tzfardaya:
Stock, thinking of trying chroma, but... Can't be arsed to flash it yet.
[Nexus 6  Original Android Development] wrongway213:
Ah, in the other thread you said that it was adaptive on/ambient off that was causing you issues? Or have both setups been problematic for you?

---------- Post added at 10:31 PM ---------- Previous post was at 10:31 PM ----------

This one http://xdaforums.com/nexus-6/general/n6-battery-life-owners-thread-t2946742
[Nexus 6  Original Android Development] Tzfardaya:
Both have been problematic for me...
[Nexus 6  Original Android Development] wrongway213:
Man this wakelock is so frustrating.. I have a feeling I'm inevitably gonna be flashing this new test kernel and trying to see what it breaks as I can't see why it would work for me and not you, but running for almost a day with no wakelock I don't wanna stop the test quite yet or I'd just flash it now lol.. really hope it does not cause any issues and we will see it implemented on other kernels, such as this one, so everyone can get back to enjoying their deep sleep... seeing 15% deep sleep on a Franco kernel with no bloat or FB or anything just outright aggravates me because I know it should be somewhere in the mid 90's anytime with FK if idle.
[Nexus 6  Original Android Development] C00lBeanz:
Low Antutu scores... Is this normal? I used to get 50,000+...
[Nexus 6  Original Android Development] wrongway213:
You have VomerTweaks installed? If so, normal.
[Nexus 6  Original Android Development] narezese:
Im on stock, with adaptive brightness on and ambient display off.. And as right now i don't have the sensor_ind, about 2 weeks was there but with 0%
[Nexus 6  Original Android Development] SmokeyMon:
I'm on the FK train with chroma rom ( fantastic ROM BTW), I run with no adaptive brightness and no ambient display. Ive had this particular wake lock only once that I have seen. It occurred a few weeks ago and has not been back since.
[Nexus 6  Original Android Development] wrongway213:
Yeah I tried that, was wakelock city for me with sensor_ind on that setup. I am running adaptive off, ambient on right now and so far have only seen the wakelock for like 30 seconds at a time (normal wakelock behavior), no deep sleep issues yet but only been running this a little over a full day... if sensor_ind kicks up with this setup I'll officially have tested and failed with them all, if not I think I'll have gotten closer to pinpointing the issue.. shall see how it goes.
[Nexus 6  Original Android Development] zephiK:
Same here. Haven't seen the wakelock in ages with both off.

Btw, haven't seen you in the Chroma thread for awhile!
[Nexus 6  Original Android Development] gamewarden234:
My phone has been awake for about 27 hours. 7 minutes of that wake lock. Both off.
[Nexus 6  Original Android Development] HdMsTrTeCh:
I'm on AOSPA, and haven't seen the sensor ind wakelock in a long while as well. I'll keep testing and report back. Are we sure this isn't ROM related?
[Nexus 6  Original Android Development] Tzfardaya:
To be honest, we Are all just guessing... We really aren't sure what it's related to...
[Nexus 6  Original Android Development] C00lBeanz:
Nope, just Franco Kernel updater pro, governor Conservative, IO noop, and on CM12 rom.
[Nexus 6  Original Android Development] suku_patel_22:
Sensor_ind is ROM related. It originates in the ROM. It is actually a bug from Google.

Sent from my Nexus 6
[Nexus 6  Original Android Development] wrongway213:
This indeed, it originates from within the ROM, any ROM, even stock, but can be disabled at the kernel level.

How are things coming with it disabled? Notice any changes or just no wakelock and better battery life?
[Nexus 6  Original Android Development] tysonwald:
2 days now and have noticed no changes other than better battery life. the wakelock is no longer appearing. It's been great id try it out if I were you
[Nexus 6  Original Android Development] wrongway213:
Oh as soon as I get done testing my current setup trying to kill the wake lock or find its source, I plan to... Can't wait to test it out.
[Nexus 6  Original Android Development] suku_patel_22:
The only side effect is better battery life :D

I would think the the wakelock disabled in franco would give even better battery life. Frankly I am missing conservative.

Sent from my Nexus 6
[Nexus 6  Original Android Development] paychex:
I can't imagine the only thing the wakelock does is cause battery drain
[Nexus 6  Original Android Development] supercluver:
Well to be fair, if it really IS a bug, and sensor_ind isn't supposed to be holding a wakelock, then that would be about all it would do, wouldn't it?
[Nexus 6  Original Android Development] wrongway213:
We need to get whoever the master debugger guru on Nexus devices is and have them tell us what this thing even is once and for all haha
[Nexus 6  Original Android Development] zzmomo73:
Ignore
[Nexus 6  Original Android Development] big_adventure:
OK, ignored!
[Nexus 6  Original Android Development] LillieBennett:
I'm worried about the change from cpu_boost, a load based boost (r11) to a touch based boost (r13). Does it mean that a background job with the screen off won't get any load boosting?
[Nexus 6  Original Android Development] big_adventure:
No - and you can show it. Reboot your phone, unlock it, then go screen-off. After an hour, check CPU states, and you'll see states used - and all of those are from load.

At least, that's what I see.
[Nexus 6  Original Android Development] Tzfardaya:
No, it shouldn't boost under load anymore (but it WILL still scale up under load....

*starts paying very close attention.. He must be hiding something If he's telling us to ignore him.. *
[Nexus 6  Original Android Development] big_adventure:
To-may-to, to-MAH-to
[Nexus 6  Original Android Development] Tzfardaya:
Boost bypasses the scaling algorithm and jumps to a set frequency.. Scaling adjusts up and down depending on variables set...
[Nexus 6  Original Android Development] big_adventure:
Sure, if you want to get all technical-like.

I was just answering the poster's question on whether the phone would increase CPU for load.
[Nexus 6  Original Android Development] Tzfardaya:
Fair enough, but why not take the chance to teach him something about the workings at the same time. This is a developers forum after all. ;)
[Nexus 6  Original Android Development] big_adventure:
When you are right, you're right.
[Nexus 6  Original Android Development] Tzfardaya:
But only when I'm right, right?
[Nexus 6  Original Android Development] big_adventure:
Sometimes when you're wrong, you're right. And sometimes when you're right, you're really wrong.
[Nexus 6  Original Android Development] Tzfardaya:
But can I be right when I'm left?
[Nexus 6  Original Android Development] big_adventure:
I don't know about that, but you can definitely be left when you're right. Happened to me just last weekend.
[Nexus 6  Original Android Development] rignfool:
I feel like I'm at the bottom of Godwin's Well
[Nexus 6  Original Android Development] Tzfardaya:
At least it's a dry well, you don't have to worry about drowning in it..
[Nexus 6  Original Android Development] Skripka:
Is that stage right or house left?
[Nexus 6  Original Android Development] Tzfardaya:
Yes
[Nexus 6  Original Android Development] dvdivx:
Next time try to upgrade to Godwin's wine cellar.

Also it looks like CM did some kernel updates so I wonder if r14 rolls out or how much CM affects franco's kernel development.
[Nexus 6  Original Android Development] kergefarkas:
That would make you a woman :P
[Nexus 6  Original Android Development] franciscofranco:
What the **** are guys talking about?
[Nexus 6  Original Android Development] suku_patel_22:
Well a ****load of crap and sensor_ind and CM stuff :D

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Pushed r14. It's a special release with lots of interesting merges from upstream. If you run into any problems make sure to grab me a log!
[Nexus 6  Original Android Development] pantmunu:
What abt the damn cat Franco ?? ??
[Nexus 6  Original Android Development] franciscofranco:
She's sleeping now :)
[Nexus 6  Original Android Development] skytron:
Awesome

Thank You! Will Be Flashing Soon!
[Nexus 6  Original Android Development] suku_patel_22:
Could you please consider disabling sensor_ind in the kernel and make it optional?

Sent from my Nexus 6
[Nexus 6  Original Android Development] big_adventure:
Someone has seen crappy Woody Harrelson / Wesley Snipes movies.

****ing nonsense, of course.

Mostly the ****load of crap.

In the immmortal words of Tzfardaya: Yes.

---------- Post added at 07:51 AM ---------- Previous post was at 07:48 AM ----------

Flashed it.

Best. Kernel. Ever. My cat got up and started dancing. And that's amazing, since my cat died when I was 7.
[Nexus 6  Original Android Development] C00lBeanz:
Stop updating so freaking fast damn dawg how many times am I gonna have to flash stuff!!! D:<
[Nexus 6  Original Android Development] carlz28:
Thanks for the update.
[Nexus 6  Original Android Development] booey24:
Everything is running silky smooth with this kernel along with stock rooted Rom. Thanks for the kernel.
[Nexus 6  Original Android Development] franciscofranco:
I'll wait for imoseyon to push the patch, I don't know how to do it from the top of my head and I don't want to search (probably somewhere on the wakeup.c and add something like if (strcmp(wakeup_source.name, "sensor_ind") == 0) return;).
[Nexus 6  Original Android Development] suku_patel_22:
Thanks, that would make it perfect. I am missing your conservative fluidity.

Sent from my Nexus 6
[Nexus 6  Original Android Development] noneabove:
XDA made your code just a little bit more flirtatious today. (At least on mobile)
[Nexus 6  Original Android Development] rauschkugl:
Yes he said somewhere that he just doesn't allow the wakelock when sensor_ind is asking for it.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] HdMsTrTeCh:
Does this happen to anybody? Looks like I can still download and flash but FKU has decided to be confusing.
[Nexus 6  Original Android Development] 6-speed:
So far r14 is doing awesome. I went from r10 to r14.
[Nexus 6  Original Android Development] grinchyyy:
This would be sweet, maybe add the selinux to permissive too for us Viper4andriod users? ?
[Nexus 6  Original Android Development] franciscofranco:
What the **** have you done with my app colors?

You can change selinux status yourself.
[Nexus 6  Original Android Development] akellar:
He didn't make it permissive, he fixed the selinux policy to allow V4A to work.
[Nexus 6  Original Android Development] HdMsTrTeCh:
I'm running AOSPA with a CM12 theme but I think this has always been the colors of your app FF. By the way I'm now showing an update. What are the stock colors by the way or are you just playing with me?
[Nexus 6  Original Android Development] suku_patel_22:
This is the real colors.

Sent from my Nexus 6
[Nexus 6  Original Android Development] HdMsTrTeCh:
So....font colors are different? I'll get over it. Enjoying the kernel and still no sensor ind wakes.
[Nexus 6  Original Android Development] naishadh:
What setting u guys use for hotplug if I want all 4 core online same time.pl suggest setting.
[Nexus 6  Original Android Development] Tzfardaya:
Hotplug load_threshold to 0 for all cores always on.
[Nexus 6  Original Android Development] wrongway213:
This would be amazing, wakelock is just horrible... your kernel is quite the opposite, so separating the two = win.

Still directed at you Franco, just bringing up akellar's post. I wanted to point this out in relation to the user who asked you to also add the SEPolicy fix to make V4A work. I believe you thought he was requesting you to make the kernel permissive - he was not. The other new patch Imoseyon applied to LK simply allows for V4A to process and function normally without having to set kernel to permissive, so it could work with your kernel out of the box. I definitely second his opinion that would also be a welcome addition to the kernel as many make it permissive simply for Viper alone.
[Nexus 6  Original Android Development] franciscofranco:
I'll have to see what imoseyon did. I know he calls sepolicy after boot has completed and runs a series of commands to allow certain parts to function correctly with selinux. Not sure I like that, but I'll think about it.
[Nexus 6  Original Android Development] grinchyyy:
Yes, I was using the app that allows this, just one less app to install if it was built in. I'm just lazy

---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------

Should have read this before I replied above.
[Nexus 6  Original Android Development] wrongway213:
I don't think you quite understand how cool the change made really is or why people are excited, to be honest (not meant to be insulting at all, sorry if it comes off condescending - not my intent in the slightest but somehow it still reads that way to me). It's not that we mind the app - it's that SELinux enforcing is good for security.. having to make our systems less secure for Viper and only Viper, the reason many of us use permissive kernels, is a very nice thing to avoid. It's a security issue, not a convenience issue.
[Nexus 6  Original Android Development] paychex:
Please don't. People need to accept SeLinux and devs need to learn how to work with it.
[Nexus 6  Original Android Development] smclaughlin3:
in other words if you want fully functional everything us lean kernel lmao
[Nexus 6  Original Android Development] wrongway213:
Not at all - not sure if being sarcastic or just unaware of Imoseyon and Franco working together and generally being friendly with one another. Also, this has absolutely nothing to do with making anything functional, it's simply an SEPolicy change that has been made... there is literally zero relevance to any kernel being more functional than another, or anything being fully functional in general.
[Nexus 6  Original Android Development] grinchyyy:
Your right, I didn't. I brushed up a bit and have a better understanding on the subject. It is very cool, I should have said that I enjoy the convenience of not having to seek out another app to make V4A work. Now we don't!

I love having a Nexus again!
[Nexus 6  Original Android Development] wrongway213:
It is indeed interesting, figured you'd appreciate it a lot more if you understood the significance. Glad a little reading shed some light on it for ya.
[Nexus 6  Original Android Development] Circaflex:
r14 is running great, thanks [MENTION=3292224]franciscofranco[/MENTION] did you see my PM regarding the n5?
[Nexus 6  Original Android Development] franciscofranco:
I did not, I don't use XDA's PM system, last time I checked I had 5k messages.
[Nexus 6  Original Android Development] Circaflex:
haha, understandable you're a legend here. I saw your post on G+ regarding your dead n5 and needing a user to test something. I have an n5 that is no longer use as a daily device, if you need anything in the future feel free to shoot me a message here or on G+, Kevin Bostwick, I can pull logs or flash a test image if need be whether it works or not as the device is not used.
[Nexus 6  Original Android Development] christianrance:
[MENTION=3292224]franciscofranco[/MENTION], just reiterating what [MENTION=1413320]Circaflex[/MENTION] mentioned earlier that r14 is running fantastically! While I don't have specific metrics to scientifically back that up, my overall impression since flashing it earlier this morning and running it through its paces as I normally do throughout a day leaves me with the feeling that this is the smoothest and most well-tuned iteration yet. Also, battery life, so far, seems to be the best I've experienced with this kernel to date. You've really created what's arguably the best kernel out there for the N6 (IMO).

**** is straight BOSS! (Rick Ross voice)

via my franco'd CleanROM Nexus 6
[Nexus 6  Original Android Development] Janzen254:
[MENTION=3292224]franciscofranco[/MENTION],

What happened to your Nexus 5?
[Nexus 6  Original Android Development] franciscofranco:
I killed it by mistake.
[Nexus 6  Original Android Development] Janzen254:
How?

Mine is messed up too. I think it's the power button on the board is what is messed up.
[Nexus 6  Original Android Development] franciscofranco:
I was updating the bootloader and my USB hub cut the power during the bootloader write, I thought it was fine and rebooted the bootloader. Goodbye.
[Nexus 6  Original Android Development] Janzen254:
Did you try the secondary bootloader (volume ± and power)?

If the secondary bootloader works, use dd to restore the primary bootloader.

dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"

mmcblk0p6 is the primary bootloader

mmcblk0p11 is the secondary bootloader
[Nexus 6  Original Android Development] franciscofranco:
I already tried everything, I spent 2 days on this, I used the most obscure tools from Qcom, LG, chinese ****, I put the device in all possible modes and whatever you can possibly imagine. It's dead.
[Nexus 6  Original Android Development] Janzen254:
Can you JTAG it?
[Nexus 6  Original Android Development] franciscofranco:
I don't have the tools, I really can't be arsed.
[Nexus 6  Original Android Development] franciscofranco:
Testing r15 with imoseyon's sensor_ind wakelock disable commit. boot.img attached.
[Nexus 6  Original Android Development] supercluver:
Was the N5 your main phone or do you have a N6? (you probably already said, and I'd guess you have the 6 since you're developing for it but you never know...)
[Nexus 6  Original Android Development] franciscofranco:
I used the N5 as main phone until I got the One Plus One, I'm now on the N6.
[Nexus 6  Original Android Development] tysonwald:
Sweet! thanks- I'm testing this out as i ran his kernel and it took care of my wakelock. testing yours now :)
[Nexus 6  Original Android Development] wrongway213:
Testing it out, thanks for looking into the issue Franco! Once again when you and Imo work together we all win and once again something good happens by close to midnight EST and I am out of thanks, so thank you.
[Nexus 6  Original Android Development] DPretzelK:
Hi Franco... I really need your help, take a look to this please:

[YOUTUBE]f_tQuSVmdyE[/YOUTUBE]

I don't know how to fix that... And sometimes the same problem appears for "Tap To Wake", I put it " Disabled" but even if it works like in the video, if I reboot or I just let some time pass when I check the value again it's turned back again to "Enabled". :crying:
[Nexus 6  Original Android Development] franciscofranco:
As said before, you're low on battery, the thermal driver automagically caps your max freq when you're like below 20%.

double tap to wake is enabled because if you have a rom with a custom powerHal that enables the feature every time you screen off/on.
[Nexus 6  Original Android Development] slekkas:
Call me silly but how do in install that boot.img?
[Nexus 6  Original Android Development] insty:
fastboot flash boot boot.img