I'm not going to spend the time going through, checking, and re-listing ROM's using this.
Yet, the title here said "Tentative Support" based on results from a handful of users who tried this on their own time. After getting more information from this thread, as it was intended to be used for, I decided to not support it. The title has reflected that for a while now.
Again I challenge you to provide a working solution that is superior than this one for most anyone using Qualcomm chipsets and for a number of people using ROM's ported from Qualcomm-based phones.
It is irrelevant that you would or have donated to any project on XDA or elsewhere. The entire reference to any sort of donation revolves around users who feel that they benefit from using the v3.x trunk versus the v2.x trunk as the 3.x utilizes custom servers. Nothing more, nothing less.
This discussion from you has done nothing to further any development or understanding that many of us seek to ascertain. I'm done with this particular conversation.
I won't argue about this tweak if he don't use his custom ntp and xtra server. what he did now is giving placebo affect that his server is best. Default server is very reliable, and I won't count on his server. On the other hand,
if his server down, most people using his patch will be troubled. And another thing, he is using v2.x claiming it is still using default server. What will you do if you see Froyo and then there is a Gingerbread claimed to be superior, will you install Froyo instead of Gingerbread. Of course everybody will install v3.x with his server.
Angeldeath setting here
http://forum.xda-developers.com/showthread.php?t=953630 is better if you have a qualcomm chip. Even I am rather skeptical about ntp server, in logical, using the server closest to you will give faster response. Just ping a server, a server located in the same country will surely give faster response. This crypted argument stating that his server is the best is unreasonable.
http://forum.xda-developers.com/showpost.php?p=21416086&postcount=38
He wouldn't want to accept others tweak is better than his, just read his statement. Simple argument above will prove Angeldeath setting is superior.
And xtra.bin, he just mirror it from original server, and he claim that he generate it or at least he want to people think so.
"I guess the original didn't fall below our process threshold for the rebuild and kept default build."
http://forum.xda-developers.com/showpost.php?p=21384629&postcount=19 What does this mean, too sophiscated words I don't even understand.
There is still a lot of people doesn't know well how GPS works. If I say, try to compare MY tweak with default setting. First, get a GPS lock, see how long it takes. Second, install MY tweak, try to lock again to see how long it takes.
Of course second try will always faster. It is hot/warm start. You don't even need to set anything, and the second lock always faster if you wait no more than a few minutes.
Even reboot doesn't clear the warm start.
But people who doesn't know GPS well will think MY patch was so great, return to forum and say MY patch was so great.
Another variable is GPS satellite, weather, and building blocking gps visibilty. Sometime there is just not enough satellite visible in your location. There a about 24 active GPS satellite rotating earth twice a day. Some unlucky guy will try to lock GPS and fail within for some reason, maybe he just try it by the windows, and most satelite is behind the windows. and maybe there is bad weather, and when he try his patch, the sky just so clear, luckily a lot satellite above his position, and he will return to forum say his patch was so great.
Crypted, as I said before, set your setting to default server, and I won't bother you. Keep using your server, what you do is breaking people's GPS.
---------- Post added at 09:44 AM ---------- Previous post was at 09:05 AM ----------
@popcorn,
I have try to learn so much about defy's GPS. I have spent 6 hour everyday for more than a month, trying to solve GPS problem, until I give up and ask in the Defy General forum.
Defy's gps driver binary is identical to milestone 2. Motorola is too lazy to update the driver, its last driver is dated July 2010. I have been downloading almost 20 rom from various device I don't own, trying to take the binary out of it and apply in defy but failed. Another device is cliq 2, but still dated July 2010.
About lto.dat, it is not enabled in driver. Closest possible enabled lto from motorola is XOOM, but it is tegra device, and to use that binary, we might need a custom kernel, that means we need unlocked bootloader.
Atrix2 is lto enabled, but it seems to use completely different binary.
Most samsung device and LG is lto enabled, they both use similar binary, but different from what motorola used.
What you see in gpsdata.nvs is data downloaded using SUPL, not lto.dat. While learnstore.bin is more something needed for wireless location, it create database of your locked gps position and what cell signal you have. Next time when you enable use wireless network, it will identify cellid, and give use approx location from database it created in learnstore.bin.
And defy suffers the same inaccurate position as SGS. SGS suffers bad antenna and bad accuracy. Because so many people complain, samsung updated their driver, and solved or at least minimized the bad accuracy. If I'm not wrong, SGS fixed their problem at near end of 2010, so our driver is still outdated as it is from July 2010.
About lto.dat, maybe motorola pay less for the chip without lto enabled. We now can just wait motorola update their driver, or wait for other OMAP3 device from motorola and take the driver to defy.
About bad accuracy, it seem the problem lies within broadcom. I don't know if the chip is bad, or broadcom makes bad driver implementation in linux. Broadcom uses too much predictive location. You can see when we drive, even when we stop, our gps shows up still moving.
Search youtube for iphone4 umts vs cdma gps, umts version uses BCM4750, same as ours, although not as bad accuracy as ours.
I have even read somewhere that atrix 2 still shows 2 block away from real position. So even in latest device, broadcom still not really fix the problem. My next device will be snapdragon and won't be Omap with broadcom chip until I can be assured everything is solved by broadcom.
I'm no developer. Things I said about might just be wrong. I just share what I learned so far.
