Bell Atrix running OTA GB. The phone is unlocked and rooted now as I have been trying to fix this for a while now.
When the GPS is activated (the circle crosshair icon appears) my data connection drops and reconnects. This can take from 10-45 seconds and is highly annoying. It has only been happening since the update.
I have:
Flashed Gobstopper for Froyo - seems to work fine with no loss of data connection
Flashed Gobstopper for GB - GPS/Data issue is back
Flashed Faux123's kernal - GPS/Data issue is there
Flashed CM7 Beta - Same GPS/Data issue
Each flash is through recovery with a complete wipe (wipe Dalvik, cache, data. Erase boot, system, userdata, cache, webtop, preinstall.)
I am out of ideas. Any suggestions?
Well I guess my issue is unique. Lucky me.
After flashing Froyo and letting the OTA update happen everything was doing well...
until I used THIS method to root my phone. As soon as I did this and installed Titanium Backup the GPS causes data connection drop.
At least I seem to have found the reason, now to find a fix.
(I am continuing to document this in case someone else has this same issue in the future.)
EDIT: After flashing 2.2.2 and letting it OTA update to 2.3.4 once more I found that it did the same thing again. GPS turns on, data connection drops then reconnects. This is without redoing IHOP. Without rooting. So the rooting method is off the hook. I am now leaning towards a hardware issue. I guess it is time to check out eBay for a spare Atrix and send this off to Bell to see if they will fix/replace it with an unlocked bootloader.
Deleted
10 char
Update: Bought a new phone. Bell Atrix. Came with 2.2. Put my sim in it. Logged in to Motoblur. Updated OTA to 2.3. Added my google account.
Still does it. I can't believe there are no others experiencing this. That is two phones. Same thing.
Only other thing I can think to do is get tasker and keep gps off until needed.
I still love my Atrix!
You are not alone!
I started experiencing this at some point after the Gingerbread 2.3.4 update as well.
It's disappointing to hear that it also happens with CM7.
Did you ever post about this in the Motorola Support Forums?
I haven't posted in the Motorola support forums. I searched there and found most of the responses lacking in service.
I am running CM7 stable and it seems to work better now. Better all around. Haven't gone back to Bell's GB for a couple of weeks.
Before I made the leap to CM7 I did find that if I left the GPS off and turned it on just before using it there was less of an issue.
Yeah Motorola has absolutely terrible support, but I only was wondering if you posted there since it might help them take notice.
I'd really love to put CM7 on mine too, but I can't get any answers to some of the questions I have first, and lots of the info I find online is contradictory.
I found though that if I turn off the "use wireless networks" option in the location settings that it seems to help a lot.
But then there are apps that nag at me about that setting being off.
Been running CM7 nightly 4. No issues at all. Best firmware for this phone. Hands down.
Follow the instructions and everything will work great.
Hey There.
Bell atrix freshly international boot unlocked, CWM with Neutrino 2.7, first time google mapping startup after bootup, Data connection drops right after GPS icon lights up. Data picks up again, and most times have to restart app, google mapping then works.
Waste around a minute every time. Can happen a while after first boot as well.
Seem to remember a problem like this on my Vibrant, had to change supl settings through phone codes.
But I've got nothing here. Still digging.
FYI - I'm also a canadian Bell Atrix owner. A commonality?
Also determined:
If on wifi when gps app/gps turns on, I see Atrix drop wifi, and go to H+ data.
If only on data when gps app/gps turns on, I see Atrix drop H+ data, and go... nowhere. H+ Data comes back after a dozen or so seconds
Also, happens when using NottachTrix as well.
Threw in my Rogers sim as well, same problems with dropping data when GPS runs
I remember having this problem on my Desire Z. It was driving me crazy back then, but I finally found the culprit.
It turns out the problem was that there were 2 data APNs (not including MMS). Whenever the GPS is enabled, the phone would disconnect from data because of this. I deleted the redundant APN (leaving only one APN that I wanted to use) and everything worked fine since.
Working rom
I found a rom that works, Max Blur 5, it is based on the original bell rom 2.3.6, I tested several other Roms and only based on bell works. The last version Max blur 6 not working it's base on ATT rom..
I am on the Bell network in Montréal Québec.
http://forum.xda-developers.com/showthread.php?t=1855288
Related
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
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.
Ok although I have few posts here at this site I wanted to first express my greatest thanks to all those that develop and maintain all roms for all of these phones and devices. Seriously killer work guys. Ok onto my story. A little history: DroidX2 on Cricket currently running Stock 2.3.4 with the stock mash up. Now I have never flashed the mash-up because I was running Eclipse 2.2.1 for the longest time and assumed it or something like it was already embedded . Then my area (Baltimore Maryland) gets hit with some nasty lighting and 90pmh winds causing 5 million to lose power. This is where my 3G starts randomly going white (loosing connection to Google's servers) and then cutting out all together. After re-flashing/SBF-ing.restoring/starting over from scratch/trying EVERYTHING about 30-40 times trying to solve the issue I came across some interesting info.
1. Called Cricket to find out the extent of their damage, turns out they are having 3G outages covering PA and parts of MD and VA, they are "working on it"
2. I was using the easySBF iso to re-flash back to 2.3.4 simply because its easy would install root and BSR in one shot (first thisng I noticed was that when SBFing back using this awesome tool, it would retain my MDN, MIN, PRL and other such Cricket setting however not the APN. Which I though was odd seeing as one of the major purposes of an SBF is go to back to stock.
3. After using RSD lite and the PC with the actual SBF file this last go round I started with 2.3.3 then did the OTA 2.3.4 all on cricket via wifi. After having the same if not worse 3G drop-out I almost carelessly flashed the stock mash-up.
To my surprise, the X2 is back on 3G! Its stable and is now staying not only on but connected to Google's servers just like it used to and my old X used to (sniffle).
So I don't know if Cricket fixed theor issue or not but seeing as how this was done at 2.30 am last night and the effect was immediate I have to give credit where credit is due. All this was to help anyone who has recently had the same issues, I also figured out ALL the correct settings for the programming menu, APN and so forth for the X2 on Cricket that I will post in another thread.
Again thanks to all those devs who made this possible!
Wrong
EDIT:
I recently re-did this and found out this is wrong. The steps are as follows:
- SBF to 2.3.3
- boot into Android Recovery by holding power and volume down, tapping vol down until you see Android recovery and selecting by pressing vol up
- wipe data and cache
- apply update 2.3.3-232_to_2.3.4-380.zip
- reboot
Then I setup cricket MIN, MDN, PRL, etc. and accounts and so forth and 3G is totally functioning. I had to redo this all because I noticed that the Stock Mash-Up is for 2.3.5 which would not allow me to install roms or much of anything for that matter. So if your having problems with getting your 3G to work on cricket with an X2 this should fix it.
Although I'm interested in explanations or theories as to what happened and why, this is more of a story than a question...
Like most of us, I've had this phone for over 2 years, and I've been running / testing / messing with a variety ROMs for a long time... My "daily driver" recently has been from the cm10.1 nightlies (updated every week or so).
I saw the March 16 availability of BAKED blackbean, and thought I would give it a try... Being lazy, my initial flash was "dirty" after clearing only the cache partition and dalvik. All looked good on boot, but I soon noticed the infamous "phantom key presses" that usually only occur in very low signal areas... This was happening even though I could see 3-4 bars of signal. 3G data was working to some extent.
I dialed *228+ to reactivate (not technically sure when it's a good idea to do this - I once heard it should be done whenever a new kernel is installed, but it rarely seems necessary). But, the call failed to connect... I rebooted to recovery, full wipe, reflashed, same issue. Reflashed back to "stock" cm10.1 (3/15 build - why does this feel like "stock" these days . Still no outgoing call capability and some phantom key presses. Couldn't send SMS messages either.
ODIN time - back to (truly) stock GB EH03. Still couldn't call to activate. My wife's fascinate, from the same room, could make calls and send texts, etc. so I mostly ruled out coincidental VZW network issues.
I went to VZW.com to "deactivate" my fascinate temporarily to a new phantom device and reactivate (an old trick), but VZW wanted me to choose a new data plan first and said I wouldn't be able to go back... So I called VZW tech support and got them to re-provision the phone from their end, and we finally got things working again only after using the EH03 stock function to factory reset (Settings --> Privacy --> Factory Reset), which kicks off an activation wizard on the next boot.
The VZW 2nd-level tech guy then called me, traded SMSes and verified I could call out to one of their test numbers... At this point, I seriously thought about staying on stock GB (or perhaps GeeWiz 2.9 - which is good stuff .
Anyway, now I'm back on cm10.1 with my usual data partition all nicely restored and everything is hunky-dorry. For a minute there I thought this old device may have been showing signs of old age and was about to die. But it seems good-as-new (better than new actually - given CM10.1 .
So, any ideas of what happened to my phone in what seemed to be the normal life of a flash-junky? I don't blame BAKED blackbean (no similar tales in that thread), although my dirty flash of that ROM coming from CM10.1 was where the problem started for me.
When should one really reactivate their phone via *228? How often is it necessary to update "roaming" capabilities?
When will the Galaxy SIII refurbs start showing up on VZW.com (I was contemplating my best replacement option there for a few minutes - why spend $200 on something new when you've got a perfectly good Fascinate)?
Very interesting story. Since I too am a Flash Junky. Hope nothing like this happens to me
Sent from my SCH-I500 using xda app-developers app
I haven't dialed *228 in 2 years lol I don't really see why you should have to
Sent from my SCH-I500 using Tapatalk 2
Just wanted to say that ive been lurking here ever since I had a Windows HD2....
Anyways, I flashed CleanRom 4.7 yesterday and charged it fully before taking it off the charger this morning. Despite the abnormal battery drain (which is abnormal even for a just flashed rom) and the weird signal issues with it switching to roaming and the like.
I clean flashed the rom, and currently have the Perseus kernel.
EDIT: I also couldn't get a GPS lock which I believe is/was a common issue? I would also receive the VZW text messages and WiFi authentication errors, even when connected to an open WiFi connection.
Only reason I didnt post this in the Development section is because of the post count.
Are you having issues with any other ROM?
Did you make sure to flash the ROM for your carrier?
I use CleanROM ACE, my wifi works as expected.
The Verizon text message will go away if you log into your Verizon account and remove the backup feature.
The GPS can be fixed by flashing a different ROM, getting a GPS lock, then flashing back to clean.
pool_shark said:
Are you having issues with any other ROM?
Did you make sure to flash the ROM for your carrier?
I use CleanROM ACE, my wifi works as expected.
The Verizon text message will go away if you log into your Verizon account and remove the backup feature.
The GPS can be fixed by flashing a different ROM, getting a GPS lock, then flashing back to clean.
Click to expand...
Click to collapse
I came from Beans Build 12 and I didnt have any problems then besides being able to get a GPS lock. I switched over to CR 1.5 SE just to see how it goes, and if it runs smooth thats what ill stick with until he comes out with another build for ACE.
Just a little update:
Battery drain is far more stable (or normal), and everything else for the most part seems like how it should. Only thing I havent tried is getting a GPS lock.
Guess CleanRom 4.7 isnt for me as of now lol