yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] mattmtx:
No, I don't use ambient display,neither use Mobile data all the day (only while I travel to the work or when I back to home, *and it is a good signal). And yes, I use Music player one hour in the morning and one hour in the afternoon, with Bluetooth earphones

I already had buyed, and I install it again. I will check in a few hours how it's working.
[Nexus 6  Original Android Development] flar2:
There you go, two hours of music via bluetooth. I think your battery usage is perfectly fine.
[Nexus 6  Original Android Development] magnamentis:
but you need the beta version which you can download only by joining the beta program in G+, perhaps you know, then sorry, else hope it helps.

EDIT: sorry i was unclear, it's 0.85-0.95%/h awake not battery drain, battery drain is 1-2% in 10h overnight and around 0.2-0.3/h, all on during day time with 8 mailaccounts syncing on wifi mostly. will go and edit the orginal post as well.
[Nexus 6  Original Android Development] LONGMANi:
In this kernel implemented possibility to record voice from line in? As I remember, this is blocked in native kernels
[Nexus 6  Original Android Development] mattmtx:
Ohh, ok, perfect I already found it and install it, also activate doze mode. :D Thanks!
[Nexus 6  Original Android Development] magnamentis:
hehe... ¡Qué copado! looks like if i was bit late answering your PM. however posting the link here for others then. hope it works well for you as it does for me :)

https://plus.google.com/communities/103850238949791125024
[Nexus 6  Original Android Development] slickie88:
The OnePlus' 1080p display helps quite a bit in terms of SOT and that accounts way more for battery life than TW vs AOSP.
[Nexus 6  Original Android Development] housry23:
I realize that, but, it was also waaaay better in idle drain as well. With Google talking up project volta, I'm disappointed in the battery life here. The note 4 does better than the nexus. Why's that? Because it's better optimized. It is good enough, but not as good as I expected it to be. Hopefully it gets better with updates.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Krunk83:
Haha. Yup. I too had a OnePlus One before this and that battery was much better. I could get 6hrs SOT easy. The N6 is a different battle. I'm hoping google puts out an update to fix the battery. Right now barely get 4hrs if I'm on WiFi all day.

nexus 6

---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------

My buddy gets like 8hrs SOT on his note 4. Pretty ridiculous.

nexus 6
[Nexus 6  Original Android Development] flar2:
I'm hoping to release an update later tonight. I've been working on a new governor that should get a bit more screen time. I go for a balance between performance and battery life, never compromising smoothness. I've been using it for a few days and I was only using about 35-40% battery each day, so I can easily get two days on a charge. I don't spend hours on my phone each day, maximum two, mostly browsing, email and texting. I'll be fine tuning it in the coming weeks.
[Nexus 6  Original Android Development] resynx:
Can't wait to see what you've got in store for us flar :)
[Nexus 6  Original Android Development] flar2:
Update!!!

Finally...

The update brings a few changes, I've started to optimize things and will continue for the next few releases. I just want to do a few things at a time to make sure everything is good.

The default CPU governor is now elementalx, which I have revamped for the Nexus 6. I think it gives smooth performance and better 3D gaming than interactive while not raising the frequency as much. I customize the governor for each device and will continue to tweak it as needed. This version of elementalx governor is a bit simpler than the one on the Nexus 5. I recommend leaving gboost enabled for best performance. I don't think you'll save much battery by disabling it.

I added USB fastcharge, which is disabled by default. This will increase the current limit from 500mA to 900mA when charging via a USB port.

There are a few fixes and enhancements for s2w/dt2w. I added optional and adjustable haptic feedback for the built-in doubletap2wake. And I disabled the wake gestures during phone calls, so the screen won't register touches while blanked during a call. Remember, sweep2wake adds about 0.6% per hour extra standby drain. Doubletap2wake does not add additional drain. I have a few ideas to reduce the sweep2wake drain, but I haven't had a chance to try them yet.

Other than that, a few other tweaks and optimizations.

Let me know if there are any troubles.

Download:

ElementalX-N6-0.07 (alpha)

Changes:

-haptic feedback for stock dt2w

-prevent touches during phone calls while s2w is enabled

-add elementalx governor

-add USB fastcharge

-update installer

-update ramdisk for Android 5.0.1

-fix simple-ondemand GPU gov

