Database Develop

Motosense for milestone.

Im not sure if the dev is a member of xda
but he had successfully booted a HTC desire rom.
here is the direct link.
http://modmymobile.com/forums/401-m...ge-motosense-htc-sense-ui-port-milestone.html
and video on youtube.
http://www.youtube.com/watch?v=UhWPP6ddhE8&feature=channel
According to him
Working
- Radio (Calls,GPRS,HSPA)
- USB
- Bluetooth
- Milestone bootup AC charging
- Wireless (Only static IP address.
DHCP is faulty at this stage)
- most apps from HTC and Motorola
(most untested)
- MilestoneOverClock v1.32
- SetCPU 1.54
- Sam2
- apps_installer
- MarketEnabler
- Camera
Not Working
- PINCODE (will not be able to enter any pincode or boot normal)
- GPS (at least not seen it working)
- DHCP for wireless
Update: According to his reply on youtube " i think going to modmymobile (.com) will explain it all..
but yes, right now i got the camera working as well, leaving just GPS not working and pincode setup."
All credits goes to the Dev (dext3r).

The last thread was about same topic...

wperdomos said:
The last thread was about same topic...
Click to expand...
Click to collapse
Yes! except that these links i have given are made by other dev on another forum.
and was made possible 10-12 hrs ago only.

Looks pretty amazing. I don't know if I have the guts to try that on my Telus Milestone. I would probably lose 3G (but Fido at least has EDGE too). Maybe I'll just wait that out for now.
I wonder though, in another thread I was told:
DAGr8 said:
cmstlist , there is an easy way to retain your baseband just flash the HK sbf , then , copy paste these files and make sure you set the permissions correctly .
Probably safest to do via adb if you dont make sure you reboot ...
for the 3G baseband Hack/Swistch it 5 files from /system/etc/motorola/bp_nvm_default
File_Audio , File_Audio2 , File_GSM , File_Seem_Flex_Tables , generic_pds_init
Click to expand...
Click to collapse
So perhaps if you want to try Motosense on your Telus Milestone, then you should backup these 5 files (and take note of the permissions) before flashing the nandroid image. Then afterwards if 3G doesn't work on the Motosense image, restore the same 5 files.
I would imagine Titanium Backup might be a viable way here to copy most of your app data from stock to Motosense.
Still... how in the world... was this accomplished?

cmstlist said:
Still... how in the world... was this accomplished?
Click to expand...
Click to collapse
no offense to all the programmers and the so called 'real hackers'
this was done using methods the above mentioned usually despised and mostly dismissed/ disregard .
common sense , risk , guts and of course a good UNIX understanding
btw there s a fixed 'new' version out at link is at motorolafans.com as well as in page 4 of the thread at M3 ( modmymobile.com)

DAGr8 said:
no offense to all the programmers and the so called 'real hackers'
this was done using methods the above mentioned usually despised and mostly dismissed/ disregard .
common sense , risk , guts and of course a good UNIX understanding
btw there s a fixed 'new' version out at link is at motorolafans.com as well as in page 4 of the thread at M3 ( modmymobile.com)
Click to expand...
Click to collapse
Can you keep us posted about the developments of this?
since you are the other half of Dext3r in porting the Motosense, i sure hope people here will appreciate it very much.
Anyway, can this be done in a Telus Milestone?

looks very interesting, i know that nexus one. 2.2 is out now, so is it possible to get the 2.2 froyo from there and then load via the same method, this would mean flash and maybe the wifi may work?

AGPS Patch Incredible S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK MORE SATS

