yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] hinxnz:
No worries, it won't tell you exactly how to fix your issue but how to go about it. Basically check your partial wakelocks, alarms and network activity in BBS

Edit: Here's some example screenshots of my stats since last night, nothing out of the ordinary here and my battery life seems pretty good.
[Nexus 6P Original Android Development] snoprosledneck88:
Well my power manager service is more than yours and my phone is only been off the charger for 7 hours. I would really like to correct it. I have went through BBS and it does not allow me to change anything. I can't find that wakelock in amplify
[Nexus 6P Original Android Development] hinxnz:
Yeah bbs is just what the name says "better battery stats" and nothing else, you can use this app to identify your battery drain, wakelocks etc.

Partial wakelocks

display what is keeping your device awake while the screen is off.

Alarms

that trigger to often can cause wakelocks which are usually caused by apps syncing etc.

The kernel itself has no issue and it's a user side problem, probably play services, post a screenshot of your partial wakelocks and alarms.

Edit: Your screenshots below don't help, edit your post and replace screenshots with ones taken from bbs displaying partial wakelocks and alarms..
[Nexus 6P Original Android Development] Kappa Lamda:
I really cannot help you if you do not understand. Kernel wakelocks are not triggered by themselves. You keep posting about Power manager Service and posting screenshots of kernel wakelocks but not a single one for partial wakelocks and alarms!

I'll try explain one more time.

If you have a high percentage of Power Manager Service on kernel wakelocks, probably THIS IS NOT the cause of your drain. This kernel wakelock is triggerd either from a "partial wakelock" or an "alarm". So actually an app. You have to look on those two tabs to find out what's causing the drain.

PS: For the *backup* bug, if you do some search(try and search my posts overall) you'll find threads for this. Actually it runs all the time, never letting you phone to sleep and it is found under "partial wakelock" tab on BBS.
[Nexus 6P Original Android Development] snoprosledneck88:
Ok, sorry. I will try to post the correct screenshot later today as it's morning and my phone is not off the charger yet. My partial wake lock that was the highest was google photos. Com.android.google.apps.photos.photos. I believe that's how it was worded
[Nexus 6P Original Android Development] jiv101:
A noticeable yellow, anyone else see it maybe because it's a screen shot from my actual phone
[Nexus 6P Original Android Development] pokedroid:
Yeah, the pink by itself wasnt terribly worrying, but if it couldnt do lows or highs, I was going to start getting a tad nervous. Im glad it's software related. In all honesty, if my brightness is at 30-40%, the screen looks the same whether the video is playing as when my screen is off, so now that I've had time to mull it over, it really doesn't bother me that much either.

---------- Post added 13-11-2015 at 12:01 AM ---------- Previous post was 12-11-2015 at 11:54 PM ----------

I hate saying it my friend, but the screenshot looks grey the whole way through for me at Max brightness... Might be the panel in your phone :(
[Nexus 6P Original Android Development] bsg411:
Same here
[Nexus 6P Original Android Development] jiv101:
Ok sorry one more I took it with my other phone
[Nexus 6P Original Android Development] pokedroid:
Wow dude, that's definitely the panel.. I would return it then buy a new one or RMA it, but I've heard RMA process is a b*tch
[Nexus 6P Original Android Development] jiv101:
Ha just as long as I'm not crazy and seeing ****

My Rma is coming tomorrow
[Nexus 6P Original Android Development] jinx10000:
Love the Sound Control. Made my speakers and earphones surprisingly loud. Helped a lot with quiet Netflix videos.

Thank you. Bought your app.
[Nexus 6P Original Android Development] stackz07:
What are the wake gestures? I can't find them anywhere
[Nexus 6P Original Android Development] zgroten:
What is the "fauxsound" support?
[Nexus 6P Original Android Development] jaidev.s:
Sorry for this stupid question, which all roms does this kernel support? There are lots of roms in the Development section. Does this kernel support ASOP ROMS?
[Nexus 6P Original Android Development] AhsanU:
Sorry if this seems like a silly question but I'd like to flash this kernel to gain some of the functions it provides.

I've flashed this kernel as well: http://xdaforums.com/showthread.php?t=3235013

That kernel was flashed so verity checks could be bypassed and I could gain access to files in the phone through twrp. It is my understanding that that kernel is stock except for the bypass. There are multiple warnings not to flash the kernel in this thread on top of another custom kernel (only stock kernel is allowed). The only difference in the kernel I'm using is bypassing the verity checks, so is it safe to flash the kernel in this thread? I wouldn't want to risk anything, so I thought I may as well ask.

Thanks!
[Nexus 6P Original Android Development] stackz07:
I am an idiot, sorry. It was late and I should have just googled my question. I did after a cup of coffee this morning :)

