Database Users

Wakelock on my Find 5

I'm switched over to the latest OmniROM nightly (Currently 20140125) for my Find5 but discovered a bad wakelock I never experienced before. It keeps the phone in a wake state like 95% of all the time.
sns_periodic_wakelock
Google and Forum search for it showed up several possiblitys, I tried to eliminate them all. Today I completely wiped my phone and installed the latest Omni nightly on a blank device with TWRP + Core Google Apps without installing any other additional app to it.
And still the sns_periodic_wakelock was there. So it must be caused by something related to google core apps or omnirom itself.
Did anybody discovered something similar with Omni Rom on find5? I never had this before on non kitkat roms.
And it's not just a display fail, the battery is really draining fast with omnirom. Unsubale in my case. Charging to 100% and 3hrs later just letting my phone "sleep" the batery is already down at 20% with only 5min display time.
Any suggestions would be awesome!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had this too ...think it was right after i switched to omni. For me the next nightly or the one after it fixed it for me. That's all I can say.
Sent from my Find 5 using XDA Premium 4 mobile app

Last time I saw an "SNS_XXXXXXXXX" wakelock...was when I had a stockish ROM, and the big hint as to what it was-was the FaceBook icon for the wakelock.
I suspect a social networking app is the culprit. "SNS" standing for "social networking service".

Today I totaly whiped the phone again and installed the latest omni again. Seems to work because now the SNS Wakelock is still present but below 5%. Strange...
I keep an eye on that.

solarizde said:
Today I totaly whiped the phone again and installed the latest omni again. Seems to work because now the SNS Wakelock is still present but below 5%. Strange...
I keep an eye on that.
Click to expand...
Click to collapse
My guess is that it's in gapps somewhere... Or maybe it's in the blobs... I should look through the blobs directory for that string.
While it's listed as a kernel wakelock, it is not actually present in the kernel as far as I can tell. It also doesn't appear in any of the frameworks.
(While most Android wakelocks go through the PowerManagerService and all get lumped under a single wakelock at the kernel level, it IS possible for any userspace application to grab a kernel wakelock of any name.)

Skripka said:
Last time I saw an "SNS_XXXXXXXXX" wakelock...was when I had a stockish ROM, and the big hint as to what it was-was the FaceBook icon for the wakelock.
I suspect a social networking app is the culprit. "SNS" standing for "social networking service".
Click to expand...
Click to collapse
not at all
sns are sensor wakelocks
@Entropy512 you will find this in the sensors.qcom binary
sns_async_ev_wakelock
sns_periodic_wakelock

maxwen said:
not at all
sns are sensor wakelocks
@Entropy512 you will find this in the sensors.qcom binary
sns_async_ev_wakelock
sns_periodic_wakelock
Click to expand...
Click to collapse
Sounds to me like some app is asking for sensor data and causing the wakelock then.

GPS Battery bug

Hi all, got my Note 3 Thursday and I love it, came from a Z1 and what I love the most is the battery life. I'm a pretty heavy user and so far I'm getting at least 6hrs screen on which is awesome for me!
Anyway I noticed today that even though my GPS hasn't been on its showing on in battery stats
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but when I did turn the GPS on it shows its off, it's like it's inverted strangely....rebooted phone still same.
I will back up and factory reset it tomorrow, but wanted to check if anyone else had this before, I did search but nothing came up. BTW I'm stock unrooted.
Sent from my SM-N9005 using Tapatalk

never heard of this.

polish_pat said:
never heard of this.
Click to expand...
Click to collapse
A colleague of mine is having same problem but with wifi, it's inverted....I will point out though it doesn't seem to have an effect on battery life. Must be a visual bug.
Sent from my SM-N9005 using Tapatalk

Edit: mine wasn't inverting like yours, just showing the gps on when it was off.
I isolated this down to google maps, I didn't notice a drop in battery, but It bugged me none the less. Once location was blocked in Xprivacy it stopped reporting GPS-on in the battery stats. This might fix it: Try temporarily disabling google maps from app info and see if it stops, then re-enable.
Sent from my SM-N9005 using Tapatalk

OP screen looks strange and looks nothing like mine: I have GPS on all the time and actually used maps for driving from work today and GPS shows active only when screen was on. With screen off on mine GPS shows off as well, where OP shows GPS active all the time. I wonder if OP has some program requesting GPS position at all times, even with screen off. Maybe some anti theft tracking or showing OP position to friends and family? Maybe same program over rides off setting? I never heard of settings being inverted, but maybe there is some system error.