AGPS Patch Incredible S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue 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: (Remember to make a backup. See Notes section for what this patch does.)
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" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* 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.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
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)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*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:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (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 NO-SSL TWRP build here. (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 NO-SSL 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 Alternative Options (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 NO-SSL 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 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
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 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
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)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
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.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
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.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
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 indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
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'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 differently which 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 threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS 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.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.

veitograf said:
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
Click to expand...
Click to collapse
Did you try v1.3? It's at the top of the post under "Downloads".

crypted said:
Did you try v1.3? It's at the top of the post under "Downloads".
Click to expand...
Click to collapse
1.3 works like a charm

i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")

baste07 said:
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
Click to expand...
Click to collapse
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.

crypted said:
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
Click to expand...
Click to collapse
thanks i'll try this out!

I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
NTP_SERVER=north-america.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
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse

itandy said:
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
Click to expand...
Click to collapse
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?

crypted said:
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
Click to expand...
Click to collapse
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk

itandy said:
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.

crypted said:
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
Click to expand...
Click to collapse
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk

itandy said:
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.

crypted said:
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
Click to expand...
Click to collapse
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk

itandy said:
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
-------
Also,
In preparing for the next iteration of the GPS patch, I'm trying to get a better grasp of the suplrootcert's on various devices. So far I have Verisign and TMobile. If anyone would be willing to check their phone and let me know if they have a different one (via private message here on xda)that would be great!
You can find "suplrootcert" as a file in /etc/ just like where the gps.conf is located.
To see which you have, open it up as a text document. It will look like jibberish. But, the top portion will say a company name within the jibberish. If you don't see Verisign or Tmobile, I would like to get ahold of the one on your device!!!

crypted said:
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
Click to expand...
Click to collapse
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Sent from my HTC Incredible S using Tapatalk

itandy said:
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Click to expand...
Click to collapse
Did it work fine before the patch, though? Can you get a screenshot of GPS Status after running for about 2 minutes?
I'm sorry I can't quickly resolve your phones issue. I'm curious about its hardware and whether it was greatly stable beforehand, or what...

Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7

BWA80 said:
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
Click to expand...
Click to collapse
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.

crypted said:
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
Click to expand...
Click to collapse
HEHEHE, good one!
Actually anything above 0 celsius is summer for us, how sad is that..
No case, my baby is totally naked. wifi not enabled. I´ll do the GPS status sit and run tomorrow, too dark now and the wolves are howling.
Will report back.
Thanks!!

AGPS Patch LG Optimus One 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK & MORE SATS

AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue 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: (Remember to make a backup. See Notes section for what this patch does.)
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" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* 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.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
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)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*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:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (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 NO-SSL 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 Alternative Options (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 NO-SSL 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 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
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 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
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)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
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.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
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.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
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 indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
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'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 differently which 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 threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS 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.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

Thank you for this helpful post.
I have tested this extensively for a bit using gps status, and have come up with the following conclusion.
Personally, i live in Sydney, Australia, my optimus one is rooted with cyanogen mod by mik_os and fserves gbs kernel v18b.
For me this patch performed poorly compared to me using the market app Fasterfix, with which u select the region you are in and in sets your gps.conf accordingly( in my case i just deleted this patch after testing, and faster fix wrote a new gps.conf once i selected my region)
I experienced a MUCH better fix time using Fasterfix, then this patch. Where it took 10 secs to lock on using fasterfixs conf file, this patch took minutes. i got more satellites fixes with Faster fix as well, 11 satelites to the 9 i got with this patch.
And yes i let it sit for at least 10 minutes each time to "learn", but after every restart it still took a few minutes to the 10 seconds average from Fasterfix.
This is results for Australia, so this patch may still be more effective in other countries especially North America, where it originally came from.
Hope this review helps other members.

deniso177 said:
Thank you for this helpful post.
I have tested this extensively for a bit using gps status, and have come up with the following conclusion.
Personally, i live in Sydney, Australia, my optimus one is rooted with cyanogen mod by mik_os and fserves gbs kernel v18b.
For me this patch performed poorly compared to me using the market app Fasterfix, with which u select the region you are in and in sets your gps.conf accordingly( in my case i just deleted this patch after testing, and faster fix wrote a new gps.conf once i selected my region)
I experienced a MUCH better fix time using Fasterfix, then this patch. Where it took 10 secs to lock on using fasterfixs conf file, this patch took minutes. i got more satellites fixes with Faster fix as well, 11 satelites to the 9 i got with this patch.
And yes i let it sit for at least 10 minutes each time to "learn", but after every restart it still took a few minutes to the 10 seconds average from Fasterfix.
This is results for Australia, so this patch may still be more effective in other countries especially North America, where it originally came from.
Hope this review helps other members.
Click to expand...
Click to collapse
All Fasterfix would do differently is set it to AU specific timeservers. So, maybe you had some bad luck with a NTP timeserver while testing. I can't solve that (yet).
Beta testers have had great success with this, even the guys using this device. Originally, this device was not on my goal to support list. But, after multiple people reported great things, I added it.
So in conclusion, thank you for the commentary. Just keep in mind the "difference" isn't really one.
EDIT: I've heard numerous reports that the ROM you're using has been screwed up with aGPS support being hard-coded as disabled in compilations lately. That may have some bearing on your results, too. I'm not a user of that ROM nor do I have the phone, so I can't personally attest. But, someone sent me the code snippets that clearly show aGPS disabled.

I dont think it is disabled, as then it would never take 10 seconds to get a lock on, which it does for me currently.
But yes the patch does give me a server connection eventually, but it takes dramatically longer.
I guess your first line is right, use this if you are experiencing issues, other wise no need to fix something that isn't broken.
Also note, after originally installing this Rom, and getting onto fasterfix, it stated that my location was Europe or something, cant remember exactly, but point is it recognised the location, so that would be the problem for most users using my mod, and all they have to do is set it to their own location, which in my case was immediate success and gps fix is great

deniso177 said:
But if it is disabled wouldnt that mean i shouldn't get any reception at all?
But yes the patch does give me a server connection eventually, but it takes dramatically longer.
I guess your first line is right, use this if you are experiencing issues, other wise no need to fix something that isn't broken.
Also note, after originally installing this Rom, and getting onto fasterfix, it stated that my location was Europe or something, cant remember exactly, but point is it recognised the location, so that would be the problem for most users using my mod, and all they have to do is set it to their own location, which in my case was immediate success and gps fix is great
Click to expand...
Click to collapse
I can't please everyone...
And I'm not following your commentary. There is literally no way this patch would cause your location to go from one end of the earth to the other via GPS. All it does is switch on some variables that your hardware is capable of for processing your location quicker. And, it adds some assistance data to be downloaded which is used in conjunction with UTC time. The NTP timeservers rarely matter because the binary file for that data is based on a 24 hour clock and updates every hour to be 23.5 to 24 hours in advance to allow up to that much time without a data connection for quick GPS satellite data parsing.

Sorry what i was meant to say is that, i dont think agps is disabled in my rom, as then i would never get 10 seconds lock on as i currently do. But yes i guess i dont understand how this patch exactly works, as there isnt that much information what hardware properties it takes advantage over the default settings.
I was just trying to display my Particular results, for my particular rom in Australia, so i cant say that this patch would not be better on other scenarios or not.
Will be good to see more testers on here say there results from all over the world using a bunch of roms, including the stocks.

regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?

sweetnsour said:
regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?
Click to expand...
Click to collapse
The gps.conf download is what it says, it only has that file, the other downloads, have an extra file called SuplRootCert, which i am not sure what it does

deniso177 said:
The gps.conf download is what it says, it only has that file, the other downloads, have an extra file called SuplRootCert, which i am not sure what it does
Click to expand...
Click to collapse
Technically, all should work unless a provider is limiting SUPL use to LAN data and not roaming phones. That wouldn't make sense since they advertise world traveler plans.
I prefer the generic Google build myself even though I use AT&T as it's always been reliable.
sweetnsour said:
regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?
Click to expand...
Click to collapse
SUPLROOTCERT is a verified certificate (think of it like https SSL websites). There is one for AT&T and its server, one for T-Mobile and its server, and one for Google and its server. Theoretically, their SUPL servers may deny your phone access for server assisted locating if your cert isn't matching the specifics for their server.
I collected what people were willing to send me and made versions based on that.

I have been using it since a month and must say this is great, works for me

i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?

GonDr said:
i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?
Click to expand...
Click to collapse
you can either:
a) redownload the file and try again
or
b) manually push the files into system/etc

