Database Info

[DEV] GSM phone calls on Nexus 7 3G - Nexus 7 3G Android Development

BEFORE YOU POST HERE - Keep in mind this is now a DEV thread and only those with a glimpse of DEV knowledge should be posting.
There is other thread with the same subject open to everybody discuss it.
Please, this thread isn't related to VOIP, SIP calls or Tethering and
It's only to 3G version of Nexus 7.
What do you think is the possibility of us getting this function guys, even if its not officially supported.
I've seen it built in on the 7" samsung galaxy tab 2.
http://www.youtube.com/watch?v=wZ9RN...t=HL1351349133
At the moment we know:
1- The chipset Intel (Infineon) XMM6260 is built-in on Nexus 7 3G (the same chipset is in that rather long list of phones). It means no hardware limitations.
http://forum.xda-developers.com/showthread.php?p=34386544&highlight=6260#post34386544
http://pdadb.net/index.php?m=specs&i...exus_7_3g_32gb
http://forum.xda-developers.com/show....php?t=1483053
it also the same controller is in the following devices
- Lava XOLO X900 [Phone]
- Lenovo K800 [Tablet/Pad]
- LG-P920 (LG ?) [Phone]
- LG-P925 (LG Optimus 3D?) [Phone]
- Huawei E369 (3G Hi-Universe) [USB 3G Modem]
- Huawei MU733/MU739 [PC/CE Module]
- Samsung Galaxy Nexus (I9200) [Phone]
2- SMS texting works perfectely with the native mms.apk but MMS messages crash the app (missed mms APN + framework parameters?)
http://forum.xda-developers.com/showthread.php?t=1998702&page=4
3- Modified framework-res.apk (by modifying bools.xml entry to name="config_voice_capable">true) shows up the native dialer (phone.apk) on the UI
JB 4.2 http://forum.xda-developers.com/showthread.php?t=1958686&page=12
JB 4.2.1 http://forum.xda-developers.com/showpost.php?p=34736932&postcount=314
4- When placing calls trough the native dialer (phone.apk) with Skype app installed, it shows up a white menu asking "Do you want to complete this action using..." the options are "Mobile data" (w/ phone.apk blue icon) or "Skype" (w/ skype icon) and "Always" or "Just Once" (perhaps there is missing a "Phone" profile (or APN) as an option too)
5- If Skype is chosen, the call is complete and everything goes well, but if "Mobile data" is chosen, we get a single sound (bip) and the call is not complete.
6- Changing the DPI to 320 in build.prop file allow us to add a SIP account (SIP calls using native dialer is now possible), DPI could be restored after SIP account settings done.
http://forum.xda-developers.com/showthread.php?p=34752693&highlight=320#post34752693
Detailed informations come from the thread in XDA developers at:
http://forum.xda-developers.com/showthread.php?t=1958686
--------------------------------------------------------
UPDATE 5th Dec 2012 by Synman
ok, I hacked NetworkPolicyManager and am no longer crashing. Network time appears to be non-functional for the time-being. Network status is a little wonky too ... even though I have a good network signal the network icon never switches from gray to blue.
MMS send/receive is fully functional (with the exception of screwed up timestamps)
Pulled down master AOSP branch
Pulled down grouper binaries
working with grouper device
Modified device.mk
- use init.tilapia.rc
- use tilapia overlay
- remove SimpleSMS
- remove ro.carrier=wifi_only
Modified full-grouper.mk
- ref full_base_telephony in place of full_base
- added full apns
Modified device-common.mk
- added gsm permission
system.prop
replaced ref to libril-icera with libxgold
tilapia overlay
- removed single apn rules
- set voice-enabled
- added mms values
NetworkPolicyManager
- removed call to time.getMaxPeriod

I tried to make a summary of the whole work on the previous thread assuming it will be much more productive.
If someone has a suggestion to the OP please let me know and I change it to keep more updated as possible.

te framework linked above is for 4.2 ROM, the 4.2.1 is on page 32 ; http://forum.xda-developers.com/showpost.php?p=34736932&postcount=314

I've done a bit more digging within the 4.2.1 source and until we have the device specific portions of the build we are going to keep struggling.
Everything I'm seeing comes back to the framework.
I'm currently focusing on getting a build of Mms.apk bypassing framework and, while slow and tedious, I'm making progress.
My current line of thinking (open to discussion, please) is that the framework hooks we need are simply missing in our build.
Keep in mind this is now a DEV thread and only those with a glimpse of DEV knowledge should be posting.
Sent from my Galaxy Nexus using Tapatalk 2

I'm wondering if the parameters in line 40 have anything to do with it.
https://android.googlesource.com/de...rameworks/base/core/res/res/values/config.xmlhttps://android.googlesource.com/de...rameworks/base/core/res/res/values/config.xml

TinTin said:
I'm wondering if the parameters in line 40 have anything to do with it.
https://android.googlesource.com/device/asus/tilapia/+/bead144d1ca3f10e5ea7a93c58b35d6bc0630f80/overlay/frameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
Oooh Lines 183-184 are even more interesting:
Code:
<!-- This device is not "voice capable"; it's data-only. -->
<bool name="config_voice_capable">false</bool>
Or is this the variable you guys already used to enable the dialer? And that's all it does?

Yeah, we've already hacked that one... Its how we got the native dialer.
#3 in OP
Sent from my Galaxy Nexus using Tapatalk 2

Synman said:
Yeah, we've already hacked that one... Its how we got the native dialer.
Click to expand...
Click to collapse
What about line 40? Did you try changing parameters yet? to like
Code:
<item>"mobile,0,1,1,-1,true"</item>
Or other combinations.

I haven't compared them to a galaxy nexus framework yet. Is that where those came from?

Synman said:
I haven't compared them to a galaxy nexus framework yet. Is that where those came from?
Click to expand...
Click to collapse
Oh, nevermind. The Mako (Nexus 4) has the same values
0,0,0,-1,truefor "item" mobile in it's 4.2.1 config.xml, so this is not it I guess.

