[Q] Can you identify this logcat process - Thunderbolt Q&A, Help & Troubleshooting

I/htcfs-manager( 6488): loadProxy(), type=oma-drm1-fs, lib=liboma-drm1-fs.so
I/htcfs-proxy( 6488): HtcFSProxy(void *proxyHandle=0xb000f9cc), entry
I/htcfs-manager( 6488): putProxy(), ok
I/htcfs-main( 6488): main()
I/htcfs-main( 6488): ############# HTC FS - START ##################
I/htcfs-main( 6488): ############# HTC FS - END 1 ##################
I was checking out logcat because my phone was chewing through the battery. It was not going to sleep. I noticed this htcfs process pops up every 5-10 seconds. Each time it has a new PID .... Any clue what this is?
I have since rebooted and battery use returned to normal but this process is still popping up every 5-10 seconds and this can't be helping our battery life out.
Check your logcat ... this happening in other HTC Roms / Rooted / Stock?
Solid 4G coverage
Radio: 1.16.00.0402w_1
Rom: Bamf Stripped
Full Factory reset /wipe prior as I was coming over from CM7.

I also have the same thing showing in my logcat happening every 6 to 7 seconds with a new PID. Wonder if this is something we could track down and disable to see if it helps with battery life at all?
Solid 4G coverage
Radio: 1.16.00.0402w_1
Rom: Bamf 1.7
Full Factory reset /wipe prior as I was coming over from CM7.

feedhead said:
I/htcfs-manager( 6488): loadProxy(), type=oma-drm1-fs, lib=liboma-drm1-fs.so
I/htcfs-proxy( 6488): HtcFSProxy(void *proxyHandle=0xb000f9cc), entry
I/htcfs-manager( 6488): putProxy(), ok
I/htcfs-main( 6488): main()
I/htcfs-main( 6488): ############# HTC FS - START ##################
I/htcfs-main( 6488): ############# HTC FS - END 1 ##################
I was checking out logcat because my phone was chewing through the battery. It was not going to sleep. I noticed this htcfs process pops up every 5-10 seconds. Each time it has a new PID .... Any clue what this is?
I have since rebooted and battery use returned to normal but this process is still popping up every 5-10 seconds and this can't be helping our battery life out.
Check your logcat ... this happening in other HTC Roms / Rooted / Stock?
Solid 4G coverage
Radio: 1.16.00.0402w_1
Rom: Bamf Stripped
Full Factory reset /wipe prior as I was coming over from CM7.
Click to expand...
Click to collapse
You cant disable that, lol. What you are seeing is a vital application on the phone. htcfs if you didnt guess what it meant, means HTC file system and controls reading/writing/mounting/other filesystem related things for the htc framework. You remove/kill that, you're going to screw up your phone bad. Your phone has issues due to something else (like what you installed on your phone app wise).
If you dont give more details (like what you have currently running/installed that uses media), that's about all I can say (like worrying less about htcfs and more about what it's calling to (loadProxy(), type=oma-drm1-fs, lib=liboma-drm1-fs.so). That looks like it's calling out to the omx media libraries' drm crap. Most likely it's just some crappy application you have installed though, but cant say without more of a logcat dump than a few lines.

2mins of logcat with phone idle & screen off
http://pastebin.com/WLCfU48i
ps |grep app
http://pastebin.com/FPKaWhqK
I suppose that next full wope I can install apps one at a time to test.

feedhead said:
2mins of logcat with phone idle & screen off
http://pastebin.com/WLCfU48i
ps |grep app
http://pastebin.com/FPKaWhqK
I suppose that next full wope I can install apps one at a time to test.
Click to expand...
Click to collapse
offhand, i cant see anything on your app list that would stand out. list seems kind of short though, are you sure that's everything in /data/app and /system/app?
When i was reading into the netflix issues on froyo (this is totally unrelated, but just random info I picked up) that froyo used to have issues with DRM working correctly in libstagefright (the frontend to the media framework). Something about it wanting to constantly scan for media on your phone even if you didnt have anything requiring DRM. Anyways, I did search similar to http://www.google.com/search?client=opera&rls=en&q=froyo+drm+issues&sourceid=opera&ie=utf-8&oe=utf-8 if ou want to poke around. Those issues were supposedly fixed though, so don't take that as what is wrong for sure. I haven't seen this in my logs when I've browsed so far so it's an isolated issue for some it seems.
I know adrynalyne had disabled DRM in his kernel at one point and you could still if compiled it from the source and removed it beforehand (he had a guide to how to compile in the dev section).
Anyways, no absolution solution yet, but those are all I can think of offhand. Could try a full data wipe I suppose.
Post back whatever you figure out and I'll see what I can make of it.

