yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] steveo17:
yeah idk what to do. this is my second 6P as well (returned the first one just because i wasn't sure if i liked it) and the battery life was comparable IIRC.

I start my day a 6 am off the charger, i take the train into the city (notoriously bad reception) and i read articles on the train in the morning. by the time i get to work I'm usually at about 80% battery or so with about an hour of SOT. auto brightness, NFC off, WIFI & Bluetooth on

one final note. my G2 had pretty similar battery stats to my new nexus so idk if its something i'm doing, the apps i use or what. the battery drains super fast when i'm actually using the phone (when the screen is on)

screenshots of my stats thus far

73% battery left at ~9:30
[Nexus 6P Original Android Development] flar2:
All of them. Do you get this problem on stock? Have you cleared cache and Dalvik? I never change anything with Bluetooth.
[Nexus 6P Original Android Development] Ramone360:
This based on almost a full day of usage ?
[Nexus 6P Original Android Development] dmarden:
I've really had great battery life with the 6P... with no real change stock kernel vs this one.

My phone is typically off the charger from about 6:30am when I get up until 1am when I get back into bed and put it on the charger.

I can sometimes get over 8 hours SOT, but typically it's around 7 hours SOT on days when I am using my phone very heavily. Even on those days, though... it's not quite dead when I put it back on the charger, though close.

Typically I only end up only using 3-4 hours SOT during the day, though... and the phone is usually still around 50% 19-ish hours later when I put it on the charger and go to bed.

Edit: I'm mostly on wifi all day in my office or home, LTE kicks in for the drives. Most use while in the office is twitter/web/email/SMS/FB Messenger. Slacker/Google Music while driving. Random amounts of everything when home.
[Nexus 6P Original Android Development] grayskul:
Not on stock. I'll upload them now. I'll also try wiping cache and dalvik.
[Nexus 6P Original Android Development] steveo17:
pm'd you about battery life.
[Nexus 6P Original Android Development] DMonster:
Just now updated to 6.0.1 stock with SuperSU 2.61, from 6.0.0 stock with SuperSU 2.52. Ofcoz, both of them with the latest ElementalX.

I don't have problem with the camera, but did have experienced LTE issue as what other people here said. It just kept as HSDPA. Though, I just find a way to solve it by first go to phone, dial *#*#4636#*#*, then go to Phone Information. Then in the "Set preferred network type" in lower part of the screen, the default was LTE/GSM/CDMA auto, I then changed to LTE/GSM auto and my N6P started to connect to LTE! Hope this could help!

BTW, I flashed bootloader > radio > boot > image > vendor > TWRP recovery, then go to recover, flash SuperSU then ElementalX.
[Nexus 6P Original Android Development] arunkr:
Hi, has anyone one u guys come across custom kernel with undervolting for N6p?
[Nexus 6P Original Android Development] flar2:
Undervolting is not likely to come to this device. The voltage is not as simple as it used to be, it is adaptive now, so not really just a single value. It gets adjusted according to how many cores are in use and stuff like that. The new chips are also very efficient, voltages are much lower than they used to be and there isn't a huge difference between frequency steps. I doubt it would make much difference in heat or battery life.
[Nexus 6P Original Android Development] c_86:
turn your wifi off if you are not using it or connected.... if its left on it is constantly looking for a signal, that will drain your battery...
[Nexus 6P Original Android Development] joho5:
I get the corrupt message when using this kernel...it doesnt cause any malfunctions, but it throws the red warning that my phone is corrupt and may not work properly.

is this normal? It goes away if I reflash the stock kernel.
[Nexus 6P Original Android Development] steveo17:
i have wifi scanning off

edit: i did not!

just found this!

https://www.reddit.com/r/Android/comments/3nrfa0/psa_wifi_scanning_reenabled_moved_locations_in_60/

they moved the WIFI Scanning available settings as well as Bluetooth

They are now located:

Location->Menu->Scanning
[Nexus 6P Original Android Development] c_86:
there you go, that should help somewhat...

I know bluetooth right now has a bug where it doesnt allow the phone to go to sleep when connected to something...

Im running CM13, and use a moto360, and during the day my phone never goes into sleep mode unless i turn off bluetooth, that could also be another issue

Download better battery stats and you should be able to track it down even further as to what the cause is
[Nexus 6P Original Android Development] steveo17:
yeah i have BBS and i have no wakelocks to report. everything is normal on that end. bluetooth is on but not connected
[Nexus 6P Original Android Development] c_86:
turn BT off when not in use as well... again, same thing, will be looking for something to connect to all the time and drain the battery...

one thing i always get into the habit of is turning all that stuff off when not in use...

I actually use a NFC chip and app to scan and it does it all for me...

examples:

leaving home, scan > turns wifi off, bluetooth on

get to work, scan > wifi on, vibrate on

leave work, scan > wifi off, normal sound mode on

get home, scan > wifi on, bluetooth off

doing this prevents me from having something on that doesnt need to be on when its not connected to anything or else battery drains
[Nexus 6P Original Android Development] just4747:
Just updated to 6.0.1 in Fastboot and flashed latest 1.00 kernel for 6.0.1 and it's fine but the double tap to wake is very hit or miss now. Most times, it does not work at all. I tried turning off all other gestures to sleep and same.
[Nexus 6P Original Android Development] steveo17:
experiencing this as well
[Nexus 6P Original Android Development] flar2:
It's normal

I know, this is why I recommend using sweep up 2 wake. I should remove double tap2 wake. Both stock and my version are not very good..

Cons of dt2w:

-unreliable

-interferes with phone calls

-easy to cause accidental wakes

Pros of sweep up to wake:

-100% reliable

-rarely, if ever, has an accidental wake

-does not interfere with phone calls
[Nexus 6P Original Android Development] just4747:
Aw :( so many ppl love dt2w and it was working great before. Is there any chance you can get it working more reliably somehow? I was happy with how well it was working before the updates.

Also it just failed 3 times to wake when swiping up for me :(
[Nexus 6P Original Android Development] tech_head:
My standard charger has issues. It just happened at the same time as me updating.
[Nexus 6P Original Android Development] nathanchance:
The nature of double tap makes it unreliable. The screen/digitizer has to recognize two taps on it in a row, which can be hard to do. Sweeping is an easier motion to detect because the finger never leaves the screen or interrupts the motion. I rarely if ever miss a sweep now, I made the switch about two months ago and I have never looked back. Once you get it right, you'll never miss.
[Nexus 6P Original Android Development] flar2:
Trust me, it never fails swiping up once you learn how to do it.

Double tap to wake is an impractical gesture, that's all there is to it. There's a reason Google ends up disabling it on their phones. I know people like it, but unless you can implement it jointly in firmware, kernel and android system, it never works that great. Manufacturers like LG have access to all that, I don't have access to the firmware and I don't want to modify the system (although you can enable pocket detection with my wake gestures app).

The main problem is the first tap is not always registered as a touch, it just wakes up the device from deep sleep. It also requires a wakelock to keep it awake long enough for the next tap to register, because it will try to suspend again right away otherwise. It's extremely difficult to protect against accidental wakes. And finally, it can be triggered by your cheek while the screen is off during phone calls.

Sweep2wake has none of those issues.
[Nexus 6P Original Android Development] chubby65:
Try nova launcher together with greenify

Works flawlessly
[Nexus 6P Original Android Development] steveo17:
Thanks! i thought that sweep2wake was waking my phone in my pocket, but it must have been dt2w. I was also wondering why it didnt work as well as my G2 but you answered that as well.

would you advise against having more than one sweep to wake option enabled?
[Nexus 6P Original Android Development] flar2:
Not necessarily, I just find that sweep up is easy and intuitive and the motion is not prone to accidental wake ups
[Nexus 6P Original Android Development] Mikulec:
Regarding the wake gestures, on Nexus 5 these gestures were sucking up the battery. Is this the same here on Nexus6P or not?
[Nexus 6P Original Android Development] flar2:
No, that issues is specific to the Nexus 5 and 5X. Battery is fine with wake gestures on all my other devices.
[Nexus 6P Original Android Development] littleprince86:
Hi guys. I have last release cataclysm

Can i to install now this kernel without flashing again ROM?

How i restore previous kernel after?
[Nexus 6P Original Android Development] NovaSlim:
Cataclysm Dec-08 is 6.0.1 based, you can use 1.00 without dirty flashing the ROM again.
[Nexus 6P Original Android Development] littleprince86:
Yes. And if i to install elementalx kernel without flash rom? It's don't work?

After , can i to return originale cataclysm's kernel?
[Nexus 6P Original Android Development] NovaSlim:
Yes, you can do just that by dirty flashing cataclysm

Check this post on instructions for using 1.00 on 6.0.1 based ROMs: http://xdaforums.com/showpost.php?p=64200850&postcount=1313

Not sure if Cataclysm is pre-rooted by you can ask the developer over there.
[Nexus 6P Original Android Development] flar2:
First backup your boot.img

I think Cataclysm is not rooted by default, so if you want root, flash SuperSU 2.62 (this is only if you want root!)

Then flash ElementalX

To return to stock, restore the boot.img. ElementalX does not modify your system partition
[Nexus 6P Original Android Development] littleprince86:
Cataclysm it's just rooted.

Then i don't have to flashing dirty ROM?
[Nexus 6P Original Android Development] flar2:
Nope, that's only if you flashed a different kernel like franco or lean.

Just flash ElementalX.

If you find the camera doesn't work, then go to recovery and wipe cache
[Nexus 6P Original Android Development] jesssiii:
Just to check, if I'm stock 6.0.1, encrypted and flash twrp then this kernel, then SuperSU, I will be unencrypted? Or would I need to format data for that?
[Nexus 6P Original Android Development] NovaSlim:
don't think you would as long you are using twrp 2.8.7.2 which support encryption, but check with the twrp thread
[Nexus 6P Original Android Development] flar2:
The kernel and SuperSU don't encrypt or decrypt. They preserve the current state. If you are encrypted you will remain encrypted, and if you are not encrypted, it will remain unencrypted.
[Nexus 6P Original Android Development] zgroten:
Would you please give me a screenshot of the lower part of that page, where it shows the toggle, cellinfosyate, dns check, etc? Want to make sure my settings are correct.

I have no WiFi calling and Hotspot doesn't work.

---------- Post added at 02:31 AM ---------- Previous post was at 02:02 AM ----------

Also, how do you get the setting to stick? I go back in and its not saved.

Strange thing is that when I disabled the radio from that screen, my hotpot connected. But it still doesn't transmit any data. Man my settings are bonkers
[Nexus 6P Original Android Development] Badger50:
Here ya go :)
[Nexus 6P Original Android Development] DMonster:
Mine is similar to this, except the preferred network type is LTE/GSM auto
[Nexus 6P Original Android Development] 360Razir:
(DELETE)
[Nexus 6P Original Android Development] zgroten:
You said you had changed it to LTE/GSM auto (prl), right?

How did you get the setting to stick?

also at the top, when you run the ping test, does it fail?

---------- Post added at 03:35 AM ---------- Previous post was at 03:29 AM ----------

This is interesting I wonder why. What carrier are you on?

If it's T-Mobile, then what's your APN settings?

What method did you use to get from 6.0, and what is your phones current state? Rooted?
[Nexus 6P Original Android Development] DMonster:
I ain't using t-mobile. I dirty flash and upgrade to 6.0.1 with all my data remained. And it's rooted with SuperSU 2.61 now.
[Nexus 6P Original Android Development] cassius_20:
Woops!
[Nexus 6P Original Android Development] Bwyan Benton:
Working normally here. Just checked.
[Nexus 6P Original Android Development] nathanchance:
Are you running aggressive doze with Greenify or Nap Time?
[Nexus 6P Original Android Development] cassius_20:
Noticed that I posted on wrong thread so retracted:) I do have greenify on aggressive and was thinking the same thing. Will disable and observe. Thx for chiming in!
[Nexus 6P Original Android Development] micmars:
Are these real apps about which you're asking, or some strange new benzodiazepine combo?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] jesssiii:
Is there a flashable stock boot image MMB29M?
[Nexus 6P Original Android Development] Bwyan Benton:
[MENTION=4684315]flar2[/MENTION]

Quick question, if I try to uninstall or freeze "Google app" & "Google now launcher" while running your kernel my phone won't boot back up upon restart. However, if I use Franco's kernel and do everything the exact same, it all works perfectly. Running newest version of cata rom, everything is all properly updated and such. Just don't understand why the kernel is making a difference here.
[Nexus 6P Original Android Development] flar2:
Reboot to recovery and wipe cache. I installed franco kernel yesterday and when I restored EX, my camera kept force closing. Wiping cache fixed it. Don't know why, but maybe it will help.
[Nexus 6P Original Android Development] franciscofranco:
That's weird. You on 6.0.1 right?
[Nexus 6P Original Android Development] Bwyan Benton:
That's so weird. I tried all that but still not playing nice. I just don't get this. It doesn't make sense to me.

*EDIT* OK weird. I just used root explorer and manually went to system/app and deleted the Google home folder then I went to system/priv-app and deleted the velvet folder. Then went into titanium backup and wiped data for Google app then uninstall then wiped data for Google now launcher then uninstall, rebooted, phone booted up, all that Google crap I never use is gone, and all working well.
[Nexus 6P Original Android Development] btort1:
Older versions never gave me any problems, but 1.00 kept giving me bug reports and killed my camera. And also for some reason my music started playing in the background for some reason with NO apps open. Took awhile to power off and music was playing, imaging if you were in a meeting and you couldn't turn it off :p Wonder if anyone ever came across this? I always installed everything the same way with enforcing on and wiped cache after install
[Nexus 6P Original Android Development] DeathmonkeyGTX:
Try a clean flash, I have experienced nothing of the sort on 1.0 or previous versions.
[Nexus 6P Original Android Development] xflowy:
guys im not sure if its a rom or a kernel (or a hardware) issue. im fresh on newest pure nexus + ex and when im streaming music with shuttle player via bluetooth to my sound blaster roar im getting a really weird behaviour: the music volume stepping seems really off, there seems to be only two steps: low and loud, e.g. when i start music on quite low and volume up via buttons the music gets freakin loud with one step, the next steps seem to make only a small difference loudness wise. there also seems to be no flawless continuous stepping and the slider always jumps a little a second time when i change the volume. i used other players: the same. luckily i have a second n6p around here at the moment running 6.0 chroma + ex and this one does not have the issue.

anyone? :l
[Nexus 6P Original Android Development] Shockz:
It's funny you mention this because I had this same issue and at the time I was just on pure nexus. I went back to stock and the problem seems to be gone. So it should not be kernel related

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

Are you on 6.0.1?
[Nexus 6P Original Android Development] flar2:
Of course.

As I've said a few times, a clean install is the way to go.
[Nexus 6P Original Android Development] slayp00n:
Guys i did a full clean install and my camera is fuggity, must be somehting in this kernel?
[Nexus 6P Original Android Development] flar2:
Reboot to recovery and wipe cache.
[Nexus 6P Original Android Development] slayp00n:
Did that, no good.

On fresh boot camera will open and work fine as long as i dont switch to front facing or video, if i try either of those it all goes to ****.

Also even if i kill the app i notice the laser sensor is still going.. only way to get it back is full reboot.

to be clear this is on 6.01, using version 1.

Never had these problems previous.
[Nexus 6P Original Android Development] sherlock5545:
It must be something on your end and not kernel related. All working fine here on Chroma 6.0.1 with Elemental X. And I dirty flashed from 6.0 too.
[Nexus 6P Original Android Development] slayp00n:
As I said this was a clean factory install of 601 and then elemental, so it could be that something in your dirty flash stuck around from 6....
[Nexus 6P Original Android Development] c_86:
did you update to the latest vendor image? make sure you update your vendor image, bootloader, and radio
[Nexus 6P Original Android Development] slayp00n:
Again i did a full factory install using flashall.bat.

---------- Post added at 04:20 PM ---------- Previous post was at 04:14 PM ----------

Logcat attached
[Nexus 6P Original Android Development] slayp00n:
sorry was too big to attach, logcat reattached
[Nexus 6P Original Android Development] steveo17:
[MENTION=4684315]flar2[/MENTION]

Any thoughts on implementing Franco's auto brightness settings? i've noticed that auto-brightness kinda sucks

https://github.com/flar2/angler/commit/ca68cae0b18dbf62d2a63eab05a62154e603fbff

Franco's comment regarding it

"Auto-brightness on stock never really worked well for me, always choosing very bright values. So either the sensor calibration is broken or the algorithm on the framebuffer Kernel driver is scaling pretty badly. After merging this patch it scales better and I can actually see the display brightness being set with more accuracy based on the lightning condition."
[Nexus 6P Original Android Development] aamitabh28:
Franco took this patch from flar2 afaik
[Nexus 6P Original Android Development] slayp00n:
12-11 10:18:42.439 444 3315 E mm-camera-intf: mm_camera_open:Failed with Connection timed out error, retrying after 20 milli-seconds
[Nexus 6P Original Android Development] jaythenut:
Noob question what is and how to use Backlight dimmer option thanks
[Nexus 6P Original Android Development] sherlock5545:
Reduces the brightness to values lower than the factory ones. You can use the EX Kernel Manager app. You may find the setting on other apps too like Kernel Adiutor but not sure.
[Nexus 6P Original Android Development] joho5:
So when flashing the images from google to get to 6.0.1, and then flashing twrp, and then flashing supersu 2.61, and then elementalx kernel...that means I have a root that hasnt modified system right?

Also to use ELementalx kernel manager, it needed busybox...doesnt busybox modify system?
[Nexus 6P Original Android Development] flar2:
Correct, system will not be modified at all.

I don't think you really need busybox for EXKM. But you can install it to /su/bin/ anyway

I have to look through the app's code and see if there is any command not included in the default toolbox. I think that warning is there because some old HTC ROMs had botched versions of the toolbox
[Nexus 6P Original Android Development] resynx:
Just wanted to drop by to say I'm still loving this kernel flar! :D
[Nexus 6P Original Android Development] flar2:
No problems here.

Everything camera related in the kernel is 100% stock. I never mess with it.

Yeah, stock brightness is terrible. Franco enables this by default, I leave it stock by default. You can enable it with EXKM, and I will add the option to the installer next release for those without the app.

It's on or off, see above. It allows the screen to go darker at minimum brightness, is slightly dimmer than stock at mid and low brightness levels, and smooths out the transition in the low-mid to low range, where before it was very jumpy.

the path to change it is something like /sys/module/mdss_fb/parameters/backlight_dimmer
[Nexus 6P Original Android Development] steveo17:
awesome thanks!

so i would just enable backlight dimmer and have it set on boot until its added to the aroma installer

also, what is the difference between enabling something via the aroma installer vs using the app and also if i select set on boot or not?
[Nexus 6P Original Android Development] flar2:
The aroma installer creates a config file (/data/data/elementalx.conf) and a script that applies your settings on boot.

The app allows you to change settings easily whenever you want, and has an apply on boot button to apply the chosen setting on boot.

Whatever you set to apply on boot in the app will take precedence, because the app settings are applied later in the boot process than the settings in /data/data/elementalx.conf
[Nexus 6P Original Android Development] jaythenut:
[MENTION=4684315]flar2[/MENTION] just got your app as a little thank you for the kernel:good:
[Nexus 6P Original Android Development] binaryfalcon:
Is there any throttling setting? Feels like the back of phone gets hot, quite worried. CPU temp varies between 35C (standby) - 41-45C (normal use)
[Nexus 6P Original Android Development] NovaSlim:
Temps normal, aluminum phones gets hot fast but cools off fast too because the high heat conductivity. Sock thermal throttling is good enough.
[Nexus 6P Original Android Development] zgroten:
I see that by default you have the CPU Governor set to interactive... Why not ElementalX? For us that aren't 100% confident in our mental grasp of governors.... What's the advantage of one over the other?
[Nexus 6P Original Android Development] krabman:
Do you need a recovery installed for your app to function? So far I've just been booting TWRP, I haven't installed it.
[Nexus 6P Original Android Development] flar2:
I haven't tuned it for this device yet

Yes, twrp is necessary to install from the app
[Nexus 6P Original Android Development] dastinger:
So glad you're here [MENTION=4684315]flar2[/MENTION]! Thank you a lot for your work.
[Nexus 6P Original Android Development] wewewi999:
Hi guys!

Just unlocked my bootloader, yet I'm a bit rusty and lost with the latest root methods.

In order to get both ElementalX and root, what do I flash, and in which order?

Is the ElementalX boot img in OP enough? (Meaning; would make no sense to flash Chainfire's boot img after that, right?)

I just flash your package then SuperSU?.. Solved!

Thank in advance for your time and consideration.
[Nexus 6P Original Android Development] raul4916:
For some reason can't change the max min freq. It is locked, did I miss something?
[Nexus 6P Original Android Development] prestige2:
Nice to see you here

Just quick question is the color calibration solve the pink/yellow hue on the screen ?
[Nexus 6P Original Android Development] wewewi999:
Just bought your app; great stuff. Beautiful.

Keep up the good work!

PSA: I really could use a doubleTap2sleep, why is it not in there? I could swear I've already saw this feature for the N5 on an earlier release..?

Here's hoping it's one of those upcoming features you're talking about. =D

Edit; found a workaround (and found out it wasnt dependant from the kernel anyway XD )

I'm not getting vibration feedback. (Not that would want to anyway)