yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] ptmax13:
OK, I know this sounds weird but bear with me a while.

Up until 6.0, Elemental has been stellar for my DEB.

With 6.0 and until 6.0.1 I've been noticing weird battery usage issues. I've downloaded several apps, thinking it's a software issue. Apps like LeanDroid and Naptime.

They didn't do much.

Battery stats didn't say much either. The Tablet was loosing 10%-20% battery in a day, just by standing on my desk, looking pretty.

Battery stats was showing 3-4 entries, which added up to 5%, and there was 20% missing from the battery percentage.

Sometimes I was leaving the tablet with 60-70% battery and when I came back from work the other day, it has shut-down, dead, with 0% battery.

And this is a 4-months old tablet, with super battery endurance until 6.0.

I tried a lot of things, resetting to factory defaults, different TWRP versions, SuperSU versions, installing-uninstalling several apps. NOTHING.

The only thing that remained unchanged was the ElementaX.

So I tried this: flashed stock kernel, charged to 100%, left tablet on a desk for a day, I CHANGED NOTHING ELSE except kernel....

BOOM! 99% when I checked back after a day...

So, I gave ElementalX another chance. I re-flashed it, leaving all defaults...

Battery usage was abysmal as before stock.

I tried changing some battery hungry settings, f.e. I disabled Double tap to wake and all swipe gestures.

Still, unchanged behavior. So I've given up and returned to stock.

To be honest, I only miss the double tap to wake, as the tablet performs just as well with stock 6.0.1.

So, am I the only one?
[Nexus 7 (2013) Original Android Development] DroidIt!:
I have seen that before, but actually the culprit was google now. I'd maybe try uninstalling and reinstalling that. I believe it was through better battery stats I was finally able to figure that out. I'm not saying that's your issue, I would still grab BBS and take a look, but I'd still go the in/reinstall route. :)
[Nexus 7 (2013) Original Android Development] ptmax13:
Unfortunately it's not G.Now, I never use it and I have it disabled on all my devices.

Like I said, I tried many things, amongst them uninstalling common battery hogs, but to no avail.

And Like I said, The only thing that I changed to fix the battery drain was that flashing of stock kernel. The rest remained the same as before.

For me, there's no doubt that ElementalX is the culprit. I just want to know if it's a specific setting that is to blame, so I can have my dt2w back...
[Nexus 7 (2013) Original Android Development] flar2:
I don't think anyone would use this kernel if it drained like that. Kernels essentially never cause drain. Battery is used by apps and services, especially ones that keep the phone awake.

Last night my N7 drained 0.6% per hour, which is actually slightly more than usual. I have sweep2wake enabled too.

The problem is something else in your setup.
[Nexus 7 (2013) Original Android Development] Dlewczyk:
Try the same test with WiFi off. There's a bug in Marshmallow that causes battery drain when not connected to WiFi and WiFi is left on.
[Nexus 7 (2013) Original Android Development] ptmax13:
I use LeanDroid, which is set to disable Wifi, GPS, Mobile Data after 10 minutes of screen being off.

I could also see from the battery stats graph, that wifi was off during sleep, but the battery drain remained.

I know that this kernel is excellent, I was using it before these issues. I'm not writing this to troll, but I must insist that it's the kernel to blame for the drain. I changed nothing else except the kernel and my battery usage is excellent again. No settings, no apps, no nothing else.

Has anybody else here used ElementalX with a DEB device, Android M and no sim-card in?

Maybe it's something about M and DEB specifically, I don't know. I'm just sharing what I found, and hope for a workaround.
[Nexus 7 (2013) Original Android Development] Dlewczyk:
I don't know about LeanDroid, but if there is a bug in the OS, how do you know if WiFi is really being turned off? I was using Franco until Marshmallow came out and moved to ElemenatlX because it was available and Franco wasn't. I noticed the same problem between stock and ElemetalX and was ready to stay on stock until I noticed the WiFi problem. I was recounting my experience as a possible explanation for your observation.
[Nexus 7 (2013) Original Android Development] ptmax13:
I know that Wifi is turned off from the Battery Stats graph. If you click on the graph to get it to display in full screen, it shows you this info below the main graph.

Unless this graph is not to be trusted, I can see that it's being turned off as I have instructed LeanDroid to do it.
[Nexus 7 (2013) Original Android Development] pilotv:
I have same problem here as you can see in attached image. The battery is always draining and I discovered when I close the magnetic cover the WiFi is always on.

