yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Damon13:
Maybe in a few days I am going to try performance and option 3 and see the effects in battery life.

this is my setting a few days ago,

1. default 300 min, default max

2. all disable

3. Sensor_ind disabled, smb135x enabled, msm_hsic_host disable, and wlan_rx_wake set to 1,000

4. Charging LED ON

5. Savoca's app configures/wrinklefree values

6. Savoca's app configures/wrinkefree values

7. 100 (default)

8. Powesaving

9. Faux Sound Yes

10. Permissive
[Nexus 6  Original Android Development] rauschkugl:
The better idle drain is really great but I think I have a problem since 1.16.

Sometimes when listening to music over bluetooth in my car, poweramp just gets closed after one track and music stops. Could it be related? This never happened before but also doesn't happen all the time now.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] LordDeath:
Sometimes when installing new apps or right after a reboot my device feels very slow and it lags heavily. During this state System Monitor shows me a full load on 3 cores which are stuck on 1.5 - 1.6 GHz while the 4th core stays offline.

Only when the CPU load decreases after a few minutes the cores start to act normally and all 4 cores start to work with full clock rate depending on the load.

Did some one else notice this, too?
[Nexus 6  Original Android Development] Franzie3:
Any reason why you have smb135x enabled? I disable it and basically have the same settings as you but i have average-slightly above average battery. I started using Tinfoil/FB Lite to help on battery (FWIW FB Lite is laggy as hell, kinda sticking with tinfoil) I changed the wLan_Rx_wake setting to 4 from 8 and obviously the wakelock increases substantially. Maybe im missing something.

Another thing i noticed in BBS is that under Alarms com.google.android.gms is always top of the list. I need to look into what that might be
[Nexus 6  Original Android Development] nobnut:
Updated to Google Play Services 7.0.8.6 by any chance?

http://xdaforums.com/showpost.php?p=59214003&postcount=5398
[Nexus 6  Original Android Development] Franzie3:
nope, still on an older version, i checked that
[Nexus 6  Original Android Development] wrongway213:
Yeah, I leave it alone because I'm a battery stat hunter and I've yet to see it for more than seconds at a time while I am charging - I just see no reason to block a wake lock that appears to be behaving as intended on my device.
[Nexus 6  Original Android Development] akellar:
GMS is the push notification system. Non-issue. Alarms are rarely the cause of any battery drain issues.
[Nexus 6  Original Android Development] old_fart:
I am running the meanpop and the leanlernel 1.16 . Have been doing so for a week. When I go to set option one in lk , it'll say :

/sbin/lk461]: can't create /data/data/leankernel/minfreq: No such file or directory. And then also 'Permission Denied' also ? ? ? . . .

Question : would there be something I am not doing right -or- something I can do at my level to fix ? . . . Would possibly the rom maker, [MENTION=2712518]mikeyxda[/MENTION] need to do differently ? ? ? . . . I don't think it's Mike cause lk is loaded afterwards . . .
[Nexus 6  Original Android Development] rignfool:
The only time I lose the 4th core is in a low battery situation...
[Nexus 6  Original Android Development] LordDeath:
I think it was just because of the heat.

I was charging the phone with Motorola's fast charger, a new CM12 nightly caused a rebuild of the dalvik art cache and as a result even the display was much warmer than usual.
[Nexus 6  Original Android Development] Franzie3:
Hey guys - WakeLock detector is showing me on my CPU that 1013 has fired off x2022 in 14m9s. Looking at it it says the type is System(audio). never seen this before. Any ideas?
[Nexus 6  Original Android Development] akellar:
Lock sounds, system touch sounds, etc would be my guess.
[Nexus 6  Original Android Development] Franzie3:
Lock Sounds was the only one i had enabled and i stopped it (turned it off). Going to see if that helps
[Nexus 6  Original Android Development] Mervingio:
[emoji15]
[Nexus 6  Original Android Development] wrongway213:
Do you have the wakelock tuned to a divisor in lkconfig? If not, enter lkconfig, wakelock control, and try setting msm_hsic_host to "4" (middle of the road) - should see a lot less drain from msm_hsic_host that way.
[Nexus 6  Original Android Development] tysonwald:
deleted

---------- Post added at 06:59 AM ---------- Previous post was at 06:57 AM ----------