-various tweaks and optimizations
[Nexus 6  Original Android Development] flar2:
Great to see you here too :cheers:
[Nexus 6  Original Android Development] Johnny424:
ex gov with simple really has things very smooth. nice release flar. thanks for fast charge as well
[Nexus 6  Original Android Development] drawde40599:
Is your battery 20% or lower ?
[Nexus 6  Original Android Development] KrazyAttack:
Just flashed, using the ElementalX CPU governor now over interactive and simple ondemand for GPU. Deadline, fsync disabled, TCP Westwood.

Only thing I see is the app tells me an update is available and shows 0.06 as latest kernel despite being on 0.07. Minor.
[Nexus 6  Original Android Development] gamewarden234:
I'm a moron. Thanks.
[Nexus 6  Original Android Development] drawde40599:
[MENTION=4684315]flar2[/MENTION] Since this question is going to come up 1000x, flashing Rom is needed to change kernels or go back to stock right ?
[Nexus 6  Original Android Development] flar2:
Forgot to add it for Android 5.0, will do now.
[Nexus 6  Original Android Development] drawde40599:
There are users getting 8 hours on N5 and N6 also , just depends on how much you wanna "disable " your device
[Nexus 6  Original Android Development] flar2:
I am using a complete boot.img this time, so you can flash this over another kernel, no need to flash stock first. Just have to watch out for scripts or apps messing with the settings. I no longer have /etc/init.d/99elementalx either. The script is now in the ramdisk to guarantee it runs at boot. I'm trying to make this more seamless and bulletproof than the N5 and N7 kernels.
[Nexus 6  Original Android Development] drawde40599:
Same thing applies to go from ElementalX to Stock or go to another kernel ?
[Nexus 6  Original Android Development] flar2:
Yep, you can just flash the stock boot.img. All that is left is /etc/elementalx.conf (which I am thinking about moving somewhere on /data for easier OTAs)

For other kernels, it depends on how they are set up.
[Nexus 6  Original Android Development] flar2:
I just used 8% battery in the past 40 minutes (reading and replying at XDA in browser, ssh to my server, and watched an episode of south park). That puts me on pace for potentially 8 hours of screen time. I don't disable anything.
[Nexus 6  Original Android Development] flar2:
Here we go:
[Nexus 6  Original Android Development] tealio:
ElementalX provides the absolute best battery life ever... Haha

Any ideas why this happened?
[Nexus 6  Original Android Development] magnamentis:
it's doze mode ( api23 ) that makes it happen. the kernel, on the positive side, depending on usage and setup is responsible for 10% of the results max. ( not counting extreme setups with extreme UC and UV ) which would reduce performance.
[Nexus 6  Original Android Development] tealio:
Note the "Haha" and the screenshot...

Apparently my device has been on for a VERY extended time, and has GAINED 91% battery while screen off and not charging....
[Nexus 6  Original Android Development] magnamentis:
did not look to be honest, thought it was a serious question, hence you pulled my leg though. [fun]
[Nexus 6  Original Android Development] tealio:
Well I got you twice then... I was jokingly saying ElX gave me superior battery life... But I was seriously asking how the data in that screenshot could have happened...

Phone charged while I fell asleep on the couch... Made it to 100%. Moved to bed around 1am and took my phone w me where it sat unplugged til about 4. It was at 98% at that point. Rebooted since my phone had been up for a few days. After rebooting, used it for a couple minutes and looked back at the battery stats (ElX app) and it looked all crazy like the screenshot.

Only thing I can think of is that for some reason ElX asked me for Root priv again

Can't remember whether it was before or after reboot. Was the app updated recently? Could not having Root for a while make the app make such gross miscalculations?
[Nexus 6  Original Android Development] magnamentis:
i don't know because i never experienced that. you can check by revoke root access for the app in superSU access > deny or deny+time and see what happens. on the other side if it happened just once and will not re-occur you can look at it as a one time glitch.
[Nexus 6  Original Android Development] tealio:
Yep... That was it. I'm assuming the app lost Root when it updated.

Regardless, when I intentionally denied it Root and rebooted, after granting Root it gave me crazy numbers again.

Crisis averted.
[Nexus 6  Original Android Development] flar2:
That's a glitch in the battery monitor. It works most of the time, but that bug shows up a lot. Unfortunately, I need to redo the whole thing from scratch so i haven't gotten around to it.
[Nexus 6  Original Android Development] mattmtx:
Try to reset statictis.
[Nexus 6  Original Android Development] mattmtx:
Oks, after a day, here is my drain %.