Is it only for north america ? Can i flash it in italy ?

GonDr said:
i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?
Click to expand...
Click to collapse
It is designed to flash using CWR. It will not flash with a number of other Recovery systems out there. That's why there is another method described. You have two other options: copying directly using ES File Explorer or Root Explorer -OR- adb push.
angeloilcampione said:
Is it only for north america ? Can i flash it in italy ?
Click to expand...
Click to collapse
This is worldwide. So should work fine. Lots of Europeans using it.

crypted said:
It is designed to flash using CWR. It will not flash with a number of other Recovery systems out there. That's why there is another method described. You have two other options: copying directly using ES File Explorer or Root Explorer -OR- adb push.
Click to expand...
Click to collapse
The flash zip you provided is corrupted/not working... It wont install neither with CWR nor TWRP nor Amon.... (Error Status (0))
BTW, theres no reason why TWRP would not flash... Just because your flash zip is screwed...
BTW2: http://forum.xda-developers.com/showthread.php?p=18141638#post18141638 , another user that is flashing zip from recovery and doesnt work

excellent crypted but if I download gps data with status gps could be overwritten the file gps.conf ?
+1

angeloilcampione said:
excellent crypted but if I download gps data with status gps could be overwritten the file gps.conf ?
+1
Click to expand...
Click to collapse
Nah. But, I just suggest using that tool to prove this does work. Typically, I only use Google Maps and I like to watch how I don't have a big blue circle around me anymore.

