yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] jishinya:
I usually does swipe away all the recent apps before I put my phone to sleep; to ensure that it'll get a good sleep. But the wake lock does occur even if I does that; and just randomly disappeared now (as per what I mentioned in previous reply).

I don't think it's kernel related, but it's really too random to pin down an application or behavior to be responsible for the wake lock. Let's see if the problem will reoccur in the future, can't reproduce it anymore for now (at least).
[Nexus 4 Q&A, Help & Troubleshooting] BloodCreams:
I have this issue too and it's killing my battery. On an average day, I would usually get around 2 hours and 30 minutes of screen on time before my battery reaches 20%. And that's without data turned on; only connected to wifi, in addition with the sleep policy set to when the screen turns off. I have been looking into this issue for quite some time now and I have deleted over 20 apps. Prior to that, I have noticed that after I have uninstalled the live wallpapers from DualBoot Games, my battery life has improved a little bit, with a few more minutes of Deep Sleep, but the difference is very minimal though. After some more digging into the cause, I have found what may be the solution, but I haven't tested it yet, due to the fear of messing something up with the kernel. My Nexus 4 is rooted, running stock rom and I have been exploring though FX File Explorer (One of the best file managers I've used so far) and one time, I came across this system dump file. In order to view this, your phone has to be rooted and have the FX File Explorer with the root add-on installed (I'm not too sure about other file managers). Next go to 'System (Root)' > sys > power > wake_lock. And in there you should be able to see those two pesky wakelocks. Should I delete it? I really hope that doesn't affect the phone in any way except give me Deep Sleep back.

UPDATE: Tried deleting it; couldn't be deleted. Can't edit it either. It goes back to its original state. However, I could change the permissions.
[Nexus 4 Q&A, Help & Troubleshooting] TotalBS:
Interesting find. I looked into the wake_lock file and I doubt a file's presence is responsible for contributing to this wakelock because all it contains is that simple text and I would assume its purpose is to be some sort of record for battery stats? But I'm just guessing here.
[Nexus 4 Q&A, Help & Troubleshooting] BloodCreams:
Maybe it could be just a file log. But then in that case, shouldn't it not be located so deep inside the kernel files? I mean, the deepest part of the kernel a file log should be is in the main storage, especially when there aren't really any detailed stock battery tracking apps. The only ones I use are GSam Battery Monitor and Better Battery Stats, both of which do not require root access for tracking kernel wakelocks. I guess if it could be some sort of record it should be deletable anyway as the system will get to record it down again?

Anyway, here's a thought: isn't most of the system made up of text files that have specific names that some may or may not contain text in them, and with that, they work with each other and other file formats to form a whole operating system? And totally, isn't the whole system coded in text? So that simple text file must have got to be somehow responsible for the wakelocks. That's from my perspective. But then again I could be wrong. Either way, I'm really hoping that Android 4.2.2 will fix this once and for all.
[Nexus 4 Q&A, Help & Troubleshooting] JsChiSurf:
I had this some problem and spent a significant amount of time trying to find the culprit in my particular case. Each person's culprit is likely different, so YMMV.

I had these same wake locks after an immediate reboot, causing the phone to never deep sleep and have 100% wake time, even with screen off, resulting in massive battery drain (12-15% / hour w/o use).

After methodically uninstalling app after app, widget after widget, my culprit was the use of Locale.

I placed an inquiry to their support team, and they stated this is a known general issue with Jelly Bean in that the ROM is not releasing the accelerometer when the app tells it to do so (makes sense therefore if you experience the same issue after playing a game). Since Locale launches on startup to monitor conditions, I had the issue 100% of the time.

They went on to state that they have a "cloud script" (whatever they hell that means), that detects the ROM version and "fixes" the known issue, but since I was running a custom ROM, the "fix" is not applied, since they cannot detect a stock ROM to apply the fix.

They told me unless I run a stock ROM that they can detect, I'm SOL.

I decided to modify my build.prop to display stock values for how the ROM identifies itself, uninstalled and re-installed Locale, reset my conditions and the problem has gone away 100%, and the phone now sleeps like a baby!

So, unless the app you are running has a similar fix, I'm not sure there is much you can do other than detect the culprit and uninstall. Perhaps 4.2.2 will fix as well?
[Nexus 4 Q&A, Help & Troubleshooting] jishinya:
An update to my previous post:

I managed to keep track of the culprit application which are responsible for these two wakelocks.

In my case, it's the Auto Call Recorder that causes the wakelocks.
[Nexus 4 Q&A, Help & Troubleshooting] Stylez Ray.:
I also had this two wakelocks which were driving me crazy...my culprit was the game Rage of Bahamut...
[Nexus 4 Q&A, Help & Troubleshooting] BloodCreams:
Just got the 4.2.2 update today. And immediately after that, the wakelocks stopped. Now I am getting Deep Sleep like I am supposed to, with only PowerManagerService having the highest wakelock of 4 minutes as of right now. The culprit seems to be Poweramp having a partial wakelock. I have encountered this before and the fix is easy; just reboot the phone and it'll stop, but it may come back, and in that case, just reboot again. Otherwise, everything else seems normal. With that said too, the wake_lock file no longer has both sns_async_ev_wakelock and sns_perodic_wakelock in it (look at my previous posts), now with only PowerManagerService. Overall, I am very happy with the 4.2.2 update so far.
[Nexus 4 Q&A, Help & Troubleshooting] TotalBS:
I've been on 4.2.2 for a couple days now and everything seems to be fine. I can't seem to reproduce the async wakelock like I could before, so it looks like Google might have taken care of it
[Nexus 4 Q&A, Help & Troubleshooting] Ok_Kaleidoscope5109:
how do you guys know it's an app? this kind of wakelock I only saw once. I'm not even sure what cauused it. How can you s ay it's a specific game or whatever? I don't even have games. It comes and goes. Sometimes it will never happen. Because you reboot and uninstall an app you say it's a specific app now?

I don't think you can specifically point to an app unless you reproduce the wakelock reliably. But given that these wakelocks only happen once in a while where you get massive wakelocks, it's hard to say.
[Nexus 4 Q&A, Help & Troubleshooting] TotalBS:
The only reason I know it was a specific app for me is because I would monitor BBS and record the time for the sns wakelocks and the time would be pretty low before I launched certain apps, but after I closed them out and let the phone sit for a while I would start getting large sns wakelocks equal to the amount of time the phone was off for. So since I didn't do anything else with it after closing the specific app it was pretty easy to tell what was the culprit. However now, the wakelock doesn't seem to be tied to any specific types of apps, so I'm not too sure how to stop them anymore (I don't even get the wakelock very often anymore)
[Nexus 4 Q&A, Help & Troubleshooting] Ok_Kaleidoscope5109:
The thing is I got it a second time today in 2 months. I don't know what it is still. I could uninstall an app now and reboot and it won't show up. The danger is that I could now post that it's gone and it's due to XYZ app. But I bet you I could not even touch the app and reboot and it won't show up again...

