yashsingh1/xdaforums huggingface dataset:
[Kindle Fire 2 Q&A, Help and Troubleshooting] elegant_universe:
Using ES File Explorer, I can navigate to '/data/local' directory and I can see a 'tmp' folder.
[Kindle Fire 2 Q&A, Help and Troubleshooting] elegant_universe:
Problem solved. Instead of using "adb push", I just place the file into '/data/local' manually. The rest of the steps went fine!
[Kindle Fire 2 Q&A, Help and Troubleshooting] ScootTheMoot:
No data/local/tmp folder...

So i go into my ES file explorer and i go to my data folder and it shows that i have no local folder, i actually have no folders in this directory. how would i create a local/tmp folder so i can successfully S-OFF my phone?
[Kindle Fire 2 Q&A, Help and Troubleshooting] stunts513:
There are folders in there, key thing is in order to see them you need root. Its weird like that, they might show up over and adb shell if you

adb shell
cd /data
ls

Or for a more formatted column listing use "ls -n", it will also display permissions of files and folders.
[Micromax A110] akashvfx:
Hello guys i am only sharing this cool app called apktool

With this apk tool you can compile and decompile apk and sign apks too

Here is the link

http://code.google.com/p/apktool/

Instructions:

Download the archive apktool4.0_armhf.zip from

http://code.google.com/p/apktool/downloads/list

Download the updated apk file Apktool4.0.apk

Extract/unzip archive to /sdcard/apktool

Install the updated Apktool4.0.apk

Open app from app drawer, and have fun using it!

If u getting error then go to system/framework/ and hold the framework-res apk and install as framework then recompile and decompile apk it will definately work
[Micromax A110] Lal Ayer:
Nice Work Bro
[Motorola Atrix 2] mohammadumair:
Guys i was on Liquid smooth rom v2.5 before (used it with BMM on JB leak 1 china). I used atrix2bootstrapper to flash razr M boot image and got bootloop. I fxzd back and then reverted back to leak 1, rooted again and installed leak 3.. Now i'm on Leak 3 rooted. The question is i have not installed atrix2bootstrapper this time. Do i need to make any change to the logwrapper file? or shall i directly install BMM and start flashing rom (MIUI to be precise). Will it any way affect the logwrapper file or will it create another logwrapper.bin file after installing BMM. Hope reply will be soon :fingers-crossed:
[Motorola Atrix 2] hafizkris90:
fxz = fresh system..

Edit: oh wait.. how do u txz leak one then go to leak 3?

Sent from my Google Eyelids while sleeping..
[Motorola Atrix 2] 1BadWolf:
If you haven't installed atrix2bootstrapper then, no, you don't have to edit the logwrapper file. Yes, you can just install bmm and start flashing.

Brought to you by time and relative dimensions in space.
[Motorola Atrix 2] mohammadumair:
I used the fastboot file(non-AT&T) leak 1. Before this i did go into AP fastboot, then recovery and formatted the system completely. Then fxzd it. Something strange did happen. The RSD lite said "status FAIL!". Then as soon as i removed the USB cable it booted automatically. Strangely enough it did boot into Leak1 JB after a whole 5minutes!. Regret using A2bootstrapper with BMM.

I didnt get the answer to my problem. Should i change the logwrapper extension or not?... Thank You
[Motorola Atrix 2] mohammadumair:
Thanks bro. Anyway whats with the bug saying miui ui (not supporting qHD) dislocation problem. If the problem is big, i better use liquid smooth or mokee. Which is the rom maximum no. of A2 users running?
[Motorola Atrix 2] 1BadWolf:
If you've flashed back to ICS via FXZ, then flash JB leak 1, then rooted and installed BMM then I don't think you'll need to do anything with the logwrapper. That procedure should only be necessary if you installed a2bootstrapper after flashing the FXZ. So, I guess the short answer is, no.

I don't know much about MIUI. I have installed it a few times on various devices but didn't keep it long as I prefer AOSP based ROMs. So hopefully someone that knows about MIUI will answer that for you.:thumbup:

Brought to you by time and relative dimensions in space.
[Motorola Atrix 2] mohammadumair:
Not found any problems with miui

No problems with miui except that there is no miui camera and also there is screen rotation problem.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] thegios:
How does an itinerary look on your note with the new gmap?

For me half of the screen on the left is covered by the list of directions, leaving only the half right visible.

Is it normal? Totally useless...
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] thegios:
I can't believe there's no one using gmaps here or at least willing to drop a couple of lines to confirm.

