A summary of the problems.
- The timestamp on all received SMS's are 1 hour behind & the issue began on DST changes.
- The timestamp on all received SMS's are hours ahead / behind & are not related to DST.
- While the received SMS timestamp is off, all sent SMS's are perfectly fine.
- It messes up ordering of SMS's [if ordered by time received / sent].
A summary of the fixes.
- CAB from Diamond forum.
> Download and install
> OR create [HKLM\SOFTWARE\OEM\PhoneSetting\TrustTimeZoneField= 0]
- Registry change from Raphael forum.
> Create [HKLM\Software\Microsoft\ConsistentRoamingIconSlot= 0]
- CAB of Official Microsoft DST patch [Updated Aug 09].
> Download and install
- Registry change from Kaiser forum.
> Create [HKLM\Software\OEM\SMS\RecvTimeStamp= 0]
- Changing system time zone from Sapphire forum.
> Fiddle with System Time Zone [Settings > System > Clocks & Alarms > Time]
* if a key [eg. "SMS" in HKLM\Software\OEM\SMS] does not exist, create it [as a KEY].
* if a value [eg. "RecvTimeStamp" in HKLM\Software\OEM\SMS\RecvTimeStamp =0] does not exist, create it [as a DWORD].
My issue.
- My issue started with the DST change - my received SMS timestamps are 1 hour behind.
- All fixes I listed above are installed / entered, but do not work for me.
- A text from myself has the correct timestamp
- Other texts still have incorrect timestamps [1 hour behind]
- These texts were from an iPhone 3G / SE K800i on the 3 network
- Any suggestions?
Anyone?
It seems the Q&A forum lacks in answers...should it become the Q forum?
[Sorry if that comes across as harsh...but I really haven't found many answers here...]
Lumic said:
Anyone?
It seems the Q&A forum lacks in answers...should it become the Q forum?
[Sorry if that comes across as harsh...but I really haven't found many answers here...]
Click to expand...
Click to collapse
Lumic,
Sorry if this sounds harsh, but this question has been asked many, many times and is resolvable (did you search, i found this using google in 3 minutes )
There is a solution at microsoft site for DST here : http://support.microsoft.com/kb/975353/en-us
Not read it all but i have posted this solution a year or so ago and it worked for others.
Greetz (and search)
Lumic said:
- MS DST patch [CAB]. [Aug 2009 Update]
Click to expand...
Click to collapse
timmymarsh said:
There is a solution at microsoft site for DST here : http://support.microsoft.com/kb/975353/en-us
Click to expand...
Click to collapse
The patch you provided still links back to this is the same Microsoft "DST update" I stated did not work for me in the original post.
timmymarsh said:
Not read it all but i have posted this solution a year or so ago and it worked for others.
Greetz (and search)
Click to expand...
Click to collapse
My searching isn't perfect, but as you saw I tried 3 xda-devs methods and the official Microsoft update. Could you point me towards other possible fixes [such as your own] if you know some?
Apolos......My bad, should read 100% and not 98 % lol
Edit....
I had posted this cab also, but noticed it had been posted in the diamond forum also.....
Most of these fixes work for 99% of people, i guess you are the exception
I am going to have to have a deeper dig, so apols if you dont get ur answer straight away
Cheers.
Thanks for your effort timmymarsh, I really appreciate it. I must say I have to take back my previous words - I guess the Q&A section does have good posters - I just don't see them often enough ;}
I am going to experiment with a few fixes at once, and continue to search for other "solutions".
Edit: I tried a few different search terms, and came across another registry entry from the Kaiser forum...which did not work.
I have updated the first post - I can text myself and receive the correct timestamp, but when my friend texts me the problem remains.
Lumic said:
Thanks for your effort timmymarsh, I really appreciate it. I must say I have to take back my previous words - I guess the Q&A section does have good posters - I just don't see them often enough ;}
I am going to experiment with a few fixes at once, and continue to search for other "solutions".
Edit: I tried a few different search terms, and came across another registry entry from the Kaiser forum...which did not work.
I have updated the first post - I can text myself and receive the correct timestamp, but when my friend texts me the problem remains.
Click to expand...
Click to collapse
we do try
Thats interesting, is your mate on the same network and has he tried the df fix (or ms one). THis would prove (or not) that the timefix works. I believe it is not your phone that is the problem but other peoples which is why texting yourself works. Many people who have applied the fixs using all kinds of devices say they have no further problems, but of course if someones devices doesnt have the fix then the timings will appear incorrect.........
.........or am i just being simple
I am on the TPG network [which I believe leverages the Optus network].
My friend is on 3.
At first I thought it might be his problem too. However, his system time is correct, and I should note he is not on a WinMo / WinPho, but an iPhone 3G.
I also got a text from a SE K800i on 3, and the timestamp was again behind by 1 hour.
My guess only: Your friends' location is another timezone from your current location.
wg5566 said:
My guess only: Your friends' location is another timezone from your current location.
Click to expand...
Click to collapse
I can practically walk to my friend's house.
Update: I am now going to fiddle around with the system time zone.
Found a thread in the Sapphire apps & games [???] forum that says that I should adjust the system time zone.
Update: Tried adjusting the time zone, but it didn't help.
This is an interesting point though - in a time zone I changed to[I think GMT +11, from GMT +10], it corrected some SMS's I had already received [i.e. that were sitting in my inbox].
However, the ones I received after the change were still behind by 1 hour.
Could this mean it is a network / external problem?
Registry change from Kaiser forum.
> Create [HKLM\Software\OEM\SMS\RecvTimeStamp= 0]
Click to expand...
Click to collapse
Actually I had to set the value to 1 for the time stamp to work on my Diamond diam500. I have to do this every time I flash a new ROM or my sms timestamps are 5 hours in the future screwing up my threads conversations.
sp991 said:
Actually I had to set the value to 1 for the time stamp to work on my Diamond diam500. I have to do this every time I flash a new ROM or my sms timestamps are 5 hours in the future screwing up my threads conversations.
Click to expand...
Click to collapse
I will check this out, though I believe I made a typo and in fact set it to 1.
sp991 said:
Actually I had to set the value to 1 for the time stamp to work on my Diamond diam500. I have to do this every time I flash a new ROM or my sms timestamps are 5 hours in the future screwing up my threads conversations.
Click to expand...
Click to collapse
Why dont you create a cab with the reg change that you can auto install via UC after the flash?
If you dont know how, there are websites that you can type in the reg change you want to do enabling you to download the cab.
If you need it i will try and find the site if you dont have software to do this for yourself.
Chow.
Here is the cab download time zone fix thing. This link works as of now. The market place is no longer working. http://support.microsoft.com/kb/977014
---------- Post added at 02:28 PM ---------- Previous post was at 02:11 PM ----------
Lumic said:
Update: Tried adjusting the time zone, but it didn't help.
This is an interesting point though - in a time zone I changed to[I think GMT +11, from GMT +10], it corrected some SMS's I had already received [i.e. that were sitting in my inbox].
However, the ones I received after the change were still behind by 1 hour.
Could this mean it is a network / external problem?
Click to expand...
Click to collapse
I have the same problem in Hawaii. I think its a network thing. It is like this for me on sprint and ATT when using my sprint branded TP2 in Hawaii. I cant figure it out.
AGPS PATCH FOR MOTOROLA DEFY USERS
Use this if you're having GPS issues (unreliability, no functionality, etc.)
IMPORTANT: This device is not officially supported. It has a different chipset than the gps.conf patch is intended for. You MAY experience better results with this aGPS Patch when using custom ROM's. Those ROM's come from other phones and can provide added benefits that this patch enables.
Before continuing, this post is of importance to you: http://forum.xda-developers.com/showthread.php?p=21456377#post21456377. Any attempt to bring a solution has been negated by six pages of attacks by two usernames that failed to proffer useful discussion to resolve this phone's GPS problem.
------
This patch was created to provide quick GPS locking across North America. But, it has been ported into a worldwide solution for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL:
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS".
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
(Thank you eagleeyetom for helping make this possible!)
Method 2:
1. Download the patch
2. Copy gps.conf and suplrootcert into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
3. Reboot the device
4. Review the NOTE section in Post #2.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
5. Reboot the device
6. Review the NOTE section in Post #2.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
There are many new builds available. The 1.x trunk only flashed a gps.conf file. Starting with 2.x, more comes along with the package. This provides the SUPLROOTCERT that many ROMs seem not to have. I prefer the Google Specific version myself.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
3.x trunk (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
NOTE(S):
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
IF you have issues with GPS locking in v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance. It has been observed that some ROM's do not have SANE values for missing variables.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differenty and is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error theshold. Food for thought.
DO NOT USE any other GPS FIXING SOFTWARE with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
AGPS Patch Officially Supported Devices:
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
Acer Iconia
LG Optimus One
Sony Ericcson XPERIA X8
HTC Salsa
HTC Flyer
HTC Evo 3D
*This works on over 15 other devices, at least with certain ROM configurations. I do not officially support those devices as of yet. You may private message me your success story for official support considerations.
(For v1.0) Thanks to Angeldeath for permitting me to take his work and start tweaking it for Inspire users across the continent. Angeldeath made a great series of AGPS patches designed for his HD2 which essentially updated the gps.conf to speed up the locking process. However, those scripts are based upon regions for USA and no general support for North America after v1.0.
Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!
Hi crypted, good to see you here on this place of the forum . When I had my LG P500 I used this patch for the GPS and it works great Then when I got my defy continued to use this patch and it works great . I regret not having informed about this before, I'm on vacation so that I'm offline
Enviado desde mi MB525
Garuxa said:
Hi crypted, good to see you here on this place of the forum . When I had my LG P500 I used this patch for the GPS and it works great Then when I got my defy continued to use this patch and it works great . I regret not having informed about this before, I'm on vacation so that I'm offline
Enviado desde mi MB525
Click to expand...
Click to collapse
Good to know you're still a fan! I intend to make this device and four more officially supported depending on results or responses from the users.
So far, three of the five are definitely good for official support.
which one to use?
am confused as to which one to use..have downloaded google ones ..cwm flashable...am from india...
cwm flashable google, works like a charm.
My problem is not to get a fast fix with GPS. This works very well (Germany, CM7.1). But the data seems to be not valid for some time. Soon after disconnecting the data connection the fix takes very long again.
Imho the AGPS data should last for a week, some days or even 24h. But it seems that even after 6 hours they are not very useful anymore.
Do you have the same experience?
From what I oberved this is indepenend on switch GPS on/off.
BTW: I didn't check the "use wireless networks" button, I download AGPS data with GPS-status.
By data you mean mobile data( internet) then you should change your baseband, look for baseband switcher in the forum if that's the case if not then I didn't understand what you said
starbright_ said:
My problem is not to get a fast fix with GPS. This works very well (Germany, CM7.1). But the data seems to be not valid for some time. Soon after disconnecting the data connection the fix takes very long again.
Imho the AGPS data should last for a week, some days or even 24h. But it seems that even after 6 hours they are not very useful anymore.
Do you have the same experience?
From what I oberved this is indepenend on switch GPS on/off.
BTW: I didn't check the "use wireless networks" button, I download AGPS data with GPS-status.
Click to expand...
Click to collapse
Are you using this patch? The data should be stored by your ROM in cache. The file you download is good for 24 hours. If your phone is in a case, remove it.
What ROM are you using? Did you read the Notes Section at all?
Should T-Mobile US users use the T-Mobile specific one or are we okay with using the Google specific one?
silentsnow31802 said:
Should T-Mobile US users use the T-Mobile specific one or are we okay with using the Google specific one?
Click to expand...
Click to collapse
As noted in the first post, I recommend the Google Build for everyone. However, I provide provider specific varieties because I had the certificate files and the correct SUPL server information to do so.
Use what you wish.
crypted said:
As noted in the first post, I recommend the Google Build for everyone. However, I provide provider specific varieties because I had the certificate files and the correct SUPL server information to do so.
Use what you wish.
Click to expand...
Click to collapse
This patch works best for qualcomm soc. HTC often uses MSM or Snapdragon, hence your patch works for most HTC devices.
Defy uses broadcomm gps chip (BCM4750 aka barracuda). It doesn't uses xtra.bin. Agps can even work without gps.conf.
starbright_ said:
My problem is not to get a fast fix with GPS. This works very well (Germany, CM7.1). But the data seems to be not valid for some time. Soon after disconnecting the data connection the fix takes very long again.
Imho the AGPS data should last for a week, some days or even 24h. But it seems that even after 6 hours they are not very useful anymore.
Do you have the same experience?
From what I oberved this is indepenend on switch GPS on/off.
BTW: I didn't check the "use wireless networks" button, I download AGPS data with GPS-status.
Click to expand...
Click to collapse
What you need is a-gps data. For qualcomm, that is xtra.bin. For broadcom, its lto.dat. xtra.bin and lto.dat size approx 40kb and valid for about 3-7days. Our defy is broadcom, it is supposed to use lto.dat, but it seem it didn't enabled in driver. Currently only enabled SUPL. Supl only download 4-8kb (4kb for ephemeris, if you wait long enough, it will download another 4kb for almanac), and valid for about 4 hours.
bobo9900 said:
This patch works best for qualcomm soc. HTC often uses MSM or Snapdragon, hence your patch works for most HTC devices.
Defy uses broadcomm gps chip (BCM4750 aka barracuda). It doesn't uses xtra.bin. Agps can even work without gps.conf.
What you need is a-gps data. For qualcomm, that is xtra.bin. For broadcom, its lto.dat. xtra.bin and lto.dat size approx 40kb and valid for about 3-7days. Our defy is broadcom, it is supposed to use lto.dat, but it seem it didn't enabled in driver. Currently only enabled SUPL. Supl only download 4-8kb (4kb for ephemeris, if you wait long enough, it will download another 4kb for almanac), and valid for about 4 hours.
Click to expand...
Click to collapse
Interesting notes. I didn't review the device specs. I can tell you that there were a number of user reports saying that it worked wonderfully, hence the "tentative" support.
I would question that and ponder the ability of the other aspects of my patch to be what gave such benefit. Just because the aGPS data is of a different nature does not mean that the other additions couldn't help...depending yes on what the hardware and/or software will support as far as additional variable features.
EDIT: Can you send me a private message with the default gps.conf file so that I may review and tweak mine to try out this theory?
crypted said:
Interesting notes. I didn't review the device specs. I can tell you that there were a number of user reports saying that it worked wonderfully, hence the "tentative" support.
I would question that and ponder the ability of the other aspects of my patch to be what gave such benefit. Just because the aGPS data is of a different nature does not mean that the other additions couldn't help...depending yes on what the hardware and/or software will support as far as additional variable features.
EDIT: Can you send me a private message with the default gps.conf file so that I may review and tweak mine to try out this theory?
Click to expand...
Click to collapse
Stock rom doesn't have gps.conf. CM7 uses standar gps.conf contain ntp and xtra server. It was added upon request, and I think it doesn't affect much.
Here is your reference. All Ti Omap uses broadcomm chip. Snapdragon and msm uses qualcomm chip. Tegra can use either I think. Hummingbird uses broadcomm if I'm not wrong. SGS2 is somewhat exception, it uses Sirf chip, for now, this is one and only android uses Sirf chip.
Defy uses old BCM4750 while first SGS series uses BCM4751. Some newer phone might have BCM47511 chip that support glonass.
Just visit gsmarena, any phone that uses Snapdragon and qualcomm MSM can use your patch.
bobo9900 said:
Stock rom doesn't have gps.conf. CM7 uses standar gps.conf contain ntp and xtra server. It was added upon request, and I think it doesn't affect much.
Here is your reference. All Ti Omap uses broadcomm chip. Snapdragon and msm uses qualcomm chip. Tegra can use either I think. Hummingbird uses broadcomm if I'm not wrong. SGS2 is somewhat exception, it uses Sirf chip, for now, this is one and only android uses Sirf chip.
Defy uses old BCM4750 while first SGS series uses BCM4751. Some newer phone might have BCM47511 chip that support glonass.
Just visit gsmarena, any phone that uses Snapdragon and qualcomm MSM can use your patch.
Click to expand...
Click to collapse
Understood. Like I said, I went here based on user reports. Thanks for the info though! I may just flood the qualcomm threads. Ha-ha.
Sent from my Desire HD using XDA App
crypted said:
Understood. Like I said, I went here based on user reports. Thanks for the info though! I may just flood the qualcomm threads. Ha-ha.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
May I know how you generate xtra.bin. AFAIK, that is proprietairy qualcomm thing. I suppose you only mirror it from original xtra server?
I think you should rather uses standard ntp and xtra server. I'm sure ntp server will be always there, and xtra server will be always there too as long as qualcomm keep making their gps chip.
Changing ntp and xtra to your server is not a good idea. I'm not sure you can keep maintain the server, and you should stop dependency to your server. If you really want to help people, just set to standard setting without dependency to you.
bobo9900 said:
May I know how you generate xtra.bin. AFAIK, that is proprietairy qualcomm thing. I suppose you only mirror it from original xtra server?
Click to expand...
Click to collapse
MD5 sum will show it as different I suppose... Tis all I can say at this juncture.
Sent from my Desire HD using XDA App
crypted said:
MD5 sum will show it as different I suppose... Tis all I can say at this juncture.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Nope, its identical. Just check it now.
I would recommend people to NOT use your patch if they have to depend on your server.
bobo9900 said:
Nope, its identical. Just check it now.
I would recommend people to NOT use your patch if they have to depend on your server.
Click to expand...
Click to collapse
Odd I guess the original didn't fall below our process threshold for the rebuild and kept default build.
You definitely are fast to judge. What does the other trunk have? It has qualcomm for those who distrust my server and our methods.
Out of all the users, only two have brought that server point up before reviewing the whole thread... You're the first nonuser to not actually review the thread and make a rash statement.
Anyway I appreciate the criticism.
Sent from my Desire HD using XDA App
crypted said:
Odd I guess the original didn't fall below our process threshold for the rebuild and kept default build.
You definitely are fast to judge. What does the other trunk have? It has qualcomm for those who distrust my server and our methods.
Out of all the users, only two have brought that server point up before reviewing the whole thread... You're the first nonuser to not actually review the thread and make a rash statement.
Anyway I appreciate the criticism.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Your patch is simple tweak, and I downloaded all your tweak, I indeed studied it before I make my statement, so that is not a rash statement.
For you who doesn't know how xtra.bin work, for which chip its working, you definitely cannot build the file by yourself.
Currently android doesn't sync to ntp server via gps.conf, or at least on defy it doesn't, but in later time if it does, it's sure a security risk.
Hi,
I'm a newbie here, so I can't post my question in the Development forum yet.
Thanks to Daniel_hk, I'm using GT-P6200 using SlimKat ROM.
I however find, from "iw reg get", that the default country is 00, which doesn't allow connection on channel 52 - 60 on 5 GHz band.
Does anyone here know how to enable those channels (or all channels on 5 GHz band) on this build?
I find no luck with "iw reg set".
I tried using SQLite to change my default carrier (mcc) code. It works for a little while, but then it will change the value back to the 'correct' value.
Any help is appreciated.
regards,
Denny
mountainhill2 said:
Hi,
I'm a newbie here, so I can't post my question in the Development forum yet.
Thanks to Daniel_hk, I'm using GT-P6200 using SlimKat ROM.
I however find, from "iw reg get", that the default country is 00, which doesn't allow connection on channel 52 - 60 on 5 GHz band.
Does anyone here know how to enable those channels (or all channels on 5 GHz band) on this build?
I find no luck with "iw reg set".
I tried using SQLite to change my default carrier (mcc) code. It works for a little while, but then it will change the value back to the 'correct' value.
Any help is appreciated.
regards,
Denny
Click to expand...
Click to collapse
I actually find that Carbon ROM also behaves the same, i.e. the WiFi region is set to 'country_00', and I'm unable to change that.
Any suggestion?