do you have an alarm set? It took me forever to figure this one out, turned off my alarm and it went away
[Nexus 6  Original Android Development] Franzie3:
I do, I use Timely, but i didnt think it would be that high.
[Nexus 6  Original Android Development] Smallsmx3:
Anyone using LK on CM? Any issues other than theme compatibility?
[Nexus 6  Original Android Development] epicnoob66:
I found it in a sprint thread in nexus 6 general forums.
[Nexus 6  Original Android Development] Circaflex:
Tonight or tomorrow a thread will be up pm me about tether maybe I can help but don't want to clog up ops thread
[Nexus 6  Original Android Development] clothednblack:
Cleaned up, my apologies to the op for clutter. Please see following post for info.

Thanks you.
[Nexus 6  Original Android Development] Steve Lazarus:
Let's talk Slim ROM until the thread is up here - >

http://xdaforums.com/showthread.php?p=57138406

Sent from my Slim Nexus 6
[Nexus 6  Original Android Development] EniGmA1987:
I am getting a lot of lag in various games, but not all of them. Usually it is in games that are not very intensive. My theory is that the ramp threshold may need to be adjusted a bit, so that games that do not put a heavy load on this powerful chipset will still ramp up high enough to maintain smoothness. One of the reasons I think this is that the games that stutter have not only never stuttered at all before on other phones I have owned in the past but the SoC in this phone is barely even getting the the point where I would call it even "warm". Would the GPU be something you could look into in a future version of the kernel?
[Nexus 6  Original Android Development] Xileforce:
The general consensus is that the majority of apps are not optimized for lollipop and art yet. But it could be what you said too.
[Nexus 6  Original Android Development] lightsout:
I know it was brought up somewhere. Can I disable double tap to wake? I don't see it in trickster yet. Anyone have a terminal command (total noob with terminal).
[Nexus 6  Original Android Development] Circaflex:
You sure its not your ROM that has that feature? I don't see dt2w listed on the changelog
[Nexus 6  Original Android Development] lightsout:
Well maybe it is, I never tried it until I flashed this kernel so just assumed thats what it was. Isn't it a kernel feature though? I don't see it referred to here either, think I mixed that up with elemental. Thanks
[Nexus 6  Original Android Development] Circaflex:
I think it can be either for instance slim has built in dt2s on statusbar
[Nexus 6  Original Android Development] lightsout:
I believe when its in the OS it can be ROM related. But I believe with the screen off its a kernel thing. I may be wrong though. I guess I will reflash the ROM and find out.
[Nexus 6  Original Android Development] stuff:
My phone seems to lock at 1.7ghz max frequency. Not sure what's happening.
[Nexus 6  Original Android Development] Circaflex:
Disable mpdecision via trickster or terminal
[Nexus 6  Original Android Development] TwelfthMan:
I can't get the min freq any lower than 1.7 mpdecision is set to off. Every time I hit apply in trickster it jumps back to 1.7
[Nexus 6  Original Android Development] simms22:
dont look at trickster, use perfmon or something similar to see your cpu speed. if that is what youre doing, then ignore me :)
[Nexus 6  Original Android Development] TwelfthMan:
OK, purchased perfmon to help out with this. When I hit the CPU widget I see the cores bounce around a lot. As low as 223 and I've only hit as high as 2265.

Edit: watching the CPU monitor for awhile I believe it is working now. 223/2880 antutu I rank in at 51.
[Nexus 6  Original Android Development] Blaze420916:
I can't run a benchmark it fc's
[Nexus 6  Original Android Development] bullhonkie:
Just curious, which games are you experiencing issues with? I'm having some framerate drops in games as well but I feel like it's because of the GPU not being able to keep up with driving so many pixels. The same games on a Moto X 2014 running lollipop don't have framerate stutters and that phone has about half the amount of pixels to drive.
[Nexus 6  Original Android Development] Xileforce:
Its not the screen. Run antutu benchmark. You will see that the 3d part of the rest actually runs faster than it does on a snapdragon 800 pushing to a 1080p display. I've run the tests on both my note 3 and my nexus and the nexus vastly outperforms it in the GPU section despite pushing more pixels. The adreno 420 is a beast.
[Nexus 6  Original Android Development] drawde40599:
Sounds like you may have been heat throttling .
[Nexus 6  Original Android Development] wrongway213:
Themes are fully compatible too (unless offical CM nightly has changed without me hearing of it) - temasek's CM for instance has no compatibility issues with anything at all and uses leanKernel as its stock kernel. Have yet to hear of any CM having compatibility issues with leanKernel.
[Nexus 6  Original Android Development] akellar:
You're right, no issues. They are working on adding in KCAL changes and an automatic night/day brightness mode. Will be interested to see if [MENTION=3357040]Imoseyon[/MENTION] will be able to make it compatible with that without breaking the current color options.
[Nexus 6  Original Android Development] Kal-El7:
I have Lean Kernel 1.13 - or, a variant of that version with "permissive" set to allow Xposed usage after hard reboots. Do all subsequent Lean Kernel versions have permissive set to enabled by default? Thanks.
[Nexus 6  Original Android Development] old_fart:
nope, enforcing... but its a easy toggle in lkconfig !
[Nexus 6  Original Android Development] mugendon:
Any update on this? My first thought was that you can customize the kernel like you did for viper, but then I remembered this quote from you. Do you still think it would be a nightmare or are there any new workarounds that could make running xposed on an enforcing kernel easier? Or is there something that rovo has to do for making it easier?

