yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Infy_AsiX:
some decent insightful ideas here. My S3 on official stock based custom has bad drain over wifi. My google services framework version is the 4.1.1-438695 which isn't affected in your case so it's not that.

Better battery stats at first put google maps as the wakelock so I realised it's location service was left on so I turned that off. Then BBS varies and shows different apps and what not causing wakelocks but the drain remains the same.

My router is an Asus with custom linux firmware Tomato with a robust plethora of functions. I updated it yesterday and put the settings back closer to default. I'll have to try disabling WMM and QoS settings as their both already on at the moment. Also the kernel developer i'm on to quote: "Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets."

After leaving wifi on last night the drain still remains at about 10% per 3 hours. Compared to before it used to be almost 15% per 3 hours. BBS doesn't show wlan_rx_wake as the top wakelock as most common before as that's down to running for 8 minutes in 9 hours rather than the top around 45 minutes. Instead battery-monitor is the top at a little over half an hour in the 9 hours. Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.

I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
[Samsung Galaxy Nexus] jangutter:
Have you tried disabling the WiFi Power Save Mode on the S3? From this article:

http://www.s3forums.com/forum/galaxy-s3-general-discussion/1329-wifi-tip.html

1. Open up the Galaxy S3 phone dialer

2. Dial *#0011#

3. Look for the “ServiceMode” screen and press the left menu button

4. Select “WiFi”

5. You should see that the “WiFi Power Save Mode” button is “ON” – turn it “OFF”'

My colleagues with the same phone has serious battery drain until they use that.

I seem to recall that the Google framework sends/receives a keep-alive packet once every hour or so. LOTS of stuff in the Android framework keep TCP connections open from the server side because otherwise the service provider just kills them. Blame stateful firewalls.

What could be happening here is that the WiFi chip offloads a number of these functions from the main CPU: i.e. it's got a simple TCP offload stack that just queues data for the main CPU to wake up. If the WiFi chip receives a keep-alive TCP packet with no payload, it doesn't bother to wake up the CPU and just absorbs it. If the WiFi chip goes to sleep, rather, it never receives these, the connection dies and the CPU needs to wake up on timeout and re-establish everything (eating battery in the process). It's paradoxically cheaper to keep the WiFi chip running on full power, than to let it go to sleep. This is pure speculation, and only one of many scenarios that might fit the facts.

The S3 has the *option* to change the WiFi sleep-mode from aggressive (default) to a value that lets the entire system use less battery. The Galaxy Nexus doesn't: which means that it may, or may not have the sleep-mode built in. In any case, it seems my router can remotely trigger disconnects when the main CPU is off, and by switching settings on it, I managed to perform a workaround. Unfortunately the Galaxy Nexus (on Jelly Bean, at least) seems to have a serious bug in this respect, and other people are not so lucky: http://code.google.com/p/android/issues/detail?id=35352

It seems that the core issue (WiFi disconnect), causes a knock-on effect, raising Google Services Framework, Android OS and potentially anything that syncs's battery profile.

Jan
[Samsung Galaxy Nexus] Infy_AsiX:
Getting good drain now 1% an hour compared to 3%. Seems setting WMM to auto rather than enabled in tomato fixed it. The night before I had it disabled as well as QoS and it was bad as well. I will test further to be certain what's the scenario.

I've got a second S3 that's been suffering as well. Having two to test makes testing much faster. The service menu power save mode off didn't help. It caused strange disconnects with WMM in all states. S3 wifi menu would state poor connection and wouldn't reconnect. Note the S3 already has strange disconnects to begin with I find but in this case it sometimes wouldn't reconnect. Also restarting the phone resets the power save mode to enabled.

Can't find any information on a difference between enabled and auto in tomato WMM. I'll be sure to keep testing.

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] jangutter:
New Google Services Framework

Hey guys,

looks like Google Services Framework got a version bump on the latest Galaxy Nexus update: it's now listed as version 4.1.2-485486

This is for JZO54K (4.1.2).

It could be that they've fixed the knock-on effect (but the core issue is likely the same, since the radio code is apparently exactly the same).

