Related
First of All, I'd like to say a big thanks to the contributors of what your about to get into.
Thanks to Kastro,
Kastro is a developer on this project and did ALOT, and I mean ALOT, of work with this script. He also cross compiled zip, which is the core this project(Originally I had the id to use aapt to do this but we couldnt get it to run on the phone), to work on our phones. So hats off to him.
Thanks to Riku,
Riku has been a big help being our guinea pig and script optimizer. Riku has tested and wiped and flashed and tested things over and over again. He also helped keep the script pretty and optimized.
Thanks to Prash,
Thanks Prash for giving us a theme to work with, he was on board from the start.
Thanks to Ted and Manup,
This guys also loaned their work to us so we could provide examples. We appreciate your talents and skills.
Now, to the Good stuff.
This is an ALPHA release. This means that there will be bugs. We expect there to be bugs....dont use this thinking that there won't be!
MAKE SURE YOU DO A NANDROID BACKUP EVERYTIME YOU FLASH!!!!
And the fun part...
Thanks to Cyanogen for this...
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the current economic crisis. Please do some
* research if you have any concerns about features included in this MOD
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you.
*/
This thread is for a project we have been working on to allow themers and end users a better way to theme our phones, any android phone btw. This method will not only allow for end users to apply updates without having to go into recovery mode, and most of the time without rebooting, but will also allow themers to start making battery packs, icon packs, lockscreen packs, status bar packs, etc. all without disrupting anything but the images and files they want to update.
Along with this project though comes with a few conditions.
1) A new way to do theme update files.
2) new rules concerning these new theme files.
3) almost limitless possibilites
The default Directory for these themes will be stored on the end users SDCARD in the directory AndroidThemes. (For now there is no way to change this, but there will be in the future)
The contents of MetaMorph.zip go into /system/bin. (For now there is no way to change this, but there may be in the future)
Once you put the content there, please cd into /system/bin and chmod mm.sh and zip to 0755, like this:
cd system/bin
su
chmod 0755 mm.sh
chmod 0755 /system/bin/zip
After you've done and put a theme in your AndroidThemes folder, you are ready to go!
Now open terminal and type:
mm.sh
to get started.
The rest is pretty self explanatory.
To theme DEVS( and users), I have videos uploaded which will go over the specifics of the new theme.zip, please watch this! Very VERY important, so important, I wont tell you how to make one here because you need to watch the videos!
First Video: http://www.youtube.com/watch?v=fX2xbY4nSd4
Second Video: http://www.youtube.com/watch?v=Dvps2501CAg
Third Video: http://www.youtube.com/watch?v=3iu5AHF-Zew
Fourth Video: http://www.youtube.com/watch?v=sgVL-0E8Rh8
Here are the files:
MetaMorph: www.RelentlessAddictions.com/android/downloads/MetaMorph.zip
Battery Pack(Needs Stericson Lockscreen): www.RelentlessAddictions.com/android/downloads/Batteries.zip
Lockscreen Pack(needs Stericson Lockscreen): www.RelentlessAddictions.com/android/downloads/Manup-Stericson-Lockscreen.zip
Full theme (Prashs theme, AlienAqua): www.RelentlessAddictions.com/android/downloads/Prash-theme.zip
Any questions, problems? Ask below, let us know!
Stericson
Update: Added some more error detection for the theme control file. Also moved the location where we put the script. Move the script and zip file to /system/bin. chmod 0755 both the mm.sh and .zip. Now you can run it anywhere just by typing mm.sh -i.
Continued Info on Metamorph
#OTHER INFORMATION, PM ME TO ADD REFERENCE/LINKS
# REGARDING NON-apps2sd USERS:
there isn't anything except two files going to be in that directory, so you should still be ok, make sure you mount your FS read-write before putting the files on your system partition:
Code:
adb remount
adb push file-to-push.ext /system/sd/theming/file-to-push.ext
also, if magic users have troubles with the default terminal app w/ the on screen keybaords you guys have on your roms, try out Better Terminal, the free version, from the Android Market
THIS IS A SCRIPT MADE FOR EITHER ADB OR USE ON THE ANDROID DEVICE ITSELF!
which means yes, you can use terminal, or yes, you can use the android debug bridge!
This script in the end will be designed to be compatible with ANY rom, we need you to test it, (we're talking to you, dev's
Theme-Devs! Join us on IRC!
irc.freenode.net/#android-mods
New Zipall script, by Kastro & Riku! working on windows port in collab with coolboh3000! stay tuned! http://forum.xda-developers.com/showpost.php?p=4795886&postcount=51
Waiting Patiently for the VID!!!
one question, for users with no apps2sd e.g. no system/sd directory needed such as those on the magics, how would it work?
regarding Non-Apps2sd
NguyenHuu said:
one question, for users with no apps2sd e.g. no system/sd directory needed such as those on the magics, how would it work?
Click to expand...
Click to collapse
this is not quite ready I think for theming third party apps, though I'm sure its entirely doable, remember its ALPHA!
also, the only things in /system/sd/theming are two files,
so you shouldn't have to worry about it, though again, its not quite ready for changing, I would suggest creating that folder
For now it wont, but as I said, in the future we will have this fixed. We allready though of this. Magics cant be rooted and use apps 2 sd?
Or are you referring to no keyboard?
Does the on-screen keyboard work in terminal?
Also...you never know...hmmm there may even be some wild and crazy app made to use this....neverrrr knowwww
Stericson
Stericson said:
For now it wont, but as I said, in the future we will have this fixed. We allready though of this. Magics cant be rooted and use apps 2 sd?
Or are you referring to no keyboard?
Does the on-screen keyboard work in terminal?
Also...you never know...hmmm there may even be some wild and crazy app made to use this....neverrrr knowwww
Stericson
Click to expand...
Click to collapse
terminal will work, but its buggy, Try the free version of Better Keyboard, on the market
Riku said my posts are boring....so I prettied it up!
any particular rom? or do we just need the right theme for the right rom
First video is up...
what do we use this on top of?
phantom574 said:
any particular rom? or do we just need the right theme for the right rom
Click to expand...
Click to collapse
pretty much this will work with any rom, however, I personally would recommend "right theme, for the right rom" as a few roms (like blur, hero, etc) have a different image setup, ALTHOUGH. this will most likely work, but thats why its an alpha release, so that we can test this fact. PLEASE nandroid before use
Can't wait for the videos to see what new toys we have to play with
rikupw said:
pretty much this will work with any rom, however, I personally would recommend "right theme, for the right rom" as a few roms (like blur, hero, etc) have a different image setup, ALTHOUGH. this will most likely work, but thats why its an alpha release, so that we can test this fact. PLEASE nandroid before use
Click to expand...
Click to collapse
1 flash theme for rom
2 metamorph
3 customize?
phantom574 said:
1 flash theme for rom
2 metamorph
3 customize?
Click to expand...
Click to collapse
at this point, I would wait until all the videos are up, it's highly recommended that you read watch the videos. there are 4 of them, 8 minutes each, if you don't want to watch them, wait a few days for other people to get the hang of things, bum off of their work lol
rikupw said:
at this point, I would wait until all the videos are up, it's highly recommended that you read watch the videos. there are 4 of them, 8 minutes each, if you don't want to watch them, wait a few days for other people to get the hang of things, bum off of their work lol
Click to expand...
Click to collapse
will wait for the vids thanks for your help!!
Brilliant idea! Had a feeling it'd be something along these lines. Bye bye, update.zips then!
/Mats
update.zips
ZilverZurfarn said:
Brilliant idea! Had a feeling it'd be something along these lines. Bye bye, update.zips then!
/Mats
Click to expand...
Click to collapse
i think that they will be still be of use, first flash teh update.zip, perhaps later supply packs, option colors, etc etc? that will be most useful I believe to end-users
rikupw said:
i think that they will be still be of use, first flash teh update.zip, perhaps later supply packs, option colors, etc etc? that will be most useful I believe to end-users
Click to expand...
Click to collapse
This could be my end all solution to maintaining all the NFL themes, and make it way easier to manage the NBA and NHL.
Following this, I could essentially issue 1 update.zip for a color set (says like Blue/Red for Giants, Patriots, Texans, Rangers, Pistons etc..) and then use the packs to have all the icons, clocks and etc. which would save me from flashing things over and over to test.
w00t
jairomeo said:
This could be my end all solution to maintaining all the NFL themes, and make it way easier to manage the NBA and NHL.
Following this, I could essentially issue 1 update.zip for a color set (says like Blue/Red for Giants, Patriots, Texans, Rangers, Pistons etc..) and then use the packs to have all the icons, clocks and etc. which would save me from flashing things over and over to test.
Click to expand...
Click to collapse
BINGO. you got it. sort of make sure you watch the videos!
Tested and working, flawlessly. Excellent work guys, kudos!
AGPS Patch Incredible S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
veitograf said:
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
Click to expand...
Click to collapse
Did you try v1.3? It's at the top of the post under "Downloads".
crypted said:
Did you try v1.3? It's at the top of the post under "Downloads".
Click to expand...
Click to collapse
1.3 works like a charm
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
baste07 said:
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
Click to expand...
Click to collapse
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
crypted said:
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
Click to expand...
Click to collapse
thanks i'll try this out!
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
itandy said:
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
Click to expand...
Click to collapse
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
crypted said:
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
Click to expand...
Click to collapse
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
itandy said:
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
crypted said:
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
Click to expand...
Click to collapse
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
crypted said:
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
Click to expand...
Click to collapse
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
-------
Also,
In preparing for the next iteration of the GPS patch, I'm trying to get a better grasp of the suplrootcert's on various devices. So far I have Verisign and TMobile. If anyone would be willing to check their phone and let me know if they have a different one (via private message here on xda)that would be great!
You can find "suplrootcert" as a file in /etc/ just like where the gps.conf is located.
To see which you have, open it up as a text document. It will look like jibberish. But, the top portion will say a company name within the jibberish. If you don't see Verisign or Tmobile, I would like to get ahold of the one on your device!!!
crypted said:
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
Click to expand...
Click to collapse
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Sent from my HTC Incredible S using Tapatalk
itandy said:
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Click to expand...
Click to collapse
Did it work fine before the patch, though? Can you get a screenshot of GPS Status after running for about 2 minutes?
I'm sorry I can't quickly resolve your phones issue. I'm curious about its hardware and whether it was greatly stable beforehand, or what...
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
BWA80 said:
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
Click to expand...
Click to collapse
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
crypted said:
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
Click to expand...
Click to collapse
HEHEHE, good one!
Actually anything above 0 celsius is summer for us, how sad is that..
No case, my baby is totally naked. wifi not enabled. I´ll do the GPS status sit and run tomorrow, too dark now and the wolves are howling.
Will report back.
Thanks!!
AGPS PATCH
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
Unofficial CyanogenMod 10.1
Rom: Unofficial CyanogenMod 10.1
Android version: 4.2.2
Status: Alpha (means not ready as beta or even stable release!)
What doesn't work:
Sound partially, only calls not working right
Wifi
GPS
Bluetooth
Brightness control
Airplane mode
Camera, did work though in earlier version
Disclaimer
I am not responsible for bricked devices, broken hearts, thermonuclear war or you getting fired because the alarm app failed. It's up to you, not to me.
Click to expand...
Click to collapse
Downloads:
Google Drive CM10.1
Mirror, hosted by Burn02
The version differences:
Code:
24/2/14
[LIST]
[*] Using new audio hall
[*] Microphone works now, call still doesn't
10/2/14
[LIST]
[*] Initial audio support
[*] Fixed Wifi symlink for MAC-adres
[*] ICS_AUDIO_BLOB disabled
[/LIST]
01/12/13
[LIST]
[*] ICS_AUDIO_BLOB enabled
[*] Using original audio blobs
[/LIST]
14/11/13
[LIST]
[*] Both Internal storage and external storage working
[*] Build modified init from source
[*] Dalvik with x86 houdini support
[*] More modules build from source
[/LIST]
6/11/13
[LIST]
[*] Only internal storage working
[*] Libc with x86 wrappers support
[*] Pixelflinger/charger with x86 encoder support
[*] Ramdisk changes
[*] Android Build fixes for x86
[*] Add intel specific codes
[/LIST]
Workarounds:
The Rom can bootloop when installed in TWRP. If so use CWM instead for a while till TWRP is working correctly.
Want to help?
This Rom is made by many people that contribute to it, if it is in code, new information or just bug logs. Everybody can help. Make a 'Logcat' about the problems u encounter and post them here. Give a brief explanation of what u did and wanted to archive (we will try our best to get them sorted, eventually) or contribute with code into my github at the moment.
Click to expand...
Click to collapse
Source:
https://www.github.com/HazouPH
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Hazou said:
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Click to expand...
Click to collapse
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
GalaxyUser said:
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
Click to expand...
Click to collapse
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Hazou said:
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Click to expand...
Click to collapse
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Hazou said:
Unofficial CyanogenMod 10.1
Click to expand...
Click to collapse
Thanks!.. is a great news...
antkalaitzakis96 said:
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Click to expand...
Click to collapse
Y' i know. He asked permission tot post it
Wifi working isn't a very big problem. I want to first hopefully fix the sound, or hope that some ideas might help.
Sent from my GT-P5110 using XDA Premium HD app
Hey can somebody post some screenshots ??
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
great .. thanks @Hazou
Enviado desde mi Moto usando Tapatalk
ICuaI said:
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
Click to expand...
Click to collapse
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
hotpokets said:
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
Click to expand...
Click to collapse
You don't need a screenshot, if this doesn't work yet. This is a thread to make the rom functional. Then it can be released to the regular users like us, who just want to use it regardless of the making process
You can go in every CM10.1-thread in this forum. I am sure that you will find enough screenshots of CM10.1. The rom for our xt890 doesn't have another look.
Or try this alpha-build on your own phone
And now for me I'll stop being of topic
Sorry for that to all the devs
GalaxyUser said:
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
Click to expand...
Click to collapse
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Hazou said:
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Click to expand...
Click to collapse
Will this ROM work on Lenovo K900?
charming.arpit said:
Will this ROM work on Lenovo K900?
Click to expand...
Click to collapse
Not out of the box, no.
Sent from my GT-P5110 using XDA Premium HD app
intel released source code for android 4.4
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Did you guys saw this?
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
drunk_ryder24 said:
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Click to expand...
Click to collapse
hey this is just
Android* 4.4 (KitKat) x86 Emulator System Image
this is for developers who running a pc (x86) and want to emulate the newest android.
this has nothing to do with our fone.
i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin
regard
Hi,
I don't want to waste your time, but I think this is a proper time to ask a question.
This tablet(s) are 9 months on the market. Tons of ROMs came to see the daylight, every less important variant of this device got AOSP or CM builds for them, and that's awesome! And everybody enjoy their cool tablets, except ... the owners of the best and most important variant - 10.5 LTE. And there is even official T705 CM12 build! Why not for T805?
I feel sorry I don't have any knowledge in programming or porting, neither I have any pleasure in doing it. But there are a lot of great and talented chiefs who love to port and build good ROMs who make a good TW stuff, and a lot of guys who make AOSP for ... WiFi version. Noone is interested in LTE model, and there is a lot of T805 users out there waiting for AOSP release and asking on every Tx00 threads for builds for their devices.
I have a lot of respect for hard work everyone do here, and we all understand everyone of you - talented chiefs here - have limited time and possibilities. I am personally very grateful for your effort. And don't get my post wrong. All it is about is to ask: Why? Why there are CMs, AOSPs for T800, which I think is not so much different from LTE model,and there is NOTHING AOSP for T805....
I think there will be more than only me to greatly ask for attention from great developers of xda, to ask them for xda miracle for us. Please, make something AOSP for T805... please please please! Let us see this:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
We all would be so grateful for your help, to let us feel the Google Experience..
Thank you!
HUGE UPDATE
It looks like we got it! Finally, good working Lollipop with LTE on our amazing devices. Now the Tab S got a new life, with pure Google Experience! For everyone interested, check out our great developer who made a HUGE effort to make this happen (big cudos to AndyT12) and his website with updates and downloads:
http://goo.gl/ODCQ94
AAAND HERE WE GO!
Another AOSP from cool developer deadman96385:
http://forum.xda-developers.com/gal...m-liquidsmooth-v4-1-lollipop-sm-t700-t3092696
Unfortunately LTE still does not work here but they have just the initial build se let's be patient! Thank you!
UPDATE ON NEXT GREAT BUILDS
We are happy to see yet another great build with working LTE! This time it's amazing work from developer Nexorr who managed available sources from NVertigo and AndyT to build this ROM! Check the links below to download the stuff:
http://forum.xda-developers.com/showpost.php?p=61934130&postcount=78
http://forum.xda-developers.com/showpost.php?p=61940915&postcount=84
Thank you Nexorr for your huge effort!
Yes.. I'm interested this project... Available for Betatester on my Sm-t805.... Happy to see Android v5.1.1 full working on this device
T805 is alot different than T800. Nvertigo explained why a while back. One simply cannot build without having the device. In my guessing, more people probably have wifi ones vs lte models in which most devs have Idk. Nvertigo made a thread also on how to build/port. http://forum.xda-developers.com/showthread.php?t=3031278
It requires a ton of work so... yeah.
So there is no hope, I guess...
Btw I thought there are much more interested people in the AOSP. I was wrong, it seems. 248 visitors came across this thread without even a word, so let's say it: buy N9 or eat TW rubbish.
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Bring him in.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
nvertigo67 said:
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
Click to expand...
Click to collapse
And the questions from the first post still apply.
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Hi Andrew! It is so great to hear! This is so cool! Thanks for the information. Are you willing to make xda thread also? Thanks!
PS. Is this build working or it is relatively experimental one? I am worried to lose my data or backups etc..
Hi, i have problems with download, it is so slow and then breaks the download fail. Any oher options to download ?
It was so great CM12.1 for the tab T805 LTE...... and great Job Thanks
One question, must i use your twrp or is it ok with the Original twrp i have 5.0.2 on my tab Iron Rom lollipop
Same here, download fail. But anyway, thank you for your effort! Would really like to try it.
Btw backing up efs, in twrp?
I could use a quick HOW-TO, @andyt12:
with both your provided Odin3.07, and my own Odin3.10, I could not graphically locate either your .md5sum file, nor the .zip ROM archive. At least I *could* enter the file/archive names at the Odin text-entry-box...
but that produced another pair of issues:
-although the suffix ".md5sum" isn't recognized, direct-entry of the filename indicates "binary corrupted" or similar
-entering the .zip archive directly results in Odin message-box saying "success 0/failed 1"
I am really, really excited at the prospect of CM12.1 for my tablet (matching my phone). But I seem to be sort of stuck at some basic point. BTW, I already had TWRP-2.8.6.0 installed on my T805, so I left that and did not try your provided version...
Thank-you for you efforts! I deeply appreciate the work you've put into this!
GordP
is this for t-805y or just t-805 ? since u seem from OZ the version i have is from telstra.
This is awesome. I'm so grateful someone is making a CM12 for t805. Will be trying it soon. Do we have a list of known issues/things that still need work?
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Please put it in Xda it will be helpful to test and to make solutions to help you in this project
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
DarkDvr said:
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
Click to expand...
Click to collapse
There is any issue or bugs in this rom ?
Cuz there is no info about rom
So, here's what I did/got:
To repeat dev's words:
Make sure you use EFS backup tools (for example, there's one in Play store) to backup your EFS/IMEI partitions somewhere in a safe place (not just on a tablet).
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Root, ADB work
USB works - able to see both device storage & SDcard
CPU: usage seems normal, with cores ranging from 200MHz to 1.9GHz. Although I don't see any cores disabling during no load. Not sure if this is normal.
Performance: subjective. To me, device seems a hell of a lot snappier. Transitions, scrolling, app switching - noticeably smoother than on Lollipop TW.
GPU test: tested in a game (hearthstone), performace is the same as on stock ROM, didn't see any difference.
Temperature: max 43C so far, seems the same.
Camera: both front and back cameras work
Battery: device is sleeping fine, no wakelocks. Battery usage completely flattens when it's sleeping, so, in a few days, I'm expecting a good battery life.
Charging: I think it's the same as on stock: around +500mA when device is ON and on a wall charger.
Bug: Samsung's stock docking keyboard: everything works, expect the app switch button.
Bug: In app switcher - there's an error loading the search widget. No big deal, but it's a thing.
Device info screen
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
DarkDvr said:
So, here's what I did/got:
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
Click to expand...
Click to collapse
Thank you for this info
What about battery and temperature of device ?
And if he used default kernel speed for cpu
Sorry for long questions
Finally what about speed and what is better TW or CM12.1 ?
All the answers before my post ? ??