I have same problem here as you can see in attached image. The battery is always draining and I discovered when I close the magnetic cover the WiFi is always on.

Sent from my N7 + ElementalX + Multirom + MM6.0
[Nexus 7 (2013) Original Android Development] ptmax13:
Thanks, but I don't have a case for my n7. I've also tinkered before with this setting but it didn't fix my drain.
[Nexus 7 (2013) Original Android Development] drewski_1:
i have this setup of Deb & no sim-card, except on Stock Rooted M
[Nexus 7 (2013) Original Android Development] SurferLTU:
After update to 6.0 and 6.0.1 I'm also experiencing battery drain. I also thought that it was kernel problem, but after I removed it the drain was still there... I think it's google's problem and specifically related to Wifi.
[Nexus 7 (2013) Original Android Development] DroidIt!:
There's a common thread with you guys, but it's not the kernel. If you guys think about it, there would have been many many more reports here of battery drain. What I would do in all your cases is do a full wipe/clean install of your ROMs and leave your devices bare bones minus a battery monitor app like Better Battery Stats and see what you come up with. Try browsing the internet for a bit, leave the tabs unplugged and do this for about a couple of hours at least. Go into the battery app and see what you can see. If there's drain, it's probably the ROM. If there isn't then it's a user app and you'll need to figure out which app it is. That's the easiest and quickest way to get to the bottom of what the issue is for each of you.

For what it's worth, I'm not sure I ever saw unusual battery drain on my flo. Almost 3 years old and still performs like a champ with both Slim and Dirty Unicorns. :)

---------- Post added at 04:07 PM ---------- Previous post was at 03:15 PM ----------

As an add-on :) If you do see battery drain on a bare setup and it just says "android", my guess would be it's the main google app...which is why I suggested to uninstall it and reinstall from the play store. Battery drain could be a LARGE number of things, but that's my best guess and something fairly simple to try out. ;)
[Nexus 7 (2013) Original Android Development] WhoIsJohnGalt1979:
For cm13 6.0.1, flash the cm kernel which is 6.0 or the aosp 6.0.1 kernel? Apologies for being a noob
[Nexus 7 (2013) Original Android Development] islammanjurul:
You need to flash CAF/cyanogenmod version, for cm13 6.0.1, it is not yet available. For 6.0 it is there on first post. Always look at the first post, see if the relevant kernel for your rom is there or not.
[Nexus 7 (2013) Original Android Development] marsaltito:
Just use 5.05 cm kernel(6.0) . i run latest cm13(6.0.1) with it ! .
[Nexus 7 (2013) Original Android Development] LucentBirch:
Anyone get stuck on Android boot animation with 6.0.1?

---------- Post added at 04:33 PM ---------- Previous post was at 04:16 PM ----------

Okay, I unchecked selinux enforcing and it booted, but now I'm getting "Google play services have stopped" over and over
[Nexus 7 (2013) Original Android Development] flar2:
There is a problem with your ROM
[Nexus 7 (2013) Original Android Development] flar2:
After the holidays I will work on a couple of the issues mentioned here, but for now, I'm heading home for the holidays.

Merry Christmas to everyone!
[Nexus 7 (2013) Original Android Development] Extreemator:
Playback apple headset control fails to work after a minute in standby mode

This is observed under stock kernel on cm13 also. Apple headset is not comlatible but middle button works, tbe the problem that it stops working shortly after went into standby. Can it be fixed?
[Nexus 7 (2013) Original Android Development] matthew2926:
Sorry if this has already been answered but I couldn't find it anywhere. I'm new to using custom kernels and I was just wondering why Cyanogenmod requires its own Elementalx kernel distro. Like, what is the reason for there being a stock/asop and a cyanogen version? Why won't the stock elementalx work with a Cyanogen ROM? Thanks in advance!
[Nexus 7 (2013) Original Android Development] drewski_1:
Kernel fork. Google search for CAF
[Nexus 7 (2013) Original Android Development] matthew2926:
So then my follow question is, why does the Nexus 7 require a special Elementalx CAF kernel for Cyanogenmod while the Nexus 6 only has one kernel that is for Marshmallow 6.0.1?
[Nexus 7 (2013) Original Android Development] DJMartini:
It all depends on the Dev if they fork/pick to build their ROM With CAF. CM uses CAF but ROM devs chose what they want when they build. There are a lot of different custom kernels for devices but it all depends on what devs build for and what is supported.