I honestly don't think this wakelock is even that big of a deal. I was getting ~4% drain in general per hour. Today I have it and my drain is about the same.
[Nexus 4 Q&A, Help & Troubleshooting] TotalBS:
2 times in 2 months isn't too bad. Before, I was able to reproduce the wakelock on command and it would appear by itself multiple times a week. 4.2.2 seems to have fixed at least one major cause of it since it's so infrequent now. And if you're getting about the same battery life like me, then it does seem like it's been "fixed"
[Nexus 4 Q&A, Help & Troubleshooting] sirxdroid:
Having the same problem of high wakelock count for both sns_async_ev_wakelock and smd_sns_dsps. I tried a clean install of 3 different ROMs without further installing any apps, just BBS. And the problem is there for all 3 ROMs: rooted stock by bigxie, EOS, MMuzzy. Must be "normal" for the N4 or a bug somewhere. I posted a thread here:

http://xdaforums.com/showthread.php?t=2272097
[Nexus 4 Q&A, Help & Troubleshooting] mgs333:
not much to add but still experiencing this wakelock from time to time on the CM 10.2 nightlies...
[Nexus 4 Q&A, Help & Troubleshooting] jackiass:
My solution was to uninstall Automatic Call Recorder. After that it now goes into deep sleep just fine and BBS doesn't show sns wakelocks anymore. I'm on stock rom 4.1.2 LG Optimus G E975.
[Nexus 4 Q&A, Help & Troubleshooting] msassounian:
I will preface by saying I do not have a nexus 4, and I know this isn't the right forum, but i've searched high and low and the nexus 4 forum seems to be the place where this is happening. I have a droid razr HD xt926....

