GPS strength problem after going back to HC - Eee Pad Transformer Q&A, Help & Troubleshooting

I tried out some ICS builds, none of them are close to ready for daily use as I use my TF as my primary workstation as I'm out and about a lot of the time.
One thing that really matters to me is GPS strength as I use offline navigation (sygic) and before upgrading to ICS I had great signal strength.
I used the super wipe (full wipe version) zip from ARHD mike1986 and reflashed a fresh install of revolver 3.11, which was my main daily driver before ICS.
However, my GPS signal strength isn't much better than it was on ICS, and I'm not sure what happened? I then used the NVflash version to ensure a clean install, although I'm pretty sure the super wipe zip does the same thing, just from recovery.
Does the ICS ROMs somehow change low level code aspects of the tablet that remain even after a full wipe?
I feel like my TF has been ruined by these ICS builds.
Any ideas?

My TF101's GPS could not get locked signal using ICS even outside under clear sky

rickyt63 said:
My TF101's GPS could not get locked signal using ICS even outside under clear sky
Click to expand...
Click to collapse
Yes, ICS is a big fail with GPS, but honeycomb used to work great.
I'm back on HC 3.2.1 and it's not much better, so I fear something has been royally screwed up by whatever installing ICS did?
It's nice to be back on revolver 3.11, stuff just works again (GPS excluded) . I'm staying away from ICS builds for at least 2-3 months until it's reliable.

Mine has actually improved with ICS. I regularly obtain a lock within 5-6 seconds. With HC it took the GPS a minimum of a minute to lock.

Related

About. [ROM][ICS 4.0.4][3G] CyanogenMod9 (29 Mar)

I just wanted to share my experience with the tf101 ROMS. Especially the cm9 by ricardopvz that i'm using right now.
Before cm9 i was on Revolver on HoneyComb, it was good but as i said honeycomb, slow and not that slick. Also tried the hc stock, revolver on ics, and revolution on honeycomb and ics.
I have a cel with an ics rom and i love it so i miss the ics experience. When the official ics update hit the market i was exited but 2 hours latter extremily dissapointed for all the problems that it has.
Yesterday i flashed cm9 with the test 8 of the guevor's kernel, im very happy with it. Is super snappy, and full ics experience. I think i found a winner
Just a couple of issues if you want to try it:
1. The GPS took a lot of time to lock. A LOT!!! but finally it worked well.
2. The USP-PC Connection doesnt work, so... no file transfer or anything this way.
3. Somtimes it reboots itself when connect it to the power. (Not always)
Thats all i found. Besides that, this is the best rom that i've tried for my tf101.
jrivasf said:
Just a couple of issues if you want to try it:
1. The GPS took a lot of time to lock. A LOT!!! but finally it worked well.
2. The USP-PC Connection doesnt work, so... no file transfer or anything this way.
3. Somtimes it reboots itself when connect it to the power. (Not always)
Thats all i found. Besides that, this is the best rom that i've tried for my tf101.
Click to expand...
Click to collapse
+1.
Same set up as yours, cm9 by ricardopvz + Guevor's kernel test8.
1- GPS could not get a lock...(only try ~10 minutes). I will try again with loooonger time!
2- Dont use USB-PC, ... but good to know.
3- Have my TF docked; connected to charger every nite and haven't had reboot/SOD
Thanks.
jrivasf said:
I just wanted to share my experience with the tf101 ROMS. Especially the cm9 by ricardopvz that i'm using right now.
Before cm9 i was on Revolver on HoneyComb, it was good but as i said honeycomb, slow and not that slick. Also tried the hc stock, revolver on ics, and revolution on honeycomb and ics.
I have a cel with an ics rom and i love it so i miss the ics experience. When the official ics update hit the market i was exited but 2 hours latter extremily dissapointed for all the problems that it has.
Yesterday i flashed cm9 with the test 8 of the guevor's kernel, im very happy with it. Is super snappy, and full ics experience. I think i found a winner
Just a couple of issues if you want to try it:
1. The GPS took a lot of time to lock. A LOT!!! but finally it worked well.
2. The USP-PC Connection doesnt work, so... no file transfer or anything this way.
3. Somtimes it reboots itself when connect it to the power. (Not always)
Thats all i found. Besides that, this is the best rom that i've tried for my tf101.
Click to expand...
Click to collapse
1. GPS, while not great like HC I still got a lock after a couple of minutes. Just earlier today used it to navigate home and never lost signal
2. USB PC connection working fine for me
3. No random reboot but if it sit for a long time it shut off. Just flashed test 10 kernel and will see how it goes
jrivasf said:
2. The USP-PC Connection doesnt work, so... no file transfer or anything this way.
Click to expand...
Click to collapse
It should work. Sounds like the boot loader didn't flash properly.