TinTin said:
Oh, nevermind. The Mako (Nexus 4) has the same values
0,0,0,-1,truefor "item" mobile in it's 4.2.1 config.xml, so this is not it I guess.
Click to expand...
Click to collapse
I found a thread elsewhere that could contain (parts) of the solution. Looking at the config.xml of the Mako (Nexus 4) and comparing it to the one of tilapia I see these parameters missing (line 40 ff.)
Code:
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,60000,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item
Please someone try adding them to the string-array of network-attributes (I don't have the decompiler yet). They definitely should be there. This might not be all yet though.

Those values might be connected with Verizon APN settings.
System Infrastructure
APN Manager by 81 Square -- Has a list of APNs for USA, Canadian and European mobile operators, plus you can type in your own. I enabled Verizon Internet (choices are CBS, FOTA, IMS, Internet). No visible effect. Power cycled the phone. Didn't help.
Click to expand...
Click to collapse
http://www.math.ucla.edu/~jimc/moto-droid3/apps.shtml
They appear here, too.
http://pastebin.com/NFGMVi2a

Here are the relevant Galaxy Nexus maguro values:
Code:
<string-array name="networkAttributes">
<item>wifi,1,1,1,-1,true</item>
<item>mobile,0,0,0,-1,true</item>
<item>mobile_mms,2,0,2,60000,true</item>
<item>mobile_supl,3,0,2,60000,true</item>
<item>mobile_dun,4,0,3,60000,true</item>
<item>mobile_hipri,5,0,3,60000,true</item>
<item>mobile_bluetooth,7,7,1,-1,true</item>
<item>ethernet,9,9,1,-1,true</item>
<item>wifi_p2p,13,1,0,-1,true</item>
</string-array>
<integer-array name="config_protectedNetworks">
<item>10</item>
<item>11</item>
<item>12</item>
</integer-array>
<string-array name="radioAttributes">
<item>1,1</item>
<item>0,1</item>
<item>7,1</item>
<item>9,1</item>
</string-array>
<integer-array name="config_data_usage_network_types">
<item>0</item>
<item>2</item>
<item>3</item>
<item>4</item>
<item>5</item>
<item>10</item>
<item>11</item>
<item>12</item>
</integer-array>

I found out that neither device.mk nor full_tilapia.mk inherit from a telephony package (while the Mako (Nexus4) does through the following line in full_mako.mk:
Code:
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
This describes a similiar situation under ICS and the steps someone took to solve the problem,
this sounds like a promising way to me (The same things are missing in the Tilapia build):
http://groups.google.com/group/android-porting/msg/3a28bb754b9ba18a

now all we need are the device binaries... c'mon google

Synman said:
now all we need are the device binaries... c'mon google
Click to expand...
Click to collapse
i know, i shouldn't post here so feel free to delete my post, but are the device binaries something we just have to wait a little for google to release or are they closed source and we have to urge google to release them?
https://developers.google.com/android/nexus/drivers
only has the binaries for the grouper...
Someone wrote that the radio chipset is the same as for the galaxy nexus so shouldn't it be possible to use the gsm binaries from the galaxy nexus?

punshkin said:
i know, i shouldn't post here so feel free to delete my post, but are the device binaries something we just have to wait a little for google to release or are they closed source and we have to urge google to release them?
https://developers.google.com/android/nexus/drivers
only has the binaries for the grouper...
Someone wrote that the radio chipset is the same as for the galaxy nexus so shouldn't it be possible to use the gsm binaries from the galaxy nexus?
Click to expand...
Click to collapse
we gotta learn somehow, right?
This is the page to watch: https://developers.google.com/android/nexus/drivers
just as soon as it hits we will be able to do our own full builds and device deploys right from the master source branch.
In the meantime I've made the change inheriting telelphony to my .mk file and am in the process of making to see what all changes. I lost a ton of time today doing a maguro build hoping to salvage something from it and ultimately coming up empty.
That same line is in the maguro build. Something that I noticed is that tliapia refers to $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk) unlike the phones.

Have also found this at the bottom of full_base.mk
Code:
# Get everything else from the parent package
$(call inherit-product, $(SRC_TARGET_DIR)/product/generic_no_telephony.mk)
full_base_telelphony.mk includes full_base + telephony and brings along some extra stuff for the ride such as carrier apns and voicedialer.
telelphony.mk includes Mms.apk
----
looks like that's just about everything. It's probably redundant to have both full_base_telelphony and full_base in tilapia's mk file. Probably better to just use full_base_telephony. At the very least have full_base_telephony referenced first -- comments indicate the earlier entries take precedence.

Synman said:
looks like that's just about everything. It's probably redundant to have both full_base_telelphony and full_base in tilapia's mk file. Probably better to just use full_base_telephony. At the very least have full_base_telephony referenced first -- comments indicate the earlier entries take precedence.
Click to expand...
Click to collapse
Sounds good so far. Did you go the extra bit and try what else was mentioned in the post I linked to? Adding the extra parameters (see above) to the networkAttributes string-array and checking if telephony contains:
Code:
PRODUCT_PACKAGES := \
Contacts \
ContactsProvider \
Phone \
TelephonyProvider \
UserDictionaryProvider \
Mms
PRODUCT_COPY_FILES := \
development/data/etc/apns-conf.xml:system/etc/apns-conf.xml
PRODUCT_PROPERTY_OVERRIDES := \
keyguard.no_require_sim=true \
ro.com.android.dataroaming=true
-> Clean build and build freshly

Synman said:
That same line is in the maguro build. Something that I noticed is that tliapia refers to $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk) unlike the phones.
Click to expand...
Click to collapse
Right, that's because most of Tilapia derives from Grouper. You'll find the same there.

Related

AGPS Patch DesireHD 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO 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.

Notes and Info post
Post #2 has been consolidated. Keeping this post open, though.

cool, I'd like to try out the DHD version when it comes out. I can't stand the GPS on my phone.

It's being tested now. Hope to release tomorrow or Thursday at the latest. Want all the beta opinions back first!
Sent from my Inspire 4G using XDA App

Officially released! Lot quicker beta tests! Everyone said it worked perfectly and gave great results.
Start flashing and have fun!

ROM devs use it!
One user has stated in a private message:
"I added your worldwide and north America configs to my app and they both work good for me but even though it is on the fly a reboot is required for best results. Also the first lock every time I change it takes a little while but after that first lock, every lock afterwards is almost instant"
Two ROM devs are baking this into their next releases.
FYI: I use Virtuous Unity 2.35 right now and it works perfectly.

works fine on my DHD with miui 1.9.2 and lordmod kernel

Hi,
i have no changes (CM7 lastest NB & LordMod 7.1 Kernel).
with friendly greet
starbase64

starbase64 said:
i have no changes (CM7 lastest NB & LordMod 7.1 Kernel).
Click to expand...
Click to collapse
If you'd like to see if you will individually receive better results and if this patch is working, do this:
1. After you install the patch, reboot.
2. Install GPS Status from Android Market
3. Run GPS Status for about 5 minutes so the device can learn GPS satellites in your area.
4. Reboot again. Rerun GPS Status. It should be almost instant results...will be same with all apps.
Typically, I enable a GPS Status setting to keep the backlight on the whole time while testing. I like to see it actually working.
What people don't realize is that aGPS requires a bit of device learning to be very efficient.

Hi,
the behavior is like without the patch, a placebo effect.
with friendly greet
starbase64

As I have observed, there are some people who have great devices and great locations already. So, it won't be of help to everyone.
But for those of us who have the worst luck, it is a gold mine!
Thanks for trying it.

It is working perfect in Macedonia.. The www one.. I'm using MIUI and for the first time in months i have 7 sats in 5 secs.. i had 2-3 in 20min scan..
Thanks..
Sent from my Desire HD using XDA App