Thanks for your feedback, after trying a few things: disabling Gmaps, rebooting device, turning off location services still no joy. So before doing a factory reset I reset the app preferences, which you can do but going to settings>app manager>all>press menu and then select ' reset app preferences' and it worked.
So it must if been some app causing this, I don't have a tracking app apart from the Android device manager, which is on, a bit stumped what it was but now glad it's gone as my OCD was going through the roof!! ?
Sent from my SM-N9005 using Tapatalk

I had the same problem,all my GPS settings were set to off but somehow the Battery stats were showing that the GPS was all time on! I tried many things until I found the real culprit, and in my case was not the OS software but an App that is keeping the GPS on despite closing it! The App (2GIS) is of course related to GPS as it includes navigation among its features.The solution was to close the app and reboot my device instead of deleting that app as I really want it! So I will advise anyone with this problem to find every app on their phone which uses GPS and monitor them, hopefully you will track down the culprit!

Google fit app on L is draining machine.

Look at this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I highly recommend you guys to disable it if you want your battery to be better ?

How was your actual battery life with it on? I've been running Fit on my phone since the first Nexus 6 port was available. While it does hold a wakelock the hit to battery wasn't all that bad considering what the app does. I average maybe 30 minutes or less SOT time with the app turned on from 630 am to 1030 pm. I was impressed as I thought I'd be recharging shortly after lunch.

Will it still drain if I don't use it but have it installed. Somehow I see notifications on my moto 360 from fit.

Use Greenify Dude !!!

thefunkychills said:
Will it still drain if I don't use it but have it installed. Somehow I see notifications on my moto 360 from fit.
Click to expand...
Click to collapse
It working without notification in backgriund. I belive only solution , if You don´t want to use it, is to freeze or uninstall this wih TiBu.
EDIT: looks like it is possible to disable Fit ( maybe ), under settings> Google Fit Data>and turn off Activity detection. I belive then it wont work ay more.
EDIT: nope...still working

Guys, it's not affecting battery. Don't constantly look for issues. I use Google Fit (cause I have a Moto 360) and it doesn't affect normal usage so therefore it's not an issue. If it WAS an issue it'd show in the battery graph and you'd kill your battery in a couple of hours - THAT would be an issue!

EddyOS said:
Guys, it's not affecting battery. Don't constantly look for issues. I use Google Fit (cause I have a Moto 360) and it doesn't affect normal usage so therefore it's not an issue. If it WAS an issue it'd show in the battery graph and you'd kill your battery in a couple of hours - THAT would be an issue!
Click to expand...
Click to collapse
Yeah me too. I don't see any difference with or without Fit.

http://nexus5.wonderhowto.com/how-to/your-nexus-5-has-real-pedometer-built-in-heres-you-use-0151267/
There is not going to be any noticable drain because the app is using the low power core. It's the same core that was supposed to give us always listening Google Now when the phone launched but Google gimped us because of patent bs.

Uh, maybe. I don't know. Maybe because we have pedometer sensor built in so its not draining battery..

Some new finding on app behavior after the 146MB update.

The battery improvement is significant for sure after the update, I also found that using samsung package disabler to freeze some of the app is not causing the battery drain any more. (My personal experience before the update was disabling app using package disabler actually causing some of the battery drain). I will attach the one I disabled right now. So far there doesn't seem to be any effect on battery life. I didn't disable the knox or samsung pay function as I use them quite often. I'm also try to be less aggressive with the app I disable. App that could making the communication in the background I try to avoid disabling them.
Also, I found greenify's aggressive doze function seems to working for me. At least, help extend battery a little bit when not in use. I only open the aggressive doze function and never force it to hibernate app. I also exclude many of my frequently used app from hibernation list.
The apps I have freezed using package disabler
https://drive.google.com/file/d/0B5iHdAT2Mw5lRjYzUHlXS0FuUmc/view?usp=sharing
I will upload some result tonight.
Hope I can hear more tips from other users. I keep getting about 60% or more left after the update with about 2 hour of sot when I go to sleep compare to maybe 30% to 40% left before the update. I don't use dark theme as I like lighter color. Also, I use chrome browser and listen to a lot of pod cast when I'm drove home. I also try to close the screen when using GPS to save power but my location is always set at high accuracy, I tried GPS only mode but don't think that effect battery life of the phone. I want to use the phone as normal as possible. Different people have different usage, If you using GPS all the time and turn off the screen while using it. The screen on time probably pretty low but still have high battery usage. Therefore, I believe SOT to be highly subjective.
I also read that the best way to protect battery is not let it fall below 40% or 50%. So after some more testing, if I found the battery report seems to be stable after this update. I will just using wireless charger to top it off during work time.