I use this kernel CAF with stock CM13 on my N7 but on my N6P I'm using temseak ROM with AK kernel
[Nexus 7 (2013) Original Android Development] matthew2926:
So the Elementalx kernel provided for the Nexus 6 won't work with Cyanogenmod?
[Nexus 7 (2013) Original Android Development] DJMartini:
Not sure if you're referencing N6 or N6P, but I have a N6P and as I recall ElementalX kernel is available and has a thread here http://xdaforums.com/nexus-6p/orig-development/kernel-elementalx-n6p-t3240571
[Nexus 7 (2013) Original Android Development] matthew2926:
I was talking N6 since that is my primary phone but it seems to be the same for the N6P. Does elementalx for the N6 or N6P work with Cyanogenmod?
[Nexus 7 (2013) Original Android Development] flar2:
yes, for N6 and N6P, it does.

However, this is the thread for the N7
[Nexus 7 (2013) Original Android Development] matthew2926:
Understood, I was just trying to figure out why the Nexus 7 requires separate builds for asop and Cyanogenmod while the 6 and 6P seem to have a build of elementalx which works across all ROMs. I still don't know why it is this way, but I now recognize the existence of such circumstances...
[Nexus 7 (2013) Original Android Development] flar2:
It's because cm diverged a lot from stock on older devices. Lately they have not been doing this on newer devices (which makes things a lot easier for me)
[Nexus 7 (2013) Original Android Development] matthew2926:
Hey man, sorry for the attitude, I didn't realize I was talking to the dev. Thanks for all of your hard work as well as all of the info that you have provided me. If I ever get into custom kernels, Elementalx is where I will be starting!
[Nexus 7 (2013) Original Android Development] mdamaged:
NM
[Nexus 7 (2013) Original Android Development] DroidIt!:
Welllll, whatchu waiting for? ElX is probably the best kernel I've seen after trying ~20 kernels across 8 devices over 5 years. Flash away, you're missing out. ;)
[Nexus 7 (2013) Original Android Development] 53l3c7a:
A Wisconsinite! Greetings from Milwaukee :)
[Nexus 7 (2013) Original Android Development] matthew2926:
I actually just flashed it for my Nexus 6. I normally flash things that I have never tried before on my Nexus 7 (2013) but I was too excited to get into the whole custom kernel scene, so I just dove in with EX for my Nexus 6, which is my daily driver. Gotta say, it's very smooth and the sweep to wake is probably one of my favorite features. Just hoping that the battery life is decent as well. The power saving mode seems like it would be very useful as well. Also, for any other noobs to flashing custom kernels, the EX kernel manager app is well worth the $4, especially if you plan to use EX as your daily driving kernel.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Huh, that's cool...Kenosha for me :)
[Nexus 7 (2013) Original Android Development] The Destroyer:
I've tried reading through many pages of this thread, but I couldn't find anybody with posts for governor settings with this kernel.

Does anybody have any recommended governor cpu settings they'd like to share with optimal battery life? Much appreciated!
[Nexus 7 (2013) Original Android Development] DroidIt!:
I set the CPU max at 1.7 GHz and leave it on ElX gov and the GPU at 477 and stay with on demand. So just bump up the speeds a bit and stay with flar's picks for governors. If doing heavy gaming that gets me 5 to 6 hours screen on time and if reading about 10 hours. If you want slightly more oomph but still pretty good battery, you could change the CPU gov to on demand and GPU to simple. Hope that helps. :)
[Nexus 7 (2013) Original Android Development] WhoIsJohnGalt1979:
+1
[Nexus 7 (2013) Original Android Development] DaveImagery:
Just flashed MMB29O, with 5.06.

Anyone else notice double tap to wake not working?
[Nexus 7 (2013) Original Android Development] 8thphloor:
Nope. Just flashed MMB29O, 5.0.6 and latest supersu and everything works like a charm ;)
[Nexus 7 (2013) Original Android Development] DaveImagery:
Okay thank you, something weird going on with mine I guess. Need to put on my detective hat.
[Nexus 7 (2013) Original Android Development] flar2:
Looks like there were no kernel changes in the January security update from Google. You may continue using the latest version of ElementalX.

There will be an ElementalX update soon, but it has nothing to do with this.

As always, it is recommended to flash the stock boot.img if you do the update, in order to have the latest ramdisk.

