AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
Thank you for this helpful post.
I have tested this extensively for a bit using gps status, and have come up with the following conclusion.
Personally, i live in Sydney, Australia, my optimus one is rooted with cyanogen mod by mik_os and fserves gbs kernel v18b.
For me this patch performed poorly compared to me using the market app Fasterfix, with which u select the region you are in and in sets your gps.conf accordingly( in my case i just deleted this patch after testing, and faster fix wrote a new gps.conf once i selected my region)
I experienced a MUCH better fix time using Fasterfix, then this patch. Where it took 10 secs to lock on using fasterfixs conf file, this patch took minutes. i got more satellites fixes with Faster fix as well, 11 satelites to the 9 i got with this patch.
And yes i let it sit for at least 10 minutes each time to "learn", but after every restart it still took a few minutes to the 10 seconds average from Fasterfix.
This is results for Australia, so this patch may still be more effective in other countries especially North America, where it originally came from.
Hope this review helps other members.
deniso177 said:
Thank you for this helpful post.
I have tested this extensively for a bit using gps status, and have come up with the following conclusion.
Personally, i live in Sydney, Australia, my optimus one is rooted with cyanogen mod by mik_os and fserves gbs kernel v18b.
For me this patch performed poorly compared to me using the market app Fasterfix, with which u select the region you are in and in sets your gps.conf accordingly( in my case i just deleted this patch after testing, and faster fix wrote a new gps.conf once i selected my region)
I experienced a MUCH better fix time using Fasterfix, then this patch. Where it took 10 secs to lock on using fasterfixs conf file, this patch took minutes. i got more satellites fixes with Faster fix as well, 11 satelites to the 9 i got with this patch.
And yes i let it sit for at least 10 minutes each time to "learn", but after every restart it still took a few minutes to the 10 seconds average from Fasterfix.
This is results for Australia, so this patch may still be more effective in other countries especially North America, where it originally came from.
Hope this review helps other members.
Click to expand...
Click to collapse
All Fasterfix would do differently is set it to AU specific timeservers. So, maybe you had some bad luck with a NTP timeserver while testing. I can't solve that (yet).
Beta testers have had great success with this, even the guys using this device. Originally, this device was not on my goal to support list. But, after multiple people reported great things, I added it.
So in conclusion, thank you for the commentary. Just keep in mind the "difference" isn't really one.
EDIT: I've heard numerous reports that the ROM you're using has been screwed up with aGPS support being hard-coded as disabled in compilations lately. That may have some bearing on your results, too. I'm not a user of that ROM nor do I have the phone, so I can't personally attest. But, someone sent me the code snippets that clearly show aGPS disabled.
I dont think it is disabled, as then it would never take 10 seconds to get a lock on, which it does for me currently.
But yes the patch does give me a server connection eventually, but it takes dramatically longer.
I guess your first line is right, use this if you are experiencing issues, other wise no need to fix something that isn't broken.
Also note, after originally installing this Rom, and getting onto fasterfix, it stated that my location was Europe or something, cant remember exactly, but point is it recognised the location, so that would be the problem for most users using my mod, and all they have to do is set it to their own location, which in my case was immediate success and gps fix is great
deniso177 said:
But if it is disabled wouldnt that mean i shouldn't get any reception at all?
But yes the patch does give me a server connection eventually, but it takes dramatically longer.
I guess your first line is right, use this if you are experiencing issues, other wise no need to fix something that isn't broken.
Also note, after originally installing this Rom, and getting onto fasterfix, it stated that my location was Europe or something, cant remember exactly, but point is it recognised the location, so that would be the problem for most users using my mod, and all they have to do is set it to their own location, which in my case was immediate success and gps fix is great
Click to expand...
Click to collapse
I can't please everyone...
And I'm not following your commentary. There is literally no way this patch would cause your location to go from one end of the earth to the other via GPS. All it does is switch on some variables that your hardware is capable of for processing your location quicker. And, it adds some assistance data to be downloaded which is used in conjunction with UTC time. The NTP timeservers rarely matter because the binary file for that data is based on a 24 hour clock and updates every hour to be 23.5 to 24 hours in advance to allow up to that much time without a data connection for quick GPS satellite data parsing.
Sorry what i was meant to say is that, i dont think agps is disabled in my rom, as then i would never get 10 seconds lock on as i currently do. But yes i guess i dont understand how this patch exactly works, as there isnt that much information what hardware properties it takes advantage over the default settings.
I was just trying to display my Particular results, for my particular rom in Australia, so i cant say that this patch would not be better on other scenarios or not.
Will be good to see more testers on here say there results from all over the world using a bunch of roms, including the stocks.
regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?
sweetnsour said:
regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?
Click to expand...
Click to collapse
The gps.conf download is what it says, it only has that file, the other downloads, have an extra file called SuplRootCert, which i am not sure what it does
deniso177 said:
The gps.conf download is what it says, it only has that file, the other downloads, have an extra file called SuplRootCert, which i am not sure what it does
Click to expand...
Click to collapse
Technically, all should work unless a provider is limiting SUPL use to LAN data and not roaming phones. That wouldn't make sense since they advertise world traveler plans.
I prefer the generic Google build myself even though I use AT&T as it's always been reliable.
sweetnsour said:
regarding the 2.x trunk, how do i know which one best suits my phone?
none of the builds say anything about location, although i am assuming that these builds were made for those in the u.s. as these are u.s. phone carriers.
obviously i should be considering the tmobile build but what makes this build different than the google build and the gps.conf?
Click to expand...
Click to collapse
SUPLROOTCERT is a verified certificate (think of it like https SSL websites). There is one for AT&T and its server, one for T-Mobile and its server, and one for Google and its server. Theoretically, their SUPL servers may deny your phone access for server assisted locating if your cert isn't matching the specifics for their server.
I collected what people were willing to send me and made versions based on that.
I have been using it since a month and must say this is great, works for me
i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?
GonDr said:
i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?
Click to expand...
Click to collapse
you can either:
a) redownload the file and try again
or
b) manually push the files into system/etc
Is it only for north america ? Can i flash it in italy ?
GonDr said:
i can't flash it E:Error or something like that
i using TWRP-ThunderG-v1.0.3.13b recovery and disabled verification
so, any idea ?
Click to expand...
Click to collapse
It is designed to flash using CWR. It will not flash with a number of other Recovery systems out there. That's why there is another method described. You have two other options: copying directly using ES File Explorer or Root Explorer -OR- adb push.
angeloilcampione said:
Is it only for north america ? Can i flash it in italy ?
Click to expand...
Click to collapse
This is worldwide. So should work fine. Lots of Europeans using it.
crypted said:
It is designed to flash using CWR. It will not flash with a number of other Recovery systems out there. That's why there is another method described. You have two other options: copying directly using ES File Explorer or Root Explorer -OR- adb push.
Click to expand...
Click to collapse
The flash zip you provided is corrupted/not working... It wont install neither with CWR nor TWRP nor Amon.... (Error Status (0))
BTW, theres no reason why TWRP would not flash... Just because your flash zip is screwed...
BTW2: http://forum.xda-developers.com/showthread.php?p=18141638#post18141638 , another user that is flashing zip from recovery and doesnt work
excellent crypted but if I download gps data with status gps could be overwritten the file gps.conf ?
+1
angeloilcampione said:
excellent crypted but if I download gps data with status gps could be overwritten the file gps.conf ?
+1
Click to expand...
Click to collapse
Nah. But, I just suggest using that tool to prove this does work. Typically, I only use Google Maps and I like to watch how I don't have a big blue circle around me anymore.
TakamineSubasa said:
The flash zip you provided is corrupted/not working... It wont install neither with CWR nor TWRP nor Amon.... (Error Status (0))
BTW, theres no reason why TWRP would not flash... Just because your flash zip is screwed...
BTW2: http://forum.xda-developers.com/showthread.php?p=18141638#post18141638 , another user that is flashing zip from recovery and doesnt work
Click to expand...
Click to collapse
I also get this error (CWM), and so when I copy the files using File Explorer (rooted) the gpsconf copies fine but it fails when trying to copy SuplRootCert
strange?
digitalface said:
I also get this error (CWM), and so when I copy the files using File Explorer (rooted) the gpsconf copies fine but it fails when trying to copy SuplRootCert
strange?
Click to expand...
Click to collapse
If this is with ES File Explorer, goto settings and enable root and mount system. You can delete the file with Terminal root and then copy a new one over, too.
I'll try to get a new method posted using a script for adb pushing. A beta-tester is assisting in such a method. It'll be a few days, though.
crypted said:
If this is with ES File Explorer, goto settings and enable root and mount system.
Click to expand...
Click to collapse
Yeah that worked, shall test GPS shortly.
Just checking your gpsconf, as I'm UK would it be worth me commenting out the other servers and changing the first to UK?
Before
Code:
NTP_SERVER=1.pool.ntp.org
NTP_SERVER=2.pool.ntp.org
NTP_SERVER=3.pool.ntp.org
NTP_SERVER=0.pool.ntp.org
NTP_SERVER=0.europe.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
Modified
Code:
NTP_SERVER=1.uk.pool.ntp.org
::: I WILL NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE :::
Hi everyone! Today my Galaxy Tab 10.1 (3G) has been updated to Honeycomb 3.2 via Samsung Kies.
During the update, i saved the Kies download folder containing the firmware.
I've uploaded to 4shared on this link:
http://www.4shared.com/file/IvMsjSLY/P7500ZVVKL1_P7500UBKL1_P7500VI.html
- Its about 727MB.
- You need Odim to flash (I cant help you with that).
- Is a Brazilian VIVO 3G version, and "i think" will work on any 3G Galaxy TAB 10.1.
- I've updated this morning so, not tested enough.
- Is more fast than the original 3.1 but, not fast enough We really need ICS.
Great job tonywalker!
Samsung released updates from gt-p7500 but vivo doesn't offer support.
Many people uses task650's roms, and look very awesome, but most of task650 updates and others works only in "gt wifi only". Is there any way to use these roms and apply 3g support on gt-p7500 from vivo?
Probably not. Developers would have to create a ROM specifically for gt-7500.
After a few days of use I can say that I really liked this update to 3.2. The most annoying problem was resolved, and now just the slowness of the tablet bothers me.
I think you should try.
Thanks a lot.
Searching an restock way for a looooong time, thank you.
which problems and apps?
tonywalker said:
After a few days of use I can say that I really liked this update to 3.2. The most annoying problem was resolved, and now just the slowness of the tablet bothers me.
I think you should try.
Click to expand...
Click to collapse
I´d like to know what kind of problem did you find on 3.2 stock? Is it slowest than 3.1? Yesterday i rooted the tablet (3.1 os) and also overclocked, after these mods i realized that honeycomb are more fast and flow now. Honestly i dont want to create new problems that now.
Some apps are very usefull and cant miss on this tablet like:
- Folder Organize (u can use lite version)
- HD Widgets (improve time and weather with a excelent widget)
- Hide bar (the propose is: hide system bar every time you want, but bottom restore didnt work as the program promess)
- wifi ad hoc enabler (this app are really getting me nervous!!! I´m looking for a app that enable ad-hoc network and share files between pc and tablets (option locked by samsung). This is a new app and most os people are leaving messages saying that its perfect. After follow all the instructions i cant share my files.
** I tried to download 3.2 stock but i think that only 4shared users are allowed to download big files. Please, split the rom in two small files and reupload
Denis Costa
Just to confirm, I flash this by putting my tablet into download mode, then selecting PDA in odin and then search for the .tar.md5 file of the ROM right?
Hello Nexus 7 lovers,
As we all know Chrome comes pre-installed for Jellybean instead of the old stock ICS browser (which is a very welcomed addition) on the Nexus 7. Chrome Mobile does not support flash (and it never probably will). Also Adobe has stopped support for any Android version 4.1 and up (regardless of chipset). But lucky for us Tegra 3 has been supported by Adobe before Adobe decided to stop even hardware support.
I don't use flash anymore really, but a lot of people still do. If you want to install flash and have a browser that can use it, follow the instructions below.
As we all know you can side-load the flash APK even though you can't install it straight to from the market.
For the new people to Android who don't know how, here is how to install app if you have the .apk file:
Go to Settings.
Go to Security (under Personal)
Check Unknown Sources (under Device Administration)
Click OK
Now Install Flash 11.1, if you need the APK, you can grab it here:
(mediafire...4940h3ixaabr2gp)
Now install Firefox Beta from the Play Store (or download the APK below).
I'm sure there are other browsers that support flash, I'll be testing out quite a few and I can make a list here.
List of browsers that DO support flash on the Nexus 7:
Firefox Beta
Maxthon Browser
Fennec (Aurora Nightly)
Dolphin HD 8.5.x (8.6+ does not support)
List of browsers that DO NOT support flash on the Nexus 7:
Chrome (The default browser installed)
Opera Mobile
bahaakhaled97 said:
Hello Nexus 7 lovers,
As we all know Chrome comes pre-installed for Jellybean instead of the old stock ICS browser (which is a very welcomed addition) on the Nexus 7. Chrome Mobile does not support flash (and it never probably will). Also Adobe has stopped support for any Android version 4.1 and up (regardless of chipset). But lucky for us Tegra 3 has been supported by Adobe before Adobe decided to stop even hardware support.
I don't use flash anymore really, but a lot of people still do. If you want to install flash and have a browser that can use it, follow the instructions below.
As we all know you can side-load the flash APK even though you can't install it straight to from the market.
For the new people to Android who don't know how, here is how to install app if you have the .apk file:
Go to Settings.
Go to Security (under Personal)
Check Unknown Sources (under Device Administration)
Click OK
Now Install Flash 11.1, if you need the APK, you can grab it here:
(mediafire...4940h3ixaabr2gp)
Now install Firefox Beta from the Play Store (or download the APK below).
I'm sure there are other browsers that support flash, I'll be testing out quite a few and I can make a list here.
List of browsers that DO support flash on the Nexus 7:
Firefox Beta
Maxthon Browser
Fennec (Aurora Nightly)
Dolphin HD 8.5.x (8.6+ does not support)
List of browsers that DO NOT support flash on the Nexus 7:
Chrome (The default browser installed)
Opera Mobile
Click to expand...
Click to collapse
Nice write up, but this is common knowledge and has been repeatedly posted. In addition why is it people post a file share sit instead of the adobe archive is beyond me. Also, please follow the rules, especially the one that says to use the search function before posting.
Sent from my Nexus 7 using xda premium
zPacKRat said:
Nice write up, but this is common knowledge and has been repeatedly posted. In addition why is it people post a file share sit instead of the adobe archive is beyond me. Also, please follow the rules, especially the one that says to use the search function before posting.
Click to expand...
Click to collapse
Considering he's also advertising warez in other threads, perhaps the APK he attempted to link to is "modified". Who knows. I wouldn't use it, that's for sure.
Yeah... I wouldn't trust ANYTHING OP posts. I wouldn't trust any of his links, either.
The "missing" Android Stock Browser, fully supports Flash. I have been using it, without any issues, so far on my Nexus7 3G.
Closed - Already very well covered elsewhere
I have created a modified version of WiFi Tether for Root Users that is available on Google Play Store. I have recompiled it from source and forced device profile to 'passion' so it now works on HTC HD2 out of the box without the need of modifying default settings.
Usage
download attached RAR
enable installation of apps from "Unknown sources" in Settings > Applications
manually install app using file explorer from SD card or push APK to /data/app using ADB
Download
WifiRouter.rar
Source code
Repository is located on GitHub.
Like a strong support TerrificSupport
:good::good::good::good::good::good:
Thank you very much.
It's work very well.
You instal you run and it work with my hd2 and my galaxy tab 10.1 P7500.
No more need setting the app.
Thanks you again
you're welcome
re
hay daekin
i have insert your modded wifi tether in my JB 4.2.2 AOKP/CARBON rom and have test this. your app works well with non problem or mistakes.
great jo my friend.
i have see your github from this app and have see thats you have insert only the passion device? right?
this.device = DEVICE_PASSION; // Overrides: android.os.Build.DEVICE; //NativeTask.getProp("ro.product.device");
the rest is only your sign? right?
many thanks for this great job....
can i work with your wifi tether in my rom´s please ????
pixelfreak
Yes, that is the trick. Also I have altered app name and raised version number so it will never get overriden from Play Store. I left package name the same.
About usin in your ROMs: sure you can use it. I do not prohibit using of my work (like some so-called devs do). I published it to help the community so let it serve you well.
Sent from my HTC One X using Tapatalk 4
Hi, why no mac spoofing ?
Hi Daekin, i tried to use the app on a s3 i9300 with ldroid rom 4.4.4 installed. Profile was set to Galaxy S3 and setup method to auto, but the starting log always say configuring ap and starting ap failed. All other log entrys are successful. Which profile should I use, or where else could be the problem? Hope you're still here and can help.
Thanks
Sent from my GT-I9300 using XDA-Developers mobile app