Thanks anyway.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
I would fire my Note up and have a look but for the ignorant post above .

jje
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] shaun298:
I just tried it. And I thought it was going to be great until I tried to exit out of the box on the left so as to see the map. when you hit the X you can no longer see the map WTF.

---------- Post added at 10:33 PM ---------- Previous post was at 10:24 PM ----------

If you could just close the itinerary it would be fine. But as it is it sucks.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] thegios:
well it seems it's a general complain...

- the directions take half of the space

- no way to use intermediate stops

- no more my maps

- if someone creates an itinerary with intermediate steps in OLD version of web gmap and you try to open it on the tablet, the intermediary steps are ignored

- if someone creates an itinerary with intermediate steps in NEW version of web gmap and you try to open it on the tablet, it open the browser and not the map
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
Looking at some XDA and Reddit posts, small set of users (my Nexus 4 including, unfortunately) experiencing some sort of bug with stock not rooted Android 4.3 after OTA on all range of Nexus devices.

The bug is Android OS holding device awake all the time and not letting it into deep sleep. It looks like it has not huge impact on battery life, but still it is abnormal. Rebooting devices, for me, curing this, but only for a day or two, after a few days wakelock makes its come back.

Unfortunately WakeLock Detector does not show who is guilty, looks like it is in the kernel. I just have bought BetterBatteryStats, and will look at its data tomorrow. What WLD does show is that my Nexus 4 had 0:00 of deep sleep today:

Here is what Android's battary stats looks like:

And here is what is should look like and does look like on my 2012 Nexus 7, that is unaffected by this. And stats looks the same for a few days after I reboot my Nexus 4, before wakelock occurs again:

I have to assume that it has nothing to do with connectivity, because same thing happens even if I disable wifi and mobile data entirely.

Here is a list of topics about the same issue I could found, but they only have questions, not answers.

Android Police's review of 2013 Nexus 7: http://cdn.androidpolice.com/wp-content/uploads/2013/08/nexusae0_Screenshot_2013-08-02-16-14-17.png

XDA thread about another Nexus 4: http://xdaforums.com/showthread.php?t=2388072

Reddit thread about Nexus 4: http://www.reddit.com/r/nexus4/comments/1jk7bz/android_43_android_os_battery_issues/

Reddit thread about 2012 Nexus 7: http://www.reddit.com/r/Nexus7/comments/1jnoqu/2012_has_anyone_else_had_similar_problems_since/

UPD: one more thread about 2013 Nexus 7 http://xdaforums.com/showthread.php?t=2394813

UPD: one more Nexus 4 thread http://www.reddit.com/r/nexus4/comments/1kck8k/android_os_is_consuming_a_lot_of_battery/

Unfortunately, I also do not have any answers (yet). The purpose of this post is gather all the info I've found in one place, and maybe rise the awareness about this.

Update:

Ok. I had BetterBatteryStats on my phone for 30 minutes, and this whole 30 minutes PowerManagerService held wakelock itself. So, it safe to assume that it is an offender.
[Nexus 4 Q&A, Help & Troubleshooting] mlj11:
Hi, I saw your reply on this thread.

I read some speculation somewhere that the wakelocks might be caused by the device continually trying to poll for location, and apparently this behaviour could be corrected by the latest version of Google Play Services v3.2.25. I don't see the wakelocks now after upgrading to it earlier today, however this could also be because I rebooted my phone... Nevertheless I'm still not getting great screen-on time, just about 3.5 hours compared to other people's 5+ hours.

What's your version of the app? If you don't have 3.2.25 you can either download it directly (Android Police has put up a copy of the apk, but it might not be a Nexus 4-specific one) or download a more recent version of Play Store and wait for it to update Google Play Services automatically.

I'll report back here if I notice any more changes in my phone.
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
Location related wakelock are reflected in Android System and Google Services in the Android's battery stats, and as NLP (and some others) in the BetterBatteryStats. They account for about 1 hour of awake in a day. And they actually DO something.

This wakelock unfortunately does not show in Partial Wakelocks statistics in BetterBatteryStats, so I think it occurs somewhere deep in kernel.

If you use Google Now, or some other location based apps like Aviate, 3.5 hours of screen time is great. I do not turn off Wi-Fi, even when it is not available, use Google Now (without location history). 3 hours of screen on is what I expecting as a best case scenario.

Unfortunately, at days then 'Android OS' wakelock happens it nowhere near 3 hours.
[Nexus 4 Q&A, Help & Troubleshooting] mlj11:
So you're saying that location polling only affects "Android System" and "Google Services" wakelocks. Ok, I didn't know that.