Procedure for updating:

1. Download factory image from Google

2. Extract boot.img and system.img and flash these in fastboot mode:

fastboot flash boot boot.img
fastboot flash system system.img

3. Reboot to recovery (important--don't reboot to system)

4. Flash SuperSU

5. Wipe cache and Dalvik cache

6. Boot into system (may bootloop once, it's okay)

7. Install ElementalX (either with the EXKM app or in recovery)

NOTE: there was no update to the bootloader, so I've omitted this from the instructions above.
[Nexus 7 (2013) Original Android Development] hoqpus:
will there be a version for cm 6.0.1.?
[Nexus 7 (2013) Original Android Development] flar2:
Yes. I think the current cm version works, but I will be updating soon anyway.
[Nexus 7 (2013) Original Android Development] enesas:
Work with pure nexus project (latest build FLO)?

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Nexus 7 (2013) Original Android Development] :
It's working flawlessly for me :)
[Nexus 7 (2013) Original Android Development] enesas:
Select during installation " Enforcing " (Pure Nexus Project FLO)?
[Nexus 7 (2013) Original Android Development] ecs1984:
Just like [MENTION=3200478]Woody[/MENTION] kindly told you in the Pure Nexus thread, you need to start searching on your own for such questions. This question has been asked and answered countless times. You can find the answer here: http://xdaforums.com/showpost.php?p=63764122&postcount=5087
[Nexus 7 (2013) Original Android Development] greves1:
Latest purenexus build here, and I just can't get 5.06 to work. It just sits forever at boot. I DID uncheck the enforcing option. Never seen this before. Any ideas?
[Nexus 7 (2013) Original Android Development] Tool Belt:
Originally from K-town, in Plover now.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Lol :) Small, small world. Lived in Plover when I went to UWSP.
[Nexus 7 (2013) Original Android Development] Tool Belt:
Excellent, wife works at UWSP.
[Nexus 7 (2013) Original Android Development] mdamaged:
My cat's name is Mittens.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hey! Now that's too personal for the thread! :p
[Nexus 7 (2013) Original Android Development] greves1:
Hi there,

I've tried twice to install v5.06 on the latest purenexus (6.0.1) build, and each time it gets stuck in bootloop. Could this be because I didn't flash the new boot.img from 6.0.1 factory image? I am on the 6.0 factory image boot.img currently, but there was nothing in the purenexus thread about needing the new boot.img so I tried without upgrading, and it worked fine. Perhaps EX kernel isn't working for another reason, though, so I'm asking you fine folks. I am leaving the enforcing unchecked, as advised by everyone for this rom... Been using EX for years on various devices and have never had a problem before. Thanks!
[Nexus 7 (2013) Original Android Development] flar2:
I'm not sure what the problem could be.

I suggest dirty flash Pure Nexus and make sure it's working, then flash elementalx.

With pure nexus, no extra steps are required. It should just work.
[Nexus 7 (2013) Original Android Development] efan3719:
working fine with me with a clean flash. you shouldnt need to uncheck enforcing anymore. he's since updated the rom to allow it to work in enforcing mode.
[Nexus 7 (2013) Original Android Development] greves1:
So strange, I really don't know what's going on with here, but I just did a clean install of the latest build, flashed the recommended gapps, rebooted, set up a bit, reboot to recovery, backup, flash EX, and bootloop! Wish I knew what I could do to make it work!
[Nexus 7 (2013) Original Android Development] flar2:
Send a log and maybe we can see
[Nexus 7 (2013) Original Android Development] efan3719:
Well here's what I did when I installed. Wipe system, data, cache. Install ROM, gapps, then kernel before reboot. When I booted everything setup just fine.
[Nexus 7 (2013) Original Android Development] greves1:
Hi, I know there are guides for making logs, but being a little bit lazy today, might you be able to tell me how to do this, or point me to a particularly useful guide for this type of problem? If not, no problem I'll look into it myself later. Thanks.

---------- Post added at 04:21 AM ---------- Previous post was at 04:20 AM ----------

