Related
I have noticed that my HTC Touch HD consistently shows heights incorrectly - about 50m too high where I live. After some research I have identified that the NMEA message GGA contains 0 in field 11 (Geoid separation) which should contain the difference between the ellipsoid height and mean sea level height. In my Mio A701 this field contains 50.5, which explains the 50m error on the HTC.
Despite searching this forum I have been unable to find any reports of this problem. Has anyone else experienced it?
What gps chipset does the HTC Touch HD use? My copy of Sirftech does not work on it, so perhaps it is not the Sirf ?
Is there any way to correct this error?
Thanks for any information
Edit
The problem has been solved thanks to the GpsModDriver which performs this correction (amongst other things), and which can be found at http://forum.xda-developers.com/showthread.php?t=571266.
rpettipher said:
What gps chipset does the HTC Touch HD use? My copy of Sirftech does not work on it, so perhaps it is not the Sirf ?
Is there any way to correct this error?
Click to expand...
Click to collapse
It uses the Qualcomm GPSone receiver, this isn't a discrete component as a SiRF chip would be, but is integrated into the 7201A chipset
Sounds like you need to try to flash a few different radios.
GPS height error
Thanks for the information about the chipset.
Because of that I found a small program (MyGPS) which is largely based on an MS SDK demonstration, and that gives the correct height !!
As I understand it, please correct me if I am wrong, that program uses the MS SDK primitives to get information from the GPS without going through the NMEA messages (?). If it can get the correct answer then the GPS must be working, but the NMEA messages, and the programs using them (ozi explorer, visualgps ...) are wrong.
It would be very helpful if someone could confirm that they do see non-zero values in field 11 of the GGA NMEA message (between the two Ms) on an HTC Touch HD.
(One easy way to see the messages is to use the log feature of visualgps).
Thanks for your help
Actually, I noticed it, and I programmed a soft-coded separation correction into the program GPSVP: http://code.google.com/p/gpsvp/
Not many chipsets have the separation. To date, I had none in my hands, other than when using a 'real' garmin connected via a cable to my PC.
Additionally, I have encountered no program that does the correction, other than gpsVP, in which I programmed that myself. I shall check that MyGPS, if it is correct, but I am sceptical, I do not believe that MS would strip the info from the chipset, nor do I believe MS has a softcoded correction.
I guess I could write some sort of serial loopback to insert the logic into other programs, but I am far to busy.
EDIT: just so you know: I only programmed this very small part into gpsVP, the rest is done by others.
GPS height error
Thanks for the reply cybermaus, unfortunately I am not sure what you are saying.
What did you notice ? Zero in field 11 of the GGA message?
Are you suggesting that most chipsets put 0 in field 11?
This is certainly not the case with my Mio A701 with the Sirftech chip, which puts 50.5 into that field and gives me accurate altitude values.
It seems (I am still learning) that there are two ways to get the information from the gps, either parsing the NMEA messages or using the MS API.
In my case it seems that the first way fails and the second works.
Which does your program use, and how have you made the correction?
Thanks (in advance) for your patience with these questions.
Well, yes, I am saying that the devices I encountered, all gave 0 in that field, except actual Garmin handhelds connected by serial. Also, I learned from reading in the internet, that many other people noticed the same. But that does not mean there are none. I believe any real Sirf III will do it correct, but I have a Sirf II dongle witch also does it wrong.
It even turns out there are a few devices, that put 0 in that field, but already subtract the correct separation from the geoid height, so you should not correct the value yourself.
The geoid separation is stable, and well known, you can look up the value for every coordinate on the internet. Also it varies only with a few meters per degree in the steepest places. The steepest separation is west of the mountains range of Peru. The biggest separation is a 100 mtr hole in the sea south of India.
What I did was program a hardcoded matrix with 10 degree resolution (to keep it small) with the correct geoid separation value. The program than takes your coordinates, and *interpolates* these in the matrix, to find your separation. I found it will yield the correct value within 1.5 mtrs, which is well within the GPS precision.
Also, if my program finds there is already a separation value in the field, it will *not* apply the correction, because it knows the chipset behaves properly.
If you want more details, browse the source to gpsVP. Unfortunately, you will not be able to use it for other programs if you are not a programmer or do not have access to the source of those other programs.
As I said, if I have some time, I will check out the MS API you mentioned, there is indeed a new API data structure in WM 6.1 and above, I played with it, but I did not check it for this parameter specifically. However, I am skeptical. I find it more likely the programmer from MyGPS did something similar as myself.
As to your Mio A701. Good. I said I did not encounter any other than the dedicated GPS handhelds from Garmin, but that does not mean there are none. To be quite honest, I only held 5 or so non-Garmins, so who knows.
I think the problem is not widely recognized because most people use GPS in 2D, for navigation. This 3D is more for people doing hiking, with programs like gpsVP or Ozi. Pilots and paragliders may have a 3D GPS, but know better than using it for altitude (I am a paraglider myself)
BTW: Ozi also does not correct the value, I checked.
GPS height error
Thanks again for the comprehensive reply.
I am surprised that you say that most GPSs give incorrect altitudes due to the missing geoid separation field, since I have seen a lot of discussion about this problem, mostly several years old, so I assumed that any modern chipset would have it sorted. I am also surprised that no-one with an HTC Touch HD (for instance) has complained about it.
Do you have an HTC Touch HD, and are therefore confirming that this model is faulty? That is - the NMEA message GGA field 9 gives height above ellipsoid and field 11 is 0.
I would still appreciate input from any other HTC Touch HD owner on the values in these fields.
As you say, and as I have seen, ozi explorer does not do a manual correction in the way you do. It does not need to when the NMEA messages are correct since field 9 is specified to contain height above MSL.
It does, however, have an option to subtract the geoid separation field from the value in field 9 to correct for the (other faulty) case where field 9 contains the height above ellipsoid and field 11 gives the geoid separation. If I use this option on the HTC it changes nothing, since field 11 is 0, but on the Mio it then gives me heights 50m too low (as would be expected).
I will now try your program.
Well, this not just my program, I only supplied 1% of the code, it just happens to be this particular part.
Anyway, yes, I do have a Touch HD. And yes, I am talking about the GGA message fields. One with altitude according to WGS84 ellipsoid, and one with the separation of said ellipsoid from the actual geoid according to the '96 model. Probably indeed fields 9 and 11, though I have not looked at the code for a few months, but it sounds about right.
Your MIO has a real Sirf III chipset. I would have expect that to work, because my Garmin also has a Sirf III in it. But as stated, I have a dongle with Sirf II, and that did not have the correction. Neither did the other dongles I have, but granted, they are all a bit aged and budget quality. Maybe my experiences are a non representative sample
But I confirm the Touch HD is faulty, and I suspect other HTC's and many other brands & models with non-dedicated chips. These do not have a real GSM chip, but a generic secondary ARM cpu shared with the GSM radio function and other radio functions like WiFi, UMTS, Bluetooth and probably even FM.
----
The way I understand it, the original GPS specifications did not have the separation specification. In '84, they simply did not realize that a simple mathematical ellipsoid model for earth and earth gravity was so incorrect.
It was only after the launch of the GSM network that they started to realize that there were so many fluctuations in the local gravity of the earth, which causes this effect, that they came up with the new '96 numerical geoid, rather than the mathematical '84 ellipsoid. Or something like that.
Of course, if HTC wanted, they could program the similar correction into the radio chip firmware, it is simple and small code. And it is 14 years after the fact. But I think they simply do not see the need.
----
If you start to use gpsVP, and you go hiking off-road, please note I find it best to use with GARMIN vector maps. I can also downloads Bing and Google raster maps, but those are not good in off-road data, though the satellite view is sometimes nice.
All in all, the program is a bit 'coarse' in its use. If you understand what it does (vector maps and preloaded cache for raster maps), it has value, but you will not be able to impress friends who are used to the smooth Google map application.
GPS height error
Thanks again cybermaus.
I tried the gpsvp program, both in the htc and the Mio. On both machines I got a correct altitude and a value of 51 for the geoid separation field, which compares well with the 50.5 which appears in the GGA messages on the Mio, so it looks as if your calculation works well.
I tried changing the value of the Geoid separation parameter in the setup options, trying auto, always and never, and in all cases got exactly the same results for altitude and geoid separation, so I am a bit puzzled. Does the setup option change anything, or does one have to do something else to activate it?
Well, the setup part of it is not complete yet, I think it is essentially always auto. Need to find the time and motivation to complete the coding. Log a case in the gpsVP website please.
I do not have much to contribute, but yes, living in Switzerland and hiking in the mountains I have also noticed that the altitude was wrong.
I first thought it was the inherent imprecision of the GPS, but then remarked that it was systematically off by several tens of meters.
I was also surprised that nobody complained, now I know that I am not alone.
I wish that programs like Ozi could apply the correction, or at least allow entering a fixed offset.
Thanks to cybermaus for explaining it.
Will give a try at gpspv.
GPS height error
Thanks marder.
Could you try running visualgps with the log activated, then look at the log file for the message $GPGGA? If the 11th field, between the two Ms, is always 0 then it proves the point.
I remain very surprised at the lack of complaints about this, if it is such a common problem.
But why would people complain? Or even notice?
The height error is absolute, but in differential measurements, it still works well. In other words, if you have a height, and you walk up a hill, it will give you a higher height (most of the time, and within margin of error). And most people are not aware of their absolute altitude anyway. Lets face it, if you live in Moscow, and the device tells you you are at 200mtrs, why would you distrust it?
I only noticed because I live at sea-level (Holland). You only noticed because you live in an area with above average separation, and got annoyed with two devices giving you 2 different values. And marder probably scratched his head when encountering these "xxxx above sea" markers which you get when hicking in the mountains. He would not encounter such markers in the city he lives.
Face it, if you had not had you Mio, would you have noticed? Or be able to confirm it?
Of course, once we know, we think it is unacceptable. Thats human nature, myself included.
But there are other people who did see it. Searching for keywords geoid and gps shows this thread, and the program appears also to have a fixed geoid position.
Like I said before, did you try different radios? As this affects the functions of the GPS. I had this problem too but flashing to the latest radio cleared it right up, along with making the gps now lock on with a strong signal within 8 seconds. Going through the complicated route of coding things to fix it is a bit pointless when others have fixed it before you. I'm not saying it will definitely clear it up for you, but taking 20mins to try a few radios is probably worth your time.
Oh and a good way to tell if it's accurate or not, for anyone else wondering, is to check on google earth for the "elevation".
GPS height error
cybermaus, I expect you are right - people do not notice.
I certainly did notice, independently of the Mio, by comparing the heights marked beside the autoroute that I use with those displayed by the HTC.
But you are right in that without the experience of the Mio I might well have assumed that it was due to some inherent inaccuracy in the GPS system and not searched further (and not found the thread at http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=10915 where this is all explained).
stuntdouble, thanks for the input. I assume that flashing new radios is trivial for you, but somewhat more traumatic for people like me, aware that a problem during the process can end with a dead phone. Could you perhaps tell me
1. Does it actually correct the problem i.e. does the NMEA message $GPGGA give a non-zero value in field 11?
2. Do I lose all my programs and data in the process
3. Which of these many radios do you recommend
4. Where do I find it/them
5. Are you sure it will work on my phone (which is apparently of Malaysian origin)?
6. What is the procedure?
Sorry for the interrogation but this is not as easy for me as it is for you.
For information I have:
ROM version 1.18.707.3 (23358) WWE
ROM date 12/10/08
Radio version 1.09.25.14
Protocol version 52.49a.25.26U
rpettipher said:
stuntdouble, thanks for the input. I assume that flashing new radios is trivial for you, but somewhat more traumatic for people like me, aware that a problem during the process can end with a dead phone. Could you perhaps tell me
1. Does it actually correct the problem i.e. does the NMEA message $GPGGA give a non-zero value in field 11?
2. Do I lose all my programs and data in the process
3. Which of these many radios do you recommend
4. Where do I find it/them
5. Are you sure it will work on my phone (which is apparently of Malaysian origin)?
6. What is the procedure?
Sorry for the interrogation but this is not as easy for me as it is for you.
Click to expand...
Click to collapse
1. Yes. All seemingly corrected.
2. No programs are touched as long as it's a successful flash. Radio is separate from the rest of the device's memory. Just backup your device with Sprite Backup or SPB Backup before you try it, in case you do need to do a hard reset. This way you can get your device back to exactly the way it was before.
3. The one in my sig fixed mine. However every device is different so you would need to find the best radio for your own device. I'd start with the latest and work backwards though if I were you.
4. Get them here.
5. If it doesn't work, it doesn't work. You can always re-flash your old radio if you wish. However I suggest you ask in the radio thread before trying, which radio would be best for your operator. There will be plenty of people who will know this and have tried it before you have I'm sure. The radio info is based on your operator and not on country of origin for the phone.
6. Easy procedure is in link above.
I'm not guaranteeing this will fix your problem, but it really is easy to do and well worth attempting as like I said it fixed it easily for me. It also increased battery life dramatically, and the faster gps fix like I mentioned before.
I understand that it may seem difficult on first read. I felt that way too when I first tried it. But it really is very simple and I was wondering what I was scared of after I tried it. Just follow the instructions in that thread carefully and there won't be any problems. If you use windows vista/7 then make sure you run as admin if you are flashing via the pc. Good luck.
Sorry guys.
I have followed most of the radio updates, and never noticed this being fixed. I have to admit, I never checked since I updated to 1.17 radio, so I checked just now, and it still reports 0 meters separation and at 43 meters altitude (at the coastline of Holland...) So for clarity, I logged out the NMEA messages, and all $GPGGA mssages give 43.5,M,0,M for field 9 through 12. On the latest 1.17 radio.
While theoretically possible they fix it in the radio, it still has not been done, not even at 1.17. I guess you either have the luck of living in a region where geoid and ellipsoid are very close to each other, and/or you are not aware of your true absolute altitude.
GPS height error
Thanks guys now I am confused.
I suppose we need to know what "seemingly corrected" means.
Has stuntdouble actually seen the NMEA messages with the correct data?
Rom update
I do not know about taking "20mins to try a few radios" - I have spent several times that amount just reading some of the information relating to flashing!!
But then I am a slow reader.
Following the links I eventually found what is apparently the 1.17 radio rom on a support page of the HTC site.
I am puzzled to see that it is described as for South Africa only, and concerned to see that it says it is only for ROM version less than or equal to 1.14.421.5. when my ROM is 1.18.707.3.
Should I be concerned and should I also be concerned about the caution when starting the program that it will destroy all the information on my phone?
Just being cautious, especially as I do not know what improvements if any I will see.
I like to alter most of the framework files in the ROMs that I use so that I can make my themes more blue instead of the green in the ginger clones that are out right now. In doing so, I noticed something wrong with the stat_sys_signal image files that will make the phone look like it is getting a better cell signal than what it really is. There are five stat_sys_signal files that are stat_sys_signal_0, stat_sys_signal_1,stat_sys_signal_2, stat_sys_signal_3, stat_sys_signal_4. The trailing number on each file should have a corresponding "bar" image with that number of bars highlighted, indicating your signal strength. So file 0 = 0 bars, file 1 = 1 bar, etc. What I have found in most of the new 2.2.1 ROMs is that these images have been shifted to make the cell signal look stronger (not saying that is intentional). So looking at the attached file, you will see the following:
stat_sys_signal_0 = 0 bars
stat_sys_signal_1 = 2 bars
stat_sys_signal_2 = 3 bars
stat_sys_signal_3 = 4 bars
stat_sys_signal_4 = 4 bars
With this scheme, there is no instance where you would get 1 bar signal and would appear to get 4 bars when you only got 3, 3 bars when you really have 2, etc. You ge the point.
Not intending to flame anyone and without looking at everyone's ROM, I have noticed this same problem in stock Phoenix, P10, Darky, and Doc's ROMs. Also, I've noticed that most of the non-stock themes have it correct and so might would appear that your signal strength dropped once you apply the theme.
I've loved using each of these ROM's but thought I would point it out so it might be corrected and people would know why it looks like the signal dropped. I hope this helps.
Nice Find! I've noticed that some of the newer roms seem to show higher signal strength and now I know its really just being displayed wrong.
Now the question...how to fix it? Preferably with a CWM flashable zip!
When I made my gingerbread theme for the JJ4 I had noticed this as well. I fixed it by taking the gb sys_stat image and resizing and editing it so that you would still see 0-5 signal bars but with the gb shape/color/glow.
http://forum.xda-developers.com/showthread.php?t=873942
Checked mine, it's fine.
It's a pretty easy fix. I think it's no big deal but the developers may want to update it on their next releases. I'm guessing it was pretty much a cut and paste issue that proliferated it throughout multple ROMs.
Darky used to intentionally do this cause he said he did tests vs other phones right next to the galaxy s and.the galaxy s had a lower signal signal bar strength than other phones with the same exact signal quality going to them both. I haven't personally tested this so I can't say if its right or not or if he even still does that. So maybe other devs followed suit or whatever I just know at one point it was done on purpose, can't say what the reason is now cause im not gonna speak for other devs
Signal bar are always relative... it's impossible to compare them to another phone.
I figured as much. I'm fairly new to my Captivate and XDA, so don't know the background. I see this all the time in product development. As an EE design engineer, I find all the time that people don't know why we do things the way we do, just that it's always been that way and "it works". It's a lot of copy and paste engineering. No one person has time to go through all the details every time a change it made.
When I first saw this, I thought of the infamous "iPhone 4 fix" for their reception probem. Now I know exactly what they did!
ALL,
I started this new thread becasue I have swap use my donor phone as htc evo , try to get more speed but it seems not at all. My donor phone most of time lock on EV(evdo) the internat is must more fater than my htc evo(max 128 b) in 1xrtt most of time. from time to time it show 3g but actually speed is very very slow.
Here is my origial setting , was getting 3G icon but speed is around 100-130 b/s
ASEBAND 2.15.00.11.19
KERNEL
2.6.32.17-GEE557FD
HTC-KERNEL at AND18-2#15
BUILD NUMBER
3.70.651.1.CL294884 RELEASE-KEY
After I flash to all kind of rom's and change my kernel, PRL, I am 99% on 1x icon, speed is aver 128k. I can not go back to original configuration since RA issue. Please share some idea how to fix this issue.
reflash radios, flash sense rom and update profile
1: Radio Flahed to : EVO_Radio-2.15.00.05.02_WiMAX-27243_PRI-NV-2.15_003_signed.zip
2: ROM to Calkulin's_EViO_2_ROM_v1.8.zip
3: Lost the signal strength, phone was not stable, able to make outgoing call but not able to receive call. Went to QPST, the system table been alter
it should be automatic but the 1st got altered.
Put RA 2.5.07 back and flash it back to
Android Version 2.2
BaseBand 1.39.00.04.26
kernel Version [email protected]#15
Build Number 3.70.751.CL294884 release-keys
Software Number 3.70.651.1
PRI Version 2.15_003
PRL 60666
3G icon is show up like original but the speed testing is
DL--> 130K
UP--> 144K
Ping time- 700 ms
It is workable when using data compare I went to Android 2.3. so what could be wrong, Can they lock my data rate as 1x ?
I updae profile, same result
nttcar said:
ALL,
I started this new thread becasue I have swap use my donor phone as htc evo , try to get more speed but it seems not at all. My donor phone most of time lock on EV(evdo) the internat is must more fater than my htc evo(max 128 b) in 1xrtt most of time. from time to time it show 3g but actually speed is very very slow.
Here is my origial setting , was getting 3G icon but speed is around 100-130 b/s
ASEBAND 2.15.00.11.19
KERNEL
2.6.32.17-GEE557FD
HTC-KERNEL at AND18-2#15
BUILD NUMBER
3.70.651.1.CL294884 RELEASE-KEY
After I flash to all kind of rom's and change my kernel, PRL, I am 99% on 1x icon, speed is aver 128k. I can not go back to original configuration since RA issue. Please share some idea how to fix this issue.
Click to expand...
Click to collapse
Why is it that every single thread that I've read today makes no sense at all? Does the XDA forum have some sort of "garble" function that takes all of the text in a thread and just jumbles it into an illegible mess?
Seriously...Is it that hard for people to take a second, read what they wrote, and correct it so that it doesn't look like a chimpanzee is typing with his feet? Jesus...
Finally Got it to work now, from ##data# chose evdo (HDR only) and from ##debug# chose evdo engineering, now all filed been populated, speed test 600k dl, 340 up.
UndeadCircus said:
Why is it that every single thread that I've read today makes no sense at all? Does the XDA forum have some sort of "garble" function that takes all of the text in a thread and just jumbles it into an illegible mess?
Seriously...Is it that hard for people to take a second, read what they wrote, and correct it so that it doesn't look like a chimpanzee is typing with his feet? Jesus...
Click to expand...
Click to collapse
LMAO!!!!!! Chimpanzee typing with its feet..... Classic!!!! *Wipes tears*
After almost one month of debugging and reading, Finally I got EVO working on 3g speed. It is not the rom, not the radio not the kernel. ##786# is the magic, I reset it, let it through with activation first time, does not work, reset it again, cancel activation, put NVRAM back, manually enter HA/AAA, work !
UndeadCircus said:
Why is it that every single thread that I've read today makes no sense at all? Does the XDA forum have some sort of "garble" function that takes all of the text in a thread and just jumbles it into an illegible mess?
Seriously...Is it that hard for people to take a second, read what they wrote, and correct it so that it doesn't look like a chimpanzee is typing with his feet? Jesus...
Click to expand...
Click to collapse
Lol I was trying to read this too lol
Sent from my Vanilla Ice Cream evO²·³·³
Hi all, I know there are threads already created for questions etc but I've an extensive list of them and I don't think its appropriate to spam them in someone else's thread. And I'll update the first post of the answers and replies I've received for the questions I've posted!
My phone's information: will5's MIUI ROM 2.5.25 GB 2.3.7
My list of questions
Android OS
::Hard rebinding hard keys::
Is that possible? My power button recently got damaged and its really tough to press the power button now which is quite a problem, is there any way to rebind the power button to say the camera button? (specifically the 2nd-click of the camera button, not the first click (focus)) MS2Toolbox is able to wake screen with the camera button but thats just soft-sided and I need to hard bind for turning on the phone and using the recovery etc... :crying:
::Allow app to stay active when screen-off and when not in foreground:: http://forum.xda-developers.com/showpost.php?p=29658020&postcount=95
I want to let my app, specifically Opera Mobile, to be constantly active as I run a script (user javascript) on it which repeats its function periodically. Is there a way to keep it active throughout deep-sleep, or when in the background? Currently its working well when I switch the screen off as long the app was in the foreground. The script and Opera Mobile still runs perfectly and I do not experience battery drain (weird). I have been doing so for the past few months and it takes probably only 30% of my battery overnight when I sleep despite the periodic data connection. However, this didn't happen on the MIUIv4 ROM when I tested it. The app is 'frozen' or suspended, it seems, the moment I switch the screen off. Tried apps which disabled deep sleep etc but didn't work. Any ideas?
Overclocking
::What are the default VSELs for the respective frequency for MS2?::
I know there's one here http://forum.xda-developers.com/showpost.php?p=11620994&postcount=1 by santiemanuel, but it gives VSELs WAY above those I'm using or the defaults from MS2Toolbox. Say, for 300MHz, the stock vsel is 33 and 30 is considered unstable. How ever the default in MS2Toolbox for that frequency is 17 if I'm not wrong. I'm using that at the moment and it seems to be running fine (used powersave governor to enforce 300MHz to test it out). Just to confirm, should I really follow that table?
WiFi
::Changing Milestone 2's WiFi MAC address::
Hi guys, I've been trying to look for a way to change my M2's MAC address but have not been able to get it to work.
I've googled up for methods but the common ones do not work.
Tried so far:
- The nvram.txt file
Can't find it in the usual folders stated.
- busybox ifconfig tiwlan0 hw ether <MAC>
- busybox ip link set dev tiwlan0 addr <MAC>
Tried these two commands but didn't work either in terminal emulator. Even did the off-on-immediately spam commands but no luck.
Unsorted
Code:
http://forum.xda-developers.com/showpost.php?p=29675172&postcount=905
::SOLVED::
Overclocking
::How do I check the current VSEL and frequency at any point in time?::
I'm trying to underclock and ultra-undervolt to save as much battery as possible and want to know how's the selected governor working in order to manually optimize the settings to my preferences.
::How do I know its an unstable VSEL?::
Q: Quite vague a question but... as said in the first question, I'm running 300MHz at a VSEL of 17 instead of 33, nearly half of the stock. How would I be able to tell if its unstable? When I'm running in powersave governor, it shows that the 'system' process stopped responding at boot and I've the wait/close option, but after selecting wait the dialog disappears and the phone still works as per usual. However its very sluggish, clearly because of the underclock. Regardless, does the system process being unresponsive at the start shows it is unstable?
A: djlooka via PM
djlooka said:
...My suggestion is: try with that setvsel app for defy (see my answer in the CM9 thread) which comes with a useful mini-stress tester app (you can install it from within the main OC app). It can stress test every single freq step, so you can find its 'sweet-spot-vsel'.
One could also think that there's some advantage in fine tuning the middle steps. IMHO it's wasted time
After some days of tweaking, I realized that our phone will stay in the two the middle steps (combined) for less than 5% of the time. So even if you could save some % of the power by losing 1 or 2 vsel points (let's say 10% of the original vsel), the "on the road" gain would be infinitesimal (10% x 5% = 0.5%).
Anyway it's fine to OCD a bit even about those 2 steps
My final word is: find the lowest possible vsel for both the top and bottom freqs by stress testing. To be extra careful, raise them by one point for rock solid.
E.g.: 300-22 is the best combo for my lowest step -> I put 300-23, and so on.
Click to expand...
Click to collapse
::3 steps shown in the bootloader but 4 shown in MS2Toolbox::
Q: This has been bugging me recently. I've read recently that the M2 has 4 steps for its CPU. So the CPU actually follows the 4 steps shown in MS2Toolbox or the 3 in the bootloader? Note: When I change the values in the bootloader, the values changes respectively in MS2Toolbox for the 2nd,3rd,4th rows (did not tick auto apply in M2T to prevent overlaps with bootloader settings). But the 1st row shows values lower than the one in the 2nd row automatically.
A: djlooka @ http://forum.xda-developers.com/showpost.php?p=29806494&postcount=908
djlooka said:
...Our phone, instead has 4 steps (300, 600, 800, 1000 MHz - the same as the Defy+).
AFAIK, when you set a configuration which allows only 3 steps (in the bootmenu), the hw internally adjusts to have the last 2 steps equal (e.g. 300, 600, 800, 800 MHz).....
Click to expand...
Click to collapse
Applications
MX Player - Does not require codecs. If it requests for ARMv7 NEON codec, get the NEON version of the player instead.
Typical Complains / Rants:
1. GPS does not lock
2. GPS takes ages to lock
3. Keeps loosing signal / picks up very few satellites
4. Lock is not consistent, and fluctuates
Since quite a few users have struggled with GPS issues (including myself), I thought that I'll share my experience. I'm on Jellytime R10.1 and I believe that the GPS issues (as quoted by several users) is not related to the ROM. I've had GPS issues with a few other Custom ICS/JB ROMs. Instead it's related to the settings in the files,
1. /etc/gps.conf &
2. /system/build.prop
I have tried the fix provided by both MarcoHD (FasterFix) & crypted (AGPS Patch) and have had mixed, but unsatisfactory results.
So, I researched on the web for GPS lock solutions, for DHD (In the UK). Based on several findings I have been playing with my settings and have finally achieved a state where I can a really fast lock, with atleast 6-8 average Satellites. Configuration that works for me:
1. gps.conf needs to have correct entries for NTP_SERVER. Best way to locate those entries is to go to http://www.pool.ntp.org/en/, click on 'Active Servers' on the right hand side for your continent, and choose your country. At the top you'll see a set of 3 or 4 servers, and all of those need to be set in gps.conf, as below (UK in my case)
NTP_SERVER = 0.uk.pool.ntp.org
NTP_SERVER = 1.uk.pool.ntp.org
NTP_SERVER = 2.uk.pool.ntp.org
NTP_SERVER = 3.uk.pool.ntp.org
Remember that these should be the only NTP_SERVER entries in the file
2. I found this suggestion in the AGPS Patch (by crypted) and it worked for me. Edit the entry in the build.prop file as below:
ro.ril.def.agps.mode = "1" (Generally this value is set as "0" or "2"
After making the above changes, reboot the phone. Then load the GPSStatus app, and you'll see that it'll start latching onto Satellites, give the app sometime until it gets a stable lock, and you're good to go.
Disclaimer: I'm not an expert, and these are settings that worked for me, based on my limited research.
Now, the only outstanding issue I'm facing is the accuracy of the lock. I had a 100 mile journey today using Copilot, and the lock was absolutely stable, but accuracy was left wanting. Typical issues were encountered when there're roads that go under/over the motorway, parallel roads, slip roads, etc. The Sat Nav kept deviating into these other roads before reverting to the motorway on which I was.
So, the accuracy will be an area where I'll need more research, and suggestions from all ..
so other such as XTRA_SERVER, intermediate, c2k_host, supl_host etc shoud remain?
Yes I haven't disturbed any other parameter.
Sent from my Desire HD using Tapatalk 2
Same problems for me. I think my gps is not working in ics and jb roms. Need to check again with gb backup ROM..
Sent from my Desire HD using xda app-developers app
dg170775 said:
......
Now, the only outstanding issue I'm facing is the accuracy of the lock. I had a 100 mile journey today using Copilot, and the lock was absolutely stable, but accuracy was left wanting. Typical issues were encountered when there're roads that go under/over the motorway, parallel roads, slip roads, etc. The Sat Nav kept deviating into these other roads before reverting to the motorway on which I was.
So, the accuracy will be an area where I'll need more research, and suggestions from all ..
Click to expand...
Click to collapse
You could try this setting:
---------------------------
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# use only increment/decrement of 10 and DON'T go below 30
ACCURACY_THRES=5000
---------------------------
A thousand thanks to you.
this really has solved my gps issue...
now my phone locked damn fast than my girlfriend unrooted.
thank you very much.
havitoc said:
A thousand thanks to you.
this really has solved my gps issue...
now my phone locked damn fast than my girlfriend unrooted.
thank you very much.
Click to expand...
Click to collapse
That is really good to hear. Feedback on how's the accuracy when you use a sat nav..
Sent from my Desire HD using Tapatalk 2
Worked well for me too. Inspire 4G on cfX 0927. Now locks within seconds. 9 satellites.
bananagranola said:
Worked well for me too. Inspire 4G on cfX 0927. Now locks within seconds. 9 satellites.
Click to expand...
Click to collapse
How long did the first lock take?
Just tried these tweaks out and it's searching for sats now.
first lock will be longer (about 20-25 secs), and preferably try the first lock out in the open (not indoor)..
Also, if you're using GPSStatus App, then you can see that it'll keep picking up one by one SATs ..
PDub11 said:
How long did the first lock take?
Just tried these tweaks out and it's searching for sats now.
Click to expand...
Click to collapse
Nearly a minute. After that, several seconds.
dg170775 said:
Typical Complains / Rants:
1. GPS does not lock
2. GPS takes ages to lock
3. Keeps loosing signal / picks up very few satellites
4. Lock is not consistent, and fluctuates
Since quite a few users have struggled with GPS issues (including myself), I thought that I'll share my experience. I'm on Jellytime R10.1 and I believe that the GPS issues (as quoted by several users) is not related to the ROM. I've had GPS issues with a few other Custom ICS/JB ROMs. Instead it's related to the settings in the files,
1. /etc/gps.conf &
2. /system/build.prop
I have tried the fix provided by both MarcoHD (FasterFix) & crypted (AGPS Patch) and have had mixed, but unsatisfactory results.
So, I researched on the web for GPS lock solutions, for DHD (In the UK). Based on several findings I have been playing with my settings and have finally achieved a state where I can a really fast lock, with atleast 6-8 average Satellites. Configuration that works for me:
1. gps.conf needs to have correct entries for NTP_SERVER. Best way to locate those entries is to go to http://www.pool.ntp.org/en/, click on 'Active Servers' on the right hand side for your continent, and choose your country. At the top you'll see a set of 3 or 4 servers, and all of those need to be set in gps.conf, as below (UK in my case)
NTP_SERVER = 0.uk.pool.ntp.org
NTP_SERVER = 1.uk.pool.ntp.org
NTP_SERVER = 2.uk.pool.ntp.org
NTP_SERVER = 3.uk.pool.ntp.org
Remember that these should be the only NTP_SERVER entries in the file
2. I found this suggestion in the AGPS Patch (by crypted) and it worked for me. Edit the entry in the build.prop file as below:
ro.ril.def.agps.mode = "1" (Generally this value is set as "0" or "2"
After making the above changes, reboot the phone. Then load the GPSStatus app, and you'll see that it'll start latching onto Satellites, give the app sometime until it gets a stable lock, and you're good to go.
Disclaimer: I'm not an expert, and these are settings that worked for me, based on my limited research.
Now, the only outstanding issue I'm facing is the accuracy of the lock. I had a 100 mile journey today using Copilot, and the lock was absolutely stable, but accuracy was left wanting. Typical issues were encountered when there're roads that go under/over the motorway, parallel roads, slip roads, etc. The Sat Nav kept deviating into these other roads before reverting to the motorway on which I was.
So, the accuracy will be an area where I'll need more research, and suggestions from all ..
Click to expand...
Click to collapse
What the hell dg!!! I leave You alone for a day ore 2 in here and You go of creating a thread about gps!!!!GREAT!!!:good::laugh:
There has been allot of anger on the Jellytime....the usual, when a ROM becomes interested and starts working smoothly. Allot of folks gets on the thread and it becomes a bit uncontrolled.....oh well!
So what is this about neither the one ore the other gps fix/patch works for You my friend.....hmm....i forgot to tell You that way back i implemented some files i found on a thread on the inet......that i cannot remember the name of....5 files.
These files where drawn out of the 2.3.5 gb HTC stock ROM and addresses the HTC gps Worldwide......before applying either the faster gps fix ore the agps patch, i did have gps connection, but very slow, so for my part, what faster fix did, was making the connection faster. Looking at Your above statement, it resembles the code within these files. i could copy them from my phone and You could have a try with them on Your phone.
The gps.spade.so, goldfish and saga goes in /System/lib/hw
The liprpc.so goes in /System/lib
The gps.conf goes in /System/etc
Here is my gps.conf script:
NTP_SERVER=0.europe.pool.ntp.org
NTP_SERVER=1.europe.pool.ntp.org
NTP_SERVER=2.europe.pool.ntp.org
NTP_SERVER=3.europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=1
C2K_HOST=c2k.pde.com
C2K_PORT=1234
SUPL_HOST=FQDN
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
SLP_TYPE=FQDN_PHONE
PROTOCOL_TYPE=Non_TLS
PHONE_TYPE=UMTS
ACCURACY_THRES=5000
CURRENT_CARRIER=common
DEFAULT_USER_PLANE=TRUE
REPORT_POSITION_USE_SUPL_REFLOC=1
I Use Europe instead of just Sweden...ore as with You U.K
I have an accuracy of between 4-14 meters out doors and 10-20 meters indoors.....
I have attached 2 .zip with the files. One with the actual files and a .txt with where to put the files, as i already described above.
So this is the only files or just NTP_SERVER entries and leave everything else there?
I'll try Geko's file first. and report back.
hmm, the accuracy, within 100m
but sometime will lost, i think that was the navi app problem.
overall is super awesome and fast.
get statellite & locked within 10seconds
well done man
Hey geko, that's a lot of info.. I will go through the details and try out..
Strangely if I use the Europe NTP servers I don't get more than 1 or 2 SATs but the UK ones work great for me.. that's why fasterfix didn't help.
I guess I was so happy that my research (fueled by your initial help ) worked that I had to share...
Sent from my Desire HD using Tapatalk 2
Remember that some desire hds have a hardware problem where the GPS antenna is not making good contact inside try pushing on your antenna wich is the square cover over the LEDs. if you get an instant lock this is your issue
Sent from my HTC Desire HD using xda app-developers app
Fast GPS FIX
Use this zip and you should get a faster fix on your DHD....
Hit the Thanks Button if i helped you:laugh:
Looks like I've managed to break my GPS Configuration now
I managed to get the GPS working as per the OP (on JellyTime R10.1), but then I flashed Jellytime R12 and my GPS again does not latch any Sats, with the same settings as in the OP.
dg170775 said:
Looks like I've managed to break my GPS Configuration now
I managed to get the GPS working as per the OP (on JellyTime R10.1), but then I flashed Jellytime R12 and my GPS again does not latch any Sats, with the same settings as in the OP.
Click to expand...
Click to collapse
Well....by the looks of it DG, RB has mad some mods on the R12 getting sat stats quicker.....the flip side is that it does not work for Europe....try flashing faster fix and the get into Your gps.conf file and modify to Your settings!!! I am not 100% sure, but i think that this will fix Your connection....
Try.....Try and Try again.....and if that does not help......reflash.....hopefully You have dun an nandroid of Your 10.1......if not....hmm....
Hey I can confirm that the GPS works on R12 without making any changes to any files. RB has cracked it...
But, once you've used GPS based apps, the gps needs to be switched off and on, to get lock again.
But accuracy still an issue..
Sent from my Desire HD using Tapatalk 2