TakamineSubasa said:
The flash zip you provided is corrupted/not working... It wont install neither with CWR nor TWRP nor Amon.... (Error Status (0))
BTW, theres no reason why TWRP would not flash... Just because your flash zip is screwed...
BTW2: http://forum.xda-developers.com/showthread.php?p=18141638#post18141638 , another user that is flashing zip from recovery and doesnt work
Click to expand...
Click to collapse
I also get this error (CWM), and so when I copy the files using File Explorer (rooted) the gpsconf copies fine but it fails when trying to copy SuplRootCert
strange?

digitalface said:
I also get this error (CWM), and so when I copy the files using File Explorer (rooted) the gpsconf copies fine but it fails when trying to copy SuplRootCert
strange?
Click to expand...
Click to collapse
If this is with ES File Explorer, goto settings and enable root and mount system. You can delete the file with Terminal root and then copy a new one over, too.
I'll try to get a new method posted using a script for adb pushing. A beta-tester is assisting in such a method. It'll be a few days, though.

crypted said:
If this is with ES File Explorer, goto settings and enable root and mount system.
Click to expand...
Click to collapse
Yeah that worked, shall test GPS shortly.
Just checking your gpsconf, as I'm UK would it be worth me commenting out the other servers and changing the first to UK?
Before
Code:
NTP_SERVER=1.pool.ntp.org
NTP_SERVER=2.pool.ntp.org
NTP_SERVER=3.pool.ntp.org
NTP_SERVER=0.pool.ntp.org
NTP_SERVER=0.europe.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
Modified
Code:
NTP_SERVER=1.uk.pool.ntp.org

[DEV/help is needed][ROM] GB Sense 2.3.3 [v1.2.1 in the second post]