Tried exactly this after reading your post and stuck in bootloop again. So weird... I'll try to get on the log situation when I have some time.
[Nexus 7 (2013) Original Android Development] Windsor1959:
I have a question about encryption - whether Elemental X is compatible with it and what settings in Aroma I may (or may not) need to change to make it compatible. I am running the latest Pure Nexus 6.01 ROM. I installed Elemental X 5.06 and it ran flawlessly. Then, because I wanted to set up Outlook with my Exchange email account (and the account required encryption), I decided to encrypt my tablet. When it rebooted, it stayed stuck in a boot loop at the point where you see the four shifting colorful shapes. I rebooted to recovery, did a factory reset. Still the bootloop. Then I wiped system and reinstalled Pure Nexus. Then my device booted up normally and was encrypted. I then tried installing Elemental X. Bootloop. Then I dirty flashed Pure Nexus. No bootloop.

I'd like to use Elemental X, but i can't seem to figure out how to make it work with encryption. Any hints?

BTW, if I wanted to decrypt my Nexus, would a factory reset do it (doubt it, based on what I said above), or do I need something more radical? Thanks.

PS - I tried Elemental X with the SELinux Enforcing option checked and then unchecked. Same result.
[Nexus 7 (2013) Original Android Development] szty0pa:
Hi, I also had problems with encryption, but I think there is more with the recent builds of Android. Lately I've been using the Glitch kernel on Flo with CM13. It was working good with nightly builds from December, but having a similar bootloop with the January nightlies as ElementalX (soft-rebooting just before it would ask for the password). So something more serious might have also changed recently in the AOSP/CAF sources, just as a hopefully helpful side-note.

I 'm not sure if you can decrypt your device without using a PC, but you can erase the /data partition (that is the one being encrypted) resulting it being not encrypted anymore.
[Nexus 7 (2013) Original Android Development] Windsor1959:
Thanks! That helps me see what may be going on here. Other than the fact that I can't use Elemental X, my Nexus is running fine encrypted thus far. I have a PC with adb and fastboot set up, but I'll wait and see how my encryption experience plays out. If it seems that having Elemental X on my device is more important than Outlook, I'll find out about decrypting.
[Nexus 7 (2013) Original Android Development] flar2:
The multirom patch seems to break encryption. I will look into this and see if we can have both.
[Nexus 7 (2013) Original Android Development] Windsor1959:
Thanks for your reply, and all your efforts with this kernel!

I just noticed that you are from Ottawa. I went to school there. Great city.
[Nexus 7 (2013) Original Android Development] Cosolord:
Hi flar2, it's possible to have cifs support with the last kernel ? I have andorid 6.0.1 on my nexus now but i can't use cifsmanager as always (with selinux permissive too).

There is something that i can do ? Any chance for me?

Thank you :good:
[Nexus 7 (2013) Original Android Development] s2k7:
+1
[Nexus 7 (2013) Original Android Development] szty0pa:
Hi Flar2,

Yes that could be a problem (I have the multirom twrp installed, but not injected it into the rom), I haven't thought of that!

Thanks for your great work! :)
[Nexus 7 (2013) Original Android Development] Deeco7:
Probably mentioned many times, but does this kernel support Deep Sleep like timur's? thanks
[Nexus 7 (2013) Original Android Development] FrenchSparda:
My 2 cents question guys...does this kernel support Power event manager, very useful in Timur's kernel for car installation
[Nexus 7 (2013) Original Android Development] Ashwin Prabhunerurkar:
could you update the cm mm kernel to 6.0.1 when you get itme
[Nexus 7 (2013) Original Android Development] jervis93:
he mentioned earlier.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

A small update to fix booting on encrypted systems. I had a look and it turns out it was not multirom, but the f2fs entries in fstab.

Those who use f2fs will have to uncomment the relevant lines in the installer zip (boot/editramdisk.sh). If you are currently using f2fs, you can just flash. The installer edits are only on clean install.

I also added some extra display settings from cyanogenmod. One is a power saving mode for the display, and the other changes the brightness and contrast. I will add these settings to EXKM in the next update.

Updates for stock/AOSP and CM/CAF

Download

ElementalX-N7-5.07

ElementalX-N7-5.07-cm

Changes:

-add cabc and sre

-fix installer (now boots on encrypted systems)
[Nexus 7 (2013) Original Android Development] Windsor1959:
Yes! I installed 5.07 on my encrypted Nexus, and it booted just fine. Thanks, flar2, for your continued commitment to Elemental X!
[Nexus 7 (2013) Original Android Development] chickentech:
Thanks!! I had wondered why my system wouldn't boot when I encrypted a while back. Love the hard work and great kernel [MENTION=4684315]flar2[/MENTION]