Decided to wipe tonight and loaded MR2 radio and Flyweight Mod.
Let Marker restore what apps it wanted to and watched logcat and no sign of htcfs at all thus far.

Related

GPS Lock Problems after upgrade.

I was getting 15-20 second gps locks when I had radio .40 and DCD 3.2.6, but as soon as I upgraded the radio and DCD then it's taking like over 7-9 minutes to get a lock. Sometimes it won't lock at all anymore unless I do a hard reset on the phone. I'm not sure what happened. Does anybody have any ideas? Look at my signiture below for my current configuration.
What's the best Radio and ROM to use right now with the least amount of problems, etc.? I was looking at the V2.2 heavy and light, but I'm not sure if I really understand much about what they are about or the differences in what I have now. I think my biggest problem is with text messaging. If I do it a lot I have to keep restarting my phone because the memory goes down to zero in no time at all. Infact, I have to keep constantly clearing the memory if I use any programs at all. Thanks for your help and time!
Try either 3.3.4 or 3.2.6. I prefer 3.3.4
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Well, in the past it kept all the information after I did the upgrade, so I just assumed it still did. I didn't need a new A-Key. I guess I'll check the QPST settings and do the aGPS fix again. It's been so long ago since I did all the GPS stuff I can't remember what I did and didn't do. I still do get locks but they take forever now and sometimes I don't get them until I restart the phone.
Why are you sticking with 3.2.6? Why don't you like 4.1.2 or 2.2 heavy or light? I've always had the memory problem where if I use programs it just eats up my memory and I don't get most of it back after exiting the software, and if I use my text messaging then my memory just goes down to zero in no time flat and I can't recover it unless I'm constatly restarting my phone. There must be some kind of fix for this. Please let me know. Thanks.. Steve
kflipproductions said:
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Click to expand...
Click to collapse
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it.
Click to expand...
Click to collapse
Are the changes in the AGPS thread?
yes they are
Oh, really? Then that's probably part of the problem. I changed them maybe a year ago or longer. I tried running QPST to check and it's giving me an error message when I start it, so I'm going to have to try to reinstall it and see if that fixes it. Also, the links for the pictures are dead and they aren't coming up anymore, it makes it harder to figure it out.
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
I ran the Serf Telus aGPS Provisioning CAB file and that seemed to help. I sometimes get locks under 1 minute now, but sometimes it won't lock at all and I have to keep soft booting the phone to get it working.
Oh, so that's why my phone keeps resetting? It's not hard resetting I think it's just soft resetting. At first I didn't like the unread text message thing, but now I do because I get a lot of text messages and when I go to read them it doesn't mark them all as read in the group and I can read them when I get a chance.
I still had the memory issues with the 3.2.6 ROM with my memory going down to nothing, especually when I did text messages, I had to keep restarting my phone. That's been a problem I had with all my ROMs. I wonder why that is? Could it be the version of the MMS software I'm using? Is it the latest version?
Maybe I should go to the MR1 ROM? I still will be able to use the GPS and the WiFiRouter software with it right? Maybe that will solve all my problems? What about the 2.2 light and heavy ROMs? Does anybody know anything about those? Thanks for your help and time...
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
Click to expand...
Click to collapse
Well, I uninstalled QPST and reinstalled it and it worked this time without any error messages. It seems if I don't use it for a while it gives me a error message if I try to use it again and I have to uninstall it and reinstall it and then it works OK. I don't remember the error message, but I think it's something about can't find a server or something.
Anyways, you were right about the information I had being old and not correct. I had 66.174.95.132 and 8888 instead of PDE IP Address: 216.198.139.92 and PDE Port Number: 8889. I corrected it and it still seems to take about 56 seconds to get a lock, but hopefully now it will be more reliable in getting the locks. I seem to remember in the past getting locks in less then 10-15 seconds, and I wonder why I can't get locks like that anymore.
Thanks for the help!
Well, I was wrong, I'm getting 15-20 second locks now and I'm getting twice the satalites, up too like 9 satelites and I was getting 1/2 that before and it's a lot more accurate now. Before when I was using Google Maps, I could see it was off like about 50-75ft, but now it's spot on, on my location. Hopefully someone knows the answers to some of my previous questions and can get back to me. Thanks..
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
DustinEarnhardt said:
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
Click to expand...
Click to collapse
I just upgraded to the v2.2 light. I think I'm going to have to get use to it because the interface is so different, but I got a GPS lock with my TomTom GPS software in about 4 seconds. I couldn't believe it. I haven't seen a lock that fast before. It's really awesome! LOL