SebastianFM has kindly agreed to provide support to fix issues.
That i think is a fantastic news
so please show your appreciation by thanking for the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM
Click to expand...
Click to collapse
I REQUEST/ENCOURAGE ANY DEV OUT THERE WHO WOULD LIKE TO TAKE OVER
OR START A FRESH TO BUILD GB-SENSE ROM PLEASE DO SO,
THIS THREAD IS MAINLY FOR INFORMATION PURPOSE
Click to expand...
Click to collapse
warning/disclaimer:
I am not maintaining this ROM, i have only transported this from SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
initial attempt was on SenseonFire ROM from wildfire
please don't bother this thread with trivial questions
this ROM is only for testing purpose and inspiration for further development only
I started this, with intention of porting the ROM, only to realize that I am not smart enough to fix most things.
I am not claiming to be dev as i am not, so posting the info for you to proceed or dump the project.
WIP <- working in pause (not work in progress)
I thank
SebastianFM for the first porting, which made possible most of the other device ROMs SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
all those involved in SenseonFire ROM project on wildfire especially VigiDroid,
and Arco for building an awesome kernel and nFinityGB v1.13 ROM for tattoo and some of the files were taken from this ROM
and dsixda's Android Kitchen
Click to expand...
Click to collapse
The main reason I have opened this thread is, to make you aware of the promising future out there for sense lovers using tattoo
and sow some seeds of inspiration for a dev out there who could fix this for us.
What i did
I took the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM used dsixda's Android Kitchen utility to transport and then adjusted few libs and binaries to get the phone started
Used Arco's 2.6.35.14 kernel and files from his nFinityGB v1.13 ROM
and added Robot font from following thread http://forum.xda-developers.com/showthread.php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
Click to expand...
Click to collapse
things like gps, fm and camera are not working on tattoo, many apps need resizing or font size needs reducing.
when i did benchmarking using cf-bench apk, the score i got was more than 500 close twice to what i got with tatfroyosense. Benchmark done at 633 Mhz max cpu

rom link and snapshots
Download links
SFM port version 1.2.1
mediafire
4shared
Changelog
V1.2.1
Pooled all patches together and few minor changes
V1.2
Few apks resized
ROM is by default Overclocked
framework symlinked from cache partition
wipe cache, data before flashing the ROM
First boot takes about 5-10 mins
Main issues:
GPS
Camera
FM
Media player sound OK - video is white
no notification lights (but button lights OK)
Battery drain - if wifi on
and other issues from user (??)
old versions
SFMportv1.2
http://www.mediafire.com/?uzutj2tura75oyr
SFMportv1.1
http://www.megaupload.com/?d=KXLUD91K
SenseonFire port link
http://www.megaupload.com/?d=UYZ4V0WJ
the rom has edify scripting and is unsigned, could be installed with clockworkmod recovery
Click to expand...
Click to collapse

This is cool. I never expected Tattoo to run anything heavy like this.
Feeling proud of you, man! With tears in my eyes.
Sent from my HTC HD2 with my fast fingers.

Waiting for news!!

Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
and about camera and videorecorder, u can get the drivers from CM7 and merge with this. For FM, u could get get drivers from CM7 and replace the HTC FM app with the one from CodeAurora or MIUI.
I am interested to help. But it seems I have got some other priorities to attend to. I will be free after April 2012. Then I will brush up my C++ skills and see if I can help u all.

...
too bad,this rom would be perfect if bt, gps, wifi, camera would working on tattoo...

sunitknandi said:
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
Click to expand...
Click to collapse
I dont think this is issues with old and new kernel, they all had access points as tiwlan0 (fyodor, ralle.gade and arco).
So far to my understanding it is device specific (see below).
Dexter seems to have tweaked the module and wpa_supplicant from ralle.gade's kernel to work with Froyo, i dont know what was changed. to get wifi working
EDIT: eth0 limitation is with hardware used in the device
Devices like: Wildfire, Wildfire S, Icon-G and Explorer -have their the access point setup as eth0 and they all have broadcom chip
while Tattoo, Magic and Hero -have tiwlan0 as the access point and they all seem to TI chip

in that case, lets ask dexter. he can help.

sunitknandi said:
in that case, lets ask dexter. he can help.
Click to expand...
Click to collapse
I asked him, he still hasn't responded...
P.S.
i get this from the logcat: " wifi_load_driver end error 2" and from dmesg i get something like: "firmware_path unknown value"
I researched and foundout that the deire had similar problems, but they had a previously working dirver and just couldn't conect....
So that leaves me nowhere again... (sadface)