hi, i wellcome every effort on improving gps as i already did this myself (in my rom): you have there many settings i do not know and am curious on testing them.
but i also want to give out a waring about this one:
INTERMEDIATE_POS=1
me (being in germany) and some others (being in uk) had many trouble with this setting. when i had this i got a lock in 2sec but it wasn't a real lock. actually it wasn't locked to a signle satelite!
it caused only trobule. djscurf for example had regular gps drops during navigation until i removed it.
i just want to point out the experiences. if you post such stuff like a general soluttion you should only include general save options. maybe make that optional.
p.s. as far as i know ACCURACY_THRES does not make any sense without INTERMEDIATE_POS=1

It Works !!!!!
i am getting a quick location fix and an accurate one too!!!

Sorry, but what's the difference with the Angel Death patch here: http://forum.xda-developers.com/showpost.php?p=11342772&postcount=1 ?
Your patch looks like a copy of its /etc/gps.conf....
But I am maybe wrong...hope so !!??!!

michelD said:
Sorry, but what's the difference with the Angel Death patch here: http://forum.xda-developers.com/showpost.php?p=11342772&postcount=1 ?
Your patch looks like a copy of its /etc/gps.conf....
But I am maybe wrong...hope so !!??!!
Click to expand...
Click to collapse
It's heavily updated compare to regions vs continents vs this being worldwide unlike his.
He likes this one.
Oh and I removed internal bin usage as it slows the lock.
And more was and will be done.
Sent from my Inspire 4G using XDA App

a user said:
hi, i wellcome every effort on improving gps as i already did this myself (in my rom): you have there many settings i do not know and am curious on testing them.
but i also want to give out a waring about this one:
INTERMEDIATE_POS=1
me (being in germany) and some others (being in uk) had many trouble with this setting. when i had this i got a lock in 2sec but it wasn't a real lock. actually it wasn't locked to a signle satelite!
it caused only trobule. djscurf for example had regular gps drops during navigation until i removed it.
i just want to point out the experiences. if you post such stuff like a general soluttion you should only include general save options. maybe make that optional.
p.s. as far as i know ACCURACY_THRES does not make any sense without INTERMEDIATE_POS=1
Click to expand...
Click to collapse
I will continue to test with and without variables.
Sent from my Inspire 4G using XDA App

well do so. but i already went through what you are
sadly the settings do not work worldwide the same. some are no problem but others can cause serious trouble depending on the region. it kinda sucks to debug that when it's running fine on your device

Since it works for most countries so far I can build a patch for duetchland only. Private message me suggestions and we can test together.
Sent from my Inspire 4G using XDA App

