Related
When I try navigating with navigon, the GPS tells me I'm completely elsewhere and picks up at that point, lol and it send me to drive into the water xD
Lucky I always mind the road, still, what could be the problem that the GPS doesn't gets my location correct, not even in a radius of 30 km's.
The Localization via GPS is ON (not only triangulation) ?
yes, the GPS icon was on my screen all the time, also my 3G network was online at that point. So I received information from 2 channels. And still, it was such a damn pitty to see my device fail - I returned to winmo, then with tomtom it only took my half a minute to get a very functional signal. strange, it's not my phone, it's android..
i have the same problem: no gps signal and the GPS(navigon, sygic, copilot) doesn't get ma location
Gps is enabled in phone setting.
Mine works for 2min before signal dies out.
Also switching gps off, the icon stays in the taskbar.
what kernel are you using? there are quite a few kernels out there now. different roms are using different kernels. Some kernels gps doesnt work, some it does.
Ive used GPS in SHUI8 1.4 build with no problems. I havnt tried any other builds lately since GPS started working in the latest kernels with his builds.
veda_sticks said:
what kernel are you using? there are quite a few kernels out there now. different roms are using different kernels. Some kernels gps doesnt work, some it does.
Ive used GPS in SHUI8 1.4 build with no problems. I havnt tried any other builds lately since GPS started working in the latest kernels with his builds.
Click to expand...
Click to collapse
I use mattc leo from 23th of august with sense. God it scared the freak out of me, lucky I knew the road 80% sure, I've been there once, but damn, if it's so unreliable, I'll always keep my windowze
veda_sticks said:
what kernel are you using? there are quite a few kernels out there now. different roms are using different kernels. Some kernels gps doesnt work, some it does.
Ive used GPS in SHUI8 1.4 build with no problems. I havnt tried any other builds lately since GPS started working in the latest kernels with his builds.
Click to expand...
Click to collapse
I am using the one supplied with Froyostone V1. I've been told no issue using GPS with this one, but I have tried more than 3 gps softwares on it and they will die after a minute or two, mind you I make sure I get full GPS reception when I am on the road.
I use Google Navigation and it works well, on mattc froyo/sense v1.5 and all is well. It does take a few minutes to get a signal, but after its solid.
A word of caution...dont follow your GPS blindly.
Also, this is not a development thread..
I have been discouraged from the Froyo ROMs for a while due to the problem with calls being dropped but then suddenly they aren't dropped. I really like the Froyo ROMs though so I decided to try it again and the first day I experienced it yet again on CELB 3.6. It only happened a couple of times then 3.7 was released and I flashed that and it happened again on the first call LOL. I then started looking through things in the settings and under the mobile data setting I turned on National Data Roaming, since then I have been on several calls ranging from 20 minutes to an hour and have yet to experience this problem since turning data roaming on, some of these calls were in areas that I know for certain I had the dropped and reconnected calls happen before. Maybe some others may want to try this out and see if it helps you as well. Hope this helps some people that have experienced this as well.
Has anyone else tried this yet? And if so, has it made any difference for you as well?
happens to me all the time. kaos froyo, tazz froyo, celb froyo, nonsensikal froyo. Only at my house tho. i have 3 bars there. not sure whats going on there but i have learned to live with it. Wont be long till we are on 2.3 anyway. deal with it for a month. by the new year kaos should have a completley functional 2.3 rom. maybe without camera, but still fully functional.
I've been messing around with the national data roaming for about a week now. When I have national data roaming enabled it doesn't happen, if I turn it of it does. Try enabling it and see if it makes a difference for you too. It's located under settings>wireless & networks>mobile networks
will enable it and see if it happens tonight.
Same here, after enabling it I have had no stopped call issues. Its been about a week, so far so good
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Scott586 said:
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Click to expand...
Click to collapse
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
CondemnedSoul said:
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
Click to expand...
Click to collapse
I also have this problem happen on non-Verizon based ROMs such as RCMix.
The call says it's dropped, but the person on the other end can hear everything that's going on.
Then the phone rings you back, but in reality, they were hearing everything going on around you in the meantime.
I almost lost my girlfriend because of it. Immediately flashed away from said ROM. Had the same problem with Froyo ROMs.
May switch to a CM ROM now, if this is a serious fix. Thanks very much for this.
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
bftb0 said:
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
Click to expand...
Click to collapse
Sorry ut didn't work for you.... so far now im at 3 weeks without it happening to me
I have still had this temporary dropped call problem occur just as frequently on CELBFroyo 3.6 with this "fix". And most of the time I'm in my apartment on the phone for hours when it happens, and it sometimes happens more than once during these extended phone calls.
Just as has been described before: the phone looks and acts like the call was dropped, I can hear nothing but the other person can hear everything, and then after several seconds everything is back to normal.
Oh well. Thanks for the suggestion, though.
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
farmdoc said:
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
Click to expand...
Click to collapse
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
CondemnedSoul said:
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
Click to expand...
Click to collapse
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
bftb0 said:
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
Click to expand...
Click to collapse
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
farmdoc said:
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
Click to expand...
Click to collapse
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
roirraW "edor" ehT said:
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
Click to expand...
Click to collapse
Thanks! BTW what is AFAIK?
farmdoc said:
Thanks! BTW what is AFAIK?
Click to expand...
Click to collapse
You're welcome! AFAIK = As Far As I Know
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.
Why did VZW pull the MR2 update? I have it and my phone works with no reboots.
When did it get pulled?
g00s3y said:
When did it get pulled?
Click to expand...
Click to collapse
Oh, I thought it was pulled. My mistake.
they delayed it because the first RC didn't fix the reboot problem. That's what I've been told anyways.
Not all phones had reboot problems. Mine did and MR2 didn't help one bit. MR2.5 did fix my reboot problem and that's what I'm rocking now.
I haven't had any reboot problems unless I use the Freedom Pro keyboard (in SPP mode, of course). While using that I had two reboots in under 30 minutes though the reboot problem went away (and stayed away) as soon as I stopped using the external keyboard.
I had the reboot problem and flashed MR2. It's been extremely stable since. However, I am having some minor radio problems. It occasionally drops to 1X, or even no data (I live in a strong 3G area). However, the only real issue I've had with MR2 is that the market doesn't recognize my phone as compatible with all apps and won't let me install some of my purchased apps. Anyone else?
Will MR2.5 radio fix my data issues?
Anyone else experience the market problems? (My understanding the market issue is that MR2 is not an official VZW release and therefor not recognized by the Market)
I'm running stock, not rooted. Only mod is having flashed MR2.
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.