Will it be to hard to have program based gestures? Like circle on screen when it's off boots camera, v turns on a flashlight etc? Similar to Oxygen OS? I am assuming they can do this because they ship their phones with their rom and kernal so they can be integrated where a standalone kernal would need separate integration for each rom?
[Nexus 6P Original Android Development] WACOMalt:
ExFat support doesn't seem to be working for me. After installing I plugged in an ExFat flash drive via otg. Only option was to reformat it.
[Nexus 6P Original Android Development] geoff5093:
Just in TWRP
[Nexus 6P Original Android Development] micmars:
It's also odd how, when looking at the thumbnail, it's deep black, once the video plays, it ups yup gray...I wonder what those with the pinkish hue screen see...

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

---------- Post added at 07:11 AM ---------- Previous post was at 07:05 AM ----------

I think any rom...definitely with the two AOSP roms on the development forums, as well as stock roms.

Just flash as indicated in the OP.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] mjgr33n:
I have noticed that with the addition of the faux sound support that although my headphones work with music, if I get a phone call the sound refuses to come out of the headphones, only the speakers, I have seen this issue many years ago when I last used a phone with faux sound support, if there is no possible fix for this, would it be possible to add an option in Aroma installer to not install it?
[Nexus 6P Original Android Development] flar2:
They allow you to turn on the screen by swiping or double tapping

It supports all of them. Some of them will require the enforcing option to be turned off on the last page of the installer.

You need the boot.img that came with your rom. That means the boot.img from the factory images that Google provides if you are on stock. Or, if you are in a custom ROM, simply flash the rom without wiping anything.

Exfat probably works if you use an app like stickmount.

I provide the kernel support, but the rest of Android does not support it. Long story, but it's a proprietary file system from Microsoft and Google would have to pay Microsoft to use it.
[Nexus 6P Original Android Development] NovaSlim:
Sleeps like a baby, Naptime!

Just to further illustrate how Greenify is unecessary with Doze. My deep sleep time with EX-0.06 + Naptime(Aggressive Doze+60 sec idle time)
[Nexus 6P Original Android Development] Kookitza:
Which idle time you selected?

:confused:
[Nexus 6P Original Android Development] NovaSlim:
The first one. Mine would have sleeped even better if Fi didn't automatically turn "always scanning for Open Wifi" on.
[Nexus 6P Original Android Development] Kappa Lamda:
OK post these screenshots and we can find the cause. Google photos keep running on the background is a known bug and many have it though. You could try setting backup only when on wifi and only while charging to see if it fixes the problem.
[Nexus 6P Original Android Development] snoprosledneck88:
I already had it set to backup only while on wifi and charging. I uninstalled all of the updates and let the phone run for an hour or so and it didn't show up. I know an hour isn't very long but it would act up within minutes before. I have reinstalled the updates for photos and I will report back if it is still acting up. Thanks for your help sorry for causing the frustration.

EDIT: So after i typed this i checked BBS because i had reinstalled the updates for photos. Go figure in a mere half hour photos was right up there eating battery. I uninstalled the updates and photos went off the list. I uninstalled it and it just flat disappeared from the list! Now photos is not uninstalled completely, just the updates. The app is still on the phone. It must be something to do with one of the latest updates thats causing it to act this way. Anymore help is appreciated. Thanks again guys
[Nexus 6P Original Android Development] therock3181:
If google photo keeps your phone awake revert back to 1.22. I have done that and the wakelock are gone. Use apkmirror. There is a thread on this since yesterday.
[Nexus 6P Original Android Development] MarcoPolo78:
Anyone else having trouble with this otg_default wakelock ? If so how can I take care of it ?
[Nexus 6P Original Android Development] snoprosledneck88:
I figured that was the case from my previous findings. I did downgrade and haven't had the problem so far
[Nexus 6P Original Android Development] jfive74:
Hey, i noticed that sound tab the optionto adjust volume of each speaker separately is gone, now 1 channel instead of left and right and that elementalx tabis gone in ex kernel manager app ver 2.7. Can someone confirm? Is it kernel or app?
[Nexus 6P Original Android Development] Toutatis_:
I believe it is due to a recent kernel change as to the sound drivers, not sure though.
[Nexus 6P Original Android Development] Jockson:
This is the first custom kernel I've installed on my 6P. Loving it so far with one major annoyance. When the phone is in deep sleep, very often after turning on the screen I have to swipe a few times before it registers the touch and unlocks the phone. I'm using double tap to wake but I'm going to try waking the device with power button as well. For some reason it seems the phone freezes for a few seconds after waking up. It seems to only happen when the phone has been off for 10+ mins or so. If I keep turning it on and off, I can't reproduce it. I'm on stock rooted rom. Any idea why is this happening?
[Nexus 6P Original Android Development] therock3181:
Running latest kernel and EXKM. Both sliders are present.