crypted said:
Since it works for most countries so far I can build a patch for duetchland only. Private message me suggestions and we can test together.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
err, i have reprots of issues with that setting from germany, uk, spain, and sweden or norway (can't remember).
to be honest i very doubt that this setting works without flaws for most countries. and considering what i actually does it is not recommended anyway.
this setting tries to use different location ressources while you do not have enough gps satelites available. so it actually fakes a satelite lock! depending on your region and on your rom this could prevent the phone from searching further for satelites.
but anyway, everyone can try it. and if it works fine. i just wanted to note that here in case people get problems, to know what to look for.
edit: don't get me wrong. i wasn't asking for a patch for me, as i already have my on gps fix conf which till now has no problem reports anymore, since i removed that mentioned setting

AGPS Patch Sensation 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO 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.

Holding this post open. I consolidated this into the top post to make it easier to update across all threads.

Is there a patch for ASIA?
Oh sorry if you need this space in reserve....Please delete mod

rockmaster said:
Is there a patch for ASIA?
Oh sorry if you need this space in reserve....Please delete mod
Click to expand...
Click to collapse
It will be worldwide. If you want to test the v1.3, send me a private message and I'll give you a link.

Awesome, looking forward to this!

Chris19145 said:
Awesome, looking forward to this!
Click to expand...
Click to collapse
If you want to test it, send me a private message.
I think I solved the problem with flashing ZIP files via CWR. Otherwise, it will require abd push or root explorer.

Im running cm7 alpha with a good 10+ minutes to lock on GPS. I'll give the patch a shot and report back the results. link me. ( please)

Wow definitely can not wait for this..my gps takes forever and/or doesn't connect nd always gets lost..hope this is the light at the end of the tunnel
Sent from my HTC Sensation Z710e using XDA App

sheetmetalninja said:
Im running cm7 alpha with a good 10+ minutes to lock on GPS. I'll give the patch a shot and report back the results. link me. ( please)
Click to expand...
Click to collapse
Ahh, I was wonder why anyone would need this, its not a Galaxy S
With a Sense based rom I get 5-9 bird locks in about 5-10 seconds. Highest I've seen is 10 satellites.

tissimo said:
Ahh, I was wonder why anyone would need this, its not a Galaxy S
With a Sense based rom I get 5-9 bird locks in about 5-10 seconds. Highest I've seen is 10 satellites.
Click to expand...
Click to collapse
I really don't get your point.
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
For those interested, you could use v1.2 for either Inspire/Desire. It ought to work just fine.
I'll have v1.3 out by the middle of next week.

This looks good! No ROM I've tried works nearly as well with GPS as stock did for me. Hopefully this does the trick. When should the Sensation version arrive?

Well ... I've been playing with the file and created my own..
My theory ... less is more.
I have posted the files and you can try for yourself.
http://www.arvida1.com
Credit to crypted for original modded file.

steve841 said:
Well ... I've been playing with the file and created my own..
My theory ... less is more.
I have posted the files and you can try for yourself.
http://www.arvida1.com
Credit to crypted for original modded file.
Click to expand...
Click to collapse
Hijacking threads ain't cool. And as I told you on another thread, less isn't always more. There are a lot of factors including physical hardware (GPS unit on the phone), software (kernel: modded vs stock), and drivers. And, I gave you access to my upcoming release to test it. Not to build something for you to post on my thread before I even had a chance to release it.... Testers are requested for testing.
Each var has a purpose. It's a matter of will that purpose be supported from what I said above. Yes, dropping a bunch of them can work just fine for one schema. But, contextually it might not be so great for many other flavors of flashing.
I have a standard release schedule. v1.3 comes out next week. Sensation will be kicked up for official support at that time.

crypted said:
Hijacking threads ain't cool.
Click to expand...
Click to collapse
Don't hate...
Just trying to help everyone.

Wow steve,
I agree with helping everyone, but you should have kept your own edits to yourself and should have stated if anyone wanted to test your version out they should PM you and not to detract this thread.
Moving on now...let's just get this patch going from the OP, he was nice enough to let us test his script.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
Bsketball said:
This looks good! No ROM I've tried works nearly as well with GPS as stock did for me. Hopefully this does the trick. When should the Sensation version arrive?
Click to expand...
Click to collapse
Just extract the 1.2 file from post 2-depending where you are, of course. Push the gps.conf file to your phone which is /system/etc.

kpjimmy said:
Wow steve,
I agree with helping everyone, but you should have kept your own edits to yourself and should have stated if anyone wanted to test your version out they should PM you and not to detract this thread.
Click to expand...
Click to collapse
I must really be on another planet ... I just edit a file from the OP and give to everyone to try (after I made sure it worked for me) ... and I get flamed for it.
Im not asking for donations, fame or "thanks".. just a working GPS.
Crypted ... pm me and I will remove all my posts and create a new thread if that makes everyone happy.

No worries. I will release it as planned. Just realize I have put over 50 hours of time into this project. Many ROM devs and APP devs have requested and have been granted permission to use this in their stuff. Just let me know what you want to do with it and talk to me via private message. No one expects to wake up and see someone using their work unexpectedly and posting it on XDA.
And remember: everything was done for a reason and will go through a major revision on V1.4.
V1.2 WILL work on Sensation as mentioned above. You can find it in Note #2. However, you MIGHT have problems flashing it with CWR. If you do, copy the file using root explorer or abd push.
V1.3 will provide CWR support for sure. I revised the update script to use more universal procedures that are compatible across many devices. It will bring some important NTP and XTRA updates. It removes one variable.
V1.4 will be a major revision.
V1.5 will have a great surprise for people. ROM dev's are excited about this one.

Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.

quierotacobell said:
Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.
Click to expand...
Click to collapse
Yes, that sounds like it is not using your GPS at all. Typically, Maps and other apps will show you in a generic location based upon the tower(s) your phone is using for data transmission. It's a backup general location method when GPS isn't catching a signal.

quierotacobell said:
Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.
Click to expand...
Click to collapse
Are you in Long Island, NY? I grew up in Huntington worked in Melville for a number of years.
Back to this thread...have you tried the 1.2 file yet? Don't flash it, extract the file and get the gps.conf out and push the file onto your device. Or you can use root explorer to overwrite the file. But remember to have a gps.conf backup to revert to if you run into any problems.

AGPS Patch Triumph 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO 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.

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!

I'd like to know what differences were noticed & on what ROM. It appears that aGPS doesn't work on the Motorola Triumph in stock or CM7. I've tried this and other various gps.conf tweaks. Initial GPS cold lock always takes about 1-2 minutes, then it's faster right away. After reboot or a long time, it's back to the cold lock times. Enabling/disabling data or network location doesn't make a difference.

Whyzor said:
I'd like to know what differences were noticed & on what ROM. It appears that aGPS doesn't work on the Motorola Triumph in stock or CM7. I've tried this and other various gps.conf tweaks. Initial GPS cold lock always takes about 1-2 minutes, then it's faster right away. After reboot or a long time, it's back to the cold lock times. Enabling/disabling data or network location doesn't make a difference.
Click to expand...
Click to collapse
Could you provide me with more details of your setup. ROM, etc. Also, if you could send me the default gps.conf provided by the ROM you use, I'll have a look and see if there's something odd-ball necessary.
Your issue with reboots is that your /tmp/, or cache generally, is being wiped. This means that any aGPS data compiled or retrieved is cleared. Definitely a pain in the butt. ROMs should control this aspect.

Here's the latest one I used in my CM7 ROM, only difference noticed was if I turn on intermediate_pos=1 will result it in thinking the phone's in africa or thereabouts (as reported by some users), until a true lock is obtained. So I disabled it.
BTW The developer who worked on this before me mentioned that aGPS doesn't work and he tried doing stuff in the source, so that's why I'm guessing these settings won't either on the MT.
Code:
NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org
AGPS=http://xtra3.gpsonextra.net/xtra.bin
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
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
#Div6-PT1-GPS-LNA_LDO-00*{
#DEBUG_LEVEL = 3
DEBUG_LEVEL = 0
#Div6-PT1-GPS-LNA_LDO-00*}
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=3000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
# Add Google SUPL server and port for Huawei(FB0.B-3409)
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
################################
# EXTRA SETTINGS
################################
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
#################################
##### AGPS Carrier settings #####
#################################
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
QOS_ACCURACY=50
QOS_TIME_OUT_AGPS=95
QOS_TIME_OUT_STANDALONE=80
QosHorizontalThreshold=1000
QosVerticalThreshold=500
AssistMethodType=1
AgpsUse=1
AgpsServerType=1
AgpsServerIp=3232235555
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE

Whyzor said:
Here's the latest one I used in my CM7 ROM, only difference noticed was if I turn on intermediate_pos=1 will result it in thinking the phone's in africa or thereabouts (as reported by some users), until a true lock is obtained. So I disabled it.
BTW The developer who worked on this before me mentioned that aGPS doesn't work and he tried doing stuff in the source, so that's why I'm guessing these settings won't either on the MT.
Click to expand...
Click to collapse
Try an "Alternate" build of mine and let know results.
Source can be an issue. A lot of times, we find that ROM's are based on source for other phones. This causes issues for sure and is one reason why I include so many variable tweaks.
If it won't work, it won't work. But I'll try my best to work with you all if it is indeed possible.

All threads have had an overhaul that was way overdue.
High points:
Note discussion of what the patch does and what it replaces.
Note confirming ICS support from various users.
Note section has gotten long, but covers most questions I am repeatedly asked.
A total of 9 officially supported new devices.
Download section reminds people to backup their settings. You only need to backup /system/etc/gps.conf and /system/etc/suplrootcert if you have one. But, I never had to revert!
That being said, welcome to official support. Thank you all who confirmed and worked with me to ensure it was proper to offer official support to this device.
As always, please don't forget to click Thanks if you use or like this patch -AND- don't forget to Rate the thread. Donations are always welcome.

I don't think the Motorola Triumph should be listed as officially supported when I haven't heard anyone CONFIRM it makes a difference on the device (maybe a lot of placebo effects and coincidences). Especially when a developer (Tickerguy) who's looked in the GPS code and said that it doesn't work. Here's another thread discussing it where more MT users hang out:
http://androidforums.com/triumph-all-things-root/483710-agps-patch.html#post3808449

Whyzor said:
I don't think the Motorola Triumph should be listed as officially supported when I haven't heard anyone CONFIRM it makes a difference on the device (maybe a lot of placebo effects and coincidences). Especially when a developer (Tickerguy) who's looked in the GPS code and said that it doesn't work. Here's another thread discussing it where more MT users hang out:
http://androidforums.com/triumph-all-things-root/483710-agps-patch.html#post3808449
Click to expand...
Click to collapse
I appreciate your input. Yes, some of the older GPS hardware can find issue with the intermediate POS variable. That is why there is an Alternate build.
I had others confirm elsewhere and in private message that it works. I will remove support if it becomes to evident that I can no longer maintain it as such.
Will review that link, though.
Thanks!
EDIT: And I never recommend using CM7 as a ROM, especially nightlies, as my Notes section discusses. Sorry for not responding to your post a while back in more detail, either. Life plus XDA...

Agentc13, a guide from the other forum wanted me to pass along this since not everyone can post in these forums here:
"The aGPS isn't enabled in the stock ROM (or any other ROM). So how are you making it work? Does your patch change any of the Triumph base code for aGPS? "
If you want to continue the discussion there I bet more people are able to comment. FYI, both Tickerguy & Agentc13 have had the MT for a long time and if it came down to it, I would believe what they say than "a few random reports" of it working for the MT.

FYI: Method 1, the easiest of the methods for those unfamiliar with file managers or recovery, has been updated. Some people required that the script also mount the partition. I have added that line to all options available and updated the ZIP file. Thanks enigmaamit for confirming that the new PUSH script works.

Whyzor said:
Agentc13, a guide from the other forum wanted me to pass along this since not everyone can post in these forums here:
"The aGPS isn't enabled in the stock ROM (or any other ROM). So how are you making it work? Does your patch change any of the Triumph base code for aGPS? "
If you want to continue the discussion there I bet more people are able to comment. FYI, both Tickerguy & Agentc13 have had the MT for a long time and if it came down to it, I would believe what they say than "a few random reports" of it working for the MT.
Click to expand...
Click to collapse
Definitely on my list to research and determine if these reports are false positives. I'm not one to just keep going with something that simply cannot work.
First I need to arm myself with some more knowledge on the phone, ROMs for it, and other commentary. Then, I need to devise a couple test builds for placebo fun.
I'm with you, not against your commentary at all. I just don't want to drop something that was confirmed to be working.

Am using a spice CSl MI410 , a GSM version of Triumph.This patch worked for me ,when I was static ,with clear sky ,on the latest sharp rom . This got me locked to 8 plus (cell towers I guess) in less than one minute . Where repeted tries with stock gps.cnfg files n patches from other thread took nearly 8 plus minutes. I am surrounded by 4 to 5 cell towers less than50 meters .... still gave me accuracy of 30mtrs before and this one gave upto 6mtrs . I will switch roms n switch places n try to get back here now give feedback.
Sent from my FIH-FB0

zailer said:
Am using a spice CSl MI410 , a GSM version of Triumph.This patch worked for me ,when I was static ,with clear sky ,on the latest sharp rom . This got me locked to 8 plus (cell towers I guess) in less than one minute . Where repeted tries with stock gps.cnfg files n patches from other thread took nearly 8 plus minutes. I am surrounded by 4 to 5 cell towers less than50 meters .... still gave me accuracy of 30mtrs before and this one gave upto 6mtrs . I will switch roms n switch places n try to get back here now give feedback.
Click to expand...
Click to collapse
Thanks for that info! Glad it works for you! Let me know about other ROM's as you have time...

Just a friendly notice that the thread has been updated.
There is a new build which I recommend. Before questioning or inquiring why I removed the use of SSL, review the NOTE on the matter. This has proven to be a faster operation by tests in various regions and numerous devices.
Lastly, I added a section for asking questions. Review that before communicating here. It gets really old seeing that people refuse to read what I've worked hard to write especially when it usually answers the questions asked.
Don't forget to consider donating if you appreciate the work and find it useful.

I'm using the 3.x
Motorola Triumph with cm7
I tried to install with the AD Push Installer and did not work..
It worked with the CMW Installer,
I went outside right after the flash and it locked with less than 5 seconds onto 8-11 sats...
I rebooted the phone and tried again and it also locked very fast less, than 15 seconds...
The next morning I tried again and now is taking more than 3 minutes to find the correct location, it locks close to Africa and stays there until it finds the correct location. It's locking on 0*0.002'N & 0*0.0'E
How this can be fixes or how to pevent it to lock at that location??...
I'm using "Gps Stats & Toolbox" to check location and sat lock status

BroadVoice said:
I'm using the 3.x
Motorola Triumph with cm7
I tried to install with the AD Push Installer and did not work..
It worked with the CMW Installer,
I went outside right after the flash and it locked with less than 5 seconds onto 8-11 sats...
I rebooted the phone and tried again and it also locked very fast less, than 15 seconds...
The next morning I tried again and now is taking more than 3 minutes to find the correct location, it locks close to Africa and stays there until it finds the correct location. It's locking on 0*0.002'N & 0*0.0'E
How this can be fixes or how to pevent it to lock at that location??...
I'm using "Gps Stats & Toolbox" to check location and sat lock status
Click to expand...
Click to collapse
Please review the thread. Provide answers to the questionnaire and we can go from there. However, this doesn't sound patch-related but something else. Try disabling all "location" options in Android Settings aside from GPS.

3.x cWM patch doesn't work. Running Miui 1125. Now i'm stuck on "searching for gps." It zooms to africa then to the correct location then it just sits there "searching for gps."

hungrymr2 said:
3.x cWM patch doesn't work. Running Miui 1125. Now i'm stuck on "searching for gps."
Click to expand...
Click to collapse
Could you read the thread and provide details as requested please? Did you read the notes? Are you sure it flashed the patch? Try the recommended no SSL build? How about the alternate build? Tried another ROM to be sure it isn't your ROM? Restart the device? Pull battery for a minute and try? Active and unfiltered data connection?
This it didn't work comment gives none of us a starting point to help you. I didn't mean to waste a lot of time making the thread content for nothing. It's purpose is to self repair and give us a base would everything fail.
Sent from my Transformer Prime TF201 using XDA

have the same lock to equator problem after flashed the google no ssl 3.1with cwm.
my rom is cm7 tg reloaded march 4th build freash installed last night, kernel is the default one from this cm7(the OCkernrl？) my location is san jose california. GPS app is the google map. my GPS lock was never as smooth as my pervious htc hero or my wife's lg optimus v.
before applied the agps patch, lock was little bit slow. made a recovery image before install the patch. after patch gps make a rapid fake lock to N0.00 W0.00 near africa then following by the quite slow real lock. restore to the recovery, problem goes away.
---------- Post added at 09:59 AM ---------- Previous post was at 09:36 AM ----------
have the same lock to equator problem after flashed the google no ssl 3.1with cwm.
my rom is cm7 reloaded march 4th build. before applied the agps patch, lock was little bit slow. made a recovery image before install the patch. after patch gps make a fake lock to N0.00 W0.00 then following by the quite slow real lock. restore to the recovery, problem goes away.

Team Cody!
Member List (in no particular order):
@thewisenerd
@omerjerk
@#Superuser
@dhrumangajjar
@navinn
@xaak
@Agaphetos
WANTED
- Testers - to beat the hell out of our ROMs
- Graphic Designers - boot logos, wallpapers, banners(one or two people)
- Themers - theme EVERYTHING!!!
- Co-Dev(s) - Do i really know what I'm doing most of the time (the answer to that is "probably not")
- Moral Support - LOL
- Suggestions - anything you got - Lay It On Meh!!

our works:
MiniCM9
CodyROM
CM9 Build #15
Evervolv
AOKP
OmniROM
AOSPA-legacy
note to self: add all the works, links
find a thread tagged [TeamCody], that's ours

Team-
@thewisenerd
@omerjerk
@#Superuser
@dhrumangajjar
@navinn
Source- https://www.github.com/CodyROM/
Blog- http://www.codyrom.wordpress.com/
Yea, we need support and suggestions!

todo list:
generalise this
First, finish the work on "reverse mounter"; as it is *technically speaking* easy (for me, to write scripts, that do things); and is pretty straight forward (no aimless edits or so)
fix gps in omni
fix video recording in omni
udpate twrp
switch to wlan0 in omni
random trolling lol

@thewisenerd
we should fix the date bug in notif bar..
is that xml derps..??

navinn said:
@thewisenerd
we should fix the date bug in notif bar..
is that xml derps..??
Click to expand...
Click to collapse
No, its a java derp

Compiling CM11/Kitkat for pico!
I assume you have knowledge of building with source, even if not, I don't really care (for there are a lot of guides).
First, get *all* the required packages installed. As for what I mean by *all*, is not really a question for me to answer. I used <insert-random-guide-from-xda> here, and the source.android.com's guide on initializing, just to be sure.
As for java, I use openjdk. *most* sources today support openjdk, elseways, either, you could force it to be compatible by removing just ONE line in build/core/main.mk
So, that's the packages part.
As for syncing sources, as most guides say, you DON'T need to use a ~/system folder or anything. You can use a folder, anywhere.
Just open up a shell, wherever you want to get the sources synced, and type in the following commands.
I assume you have the repo tool installed. IMHO, you should really create a "bin" folder in your homefolder (short linked as "~/") using the following commands:
Code:
mkdir -p ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Then, open up your ~/.bashrc file, using Geany (a better alternative to Gedit, perhaps ), using the command:
Code:
geany ~/.bashrc
Just insert this line, randomly (preferrably at the end of the file).
Code:
PATH=$PATH:/home/<insert-your-username>/bin
Now, for syncing sources. Make sure you are a directory above working folder.
Code:
mkdir -p <insert-ROM-name>
cd <insert-ROM-name>
Now, that you are inside the working folder, take your pick about the ROM that you are going to compile. This tutorial is for CM11, so i'd be running the following command.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Yes, you can reference this from a cm10.2 source that you've already downloaded, and this will reduce the size required to download. Why, you could even reference this from an ICS source (just saying, not meant to be even tried).
If you aren't really building for mac, I'd suggest that you don't download the darwin repos.
Short way that I use:
Run following command in working folder.
Code:
mkdir -p .repo/local_manifests
grep "darwin" .repo/manifests/default.xml > .repo/local_manifests/local_manifest.xml
Open up local_manifest.xml using
Code:
geany .repo/local_manifests/local_manifest.xml
Add these lines on top:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
and the following line at end.
Code:
</manifest>
Now open up "search and replace" dialog box.
Search for:
Code:
<project
and replace with:
Code:
<remove-project
Voila, you've removed all the unnecessary darwin repos.
Now, for repo syncing.
I'd seriously suggest that if you live in parts of the world where the internet speeds are less than 1 m'b'ps (~128 k'B'ps (worst case, mine's around 60 k'B'ps, and I've known people with speeds ranging 30 k'B'ps), you'd sync just one repo at a time (the -jx).
run:
Code:
repo sync -j1
Else, if you have a super fast internet connection, please don't brag. Use a higher number, preferably 3, or 4.
Now, sync these repos, while I attend my classes. I'd return back and write part 2.
edit: part 2; go here: http://forum.xda-developers.com/showpost.php?p=49349691&postcount=8

Compiling CM11/Kitkat for pico! PART 2
reserved
Also, yes, you could use this localmanifest here: https://github.com/PicoKat/local_manifest/blob/dev/local_manifest.xml
but, you'd miss out the learning process
Anyways, this post would take up part 2 of the tutorial.
This is purely device specific. and, there's already a guide on android development section (of this device), the reason why I didn't make a new thread.
part 2 begins here:
Ok, so, you'd synced the repos?
Now, as opposed to roomservice, I'd prefer manually cloning the device tree, kernel, and vendors.
Clone a device tree (galaxyfreak's, or mine), into /device/htc/pico.
Clone the kernel sources from here: https://github.com/PicoKat/android_kernel_htc_pico
Clone the vendor tree from here: https://github.com/PicoKat/android_vendor_htc_pico
(note: if you are using my device tree, that has ION, you'd have to use my vendor tree, with updated blobs here: https://github.com/vineethraj49/android_vendor_htc_pico)
Ok, so that part's setup.
Now, lets move on to cherry-picking, and/or patching some stuff (from legaCyMod).
Note: you could have just added these to local_manifest too...
android_build:
Hopefully, you should know how to add remotes, and working with them, if not, click on the show content, below (as a sample for android_build):
Code:
git remote add legacymod git://github.com/legaCyMod/android_build.git
git fetch legacymod cm-11.0
git cherry-pick <commit-id>
where commit id's the looong "number" following /commit/ in the URL.
1. always rebuild build.prop
2. bringing back squisher
3. Removing TTS data
4. Revert adding auditd
5. add kitkat sdk versions
6. Revert "add drawables for all densities" (seriously, this saves space.)
7. adding support for our recovery
frameworks/av:
1. enable meta mode for video msm7x27a
2.bring back support for legacy omx
3. support legacy qcom audio variant
vendor/cm:
1. bring back squisher
2. revert adb authentication (yea, screw adb while dev'ving
3. remove ze bloats
Next, clone media-legacy to hardware/qcom/media-legacy, and display-legacy to hardware/qcom/display-legacy.
waait!!!!
You need to do some patches in some files. required to fix up camera.
patch two files, manually, making some sense out of this:
frameworks/base: https://github.com/szezso/vivo_cm11_patches/blob/d819363fe7d181e73841d3fa35c1b8c0c7d7c046/frameworks_base.patch
frameworks/av: https://github.com/szezso/vivo_cm11_patches/blob/2f1c87f4453c1c7c88e3c7d2b011994f894fe669/frameworks_av.patch
The next step:
Get prebuilts, seriously.
Code:
cd vendor/cm
./get-prebuilts
Then, "cd" back to root of source dir.
Run the following commands:
Code:
. build/envsetup.sh
brunch pico -j4
Hopefully, you should see an output package by the end of <insert-time-directly-propotional-to-crappiness-of-computer>

For batch-resizing bootanimation (in linux):
resizing part:
Code:
for file in *.png; do convert $file -resize 320x320! $file; done
you'd know which part to edit
for zip'ing part:
Code:
zip -r -y -q -0 bootanimation.zip *
will edit this later

Using CCahe
Now something very important who gonna compile ROMs, use CCache. It'll spped up the building process.
CCache - Compiler cache
How to use?
> Open a Terminal(Ctrl+Alt+T)
>
Code:
gedit /.bashrc
[You can use any alternative to gedit )
> Add the following lines to it:
Code:
export USE_CCACHE=1
export CCACHE_DIR=/[COLOR="Red"]source[/COLOR]/prebuilts/misc/linux-x86/ccache
Source here is the folder in which you have the code downloaded.
>
Code:
cd source
>
Code:
prebuilts/misc/linux-x86/ccache/ccache -M [COLOR="red"]25G[/COLOR]
25G = 25 GB of space to be used as CCache. You can use any value in this.
How does ccache work ?
Well , in short , what it does is that for C and C++ programs it caches the output. One it detects that the program is getting repeated it directly sends out the output and thus reduces the time of compilation.
After using ccache you will really feel the difference in the compilation speeds of your ROMs and kernels. //Copied.
Credits - Red Devil.

I use CCACHE, but the only difference is that I don't specify the directory. also, I did a "apt-get install ccache" long ago, and set file size according to that. Its still working just as fine.
and oh, yes, adding that USE_CCACHE=1 to .bashrc is required

IRC and you!
In case you came here via my signature, sorry for that. But really, you need to know some stuff about IRC, before going to a channel. The pico channel is #pico :fingers-crossed:
So, you might have heard about IRC, even logged into one (freenode, probably, the webclient of it), (and most probably saw that there was no activity and just closed that browser tab).
Let's take a timeout here to talk about IRC.
Instead of me talking about IRC, (and you being too lazy to Google stuff (not intended to those who solve problems themselves (not noobs (?) :wink: :wink)), here's a nice article by Rey Bango that you might want to read: IRC is Back: Here's Your Starter Guide
So, instead of me talking blah blah, and you skimming through most parts, which I assume, you did in the above article (considering you taking the energy to read it), here's what you need to know about Freenode:
..but in terms of development, from my experience, most developers tend to jump on Freenode - and rightfully so.
Click to expand...
Click to collapse
So, just to let you know, in those channels (where you thought there was no activity), there actually is a lot of discussion going on. You just don't know it yet.
So? What am I supposed to do? Keep a browser tab open? Don't expect me to say "Exactly not!" because that too is a viable option, though not very practically possible.
Here's where bouncers come in. Known as BNCs, here's what they do:
A bouncer (BNC for short) is a piece of software used to relay the communication between an IRC client and the network it is connected to, acting as a Proxy.
So, whats the point you ask? The reasons and benefits of using a bouncer are many and include hiding the real IP you are connecting from, protecting your nickname and channel from being taken on networks that don’t provide channel-/nickname registration and most of the time they’ll also notify you of private messages that came in when you’ve been disconnected – of course only when the bouncer can stay online being connected from a server.
Click to expand...
Click to collapse
Coming as either free or paid (either of them being useful, nonetheless), and cutting all the tech jargon, they allow you to "stay online" allowing you to close that browser tab you feared to keep open.
So, in case you actually read through the above quoted text, software!? Being connected from a server? Nah, just kidding. Here's where online BNC providers come in. They provide you a username, (and of course a password, which you need to select), and they host for you the BNC software (in most cases, ZNC).
Most BNCs allow caching of messages, i.e. buffered playback. Their servers are connected 24x7. You, the user, connect to their server, and through their server join the channels. You then, disconnect from their channel. Poof! But, their server still remains connected to the channels, and logs the messages in the channels, and any PMs sent to you. The next time you connect to their server, it gives you all the logged stuff, and it gets cleared. The next time you disconnect, ... Well, you get the flow.
Questions. That's what you go to IRCs for (mostly. I do it for the conversations ). How exactly do you ask questions? Similar to on XDA, but slightly different. I couldn't have said better than l3dx's answer on stackexchange:
Rule #1: Don't ask to ask
Rule #2: Behave as you would do in a real life conversation
Rule #3: Be patient. If there is no activity, it usually means that no one has read what you wrote yet. If no one responds, they don't know or didn't notice. You can re-try after a while, or ask if anyone has any clue with regards to your question x minutes ago.
Click to expand...
Click to collapse
What does Rule #1 mean?
Something very similar to what zxcdw said in the comments:
"Don't ask to ask. Just ask". Don't ask people "Anybody around?" or let alone highlight others to ask if they are around. It's just easier to drop your question, hang around and wait. Ask again in a few hours or so.
Click to expand...
Click to collapse
Also, use English, in most channels, if possible. Stay safe, don't open any unknown links or links to untested software, scripts and stuff. Stay safe.
IRC clients help you stay connected. A few simple google searches will get you going in the right direction. I personally use XChat IRC on Linux, but there are a lot of other good IRC clients available too.
Free bouncers should do, mostly. I use bnc.im, seen people using EliteBNC, some people installing ZNC in their own private servers that are online 24x7, YMMV.
That's about it for IRCs. Happy chatting!
P.S. Make sure you ask the right questions in the right channels.

sys2cache... something to help with less /system partition size.
note: this would be running at boot, with busybox, so,...
Code:
# algo:
# if read(switch_file=1)
# goto case 2.
# else case 1:
# get /system size
# get /data size
# get /cache size
# check /cache remaining size
# check for files in /system
# check for the following folders
# name generic size priority
# ./etc 3.1M 6
# ./vendor 36K 9
# ./addon.d 12K 8
# ./core 76K 7
# ./xbin 1.6M 5
# ./fonts 18M 1
# ./usr 21M 2
# ./media 4.8M 3
# ./bin 5.5M 4
#
# switch = 0;
# file folder_list;
# for i in list_args
# if (getsize($i) < getfreesize(/cache))
# mv $i /cache/$i
# mount bind /cache/$i /system/$i #fix syntax
# ifexists(/system/$i)
# switch = 1;
# folder_list >> $i
# else
# switch = 0; break;
# else
# echo "fak this, we're out of space!"
# fi
#
# echo $switch > switch_file
#
# sync; exit!
#
#
#
# case 2:
#
# for i in xargs(folder_list)
# do
# mount bind /cache/$i /system/$i #fix syntax
# done
#
# sync; exit!
#
#
#
# todo:
# * actually code this shiz
# * better error checking
# * add logging

Hey!
Make sure y'all check this!
http://team-cody.github.io/ :highfive:

welcome to another member @Agaphetos

Source- https://www.github.com/Team-Cody/
todo: update this post with website link.
lol, nvm this post

shameless bump.
since my board exams are over (sort of; only CS is left); i thought of building something for pico (a looong time since I did so).
Waht do I build?
At first thought; one *pure* CM9 build with *some* cherry-picks;
another; an updated CM11 build (updated sources and stuff)...
fixing up omx and stuff on Omni is on the "to-do" list and going to take some 'time' to do; so don't expect it to be fixed already :silly:
So; which one do I 'invest' time in? :cyclops:

@thewisenerd
MTP and OTG in cm9
Cm11 only if you can make it compressed
Sent from my Xperia S using XDA Free mobile app

mirhl said:
@thewisenerd
MTP and OTG in cm9
Cm11 only if you can make it compressed
Sent from my Xperia S using XDA Free mobile app
Click to expand...
Click to collapse
you mean MTP && USB tethering?
edit: a test build will be up today (if build goes well, that is).
edit: here you go: cm-9-20150315-UNOFFICIAL-pico.zip

thewisenerd said:
you mean MTP && USB tethering?
edit: a test build will be up today (if build goes well, that is).
edit: here you go: cm-9-20150315-UNOFFICIAL-pico.zip
Click to expand...
Click to collapse
This is one sick ROM - good job !!!

As many know, the developer of Textsecure has abandoned secure sms messaging in favor of over the internet messaging. In addition, his insistense on including Google proprietory blobs in his app and the requirement of having the spying Google services framework, totally negates security. Here is a fork of Textsecure, which is a pure sms application. No Google binaries are included. No GAPPS are needed. This app fully replaces stock messaging.
In addition, I have made the following changes: 256 bit symmetric AES encryption instead of 128 bit and 192 bit elliptic curve encryption instead of 160 (160 is weak). I have also increased the iteration when generating random numbers.
Credit: Original creator Moxie Marlinspike; Initial fork by Bastien Le Querrec and Carey Metcalfe
Application is attached. If you want to build it yourself, see below.
Source: http://d-h.st/OsQ7
To build, unzip the source code, make sure android sdk is in your path and execute ./gradlew build.
Edit: In source, open local.properties and put there your android sdk path
P.S. This app won't work with older versions of Textsecure, because you have different length keys and will fall back to unencrypted transmission. Same will apply if the other person has stock SMS. In other words, both users must have this app to communicate securely.

optimumpro said:
As many know, the developer of Textsecure has abandoned secure sms messaging in favor of over the internet messaging. In addition, his insistense on including Google proprietory blobs in his app and the requirement of having the spying Google services framework, totally negates security. Here is a fork of Textsecure, which is a pure sms application. No Google binaries are included. No GAPPS are needed. This app fully replaces stock messaging.
In addition, I have made the following changes: 256 bit symmetric AES encryption instead of 128 bit and 192 bit elliptic curve encryption instead of 160 (160 is weak). I have also increased the iteration when generating random numbers.
Credit: Original creator Moxie Marlinspike; Initial fork by Bastien Le Querrec and Carey Metcalfe
Application is attached. If you want to build it yourself, see below.
Source: http://d-h.st/JsjA
To build, unzip the source code, make sure android sdk is in your path and execute ./gradlew build.
P.S. This app won't work with older versions of Textsecure, because you have different length keys and will fall back to unencrypted transmission. Same will apply if the other person has stock SMS. In other words, both users must have this app to communicate securely.
Click to expand...
Click to collapse
Bravo

Thanks sounds promising after TextSecure drops his SMS encryption. I'm currently using Tinfoil-SMS.
The question is if you gonna release this for the mass or just only here on xda (maybe F-Droid build or another place)?!
And a compare between the binary (for future possible releases) and the source would be nice, something like this:
unzip -p suspectsmsecure.apk META-INF/CERT.RSA | keytool -printcert
unzip -p suspectsmsecure.apk META-INF/CERT.RSA | keytool -printcert | grep SHA-3
unzip -p knowngoodsmssecure.apk META-INF/CERT.RSA | keytool -printcert | grep SHA-3
jarsigner -verbose -verify suspectsmsecure.apk
To see all necessary stuff about the certs to compare the downloaded one.

CHEF-KOCH said:
Thanks sounds promising after TextSecure drops his SMS encryption. I'm currently using Tinfoil-SMS.
The question is if you gonna release this for the mass or just only here on xda (maybe F-Droid build or another place)?!
And a compare between the binary (for future possible releases) and the source would be nice, something like this:
unzip -p suspectsmsecure.apk META-INF/CERT.RSA | keytool -printcert
unzip -p suspectsmsecure.apk META-INF/CERT.RSA | keytool -printcert | grep SHA-3
unzip -p knowngoodsmssecure.apk META-INF/CERT.RSA | keytool -printcert | grep SHA-3
jarsigner -verbose -verify suspectsmsecure.apk
To see all necessary stuff about the certs to compare the downloaded one.
Click to expand...
Click to collapse
The source have been there from day one, see the OP. I don't think I am going to release it on Googleplay. Maybe F-Droid... .

Some reported F/C on entering passphrase for local encryption. I have just posted the fix. See the OP.

Thanks for this! Think you could start a github repo for the fork or some such? Downloading the source code in a zip file from a forum is a bit less convenient, and means I can't use git to pull updates.

optimumpro said:
The source have been there from day one, see the OP. I don't think I am going to release it on Googleplay. Maybe F-Droid... .
Click to expand...
Click to collapse
+1 for f droid and github or similar (though I wouldn't dabble with source code, would still like other devs contributing easily)

Nice, I'll give it a try.

Yes please.. Interested in git / alternate host

@optimumpro:
Thanks for pointing that out. Are you affiliated with SMSsecure? We will see how this project is holding up.
How did you make these AES and elliptic curve changes?
Regards

thomson.aa said:
@optimumpro:
Thanks for pointing that out. Are you affiliated with SMSsecure? We will see how this project is holding up.
How did you make these AES and elliptic curve changes?
Regards
Click to expand...
Click to collapse
I am not affiliated with smssecure. I initially contacted them with a few changes, but they were not receiptive, which is their right. With regard to changes, there are a few java files where you change numbers from 16, which equals 128 bit to 32 and from 20 (160) to 24.
I have modified the app to my taste and shared it...

F droid has SMSSecure 0.5.1, I wanted to confirm if it's a the same app?

wis3m0nkey said:
F droid has SMSSecure 0.5.1, I wanted to confirm if it's a the same app?
Click to expand...
Click to collapse
Serious? Right above your post...
optimumpro said:
I am not affiliated with smssecure. I initially contacted them with a few changes, but they were not receiptive, which is their right. With regard to changes, there are a few java files where you change numbers from 16, which equals 128 bit to 32 and from 20 (160) to 24.
I have modified the app to my taste and shared it...
Click to expand...
Click to collapse

Wakamatsu said:
Serious? Right above your post...
Click to expand...
Click to collapse
Oops thanks. I read the post but was comparing text secure and SMS secure (this app, while reading post I didn't know about existence of separate app on f droid)
Thanks for pointing it out.

wis3m0nkey said:
Oops thanks. I read the post but was comparing text secure and SMS secure (this app, while reading post I didn't know about existence of separate app on f droid)
Thanks for pointing it out.
Click to expand...
Click to collapse
I posted this app on XDA before SMSSecure guys published theirs on F-Droid. Both apps are rock solid stable thanks to Moxie Marlinspike, the original author. My version is a bit tougher on encryption.
I have noticed that SMSsecure guys keep implementing some minor changes (icons et al) which don't involve encryption/sms transmission/user interface. I am not going to change graphics for the sake of version bumping.
So, I am stopping here unless there is a major change in encryption protocol...

Thank you for sharing your changes.
I hope you will continue to provide this very useful service to the security conscious community.

Hello,
SMSSecure work very good on my HUAWEI Ascend Mate 7 but not on the HUAWEI P7 from my wife.
The list of contacts flash always ... what's happening with this ?
GO Sms is disable and SMSSecure is set as the default SMS application.
I don't understand why doesn't work !

Could you help me and reply to me ?

[email protected] said:
Could you help me and reply to me ?
Click to expand...
Click to collapse
Try smssecure on fdroid.
Not as good of encryption but still very good.

[email protected] said:
Hello,
SMSSecure work very good on my HUAWEI Ascend Mate 7 but not on the HUAWEI P7 from my wife.
The list of contacts flash always ... what's happening with this ?
GO Sms is disable and SMSSecure is set as the default SMS application.
I don't understand why doesn't work !
Click to expand...
Click to collapse
Flash as in contacts blink or does it mean all contacts get deleted?
Sent from my Xperia Z1 using Tapatalk