Few things that i have't mentioned earlier:
Following are the commands in wpa_supplicant script for tatfroyosense
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant.bin -Deth0 -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
As it is tiwlan0 interface in Arco's kernel, i have copied wlan_loader, wlan_cu, wpa_supplicant, wpa_cli binaries from nFinityGB rom along with /system/etc/dhcpcd folder and the wifi module. (These are already in the ROM attached)
As some of you might have noticed:
module wont load at boot
so i have tried to execute following commands from shell (they are in the init.rc script except insmod of module)
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/firmware/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant -Dwext -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
module loads fine but then wlan_loader give following error
Code:
rtnl_open: Protocol not supported

Hello mate. Is it possible to provide a github repository with the code?

ntenisOT1948 said:
Hello mate. Is it possible to provide a github repository with the code?
Click to expand...
Click to collapse
I dont think HTC source code out there for sense andriod phones.
The time line for this ROM is as follows:
HTC Salsa was ported to Sapphire
http://forum.xda-developers.com/showthread.php?t=1025330
From Sapphire to wildfire
http://forum.xda-developers.com/showthread.php?t=1067868#13557996
wildfire then updated to this
http://forum.xda-developers.com/showthread.php?t=1269485
From above ROM to this ROM
Following files were taken from nFinityGB v1.13 ROM to this ROM
Code:
Filename Folder
wlan_loader system\bin
wpa_cli system\bin
wpa_supplicant system\bin
vold.fstab system\etc
dhcpcd.conf system\etc\dhcpcd
brf6300.bin system\etc\firmware
brf6350.bin system\etc\firmware
Fw1251r1c.bin system\etc\firmware
tiwlan.ini system\etc\wifi
wpa_supplicant.conf system\etc\wifi
Clockopia.ttf system\fonts
DroidSans-Bold.ttf system\fonts
DroidSans.ttf system\fonts
libwpa_client.so system\lib
copybit.bahamas.so system\lib\hw
gps.bahamas.so system\lib\hw
gps.goldfish.so system\lib\hw
gralloc.bahamas.so system\lib\hw
gralloc.default.so system\lib\hw
lights.bahamas.so system\lib\hw
sensors.bahamas.so system\lib\hw
sensors.goldfish.so system\lib\hw
wlan.ko system\lib\modules
bahamas-keypad.kcm.bin system\usr\keychars
bahamas-keypad.kl system\usr\keylayout
AVRCP.kl system\usr\keylayout
vim system\usr\share
colors system\usr\share\vim
filetype.vim system\usr\share\vim
ftoff.vim system\usr\share\vim
indent.vim system\usr\share\vim
indoff.vim system\usr\share\vim
scripts.vim system\usr\share\vim
blue.vim system\usr\share\vim\colors
darkblue.vim system\usr\share\vim\colors
default.vim system\usr\share\vim\colors
delek.vim system\usr\share\vim\colors
desert.vim system\usr\share\vim\colors
elflord.vim system\usr\share\vim\colors
evening.vim system\usr\share\vim\colors
koehler.vim system\usr\share\vim\colors
morning.vim system\usr\share\vim\colors
murphy.vim system\usr\share\vim\colors
pablo.vim system\usr\share\vim\colors
peachpuff.vim system\usr\share\vim\colors
ron.vim system\usr\share\vim\colors
shine.vim system\usr\share\vim\colors
slate.vim system\usr\share\vim\colors
torte.vim system\usr\share\vim\colors
zellner.vim system\usr\share\vim\colors
VoiceDialer.g2g system\usr\srec\config\en.us\grammars
wlan_cu system\xbin

Great news guys
I got wifi and bluetooth working
As i mentioned the history of the ROM in previous post,
It occured to me, may be i can start fresh from Sapphire ROM
So i went to the follwoing post and started with SFM 3.0.2
http://forum.xda-developers.com/showthread.php?t=1025330
and with rough porting i could get wifi and bluetooth working and i bet gps would also work.
you know it was quick and dirty port (huge size and bad layout),
now we can do proper port with relayout and resizing the framework and would be better ROM

Cool... Keep up the hard work. Once u finish the port, we can get someone to optimise it.

