• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Atfw-deamon KILLING battery

Hey lightsleeper23,

I received a nice heads-up from iowabowtech, too, and did a little searching.

There is precious little published documentation about this daemon / process that you are referencing. The peripheral references I've found seem to indicate that it's related to one of the radios (that's not for sure, though) and possibly that it's related to processing the "AT" commands that are forwarded (again, not confirmed).

I've found one other post on XDA that mentions the same issue you are experiencing:

http://forum.xda-developers.com/showpost.php?p=12410546&postcount=4130

No resolution there, I'm afraid.

If you were rooted, you could probably disable that daemon (and it sounds like a reboot temporarily fixes it).

Since there's no public source for this daemon, I can only conclude that it is indeed part of the manufacture's proprietary drivers or firmware and probably is very much specific to your device or your manufacturer.

Wish I had better news to give you...:(.
 
Well thank you for the time you've put into researching this for me. I truly appreciate it.

Although I'm still not sure why my thread must be relegated to this very unpopulated corner of the forums. Considering the issue is present on other devices and some of their owners may have run into it and perhaps had some insight to provide about what the process does. Oh well.

i moved your thread back to the android lounge as per requested.
 
Hey lightsleeper23,

I received a nice heads-up from iowabowtech, too, and did a little searching.

There is precious little published documentation about this daemon / process that you are referencing. The peripheral references I've found seem to indicate that it's related to one of the radios (that's not for sure, though) and possibly that it's related to processing the "AT" commands that are forwarded (again, not confirmed).

I've found one other post on XDA that mentions the same issue you are experiencing:

http://forum.xda-developers.com/showpost.php?p=12410546&postcount=4130

No resolution there, I'm afraid.

If you were rooted, you could probably disable that daemon (and it sounds like a reboot temporarily fixes it).

Since there's no public source for this daemon, I can only conclude that it is indeed part of the manufacture's proprietary drivers or firmware and probably is very much specific to your device or your manufacturer.

Wish I had better news to give you...:(.


Hmm. But even the post you linked to was referring to an Experia device. And i found this
http://androidforums.com/spectrum-all-things-root/592032-updated-8-8-12-breath-fresh-air-update-10.html#post5059244

In reference to an LG Spectrum. I have also seen threads on xda mentioning the atfwd-daemon in reference to a custom rom for a Galaxy Nexus. So it definitely does not seem specific to my device or manufacturer. It seems to be a type of android code software that may not be used in all devices, but definitely in quite a few. The theme seems to be that it is related to AT commands. I cant say I know what an AT command is, but in all the references I've seen to this process, people seem to be complaining about it "draining their battery", or "going crazy", so whatever this is it does not seem like a good thing.

I don't know how it would get into custom roms, I'd be interested to know where they were ported from. Or if it is something that is present in base android or linux coding that just gets aggravated in certain roms. Although my vanilla android nexus does not have the issue.
 
Hmm. But even the post you linked to was referring to an Experia device. And i found this
http://androidforums.com/spectrum-a...2-breath-fresh-air-update-10.html#post5059244

In reference to an LG Spectrum. I have also seen threads on xda mentioning the atfwd-daemon in reference to a custom rom for a Galaxy Nexus. So it definitely does not seem specific to my device or manufacturer. It seems to be a type of android code software that may not be used in all devices, but definitely in quite a few. The theme seems to be that it is related to AT commands. I cant say I know what an AT command is, but in all the references I've seen to this process, people seem to be complaining about it "draining their battery", or "going crazy", so whatever this is it does not seem like a good thing.

I don't know how it would get into custom roms, I'd be interested to know where they were ported from. Or if it is something that is present in base android or linux coding that just gets aggravated in certain roms. Although my vanilla android nexus does not have the issue.

Yeah, saw a bit of all that stuff myself :p (and I'm sure IBT did, too :)).

Drivers and such like that make it into custom ROMs because devs have to copy/transfer the proprietary driver files from a stock ROM since they don't have access to the source in order to recompile. At least in a custom ROM or root device, you'd be able to disable the daemon or remove it from the ROM build (at least that's what other's seem to have done when in the threads that I've read).

In the "old days", there were Hayes modem "AT" commands for the dialer to set / change various settings in the modem (baud rate, etc.). Perhaps these functions have survived to the current radio interfaces for some devices? Dunno.
 
Just wanted to add to the OP's view that this is a widespread problem. I had the same problem, with ATFWD-daemon spinning the CPU at almost maximum for 5 mins or so.
I worked around the problem by powering off the device, and restarting. GIven that I have the 'fast boot' option enabled, this took maybe 10 secs in total, so not a big deal.
I use a Huawei G300 with Android 2.3.6.

The ATFWD-daemon process is definitely related to radio. I cannot post a link (new to the forum), but search for 'init.mako.rc' in the 'android-source-browsing' project (device: lge mako) on Google Code (Git SHA: fefe23cb22e5), you'll find this code at line 491:

[HIGH]
service atfwd /system/bin/ATFWD-daemon
class late_start
user system
group system radio
onrestart /system/bin/log -t RIL-ATFWD -p w "ATFWD daemon restarted"
[/HIGH]'group system radio'

Other forum posts suggest that this daemon is legacy or old.
 
Hangouts Update could be responsible. I used google Play to open My Apps Select All Aps Hangouts Uninstall Update {touch bottom touchscreen for menu option to deselect Auto Update feature. Luck -HH
 
Back
Top Bottom