First of all, you guys doing the development for our devices are simply amazing. By improving the usability of our pda phones you are actually significantly improving the quality of day to day life (at least for me personally). It's a big deal, so thank you for all your work.
I don't post very often, but I lurk every day and generally have no issues to post about, but now one has come about that I need some help with.
_________
So I just began using Chainfire's WMWifiRouter yesterday for the first time, and it works perfectly for me. To be able to wirelessly tether multiple laptops is an unbelievably useful and cool capability. One of the features built in which is a very welcome one is also causing me a problem.
As you all know (if you've used the program) it is set up to keep the wifi active if you hit the power button and put the device in standby.
My issue is that it seems that the change it makes to keep the wifi active in standby doesn't revert to the default setting when the program is closed. So when I'm not using the program and I am connected to a wifi network in my house, and I press the power button, the battery is still draining very fast. Normally I can keep it in standby all day just waiting for calls to come in to wake it up and the battery will barely go down. But today I put it in standby and try to turn it on a couple hours later and it's completely dead.
It is just my assumption that the problem is caused by what I described because using this program is the only new thing I've begun doing since yesterday before the problem existed. Soft reset doesn't change anything, and the "crash cleanup" option doesn't help.
Can anyone confirm that I am correct in my assumption of the cause of the problem? Or any other ideas of what could be causing it? Just to be clear, I'm using a version that came with my rom (Colonel's 12-28-07 custom rom for the sprint mogul) and it is an older verion, v.081. I would try the newest version, but I couldn't find any details on the website about how much it costs once the trial is over.
Thanks a lot if anyone can help, I'd appreciate any bits of insight even if you're not completely sure.
THANK YOU!
So, no one has any thoughts on this?
It is becoming quite annoying to have to turn off the wifi in the comm manager every time I put the phone into standby just so it's not dead in an hour and a half.
Also, if I leave the wifi on and hit the power button, when I turn it back on the symbol shows the wifi connection still active but when trying to stream a radio station or open a browser it won't connect, and I have to turn off and back on the wifi to get a new working connection.
I'd just like to know if any of the other thousands of wmwifirouter users have the same experience, or just haven't noticed it or what.
Thanks.
Mogulus: Please try my Wifi Profiles -option Wifi Power->Normal Mode in menu.
BINGO!!!
Your program absolutely did the trick, thank you so much.
The only other suggestion I got was to flip off the wifi switch before entering standby and flipping it back on when returning from standby. Well that is simple enough but when you're picking the thing up every few minutes to check a random thing that pops in your head, that extra step gets so annoying.
Again, thanks a lot, you can expect a donation from me.
Thank you!!
Mogulust:
You are welcome
And Your suggestion - added to tasklist
As being discussed in various threads, some people are having BT problems with EB13 based ROMs.
The Problem
Inability to connect at some future time after having paired device with phone. Rebooting doesn't help. Only solution is to unpair, and re-pair, then device will both pair and connect with phone.
Also seen by some people are audio routing problems after disconnecting BT. Not sure if this is confined to devices that support (and connect) A2DP... more investigation/testing needed.
The Workaround
I tested various conditions to see how the BT subsystem behaved under various usage modes. In particular, across boots, turning BT on and off on the phone, on the device, etc. -- and then observed if automatic connection would re-establish after each combination of conditions.
I found that the problem seems to only happen if I turn off BT on the phone. If I leave it on, pair and connect with a BT device, then I can turn the device on and off at will, and it will automatically connect.
This (normal) function persists across reboots, at least for the few I tested.
I don't know how power-hungry the BT radio is when idle and not connected. My gut feel is that it is a pretty small drain, so leaving BT on all the time as a workaround probably won't have much of an impact on battery drain. I use Juice Plotter, and have a good history with BT off to compare to. I'll post JP measurements/results tomorrow after a 24 hour cycle.
Caveats
I also changed my Epic BT device name before I explored this situation with toggling the BT radio on the phone. While the name change did not correct the problem on its own, I can't rule out that the combination of name change and leaving BT on is what is making things work, rather than just the latter alone. So, to try this workaround, you must also change your BT device name on the phone, and leave BT on. Then, clear pairing and re-pair for the target BT device.
My Request
Would people that are having this problem please try this out, and report back in this thread success/failure, and any other observations. What we see in testing these different modes will be very helpful to the devs in trying to trouble-shoot an fix this problem (which I have no doubt they will long before Samsung does).
It should be noted that some folks are having issue connecting to a device, even after un-pairing and re-pairing. If that is the case, you might try this-
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Also, some folks are reporting an issue with multiple pin requests before a device will finally pair. I haven't seen that one myself, but just thought I'd mention it.
For what it's worth, other than the BT routing issue, I haven't seen any of these pairing or connection issues on my stock rfs Epic. It wasn't until I converted my other Epic to ext4 that Bluetooth had any issues, and they were all fixed by wiping data and have not returned since.
I have tried the workout around before in the past, and it changed nothing. Also I have noticed I seem to have more issues with particular audio bluetooth ear pieces, like BlueAnt Q2. It will show pairing is connected but after a couple hrs on the bluetooth connection is gone, but like I said it shows paired. My cheaper Plantronic ear pieces seem to work much better, except the fact I have to re-pair after each reboot of the Epic.
Ive tried leaving bluetooth on all the time, but after a reboot,
i have to repair ive tried all suggestions to fix it and the only way it seems is once it gets connected is always have the phone on and cant die and bluetooth always has to be on,
even after a long period of time somehow it loses the connection even if bluetooth is on and phone stays on,
There must be somethng the developers can patch with a flashable fix or another work around to get squash this annoying bug.. ill try to get a logcat today and try your method again see if i have luck
I will try to leave mine on and see what happens. Name change did not help.
But short on time. But given the chance I want to go back to bonsai 3.0.1 and see if I have the same problem. I don't recall it giving me a problem.
Edit: of I leave BT on, on the phone and just turn the BT device on/off it will not pair back up.
Edit: May have figured something out. I have been toggling BT with a widget. When I toggle from the notification bar it seems to work (so far). Which would also explain why it quite working as I added apps. As from clean install is used the notification bar and later used my power widget. But I have always used a widget before. I will test this out at work and see if this work around keeps working for me.
Sent from my SPH-D700 using XDA Premium App
I have to re-enter the PIN after every reboot. Mildly annoying.
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
automator said:
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
Click to expand...
Click to collapse
In my experience, the BT radio does not use any power when not connected to a device. If it does, it's not noticeable in Spare Parts or in performance.
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
blackdragon79 said:
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Have the pairing issue with ACS EB13 Frozen ROM 1.0.3/ Twilight kernel. The BT headset I use is Plantronics 975. Never had a problem with any of my phones until now... even my Treo 755 connected properly, not to mention BB Tour FWIW, my headset supports A2DP and I wiped/reflashed ROM/kernel several times without resolving the BT issue. Will leave BT on, but does it mean after every reboot I have to re-pair? That's not good if true, I hope a permanent fix can be found soon.
davidrules7778 said:
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Click to expand...
Click to collapse
I'm using syndicate frozen
Sent from my SPH-D700 using XDA Premium App
Update: For me at least, this workaround is still working 3 days later without a hitch, and across more reboots than I can count.
While I don't _know_ with tech/spec/engr certainty, as mentioned above it seems that BT uses negligible power when it is only listening for connection requests, and has had no discernible impact on battery drain at all.
So, this seems to be a viable workaround for the time being for some of us... it's real. What we need to work on as a community is figuring out what the critical difference is between those for which it works, and those for which it doesn't. KEEP POSTING AS MUCH DETAIL AND INFO IN THIS THREAD AS YOU CAN, EVERYONE... DATA IS WHAT WILL GET US TO THE BOTTOM OF THIS.
Personally, I think the key difference between the two groups is the size of your junk -- People with small equipment seem to be having all the failures
Sent from my mind using telepathitalk
I've had this issue on all Froyo builds. I have tried 7 different BT headsets from Samsmsung, Plantronics, Jabra & Blue Ant, all of them a2dp compliant with the same result, after a while, they stop connecting and I have to re-pair. As for the "workaround" since I have several extended batteries I've never turned BT off, and while it does take much longer to lose pairing, it eventually stops syncing or syncs only the headset protocol but not A2dp. For myself, the only solution I've found is to go back to DI18 which, although has its faults, works flawlessly with BT
I have been trying to get my brother's Epic working properly. It is rooted with EB13 installed. If this bluetooth error is not related to what others are having, let me know and I will create a different thread. I got his motorola H520 paired. I press the button and it starts the bluetooth voice dialing. It beeps and says please speak and then immediately gives and error saying the connection to the bluetooth was lost but the settings shows it to still be conneceted and it is as you can answer calls with the bluetooth without having to reconnect it.
My plantronics backbeat is paired and for phone calls is working, but sometimes no audio through music or video players. I had to un-pair, then re-pair then audio will work for a while.
I am using CWM 3.0.0.6 with midnight ROM with its installed kernal
Happening on my Plantronics Voyager Pro+ - It seems that everytime I pick up my phone the BT disconnects and then after about 15 to 30 seconds reconnects as long as I don't push any buttons.
There is also a lag "thingy" that occurs when I'm on a call and then another person calls - while the the second call is coming in, it seems like the packets get interrupted from the handset to the headset. Then once the incomming call goes to VM, the audio from the current call gets restored. Not sure if this is helpful or not, but I wonder if there are some routines in the BT transmission that have common "hooks" which are used when a second call comes in - Hope that is not too much of a noob statement...
Is anybody else having that "laggy" issue in the same circumstances?
Folks whose devices fit the criteria of what I have (see attached screenshot of my "About Phone" screen), please read on. I say this only so I can figure out what is common between us to be having the following Bluetooth issue:
1) Bluetooth toggle switch is OFF.
2) You slide the switch to "on". The phone sits there for approximately 10-15 seconds, but Bluetooth doesn't come on at any point, eventually the toggle switch in settings slides back to OFF.
3) There is no setting/method in the device that will turn Bluetooth on.
From when I received the phone from Google Play store, the only thing I have done to it is root it following this method.
Clearly, something with the rooting process did this (I am also having one other issue, but that one is less annoying than this Bluetooth one). But everything in my phone points to me still having the stock ROM but just having root access.
If I can just see the common thread between my phone and others having the same issue, maybe I can figure it out.
I don't want to flash my ROM or start from scratch for the fear of making matters worst for myself; the device appears to be working fine otherwise.
If I am completely unable to fix this, my only hope is that the eventual release of 4.4 KitKat would fix it on its own (and probably break my root at that point, haha).
After searching high and low for an answer to this, I ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Thanks to the Android OS, I let my phone charge overnight while on WiFi and by the morning all the apps were reinstalled and updated, including the OS itself. My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting.
Now, I just have to find the absolute least intrusive way to root my phone without any ROMs or system-level updates that could screw up stuff like Bluetooth or USB Connectivity for me.
has anyone else seen this with stock OOS? when i pick my phone up after not using it for a while, almost every single time it can't connect to anything until the screen is on for a few seconds...as if it's needing to reconnect to the wifi. after a few seconds, everything is fine (as if it had finished connecting and now works). i have it set to keep wifi on during sleep, but it seems to be ignoring that setting...at least that's the only thing i can figure as to what's going on. i'm stock unrooted on oos 4.5.15.
is there anything i can do here? i love this phone in every way EXCEPT for the god-awful wifi performance. the wifi in general has gotten much better, but this one bug in particular is incredibly annoying...also, before someone mentions it, i've already changed my router out trying to fix this. i was having other wifi issues, so i upgraded to ubiquiti gear...hasn't resolved this particular issue.
edit: of note, i've also tried turning doze off to help fix this...but doze mode in general on this phone seems completely unreliable in pretty much every way. that didn't help fix anything either.
I'm currently using the Pumpkin 8.0 unit and I really like it - however, the process of when I get in my truck is not nearly as simple as I would like it to be and usually involves several minutes of having to stop-start personal hotspot on my iphone (or unlock the screen) and then often opening the wifi settings, sometimes seeing an authorization error that clears up on the next attempt. It's never the same process, seems like there are several things that happen different to get in the way of it just happening.
I have an iPhone 8 Plus I dont use very often that I was just keeping in there with Personal Hotspot turned on, which seems to stay on for a day without turning off. But I usually have to unlock it to get it to show up in the wifi section. Should I disable the lock, would that make a difference? What about using my Galaxy S7, would that be "easier", I havent really tired messing with it yet since that is my main phone.
What hotspot solutions do people use in their setups to avoid the "process" of getting online?
Assuming Android would be much easier. The quickest way I can turn it on off is with bixby with note 8.
Since I'm not rooted I couldn't get Tasker to automate it. I tried nfc tags also. Eventually bixby was my solution.
I'll follow the thread for other recommendations
I also tried NFC tag, but for some reason cellular data can not be switched ON by NFC soft on non-rooted phone (it's OK with WiFi hotspot) - keeping this down during day helps to save battery.
I tried the NFC tag and while I dont turn off cellular data, I was disappointed to learn from the developer that the API to turn on and off hotspots was removed by Google and is not supported in 3rd party apps. I put the quick setting in my drop down notification screen, so at least I can turn it on and off easily. I'm going to try the android phone for a couple days and see if its just another reason for me to dislike apple.
So I have noticed that this is only an issue after the device wakes from sleep via the fast boot. If you reboot the head unit for real it connects first time with no issues.
It also seems happy to connect to real wifi networks without any issues. I don't have an android phone so have not been able to try that, but it would be good to know others findings. I'm not sure how the iPhone hot spot works but it must differ slightly to a normally wifi base station.