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
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 tentative support.
Tentative support is based upon reports from users of this device who decided to use the patch and report back on their own.
Reports indicate great success.
crypted said:
Currently, this is tentative support.
Tentative support is based upon reports from users of this device who decided to use the patch and report back on their own.
Reports indicate great success.
Click to expand...
Click to collapse
Thank you for your work... The only issue/non-issue I can see is that our Blades have stellar GPS reception out of the box (at least on CM7 and latest 2.3.7 ROMs).
My guiding line in Android is: if it aint broke, don't fix it, but for people encountering reception problems, this may help.
Good to see people sharing good practices and making our experience better !
vulpy said:
Thank you for your work... The only issue/non-issue I can see is that our Blades have stellar GPS reception out of the box (at least on CM7 and latest 2.3.7 ROMs).
My guiding line in Android is: if it aint broke, don't fix it, but for people encountering reception problems, this may help.
Good to see people sharing good practices and making our experience better !
Click to expand...
Click to collapse
This patch is here because multiple users had issues, requested my assistance, and found repair with my work.
Sent from my Galaxy Nexus using xda app-developers app
GPS on the Blade is perfect. No patches needed
Asus TF300T | ZTE Blade
QuantumFoam said:
GPS on the Blade is perfect. No patches needed
Asus TF300T | ZTE Blade
Click to expand...
Click to collapse
Do you make a habit of bot reading before posting?
Just because your phone works great doesn't mean that everyone else is in the same boat.
I only bring support to devices after multiple people have issues and we resolve them.
Therefore, support is here for the FEW that aren't so lucky as to have a perfectly working GPS unit.
Sent from my Galaxy Nexus using xda app-developers app
crypted said:
Do you make a habit of bot reading before posting?
Just because your phone works great doesn't mean that everyone else is in the same boat.
I only bring support to devices after multiple people have issues and we resolve them.
Therefore, support is here for the FEW that aren't so lucky as to have a perfectly working GPS unit.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
1. Chill
2. Okay I may be mistaken. But if its not a hardware issue, Our cm10 has a flawless GPS
3. Chill Again
Asus TF300T | ZTE Blade
QuantumFoam said:
1. Chill
2. Okay I may be mistaken. But if its not a hardware issue, Our cm10 has a flawless GPS
3. Chill Again
Asus TF300T | ZTE Blade
Click to expand...
Click to collapse
Before directing an OP to chill, consider that some OP's might maintain 50+ threads not just on XDA alone and receive over 100 comments and several dozen private messages daily.
Now, consider that 60% of all comments and messages are from people who fail to read what's clearly written in front of them or to consider why a patch is provided for. It gets old having to repeat and repeat and repeat and repeat and repeat.
EDIT: Did I mention it's really getting old having to repeat?
crypted said:
Before directing an OP to chill, consider that some OP's might maintain 50+ threads not just on XDA alone and receive over 100 comments and several dozen private messages daily.
Now, consider that 60% of all comments and messages are from people who fail to read what's clearly written in front of them or to consider why a patch is provided for. It gets old having to repeat and repeat and repeat and repeat and repeat.
EDIT: Did I mention it's really getting old having to repeat?
Click to expand...
Click to collapse
I know dude. I have a few threads like that and in case you haven't noticed, I'm an RC too. I know exactly how you feel.
I apologize for not reading. My bad
Asus TF300T | ZTE Blade
Related
Developers: Please read this!
Host your ROMs, Themes and everything else
No more searching for free hosting space to place your ROMs with limited download speeds and 60 second waiting periods for downloaders.
7/23/2011
We have been hard at work creating better tools for you developers to manage your releases on Community Release.
Along with the new site release we just made, you now have the following features:
Browser based File Manager and/or FTP Access to your Files.
Dedicated Forum area with Full moderation rights.
Full release access to the Community Release Database.
A FREE central repository for the Android Community with FREE, Unlimited bandwidth File Hosting.
We are constantly working on the site and some of the functionality we are developing is:
Each developer NOW HAS their own section in our forums where you can post all the info about your ROMs.
You will also have ROM upload space (no more searching for free accounts) and your ROM files will be tied to the database so people can download them directly and not have to switch between the ROM database and XDA or whatever else.
You will have full access to anything related to your ROMs so you can keep the info up to date.
We will provide any RSS / XML streams for other people to use for almost anything. So if you want to write a single ROM update program for the Android Phones, you can write the app and take the latest info directly from the ROM database. This will mean that the data will always be the latest info from a common location as long as we can get your support.
You’d be able to see how many times you’re ROM has been downloaded and how the community rates it. It’s up to the you and the community to let us know what you want from the system.
As users, you can register in the system and then follow:
Releases
Devices
Developers
Rate the releases you like so other know if they are good or not.
Soon you wil be able to leave comments with your ratings too
We want to do this right. We want to build something that the community will really use.
This is just the start of things to come but we need need your input!!!
What do you want to see?
What will help you get your ROMs, Themes, Applications and more out to the community quickly and easily?
Please contact me at [email protected] with your contact information and include the information listed below (or as much as you feel comfortable sharing) and any thoughts and suggestions no matter how wild they may seem. We'll consider anything.
I'm setting up profiles for everyone for developer accounts that would include:
Full Name
Email Address
Nick Name
Location (or at least time zone)
Twitter Account
Blog Page
Home page
A brief description about yourself and what you develop
That should do for now.
Thanks again.
Simon
MobileTweek / AndroidSPIN / Community Release
awesome thanks =) i was thinking about switching from jf1.5 now i wont, since Hbuild doesnt support google synce
Good idea! This should be stickied if you can do a comparison table with all the builds.
One little typo, JF ADP 1.5 does not come with AIM/Yahoo/MSN out of the box.
t1n0m3n said:
One little typo, JF ADP 1.5 does not come with AIM/Yahoo/MSN out of the box.
Click to expand...
Click to collapse
Thanks.
I'll make the change.
Keep them coming.
The more info I can get, the better.
A couple of corrections:
1. Haykuro's 5.0.x builds (both H and G) are based on Android 1.5, not 1.1.
2. Haykuro's 5.0.xH builds do indeed do Google sync, there's just no way to configure it.
What do S and E mean? Standard and ?
all the builds are 1.5cupcake
spy_owl2 said:
A couple of corrections:
1. Haykuro's 5.0.x builds (both H and G) are based on Android 1.5, not 1.1.
2. Haykuro's 5.0.xH builds do indeed do Google sync, there's just no way to configure it.
Click to expand...
Click to collapse
Thanks.
Fixed.
t1n0m3n said:
What do S and E mean? Standard and ?
Click to expand...
Click to collapse
Standard and Enhanced (or not standard).
I've added a legend to the bottom.
Thanks.
t1n0m3n said:
What do S and E mean? Standard and ?
Click to expand...
Click to collapse
Enhanced, i guess.
great thread.
+1 vote for sticky
wyinsz said:
Enhanced, i guess.
Click to expand...
Click to collapse
Correct.
Already fixed.
I welcome suggestions for how to show things better if anybody has ideas.
and all builds have camera/video camera, either Standard or Enhanced.
all builds have Virtual Keyboard, either HTC IME or Standard.
"Enhanced" perhaps?
EDIT: Whoops, I didn't realise people replied so quickly on this forum ><
wyinsz said:
and all builds have camera/video camera, either Standard or Enhanced.
all builds have Virtual Keyboard, either HTC IME or Standard.
Click to expand...
Click to collapse
Do you know which ones have which?
Im curious as to the HTC lockscreen on H's 5.0.2 and there will have to be an update to include his new fully stable 5.0.2+1.5 = Hr6.0
Dantehman said:
Im curious as to the HTC lockscreen on H's 5.0.2 and there will have to be an update to include his new fully stable 5.0.2+1.5 = Hr6.0
Click to expand...
Click to collapse
I haven't used the 5.0.2H build yet! I understand that it has an enhanced lock screen but I don't know what is on it.
Any screen shots welcome!
As soon as Haykuro has the new build, I'll post info.
Thanks
arent there themes available for jf ADP1.5??
or are u tlking bout just a custom theme for that rom?
Dude's Cupcake supports A2SD.
Greetings XDA folks! Brian R, Swype's Community Relations Specialist here with a request for help in tracking down a potential issue that's been reported to us by several users.
We're getting reports from various sources that prediction accuracy has severely decreased after recent over-the-air updates that include a new version of Swype. We believe this is related to old user data being improperly updated for new versions of Swype.
To help us identify and correct this issue, we're looking for a few helpful users to provide us with some data off of their phones.
Am I qualified to help?
We want you're help if you meet the following criteria:
Your phone is STOCK (rooted is OK, but you must be running a STOCK ROM)
Your device comes with Swype pre-installed by default (I.E. NO BETA USERS)
You have recently (within the past 60 days) received an over-the-air upgrade that included a new version of Swype. (for example, Samsung Captivate users)
You use Swype as your primary input method. That means using it daily, for weeks at a time, to build up a long-term usage profile in your userdata
What are you looking for?
Swype is looking for ANY of the following:
The version number of Swype that was installed PRIOR to the OTA update
The version number of Swype that was installed AFTER the OTA update
A zipped copy of the /data/data/com.swype.android.inputmethod directory from BEFORE you received the OTA update (this one's a long shot, but it's worth asking. Perhaps someone has an old nandroid backup that has this?)
A zipped copy of the /data/data/com.swype.android.inputmethod directory from AFTER you received the OTA update. NOTE: You MUST NOT have used the "CLEAR DATA" option for Swype since the update! If you have, the contents of your data directory will not be helpful to us.
In the interest of full disclosure, we are obligated to make you aware that the contents of your /data/data/com.swype.android.inputmethod directory includes your USER DICTIONARY which may have passwords or other sensitive information in it. We give you our GUARANTEE that we will not abuse this information, but if this makes you in any way uncomfortable, please DO NOT send us your info.
In return for your help, we're offering the first 5 users to send us their data directories a free Swype t-shirt (pending confirmation that your data dir fits the criteria above). We know it's not much, but it's what we've got handy
If you are able to provide any of the above information, please either upload the files as an attachment in a reply to this thread or send an email to brian[dot]resnik[at]swypeinc[dot]com
Thank you in advance for any help the Android community is able to provide! We'd love to track this issue down and make sure it doesn't continue to effect users in the future!
P.S. In case you're wondering why we are requesting version information as well: We provide constantly updated download links to our OEM partners so they can access the latest compatible build any time they want. When they choose to download their version of Swype, and which precise version of Swype makes it onto each device with each OTA is often times not up to us, but up to the manufacturer/carrier.
Thanks again! Cheers!
I had to uninstall Swype to be able to update it (remove, then run the new installer, which installs it "fresh"), so I don't think my data directory would be useful. However, obviously, that is a problem that I had with the update.
On a side note, one issue which is driving me nuts with the new update is that words with apostrophes are difficult to use now. Words like "you're" and "don't" especially. Before, if I swyped "youre" it would add the apostrophe. Now it won't. I have added it to the custom dictionary, (at least I think, I don't know if it is built in) but no matter what, to get you're or don't, I have to actually include the apostrophe in my swipe, like y-o-u-'-r-e.
I will try to add a list of words that work (so I presume they are built in) and ones that don't. Here it is for now:
Work
--------
wasn't
didn't
won't
can't
DON'T Work
-----------
you're
don't
they're
Thanks for a great app though! Don't want you to get the wrong impression, I am very thankful to have swype!
First like to thank "mf2112" for setting this up within the XDA Community.
Keep in mind this is a work in progress WIP. His original thread with lots of great Info is located in the General Section of XDA.
Due to the XDA higher ups we have been asked to change/mod/take away the original idea of putting the new users guide in our individual sections.
So I am setup this up for the Infuse only Guide to help all and any find their way around here. Since I am better with acronyms (wonder why) I have Titled it the:
{INSUT} Infuse New & Seasoned Users Thread (WIP).
I say the New for that reason for the New Users or the Seasoned because we tend to forget; those that been around for a while and those that have just been around (like me), so no harm or disrespect is meant to any and all. Thank You.
Any of the Jedi Masters see something that requires attention or correction in this, please PM or post letting me know, and thank you all that can or have time to pass this info along. Also if you want me to add to this, again just holler.
This thread is intended to be a starting point for noobs/new users to help them, in starting out on XDA and have a good experience and become good Infuse XDA members. And here the new addition to the XDA video for the new guys. XDA YouTube vid
Good Reading for the New Member to the Infuse XDA Community. Then we say read it again and yes re-read, not to say your incapable of reading or understanding....just helps you from soft bricking your investment...your phone.:
[GUIDE] How to be a New User (and not a noob)
[REF] Super Infuse Noobie Question Thread. Lots of questions answered
Welcome to the XDA-Developers Wiki
Android (operating system)
ROM-VS-Kernel
Ok, some fast links/info due to soft bricking or want to know where to find the Custom ROMs or how to everything for their Infuse.
This page has everything and anything you might need and don't need for your Infuse:
[REF] {ISET}: Infuse 4G Super Everything Thread {2nd Edition}
The Highly sought after, for that (taken from qkster op) "Oh crap! I just #@#% in my pants! I bricked my phone. OMG!!! I'm stuck on SAMSUNG logo! I'm boot looping! I lost recovery! Help me!!!"
[HEIMDALL][FIRMWARE][ROM][KERNEL] UCKE3; UCLB3 ROOTED; FROYO; ENTROPY's; JT's Last Updated: June 03, 2012
Heimdall One-Click Back To Stock UCLB3 + Easy Clockwork Recovery Mod Install (FOR AT&T USERS) Last Updated: June 03, 2012
[ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included
[ODIN][KERNEL] Odin Kernel and Recovery Repository - Infuse 4G
[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root added - Infuse 4G Last Updated: April 25, 2012
[Guide] [UXKG3] Complete Stock (FOR ROGERS USERS)
And if you wanna flash some custom ROMs to your Infuse, you will find them here, and yes we have AOKP/ICS/CM9 ROMs and the ever so favor Gingerbread Greatness but you should take another read here: [REF] [HOW TO] [ROM Installation] Where to start?
[REF] {ISET}: Infuse 4G Super Everything Thread {3rd Ed} Updated Weekly.
Now some more basic info again, very good reading:
A message from your Moderator
The Rules
Like anything in life, there are rules here. There are also moderators (mods) who enforce the rules when necessary.
Here is the short version. Please:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the longer version. XDA Rules
Searching
When you have a question you don't know the answer to, don't post a new thread when you could post a question in a relevant open thread, and don't post a question when a few minutes reading and searching will not only give you an answer, but a feeling of accomplishment that you were able to find it yourself, and the confidence to remember and repeat the answer with the link to the thread or post with that answer when you see someone else post that question.
Consider the question you are going to post, pick out the keywords and type them into the search box. Try a few different searches with slightly different words.
New Members Guide-Get the most out of XDA!!
Search guide video
If you aren't sure what a term or acronym means, check this Excellent term definition Glossary by benjamingwynn.
Acronyms
Good to know Definitions:
Glossary
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
Giving Thanks
Giving thanks is important. It lets people know that their work or answer is appreciated. It is a faster method of feedback than posting a reply like "Thanks for your answer!" You must have one post to give thanks, so here is a good place you can do that without running afoul of the mods for posting no content posts.
The "Say Hi" thread.
You get 8 thanks per day, and they renew after 24 hours or so. Each thanks is independent of the others, so if you give someone a thanks at 3, and then another at 4, those will renew at 3 and 4 the next day. If you run out of thanks, then bookmark that page or open it in a new tab and give thanks later when you have one available.
If you use them all every day you are doing it correctly.
Some member titles you will see around the threads.
There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase.
Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods.
Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing.
Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc.
Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community.
Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly.
Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace.
Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole.
At the top is Mike Channon, who is overall Forum Administrator.
Other titles you may come across:
Moderator Committee - sits on the Mod Committee
Developer Committee - as above, but for Developer Committee
XDA Newswriter - publishes articles for the Portal (front page)
Retired xxxx - have since officially 'left' their XDA position
Posting
Posting is something you may do a lot of here, but it is always important to remember to make your posts good ones. Don't post just to drive up your count, there is no special reward for the poster with the highest total and you won't catch the long timers here anyways.
You will find that there are some restrictions on your posting ability when you first start here. For starters, for your first 5 posts, there is a prompt and a time limit in between posts. While this may seem burdensome, it does an excellent job of keeping spammers from posting garbage throughout every thread. There is a 2 minute limit between posting and editing your posts. This stops at 30 posts when you go from Junior Member to Member.
Rate the ROM
"Rate the dev's thread with 5 stars using the rate drop-down button at the top of every page of the thread." If your found the ROM or MOD/TWEAK useful, then be truthful rate it there Rate drop down menu that have the star rating, along with the thanks you give the individuals that provided you with help or the DD (daily Driver ROM) you are using, or if you just test a ROM slap the rating.
Donations
Making a donation is neither expected or required,but always gratefully received and appreciated.
There are "Donate to me" icons above people's avatar,or in their signatures.
You can also donate to XDA by clicking HERE.
When you donate 10 EUROS to XDA,you get rewarded with a STAR
,which is displayed a little below your avatar. If you buy 10 STARS ,you will be rewarded with a
.
Originally Posted by samizad
The first PDAs (Personal Digital Assistants) originally did not have any radio hardware. Soon they had bluetooth and infra-red connectivity but they did not evolve into "smartphones" until they got given radio for telephone and 2G data modem. So, O2, the British network provider (now part of Spain's Telefonica) contracted HTC to build such a device and so released the XDA (i.e. a PDA with the "X Factor" - telephony and 2G data hardware); hence the XDA was born in 2003.
I didn't get the XDA because it had a great big antenna sticking out of the top. I waited and got the O2 XDAII (aka HTC Himalaya) in 2003 http://www.gsmarena.com/o2_xda_ii-697.php.
There's a lot of love on these forums for HTC because they were the original pioneers of the smartphone.
Remember, always be respectful of other members here and considerate. Most people here are doing this for nothing more than the feeling of helping people as we have been helped by other people previously, and sometimes the occasional press of the thanks button. We aren't making money here and this isn't a job, so please don't tell people what to do or demand things of people such as mods or custom ROM configs to suit you these ROMs/Themes/Mods belong to the guys that make them, we are just lucky to have them share them with us....
Stickied.
Found very interesting
samizad said:
The first PDAs (Personal Digital Assistants) originally did not have any radio hardware. Soon they had bluetooth and infra-red connectivity but they did not evolve into "smartphones" until they got given radio for telephone and 2G data modem. So, O2, the British network provider (now part of Spain's Telefonica) contracted HTC to build such a device and so released the XDA (i.e. a PDA with the "X Factor" - telephony and 2G data hardware); hence the XDA was born in 2003.
I didn't get the XDA because it had a great big antenna sticking out of the top. I waited and got the O2 XDAII (aka HTC Himalaya) in 2003 http://www.gsmarena.com/o2_xda_ii-697.php.
There's a lot of love on these forums for HTC because they were the original pioneers of the smartphone.
Click to expand...
Click to collapse
Back to work from holidays, i will release my ROM today based on ThunderSnap V2.2 by Eklovya Dutta
Changes so far:
1. Reduced every possible file causing high RAM consumption.
2. Message force closed fixed.
3. No Power off issue fixed - partially
4. NFC for supported devices
5. Front camera - partially, Skype working yeahhh
6. 3D camera - partially, upside down effect
and many more
The rom will be free and without donation [email protected]
FOLLOW THE VERY EASY STEPS TO FLASH :
1. Download the zip from the links given below.
2. Copy to the INTERNAL SD CARD
3. Boot into CWM RECOVERY using 3D key volume-down key and power key.
4. Wipe Data and Factory Reset
5. Install Zip from SDCARD.
6. Reboot
LINKS : <MODERATOR EDITED - LINK REMOVED>
Enjoy, updates will be provided monthly
FAKE
ITS THUNDERSNAP V2.1
ONLY NAME CHANGED.
AND IT HAS SAME BUG AS IN THUNDERSNAP V 2.1
This thread is going to be closed
Sent from my LG-P725 using xda app-developers app
Eklovya i read your private msg and i am replying you public. So you asking..
May i know your name??
And may i know why you are releasing this???.
Where did you got v2.2??
I don't remember you.
I am releasing the rom free from donation stuff to people who love the LG 3D MAX and LG dissapointed them.
People who willing to help to fix the remaining bugs are now able to do it.
XDA community is here to help to make a step forward.
I will give you proper credits or i will remove specific stuff of your work if you want. As you can see i am not promoting your kernel.
I got the rom from you, you released today, at the end of the month
ROM WILL UPLOADED EARLIER, link will provided in 1 hour, uploading right now...
URBANIUS123 said:
Eklovya i read your private msg and i am replying you public. So you asking..
May i know your name??
And may i know why you are releasing this???.
Where did you got v2.2??
I don't remember you.
I am releasing the rom free from donation stuff to people who love the LG 3D MAX and LG dissapointed them.
People who willing to help to fix the remaining bugs are now able to do it.
XDA community is here to help to make a step forward.
I will give you proper credits or i will remove specific stuff of your work if you want. As you can see i am not promoting your kernel.
I got the rom from you, you released today, at the end of the month
ROM WILL UPLOADED EARLIER, link will provided in 1 hour, uploading right now...
Click to expand...
Click to collapse
I think you do not read my ics thread that you are not allowed to use my work without my permission.
you didn't asked permission to use it.
and i am not providing you that also.
so its better you remove it.
and by the way
If network is working it means kernel is compiled by me.
because stock kernel doesn't have network working and it was also covered by secure boot.
so you are using my kernel and system.
there is no change in that
only you released my full rom under your name without any changes.
RULE 12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.
In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Thread Closed.
Hi everyone,
I have a RN5 global whyred waiting to have it's bootloader unlocked in a week and I am trying to collect as much information as I can about what would be the best set up once I unlock. But this has been a difficult process, since the information is all over the place and hard to keep up with. The known bugs list of most roms are not always updated, and sometimes a bug is mentioned in a thread, then not mentioned again for several releases, so it is hard to know if said bug has been fixed in the latest update. Camera mod info is also scattered in various threads. So I am asking for some help in collecting that sort of information. While I would like to collect this information for myself I hope it would be helpful for others who are looking for similar information, since my needs from a phone are most likely the needs of most people. If I have time I may even keep the second post updated with the latest info for a quick look for people who don't want to read the whole thread, though I make no promises about that.
In any case, these are my needs, and I would imagine, the needs of most people:
- calling
- sms
- data
- mms (on the Sim not active for data)
- Bluetooth calling and music
- WiFi
- gps
- reliable camera
- reliable finger print sensor
- root
- decent battery life
- no show stopping bugs (like ringtone or notifications going missing, alarm not sounding, random reboots, etc.)
I realize there is no such thing as software without bugs, but I think the above list is fair to expect from a phone.
If you could please reply to this thread with your current setup or a setup you recommend for the above functionality with the following information it would be appreciated:
- model (pro, China, global)
- Rom (build date)
- kernel (version or build date)
- gapps version
- recovery (version)
- root method
- gcam version
- any camera related mods, and method of flashing
- any other mods
- followed by any known issues with your set up, especially concerning any of the core functions listed above (e.g. I have read certain ROMs have laggy gameplay, which for me is not an issue as I don't game, but if you know your setup has such an issue, even if it's not important for you, please mention it.)
I hope this doesn't turn into another, "which is the best Rom" thread but provides more tangible information. In that light, please refrain from posting short posts like "x rom is the best."
I may adjust this OP if I see that more info is needed in each post, but I think that should suffice for the moment. Hopefully a collection of such info might mean that people won't have to flash and test every custom Rom in the dev section before settling on one.
Thanks in advance everyone.
[reserved]