And Elementalx present.
[Nexus 6P Original Android Development] steviemch:
DT2W is notoriously flaky, use sweep to wake instead, never had any problems using it.

Nexus 6P
[Nexus 6P Original Android Development] Maxamillion:
There's so many CPU temperature sensors in the Nexus 6p, which one should I be using as the main CPU temperature sensor? Some sensors report higher temperatures than others, so I'm not sure which to trust
[Nexus 6P Original Android Development] hinxnz:
Well I just installed latest Google Photos and the persistent partial wakelock showed up for me too.

I just disable AutoSignInAndSyncBroadcastReciever to prevent the wakelock, I think it better than disabling the service for now.

Enter code into terminal emulator to disable broadcast:

su -n pm disable com.google.android.apps.photos/com.google.apps.photos.onboarding.autosignin.AutoSignInAndSyncBroadcastReceiver

To enable again:

su -n pm enable com.google.android.apps.photos/com.google.apps.photos.onboarding.autosignin.AutoSignInAndSyncBroadcastReceiver

To disable service:

su -n pm disable com.google.android.apps.photos/com.google.apps.photos.onboarding.autosignin.AutoSignInAndSyncJobService

To enable again:

su -n pm enable com.google.android.apps.photos/com.google.apps.photos.onboarding.autosignin.AutoSignInAndSyncJobService

Edit: After disabling the broadcast, the wakelock disappeared for awhile, then after writing this post it came back but only for roughly 10mins. I don't have many photos/videos on my phone, so maybe it just indexing files to Drive or something. I'm not going to disable the service for now because it doesn't seem to be persistent at the moment..
[Nexus 6P Original Android Development] jfive74:
running stock rom?

---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------

Running stock rom? It changed for me with June update to rom.
[Nexus 6P Original Android Development] therock3181:
Yes stock Rom. Although I just rooted.
[Nexus 6P Original Android Development] jfive74:
Very interesting. Cause i dont have that. flash kernel many time and settings still dont come back. Im running stock with this kernel, xposed and that's it. Wonder if it has to do with viper4android sound mod? Is there anyone else who can confirm below? Thanks.

Quote:

Originally Posted by jfive74

Hey, i noticed that sound tab the optionto adjust volume of each speaker separately is gone, now 1 channel instead of left and right and that elementalx tabis gone in ex kernel manager app ver 2.7. Can someone confirm? Is it kernel or app?
[Nexus 6P Original Android Development] therock3181:
I don't have Viper installed. That could be it!
[Nexus 6P Original Android Development] JRJ442:
I'm running Viper on the newest Pure Nexus build and I have individual sliders for left and right gain control in EXKM.
[Nexus 6P Original Android Development] therock3181:
He's running stock.

Maybe flashing the old boot.img containing the stock kernel and flash elementalx after could possibly do it.
[Nexus 6P Original Android Development] snoprosledneck88:
I didn't have to disable the service entirely, just got back to 1.22
[Nexus 6P Original Android Development] matesc:
The name of the thread should be updated, [MENTION=4684315]flar2[/MENTION] - or is the DP4 version beta?
[Nexus 6P Original Android Development] xflowy:
[MENTION=4684315]flar2[/MENTION] after updating the high brightness widget i cant toggle it on and off any more. it stays on auto now. double click changes nothing either. is this intended, as u state in the info of the widget, that we can either single or double click?
[Nexus 6P Original Android Development] jfive74:
Are you guys rooted using systemless root or other?
[Nexus 6P Original Android Development] flar2:
Nova Launcher?, If so, turn off the double tap lock screen setting.
[Nexus 6P Original Android Development] jfive74:
[MENTION=4684315]flar2[/MENTION]