Jan
[Samsung Galaxy Nexus] baknblack:
I have this same wakelock on my evo 4g lte. Same log error exactly. Only on my works wifi. Problem is eliminated when running a Vpn on the phone. Only caveat Is all the free vpn services seem to disconnect after a period of inactivity. :(
[Samsung Galaxy Nexus] Rawi666:
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.

After weeks of searching and trying different things I found the solution.

Change DTIM value in your router configuration from 1 (default) to 255.

This value is usually in Advanced->Wireless tab on most routers.

Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
[Samsung Galaxy Nexus] SpinTX:
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
[Samsung Galaxy Nexus] Rawi666:
Try lowering this value to 10 or 8 and see if it helps.
[Samsung Galaxy Nexus] SpinTX:
Thanks, will give it a shot. Also, because of your post, I discovered that toggling wifi on and off stops Google Services from draining. It will still drain, if your wifi is set to turn off, when the device sleeps. I really think you hit the nail on the head, discovering the source of the problem. It's an issue I have been trying to fix for a long time and your post at least got me to toggling the drain. So thanks again!
[Samsung Galaxy Nexus] croach246:
Would love to he root cause of this... I had the same problem on my s3 and now on the s4.with and without custom roms etc. The problem only is work, and I'm putting it down to some service that the work firewall or something blocks... Only solution I've come up with is turning off the wifi when I'm at work.. Else I get in excess of 15min /hour of wakelock.

All apps etc. Up to date, sync on/off, no difference, all "location" settings turned off.

I give up.
[Samsung Galaxy Nexus] keltickal:
Wifi signal strength!

Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.

Kal
[Samsung Galaxy Nexus] croach246:
A friend with the nexus 4 and same problem told me to try disabling Google hangouts (formally talk).. Apparently it keeps refreshing itself once ur signed in (and it signs in automatically)... Will experiment tomorrow at work where I get the problem.
[Samsung Galaxy Nexus] jangutter:
Multiple causes...

Hi, as the original poster, I'd just like to share again what I found out about this battery drain issue.

I think we've all traced back the problem to the wireless stack, then gotten lost. Basically, we KNOW that the long-standing connections that Google makes tend to break on certain Wifi access points. This has nothing to do with firewalls or anything layer 3 and up (keep in mind, there might be other broken systems where this is the root cause. This case is only when you've eliminated that possibility.)

My working theory (and it seems to fit the facts) is that Android switches on "Wifi power-save" by switching OFF the CPU IP stack and transferring the IP stack to the Wifi chip. This is similar to how "segment offloading" works in lots of modern network cards. So, the CPU does not need to be awake to keep the TCP sessions going, the Wifi chip keeps it going.

Well, you can ask any kernel developer, but what sounds good in theory turns out to be horribly broken in practice quite often. Offloading an entire TCP/IP stack is rarely 100% bug-free and I think we're hitting some very specific bugs here.

For certain settings on the Wifi access point, the firmware on the Wifi chip loses connections. This causes the Google Services Framework to wake up the CPU, re-establish the connection and generally waste a bit of battery. When the CPU goes to sleep again, the Wifi chip takes over. Wifi chip loses connection and the cycle repeats.

When the Wifi chip is well-behaved, this doesn't happen: the chip keeps the connections going and wakes up the CPU if data comes from outside.

Now the bad news: Google, Samsung and the Wifi chip vendors are hilariously bad at doing the right thing. EVEN if it's possible to fix the firmware, there's absolutely no incentive for them, they'd rather sell you a new device. This is one of the many drawbacks of firmware blobs and Google deciding to just dump all sorts of crappy mods into the Linux kernel. Android userspace is pretty much tied into this model and I can guarantee there's going to be no software fix to this. Chances of this getting fixed by Google is zero, because they don't have access to the code. Chances of this getting fixed by Samsung is zero, because they don't have access to the code. Chances of this getting fixed by Broadcom is zero, because they'd rather sell you a new chip.

If you hit on the right combination of settings on the AP that stops the chip from disconnecting, or if you manage to disable "Wifi power save mode" on the chip (thereby using more CPU to maintain the connection, but NOT dropping it) you might be able to fix or mitigate the issue.

There are no good OS'es anymore...
[Samsung Galaxy Nexus] Roodyy:
Thanks OP for following up on this thread. I'm a Nexus 4 user and just did some googling on the topic and came across this thread after having a similar behavior with GTALK_ASYNC_CON... showing thousands of wakelocks while I'm connected to Wifi at work.