Alright guys i'm going out of my mind with this issue. My phone will not go to sleep. at all. I notice it's two wake locks that seem to start up the moment i try to lock my phone (any time the screen is not on, these wake locks are running). I've searched all over and read probably every thread through that has these wake locks in it and i'm at a loss. I wiped the phone clean (no FDR...) reflashed the ROM, let the phone sit idle over night (twice under different conditions). Here's what happened. I attached screen shots of BBS if that helps anyone see what i'm talking about

Culprit Wake Locks: sns_async_ev_wakelock, smd_sns_dsps

#1: this was on the last unofficial build of PA. It sat all night on idle and lost 4% battery/hour. didn't sleep for one second.

#2: clean wipe, clean flash. only booted it up enough to re-download better battery stats. immediately shut off sync for my google account. let the phone idle over night again on but on airplane mode this time. Same two wake locks (plus power manager service....) running the whole time it should have been trying to sleep. I then saw that one of the wake locks was NFC related, so i turned off NFC and android beam. still the same ****.

I'm officially out of ideas.

Any help, any ideas, any direction would be much, much appreciated. Thank you guys.

the screen shots are from attempt #1. the dump file is from #2
[Nexus 4 Q&A, Help & Troubleshooting] niekschoemaker:
Well after 2 months I finally managed to fix this problem! :D

at first I found somewhere that this was the kernel not releasing the accelerometer, I too was positive about this.

So as a temporary fix I disabled auto rotate, fixed it temporary, sometimes another app still wanted the accelerometer, I kept an eye on this in wld and just rebooted when it appeared, kinda annoying, but better than a dead battery at around 3 pm.

And now I installed Nexus 5 experience rom, had it already but with caf kernel, now I did the aosp (stock) kernel and there it went, problem solved! :D
[Nexus 4 Q&A, Help & Troubleshooting] ScumDroid:
Its definitely an issue with the accelerometer. When i lock the rotation on my nexus7 2013 the sns_async_ev wakelock stops dead until screen rotation is turned back on, then it starts again. I know this isn't the proper forum for this post, but its the only place i found any helpful info on this wakelock. I sent my tab back to Asus last week after the screen randomly showed a purple circle on it one day the size of a dime, I dont know what they did to it but now i have it back and im getting this wakelock over 100 times a second, yes you read that right, over 100 times per second..... I can literally watch the battery drain before my eyes, and it was definitely not there before Asus "fixed" the tablet. I will be contacting them tomorrow to see what can be done, I'm surely not paying shipping again to send it back to them a second time. :(
[Nexus 4 Q&A, Help & Troubleshooting] niekschoemaker:
Well for me it was just a cheer done too early, it returned, and worse than before, same as with you, like massive, massive amounts of them! I broke my screen and have to get it repaired, I'm thinking about just buying a new one, costs the same amount of money.
[Nexus 4 Q&A, Help & Troubleshooting] niekschoemaker:
Oh well, I think I got it right this time, not sure, just testing it for half an hour now, but I noticed another wakelock too: smd_sns_dsps, so after searching a while, Google constantly gave me search results of dsp (equalizer) so I thought: maybe there is some sort of sensor for the equalizers so that the extra s is just a way of saying it's more than one, and since the sns_async is a sensor wakelock too but the difference"sns_async_ev_wakelock" is only saying, hey you got an asynchronous task running in the background, something to do with sensors, but the other actually gives the device (smd_sns_dsps is litterally listed in the dev folder) and I had viper4android installed, a really advanced dsp, so I just took the leap and deleted it, and so far so good, no excessive wakelocks. Hope it stays this way this time, I'll report in few days.
[Nexus 4 Q&A, Help & Troubleshooting] calav3ra_de:
sitting here right now with a nexus 4, marshmallow rom (frank) and hellsgod kernel, same wakelocks - disabling screen autorotation seemsto have fixed it for now. :)
[General Questions and Answers] alexkiorp:
Hello everybody,

I have some serious issues with internal memory since i flashed the Cyanogenmod 10.Now i have a question that i need to answer:

is there a way to flash Cyanogenmod 10 from sd card on Samsung Glalaxy 3 or even better to move EVERYTHING from internal memory to sd card (or at least everything i CAN move) to free some space?

Please remember that i'm new to these so if anyone will try to help me should give me something like step-by-step help.

I've messed my head trying to solve this by searching Google but i came up with nothing.