Signal

I have flashed a lot of Roms successfully, ever since I got the inspire (over a year ago). Sure in the early stages of learning the device I had some boot loops, flashes that didn't take, or just random items.
However, as time has past I have noticed a problem when it comes to signal.
When I flash a Rom I always use the recommended radio, and ril combo that is suggested, however, I flash all available radios for our device, to make sure I have the right one for my area. (Mississippi, Alabama, and Louisiana)
I have a device that doesn't like overclocking, past 1.2 normally, no matter the Rom or kernal.
So I keep the device a hair over 1G, for stability.
Now to my question.
When I flash GB with sense 2.1, I get the best signal, and GPS lock of any build.
When I flash GB with sense 3.0, the signal drops some, but still ok.
When I flash GB with sense 3.5, the signal goes away. (I know some Roms have a glitch in the display) however I totally lose signal, where I had full service with the above.
My question is? Is there a way to pull the radio set up from GB 2.1 and align it with GB 3.0, GB 3.5 or even ICS?
Or is this based off the RUU that the Rom is based off of?
The Rom that gives me the best radio and GPS is Rumrunner 4.0, and the worst is any sensation port.
I have found a lot of stable, clean, and fast Roms that I like, however, I always have to return to a GB 2.1 Rom, because of signal issues.
Any insight on this would be awesome!!
"This has occured on multiple devices I have rooted, and flashed for others, so I know it is not just my device."
Sent from my HTC Inspire 4G using xda premium
SGF11 said:
I have flashed a lot of Roms successfully, ever since I got the inspire (over a year ago). Sure in the early stages of learning the device I had some boot loops, flashes that didn't take, or just random items.
However, as time has past I have noticed a problem when it comes to signal.
When I flash a Rom I always use the recommended radio, and ril combo that is suggested, however, I flash all available radios for our device, to make sure I have the right one for my area. (Mississippi, Alabama, and Louisiana)
I have a device that doesn't like overclocking, past 1.2 normally, no matter the Rom or kernal.
So I keep the device a hair over 1G, for stability.
Now to my question.
When I flash GB with sense 2.1, I get the best signal, and GPS lock of any build.
When I flash GB with sense 3.0, the signal drops some, but still ok.
When I flash GB with sense 3.5, the signal goes away. (I know some Roms have a glitch in the display) however I totally lose signal, where I had full service with the above.
My question is? Is there a way to pull the radio set up from GB 2.1 and align it with GB 3.0, GB 3.5 or even ICS?
Or is this based off the RUU that the Rom is based off of?
The Rom that gives me the best radio and GPS is Rumrunner 4.0, and the worst is any sensation port.
I have found a lot of stable, clean, and fast Roms that I like, however, I always have to return to a GB 2.1 Rom, because of signal issues.
Any insight on this would be awesome!!
"This has occured on multiple devices I have rooted, and flashed for others, so I know it is not just my device."
Sent from my HTC Inspire 4G using xda premium
Click to expand...
Click to collapse
What are you using to measure signal strength? If you are counting bars, each rom calculates them slightly different, only creating the illusion of different strength levels. Changing radios and rils often also isnt going to help you gain much. ive never seen a signal strength different between roms but i also have mine set to show -dbm so i know actual signal. Me personally, im using my gb ota radio as its given me the best signal retention out of the ones ive tried.
By the way, recommended radio ril that rom devs suggest is simply what they use on their device. They state this because this is the combination they know for 100% that it works. You are free to use whatever radio you want. and with sense roms flash the respective ril. aosp/aokp roms, do not flash ril (it will cause modem to not work until a reflash)