I'm going to see what happens by simply turning Wifi off then back on when I get back to work next week. If this yields better results then I'll probably just use Tasker to do this for me once every few hours.
[Samsung Galaxy Nexus] tcat007:
Have the same exact issue with my Nexus 7 (wifi only, 4.3). Wifi on at work I get about 10% drain in 6 hours; wifi on at home I get about 40% drain in 3 hours. Screen off 90% of the time in either case. Must be either home router (WRT54G) or cable modem (SB6141).

Be nice to find "the answer". I have VOIP at home so can't mess with DTIM setting much or voice will go bad. I need to look at work settings to see how it's set, but my gut says it's my cable modem since it's a few weeks old and this started a few weeks ago.
[Samsung Galaxy Nexus] tommy.:
Hi guys, i had the same problem. Google seevices was eating everythin. After couple of tests, i fugured out that Google now was causing the problem. I turned it of from its menu and i've charged my FLO on 100% so I can look at a reseted graph. Without the Now, the devices is doing 4 days with wifi and couple of hours of browsing and reading. I have also noticed that Now is also disabled on my phone as well because of the sync. It is htc one x and is doing a little bit better than before I think, but nothing compared to the nexus improvement! Hope some of you can solve the problem in this way.
[Defy Q&A, Help & Troubleshooting] ejlmd:
I'm trying to discover the SPC/MSL for my Defy XT557 (Republic Wireless) in order to obtain root. Can flip the phone into DIAG mode using SUT LR and open a COM port, which is then recognized by CDMA WS and DFS cdmatool, but cannot even obtain a successful memory scan or dump using those programs. Radiocomm gives a green circle but no RDELEM hex readout. getprop ril.MSL readout is empty, and alogcat while entering diagnostic phone codes does not show the MSL.

Any ideas would be greatly appreciated.
[Defy Q&A, Help & Troubleshooting] Aragorn450:
So I'm thinking at this point that we should wait for the OTA in January and then we might be able to piggyback onto that... Obviously the update will be signed, so we won't be able to modify and then apply it but... we might be able to log enough of the process that we could get lucky and get the info we need to hack this sucker.
[Defy Q&A, Help & Troubleshooting] krazies:
has there been any progress in the XT557...
[Defy Q&A, Help & Troubleshooting] kratt:
How do you get the phone into diag mode using SUT LR? I have installed SUT LR and it detects a phone, but I don't see how to open a com port. I checked the device manage and it only had COM1. Thanks for your help.
[Defy Q&A, Help & Troubleshooting] 3a4yI7aTiY:
How do I put my Defy XT in DIAG mode? sut lr not detects phone...
[Defy Q&A, Help & Troubleshooting] 3a4yI7aTiY:
how you get diag mode with SUT LR???
[Defy Q&A, Help & Troubleshooting] ejlmd:
Sorry, I no longer own the phone. But in any case it seemed like a dead end.

The following was posted on one of the Republic Wireless forums regarding obtaining carrier info from a rooted Defy XT 557:

For anyone trying to get information from CDMA Workshop or get info DIAG mode, you can gain access by doing the following:

change the value of /sys/class/usb_composite/diag to 1

I did this using root explorer and edited the value using text editor.

you can then connect without SPC and click read to view most settings (probably enough to cl*ne if wanted).

It also looks like data in the NV Dump file showed data connection info of:

YOUR_HEX_MEID@hcm.sprintpcs.com

hcm.sprintpcs.com
[Galaxy S II Q&A, Help & Troubleshooting] Sizuke:
Hi im sorry in advance for my noob question but here what im trying to achieve i hope someone can help.

Im using a CM10 nightly build and i am wanting to add a few wallpapers to the default system ones, i know you can just put them anywhere and have them that way but what im trying to do is to have them so that they selectable from the default ones and not show on gallery etc.

So where about is the directory where these are stored if there is such thing and if there isn't one how do i go about doing it.

And search on google and did a forum search and could find anything.

I like to put them in the Wallpapers not Cyanogenmod Wallpapers

Many thanks in advance

Regards
[Galaxy S II Q&A, Help & Troubleshooting] saywhatt:
You can try Root Explorer to push the files to its system ;) hope this helps!
[Galaxy S II Q&A, Help & Troubleshooting] Tefanym:
JB ? Well try this huge wallpaper pack and it's an installable apk .. To select a wallpaper just menu wallpaer and select neutrino wallpapers