I don't know why the active drain increased a 5% jajaja
[Nexus 6  Original Android Development] tealio:
OK... It seems to happen after a charge. The root request was a coincidence. It's doing it again now. No big deal. Glad you're aware of it. Thanks.

ETA: It is messed up on the 'Since Start' setting, but I did a 'Since Now' around 645am and its showing sane stats.
[Nexus 6  Original Android Development] AverageLibrarian:
I went into the kernal manager and changed the CPU max frequency now it won't go back to 2880 like it used to be! HELP! It is stuck in a lower than stock frequency!
[Nexus 6  Original Android Development] flar2:
Is your battery at 40% or less? Or is your phone warm? Those are things that can lower the frequency temporarily.
[Nexus 6  Original Android Development] AverageLibrarian:
Lol it is at 38%
[Nexus 6  Original Android Development] Lagarde:
A little belated to the topic, but I also was getting the random lock/reboot.

- Kernel 3.04, 3.02, 3.01, no issues at all. Problem appeared within 1 hour of upgrading to 3.05 (I know it's not supposed to have any changes that matter). DT2W enabled on all versions.

- Downgraded to 3.04 and issue vanished. DT2W still enabled.

- Upgraded to 3.05 and issue returned.

- Wipe, reload on 3.05. Issue occurred within 2hrs.

- Downgraded to 3.04 and issue vanished.

No clue why, just providing some data. Happy on 3.04.

Additional notes: Reboots always happened within 10 seconds of unlocking and always when typing. Verified on both stock and swiftkey keyboards. Just was able to cause the reboot on 3.04...appears to have a chance to happen if EX Kernel Manager is applying any CPU speed, sound, or governor changes on boot. Removed the on-boot changes and no reboots.
[Nexus 6  Original Android Development] flar2:
3.05 has one small change.

Can anyone else who has experienced reboots consistently try downgrading to 3.04 and see if it helps?

Hopefully that commit isn't unstable (it shouldn't be) but you never know. I could make it optional if it turns out to be unstable.So far I have not had any issues on 3.05 (or any other versions).
[Nexus 6  Original Android Development] suku_patel_22:
[MENTION=4684315]flar2[/MENTION] Would it be possible to add some kcal profiles to the aroma installer? I use my n6 without root.

This would make it really useful.
[Nexus 6  Original Android Development] flar2:
I'll think about it.

For another more urgent matter, I see you got some reboots on franco's kernel. Can you test with EX 3.04 and 3.05? If you get reboots with 3.05 and not with 3.04, it might solve the problem.
[Nexus 6  Original Android Development] suku_patel_22:
I will surely try. It's very rare. Probably on GPU overload.
[Nexus 6  Original Android Development] franciscofranco:
You think it might be: https://github.com/flar2/shamu/commit/c1629261675f0d917aa1beaae7361e5ddd026ea6 ?
[Nexus 6  Original Android Development] flar2:
That is the only change between version 3.04 and 3.05 of my kernel.

I think there might be a situation that simulates a power key long press and reboots the phone.
[Nexus 6  Original Android Development] franciscofranco:
Yeah, it explains the empty console_ramoops. I wouldn't have linked to the commit if you didn't say you only changed one commit between your two updates. I'll keep an eye on this thread.
[Nexus 6  Original Android Development] Formhault:
This is unrelated to the reboot that has a chance of occuring randomly just a few seconds after a finished (intended) reboot, right?
[Nexus 6  Original Android Development] TonyTurboII:
Tried digging through the last 150 posts, couldnt see a definitive answer, so If I didnt go back far enough or I missed it I apologize.

I tried flashing just the kernel, and the device would not boot.

Decided to add in the permissive boot. Tried flashing it after and before the kernel, no dice.

Guessing im going to have to add the chainfire boot img as well.

What order should I flash these in?

