Related
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
[SIZE=+1]Edit 2/15/2011 - A very likely fix for this problem has been identified. See this post:[/SIZE]
http://forum.xda-developers.com/showthread.php?t=956091
Edit 9/14/2010 - see diagnostic information in post #27
bftb0 said:
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
Click to expand...
Click to collapse
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
jrozga said:
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
Click to expand...
Click to collapse
I poked around a little and couldn't find any mention of it as an official feature of 2.2; do you have a link?
Does it seem to happen to you about as frequently as you were getting plain ole' dropped calls on 2.1 or 1.5, or more frequently?
bftb0
Never had a call dropped =\ can't say, sorry.
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
carycooke said:
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
Click to expand...
Click to collapse
Does it happen more frequently than the rate at which you used to get dropped calls when you were on 2.1 (or 1.5) ROMs?
I don't know whether it is a bug or not - if jrozga is correct, then it should happen about as often as plain-ole dropped calls occurred with 1.5 or 2.1 ROMs. (Or maybe to be fair, as often as dropped calls occur with stock 2.1 phones with the July 2010 OTA - they have the same radio as most rooters are using)
I still haven't found anything on line from "official" sources that mention that this is expected behavior in Android 2.2 phones. The last time it happened to me, I questioned the other party on the line, and they said "I heard one buzz for about half a second". (They were on a land-line, so it eliminates their end of the connection as the source of the trouble.)
That's a little bit bizarre if they heard the first of the two vibrations on my Eris - it means my Eris had decided that the call had terminated even though it had not. That alone inclines me to believe it is a bug, not a feature.
bftb0
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
I'm running celb 2.1 and today made a phone call in a poor signal area and still made it all the way thru without dropping or anything is it a radio problem per chance?
tburns said:
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.
As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.
Which ROM and Radio firmware are you using BTW?
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
Sent from my ERIS using XDA App
Bump.
We now have 15 people on XDA (in the Eris forums) reporting the symptom:
bftb0: Tazz V6; Kaos Froyo V29 [Froyo]
jrozga: (unknown) [Froyo]
carycooke: Tazz V8 [Froyo]
tburns: ??? [Froyo]
mcook1670: "All Froyo ROMs" [Froyo]
punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]
Macrodroid: Kaos & Tazz [Froyo]
droiderisuser: ??? "2.1"
danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]
pablocasiano: WW4.6, KaosFroyo V29
crax0r: KaosFroyo V29
tjthebest: CELB 2.8-CM5.0.8
mistaj: CELB 2.8-CM5.0.8
npong: CELB 2.8-CM5.0.8
mflane: CELB 2.8-CM5.0.8
Some of them say "it happens all the time"
And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:
erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]
snozzcumber: Kaos Froyo V?? [Froyo]
TJTHEBEST: CELB 2.9 [CyanogenMod]
MrBojenglz: Buufed v???
BlueDC2: CELB v?, Kaos V?
rick311:
BellaSkye: Kaos V32
Kaessa: Kaos V32
tpatnoe: Kaos V30
rc346: Kaos V34
funkyfender: "CM6"
john58543: KaosV30
So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser
[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)
If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.
Code:
C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]
[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
Sent from my ERIS using XDA App
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
bftb0 said:
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
Click to expand...
Click to collapse
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
punkxdead said:
I have had this problem with ErisLightningBolt and CELB Froyo, (and KaosFroyo when I tested it). I never had this issue in a Sense based ROM (PlainJane), only in the AOSP/Cyanogen based ROMs. I live in a city with great 3G coverage and never experience the issue while at home, however I travel alot for work. When driving through rural areas it happens to me all the time. My call "ends" screen goes away, phone beeps and vibrates (like when you end a call), audio drops out, 5 secs later, screen comes back, call resumes. The caller on the other end always assumes I had another call/call waiting beep, etc. I believe the phone is switching from 3G to 1x in the process causing this, but I can't be certain. I have been patiently searching/working to find a solution but to no avail. Just thought I'd post since I'm finally hearing of others with this issue.
Click to expand...
Click to collapse
Never happens to me, and I make phone calls about twice per day.
punkxdead,
Thank you for that detailed report. Very useful information
Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.
So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.
It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.
If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.
bftb0
punkxdead said:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
Click to expand...
Click to collapse
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Macrodroid said:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
bftb0 said:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
Click to expand...
Click to collapse
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
Sent from my Froyo Eris using XDA App
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
I have the US locked Streak running 1.6 . I paid full price and never activated the AT&T sim. I only use wifi. I am getting ready to update to one of the 2.2 roms here, probably Steves. I have seen some posts that lead me to believe there may be some problems with the wifi. Am I wrong about this. Sure hope so.
I had WiFi issues with 1.7.0 and there have been other reports of WiFi problems.
I went back to 318 with the perfmod installed and it works with no issues.
YMMV and lots of people don't have any problems with 1.7.0.
On Dj_steve's 1.7.0 and no issues with wifi. i think if you do "volboost" in the install.txt you might have issues (as i did with one of the betas) and steve explained that volboost uses an old/bad kernel. So don't know if that was only in the beta or not but i use wifi all the time to tether my laptop to my streak (as i'm doing right now actually)
which kernel are you on fone_fanatic? im having wifi problems when switching between data and wifi, i need to reboot everytime i switch connection types. im currently using 2.6.39.9-DJ-Steve-BFS-CFQ-KG2L2D-Vol-OC but i didnt select volboost when i installed 1.7, i did have it on 1.6.0 though and i didnt factory reset when going to 1.7
having the same issue as rptw...
My own experiences were as follows (on a wide variety of routers, both G and N, running anything from stock Linksys/Cisco to Tomato and DD-WRT, using no encryption or WPA2/AES):
- ALL stable CM7 releases: Completely unreliable. Would connect initially, maintain communication for maybe 1-2 minutes at best, then lose connectivity (although the icon would remain green)
- Beta 3.1: For the first time, WiFi was rock solid. Worked absolutely flawlessly.
- n86: WiFi broke again, in much the same (apparent) way as stable.
It would seem those with WiFi problems (all of us?) fall into one of two categories - those for whom WiFi worked great with the .32 kernel until n86 (that would be me, and from what I've read, several others), and those for whom WiFi *never* worked properly on .32 _until_ n86, who now work flawlessly.
Is this a reasonable assumption? If so, I would guess this change:
Don't renew the leases if mDhcpInfo.leaseDuration is not positive
actually made things better for some and worse for others.
Anyone else with thoughts on this? The inability to maintain connection long enough to even copy a few hundred meg video over Samba is frustrating to no end - especially when, for a brief but glorious time, it was perfect!
Rodney
I own two NC and one is on n86 and the other is running Phiremod 6.3 which is Cm7 based with zero wifi issues
I've seen one WiFi issue:
My WiFi graphic indicator would show only the lowest signal strength. I have no idea if the signal is that bad, or it's just a bug.
I've not seen any disconnect issues.
In fact, my Nook Color has been more reliable with WiFi than my iPad 2!
I've connected to public WiFi, WiFi routers running stock Netgear, Tomato, DD-WRT, etc. No issues.
I've mostly ran the CM7 nightlies. I've used a little of Phiremod and Stock, but by far the nightlies.
I have this problem currently on both of my nooks running n87. its been happening for me since .32. weird thing is, it only seems to happen on my wifi, when i go to work and connect its all fine, or if i steal my neighbors wifi its fine too. but if i connect to my home wifi, it connects for 1-2 mins, then disconnects me but still shows that im connected. i even replaced my netgear router on stock firmware(i did try updating it) to a linksys that im currently using dd-wrt on and its still happening.
Have you tried N86+ with the OC Kernel and WiFi update?
Homer
What is this "wifi update" you speak of?
WEP works every time for me. Anything WPA protected is hit or miss.
I have a NC running CM-N86 and no WiFi issues.
Also, I my coworker's NC running CM-N87 doesn't have any WiFi issues either...
1) I have been running CM7 since it has been available. I have not once seen problems with WIFI. At home I have a linksys WRT54G router running DD-WRT using WPA2.
2) you posted in the wrong area. This should be in the CM7 user thread or the general forum area.
mr_fosi said:
What is this "wifi update" you speak of?
Click to expand...
Click to collapse
i wasnt aware of a wifi update >.>
CM7 Nightly - NO issues with Wi-Fi. Use it everywhere Wi-Fi is available...
i actually only have issues when i'm connecting to wpa2 enterprise. after disconnecting and trying to reconnect, the credentials no longer work. i have to delete and recreate it every time.
i'm running nightly 87 w/ oc kernel on emmc.
No wifi issues here either. No matter what I connect to.
Also... this should be in general... not dev section...
Sent from my HTC Glacier using XDA App
mr_fosi said:
What is this "wifi update" you speak of?
Click to expand...
Click to collapse
How about here. You must push the system folder contents or flash.
Homer
Homer_S_xda said:
How about here. You must push the system folder contents or flash.
Homer
Click to expand...
Click to collapse
thats not a wifi update, its the OC kernel. and at the very least my issue occurs wether i have the oc kernel installed or not
Homer_S_xda said:
How about here.
Click to expand...
Click to collapse
Yeah, I'm running 5/23 and I still have wifi issues on my home router (D-Link with WPA2-PSK).
Oh well.
re: general vs. dev...I respectfully disagree. I submit there _was_ a change in behavior, in the negative, for some users beginning with n86...and that is most definitely a -development- concern.
Rodney
The issue relies in the type of security and if you are using Aes or tkip. I have confirm this changing my router settings. The problem is that if I get my setting for the nook, tgen I have to reboot the router almost daily for my phone to connect.
I'm on nightly-87, Dal's 1.2GHz OC Kernel 5/23, and I'm experiencing something very similar. I went from 7.0.2 to N87 without a hitch, but I immediately started to see the WiFi icon go gray and lose it's connection. I was forced to restart WiFi as a remedy. As of today I'm getting something closer to what you're talking about; when WiFi turns on, the nook will infinity cycle through: disconnected->connecting->disconnecting->scanning. I've wiped Cache, Delvik-cache many times to no avail. Also tried re-flashing N87 and the OC Kernel, which did not work. I'm still not able to connect to my home network(netgear, WPA). But, after enabling/disabling airplane mode, I was able to connect to my LG vortex and obtain the interbuttz.
The last time I did a fresh install was around N20 something. As far as possible causes to this erratic and ethereal bug, my money is on certain update paths for both the OS and Kernel having different remnants. Example: with 87 different experimental OS installs and, to a lesser degree, the three different stable OS installs. There are technically !90 different upgrade paths. Compounded by being paralleled by kernel installs, but I believe when a kernel is updated the former is completely replaced instead of merged. I'm not calling out the Dev's, it would be nearly impossible to foresee and head-off all of the permutations of merging 87+ releases.
I'm no expert, just my two-cents. I'm not really concerned about this as a long term bug. There are fine people hard at work, and unfortunately have far more pressing issues to contend with. It's a sad reality that community driven projects, notably the nook Color, rarely reach maturity or complete/efficient hardware-software integration before the allure and newness of a product wares off.
As a consumer of .rockbox, a Linux based OS for G5.5 ipods and below, Of which I've been using for years and years. And, I would say it's just now becoming 'perfect', even with it's lack of support for many peripheral devices. I'm long term with my gadgets.
I'm rambling now.
Hope this helps to narrow down symptoms and possible causes.
I love spending time on a post, just to realize after it was posted that I was typing in the wrong thread reply tab. Oh well. Que Sera, Sera.
I have the reverse experience of the OP.
I never had any problems with Wifi ever, until the .32 test builds, when Wifi would stop without notice, requiring a disconnect/connect. This caused me to go back to a .29 stable.
Perhaps what the OP is suggesting is that the change, that was reversed, should be a toggle/option, rather than changed and then changed back.
I just got the thing and it came with GSB3.6 and it had SO many problems i put 3.7 on there and most where fixed, but my wifi disconnects every 15 seconds or so. any known fixes?
EDIT: Tried OMFGB, Same problem. i hope its fixable. someone help meeee
Check Settings, Wireless & networks, Wi-Fi settings, then tap Menu and Advanced. Change the 'sleep' policy (try "Never") and see if it continues disconnecting.
I would like to think that the default setting, "When screen turns off" does not kick in when there's an active connection...
I've used GSB v3.7 (Odex) with my WiFi without any problems.
Based on the fact that you observe the same symptoms with two different dev ROMs, I would suspect that the problem is either (a) your WiFi hardware, (b) your WiFi router, or (c) a software incompatibility between your WiFi router and the Eris' device driver (very similar from ROM to ROM).
You could try installing a completely stock ROM, for instance the
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
(Note that although this ROM is "completely stock" and "not rooted", flashing it does not touch your recovery boot, so you treat it just like any other dev ROM).
Running this test - if you still experience the problem - will exonerate any Eris dev ROM, and you have a couple of options at that point:
- see if your WiFi router has a firmware update available (router firmwares contain bugs, too). I have experienced incompatibilities with the Eris which were solved by flashing WiFi routers to newer firmware.
If you try that and you still experience problems, you actually still won't know if the problem is (a) or (b) - but if you take your phone to a Starbucks or other place with a WiFi hotspot available, and you still experience problems of the same nature, then it is time to suspect that the problem is "(a)" - hardware trouble with your handset.
good luck
bftb0
I switched the router from duel band N to single channel G, and now i only disconnect every 45 minutes or so.
also i tried swapping routers to a diff one, and then my dads DX, his wifes Droid, nor my Eris, could connect at all, under any settings. so it seems Android has alot of issues with wifi? anyways, i still disconnect, but not enough to bother me. thanks for the replies!
as much as it might suck, you should try doing a full wipe of data/dalvik and see if it fixes the issue. i had gone from 2.4 or so up to 3.7 without doing a wipe, and eventually things started to happen (widgets would not show up for new programs). i did a full wipe and everything is working great now.
I also am having wifi issues, didn't have them til I put the gingerbread cyanogen rom on.
I will do some more trouble shooting today and see if I can narrow down some of the variables. I have a Buffalo router with WPA2 for security on it. Some have suggested the security, but then I've talked to others that have WPA2 set up and no problems.
The wifi was working previously, did a full wipe of data and dalvik when I installed. I am running 3.2 or something close to that, haven't upgraded to the most recent version yet.
SO. Theres my info. But I love the rom and won't get rid of it, even if it is the rom.
My husband is fine just running 3G.
i have a linksys wrt54g running ddwrt using wpa2 with no problems, gsb 3.7 on my eris.
Bunie89 said:
I switched the router from duel band N to single channel G, and now i only disconnect every 45 minutes or so.
also i tried swapping routers to a diff one, and then my dads DX, his wifes Droid, nor my Eris, could connect at all, under any settings. so it seems Android has alot of issues with wifi? anyways, i still disconnect, but not enough to bother me. thanks for the replies!
Click to expand...
Click to collapse
In general, WiFi compatibility from clients to APs is far worse than most people expect; I've experienced interop problems with all sorts of gear. It is hard to draw general conclusions, as the results you get are highly dependant on specific hardware models & firmware versions.
About the only generality that can be stated is this: the more bells and whistles you enable on the AP, the more likely it is you will experience a problem.
FWIW, my GSB 3.7 Odex Eris seems to work flawlessly with a Linksys WRT54G with WPA2. I think I have multiband (A/B/G) turned off in favor of G-only.
cheers
Bunie89 said:
so it seems Android has alot of issues with wifi?
Click to expand...
Click to collapse
I certainly wouldn't say that.
hallstevenson said:
I certainly wouldn't say that.
Click to expand...
Click to collapse
Yeah I wouldn't say that either. I've had my Inc for a year, never had any problems with it, and like I said before this rom, no problems with wifi.
I also have an android tablet. No problems with stock.
So clean install with 3.7, did data wipe and cache, first thing I did was try to get wifi going, all it does is scan. Entered my SSID and everything. Says it's not in range. Bah.
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
alphax_0 said:
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
Click to expand...
Click to collapse
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
droidstyle said:
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
Click to expand...
Click to collapse
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
I see. It's just sometimes my 3g/wifi will be colored and still won't be receiving signal every so often even when I disable the other data method. Oh well
sendan said:
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
Click to expand...
Click to collapse
same here...but quite a few report the same issue as op. I seen a post where chopper said to only leave one on or the other. just passing the info along.
Hmmm, it may have to do with the radio. I've seen a few people mention that the handoff is better with the eh03 radio; coincidentally that's what I've been using since I came back to MTD.
Sent from my SCH-I500 using xda premium