http://xdaforums.com/showthread.php?t=1830506
[Sony Ericsson Xperia Neo, Pro] tujamo1:
The Xperia S apps will work on stock .587 ? Or notification pannel ?
[Sony Ericsson Xperia Neo, Pro] salsreloded:
Yes because it's still 4.0.4...
[Sony Ericsson Xperia Neo, Pro] tujamo1:
Those who updated to new .587 firmware update didn't dare to install Mods from XDA which includes 'Framework'... Otherwise u'll get Bootloop!
[Sony Ericsson Xperia Neo, Pro] darn02:
I'm on .587 and I've installed both toggles and walkman mods and I have no problems, so I'd say its safe, just make a backup first.
[Sony Ericsson Xperia Neo, Pro] jeopardise:
I've tried XS Lockscreen mod involving changing the framework file and got bootloop/stuck at boot screen.

Walkman, Toggle and Home mods seems to work just fine
[Sony Ericsson Xperia Neo, Pro] geondut:
Do u use walman mod for pureness 11?? Last time I tried it on (stock) older build of ICS 4.0.4 and get error on setting, cannot create apn so I cant connect to internet, and also it always FC every 10 seconds.. I want to try again in 587 but Im afrait it'll be the same as the older one..
[Sony Ericsson Xperia Neo, Pro] samxsam:
Walkman mod for ICS neo v

Don't use the walkman mod from Pureness11, instead use the Walkman app from these threads, these both are working perfect in ICS version of neo and neo v.

knight47 walkman mod: http://xdaforums.com/showthread.php?t=1734627

Thilinac walkman mod: http://xdaforums.com/showthread.php?t=1681256

Please hit thanks if this helps you.:p: fingers-crossed:
[Sony Ericsson Xperia Neo, Pro] darn02:
Basically what SamXSam said, I used pandemics toggles and Thilinac's walkman mod.
[Sony Ericsson Xperia Neo, Pro] SSyar:
Notification Toggle http://xdaforums.com/showthread.php?t=1534903 is working on 0.587.. i have installed the PART C

did any one tried...! Thilina's walkman.. http://xdaforums.com/showthread.php?t=1681256 !! on 0.587 ?? which update is working !! ??

---------- Post added at 12:46 PM ---------- Previous post was at 12:25 PM ----------

http://www.mediafire.com/?vhhh8tpb18b796h THIS Xperia S keyboard is also working on 0.587
[Sony Ericsson Xperia Neo, Pro] Pandemic:
i installed thje walkman on 587 on my neo v, but the beats.apk is missing but ThilinaC put it in a attechment in general chat install that with root explorer reboot and all works fine ;)
[Sony Ericsson Xperia Neo, Pro] SSyar:
which update u install .. !! and can u give me the link..! of that beats.apk..

is it beats.apk for dr dre..!! its not necessary ... !! i will work fine. if not installed
[Sony Ericsson Xperia Neo, Pro] geondut:
Nice... haha I really love walkman player.. thanks bro
[Sony Ericsson Xperia Neo, Pro] Pandemic:
here:

http://xdaforums.com/showpost.php?p=31323986&postcount=2044

Beats.apk

and i installed just the u7 from ThilinaC on 587 ;)

this one:

http://xdaforums.com/showthread.php?t=1681256
[Sony Ericsson Xperia Neo, Pro] geondut:
which version of thilliana walkan do u use? is it u4 (older one)?? cos I've tried u6 and 7 on .587 but gets some error... :(
[Sony Ericsson Xperia Neo, Pro] Pandemic:
What do you think?? U7 mate and what kind of error?

sent from my Xperia Neo V with supercharged 587, do you have that? i hope not xD
[Sony Ericsson Xperia Neo, Pro] 3kay945:
supercharge

How can iI get this supercharger on my neo v. assist me and iI will hit thanks button 20times.
[Sony Ericsson Xperia Neo, Pro] Pandemic:
I replied in general chat, you can also click in my signature on sticky thread and my projects but you can also search;)

Dont be to lazy mate, and read good in the v6 supercharger thread:)

Hahaha you cant hit thanks 20 times, that is not possible for a junior;)

sent from my Xperia Neo V with supercharged 587, do you have that? i hope not xD
[General Topics] dashingd:
Mobile Internet Banking in india is still a pain because of regulations by RBI.

Before every transaction user needs to generate an OTP from different sources such as SMS / IVR / internet.