Please give me some help.Thank you for your time,I appreciate.
[Galaxy S I9000 Q&A, Help & Troubleshooting] neo143:
Hi my i9000 totally messed up. I can only goto download mode. even when i flash CWM and try installing any rom .the phone switches off in between. all i could do is flash rom directly using odin. can any one provide me any rom with .tar so that odin can flash as all rom i find are zip.:cowboy:
[Galaxy S I9000 Q&A, Help & Troubleshooting] ts1506:
Find a stock ROM with 3 files , like XXJVU , then flash .tar based Value Pack like XWJW6 etc.

Here is a list of Stock ROM and link

http://xdaforums.com/showthread.php?t=1102881

BTW , I think this thread should be in Galaxy S i9000 General.
[Galaxy S I9000 Q&A, Help & Troubleshooting] neo143:
Can u specify any custom rom with .tar extension. i have tried but the phone stops at repartioning. i had been previously on jelly bean cynaogenmod 4.2.1
[Galaxy S I9000 Q&A, Help & Troubleshooting] empulse92:
http://www.share-online.biz/dl/7EZYMR5MVOQT/free/

this should do it.

flash with the pit file and repart should work
[Galaxy S I9000 Q&A, Help & Troubleshooting] Neobomb:
Darkyrom RE ROMs are tar
[Galaxy S I9000 Q&A, Help & Troubleshooting] Deleted member 4142310:
+1 for darky

http://www.alliance-rom.com/community/threads/odin-darkyrom-10-2-resurrection-gt-i9000.4272/

sent from a slim bean with max memory
[Galaxy S I9000 Q&A, Help & Troubleshooting] stephendt0:
Install the latest stock ROM and then use CFROOT to install CWM 3.0.x.x. Then install cm10 stable (zip format). Make sure to factory reset in CWM 3.0.x.x first, then install CM10, then it will reboot to a newer recovery so install CM10 again, then install GAPPS, then factory reset again. That should do the trick (just did exactly that 5 minutes ago).
[Galaxy S I9000 Q&A, Help & Troubleshooting] egonzalesjr25:
I think we have exactly the problem and cause..... for additional, i cant even boot on cwm recovery.......... hope i can find a way
[Nexus 4 Q&A, Help & Troubleshooting] kgeissler:
My screen cracked on my N4 and I am sending to LG to get repaired. I want to wipe the device first, but my screen is unresponsive. I don't have USB debugging enabled, but I can see my N4 directories if I plug the phone into the PC.

Is there anyway to flash images or even power off the device? I can turn the screen on, but the screen won't work. So I can't even power it off or boot into bootloader. Any ideas?
[Nexus 4 Q&A, Help & Troubleshooting] kgeissler:
Well, I figured out a way. I remembered I had Cerberus installed with the ability to wipe the phone and SD card remotely, so that is what I did.
[Nexus 4 Q&A, Help & Troubleshooting] Censura_Umbra:
If the phone is on/ awake hold the power button for about 15secs. Then boot into recovery, up col and power I believe, then wipe data. Not sure the button combo to do that though. Probably up then down x 3 then power. But don't quote me. I don't have my N4 yet so if someone can try it and record the exact button steps that would be great.

This is assuming you don't have a custom ROM or recovery.

---------- Post added at 03:44 PM ---------- Previous post was at 03:35 PM ----------

So it wasn't rooted or custom ROM or boot loader unlocked etc?
[Nexus 4 Q&A, Help & Troubleshooting] kgeissler:
Also...funny thing is, I had an RMA with google already because I had yellow tinting on the screen when it got warm. The RMA arrived the same day I cracked the screen. So I called Google and told them and asked if I could just buy the new one and not send my old one back. They said that was fine. So, when the cracked screen gets fixed by LG, I will have an addition N4.
[Nexus 4 Q&A, Help & Troubleshooting] Censura_Umbra:
I'll take it for $325! Lol you know,as a helpers bonus...or something
[Nexus 4 Q&A, Help & Troubleshooting] kgeissler:
I will probably sell it for $450...it is the 16gb you know. :)
[Nexus 7 Q&A, Help & Troubleshooting] Skyfall007:
Hi guys. I bought my N7 2 weeks ago and I think it has screen lift on the left side. Please look at the photos and tell me if I should send it to warranty. And one more question.. screen lifting is happening in time or it had been there since you bought it?

