This is usual thread all over net..
I have problem, a big one... Every cooked rom I have tried works great but GPS dont work. Fix takes 15 - 20 min quickgps updates normaly but no fix... with original rom and quickgps updated fix is under 30sec but i have problem with touch screen on original ROM. so i have spend 15 days of experimenting, flashing various roms, radios but no luck....
interesting is that when i connect external gps antena with amplifier i get fix around 1 - 2min.... then it works with integrated, but 2 hours later same problem...
Kaiser130 is my device
tried roms: shifu v1 & v2 basic & full, Dutty's WM6.1, REV_ROM_V8, SimpleOsManila, AtheneOS....
also i have tried exporting registry branch from original rom for quickgps and copyed quickgps files over but no luck.
no luck
I have used almost all of these roms and my lock is in 2-3 minutes. 1st, make sure you are using the recommend radio. If you use the wrong Radio, you will never get a lock. Also make sure it is not just your area; if there are only a few sat's then the GPS module in the phone will take for ever for a lock.
vratko28 said:
This is usual thread all over net..
I have problem, a big one... Every cooked rom
Click to expand...
Click to collapse
C'Mon dude really... 3rd post and you come out dropping bombs like "every" and "it's the usual" and "a problem... a big one"
I have used many different ROMs here too and have not had a single issue with GPS working!
I think "every" and "usual" is disrespectful to the cooks here and that your issue is likely hardware (hence your comment about it working w/ an external ant) or possibly between the screen and the seat
have you tried gpstest to check your com ports and then set it manually?
I also had the same issues
already changed the com port and radio from 1.65.16.25 until 1.70.19.09 (KAISER Radio)
As u see raf1987 has same problem as me, yesterday I have tried original HTC WWE 6.1 rom but with same result.
I dont mean to disrespect cooks, and dont see what is problem with me having 3 posts??
k2rolla503 Yes I have tried gpstest, nonigps plot.... they find satelites but no fix 1 to 4 satelites all time but no fix.. signall strength is normal in all roms (graphicaly to me).
I too have the same problem.
I find the GPS fixes to be very flaky. I've used both the ROMs from Laurentius up through V10 and now using Phoenix II.3.
Laurentius ROMs I found I had much faster lock time if I downloaded the ephimeral file right before I used my GPS. We are talking 24 hours between uses. This could mean the difference between a 2 minute lock and a 20 minute lock. I've never gotten GPSTest to show me anything other than starting...
On Phoenix II.3, the ephimeral file only last for 3 days instead of 7 like Laurentius. Once I saw the fastest lock in my life ever on this ROM, it literally must have locked in 15-30 seconds. I have never seen it do that again. Currently it's taking me a good 10-20 minutes to lock on average. I have to start up my GPS 10 minutes before I go anywhere just to get it warmed up.
I've also tried fiddling with the assisted GPS setting on both ROMs. I found that with Laurentius the fix is slightly faster. On Phoenix I haven't noticed any real difference in getting a fix aGPS vs GPS. Nor do I find it assists in tunnels.
The only thing that really bothers me about aGPS is that I get that dialup connection dialog that says it fails to connect every time I use TomTom. I have to hit dismiss before it appears to start trying to get a fix. I've tried reapplying the connection settings for AT&T, that didn't seem to help much. It is super annoying.
In the end, GPS does work, but like the OP, I found that my fixes were consistently faster on the stock ROM than the cooked ROMs. I too mean no disrespect and I appreciate the hard work that goes in to each and every one of these ROMs even if I don't use them. I too like the OP just want my fix to be as fast as those claimed here and elsewhere. It can be frustrating to hear about these fast lock times and have to suffer with long lock times. It's especially annoying to me because I travel for business a lot and find that I am now nearly half way to my destination before I finally get a lock.
While I may not have many posts, I do follow these forums regularly. I hope that my input will be constructively used to find an answer if there is one to be found.
I have no issue using L26's TF3D V4, Athine OS Jan 22, Mbarvian Solace 1.5 and Josh' Revealed 21500. All has the GPS working fine. I'm not that particular that I measure individual response time.
As long as it locks within 1-2 mins (from nothing), it's ok to me.
hmm.... i think , i found the solution... don't know if it could work for others
now, I use PDA corner from Abusalza... with Radio version 1.70.xx.xx
so, after flashing your new rom... make sure you update the GPS support programs like quick gps , etc
then, execute your GPS program ( I use Garmin for this).. and make sure you are outside of your house, or apartment, or wherever..
the reason why my tytn II could not find satelites is because I did it in my house, did not think that outside my house could work (because my Trinity could detect satelites in my house without any support GPS program like quick gps)
then... your tytn II should detect the satelites and GPS is activated...
NB: sorry for my bad english
k2rolla503 said:
have you tried gpstest to check your com ports and then set it manually?
Click to expand...
Click to collapse
I am having the same problem. The original Three (Australian) ROM would get a GPS lock within seconds.Now, I take 20smins to get a lock.
ROM version: AthineOS WWE
ROM date: 1/22/09
Radio Version: 1.65.24.36
Protocol version: 25.94.40.06H
I have just used GPS test and the only thing I changed was the baud from 4800 to 9600. Will try it out later, but hope it works.
http://www.smartphone.net/software_detail.asp?id=3170
PS Most of us know that GPS works only if there is line of sight with the satellites, so yes, I am outside on cloudless days when I try to get locks.
PPS If it dont work, I might go back to official ROM. http://www.htc.com/au/SupportDownload.aspx?p_id=13&cat=2&dl_id=342.
flash back to WM6.0, there are no problems with gps. every fix in 30 sec.
Hmm I would like to go back to 6.0 but my provider has only this rom 6.1 for download that has touch screen problem...
Any link to 6.0 WWE would be helpful
Found 6.0 sry.... ill try and post reply
Search the Wiki. There're links to various WWE versions.
Hmm, I wonder then what the difference is between 6.0 and the higher version that causes this inconsistency in locking. This would seem to indicate software issue rather than a hardware issue. I love the newer ROMs but the inconsistency or complete latency in getting a lock can be extremely annoying especially when you need a lock quickly.
jorakae said:
Hmm, I wonder then what the difference is between 6.0 and the higher version that causes this inconsistency in locking. This would seem to indicate software issue rather than a hardware issue. I love the newer ROMs but the inconsistency or complete latency in getting a lock can be extremely annoying especially when you need a lock quickly.
Click to expand...
Click to collapse
I changed the baud from 4800 to 9600 and so far, the GPS locks within 30 seconds. I need further testing, but perhaps the default settings of the cooked ROMs is causing this problem?
I have tried and sucesfuly cooked ROM from stock firmware, added some apps, replaced buggy touch.dll so far so good ROM is 6.1 (WWE 3.31.xxx) using radio 1.65.20.15 i think.
Yesterday cloudy weather with rain i got lock within 4min cold start after flash, today morning warm start 2min (still cloudy no rain) and around noon no clouds got lock in 5sec.
Big THANX to SHIFU for help with dll
help with dll?
hi Vratko,
could you provide more info on the dll that u got helped with?? cos as u can see, lots of us are facing the same problems....even i have tried all sorts of ROM's and radios....yet no success in getting a quick lock...any specific settings to be done?? any
Hi,
I have different problem on GPS, I am using Garmin DK Series, dated 01/16/09. The problem is if use GPS for more then 10 min, back of the kaiser started to heatup, if I turn it off, after a while it is fine. Otherwise, it is detecting the GPS faster. I have downloaded QuickGPS & SeaSGEE.
Is anyone having these problem.
Thanks
Vratoko:
5s ????????????????????????? Please do enlighten us.
Newwonder:
Can you please provide SeaSGEE link. What does it do? is it like quick GPS?
i went on a few drives today to test out my gps, the odd thing is i couldnt get it to misbehave in a significant way. i am using eugenes ginger clone and da_g's update.zip using his own jupiter.xml. i chose his control plane version. i also used some files from jj4 not because i thought they were better but because i was experimenting with the jm9 "FIX" files but wanted to revert back and grabbed the wrong ones from my computer.
my lbs test settings were:
Sesssion Type: tracking
Test Mode: s/w Test
Operation mode: Standalone
Start mode: Hot start
GPS Plus: OFF
Dynamic accuracy: OFF
accuracy: 50
Logging: OFF
supl settings:
server: supl.google.com
port: 7276
secure socket: off
agps mode: control plane
"use wireless networks" in setting>location and security, was not selected
i ran several my tracks trying to recreate the situation described by Da_g where the gps position jumps around and locks are lost when mytracks is in the foreground and lbs in the background but is accurate in the opposite situation. i wanted to see if any "fix" would help this situation, be it a modem file or gps library from other rom but could not create the unstable situation observed by others. this bugged me because i have had serious trouble with google maps acting erratically while all my stationary tests come out fine. the problem is i never used the gps on this rom and did not know if it suffers from this problem in the first place.
it appears this rom does not have that particular problem or the problem is not predictable or can not be caused at will.
i ran a few my tracks with jm9 files. the results were mediocre at best, did it help? nope
did it hurt? maybe, not sure but probably not.
then i ran the test with jj4 files. did it help? maybe but probably not, tests did appear slightly better but were not free of imperfections
did it hurt? nope
on each test i ran one my tracks with mytracks in the forground and lbs in the background then another with lbs in the foreground and my tracks in the background.
observation: phone did not lose gps signal upon starting any app or switching to any app like others reported. tracking results were too close to call. i used similar routes with clear skys and the accuracy was similar when compared on the same road. with lbs up front i could watch the reported accuracy, it mostly jumped from 10 to 30m occasionally hitting 5, and spending more time at 10. average was about 15meter accuracy.
then for s's and g's i ran my tracks behind maps navigation to see if navigation would aggravate the bad behavior. well it didn't. perfect results! this is both reassuring and disapointing. while i can be a little more confident in my gps which in the past has been good except when using google navigation it also make me wonder if maybe the gps is just plain unstable and cant be predicted.
did samsung get it right in the base rom that eugene worked from? did using control plane fix it? did i just get lucky today with different results tomorrow? does touchwiz somehow cause the problems(not likely but who knows)? eugene did a pretty good job of removing touchwiz from samsung sources, not true aosp but it would fool most.
did i stumble on a unique combination thus fixing my gps? im sure the answer is no. it is either in the control plane settings with da_g's mods or in the rom itself.
the jl3 modem seems to get a slightly better signal but is certainly not a "fix"
will you have similar results? dont know, try it. but be warned that the rom is giving me some funny battery reporting and the standard recalibration isnt really working. i also had some random shutdowns when i used juice defender(maybe a bad install on the app) it also is not likely to work with samsung widgets and the video player wont play those weird media hub files.
i do believe that axura was built off the same base rom (im really not sure about this, just a hunch) but i had no luck with gps on that rom, i didnt use axura long enough to try fixing it but others report it as being very good.
i wonder if anyone has looked into available ram as a cause? eugenes rom seems to have a small memory footprint and i often have over 200mb free! could minfree be killing a service when ram runs low? could a setting in other roms be killing a service when exiting some gps apps for the sake of ram/battery usage?
im not a dev and would have no idea where to start on this. i also know that much files that control gps are proprietary and cant be fixed by the community, we can only hope to identify the problem and employ a workaround to prevent problematic situations assuming that the proprietary files are infact more or less functional. will samsung employ a fix? well i think with the number of identified problems with the gps that the galaxy s was released prematurely. samsung likely rushed the release to get a bunch of ooohs and ahhhhs without doing enough testing. it appears that they are incrementally improving gps performance over several builds and it may continue to get better, maybe over several updates. untill then ill use eugenes rom. i also think that if froyo builds did not help you then you may have an antenna issue!
ill attach the my tracks file when i have time.
i would like to thank clshortfuse and especially Da_G for there efforts. Da_G i hope you find a solution that we can all use regardless of rom, or maybe you can cook up a rom yourself, people would definately use it..
I was helping my brother trouble shoot his Inspire's inability to get a GPS fix when using MIUI. He told me he had tried all the driver swaps and other methods that are commonly prescribed, and that nothing had worked. However, in CM7 and sense based ROMs the GPS worked fine.
In EVO circles, this is a common problem on MIUI as well. The work around that has been developed is as follows:
1) Install a [near]stock ROM. Anything sense based should work.
2) Turn on the GPS radio
3) Leave it on, and reflash your favorite ROM (MIUI/CM7/etc)
That should fix it. It worked great on his phone, and he is happily navigating in MIUI with full accuracy and a very short acquisition time.
Enjoy!
sounds more like it was a bad flash or bad agps data left behind. but then i dont use miui. There is a bit more involved with the 'evo gps fix' and you havent done any of that. I havent seen any problems thus far with gps that wasnt fixed with the proper methods for cm. miui has its own set of problems and isnt really supported here.
Darunion said:
sounds more like it was a bad flash or bad agps data left behind. but then i dont use miui. There is a bit more involved with the 'evo gps fix' and you havent done any of that. I havent seen any problems thus far with gps that wasnt fixed with the proper methods for cm. miui has its own set of problems and isnt really supported here.
Click to expand...
Click to collapse
Well this was the method that worked for his phone, after all the other inspire fixes had failed. He'd flashed, cleared, reflashed, MIUI (various releases) and continued to have the same GPS problem. I figured I'd share in case anyone else was in a similar boat.
Cheers,
Kyle
Title should be GPS issues on AOSP Roms HTC One m7 Sprint. I tried a different map app with the same results.
So, there I was having a grand time with an awesomely awesome custom ROM (LiquidSmooth) and Kernel(SlipperySlothAOSPv.2), overclocked and with sweep2wake and t2w functioning perfectly and a **** eating grin on my face. Then I had to go somewhere I had never been before. Busted out Google Maps app, got a signal and a very inaccurate "lock," and then I hear "GPS signal is lost." Numerous restarts, hard resets and even trying a different Kernel and custom ROM (Beanstalk) yielded the same results: GPS is busted on all AOSP Roms for this guy. Not sure why.Any ideas on how I can get this important feature working on Liquid or BeanStalk? I tried GPS Fix and another app that erased the GPS data and downloaded updated data, but that didn't work either. Is there something out there I could try flashing after I flash one of the custom ROMS?
My device is the Sprint HTC One m7. Radios don't have anything to do with GPS do they?
MarkBell said:
Title should be GPS issues on AOSP Roms HTC One m7 Sprint. I tried a different map app with the same results.
So, there I was having a grand time with an awesomely awesome custom ROM (LiquidSmooth) and Kernel(SlipperySlothAOSPv.2), overclocked and with sweep2wake and t2w functioning perfectly and a **** eating grin on my face. Then I had to go somewhere I had never been before. Busted out Google Maps app, got a signal and a very inaccurate "lock," and then I hear "GPS signal is lost." Numerous restarts, hard resets and even trying a different Kernel and custom ROM (Beanstalk) yielded the same results: GPS is busted on all AOSP Roms for this guy. Not sure why.Any ideas on how I can get this important feature working on Liquid or BeanStalk? I tried GPS Fix and another app that erased the GPS data and downloaded updated data, but that didn't work either. Is there something out there I could try flashing after I flash one of the custom ROMS?
My device is the Sprint HTC One m7. Radios don't have anything to do with GPS do they?
Click to expand...
Click to collapse
OK. So the fix for this is to enable GPS (with High Accuracy mode selected in the sub settings) in a stock sense-based ROM before rebooting to TWRP, wiping and flashing your new ROM. I don't take credit for the fix, as I read about it somewhere else. Just can't remember where since it has been a few days.
Anyone know how to get a gps lock on CM12 based roms? I have tried using the gps.conf from a sense rom, but to no avail.
Backup aosp ROM
Clean flash sense
Get a GPS lock in maps and/or something like gps toolbox.
Wait a minute or two for good measure.
Restore aosp ROM
Lock on in maps and/or GPS toolbox.
If no lock achieved, try try try again. As per some peoples experience in threads they didn't get it until 5 or 6 times, whereas I have either had working GPS off the start or only had to do it once, so mileage varies.
I hope it works for you
This is kind of reflection as CM as a whole. It's great they support 38475728 devices now but in turn the overall quality has seemed to go south for a year or two. They almost always move on to the new version before making the current one stable.
How I fixed it
xsteven77x said:
This is kind of reflection as CM as a whole. It's great they support 38475728 devices now but in turn the overall quality has seemed to go south for a year or two. They almost always move on to the new version before making the current one stable.
Click to expand...
Click to collapse
My GPS was working on CM 11, but broke since I've gone to CM 12.1 nightlies. After quite a bit of fiddling, I got it working again but the fix is somewhat involved. I outlined it here on the CM Bug tracker, which I can't link to directly because I'm a new user. jira.cyanogenmod.org/browse/CYAN-5691?filter=-3
If you've got root access, you might be able to just drop this .conf file into /system/etc/ (if that dir exists on your CM version) or /etc/ (if /system/etc doesn't exist). Reboot your phone after putting this file in, and see if GPS works. I recommend using the app "GPS Status & Toolbox" by MobiWIA - EclipSim to test your GPS-- it will let you see what's going on with just your GPS, independently of other location services.
Edit: I was going from VZW stock software to CM 12.1, and getting a solid GPS fix on stock software before switching over did not work for me. That said, getting the GPS fix on stock software may be necessary but not sufficient to get the GPS working-- if in doubt, do both.
Good luck.
connorc0405 said:
Anyone know how to get a gps lock on CM12 based roms? I have tried using the gps.conf from a sense rom, but to no avail.
Click to expand...
Click to collapse
For a reliable GPS fix, add/replace two files: gps.conf and gps.conf_default, from a stock rom. You find these files in the system/etc directory. Fix permissions, if necessary. GPS is fixed.
GPS.conf_default file request
Hi. Can you tell me if it is possible to download this file from somewhere as it is missing on my device. I am using SM-N9005 and can't get any lock. Wondering if this file missing may be the cause. Many thanks. Karl.
jdaggar said:
My GPS was working on CM 11, but broke since I've gone to CM 12.1 nightlies. After quite a bit of fiddling, I got it working again but the fix is somewhat involved. I outlined it here on the CM Bug tracker, which I can't link to directly because I'm a new user. jira.cyanogenmod.org/browse/CYAN-5691?filter=-3
Click to expand...
Click to collapse
This has been fixed in the CM 12.1 nightlies months ago. Just validated in cm-12.1-20151010-NIGHTLY-m8.zip that PHONE_TYPE=CDMA