But I did note that my "Android OS" wakelocks have now stopped. Although I cannot say whether the update to Google Play Services / Google Play Store had anything to do with it, or whether it was simply because I rebooted my phone. Do you know for sure that Play Services has no effect in this respect?

And yes, I do use Google Now and also Field Trip.

In any case, I'm also noticing that my battery drains at a much faster rate (as compared to 4.2.2) when I have my phone turned on.
[Nexus 4 Q&A, Help & Troubleshooting] Galaxo60:
Possible answer here:

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

Hope it helps.

:good:
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
It'll help with Google Services drain, I think. Anyway Google Play Services just updated for me (with Android Device Manager), hope it'll fix Android OS drain too. Hope is not high, though )
[Nexus 4 Q&A, Help & Troubleshooting] flintdragon:
I've recently have this issue as well with "Android OS". Luckily I can still make it through the day easily but annoyed this kind of stuff still happens. I got the latest Google Play Services yesterday and still have this issue today after a full charge. Will reboot and see what happens I guess.
[Nexus 4 Q&A, Help & Troubleshooting] steven676:
I've been seeing this on my Galaxy Nexus with AOSP 4.3 as well. It looks like this patch might be relevant: https://github.com/CyanogenMod/andr...mmit/e6771c41e8ae905a616f3fd369d0eacfcd2003b9
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
It looks relevant indeed. Although, I would not call the drain "rapid". I'm now looking close to my device statistics and try to pinpoint exact moment this lock occurs to find the cause.

If it is indeed caused by concurrent condition in PowerManagerService there is not much to do, but flash another, patched, ROM. But I eager to stay on stock.
[Nexus 4 Q&A, Help & Troubleshooting] morgante:
Also seeing this with my Nexus 4. Reboot doesn't do much at all for me.
[Nexus 4 Q&A, Help & Troubleshooting] nosch:
I was having the same problem with Android OS keeping my nexus 4 awake. It turns out the problem was using a wireless charger. If I wirelessly charged overnight my phone would never go into deep sleep when I took it off the charger. I went back to using the usb charger and the problem has gone away. I don't know if you are wirelessly charging but it did the trick for me.
[Nexus 4 Q&A, Help & Troubleshooting] xramonz:
confirm exactly the same trouble.

usb charger solves this problem for a while
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
It's documented problem about wireless charger https://productforums.google.com/forum/#!msg/mobile/c4HRzEUNmFk/geRlvQRtSPoJ

Looks like it was there since 4.2.2 and nobody cared to patch this in 4.3.