0verdaflow said:
which apps did u freeze ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I attached the link which contain the app I freeze. You can also download it and import through package disabler.

What are these wake locks? (13960000.decon_f, ssp_wake_lock)

Hello there! I have a S7E rooted and I have the following wake locks that are bugging me (can't find any info on them).
13960000.decon_f
ssp_wake_lock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

andrepcg said:
Hello there! I have a S7E rooted and I have the following wake locks that are bugging me (can't find any info on them).
13960000.decon_f
ssp_wake_lock
Click to expand...
Click to collapse
Your sensors and screen on time.
You know Google, right? They actually made your OS, but they have this big search engine which can give thousands of answers.

Faspaiso said:
Your sensors and screen on time.
You know Google, right? They actually made your OS, but they have this big search engine which can give thousands of answers.
Click to expand...
Click to collapse
I searched but every forum I went nobody had an answer, or I couldn't find it. I always search before asking

andrepcg said:
I searched but every forum I went nobody had an answer, or I couldn't find it. I always search before asking
Click to expand...
Click to collapse
Well there you have your answer. I confirmed both with a Google search though.
You can't change kernel wakelocks without a custom kernel, but yours are normal. Disable some things you use, that use sensors if the battery life annoys you. But really, it don't drain much.
Partial Wakelock and Alarms are the things you have the ability to change.

I just really wanted to know what they are that 13960000.decon_f name was pretty weird and I decided to investigate.
Thanks guys!

Faspaiso said:
Well there you have your answer. I confirmed both with a Google search though.
You can't change kernel wakelocks without a custom kernel, but yours are normal. Disable some things you use, that use sensors if the battery life annoys you. But really, it don't drain much.
Partial Wakelock and Alarms are the things you have the ability to change.
Click to expand...
Click to collapse
I am also having the same issue. But i am having custom kernel on my s7e. So what I have to do? Please explain step by step.
Sent from my SM-G935F using XDA-Developers mobile app

nimalen87 said:
I am also having the same issue. But i am having custom kernel on my s7e. So what I have to do? Please explain step by step.
Click to expand...
Click to collapse
Which kernel do you use? You need a kernel that have synapse. AEL and Superkernel have Synapse support which can disable kernel wakelocks. Don't know about other kernels.

decon_f
should match your screen on time
"It's a wakelock that is taken when you turn your screen on. The count is how many times you turned your screen on and the time is your screen on duration. It has zero effect on battery consumption." [email protected]
ssp
advanced sensor hardware
https://github.com/gokulnatha/GT-I9505/blob/master/drivers/sensorhub/Kconfig

I had the 13960000.decon_f when I had the xposed module Fingerprint enabler enabled. After turning that off it vanished. Now, its returned again. Is there any way to detect what was causing the wake lock

sohojmanush said:
I had the 13960000.decon_f when I had the xposed module Fingerprint enabler enabled. After turning that off it vanished. Now, its returned again. Is there any way to detect what was causing the wake lock
Click to expand...
Click to collapse
I just told you what it is one post above yours. That wakelock has NO effect on battery. Ignore it.

Just chipping in here, as I see some people's answers are on the hostile end of the spectrum.
I also have the 13960000.decon_f wakelock on my s7 flat that I'm trying to figure out. The amount of time for this wakelock is about an hour, but my screen on time so far is 3 hours. So there doesn't seem to be a direct link between the 2 so far
However, I also have a PowerManagerService.Display wakelock that is identical to that of the decon_f wakelock

theo5388 said:
Just chipping in here, as I see some people's answers are on the hostile end of the spectrum.
I also have the 13960000.decon_f wakelock on my s7 flat that I'm trying to figure out. The amount of time for this wakelock is about an hour, but my screen on time so far is 3 hours. So there doesn't seem to be a direct link between the 2 so far
However, I also have a PowerManagerService.Display wakelock that is identical to that of the decon_f wakelock
Click to expand...
Click to collapse
The 13960000.decon_f wakelock seems to match up with SOT for me—not exactly, but with about a small difference that seems to get larger as the day goes by, which I presume means the wakelock takes a second or something after turning the screen off to actually unlock. So what dynospectrum said seems to check out for me, but it's very interesting that it doesn't match up for others. I wonder if there could be something that causes it to hold the wakelock longer after the screen is turned off, resulting in the longer time. @dynospectrum, do you happen to have a link back to the source where @AndreiLux wrote that quote you posted?

It doesn't for me definitely. decon_f wakelock around 12h 31min, while my SoT is only 30 minutes.