Related
When I first got the phone it seemed like I could lock on in about a minute. Tried to use the GPS the other day and after it searched for a few minutes in the car I just turned it off. Very frustrating... What are you guys experiencing?
I am on stock rom, rooted, gorilla v05 OC kernel.
Are you moving when you were trying to get a lock? When your moving it takes much longer to get a lock, this is true even with dedicated GPS units. Having said that my MT4G takes about 10-15secs to lock outside not moving, very nice coming from a Galaxy S which couldn't lock or track to save it's life. To many variables if moving to make a good comparison in GPS performance.
mine locks in seconds... love it after the vibrant lol
Yes, I have tried while walking and while in the car. Just tried to put the phone up to the window of my apartment for several minutes with no luck. I will try to stand still outside tomorrow.
larryg2k3 said:
Yes, I have tried while walking and while in the car. Just tried to put the phone up to the window of my apartment for several minutes with no luck. I will try to stand still outside tomorrow.
Click to expand...
Click to collapse
I had the same issue! It wasn't like that in the beginning but the other day I was trying to get directions while driving and it was such a pain in the ass that after 4 minutes, it still said "searching for GPS". Garbage...
i wonder what was wrong. I was outside and the weather was pretty decent but nighttime.
Same thing here, although I was blaming it on CM rom....
borodin1 said:
Same thing here, although I was blaming it on CM rom....
Click to expand...
Click to collapse
I didn't root mine but I have the same problem. When I first got the phone it used to lock on GPS very fast, now I use Igo or Copilot and both take like ever to find lock on GPS . I use GPS test app and it shows like 6 GPS Sats but the programs still can't get the gps reading.
I have just tried it after uninstalling copilot just to keep one navigation application and I disabled wireless network location assistance and I think gps worked fine,i have to try it tomorrow again.
Sent from my HTC Glacier using XDA App
Gps is not stable, today I tried it by holding the phone in street and standing . Gps test apo got about 6 or 8 but no location locking on google maps or igo . I went to my room, placed the phone on the window I got sometimes 3 and then 8or 9 .it worked eventually and started to become fast (i turned the gps on and off) it seems like a software problem!i am not sure
Sent from my HTC Glacier using XDA App
I had a lot better luck trying to lock on while standing still. I have also since switched to Iced Glacier 1.1.1 and now 1.1.2, but I think that being stationary with a good view to get initial lock is key.
My brand new Mytouch 4G (stock rom, not rooted) has the same issue. It tries to get a GPS lock using google nav for minutes without ever getting a lock. I can disable GPS and enable it to sometimes speed up the lock process, but it never locks in less than 30 seconds. From the previous posts, it sounds like the GPS hardware is sub par on this phone and there may be no quick fix. Fortunately, mine is still new and can swap it out for another and see if that helps.
My gps works fine, although once it would not lock on, and a simple reboot took care of that...
I often use GPS test or navigation just because I love seeing how well it works...
...coming from a Vibrant
I experience the same problems with the mytouch before and after rooting and installing custom roms, I think its the phone itself, I never had this problem with the nexus one
I too have noticed it is sometimes really really slow.
Much much slower than my old E-71 sometimes.
I wonder if cases/how you hold it can affect it.
- Frank
Incredible reading:
http://www.techtree.com/India/Reviews/Samsung_Galaxy_S_LCD_GT-I9003_Review/551-114781-614-5.html
GPS locking with Google Maps was one of the early and crucial issues with the GT-I9000 and I hoped that it didn't exist in GT-I9003. But I was disappointed partially. Even this phone continues to have quick GPS locking issues. Whether I used the GPS or turned on data connection for A-GPS support, the accuracy level is still around 500-600 meters. It was the same with my backup phone Nokia E63. Apparently, the smartphone offers A-GPS support and is dependent on data connectivity to fetch the exact location.
Click to expand...
Click to collapse
One year later, they release a new phone with a GPS that s**ks again...
Well, I'll be really waiting for guinea pigs to jump on the i9100 before moving....
My i9000 is awesome for GPS. Better than my iPhone 3g and my 2.3 nexus one.. I sold my navman. Different region's I guess.
Sent from my GT-I9000 using XDA App
Can't say I am satisfied with the i9000 gps, my old glofish 500 beats it hands down but with a couple of tweaks the i9000 gps works ok.
The i9003 battery is 1650 instead of 1500 and it should also fit in the i9000.
The i9003 is the SAME PHONE as the i9000, just with different screen technology. Therefore, its perfectly reasonable to expect the GPS to function in EXACTLY THE SAME WAY.
If yours sucks, then that's the perception you'll have of the i9003. Personally I don't think it's that bad, but it's not as good as the i8900; which goes to show that Samsung *DO* know how to do GPS; they just got the antenna wrong in the i900x range.
stuclark said:
The i9003 is the SAME PHONE as the i9000, just with different screen technology. Therefore, its perfectly reasonable to expect the GPS to function in EXACTLY THE SAME WAY.
If yours sucks, then that's the perception you'll have of the i9003. Personally I don't think it's that bad, but it's not as good as the i8900; which goes to show that Samsung *DO* know how to do GPS; they just got the antenna wrong in the i900x range.
Click to expand...
Click to collapse
Totally agree with this. Although since loading JV1 onto my SGS I'm of a somewhat different opinion - 3 days in and my GPS is working "great" and I'm getting an accuracy of between 8-16 feet every time, something which I never had with <= JPY. Makes you wonder why it's so hit and miss...
stuclark said:
The i9003 is the SAME PHONE as the i9000, just with different screen technology. Therefore, its perfectly reasonable to expect the GPS to function in EXACTLY THE SAME WAY.
If yours sucks, then that's the perception you'll have of the i9003. Personally I don't think it's that bad, but it's not as good as the i8900; which goes to show that Samsung *DO* know how to do GPS; they just got the antenna wrong in the i900x range.
Click to expand...
Click to collapse
no its not just the screen. different gpu(sgx530 instead of sgx540), different chipset(OMAP instead of hummingbird). And its thicker.
stuclark said:
The i9003 is the SAME PHONE as the i9000, just with different screen technology. Therefore, its perfectly reasonable to expect the GPS to function in EXACTLY THE SAME WAY.
If yours sucks, then that's the perception you'll have of the i9003. Personally I don't think it's that bad, but it's not as good as the i8900; which goes to show that Samsung *DO* know how to do GPS; they just got the antenna wrong in the i900x range.
Click to expand...
Click to collapse
Maybe you should do a little research before posting. Like someone has already pointed out, the hardware is quite different.
In any case I bought a GT-9003 last week and I havent faced any GPS issues like you mention, whether under open skies or inside a building.
Blaaargh said:
Maybe you should do a little research before posting. Like someone has already pointed out, the hardware is quite different.
In any case I bought a GT-9003 last week and I havent faced any GPS issues like you mention, whether under open skies or inside a building.
Click to expand...
Click to collapse
Have you actually used it in the past week?
My i9000 GPS is ok, unless you drive in areas with high density roads. The issue is with accuracy, really uneven and sometimes just not enough to avoid jumping through roads while driving.
Fix in steady mode, no driving is a very bad way to test the GPS.
Actually, when driving in a city with many close roads, I pare it with my external Bluetooth GPS. Accuracy is unbeatable (3-16 ft all the time) and I spare my battery
PS: googoo Bluetooth GPS v0.5.9a works like a charm, no crash with JS7 (unlike Bluetooth GPS Provider v1.2.6 which crashes in froyo)
jonny_ftm said:
My i9000 GPS is ok, unless you drive in areas with high density roads. The issue is with accuracy, really uneven and sometimes just not enough to avoid jumping through roads while driving.
Fix in steady mode, no driving is a very bad way to test the GPS.
Actually, when driving in a city with many close roads, I pare it with my external Bluetooth GPS. Accuracy is unbeatable (3-16 ft all the time) and I spare my battery
PS: googoo Bluetooth GPS v0.5.9a works like a charm, no crash with JS7 (unlike Bluetooth GPS Provider v1.2.6 which crashes in froyo)
Click to expand...
Click to collapse
Bluetooth GPS doesn't work anymore in some new kernels from Samsung
based on the specs... it's just a crappier version of the i9000. seems like what ended up with excess materials not used by i9000.
why the hell would it have better GPS then ?
herbert1 said:
Bluetooth GPS doesn't work anymore in some new kernels from Samsung
Click to expand...
Click to collapse
JS7 is a very new kernel. I don't expect the soft not working on JS8 as no major differences
However, "Bluetooth GPS Provider" is another soft and yes, it doesn't work anymore.
On the other hand, Bluetooth GPS from googoo works
jonny_ftm said:
JS7 is a very new kernel. I don't expect the soft not working on JS8 as no major differences
However, "Bluetooth GPS Provider" is another soft and yes, it doesn't work anymore.
On the other hand, Bluetooth GPS from googoo works
Click to expand...
Click to collapse
Would flashing a custom kernel help?
gothfebrio said:
no its not just the screen. different gpu(sgx530 instead of sgx540), different chipset(OMAP instead of hummingbird). And its thicker.
Click to expand...
Click to collapse
is thiccker because of the bigger battery... the worst of this phone is lack of custom rom or kernel mod, is just a simple samsung phone with stock options... and no more. but performance is good and the screen is not bad.. i've got it couple of days,and i'm well impressed.
GPS not working on my i9003 also . Even tried GPS aids,GpsFix, GPS Status and FasterFix apps also for GPS but of no use. Any Idea how to get it working. Mine is an India version
FROYO.DDKB2
Kernel version 2.6.32.9
Baseband version I9003DDKA5
Firmware version 2.2.1
Please help me how to go about it.
My GPS on i9005 was terrible using Arabic JPKB1 Firmware.
Installing European XXKB3 Firmware solved the GPS issues. GPS now works great -- A Cold fix in under a minute and hot fixes in few seconds. Accuracy is very good.
Mine is i9000 manufactured in October 2010. I bought it as a secondhand one. For the first two months I was crazy with the GPS and I really wanted to sell it to buy another one (like Desire Z or Droid 2 Global). The reason is it was really hard to get fixed, If I were lucky, sometimes 2 minutes with maximum 3-4 satellites, but most of the times I had to give up after 5 mins without any locks.
But after I upgraded to the latest 2.3.3 European ROM AND installed GPSfix, now it's just easy for me to get fixed under 20s outside with at least 6 satellites, sometimes 9 or 10. Once the satellites get locked, if you restart the GPS even after a while, it takes only 5-10s to get them locked again. It works like a charm with all Navigation apps, such as the buit-in Nav, Google maps or Osmand.
The accuracy is normally 30m, but sometimes it goes up to 10m. I've been testing for 2 weeks and never had a problem since then.
I don't know what fixed the problems, the Gingerbread or the GPSfix, but now I don't dare to try anything, even uninstalling the GPSfix.
It's quite funny that I live in Vietnam and I flashed the European ROM via ODIN, and now my GPS is working flawlessly.
PS: my firmware is XXJVO
Hi everyone/anyone,
I can't post in the developer sections so I'd like to comment here then.
Have used IColdS on my Desire S for about 6 months as a work phone with heavy email and talk usage. The biggest pain was email not showing the email body and then not responding - alot. Every now and again other apps stop responding.
Anyway, I came back here and tried Jellytime as a random pick. Worked great after a week of use. Even USB tethering and Wifi hotspot works. Apart from the 5mp camera photo issue and Bluetooth not working at least email and general stability is good. The 2 issues are known and being worked on. Great upgrade I think and extended the life of the old girl a little longer.
Axel
How is battery life on this ROM? I am currently on Pacman 19.3, but have issues with 3G battery draining. So I only use 2G of wifi.
Otherwise, I like the Pacman ROM a lot. Now and then a spontaneous reboot when the phone is idle, but until now, it hasn't disturbed me.
zertyx said:
How is battery life on this ROM? I am currently on Pacman 19.3, but have issues with 3G battery draining. So I only use 2G of wifi.
Otherwise, I like the Pacman ROM a lot. Now and then a spontaneous reboot when the phone is idle, but until now, it hasn't disturbed me.
Click to expand...
Click to collapse
I must say I haven't run on battery alone for a whole day yet. At my work desk it's always docked and charging. This weekend I'll be running off the battery so will report back how it goes.
Axel
axelmasok said:
I must say I haven't run on battery alone for a whole day yet. At my work desk it's always docked and charging. This weekend I'll be running off the battery so will report back how it goes.
Axel
Click to expand...
Click to collapse
Phone was about 70 odd % Friday night. It was 2% Monday morning after only 2-3 phone calls over the weekend with no charging. My un-scientific conclusion would be it's battery life is worse than IceColdSandwich. Bothers me none. I prefer the stability (so far).
And is this with 3G activated or do you use WiFi all weekend? At home my battery lasts long, but when I leave and put 3G on, it's terrible. 2G is ok.
Verstuurd van mijn Desire S met Tapatalk
3g, data and WiFi all on. All weekend. I live in an area that requires 3g or I lose reception.
Upgrade
axelmasok said:
Hi everyone/anyone,
I can't post in the developer sections so I'd like to comment here then.
Have used IColdS on my Desire S for about 6 months as a work phone with heavy email and talk usage. The biggest pain was email not showing the email body and then not responding - alot. Every now and again other apps stop responding.
Anyway, I came back here and tried Jellytime as a random pick. Worked great after a week of use. Even USB tethering and Wifi hotspot works. Apart from the 5mp camera photo issue and Bluetooth not working at least email and general stability is good. The 2 issues are known and being worked on. Great upgrade I think and extended the life of the old girl a little longer.
Axel
Click to expand...
Click to collapse
Some of the custom rom builds like the one build by @blindndumb (jelly time 4.2.1) has a new release every third day. Is it possible to upgrade to latest release over the air if u have previous release on the device?
I'm not sure. I would probably update from recovery myself.
Cheers
battery
The battery life in JellyTime is great.
maxmax195 said:
The battery life in JellyTime is great.
Click to expand...
Click to collapse
Yes I see that there is a new version as of a few days ago. I'll update to it this weekend and hopefully enjoy Bluetooth and better battery life. As it stands with JellyTime R.4.0 the battery lasts me 7:30am to about 7pm before the battery goes into red < 20%. Can't complain but it used to be better.
Ah also, some users reporting their phone locks up requiring the battery to be removed. This has happened to me about 4 times. I'm pretty sure every time it happened when I rebooted or powered off/on the Desire S. I'm not keen on removing the battery but waiting for 10min or so it wouldn't reboot itself. Holding down all the buttons didn't work either. I might try connecting via adb next time it happens.
I just changed to Jellytime from Icecold sandwich. I'm having a problem with AOSP roms. Taking screenshot in some screen seems impossible unlike sense roms where u just need to push POWER +HOME to take screenshots. on AOSP roms, i cant take screenshots of a zoomed pic,zoomed webpage etc. anyone knws any app that can assign keys to take screenshots?
its_Khal said:
I just changed to Jellytime from Icecold sandwich. I'm having a problem with AOSP roms. Taking screenshot in some screen seems impossible unlike sense roms where u just need to push POWER +HOME to take screenshots. on AOSP roms, i cant take screenshots of a zoomed pic,zoomed webpage etc. anyone knws any app that can assign keys to take screenshots?
Click to expand...
Click to collapse
I just tried it then with JellyTime and it works here bud.
Held down volume button and then held down power button until the screen shot captured. Worked fine.
I have also had the one earphone side only issue. Only when I have answered the call and then plug the earphones in. I work around that by selecting loudspeaker on then off. Then I can hear audio in both earbuds.
Cheers
axelmasok said:
I just tried it then with JellyTime and it works here bud.
Held down volume button and then held down power button until the screen shot captured. Worked fine.
I have also had the one earphone side only issue. Only when I have answered the call and then plug the earphones in. I work around that by selecting loudspeaker on then off. Then I can hear audio in both earbuds.
Cheers
Click to expand...
Click to collapse
Worked great!!!! Thanks buddy!
Sent from my Desire S using xda app-developers app
Jellybean ASOP Feedback
as other users i don't have the rights to write on the dev threat to report issues and experiences, then lest do it here.
Upgraded from Saga to ASOP jellybean a week ago, the process pretty strain forward and no issues.
Bugs I've found so far:
- The battery drains very quick (less than 24h on normal use), despite of the settings on not altered from default ones.
- The wifi and phone signal meter it's showing very low values, but no issues or loss of signal at all, seems more like a signal meter calibration.
- The proximity sensor when on call in progress is not working, i mean, display doesn't turn off and the ear can mess up with commands on the phone screen.
-Time to time background apps (google now, google +, swift keys) crashing and restarting, no loss of data noticed.
-Some random problems when shooting videos.
In general the ROM is very responsive, a big improvement from ICS, and can be used for a daily basis, still need to be improved but stable enough to adopt it.
JellyTime feedback too
Hi,
I can't write to dev section, so here's my problems with JellyTime. I can't adjust screen lights, buttons change but there is no diffrence. I have MDDI panel, so it might be related to it. Thanks again to pointing it out. Battery drains a little bit faster than I expected, but it's generally really good and stable ROM.
ROM: JellyTime R6.1 - Saga Edition
aliegm said:
as other users i don't have the rights to write on the dev threat to report issues and experiences, then lest do it here.
Upgraded from Saga to ASOP jellybean a week ago, the process pretty strain forward and no issues.
Bugs I've found so far:
- The battery drains very quick (less than 24h on normal use), despite of the settings on not altered from default ones.
- The wifi and phone signal meter it's showing very low values, but no issues or loss of signal at all, seems more like a signal meter calibration.
- The proximity sensor when on call in progress is not working, i mean, display doesn't turn off and the ear can mess up with commands on the phone screen.
-Time to time background apps (google now, google +, swift keys) crashing and restarting, no loss of data noticed.
-Some random problems when shooting videos.
In general the ROM is very responsive, a big improvement from ICS, and can be used for a daily basis, still need to be improved but stable enough to adopt it.
Click to expand...
Click to collapse
I did a complete wipe/format of everything before install of 6.1.
- Battery drain seems normal to me coming from ICS
- Wifi and Network levels look and behave normally for me
- The proximity weirdness was apparent to me and solved after installing the Sweep2Wake app and disabling.
- I get no crashing of any apps. None since moving to Jellytime 4.x and now 6.1. I don't have any games. Just news/weather/email/web apps.
- I must admit I don't film videos. The camera and video control is so slow and clumsy I don't bother.
Sounds like your issues all relate to something local with your phone IMO.
Hemmodeli said:
Hi,
I can't write to dev section, so here's my problems with JellyTime. I can't adjust screen lights, buttons change but there is no diffrence. I have MDDI panel, so it might be related to it. Thanks again to pointing it out. Battery drains a little bit faster than I expected, but it's generally really good and stable ROM.
ROM: JellyTime R6.1 - Saga Edition
Click to expand...
Click to collapse
I'm not sure what you mean. The backlight/LCD brightness? Works fine for everyone else. If you have the Sony LCD then your in another boat altogether and yes I'm pretty sure changing brightness doesn't work which will make your battery life interesting. eBay out your phone and buy find another one there if your a fan of the Desire. Otherwise upgrade to another model.
I remember somewhere somebody reported issue with compass in our Relay.
Now I found that it is somehow related with other sensors and/or modules.
So if your compass not working properly turn off wifi, data transfer and GPS and try.
Regards
Mac
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
for me also no difference, however i try, google maps with gps is usually going sometimes ok. havent got the clue behind yet
Jax184 said:
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
Click to expand...
Click to collapse
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
gee one said:
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
Click to expand...
Click to collapse
That's only needed if your GPS is totally inoperable.
So the Relay 4G has horrible GPS? Seems to be an ongoing theme with Samsung phones.
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Jax184 said:
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Click to expand...
Click to collapse
I...don't know the difference between the GPS and the compass. I thought people were using the terms interchangeably, but apparently not.
Solkan said:
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Click to expand...
Click to collapse
Okay...this is very interesting. Differences between GPS and compass aside, this still seems like good news. At least to me, cause GPS is very important to me, and its my understanding that the Captivate Glide's GPS is very hinky. Seems like if you stick with stock you'll be fine. Now, bluetooth, I have no idea how the bluetooth is on the Relay (stock or custom ROM), but at least the GPS is good and even better with this GLONASS.
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Jax184 said:
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Click to expand...
Click to collapse
Okay...I've actually been experiencing that lately with my Epic 4G on Cyanogenmod, but I blame that more on the most recent update of Google Maps which changed the entire interface than I do the ROM (I'm on the most recent stable release and before the Google Maps update GPS worked perfectly). But that's still something I'll save for that board. But what you described is exactly what I've been experiencing, the Navigation seems to work, but it takes a while for the indicator (the red arrow) to face the right direction. Since I use it to drive around my own town its not that big a deal, but if I ever go out of town, yeah it could be an issue.
Someone on one of the Relay 4G boards here opened up his Relay 4G and showed exactly where the metal components are, and how with some tweaking it may correct it without calibration...but with my luck I'd break the thing permanently.
I do wonder why the Relay 4G is like this...my only guess is that Samsung was trying to rush it out and didn't have the time to properly test it? I know it was supposed to be called something else (Blaze Q or something). But the funny thing is, even with this "error" (which from the sounds of it is easily remedied), it still seems like more of the spiritual successor to the Epic 4G than I originally thought the Captivate Glide was, or at least an Epic 4G if it was GSM. 5 rows of keys, same shape...I just don't know why this phone isn't more successful than it is. At least you can get it on eBay, new, for about $200-$300. I haven't been inside a T-mobile store in years so I don't know if they regularly keep them in stock or not. But its still available. That Captivate Glide is still available for less than $200, but with its issues with GPS and bluetooth...I don't know, seriously thinking about this phone now.
Anyway, thanks for the response. And by the way, how is the bluetooth on this phone?
EDIT: Herp derp, it was YOU who opened up their Relay 4G! My apologies, sometimes these boards blur together.
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Jax184 said:
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
Click to expand...
Click to collapse
Ah okay. Though I can't remember the last time I tried to use both at once. Also, since the Relay 4G actually has a stock JB rom, what benefits would there be getting CM instead? I'm only on CM for the Epic 4G because Samsung/Sprint stopped updating it with Gingerbread.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
Click to expand...
Click to collapse
Thanks. The folks on the other board said it was an issue with the updated Google Maps app as opposed to the GPS/compass itself, and suggested a downgrade. I may try both solutions, though to be honest with you there's a huge learning curve with the most recent update to Google Maps (for instance still can't figure out how to get it to record my current location, which came in handy with the previous versions if I ever came across a place or store I wanted to visit again).
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Click to expand...
Click to collapse
Speaking of that calibration trick, where is it described in detail around here?
EpicMikeNC said:
Speaking of that calibration trick, where is it described in detail around here?
Click to expand...
Click to collapse
That was it! :laugh:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Jax184 said:
That was it! :laugh:
Click to expand...
Click to collapse
Oh. lol Ok, thought what you described for the Epic 4G was different, not the same. Gotcha. :good:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Click to expand...
Click to collapse
Well I know from my experience with the Epic 4G, you can remove the bloatware with Titanium backup and tether via an ap (if you mean hotspot tether). But at least there's options, stock or CM.
Still don't get why this phone isn't more successful than it is.
Compass is wacky on mine
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Bobby Tables said:
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Click to expand...
Click to collapse
How did you root by the way? One-Click?
But yeah, based on what you just said, I'm convinced its the update, not the compass. I don't understand how Google went backwards in regards to this so-called update to Google maps. But the Metal Sniffer solution seems to work, 9 times out of 10 anyway.
Also, I keep looking and looking, but unless I'm still missing it, didn't the update take away to ability to save your current location?
The bootloader is unlocked, there is no reason to run a rooting script. Just flash CWM with Odin/Heimdall and then supersu
I'm having a very similar experience here on CM 10.2 nightlies. Calibrating the compass doesn't always work. When it does it doesn't always stick. And when it sticks, it will be very jumpy, skipping from one direction to the other at random. This prevents compass mode in Google Maps, so it's annoying but not such a huge deal.
This weekend for the first time I had to use my Nexus 5 turn-by-turn navigation on Google Maps to get somewhere. I'm no stranger to the feature, as my previous Note 2 had a dashboard mounting bracket in my truck for this very reason.
Besides the speaker not being loud enough to hear the directions (one of my complaints with this devie), I found the GPS isn't very accurate at all. I have it set to High Accuracy, using GPS, WiFi and data network to find my position. The software often put the arrow about a block away from where I actually was and it kept falling behind telling me where I was supposed to turn.
I was driving at about 40-50 km/h at night with a cloudy sky. I reckon this was never an issue with my Note 2, both with stock TouchWiz and custom ROMs. My Nexus 5 is on stock 4.4.
So, what's going on here?
I honestly can't say I face this issue. My GPS is on point whether driving or just using it when I go hiking or camping.
A couple of weeks back I helped a buddy move into a new place and I loaded up my truck and he gave me the address and I popped it in the GPS, it locked within seconds and got me there just fine. No issues.
I also use it when I go camping. I'll find a nice place to pitch the tent and mark the campsite, then go exploring. Anything interesting I put a pin on it and can find my way back real easy. The speaker issue, sure. I use Viper4android (sound mod) and custom kernels to raise the output gain and make the speakers louder so that's a non-issue for me.
If you're rooted, check out FasterGPS (and if you're not rooted.. go and root).
Regarding sound loudness: try fauxsound (you'll need a compatible kernel and root). It boosts speaker, handset, and aux output significantly without adding distortion (although you can push it far enough to distort if you please).
Great, thanks for the tips.
Yes, it's rooted.
Regarding the sound boost apps, do they work on stock kernel, or do I need to flash a new one, like franco? I really don't want to do a clean wipe at the moment to install a new kernel.
GPS accuracy might be a loose antennae. As for speaker sound, not sure what to tell you. I had the phone resting on the seat beside me since I have no dock, with the radio going at highway speeds and had no problems hearing the voice directions. I didn't even have to max the volume, it was about 70%. No modifications.
Perhaps you have the extra glue around the speakers issue?
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
bionemesis said:
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
Click to expand...
Click to collapse
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
I haven't driven much lately, so this issue alone doesn't warrant a return for me.
However, the disappointment is stacking up over time. It seems to me that the N5 does a lot of things, but none of them very well. It's basically a tinkerer's toy with an attractive pricetag for the specs. Maybe it's because I came from a former flagship Note 2 device, but I do sometimes miss it.
Ajfink said:
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
Click to expand...
Click to collapse
Will do. I did go back to factory, unrooted and relocked the boot loader. GPS is much, MUCH, worse. It actually loses GPS signal now all the time. I'm convinced now more than ever that this is a hardware issue that gets worse over time combined with software that makes it worse. Hopefully the new, albeit refurbished, phone is better.
My GPS has never worked well, I have had mine for about 10 months as well. I've opened it up so the warranty is void but I don't care about that. I would fix it myself if I knew what exactly the problem was.
I use navigation at least a few times a week and I've never had a single issue with the GPS. It locks on right away, and is always accurate.
I had a nexus 5 from Sprint and the GPS was noticeably off, returned it and Sprint (terrible coverage). I got one from the play store and it's spot on.
Sent from my Nexus 5 using XDA Free mobile app
Got the replacement. Preliminary results...huge difference. Better than the phone originally was when I got it. GPS locks in immediately. And this is rooted stock with elementalx kernel. Will update again after a few days of use, but so far, so good.
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
bionemesis said:
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
Click to expand...
Click to collapse
Gps set to always on? Or can device manager swtich on gps?
doctor_droid said:
Gps set to always on? Or can device manager swtich on gps?
Click to expand...
Click to collapse
Device manager turns on GPS remotely.