Unfortunately, it has nothing to do with my case. I do not own a wireless charger and the name of the wake lock is different. When it is related to charger it is PowerManagerService.WirelessChargerDetector keeps device from sleep. In my case it is less specific PowerManagerService.Wakelocks
[Nexus 4 Q&A, Help & Troubleshooting] max4wdc:
I have this issue i think maybe going back to 4.2.2
[Nexus 4 Q&A, Help & Troubleshooting] zerohunk:
I have the same problem of android os keeping phone awake on my nexus 4 .. I cant go back to 4.2.2 coz i face notification delay prob on 4.2.2 so i am stuck up with battery drain on 4.3 :( .. all os updates seem to have some or the other bug! really annoyed ... maybe i should have sticked to my htc one x+ .. atleast it dint hav any probs as such :(
[Nexus 4 Q&A, Help & Troubleshooting] Calebz:
I have been having the same issue . I finally dealt with it last night after flashing multiple ROMs and kernels. I went back to OTA 4.3/rooted/twrp and flashed from the updated .84 modem back to the previous .48 modem. Went back to only losing ~4% overnight. The problem appears to be the qualcomm modem driver. Additionally, I am mostly seeing this problem from people outside the US.
[Nexus 4 Q&A, Help & Troubleshooting] Heritz:
What I also tried, that didn't work at all, was stopping all running services during an Android OS wakelock. Even with all the services stopped and the RAM cleared, the wakelock didn't stop at all. So, it means the drain comes directly from the OS/drivers/etc, not any running app. In fact, after 2 factory resets, 1 reflash and keeping my phone completely stock for days, the Android OS wakelock kept occurring. Even if you don't sign-in into your Google account, the wakelock will still be there eventually draining all your battery.

I will have to give the old modem a shot.
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
So, somewhere here, on XDA, I read suggestion to clear cache (Settings -> Storage -> Tap on 'Cache' and then 'Yes') and then reboot.

I did this on Friday and to date wakelock did not return. I do not know did this really help. May be it was just a coincidence, or maybe this nasty wakelock will return, but this procedure is easy and harmless, so maybe it is worth to give it a shot.
[Nexus 4 Q&A, Help & Troubleshooting] jong31:
Same Problem

I just got my nexus 4 a week ago and I have been having this problem ever since I got it. It seems to be an issue for me no matter what rom/kernel/radio I flash. I've also tried complete factory image flashes of 4.2.2 and 4.3 with radio and it has no effect on this issue. I am very discouraged because I love this phone other than that problem.:(
[Nexus 4 Q&A, Help & Troubleshooting] sofratuzu:
Nothing else on the forums worked for me so as a last chance, i tried this solution and it worked. Well, sort of. I did this last friday and afterwards android OS battery usage dropped from around 25% to 8%. Also in Wakelock Detector, i saw that my CPU was no longer awake all the time. But unfortunately, as of this morning, problem reappeared. I tried to erase cache again but it didn't work.

Is this happened to you as well?
[Nexus 4 Q&A, Help & Troubleshooting] masterfunk:
similar issue

Hi all,

I just got the new nexus 7 and I'm have the same issue with it never going to deep sleep. I believe its due to a wake lock but I have not been able to find anything on this particuar program it is running. I've attached a couple screenshots. I've tried everything such as factory reset, rooting,turning all WiFi location and syncing off, and deleting cache and rebooting to no avail.

The only thing i havent tried is flashing a new rom because i would like to make that a last resort since this is my first android device and have no experience with it.

Any advice would be really appreciated. Overall I've loved the nexus its just very disappointing with this issue and the lack of support Google provides.
[Nexus 4 Q&A, Help & Troubleshooting] andrewf403:
No my Nexus 4 is still fine, but I continue to monitor it, it case problem returns.

On the other hand, looks like now my Nexus 7 (2012) may be starting to be affected by this problem :mad:
[Nexus 4 Q&A, Help & Troubleshooting] scherfa:
Same Problem here. Android OS is active all the time. Updated Google play service did not help. Turning off the service is only a temporary solution.. ?

I'm on stock rom. And I checked it last night with wake lock detector.. The system never sleeps.
[Nexus 4 Q&A, Help & Troubleshooting] rodrigo9411:
Im also having the exact same problem on the 2013 nexus 7, and the strange thing is that it was working flawlessly 1 week ago and out of nowhere battery drained. I've tried cyanogenmod and the problem continues, i also tried restoring the factory image and didnt work. I've tried 2 different kernels and nothing... will try Carbon rom and report back
[Nexus 4 Q&A, Help & Troubleshooting] Judge584:
If you see "PowerManagerService.WakeLocks", this means something is using "Partial WakeLocks". So look for Partial WakeLocks and you will see exactly what's going on.

More here , see section "test case" : http://software.intel.com/en-us/articles/wakelocks-detect-no-sleep-issues-in-android-applications
[Nexus 4 Q&A, Help & Troubleshooting] Heritz:
Are we all based outside of the US? I've been wondering if this is just a radio/driver problem related to the networks outside of the US.
[Nexus 4 Q&A, Help & Troubleshooting] ronin7:
Are there any news on this bug? Is Google even aware of it?
[Nexus 4 Q&A, Help & Troubleshooting] steven676:
There's nothing there as shown by "dumpsys power", yet PowerManagerService's internal reference count on that wakelock is greater than zero. That's one of the factors pointing to it being a bug in PowerManagerService.

For reference, I've been running AOSP with this patch for several weeks now, including periods of long uptimes, and have not experienced a recurrence of the bug.

Given that the above patch is by a Google employee and contains a reference to an internal Google bug number, I'd say so. I'm mildly curious as to where CyanogenMod got the patch from, though, because it's not in AOSP (if I had to make a guess, Qualcomm picked it up in the CodeAurora tree and CM pulled it in from there).
[Nexus 4 Q&A, Help & Troubleshooting] MadFinn:
I've found a dodgy workaround - so long as the phone is awake when you remove it from the charger it seems the wakelock doesn't occur.

If you remove it from the charger while it is attempting (unsuccessfully) to sleep, you need to unlock it and place it on the charger, remove it from the charger, place it on the charger (this time it will give the 'i'm charging' chime, the first time it didn't), then remove it from the charger.

Both of these seem to stop the wakelock from occurring when you are on battery, but don't stop the bad battery drain after the phone gets to 100% on the charger, rendering the charger... well, ... somewhat less than good.

Mine is a Nexus 4, hardware version rev_11 but with the rubber nipples on the back.

What hardware version are others seeing this with? There were some wireless charging fixes with rev_12 which resulted in better compatibility with the Nokia Qi chargers, so there may be some correlation to this bug.
[Nexus 4 Q&A, Help & Troubleshooting] riko540:
It seems to be severely different things. I have disabled the location access, back up and restore to Google servers and Google Now hot word detection. If I enable any of these the issue with the phone always being awake returns.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] anwedr:
I have this issue too. Android OS would keep wake for hours.

Location Report OFF did not do the trick.

Google Now disabled did not solve anything.

Greenify didn't do anything at all.

Now to test Wifi and Network Location OFF on 4.3 as I have that ticked since day 1 and had no issues when running 4.2.

I'm curious if the wireless charger is the culprit as some pointed out. I never had a problem on 4.2.2 when charging the device overnight via wireless.
[Nexus 4 Q&A, Help & Troubleshooting] SmXtrem:
SO having this nice wakelock since 4.3 :|

By me it only appear when the phone is charged to 100% and when i forget to remove it from charging in max 1h after it reached 100%
[Nexus 4 Q&A, Help & Troubleshooting] nemanja066:
SOLUTION:

Uninstall Viber. Works for me perfect! I don't wakelock a month ago :D
[Nexus 4 Q&A, Help & Troubleshooting] joshuab227:
I too have been facing the problem for a while now.

For me disconnecting from the charger / usb cable without waking the phone first seems to trigger it.

Just today I had connected my phone via USB to a laptop for a few minutes and disconnected it without first waking the phone. A few hours later I realised that my phone was not going into deep sleep.

A reboot always seems to remedy the problem.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] kermitdefroghere:
I'm curious about this.. Because my non sleeping may correlate to charging as well.