---------- Post added at 12:31 PM ---------- Previous post was at 12:05 PM ----------

Reflashing to stock, rooting then flashing kernel solved the issue. Will load viper4android and see what happen. Thanks.
[Nexus 6P Original Android Development] xringo:
I want to run darkspicer 7.5. Does anyone know which settings I turn off in the cpu settings page? And what the numbers should look like?
[Nexus 6P Original Android Development] Jockson:
Ah OK. I've flashed franco kernel and DT2W works perfectly so it's definitely down to ElementalX. Though I find ElementalX smoother and would really like to contine using it. I'm going to try sweep to wake. Thanks.
[Nexus 6P Original Android Development] steviemch:
I used DT2W exclusively on my N4 but found when I switched to S2W with this kernel, it was far more stable and intuitive. You shouldn't have any problems with it.

Nexus 6P

---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------

Disable Touchboost and check your settings match the ones in my screenshots.

Nexus 6P
[Nexus 6P Original Android Development] tech_head:
I'm running systemless root and systemless Xposed, thermal-engine.conf tweaked.

I'm not seeing any issues.
[Nexus 6P Original Android Development] Jockson:
I've now realized the touch freezing upon screen waking up is not directly related to DT2W. Even when using ambient display to turn on the screen, touchscreen still freezes for some time before responding. So I pick up the phone, display turns on, I swipe to unlock and - nothing happens. Takes a few swipes for it to register. Happens almost always when the phone has been off for a few minutes. I can't be the only one with this issue? Where can I download older versions of this kernel?
[Nexus 6P Original Android Development] hinxnz:
Try lowering swappiness, you can do this in ex app or terminal etc, if you got zram enabled that is. I noticed that sometimes with waking up screen to xda app can cause lag
[Nexus 6P Original Android Development] flar2:
Dt2w is the same in elementalx and franco.

Make sure you reflashed the stock kernel before flashing ex. You shouldn't flash ex over franco.

Other than that, ive never had lag or delay on wakeup, so don't know what's causing that.
[Nexus 6P Original Android Development] igalmarino:
Are you using naptime or a similar tool ?
[Nexus 6P Original Android Development] SyCoREAPER:
[MENTION=4684315]flar2[/MENTION]

Is this a bug or a preference on how to toggle?

Example:

Under Graphics

Backlight dimmer if I click on the text it switches between enabled and disabled but the icon on the right remains static and is it's own toggle
[Nexus 6P Original Android Development] Ophidian_DarkCore:
Is there a specific reason to stay on 3.10.73?
[Nexus 6P Original Android Development] flar2:
The icon on the right is apply on boot
[Nexus 6P Original Android Development] flar2:
Stability and simplicity. Linux updates are 99% for drivers that have nothing to do with phones or Android.
[Nexus 6P Original Android Development] kyzn:
I've been using this kernel for a week and I love the battery life it gives me. Tested today with heavier use than my daily routine. Listened to 3 hours worth of podcasts, streamed Spotify, played a couple of games, downloaded several apps, emails, social, forums all on the phone. Results aren't too shabby. :victory:
[Nexus 6P Original Android Development] shafubhai:
What are your settings?
[Nexus 6P Original Android Development] kyzn:
Pure Nexus rom. ElementalX DarkSpiceR7.5 profile with tweaks.
[Nexus 6P Original Android Development] knlgSeeker:
I have it on DP4.. EX 3.03 rooted. Excellent kernel, S2Wake & S2Sleep are 2 reasons why I'll always flash this over the stock kernel [emoji106] [emoji481]
[Nexus 6P Original Android Development] Zyphur:
Off topic question for those of you on DP4. What do you use for expanded power menu (reboot options added instead of just power off)?
[Nexus 6P Original Android Development] blitzerking1:
If I need to easily reboot or reboot recovery I just use the scripter in ROM toolbox pro.
[Nexus 6P Original Android Development] Ophidian_DarkCore:
i was just interested in some net updates hoping it would fix gcc 4.9 compilation with linaro.
[Nexus 6P Original Android Development] steviemch:
Quick Reboot from the Play Store.