p.s:screen is covered by a protector film
[Nexus 7 Q&A, Help & Troubleshooting] rcarnes911:
Try tightening the screws on the side with the lift that worked for me and it did not take weeks for them to do the same thing
[Nexus 7 Q&A, Help & Troubleshooting] Skyfall007:
Will they send me another tablet or add some glue to my tab?
[Nexus 7 Q&A, Help & Troubleshooting] Adinaky:
If you want to do it fast try tightening those screws, it worked for me too. Or of course you can send it back. They certainly won't add any glue, I don't think so. They'll replace the tablet or the screen.

Next time please use the search function, there are hundreds of threads about the screen lift.
[Nexus 7 Q&A, Help & Troubleshooting] Skyfall007:
i know how to use search button.. but i wanted to post these photos.. to get your opinion
[Nexus 7 Q&A, Help & Troubleshooting] Adinaky:
That's what I was talking about, the screen lift is the same for everyone. Some millimeters on the left side. This is the most common issue for our N7.

Anyway, I think you should tighten the screws. That's the simplest solution to the problem, because if you change it, there is chance for the replacement to have the same or maybe another issue.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] mcluskyisms:
Hi,

I tried posting this on the official build thread although I haven't enough posts to do so, anyway I was just wondering if anyone else has had any trouble with the latest CM10.1 builds?

I'm having issues with not receiving push notifications for things such as Facebook, Twitter, Instagram & email accounts etc. Also there is issues when using SwiftKey (suggestions dissappear after reboot) battery saver application keeps crashing although the notification problems is the main query.

Also wondered if the wifi/mobile signal indicators are no longer blue? Mine have been grey since I updated to CM10.1.

Cheers

Chris
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] The Lum:
I am running latest nightly and have done so since about 15th Nov last year. No problems getting push notifications here. Maybe just double check that push settings are on?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] mcluskyisms:
Hi, thanks for the reply. I've checked push settings in all the apps I mentioned and all notifications are on, still no joy. Also tried clearing app data and resigning in to each and that's not worked either.

Cheers,

Chris
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] perri.etb:
I'm also having trouble with fb but I havnt investigated since I don't use it very much.

The wifi being gray is normal. Thats the way its ment to be. The SwiftKey problem I solved it by instslling SwiftKey flow beta. I don't know why these one works.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Anthropostar:
The reason the wifi indicator icon is grey is because youre not connected to googles server. Try logging in with google talk.

Oh and stop using battery saver.

Youre not getting push notifications because batsav is killing your background apps (bookface, and such...)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] mcluskyisms:
All sorted out now cheers.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] tzortst:
How did you solve this?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] alinux777:
the wifi signal and the network signal are supposed to be blue, when they are grey there is no network, meaning problem with DNS or something.

thats in my case in every CM, AOKP, AOSP ROM i have tried.
[Galaxy S III Q&A, Help & Troubleshooting] adiel91:
Hey guys,

having some trouble for the last couple days.

my phone is getting laggy and very slow both in lock screen and in home screen and even when in the middle of using

some applications, sometimes it even freezes for 2-3 seconds before i can re-use it.

its not happening 100% of the time i'm using the phone, but it happens often.

i don't think its rom related, because i've used the rom for two weeks and all was good, then in the last days

its started. i'm assuming its got something to do with running proccesses or some app/mod i've installed.

Info:

S3-I9300

Rom: cfDroid v10 (based on XXELLA 4.1.2)

Kernel: Perseus 31.2

Themes used: JB Domination 1.5.5+Soul Bound 2.3

also using JKay Mod + Deluxe Settings. in deluxe settings i've checked the following options:

Whitelist TouchWiz Home

Whitelist Phone&Contacts

Whitelist Tab Lock Screen Apps (using JKay tab lockscreen)

In developer options, i've set "Windows animation Scale" and "Transition animation scale" to 0.5x

Here's a pic of running processes (if you need also the cached processes, please tell me):

The hebrew named processes, by name order, from left-to-right (in the pic) are:

Camera, Messages, Contacts, Firmware Update, Settings, Media, Email, Exchange Services, Simple Alarm Clock

If you need anymore information, please ask.

i don't want to re-flash the rom+kernel+themes+certain mods all over again, its a big headache for me, it will be my last resort.

Thanks for any help

Regards,

Adiel
[Galaxy S III Q&A, Help & Troubleshooting] adiel91:
please anyone..
[Galaxy S III Q&A, Help & Troubleshooting] DSA:
wipe, reflash the rom, then put each mod back in one by one and see what happens

its the only way to pinpoint the issue