Have you updated the download link? Iwould like to have a look to graphics to know if I can do anything about them.
Edit: I can see you don't. But I'm going to start trying to resize some graphics as a practice for future.

2nd post updated with new rom port
some of the applications are not working and poor layout.
Alternative launcher like adw working fine

I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk

sense zero on tattoo
Now that i could port (transport) GB sense, i wanted to have a crack at sense zero (it was to decide which one would be best carry on)
so I did try port Hintay Zero 0.14 (Sense 3.5 Android 2.3.5)
and i could get it booted on Tattoo,
but have to set lcd density to 100, so that you can see launcher work.
But most of other things look decent if it is set to 120.
And you can see that layout and size are bad.
but i have to say it takes lot of memory and gets very slow.
framework moved to cache to make space in system.
takes 10 mins on first boot
here the link
http://www.megaupload.com/?d=X1B721BZ
and snapshots

GbermuG said:
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.

sunitknandi said:
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
Click to expand...
Click to collapse
That's what I can understand using translators: they've tried it, and like it. They thik is smooth and powerfull, but ram memory is low. Someone is asking about Sense 3.0, but the tread is not updated, so they only tried SenseonFire (first port). Simply (as I said), they're waiting.

[TWEAK] Fix GPS for your region on Custom ROM

Having problems with GPS locking on (and on a custom ROM)? Read on...
But the obligatory first:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this
* tweak before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Inspired by this XDA TV spot, I took things a step further, as I find myself re-flashing on a regular basis - why not have the gps.conf reload with the ROM update?
I created a series of flashable zip's, for each region (right now I only have a small handful), using the gps.conf files found here. These should run independent of whichever custom ROM you have chosen (although update-binary taken from, and tested with, CarbonROM).
Because of the update-binary, it will only work with Intel devices, and would only make sense for devices that have a GPS on-board.
REGIONS:
This list will undoubtedly grow, but for now, here is what is hosted:
Brazil
Canada
India
Indonesia
Italy
Qatar
Russia
Switzerland
United Kingdom
USA (Mainland)
... if your region is not in the list, check the download archive. If it is not there either, let me know (via thread reply), and I can add it (or follow instructions in post two).
DOWNLOAD:
Archive
INSTALL:
Flash in recovery after any Custom ROM install / upgrade, to be in queue after GApps
If flashing standalone (no other packages), no need to wipe dalvik afterwards
CREDITS:
rirozizo
BlackICE Team
ocd_amp

Make your own gps.conf flashable!
So, your region/country is not in the list, and you cannot wait for me to get around to it? Well then...how about making one yourself?
THINGS YOU NEED:
An existing GPSFix flashable (can pick any region)
Your region's gps.conf
SignAPK (original page)
INSTRUCTIONS:
Extract the GPSFix zip in an empty folder, while preserving the folder structure
Code:
unzip x GPSFix-Canada.zip
Move away or delete the zip so it doesn't get in the way for the next steps
Copy and replace the gps.conf file (under system/etc) with the one for your region
Make sure the permissions for the new gps.conf is rw-r--r--
Re-zip the package
Code:
zip -r9 gpsfix.zip *
Copy the gpsfix.zip to the SignAPK folder
Run the following command to sign:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 gpsfix.zip GPSFix-NewRegion.zip
Done!

I use a navigation app called MAPS.me a lot....
But since I started using custom ROMs it kept FCing as soon as it starts..... Will this fix it or is it rom bug?
Also I live in UAE

Can you add the Brazil gps.conf?
P.S.: ZF2 was launched past month here, with a massive hype lol

Abd121 said:
I use a navigation app called MAPS.me a lot....
But since I started using custom ROMs it kept FCing as soon as it starts..... Will this fix it or is it rom bug?
Also I live in UAE
Click to expand...
Click to collapse
Sounds like this commit instead (the switch from dlmalloc to jemalloc). So if you are using a build newer than August 29th, you should be okay (I was getting force closes on apps before this commit - Adobe Reader has been fixed, my transit app seems to be as well).
Unfortunately the UAE does not have a gps.conf, but I did upload one for nearby Qatar. But if across the gulf for Iran works better, I can do that too.
Dan_Jacques said:
Can you add the Brazil gps.conf?
P.S.: ZF2 was launched past month here, with a massive hype lol
Click to expand...
Click to collapse
Done. Will update the OP in a minute.