Nexus 6P
[Nexus 6P Original Android Development] Jockson:
I just got my 6P a week ago and EX was the first custom kernel I've ever flashed on it. Immediately noticed this issue, flashed stock kernel, then franco and dt2w worked perfectly. Like every single time. Flashed stock boot.img again, then flashed EX and I'm still having this issue. Like I said in another post, it doesn't seem to be related directly to dt2w, ambient display does the same thing. I pick up the phone, screen turns on, I try to swipe and nothing happens. Needs a few swipes for the touch to register. For some reason the touchscreen is unresponsive for a few seconds after waking up. And only when the phone has been off for 5+ mins or so. I thought it was a hardware issue but on stock and franco, it works 100% perfect. Though I don't like franco because of choppy scrolling and EX has everything else I want :(

Nope, nothing of the sort.
[Nexus 6P Original Android Development] Toutatis_:
No issue at all here on rooted stock ROM + EX 1.18...

D2TW and Ambient Display work perfectly.
[Nexus 6P Original Android Development] Jockson:
Interesting. I wonder if doing a factory reset would help although it's weird that stock and other kernels work without issue like it is.

Is it safe to flash older version of EX over 1.18?
[Nexus 6P Original Android Development] Toutatis_:
I've been using franco kernel for a long time (I'm constantly switching between franco, Kylo, EX, AK...) and D2TW / Ambient Display have always worked flawlessly on all these kernels as far as I'm concerned.

That's weird, indeed. Are you on stock ROM? are D2TW and Ambient Display laggy and screen unresponsive right after a clean flash without any additional apps installed or tweaks?

If it's worth the hassle to you, try to fully go back to stock (I would also wipe internal storage if I were you, just to make sure there's no old imprint of previous kernel/ROM flash that may cause issues) and see what happens.

I don't know. I guess it's okay to do since the opposite process is possible: we can flash newest versions over the current one installed on our device. But I'm really not sure about that, wait for someone else's answer!

Are you asking this because you didn't have this issue on earlier versions?
[Nexus 6P Original Android Development] mtnlion:
Simplereboot from the play store.
[Nexus 6P Original Android Development] Jockson:
Yeah, stock ROM. The first kernel I ever flashed on this phone was EX 1.18 right after I rooted my phone. No additional tweaks whatsoever and I immediately encountered this issue. I wonder if it is some kind of conflict between DT2W and S2W. If both are enabled things get really unpredictable and unreliable.

Another thing. When the screen doesn't registed the first swipe, if I keep swiping around the screen without lifting my finger, it won't register for as long as I lift off the finger and swipe again.

Nah, I'm asking because I was hoping an earlier version wouldn't have this issue for whatever reason :)
[Nexus 6P Original Android Development] Toutatis_:
I've just tried to enable all S2W gestures (up, down, right and left) along with D2TW: no issue either! all gestures are well recognized and the screen turns on almost instantly after any of them.

What happens on your side if you only enable D2TW and disable S2W?

That's the expected behaviour I believe. Same here: if I do a very little swipe gesture (which is obviously not recognised), moving my finger in all directions possible won't make the screen turn on (although sweep up, down, left and right are enabled).

Oh, ok. I don't think any changes were made to wake gestures for quite a long time, but once again I'm not 100% positive about that.
[Nexus 6P Original Android Development] Jockson:
Then I only get this touchscreen freeze thing. If I enable both, DT2W doesn't work properly and very often doesn't work at all. What I've found is, when only S2W is enabled, then there is NO touch freezing! SOMETIMES it won't recognize the first swipe and the screen won't come on, BUT whenever it does, the touch never freezes and I can unlock the phone immediately. The only problem is that S2W always gets activated in my pocket so the phone starts calling people by itself. I've tried installing wake gestures app to turn on pocket detection but then S2W itself isnt reliable anymore. And all I wanted was simple DT2W lol.

Sorry, I meant AFTER the screen wakes up. So I do a regular swipe after that, it doesn't register, and will continue ignoring it until I lift the finger off and do another swipe, then it does register. S2W working fine by itself leads me to believe it's some kind of conflict between it and DT2W but then again, I have no idea how it works and also it appears to work fine for others so, who knows.