Im running the latest PureNexus.
[Nexus 6  Original Android Development] nathanchance:
I have heard flashing the permissive zip then the kernel zip will not involve the boot.img but I prefer the boot.img then the kernel zip to get an Enforcing kernel versus a Permissive one with the first one.
[Nexus 6  Original Android Development] magnamentis:
did you have another custom kernel installed before you tried EX? if so you'd have to dirty flash your rom over before flashing EX, if not try the other recommendations, no idea because it never happened to me on N5 as well as N6. BTW i heard about similar issues from several sides with this rom, not a qualified answer but still an observation which could be considered. try cataclysm if you have furhter issues, it beats them all anyways and it's 99% stock + 9 lines of extra code.
[Nexus 6  Original Android Development] NLBeev:
Is it possible that is has to-do with sepolicy? After flashing custom Rom's my N6 was working as expected. But after flashing another kernel (enforcing) I can read but not write system files like build.prop, and the layers in system/vendor/overlay
[Nexus 6  Original Android Development] nathanchance:
Some ROMs require a permissive kernel to do that I believe but the whole point of the modified SEPolicy is to allow root with r/w to the system partition with Enforcing SELinux status I believe. You have to make sure that you follow the particular kernels instructions when it comes to flashing because some require Chainfire's modified boot.img, others do not
[Nexus 6  Original Android Development] magnamentis:
yes, that's exactly one of the possible issues, some apps don't perform properly. i for example cannot see the "clockworkmod" folder with my nandroid backups in enforced mode with two very reputed file managers and the build.prop write error has come to my attention as well. just download SELinuxMode Changer app and set to permissive and all is working as expected.
[Nexus 6  Original Android Development] NLBeev:
OK, but then the selinuxmode is disabled. That opens the question what's the use of kernels with sepolicy on?
[Nexus 6  Original Android Development] magnamentis:
the features and advantages of a specific custom kernel is not affected by either SELinux mode. it's like if your device is encrypted or not, everything is looking and working the same way. i think you mix something up and if you're concerned about safety you would have to consider what you are using your device for and then read ( google search ) for the origin of SELinux and think which security risk is higher for you, the one that someone can see something unimportant on your device or those who do it permanently. you have to read up to understand the meaning. not the right place to disuss this here.
[Nexus 6  Original Android Development] NLBeev:
Just wanted to disable forced encryption and use the M6.0 stock with root and custom kernel.

And you are right I mixed something when flashing and found out the differences when flashing custom kernels. (persmissive and enforcing)

It do not want to open a discussion about safety, sorry for the misunderstanding.

I am just curious why making a kernel enforcing, because most of the flashers are already rooted.

Thank you for your response.
[Nexus 6  Original Android Development] magnamentis:
[/COLOR]

all well sir :) i did not want to imply that you start a discussion, i only explained why i won't post more details on the matter and therefore recommend to look it up in google search LOL. no problem and good luck finding your perfect setup. if you have any more questions just PM me, don't hesitate. cheers :good:
[Nexus 6  Original Android Development] flar2:
Stock is enforcing, and so are all the kernels in the Original Development section. Root works with selinux enforcing and anything else can be made to work with selinux enforcing using the supolicy tool. Selinux (actually seandroid) is part of the operating system, it should not be disabled, especially when it doesn't really prevent us from doing anything. If someone needs permissive, then I made a flashable zip to do so. There is little need for permissive, aside from some apps that haven't been updated to work on Marshmallow, which the devs should update.
[Nexus 6  Original Android Development] lords8n:
SuperSu

Hey flar2, I know this is an extremely experimental beta, but any chance we'll see Chainfire's no /system mod root incorporated into EX? :

http://xdaforums.com/showpost.php?p=63197935&postcount=2
[Nexus 6  Original Android Development] flar2:
I haven't checked it out yet, but since EX keeps the existing ramdisk, it will probably work.
[Nexus 6  Original Android Development] kraehetest:
hello flar2

I want to thank you for the great kernel development. Stay a cool developer. :) :good:

thanks
[Nexus 6  Original Android Development] RandomPooka:
^^ or else!
[Nexus 6  Original Android Development] ArcMage:
Alright, I've finally had another crash and reboot. I'm linking to the last_kmsg and pstore contents for you.

Nothing changed since the last crash, phone was unattended on the charger all night and morning, and this happened somewhere in there.

To verify, that's stock 6.0, ElementalX 3.05, SuperSU 2.52 beta with Chainfire's boot.img, and the kernel's default install settings.

https://www.dropbox.com/s/a0smk15ajthrzgp/pstore.zip?dl=0

https://www.dropbox.com/s/pbojcxpe85wyuty/last_kmsg_31OCT.txt?dl=0