Edit:

I have absolutely no clue what I am talking about, but could this help:

Atleast you didn't use this for the viper commit, so it might be something new.
[Nexus 6  Original Android Development] old_fart:
I truly am like you in that I am clueless for the most part.

But my thoughts run like this . . .

A domain ( website ) is a different animal that an local app twiddling with the memory system bits . . .

hth.
[Nexus 6  Original Android Development] supercluver:
Is that permanent then (ie it stays permissive through any and all reboots)?
[Nexus 6  Original Android Development] mugendon:
But a domain is a more general term and not only used for websites ;) So this makes me still hoping it can be used for something like "everything related to package.of.xposed.*" or something like that.

[MENTION=265835]supercluver[/MENTION]

Yap, it's permanent.
[Nexus 6  Original Android Development] akellar:
Not sure how much effort should go into making it work until xposed is out of beta anyway. Rovo is already working with other developers (chainfire for example) to see if xposed can work without a permissive selinux environment.
[Nexus 6  Original Android Development] mugendon:
That are great news, didn't know he is already working on it. Thought the whole Samsung issue is eating up his time ;)
[Nexus 6  Original Android Development] Imoseyon:
As long as they use [MENTION=4316709]savoca[/MENTION]'s implementation I shouldn't have to make any changes in my kernel/ramdisk.

Yeah I agree this is the best course of action for now.
[Nexus 6  Original Android Development] akellar:
Here's the commits if you want to see what they are working on. I'm too dumb to know if it'll play nice or not ;)

http://review.cyanogenmod.org/89163

http://review.cyanogenmod.org/89164
[Nexus 6  Original Android Development] savoca:
My post regarding LiveDisplay here: http://xdaforums.com/showpost.php?p=59227182&postcount=11545

Using both CF.lumen's KCAL driver and LiveDisplay at the same time will conflict, as they're both writing to the same registers. Just pick an app and call it a day, no issues there.

KCAL is still the only driver with kernel-level Saturation/Contrast support, so nothing can mess with those.... yet. :mad:
[Nexus 6  Original Android Development] Imoseyon:
I haven't seen CM's LiveDisplay kernel implementation so I could be off-base here. But based on your description, there can be a rather simple workaround to support both. If the kernel sees an RGB value of say 4480 (35*128) or higher, just divide the value by 128.

In fact, once a CM nightly is ready with the implementation, all I need is a tester to crank out a leanKernel mod for this (support both LiveDisplay and KCAL) in 10-15min.
[Nexus 6  Original Android Development] akellar:
It was merged this afternoon, just an FYI
[Nexus 6  Original Android Development] savoca:
KCAL and LiveDisplay also have different sysfs paths. If someone added KCAL support to LiveDisplay's ROM-side driver so that we wouldn't need two kernel-level PCC drivers doing the same thing, that would be perfect and you wouldn't even need LiveDisplay's Linux changes.
[Nexus 6  Original Android Development] Imoseyon:
Different sysfs paths? Damn... I'm not sure if we can get CM to use the KCAL sysfs paths, although I know dhacker29 so I'll see if I can ping/persuade him.

Workaround for different paths in kernel is still possible, although it's a bit uglier. I may go that route anyway - i've done this exact workaround before on gnex. ;)
[Nexus 6  Original Android Development] franciscofranco:
I'll be with Kondik on Monday, I'll talk to him about this to see if he can add a knob on their userspace implementation to detect if we're using savoca's code or their Kernel implementation (sysfs paths etc, since I can imagine code should be practically the same).
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=4316709]savoca[/MENTION] and [MENTION=3292224]franciscofranco[/MENTION], looks like dhacker is taking care of it (at least for shamu):