Disappointed with stock (JB) experience?

Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Stock JB was very laggy on my NS for some reason. Even swipping pages in the home screen was laggy. Some apps would instantly crash, too.
I've been running custom JB roms on my Nexus S, and its been running really well. The only thing is im experiencing the same lag that you do with Google Now. It has caused me to open my browser to do a search, which is disappointing, because in GB and ICS, the Google Search bar was so quick and convenient.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
polobunny said:
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Click to expand...
Click to collapse
heh, that's a fair point. I'm not so upset with the cards taking a long time to load as I am that, while they are loading, the OS is very unstable. It's difficult for me to bring up the keyboard and search google while it's trying to load those cards. I can't believe it's not butter
Nothijngrad said:
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
Click to expand...
Click to collapse
My thoughts exactly . I was excited to get back on stock so I could have a functional phone without any added bells and whistles. New features are nice, but not at this price.
Try running a custom kernel.. Try the thalamus kernel its very stockish and it's SUPER smooth..
Sent from my Nexus S 4G using xda premium
I'm running stock on [email protected] with a matrix kernel everything smooth for me
Sent from my Nexus S using xda premium
I had problems with JB too. There were a few lags, especially with Google Now. Some apps would crash every time I tried to open them, and the launcher crashed every time I tried to change wall paper.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
Hmm I can say that AOSP JB is WAYYYY better than ICS. Soon I can port my ROM from the NS4G to the NS.
I have to agree with this. I've used stock JB when it was released, I was wowed by it's smoothness and cool animations. But everything felt a little slow and sluggish coming from ICS custom rom. After switching to Jellybro, JB feels both very fast and smooth. If you feel disappointed with JB, try using custom rom.
Sent from my Nexus S using Tapatalk 2
I don't know if you guys with problem tried that yet, but it might be a good idea to do a factory reset. You will lose all your data if not backed up but I'm getting a feeling it could help. JB has only been smoother than ICS for most.
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
got556 said:
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
Click to expand...
Click to collapse
I just got my GNex and the difference with JB on this phone is night and day. I didn't think it would be but I'm pleasantly surprised. But yeah. The RAM issue seems to be my biggest gripe with it on the NS. And for some reason, it just dominated my battery. I went through my first cycle on stock with Trinity and managed 3.5 hours of screen time over the course of almost 17 hours and still had a little under 50% remaining. My NS would've been dead long before that with the same usage pattern.....
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
ekerazha said:
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
Click to expand...
Click to collapse
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
I'm running Androxide 3.1 and used to run AdamG's custom ROM. Both ran great, no hiccups what so ever, Google now loads very fast, I guess it depends on your GPS and internet connection. My experience with JB is far better than the fastest ICS ROM out there, I believe given enough time, performance will become exceptional.
Logomotph said:
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
Click to expand...
Click to collapse
That can be tweaked a bit with different kernels.
I am running XenonHD 9 + marmite 4.2 kernel. It's stable and smooth. Worth a try.

Canadian Skyrocket GPS issue (i727r)

The GPS takes 5 minutes to lock, and it does it at 1600 meters (un)accuracy.
It behaves like this no matter what rom i try (Sky, Slim, CM9/10, Embryo etc), except for stock Rogers ICS.
The agps patch and other gps patches on XDA didn't do anything.
When i first bought it, it had stock Rogers ICS and GPS worked perfectly, never mind the fact that i live in EU.
Then i tried custom roms and it started to funk around and has been doing as long as i run a custom rom.
Today i installed Rogers ICS as a last resort and suddenly the GPS locks in seconds and with great accuracy too (9 meters).
And so the question, what the hell is causing this?
OR
How do i make the GPS work with the custom roms?
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
rpr69 said:
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
Click to expand...
Click to collapse
I'm not sure either.. The phone is canadian with a Rogers brand on battery cover. When i install a stock AT&T rom the GPS more or less dies.
Any other rom and the GPS dies. Stock Rogers ICS rom and voila works like a clockwork.
And it doesn't react at all to any GPS patch, and i've tried like 10 different ones. aGPS is not new to me, i've successfully used it on other phones. But for some reason it doesn't do anything for my Skyrocket.
Mike on XDA said:
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
Click to expand...
Click to collapse
Thanks i'll try that, just don't see how Aroma is going to help if it's the same patch i've tried earlier.
On the other hand, with ghouly issues like this who knows what might help and what won't ?
Worst case scenario is that i'll be stuck with Rogers FW if i want working GPS, which is acceptable with some tweaks especially the Droid Razr M launcher
The thread is here: http://forum.xda-developers.com/showthread.php?t=1732304
--------------------------------------------------------------------
Sent from my Skyrocket i727 running Team Dirt
--------------Nexus 7 running AOKP PUB--------------
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
icenight89 said:
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
Click to expand...
Click to collapse
Nope, it's always turned on.
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Jack_R1 said:
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Click to expand...
Click to collapse
Hi Jack_R1
Software does indeed solve everything. In short: stock rogers ics rom = perfect gps, custom rom/stock at&t rom= no gps.
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Jack_R1 said:
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Click to expand...
Click to collapse
1 The AT&T roms didn't give me an adequate lock, until the JB updates were leaked & released.
2 I'm always using automatic APN's but they don't have any GPS info.
Haven't tried #3..
4 FasterFix didn't help.
5 GPS Status shows 4-7 satellites and only 2-3 locks with horrible accuracy. The thing is now i get perfect locks with any ROMs.. I could've disallowed Google Services to use GPS as I might've confused it with Google Search & Ads wanting my location..
Thanks for your help :good:

Stable ICS

Is there a stable ICS out for T959v? Stable as in GPS and wifi calling for t mobile is functional.
knicks791 said:
Is there a stable ICS out for T959v? Stable as in GPS and wifi calling for t mobile is functional.
Click to expand...
Click to collapse
lol no.
I wouldn't consider WiFi calling a factor in a roms "stableness". Its more of a feature. Cm9 is stable and GPS does work
Yeah forget about wifi calling. I think cna 2.0 is great. Cm9 release 8 and well for as early as it was released beam is fairly stable.
Sent from my SGH-T959V using Tapatalk 2
ICS AOKP is stable.....
Stable as in normal human definition, yes. Stable as in Wifi calling, no.
Wifi hotspot?
Theraze said:
Stable as in normal human definition, yes. Stable as in Wifi calling, no.
Click to expand...
Click to collapse
How about stable as in wifi hotspot? I don't use it often, but when I do I need it to work well (business). Works fine on my Vibrant, but I also have SGS4G that I'd like to see if I can get better signals on cell (especially), gps and wifi. I had been sticking with GB ROMs since they seemed the best for GPS/wifi, but would like to move to ICS if possible.
The ICS hotspot has worked basically always worked fine unless you screw with services. My wife used AOKP when we were out of town a few weeks ago. I used Barnacle and Wifi tethering for root users while on JB.
Both ICS and JB worked fine for tethering.
Theraze said:
The ICS hotspot has worked basically always worked fine unless you screw with services. My wife used AOKP when we were out of town a few weeks ago. I used Barnacle and Wifi tethering for root users while on JB.
Both ICS and JB worked fine for tethering.
Click to expand...
Click to collapse
Good. Is there a "best" for GPS? Seems most JB have issues and several ICS as well from what I've read so far.
JB doesn't have GPS yet. That's its issue, but airfluip1 thinks he might have some ideas on how to fix it. Hopefully he'll get it working, or Erik will, or someone else maybe. But for now, skip JB if you need GPS.
ICS has 3 different options for GPS, and it's not always apparent which is better.
1) Assisted GPS. This requires having a build.prop file that tells your phone how to use GPS for this. Most of our ROMs want to do this, but end up in number 3 instead. There are directions on how to fix this if you aren't using Ultragen, or just use Ultragen which comes with this properly configured from the start. First connection to GPS may take 15-30 minutes, but it should be much faster after that.
2) Non-assisted GPS. This comes from flashing YAGF. It disables the assisted GPS and just uses the satellites fresh every time. This CAN be much faster, but won't work well in clouded/wooded/indoor areas.
3) Bad GPS. This is when 1 or 2 fail, generally number 1. The phone is told to use AGPS but it's disabled in the build.prop, or any of a wide variety of other issues. GPS will work... sometimes... but it's highly irregular.
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Or start modifying your own files, but be careful that your phone boots up. Don't use Microsoft Word or Notepad or Wordpad or any of those tools. Use a proper hex or *nix editor.
Theraze said:
JB doesn't have GPS yet. That's its issue, but airfluip1 thinks he might have some ideas on how to fix it. Hopefully he'll get it working, or Erik will, or someone else maybe. But for now, skip JB if you need GPS.
ICS has 3 different options for GPS, and it's not always apparent which is better.
1) Assisted GPS. This requires having a build.prop file that tells your phone how to use GPS for this. Most of our ROMs want to do this, but end up in number 3 instead. There are directions on how to fix this if you aren't using Ultragen, or just use Ultragen which comes with this properly configured from the start. First connection to GPS may take 15-30 minutes, but it should be much faster after that.
2) Non-assisted GPS. This comes from flashing YAGF. It disables the assisted GPS and just uses the satellites fresh every time. This CAN be much faster, but won't work well in clouded/wooded/indoor areas.
3) Bad GPS. This is when 1 or 2 fail, generally number 1. The phone is told to use AGPS but it's disabled in the build.prop, or any of a wide variety of other issues. GPS will work... sometimes... but it's highly irregular.
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Or start modifying your own files, but be careful that your phone boots up. Don't use Microsoft Word or Notepad or Wordpad or any of those tools. Use a proper hex or *nix editor.
Click to expand...
Click to collapse
Just a suggestion, but the Pimp My Rom application https://play.google.com/store/apps/...sMSwxLDYsImNvbS5hbmRyb2d1aWRlLnBpbXBteXJvbSJd under GPS Tweaks will download the proper GPS files for location, or alternatively, you can install the GPS Status and Toolbox App https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5lY2xpcHNpbS5ncHNzdGF0dXMyIl0 which you can set to download the newest AGPS File when you open it.
I am using AOKP ICS and have no issue with GPS. Was getting like 120 sec TTL for like 12 Satellites according to GPS Tools, which is not terribly life affecting for me.
Which... is irrelevant if your build.prop doesn't use those files. As I said. You can tell GPS Status to update every hour, but if the phone isn't set to use them, they're helping you as much as throwing the phone up 20 feet into the air (without twisting it). Slightly less, since they're using up storage and not getting your phone closer to the satellites.
That being said, the TopNTP app did have GPS modifications as one of its options. Not sure if it does the build.prop flag we need, but...
Wow, it seems the SGS4G may actually be worse than the Vibrant for GPS.
LoL
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
Theraze said:
Which... is irrelevant if your build.prop doesn't use those files. As I said. You can tell GPS Status to update every hour, but if the phone isn't set to use them, they're helping you as much as throwing the phone up 20 feet into the air (without twisting it). Slightly less, since they're using up storage and not getting your phone closer to the satellites.
That being said, the TopNTP app did have GPS modifications as one of its options. Not sure if it does the build.prop flag we need, but...
Click to expand...
Click to collapse
There is gps. It just no worky right! It will take a lil more then downloading a * "NIX" EDITOR and edit build.prop
Sent from my SGH-T959V using Tapatalk 2
hechoen said:
We'll call this one hidden in plain site.
I've been testing a new kernel for Beastmode lately and was trying to get GPS to work. I flashed 3.1 google specific build and still no lockie. So I did what cryptic mentions in the OP and READ the notes. Well that note that I quoted up above is the thing that needs to be done for this phone to make GPS work. After I added that line to the build.prop and rebooted I got a lock in about 10 seconds indoors to an accuracy of 6 meters. Not bad for this phone at all.
Most of are ICS ROMs use CM as a base. So after going through and looking at most of their props NONE of them have that line. I don't know how it's escaped notice as long as it has. I've only tested it on CM9 8-29 build with Beastmodes yet to be released kernel. I doubt that it matters though. Flash the zip, add that line, reboot and you should be good to go.
So thanks to cryptic for this fix and one of the most detailed OP's I've ever had the pleasure of reading. And too erikmm(aka Beastmode) for the incentive to actually look into this.
Click to expand...
Click to collapse
As I said...
Theraze said:
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Click to expand...
Click to collapse
Thanks ! Where can I download YAGF for a T959v ? Is Ultragen v1.8 also good or only 1.0.1 ?
Remember that you have to flash something that actually works on our phone, unless you're making your own franken-build.
Ultragen 1.01 is available in post 4 of the Ultragen thread. There is no Ultragen 1.8... at least, not here on XDA for our phone.
Regarding the GPS, it's the same YAGF2 from the Vibrant forums... it's just a generic-ish fix that may or may not placebo you.
Unfortunately, I don't understand the technical jargon regarding all the GPS options...maybe I'm better off not knowing.
However, I'm running CM9 with Proton kernel & LB6 modem and everything works (except, of course, for wi-fi calling).
No problems whatsoever with GPS. Battery drains a little fast but I have a zillion chargers laying around the house,
office, & car...no big deal.

Categories

Resources