Just so happens I've been using a generic charger.

What kind of charger are you using?
[Nexus 4 Q&A, Help & Troubleshooting] joshuab227:
I'm using the normal wall charger that came with the nexus 4

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] ronin7:
This wakelock bug is really weird. My phone was fine for 2 or 3 days. Then I had to do a reboot and after that reboot I had the permanent wakelock again. When I noticed it I did yet another reboot which fixed that again. :eek:
[Nexus 4 Q&A, Help & Troubleshooting] harry_martini:
I think i found a workaround fot this bug just go to the wlan settings an set the standby option to never this solved the issue for me
[Nexus 4 Q&A, Help & Troubleshooting] laithmurad:
What works for me.

The only thing that worked for me is to reboot the phone whenever I fully charge it.
[Nexus 4 Q&A, Help & Troubleshooting] Dark Emotion:
Or just unplug your phone while your screen is on (device awake).
[Nexus 4 Q&A, Help & Troubleshooting] Jazavchar:
I also suffer from this problem and for me, the bug seems to appear spontaneously. It doesn't matter how I remove my phone from the charger, the wakelock will appear somewhat randomly.

Running stock 4.3, rooted with faux kernel and .84 radio. No luck.
[Nexus 4 Q&A, Help & Troubleshooting] RobertSand:
Same problem here, so annoying bug!! Hope some of you could find a fix.

Stock, only open bootloader
[Nexus 4 Q&A, Help & Troubleshooting] Indian03:
same problem

I'm having the same problem after getting the second 4.3 OTA update. Before it, I was getting great battery life. Now wakelocks are draining the battery... I had already planned to root relatively soon so I'm going to try a factory reset after backing up and hopefully that will work. Here are my strange stats:

Kit Kat better release soon (along with the Nex 5) and fix some of these things. A truly debilitating bug.

View attachment 2256177

View attachment 2256178
[Nexus 4 Q&A, Help & Troubleshooting] +SN BLSN:
Same exact problem on Galaxy Nexus. Reboot immediately solves but it always returns at some point,
[Nexus 4 Q&A, Help & Troubleshooting] DrakeSlayer:
No ****ing solution yet to this. Im having the same prob,hope itll go away with kitkat
[Nexus 4 Q&A, Help & Troubleshooting] AJ205:
count me in on this bug. on latest OTA stock not rooted N4 outside the US. i tried everything but it always comes back.
[Nexus 4 Q&A, Help & Troubleshooting] Kendaihou:
Any idea what the second one does? Is that Google sync stuff or something?

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] harry_martini:
Has Anyone a idea how to revert to 4.3 ( without the small update) without losing data ?