This SDK is for the developers to generate the OTP for the users so that user doesn't need to leave your application. SDK is free and suggestions are open.

Try it out.

http://openotp.in

Its way simpler than using fbconnect in your app.
[Nexus 7 Q&A, Help & Troubleshooting] juanito05:
Good day XDA. I just noticed that my N7 is having problems with its accelerometer. I was playing temple run and mutant road kill and the characters always veer to the right.

Question is: is this a software or a hardware issue?

also, is there a fix/app if this is indeed a software issue?

thanks
[Nexus 7 Q&A, Help & Troubleshooting] Raisone:
well, i know that there is apps for calibrate the accelerometer, i can´t remember now the name, sorry, but i´m sure that you can find it on the market o google.

Anyways, did you try in diferents places? i mean, maybe the surface where you try wasn´t flat...
[Nexus 7 Q&A, Help & Troubleshooting] juanito05:
thanks for the reply man.. anyway, i already found a way to fix it and it's been holding up.
[Nexus 7 Q&A, Help & Troubleshooting] espionage724:
What's the fix?
[Nexus 7 Q&A, Help & Troubleshooting] RockNrolling:
What did you do to fix the issue?

Sent from my Paranoid Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] juanito05:
well first you have to confirm that you indeed have the gyro/accelerometer problem. you guys could download an app for that (i used Android Sensor Box). once that is confirmed, download the app "GPS Status". Run it and go to tools, then calibrate pitch and roll and just follow the instructions. I suggest you guys do this while your device is lying flat on a surface.

after trying this fix, i uninstalled GPS Status, rebooted my device and it held up. played temple run and the character started right smack in the middle lol. also tried checking the sensors using Android Sensor Box and it was calibrated. i just reinstalled GPS Sensor just in case i might need it down the road but im hoping this fix will be permanent. if it isnt, im pretty sure that this is a software problem and an update could give a permanent solution.

let me know if you guys get the same result i had with this.

Thanks :)
[Nexus 7 Q&A, Help & Troubleshooting] joelhon:
That was amazing man. I have been swearing over this accelerometer issue ever since I got the device, and now it's perfect. :beer:
[Nexus 7 Q&A, Help & Troubleshooting] Del_Bryan:
Had exactly same issues on all three units I have purchased. GPS Status app does fix the problem. Thanks for the solution.
[Nexus 7 Q&A, Help & Troubleshooting] Alex240188:
GPS status did nothing for me.

Same problem veering to the right

Held n7 landscape

Reboot

After reboot accelerometer is working fine

Sent from my Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] reef2009:
This didn't do the thIng for me neither

But I did the job like this.

Open an app that uses the compass. You can use GPS Status, Android Sensor Box or whatever app you like that uses a compass.

twist/turn your device 3 times around each of all the three axes

FINISH

Even after a reboot it works great.

But if you flash a new rom this fix will be broken :(
[Android Q&A, Help & Troubleshooting] loveweijia:
i have got a meizu MX 2-core android phone,but there are some problems on rooting and unlocking the bootloader.

meizu is a small chinese android smartphone producer,it has produced mx 2-core and 4-core both have an chinese version and hongkong version.Both of the mx are running the flyme os,and the latest version is flyme 1.0.5 for chinese version and flyme 1.0.3 for the hongkong version.

1.chinese version

meizu has locked the bootloader,and also it prevent customers rooting the phone.

2.hongkong version

it can be rooted but the bootloader is locked as well.

i have heared from a administrator of an android forum called jifeng(bbs gfan com) that there are many skilled guys here.so if anyone can give our chinese users a hand? Please hlep us to root the mx 4-core and 2-core of chinese version.If some one can unlock the bootloader,that must be appreciated by all of the chinese users.

FIY:en meizu com and ,here u can buy a hongkong version: meizumxon com and ,if u want to get a chinese version mx ,please PM me!or my e-mail:loveweijia@163.com

thank you very much!

ps:

i am a chinese user,so my english is ralatively poor.i wish my description might help some great guy understand the current situation.
[Android Q&A, Help & Troubleshooting] AJ88:
So your device is running on android os or flyme os?
[Android Q&A, Help & Troubleshooting] loveweijia:
thank you for your attention!

it's called flyme os, but this os is based on android 4.0.meizu company has used some encryption mechanism to lock the bootloader and no one can root mx 2/4-core chinese version.