I haven't actually looked at them yet because I'm busy, so if it turns out to be something dumb I apologise in advance.
[Nexus 6  Original Android Development] flar2:
There are a million entries about battery health and then the watchdog initiated a reboot. It's the flaky hardware again, not much we can do.
[Nexus 6  Original Android Development] ArcMage:
Well, they're normal healthd entries, indicating a healthy battery on charge, but the watchdog kill isn't what it was doing before.

If it's hardware it's hardware I guess.
[Nexus 6  Original Android Development] :
Honestly.... With the frequency of those battery messages... Is guess that the function generating that message went into a death loop.... Causing the watchdog bite.
[Nexus 6  Original Android Development] ArcMage:
It's stable for arbitrary periods with it going on, though. It's in dmesg at that same frequency at all times.

Someone with a known good device, grab a dmesg or something that I can look at? Both of my N6s logged this same behaviour, and it'd be sad if I got two devices broken in the exact same way.
[Nexus 6  Original Android Development] flar2:
That message is normal, but on mine it's not nearly that frequent. It's hidden in between a lot of other stuff.

On yours, I don't see anything else but that line. There is no kernel error showing, just the watchdog bite. I don't know what tripped the watchdog.
[Nexus 6  Original Android Development] ArcMage:
That's because the phone was untouched on charge for something like 20 hours, there's other stuff in it when I'm doing anything with it.

The watchdog bite is not what it was doing before, though, yeah.

I dunno. Thank you for your amazingly prompt help. Sorry to keep bugging you with garbage problems.
[Nexus 6  Original Android Development] Brotuck:
Experiencing a few crashes myself. Twice the last three days. Both times i was playing a gameand the screen just froze. After a while a reboot occured. Is there any log i can grab and post ?

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] Formhault:
What's a watchdog kill / bite...?!

Also, what could be hardware? You mean the battery dying?!
[Nexus 6  Original Android Development] ancidroide:
Guys please help me :( I'm trying to flash EX on chroma rom marshmallow... So,I know that chroma needs a permissive kernel,so after Ex I also flashed the permissive.zip released by [MENTION=4684315]flar2[/MENTION] ... However my device doesn't boot... Is there something I may do???
[Nexus 6  Original Android Development] ArcMage:
The watchdog process is what caused the system shutdown, per the kernel logs. Nothing is wrong with the battery. That is in fact the exact thing healthd is reporting.

There might be something wrong with healthd, but that's not any less weird than a battery failure, really.
[Nexus 6  Original Android Development] NLBeev:
First get it working without flashing permissive. Zip. Check if you can change system files like build.prop and/or install layers.
[Nexus 6  Original Android Development] muppetmaster916:
For some reason every time I flash a custom kernel on this phone I get a big bowl of bootloops for breakfast. No clue why, I've never had trouble before.
[Nexus 6  Original Android Development] DroidIt!:
Have you tried with different rom's? As far as I can recall, I've flashed ElX with every ROM I've tried (at least 15-20 over time) and never had the kernel cause an issue. Is there something else you're flashing along with the ROM and kernel? What gapps are you flashing? When I flash I always do xxx ROM, slim gapps and ElX. No matter the ROM I'm flashing that combo has always worked for me. ;)
[Nexus 6  Original Android Development] wesley404:
I'm experiencing a different issue, I'm getting incorrect battery levels. Sometimes it will deplete to 5% and shut off and other times 27% and die. I have let it die and then charged to 100% and get similar results from time to time, is this a kernel reporting issue or a stock ROM issue?
[Nexus 6  Original Android Development] rignfool:
Dirty flash ROM...

Flash Chainfire boot.img

Flash Elemental X kernel...

Profit...

Now... Next time you see someone with this question... It's your turn to repost
[Nexus 6  Original Android Development] Formhault:
Okay.

Now... What's a watchdog kill / bite...?!
[Nexus 6  Original Android Development] ArcMage:
It's the watchdog seeing something it doesn't like and shutting the system down.
[Nexus 6  Original Android Development] nathanchance:
Had some pretty good battery life yesterday with ElementalX 3.05 and Cataclysm :good: If only I lived in an area with better cell signal
[Nexus 6  Original Android Development] Formhault:
Does this look okay? LightFlow seems to have been going off a bit... EX reported 2.51% drain per hour. During a 4 hour sleep.