Radio: No Signal

My installation has been working fine and I even managed to increase battery life by installing "Juice".
Suddenly, about 3 days ago I noticed the phone was saying no signal. I was clearly getting data, as my apps worked and I was getting eMail alerts and downloads, but no calls.
I tried restarts, but to no avail. I am using Rod_100 UK as I am on Vodafone UK... I assume it is correct, certainly worked for the past month.
I have had to revert back to Windows Mobile.
My immediate thoughts are it is Juice that is causing it. I have just logged back in to my XDAndroid to write this and Juice did not load, and guess what, the signal has come back.......
Just in case is there anything else to look for?
Never heard of "Juice". I have heard of JuiceDefender however...
If you don't have the issue on a clean install, I'd say that app (or one of many I'm assuming you have installed) is the culprit. Rename your data.img and boot, see what happens.
Yes, it is JuiceDefender, apologies for the abbreviation.
I un-installed it and I have network again, but I guess I will loose battery longevity again, not that it made a huge difference.
I'll keep my eye on it....
Still no improvement
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
I dont know what exactly but some program is giving android problems
jonners59 said:
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
Click to expand...
Click to collapse
All I can say is do the standard mess.
Make sure you're up to date.*
Delete (move, rename) data.img.
Format SD. Full format. HP tool.
*There's a lot of testing stuff flying around right now too, making that difficult admittedly. Hopefully the auto-build service will return soon, and all the madness will get committed soon!
Check in your startup file forcecdma=0. I had that problem too.
wormy315 said:
Check in your startup file forcecdma=0. I had that problem too.
Click to expand...
Click to collapse
The command is force_cdma=X....
arrrghhh said:
The command is force_cdma=X....
Click to expand...
Click to collapse
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
jonners59 said:
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
Click to expand...
Click to collapse
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
arrrghhh said:
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
Click to expand...
Click to collapse
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
jonners59 said:
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
Click to expand...
Click to collapse
What is not "Executable" any more... haret.exe?
The startup file
Sorry, ignore me.
After the change, I double clicked the Android shortcut to launch Android, but it would not start, so I assumed the file had to be executable (as it was the only item I had changed)... I had forgotten to disconnect my TP2 from my laptop!
I've done so now and it has launched. A stupid user errorhttp://media.xda-developers.com/images/smilies/biggrin.gif
I'll keep you posted on any changes.
Ha, fair enough. Enjoy.
Solved. Keep loosing Radio
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
jonners59 said:
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
Click to expand...
Click to collapse
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
jonners59 said:
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
Click to expand...
Click to collapse
Hrm, didn't realize that app would help out that much. But, it makes sense if it's turning off all your radios lol.
Anyhoo, have you seen the kernel I posted from WisTilt2? It has full panel collapse, and battery life is astounding with it.
Code has yet to be committed, as he still has some work to do for the AUO panels (select RHOD100's basically) - so unless you have one of those you can reap the benefits of his new code .
(bzo got nearly 65 hrs with the radio on, sync off - 100% sleep.)
Looks interesting, but where do I download the latest version... I don't plan reading all the threads! And IF I installed would I loose all my settings and apps?
Update
It has been a while since I did all this tinkering, during which time there has been an update.
What I find I get is sometimes (c every couple of days) the meter says I have signal but nothing connects with a message "no network". Also, but far more frequent, as with today where it has occurred 3 times, I dial a number and nothing happens. It says ringing but there is no ring tone and it never seems to connect. I then shut the call down either by using the hang up button or the soft hang up key. The screen then changes to "Hanging Up" but again sits there indefinitely. The only solution id to do a restart.....
Any ideas?
PS: any news on when the bluetooth and camera will be working...?
I have found that any app that acts as a task killer of any sort (juice defender must in someway stop apps to save battery) can also kill your connection. I found this out while using xdandroid and it became immiediately clear when I stopped using the task killer my bars and data proved to be more consistant! Hope that helps.
-------------------------------------
Sent via the XDA Tapatalk App

[Q] US Cell TP2

I'm currently using a USCellular (CDMA) Touch Pro2, on a GSM network (Viaero wireless, in Nebraska). In WinMo, everything works fine, and when I boot into Android everything that should work does... except... Anytime it sleeps, it drops it's connection to the GSM network and doesn't connect till I wake it. That means any calls, texts, emails, etc that come while it's asleep don't show till I manually wake it (or in the case of calls, they go to voicemail). I've tried searching, to no avail, so I was wondering if any of you smarties can help. My startup.txt is as follows
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 board-htcrhodium.is_cdma=0 pm.sleep_mode=2 physkeyboard=rhod400"
boot
the pm.sleep_mode=2 was based on advice I found by searching and tried, but no dice, still dropping... it was set to 1 before...
Any ideas? I would LOVE to run Android as my daily, and AFAIK this is the only thing stopping me...
I don't know it will help, but on any recent kernel I believe you should use sleep mode of 1.
board-htcrhodium.is_cdma should be 1. F
Holograph said:
board-htcrhodium.is_cdma should be 1. F
Click to expand...
Click to collapse
I had it that way, but when I did it wouldn't see the GSM at all, it would try CDMA, and then fail and drop into airplane mode... That's when I tried setting it to 0, and was able to get a consistant signal, except for the sleep issue...
Thank you for your reply!
snalbansed said:
I don't know it will help, but on any recent kernel I believe you should use sleep mode of 1.
Click to expand...
Click to collapse
As I had said, it was at sleep mode of one, and I got the dropping. Based on my searching there was a suggesting of using 2, or even 3 on that, so I did, still didn't help...
Thanks though!
Seems like a bug in the newer kernels. I have a RHOD400 and do not have this problem at all, but it seems a lot of people are using their CDMA devices on GSM networks.
I've had a lot of reports from folks that are doing that, so try an older kernel. You'll lose camera support, but in theory this bug will not be present. I'd like you to help narrow it down if you can, to which kernel it starts in.
arrrghhh said:
Seems like a bug in the newer kernels. I have a RHOD400 and do not have this problem at all, but it seems a lot of people are using their CDMA devices on GSM networks.
I've had a lot of reports from folks that are doing that, so try an older kernel. You'll lose camera support, but in theory this bug will not be present. I'd like you to help narrow it down if you can, to which kernel it starts in.
Click to expand...
Click to collapse
Well... I switched to the kernel you posted here ( http://forum.xda-developers.com/showthread.php?t=885550 ) and that problem seems to be gone! Did get a SOD last night, but the signal seems consistant most of the time...
small glitches here and there, (market sometimes won't install apps, downloads, but hangs on instal, and a few system crashes that reboot to no service) but otherwise smooth sailing!
sooooooo... tonight I've been getting a ton of system crashes, usually when on the market, complete with relaunching in airplane mode, which is annoying... Anyone else getting these, or is it just me? Also, as I said before, 4 out of 5 times the market won't install... It'll download fine, just hang on installing and never finish... it takes a full reboot to enable me to try again...
Been getting a few more "program unresponsive" dialogs than I would hope, and on my Hero I would have run a fix permissions from ROM Manager, but I can't get it to install... Any ideas?
I truly do appreciate the help you have been giving me!
driftin said:
sooooooo... tonight I've been getting a ton of system crashes, usually when on the market, complete with relaunching in airplane mode, which is annoying... Anyone else getting these, or is it just me? Also, as I said before, 4 out of 5 times the market won't install... It'll download fine, just hang on installing and never finish... it takes a full reboot to enable me to try again...
Been getting a few more "program unresponsive" dialogs than I would hope, and on my Hero I would have run a fix permissions from ROM Manager, but I can't get it to install... Any ideas?
I truly do appreciate the help you have been giving me!
Click to expand...
Click to collapse
Kinda stealin your own thread at this point .
Are you on FRX05? Not sure if you said what build you are running... these kinda questions should go in the build thread tho TBH.
With that said, I would delete the data.img and start over. This will remove all the user stuff you've customized - basically starting clean.
dude i have the same problem on my rhod500, right now im using the tiad froyo x + the test kernel that arhhgggggg post from wilt2tilt and everything is working fine, try with that and let me know. the kernels from the autobuild site have the signal lost bug in my phone too

[Q] Wifi Error after EB01 Froyo Upgrade

Since upgrading to the EB01 Froyo leak (debinged/deodexed) I have wifi issues where every 3 or 4 times I attempt to enable it, it will fail, and show "Error" under the Wi-Fi settings (where it ususally says in blue text "Turn on Wi-Fi", "Connecting..." "Connected to <network>", etc). I finally got the log message associated with it, and was wondering if anyone has figured out a way to address this?
From what I gather insmod is the kernel's mechanism for (in this case) loading the wifi driver, so this would be an issue with the kernel? So now what?
E/WifiHW ( 2467): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1) : ret = -1, Invalid argument
At first I thought a reboot was necessary to get it to attempt to reload the driver, but I've since found clearing level 2 ram in the task manager does the trick. Still a big PIA though.
Thanks for any help.
Kidd_Funkadelic
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
AlgorithmX said:
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
Click to expand...
Click to collapse
So, if I'm not mistaken I can just install the non-voodoo zip w/ Red CWM directly over EB01 with no wiping/cache clearing, etc, and be up and running with no data or configuration loss? Sounds like a pretty quick and easy way to fix my issue.
I haven't been following the EC10 thread, but I just took a look and looks like the static issue when the screen comes on during a call is fixed as well, the only other issue I've had.
Guess I may have to give it a shot! How long have you been using it?
KF
I've been using it for a couple days and have to say that it combined with SuperClean 2.9 has made my phone super smooth. I haven't found a single glitch so far.
Took the plunge and updated to EC10 last night. I've had only a brief time to play around with it, but so far so good with the wifi. Thanks for the help!
Could just be my mind playing tricks on me, but I could swear in general everything is more responsive as well... Not only loading apps, but when I brought up navigation this morning I've never once seen it lock on and start driving directions this fast.
Nevermind... Same problem still with EC10. Got my hopes up there for a minute.
I got the same problem with SC 2.9.2v and had with any other SC Froyo build. I'm using JuiceDefender so WiFi is turned on/off lot of times (every 15 minutes on schedule or when screen is unlocked). Usually once or twice a day I find that there is an error with WiFi and the only way to fix it is to wait couple of minutes and try turning it on manually or switch to airplane mode on/off.
I also use JuiceDefender w/ Wifi. If it doesn't occur less often with EC10 (too soon to tell still), I'll have to disable the wifi controls in JD so it's toggled on/off far less frequently.
Glad to see I'm not the only one seeing it. I bet the JD users will just notice it more since we are loading the wifi driver all the time.
Kidd_Funkadelic
And thanks for the airplane mode tip- I'll have to try that. I was clearing level 2 ram in task manager to do it. AM would be slightly more convenient.
jt1134's source build EC10 didn't help, still having same problem with WiFi. My log is showing the same thing.
At least the new kernel fixed the static issue. One thing at a time, right? I hope that this means there will be ED01 kernel drop
Actually, maybe April Fool's day is a bad choice...
What radio are you using? EB01?
Yes, I did the full Froyo update to EB01 over the stock 2.1 Verizon eclair, then installed the EC10 specifically for this issue. That's all I've done. Oh, went back into CWM after seeing the problem for a few days to clear the Dalvik cache. That's all I've done to date...
OK so it's not radio related but kernel/rom then. I'm on EA28 radio cause I had problems with missed calls with EB01.
Solutions? Bump?
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
jbjcurly said:
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
Click to expand...
Click to collapse
I was able to get rid if the problem by using Auto Killer Memory Optimizer. It turned out to be a memory issue. Use one of the preset profiles, like aggressive, and see how you do. I was having the problem several times a day and it never came back.
Or, upgrade to PWGB, which takes care if the problem too and doesn't require messing with memory mgmt settings...

ATFWD-daemon keeps phone awake

See screenshots. This happened for the second time now, a reboot fixes this.
But I want to get rid of this! I haven't found anything in the build.prop.
With a Google search, I've found some vague reference to a Qualcomm radio service, but no details.
Is anybody in the know here?
I'm running 10c, unlocked, rooted and decrypted (850).
Edit: it seems to be the miracast functionality: http://forum.xda-developers.com/moto-g/help/com-qualcomm-atfwd-service-bloatware-t2820010
It's located at /system/app/atfwd
So I cannot deinstall or freeze it. I wonder why the phone was kept awake, though. It happened after charging the phone, before it was OK...

Categories

Resources