Related
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.
Several Galaxy Nexus users have indicated this fixes their GPS problems.
So, I'm opening up a tentative support thread. Let me know!
my nexus doesn't have any GPS issues... never heard of this issue ? My GPS locks in under 10 secs anyway... will it improve it Even more?
Sent from my Galaxy Nexus
ceo.mtcl said:
my nexus doesn't have any GPS issues... never heard of this issue ? My GPS locks in under 10 secs anyway... will it improve it Even more?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
you can test and tell me
Sent from my Transformer Prime TF201 using XDA
Flashed 3.1 zip using cwm, went from lock of 20m within 10 secs to lock of 10m within 10 secs on Gnex i9250 on aokp B28!!! Thanks used this for my sgs2 before also.
Sent from my Galaxy Nexus using Tapatalk
Heya crypted, good to see your patch here as well. I saw you on the T-mobile GS2 forums. I'll get my phone on Monday and will gladly test this out.
E:Error in /sdcard/bla bla bla <the zip>
arzbhatia said:
E:Error in /sdcard/bla bla bla <the zip>
Click to expand...
Click to collapse
Use one of the other two methods...
Sent from my Desire HD using XDA
n00b question
sorry i could have read it wrong but...
when using Method 2, is it enough to copy just the gps.conf into the system/etc/ directory?
bstijl said:
sorry i could have read it wrong but...
when using Method 2, is it enough to copy just the gps.conf into the system/etc/ directory?
Click to expand...
Click to collapse
Yes for the no ssl versión.
Sent from my Desire HD using XDA
crypted said:
Yes for the no ssl versión.
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
cool then i'm golden, will post feedback after i've used it a couple of days
Proud to report 3 seconds lock without Google location service turned on.
Sent from my Galaxy Nexus using xda premium
jroyalty7 said:
Flashed 3.1 zip using cwm, went from lock of 20m within 10 secs to lock of 10m within 10 secs on Gnex i9250 on aokp B28!!! Thanks used this for my sgs2 before also.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Want to check if you did the mount system step?
oblivionstalker said:
Want to check if you did the mount system step?
Click to expand...
Click to collapse
I wasn't complaining I was reporting an improvement!!!
Sent from my Galaxy Nexus using Tapatalk
i9250 has the best gps experience for me. i dont think i need this.
Sent from my Galaxy Nexus using xda premium
does it work on 4.0.4?
oblivionstalker said:
does it work on 4.0.4?
Click to expand...
Click to collapse
yep
Sent from my Transformer Prime TF201 using XDA
I'm having a horrible time with the GPS on my gsm gnex. It finds the birds and locks on quickly but the accuracy is absolutely horrendous. When using google navi I'm oftentimes trampling through neighborhoods like Godzilla.
I've tried your various patches and they seemed to have improved my issue a bit (maybe? placebo effect) so I'd like to do some tweaking myself. My question is, where can I find definitions for ALL the variables available for use in gps.conf? I've scoured the net and came up empty.
Thanks
aeroseek said:
I'm having a horrible time with the GPS on my gsm gnex. It finds the birds and locks on quickly but the accuracy is absolutely horrendous. When using google navi I'm oftentimes trampling through neighborhoods like Godzilla.
I've tried your various patches and they seemed to have improved my issue a bit (maybe? placebo effect) so I'd like to do some tweaking myself. My question is, where can I find definitions for ALL the variables available for use in gps.conf? I've scoured the net and came up empty.
Thanks
Click to expand...
Click to collapse
You have read my variable section descriptions in the gps.conf I assume? I have discussed a lot of these variables in the various patch threads.
I wouldn't touch anything except:
INTERMEDIATE_POS=1
ACCURACY_THRES=3000
The "Alternate" patch sets POS to 0. If you haven't tried the Alternate patch, do so.
Accuracy threshold resolves how to throw out bad readings from satellites. Increase it to 5000 to see if you can get some more birds to help throw out useless crap. Or, you can go down to 2000 to force it to get better data.
I'd think you would want to start out as:
INTERMEDIATE_POS=0
ACCURACY_THRES=3000
Move to:
INTERMEDIATE_POS=0
ACCURACY_THRES=5000
Yup I've read your descriptions. I was asking for more because in my quest to alleviate the gps issue I've come across other variables that are not in your patch, for instance C2K_HOST and ENABLE_WIPER and I could not find adequate explanations of their meaning.
I've played with INTERMEDIATE_POS and ACCURACY_THRES, currently they are set at 0 and 0 respectively so I will try your suggestions right now.
This rom is based off the HTC Aria/Gratia (codename liberty) 2.37.709.11 RUU, which can be found on shipped-roms.
Note it is quite buggy and various functions don't work.. (Radio(RIL)/Camera/etc) Obviously not for daily use just yet
Features:
-FRF91/2.2 Froyo Sense (latest ATT Aria version is based on 2.2.2/FRG83G but I had issues booting it)
-Completely stock
-Working audio (compiled libaudio/htc_acoustic from xdandroid sources with froyo r8 sdk)
-Compiled kernel based off xdandroid 2.6.27; enabled ext3, compiled all modules except bcm4329 into the kernel
-Apps2ext (moves only app and app-private to /sd-ext)
-Working sdcard
-Working touchscreen
-yes/no in recovery to choose whether to format sd-ext or not; use volume up/down to choose
-Disabled verify-bytecode
-Dalvikvm set to 20m
-Wifi turns on, scans, and connects (modified libhardware_legacy.so to point to correct wifi firmware and wpa_supplicant compiled from froyo source)
Click to expand...
Click to collapse
Bugs
-not all Market apps show (incorrect build fingerprint, will fix in next release)
-flash player is buggy and crashes browser
-Radio doesn't work
-Bluetooth doesn't work
-Resolution is screwed up (in nearly all apps)
-Camera doesn't work
-Choppy graphics but no stalls.
-All sensors (light, g-sensor).. using xdandroid sensors that doesn't work so well with current kernel
-Everything else
Click to expand...
Click to collapse
Instruction:
Just flash package.. system and data will be wiped
fastboot erase not required if coming from another rom or task29 already performed
Click to expand...
Click to collapse
Downloads:
Current Version: v0.1-alpha 122.42 MB
md5sum
Code:
b53ee905f5c56d13ca472d152ad490a4
Click to expand...
Click to collapse
Screenshot:
Click to expand...
Click to collapse
Credits:
Entire XDandroid team(LK, wifi firmware, ril, kernel, device specific libs), Neopeek (For getting me started), Infinimint (for his great ideas), tvall (team member), goAPK? (for libdvm), mundixx (disable verify bytecode), arrrghhh (for keeping the forums sane ) and everyone else I didn't mention!
Click to expand...
Click to collapse
and last note.. the CALL button is mapped to "home", all other buttons will work as they should
Please do not kang this rom without my permission.. thanks!
Kang this if you want, i don't see too much hope for this project.
This is rather interesting, and quite fitting. Is there anything you need tested? (I have a Rhodium100, if it matters)
I'll try this out later.
Japamala said:
This is rather interesting, and quite fitting. Is there anything you need tested? (I have a Rhodium100, if it matters)
I'll try this out later.
Click to expand...
Click to collapse
I would appreciate it if you could test out wifi and see if it works on gsm variants of rhod (I have rhod400).. but I'm sure everything else is broken..
Tell me what bugs you see (other than those listed), and I will attempt to fix them, along with the listed bugs..
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in /tmp/sideload/package.zip
(status 2)
Installation aborted.
Doesn't work for me. Will try flashing a different rom to double check.
Probably because of me being GSM
[EDIT] Just tried installing omgb, that works fine. It's the GSM then.
Does anyone have a clue how ACL/klinux ported Desire apps to their hero build?
I've tried various combination of framework mixing (with HDPI apps) but it always results in crashing/error..
Just FYI, I am abandoning this project since I don't have any froyo sensors for nand (froyo xdandroid sensors were meant for sdcard use) and I'm missing quite a few drivers that I don't have the skill/patient to create/modify..
@ mods: Please close thread, I'm not updating this anymore Thanks!
CyanogenMod is a free, community built distribution of Android 4.3 (Jelly Bean) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM10 RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
DOWNLOAD
http://unrestrict.li/FXP
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
FXP236 released
FXP237 released
Hi, there's any change from your releases and Cyanogem mod releases for Xperia ZL? I couldn't find any info about modifications made by FreeXperia Xperia. So i guess it is the same version as available at CM website, correct?
fabioascoelho said:
Hi, there's any change from your releases and Cyanogem mod releases for Xperia ZL? I couldn't find any info about modifications made by FreeXperia Xperia. So i guess it is the same version as available at CM website, correct?
Click to expand...
Click to collapse
depends
ususualy we test features on FXP builds then push to cm
FXP239 released
I was wondering, is there a particular reason why the phone (C6503) is unable to successfully connect, neither automatically nor manually to a given mobile network after a normal (lengthy) network search? I've had other people here report that they experience this very same problem on their ZL as well, both on 10.1 and 10.2. All it says is: "Cannot connect to this network right now. Try again later."
Another question is, would it be possible to add the network types (4G, 3G and 2G) beside each available network as it is displayed on original Sony Firmware? You can see an icon beside each network type you choose from. That way, if you need to use only one specific "tower" or band during a given time, you could do so, without having to manually switch the radio on or off between 4G, 3G and 2G manually.
I hope you get what I'm trying to say here...
Thank you FXP for your hard work and dedication. Your work is really appreciated. :thumbup:
:beer:
FXP said:
FXP239 released
Click to expand...
Click to collapse
Is it Stable release or Nightly?
"Nightly-ish" unless otherwise specified
Any chance to get new "Color/gamma calibration" feature working on fusion3 devices?
Does it need some kernel changes to be implemented first?
NeverGone\RU said:
Any chance to get new "Color/gamma calibration" feature working on fusion3 devices?
Does it need some kernel changes to be implemented first?
Click to expand...
Click to collapse
Very good question, I'd also like to know this.
Be nice if the libs etc. were updated to .67 and the audio paths fixed so Spirit FM has audio every boot not 1 in 3... and Autobrightness - works sometimes, not others!
I also find that building one's own CM 10.2 fails to boot fully since late September, gets as far as "Android is updating apps and loops - if anyone has any ideas... appreciated
LenAsh said:
Be nice if the libs etc. were updated to .67 and the audio paths fixed so Spirit FM has audio every boot not 1 in 3... and Autobrightness - works sometimes, not others!
I also find that building one's own CM 10.2 fails to boot fully since late September, gets as far as "Android is updating apps and loops - if anyone has any ideas... appreciated
Click to expand...
Click to collapse
i have 2.67 blob ready, but i need to test on Tab Z Wifi
Spirit FM ?
AutoBrightness is wonky, sometime sensor report wrong value i think sony have some kind of workaround somewhere
if it doesnt boot, it's your fault
My fault? Build is broken. If someone has changed something and not reflected it in the CM Wiki or on here, then that's a shame. Try it and see all the build errors and warnings.
Sent from my C6503 using XDA Premium 4 mobile app
LenAsh said:
My fault? Build is broken. If someone has changed something and not reflected it in the CM Wiki or on here, then that's a shame. Try it and see all the build errors and warnings.
Click to expand...
Click to collapse
buildbot seems to be better then u
imho, look the errors, but i'm pretty sure u miss something
Has the manifest changed? Repo syncs OK and the ROM builds but with many warnings and errors. This "problem" started a little over a week ago. I haven't changed the way I do this, so my only assumption is something has changed that is not reflected in the build guide. The GS3 and H One build fine...
To answer your query about Spirit FM, this is a good replacement FM radio app that's been around for a while. Since the stock CM FM Radio app is "flakey" Spirit provides a usable alternative. However, on CM (using the Digital audio path as the Analog audio doesn't work at all) it is a lottery whether any sound is produced without a reboot. I haven't been able to work out yet what conditions MIGHT cause this... sometimes a toast appears stating that xxxx couldn't start the media player. Once working, it works extremely well.
Hope that helps and look forward to your forthcoming updates for the Sony 2013 models.
Sent from my C6503 using XDA Premium 4 mobile app
Get this - trying the new repo release -
info: A new version of repo is available
object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <[email protected]> 1380645867 -0700
repo 1.12.4
gpg: Signature made Tue 01 Oct 2013 17:44:27 BST using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'
warning: Skipped upgrade to unverified version
Syncing work tree: 100% (397/397), done.
EDIT: Build now works - shame the guy who updated it on the 1st October omitted to tell the world...
Thanks for the recent updates Giulio, appreciated.
Sent from my C6503 using XDA Premium 4 mobile app
Guyz can any 1 port nexus 5 lollipop update for galaxy grand duos i9082.
When will the new lollipop update come for our grand duos....???
Sent from my GT-I9082 using XDA Premium 4 mobile app
::thumbup:
Sent from my GT-I9082
pawitp said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy Grand Duos are available from https://github.com/pawitp/android_device_samsung_i9082 and https://github.com/pawitp/android_kernel_samsung_i9082.
Compatibilitiy Patches: https://gist.github.com/pawitp/cba169c87dba57eea8ef
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: http://goo.im/devs/pawitp/i9082_cm12.0
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Dual SIM
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Additionally, Dual SIM has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support (.tar) (.zip by codekidX). Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
How do I enable/disable Dual SIM?
Dual SIM support is enabled by default. If you only use 1 SIM and wants to disable Dual SIM support, you can use the following instruction:
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
(Instruction screenshots)
Are delta updates available?
Delta updates are not yet available for CM 12.0.
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Will you make this official CM?
Due to the amount of work and commitment involved, I am not planning to make an official CM port.
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (I9082 or I9082L):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- My real-life friend for letting me borrow his phone to work on this
- RampantRhino for donating a phone to help me continue with this project
Click to expand...
Click to collapse
See this
Press thanks if I helped
Sent from my GT-I9082 using XDA Premium 4 mobile app
Legendary PAWITP has given us a great cm12 ROM
I find it almost 100% similar to the official lollipop
Great ROM...
I cannot thank "pawitp" enough....
Grand users are lucky to have such great developers like pawitp, xenon, and others...
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Introduction
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
Prerequisites for Installation
- You must be on stock firmware:
update-fire-phone-33.4.6.1_user_461013320.bin OR ...461013820.bin <- Please confirm this before proceeding <-
- You must have root access
Known Issues
- Secondary slots do not work at all. Any attempt to flash a secondary slot will result in you having to re-sideload stock 4.6.1
Compatible ROMS
- CM-11 coming soon
Installation
- If not already rooted, use Kingroot from here to obtain root access.
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for Amazon Fire Phone (Kodiak)
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Fire Phone
Contributors
ggow
Version Information
Status: Beta
Current Beta Version: 4.0.1
Created 2015-07-04
Last Updated 2016-08-17
Reserved
---
- Link is now up
CM-11 progress so far
- Attached is a couple of photos of CM-11 running on Fire phone
Things that are not yet working:
(1) Audio through the speakers
- Music and system sounds through the headphones seems to be working
- This phone uses a TFA9887 audio amplifier chip. Need to figure out a way to enable it. The stock kernel sources don't seem to make any references to it so... must be controlled in userspace.
- In the amazon stock ROM it looks be controlled by two shared libs: libaudio-ExternalSpeakerAmps.so and libaudio-NxpTfa9887.so which are loaded by audio.primary.msm8974.so
- When trying to use the stock audio.primary.msm8974.so I see this in the logs:
Code:
[INDENT]D/audio_hw_primary( 496): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 496): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 496): ACDB -> send_audio_cal, acdb_id = 53, path = 0
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (0) at address = 0x34. Error = 108
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (1) at address = 0x35. Error = 108
D/audio_speaker_platform( 496): Loading speaker use case "music"[/INDENT]
oooooo going to be keeping a very close eye on this thread now.
Update
Progress for today.
- WiFi is working
- Sensors are working
- Baseband seems to be detected correctly - put my sim card in and got a SIM network unlock screen - screenshot attached. I got the phone for nearly next to nothing. But looks like I need it unlocked to use my SIM.
- Bluetooth is working - paired with a keyboard and works good.
- Gapps working
- Front and rear camera not working yet
- Sound, need to figure this out - this is a show stopper at the moment. No Ringing of phone etc
On the amplifier issue did a little digging and other devices like the HTC M7 tend to have a kernel driver which implements an IOCTL interface to userspace but this doesn't seem to the case in the Fire Phone's stock kernel in which I couldn't find any reference to the TFA9887.
I'll have to research a bit more.
I'll do an early preview release at a good point.
Thanks for your hard work.
wonderful ! I just bought fire phone
Thanks for your. Hard.working,I just get my fire phone
Great work! Congrats!
Great work will this also work on the US 4.6.1 software version 461013820.bin. thanks
tintin1892 said:
Great work will this also work on the US 4.6.1 software version 461013820.bin. thanks
Click to expand...
Click to collapse
Should work. If it doesn't, you should be able to boot into the amazon recovery and sideload your stock firmware.
Let me know your results. Once you confirm its working I'll update the OP.
Sent from my Nexus 6 using Tapatalk
Thank you very much, i already installed it and it works fine with the us version 35.4.6.1...461013820, too.
D/audio_hw_primary( 496): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 496): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 496): ACDB -> send_audio_cal, acdb_id = 53, path = 0
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (0) at address = 0x34. Error = 108
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (1) at address = 0x35. Error = 108
D/audio_speaker_platform( 496): Loading speaker use case "music"
Click to expand...
Click to collapse
@ggow
Just making an observation, the external speakers do not depend individually on the stock audio libs (libaudio-ExternalSpeakerAmps.so ; libaudio-NxpTfa9887.so etc..) but might also depend on Dolby frameworks that the stock rom calls.
I want to test it out but i'm having problems with hyper-v atm.
v6ser said:
@ggow
Just making an observation, the external speakers do not depend individually on the stock audio libs (libaudio-ExternalSpeakerAmps.so ; libaudio-NxpTfa9887.so etc..) but might also depend on Dolby frameworks that the stock rom calls.
I want to test it out but i'm having problems with hyper-v atm.
Click to expand...
Click to collapse
Thanks.
I had a brief look at the chain of dependencies. This is all I could find. However I will take a look tomorrow. And let you know what I find
CM-11 Progress update
- Front and rear cameras are now working.
- Google camera and OpenCamera are perfectly fine
- Stock camera app is displaying the preview image upside down.
- Google camera seems to give significantly better photo quality than the stock camera app.
- I will probably remove stock camera app from the build.
Good News
- I have audio on the the speakers... Exactly as I thought- the Tfa9887 is controlled only from the two shared libs I previously mentioned. The fix was to set the correct permissions on /dev/i2c-8 and set a property which indicates audio has been initialized correctly.
- I have a few things to tidy up - like a couple of force closes etc
- Need to do a bit of testing, test video, a couple games etc
- After all of that it should be ready to go.
- I won't have tested make calls, sms and mobile data - so the first release will be a BETA.
EDIT: I should start a [DEV] thread for this so I don't clog up this thread anymore.
ggow said:
- I have audio on the the speakers... Exactly as I thought- the Tfa9887 is controlled only from the two shared libs I previously mentioned. The fix was to set the correct permissions on /dev/i2c-8 and set a property which indicates audio has been initialized correctly.
- I have a few things to tidy up - like a couple of force closes etc
- Need to do a bit of testing, test video, a couple games etc
- After all of that it should be ready to go.
- I won't have tested make calls, sms and mobile data - so the first release will be a BETA.
EDIT: I should start a [DEV] thread for this so I don't clog up this thread anymore.
Click to expand...
Click to collapse
great work as i have a fire phone been hoping something would come out. i have installed safetrap which is working going to install the stock firmware through safestrap. also my fire phone is unlocked to all networks and maybes be able to test it just a thought.
fantastic work
can cm11 be downloaded yet as most my android apps wont work with fire os
wjamie30 said:
great work as i have a fire phone been hoping something would come out. i have installed safetrap which is working going to install the stock firmware through safestrap. also my fire phone is unlocked to all networks and maybes be able to test it just a thought.
Click to expand...
Click to collapse
m4nik10 said:
fantastic work
can cm11 be downloaded yet as most my android apps wont work with fire os
Click to expand...
Click to collapse
- I will be doing a release today
- Netflix and youtube are not working ATM it seems but I can fix that up later.
- Keen to now get it out there to find out if telephony, sms etc is working.