Hey dude,
I am using RR rom on my Zenfone 5 and my region is India. from the first build GPS is dead and Dev found no solution till now.
Can you help me ?
please let me know if you can help me solve this, its really important for me.
Thanks

abhimanyu.singh said:
Hey dude,
I am using RR rom on my Zenfone 5 and my region is India. from the first build GPS is dead and Dev found no solution till now.
Can you help me ?
please let me know if you can help me solve this, its really important for me.
Thanks
Click to expand...
Click to collapse
Hello,
Get gpstest from the play store to see if you can access any satellites. If you can, but cannot lock on, this tweak is for you. If no satellites are coming up, then there are underlying problems.
I'm away from my PC the next few days, so if this tweak is for you and want to try it, check out post two to make your own (or I can make one for India in about a week).
Hope this helps.
Sent from my ASUS_Z00AD

OfficerJimLahey said:
Hello,
Get gpstest from the play store to see if you can access any satellites. If you can, but cannot lock on, this tweak is for you. If no satellites are coming up, then there are underlying problems.
I'm away from my PC the next few days, so if this tweak is for you and want to try it, check out post two to make your own (or I can make one for India in about a week).
Hope this helps.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Dude i tried the app you mentioned but it showed no Satellite and it was just showing no GPS fix.

abhimanyu.singh said:
Dude i tried the app you mentioned but it showed no Satellite and it was just showing no GPS fix.
Click to expand...
Click to collapse
Just what I thought would happen. Your Roms GPS has underlying issues that this tweak cannot fix.
Sorry.
Sent from my ASUS_Z00AD

India.... please do that too

android lover 2000 said:
India.... please do that too
Click to expand...
Click to collapse
Added to the archive.
Hope this helps.

used the germany gps.conf (cause living in germany ), just replaced the old one, now i dont get any fix at all anymore.

Hastaloego said:
used the germany gps.conf (cause living in germany ), just replaced the old one, now i dont get any fix at all anymore.
Click to expand...
Click to collapse
Sounds to me like the file cannot be found or is unreadable. Is the new file in /system/etc with permissions rw-r--r-- (644)?

OfficerJimLahey said:
Sounds to me like the file cannot be found or is unreadable. Is the new file in /system/etc with permissions rw-r--r-- (644)?
Click to expand...
Click to collapse
its all ok with the file, just the content doesnt work.
tried several other settings too.
this is what worked:
NTP_SERVER=de.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra4.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra5.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276

Hastaloego said:
its all ok with the file, just the content doesnt work.
tried several other settings too.
this is what worked:
NTP_SERVER=de.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra4.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra5.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
I did a little pinging, looks like some of the time servers have moved or are just unavailable. I guess it's understandable, since the conf files are approaching 2.5 years of age. :silly:
So "NTP_SERVER=ntp1.fau.de" should be "NTP_SERVER=ntp1.rrze.uni-erlangen.de", and et cetera, and might as well remove the "NTP_SERVER=ptbtime2.ptb.de" line altogether.
May as well want to give preference (move to top of list) for the NTP_SERVER=de.pool.ntp.org ones as well (since they worked for you, if you want to maintain BlackICE Team's version).
Hope this helps.

OfficerJimLahey said:
Hope this helps.
Click to expand...
Click to collapse
i tried a bit.. even if the phone finds up to 14 sats. none of them are used.. i quess its something with the other settings.

OfficerJimLahey said:
Just what I thought would happen. Your Roms GPS has underlying issues that this tweak cannot fix.
Sorry.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
No problem. Thanks for trying to help me.

fix italy gps

max997 said:
fix italy gps
Click to expand...
Click to collapse
Added.

@OfficerJimLahey
Possible france gps.config?
Thank