https://twitter.com/dhacker29/status/573639926060879873
[Nexus 6  Original Android Development] franciscofranco:
Very gud.
[Nexus 6  Original Android Development] savoca:
dope!
[Nexus 6  Original Android Development] old_fart:
Is it true that the new / updated google service :

3-4-2015

-Google Play Services 7.0.86 (1763202-438)

3-5-2015

-Google Play services 7.0.87 (1766486-438)

-----------------------------------------------------

fixes a long standing bug that you're mitigating in lkconfig, option 3 ? ? ?

or was I reading and falling for some happy horse $hit ?
[Nexus 6  Original Android Development] akellar:
The new one fixes the wakelock that the older one caused. Not related to the wakelock fixes in the kernel.
[Nexus 6  Original Android Development] wrongway213:
Discard
[Nexus 6  Original Android Development] nobnut:
Don't say that. It just isn't true.

If you bother to check, your device won't go into deep sleep with either installed.

I wish people would stop copy/pasting any old junk on XDA.

Why don't they just rename it xda-downloaders.com.
[Nexus 6  Original Android Development] akellar:
Someone needs a Snickers
[Nexus 6  Original Android Development] wrongway213:
Not sarcasm, genuine question - why am I able to deep sleep on 0.7.87 then? I am on 0.7.87 and have absolutely no deep sleep issues whatsoever. I even tested it on a ROM that keeps SystemUpdateService on by default (Dirty Unicorns) and one that keeps it off by default (Temasek's CM12), neither had any sleep issues on Banks 3-05-15 gapps which are 0.7.87. Since everyone is saying it's something to do with SystemUpdateService I figured either having it enabled or disabled would induce the wakelock.. neither did. I have seen reports of people having problems on 0.7.87, but so far it seems to me that people with issues installed the apk instead of waiting for a proper gapps update. Am I just lucky, something else at play, is the issue gapps vs. apk, or does this entire post make as little sense to you as it does me when compared to the rest of what is being said? On clean flashes on both ROMs FWIW.
[Nexus 6  Original Android Development] pispuso:
Hmm I waited for proper Banks Gapps, have last Lean Kernel installed and still having SystemUpdateService wakelocks. My phone won't go to sleep no matter what. I even disabled it with disable service and for some reason it still wakes up the phone :|
[Nexus 6  Original Android Development] old_fart:
Is the same for me and I wiped it all.

I went into "MyAndroidTools Pro" and chose services, and within system chose google play services ( holy crap this is a Looong list ! ) and system update services was red ( disabled ) but it is/was definitely stuck "on" . . . So, since it thinks its "on", I turned it "on" now . . . . So, now what will happen.

.

I apologize [MENTION=3357040]Imoseyon[/MENTION] for dirty'ing up your thread.
[Nexus 6  Original Android Development] pispuso:
Yeah, I realized that as well and "Enabled" it since it was Disabled as default. For now it seems that does the trick since now my phone goes into Deep Sleep and no wakelock for now, but we have to do this every time we reboot sadly. Damn Google and it's stupid updates giving wakelocks every time...
[Nexus 6  Original Android Development] wrongway213:
Just download Disable Services and enable it, it should persist through reboots that way.
[Nexus 6  Original Android Development] pispuso:
For some reason, it does not persist. :C
[Nexus 6  Original Android Development] wrongway213:
I wish I could figure out what is causing the issue. I just checked and I am on 7.0.87, 91% deep sleep and I've actually used my device for about a half hour SOT and about another 10 minutes awake, mostly from when I synced Google accounts (all of them) in the last 7 hours.. 1.3% deep sleep even after syncing.. I am really curious if there are other people on 7.0.87 who are having no issues at all.. haven't heard from anyone other than to say they haven't updated or they've had problems.. I'm curious just how prevalent this issue is, because I am not affected by it.
[Nexus 6  Original Android Development] Damon13:
Hey wronqway here is a quote from a guy named coldgin_

Had the same problem after update with 7.0.87-034. Solved with force stop & clean all data and cache in framework and google play (both of them!!), and after that made a cold reboot.

Do all of this in "plane mode" so you avoid any data sync in the middle of the process.

Then, go back to "normal mode" about 5 minutes after the reboot has finished and you rom is up and working, so all data is going to resync.

If you still have problems after normal use, repeat the actions, or at least reboot a few times.

Hope it helps!
[Nexus 6  Original Android Development] wrongway213:
Definitely hope it helps someone - will be sure to send people having issues to this post. Thanks Damon.
[Nexus 6  Original Android Development] old_fart:
Groan, did not work . . . But I'm not the smartest turnip that fell off the truck, so maybe I did it wrong . . . Is there a you tube video ?

.

maybe I need to wait a spell ? I see the service is disabled currently . . .
[Nexus 6  Original Android Development] Damon13:
Zephik posted a link to 2-21-15 Banks Gapss in page 575 of Chroma ROM, hope it helps.
[Nexus 6  Original Android Development] rearden_metal:
S2W and touch screen issues while in-call

So I'm running stock with LK 1.16 with haptic DT2W and S2W enabled.

What I've found is that when these are enabled and I'm on a phone call, the screen will remain sensitive to touch input despite being physically "off." This will 9 out of 10 times end in my cheek brushing up against the screen and ending the call.

flar2 describes this issue on his kernel's XDA page and suggests a fix by downloading his app called S2W Phone Call Disabler, which disables S2W/DT2W upon initiation of a phone call. It fixes this problem, though I've [unfortunately] found it to be pretty buggy, almost 50% of the time preventing me from waking the screen during a call or even preventing me from ending a call. I tend to have to wait until the person I'm talking to hangs up and the network registers that the call is over (usually up to 10 seconds) before I'm able to wake my device or even use my screen again.

Has anyone else had this issue? If so, what's your setup? I'm almost certain it's the Phone Call Disabler app, but without it I essentially can't trust myself to not hang up on everyone I talk to. Lose-lose situation.

Love LK and the DT2W/S2W implementation, just trying to figure a way to have them both. Thanks so much [MENTION=3357040]Imoseyon[/MENTION] for what you do.
[Nexus 6  Original Android Development] old_fart:
Thanks, it really was disabled like it showed, and so there be 'deep sleep' back again. Ug, will it be back if I warm boot -or- cold boot ?

.

When I was doing the 'forced stop', it was immediately un-stopping itself ! ! ! So I did not have a warm and fuzzy feeling it was headed for a fix. . . .
[Nexus 6  Original Android Development] Damon13:
Here check this thread its in page 34, they talked about it further. Hope your nexus deep sleeps again. Zephik also posted an old version of GAPPS that doesn't have the update system wakelok

http://xdaforums.com/android/apps-games/app-google-play-services-t2795911/page34

If you are referring to Zephik link, I think you should be fine after a reboot.
[Nexus 6  Original Android Development] bradputt:
[MENTION=3357040]Imoseyon[/MENTION] , would you consider multiboot kexec support sir?

https://plus.google.com/106544733723469872647/posts/FZ2cSzTQwBH
[Nexus 6  Original Android Development] anthonyg45157:
I haven't tested this kernel since my galaxy nexus. Let's see how it does! :D

Thanks imo
[Nexus 6  Original Android Development] Yank555:
This is normal, since the digitizer will remain active when the display is turned off.

We had the same issue with touchwake, what we did back then on i9300 and I also did on n9005 was to read the proximity sensor whenever a touch was detected, and to ignore the touch if the proxy was triggered (phone close to your cheak).

That would always be active, don't think a kernel can see call status since that's handled by RIL with the radio h/w directly... I could be wrong here ;)

Anyway, including the proxy reading solved the issue for touchwake and should do just as much for dt2w / s2w etc.

But it needs coding this first ;)

JP.

PS: Haven't cared coding that as I don't use dt2w because of the battery drain...

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.65 kernel.
[Nexus 6  Original Android Development] Imoseyon:
um, i'm not sure exactly what multirom is and why it requires kexec support (although I can guess why). I probably won't add kexec support unless there's a huge demand for it.
[Nexus 6  Original Android Development] LordDeath:
Has someone already experimented with undervolting the CPU? My PVS BIN is only 4 and I noticed some slowdowns during longer gaming sessions due to throttling.
[Nexus 6  Original Android Development] natezire71:
I just tested this. I have DT2W enabled. I placed a call, and then tried tapping all over the screen while I held my hand in-front of the prox sensor. Nothing happened.