AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
Currently, this is tentative support.
Tentative support is based upon reports from users of this device who decided to use the patch and report back on their own.
Reports indicate great success.
Works awesome and the mod has helped me getting a GPS fix in just 40 seconds that too from inside a building. I lost the quick fix since updating from a stock ROM to CM 10 AOKP but I see this has better performance than the stock ROM too. A must try for anyone. Besides, the best part about this mod is that the one file that is replaced if not giving satisfactory results can be reverted back to the old one without a fuss.
---------- Post added at 11:05 PM ---------- Previous post was at 10:32 PM ----------
Umm, a question to the dev and anyone who has any info on this, has GLONASS been disabled on the FXP or CM ROMs for the Xperia S?
a4rocks said:
Works awesome and the mod has helped me getting a GPS fix in just 40 seconds that too from inside a building. I lost the quick fix since updating from a stock ROM to CM 10 AOKP but I see this has better performance than the stock ROM too. A must try for anyone. Besides, the best part about this mod is that the one file that is replaced if not giving satisfactory results can be reverted back to the old one without a fuss.
---------- Post added at 11:05 PM ---------- Previous post was at 10:32 PM ----------
Umm, a question to the dev and anyone who has any info on this, has GLONASS been disabled on the FXP or CM ROMs for the Xperia S?
Click to expand...
Click to collapse
I have no clue as to what a particular ROM does to GLONASS support in devices that do support it. However, this patch does not alter GLONASS usage whatsoever on a device. This only alters the GPS side of the location functionality.
This does assist in better performance of GPS/GLONASS combinations because it decreases the GPS response time which works in tandem with GLONASS when GLONASS is enabled within your device's code -and- functioning through its receiver.
crypted said:
I have no clue as to what a particular ROM does to GLONASS support in devices that do support it. However, this patch does not alter GLONASS usage whatsoever on a device. This only alters the GPS side of the location functionality.
This does assist in better performance of GPS/GLONASS combinations because it decreases the GPS response time which works in tandem with GLONASS when GLONASS is enabled within your device's code -and- functioning through its receiver.
Click to expand...
Click to collapse
Ok so a couple of hours of research into GPS and GLONASS gave quite a bit of interesting insights. GLONASS does work on CM10 JB as tested by GPS Status. Phew, there is so much to learn. Its actually interesting tech. However, I see that GLONASS is not as active or quick as it used to be on the Stock Sony ROMs. Any way you could try and tweak that crypted?
a4rocks said:
Ok so a couple of hours of research into GPS and GLONASS gave quite a bit of interesting insights. GLONASS does work on CM10 JB as tested by GPS Status. Phew, there is so much to learn. Its actually interesting tech. However, I see that GLONASS is not as active or quick as it used to be on the Stock Sony ROMs. Any way you could try and tweak that crypted?
Click to expand...
Click to collapse
I really don't have experience with GLONASS. If there are configuration files (.conf or .xml), I can look into it. You'd have to private message me the contents though.
Just to reiterate, this patch does not affect GLONASS with any device. It only benefits GPS and in combination helps with locks that are either GPS or a mixture of GPS and GLONASS data.
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
devilsneck said:
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
Click to expand...
Click to collapse
You proved your ignorance in how aGPS works. Good for you!
Downloading the almanac isn't the only thing that resolves GPS issues. Sure, you're lucky and get a great lock time. How good is your accuracy, though?
From that, this is for people with problems as the OP post discusses. Do I suggest someone use it if there isn't an issue? NO.
Before you post on some development thread, make sure you're ignorance isn't showing.
devilsneck said:
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
Click to expand...
Click to collapse
First of all, you may be using the stock ROM and as I reiterate again, stock ROMs have better GPS fix times than CM ones. Sony must have optimised them nicely but since I upgraded to Jelly Beam CM, I was having issues with respect to quick fix on location. In fact, no one even looks at GPS fixes around unless there is something drastically wrong. Good that you don't issues but please do not berate someone else's work for something that is of no use to you but a lot of use for other mates with Xperia S and JB.
a4rocks said:
First of all, you may be using the stock ROM and as I reiterate again, stock ROMs have better GPS fix times than CM ones. Sony must have optimised them nicely but since I upgraded to Jelly Beam CM, I was having issues with respect to quick fix on location. In fact, no one even looks at GPS fixes around unless there is something drastically wrong. Good that you don't issues but please do not berate someone else's work for something that is of no use to you but a lot of use for other mates with Xperia S and JB.
Click to expand...
Click to collapse
First off, I'm not on stock, I'm using PA's latest JB build.
Anyway, as I said, I didn't mean to diss the member's work.
I respect the time he has put into it.
I'll just leave you guys to yourself, apoligies for pointing out something easier.
Peace.
---------- Post added at 08:17 PM ---------- Previous post was at 08:02 PM ----------
crypted said:
You proved your ignorance in how aGPS works. Good for you!
Downloading the almanac isn't the only thing that resolves GPS issues. Sure, you're lucky and get a great lock time. How good is your accuracy, though?
From that, this is for people with problems as the OP post discusses. Do I suggest someone use it if there isn't an issue? NO.
Before you post on some development thread, make sure you're ignorance isn't showing.
Click to expand...
Click to collapse
I have pretty good accuracy, I use my GPS daily.
I only posted cause I was having the same problem and I fixed it by updating the a-gps data.
Somebody try it first maybe and report back if it helps?
Im sure you know more about GPS than me,
So Im sorry if I came along as a douchebag and thank you for your great contribution!
:good:
devilsneck said:
First off, I'm not on stock, I'm using PA's latest JB build.
Anyway, as I said, I didn't mean to diss the member's work.
I respect the time he has put into it.
I'll just leave you guys to yourself, apoligies for pointing out something easier.
Peace.
---------- Post added at 08:17 PM ---------- Previous post was at 08:02 PM ----------
I have pretty good accuracy, I use my GPS daily.
I only posted cause I was having the same problem and I fixed it by updating the a-gps data.
Somebody try it first maybe and report back if it helps?
Im sure you know more about GPS than me,
So Im sorry if I came along as a douchebag and thank you for your great contribution!
:good:
Click to expand...
Click to collapse
aGPS almanac data renewal downloads is less than 10% of the issue most of the time.
If you open up my configuration file, you will notice that there are tons of variables and each are customized. I created sections explaining the general synopsis of var sets...
Now we have a (near) complete configuration. I tossed in that near because there could be surprises I haven't found, but this thing has brought devices back to life that had no GPS. In fact, ASUS ripped my work on the Transformer series and put it in their official ROM updates without a gracias whatsoever.
Lets then consider internet mobile data networks. I offer something more. GPS Status queries the same address in the gps.conf to update the aGPS data. Well, compare them. I provide a CDN (content delivery network) that provides xtra.bin data rather than Qualcomms overloaded server. This has brought about great resolutions in general latency and timeouts of downloading almanac data.
This is directly on subject with your little mention.
From that, I created and maintain an DNS pool of Stratum II time servers rather than NTP.ORG cable modems because of the same network testing observations.
Over 20 mobile carrier networks around the world were tested.
There's gotta be a reason why my patch has tens of thousands of direct downloads, millions of queries per month, etc.
EDIT: The dev of GPS Status and I are considering a joint effort to bring his APK and my work together in a Google Play environment. If we do it, it'll be early 2013. He knows APK side and bringing GPS readings to the forefront. I know the backend process.... Sounds like a good mix...
Crypted, my GPS isn't communicating at all with Google Maps. While GPS status is properly tracking, there is no location in Google Maps. Data connection only helps in tracking the same. What may be wrong here?
Sent from mein wünderbar Xperia S
a4rocks said:
Crypted, my GPS isn't communicating at all with Google Maps. While GPS status is properly tracking, there is no location in Google Maps. Data connection only helps in tracking the same. What may be wrong here?
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
Uninstall, then reinstall Maps. If all other apps are working fine with GPS, then the problem lies somewhere within the GMaps receiving and processing of the data.
crypted said:
Uninstall, then reinstall Maps. If all other apps are working fine with GPS, then the problem lies somewhere within the GMaps receiving and processing of the data.
Click to expand...
Click to collapse
I will try other apps but reinstalling, checking unchecking GPS options, clearing cache and dalvik cache haven't helped at all. It's strange because in any case, it is not even interfacing with the GPS.
Any fixes you can suggest?
Sent from mein wünderbar Xperia S
a4rocks said:
I will try other apps but reinstalling, checking unchecking GPS options, clearing cache and dalvik cache haven't helped at all. It's strange because in any case, it is not even interfacing with the GPS.
Any fixes you can suggest?
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
Did you completely uninstall Maps and reinstall it after a reboot?
And, did you try another ROM?
Sent from my Galaxy Nexus using xda app-developers app
I haven't tried another ROM but I guess I will. And I definitely completely un installed, rebooted and reinstalled. The fact that this is so weird that I could not find any solutions elsewhere has made me mad. I actually kinda love this ROM. I will try another navigation application in the mean time but if you have a prospective solution, it would be absolutely awesome
Sent from mein wünderbar Xperia S
a4rocks said:
I haven't tried another ROM but I guess I will. And I definitely completely un installed, rebooted and reinstalled. The fact that this is so weird that I could not find any solutions elsewhere has made me mad. I actually kinda love this ROM. I will try another navigation application in the mean time but if you have a prospective solution, it would be absolutely awesome
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
As I said before, it's a GMaps library issue from what you described. It could be ROM related since you stated that GPS Status is perfectly on target and GMaps uninstall didn't work.
If this randomly began happening with everything working 100%, something may have corrupted in one of your NANDFlash partitions....
crypted said:
As I said before, it's a GMaps library issue from what you described. It could be ROM related since you stated that GPS Status is perfectly on target and GMaps uninstall didn't work.
If this randomly began happening with everything working 100%, something may have corrupted in one of your NANDFlash partitions....
Click to expand...
Click to collapse
And is the NANDFlash partition recoverable? :crying:
crypted said:
aGPS almanac data renewal downloads is less than 10% of the issue most of the time.
If you open up my configuration file, you will notice that there are tons of variables and each are customized. I created sections explaining the general synopsis of var sets...
Now we have a (near) complete configuration. I tossed in that near because there could be surprises I haven't found, but this thing has brought devices back to life that had no GPS. In fact, ASUS ripped my work on the Transformer series and put it in their official ROM updates without a gracias whatsoever.
Lets then consider internet mobile data networks. I offer something more. GPS Status queries the same address in the gps.conf to update the aGPS data. Well, compare them. I provide a CDN (content delivery network) that provides xtra.bin data rather than Qualcomms overloaded server. This has brought about great resolutions in general latency and timeouts of downloading almanac data.
This is directly on subject with your little mention.
From that, I created and maintain an DNS pool of Stratum II time servers rather than NTP.ORG cable modems because of the same network testing observations.
Over 20 mobile carrier networks around the world were tested.
There's gotta be a reason why my patch has tens of thousands of direct downloads, millions of queries per month, etc.
EDIT: The dev of GPS Status and I are considering a joint effort to bring his APK and my work together in a Google Play environment. If we do it, it'll be early 2013. He knows APK side and bringing GPS readings to the forefront. I know the backend process.... Sounds like a good mix...
Click to expand...
Click to collapse
Apk on google play would be awesome!
a4rocks said:
And is the NANDFlash partition recoverable? :crying:
Click to expand...
Click to collapse
I don't know how it works for your device as it's different in each model, but usually in those instances it flushes out corrupted GPS cache within a few days.
You really need to test another ROM if other navigation apps (not Google's or any relying on GMaps API) fail you.
Related
VillainROM 5.5.0
This is the latest version of VillainROM - version 5.5.0
Important Info:
As of Today, VillainROM will use a highly optimized, zip-aligned version of the STOCK HTC ROSIE. Authorised VillainROM themes will soon be available as OTA updates (yey).
A lot of hard work goes into these roms. If you like our work, please consider making a small donation.
To the ROM:
- Multi-Language (Keyboard Only I am told)
- Good 3D Performance (Further improved in 5.5)
- Gallery 3D 100% working (Speed & rotate fixed)
- Apps2SD working
- Streaming works perfectly
- VillainROM custom splash screen (you'll only see it once or twice
- Stock Rosie
- VillainROM Wallpaper
- Syncing works flawlessly
- Extra Special HTC Keyboard with Voice Input & LOADS of options
- All hardware working as it should
- No graphical glitches anywhere
- Busybox
- Rooted
- Huge APN list
- VPN
- Launcher 2 works - just push it.
- LIVE WALLPAPERS WORK WITH SENSE (Use optional patch)
- Network Location working 100%
- All apps in market
KNOWN ISSUES/FYI:
- MMS Issue exists, fix is available within the forum (just search)
- Split messages (Hotfix coming soon - two of us are working on this)
- No Voicemail indication
DOWNLOAD LINKS:
VillainROM 5.5.0
IMPORTANT INFO!
Thanks: To ALL the VillainROM Mod/admin/dev team & the various devs which have helped me in the past.
You may or may not be aware, VillainROM has its own kitchen, created by our very own Kendon.
OTA INFO
The OTA tool is now far more stable than it was at launch. All hotfixes & updates to this ROM will be made available OTA.
PLEASE BE AWARE: If your Phone is connected as a disk drive via USB, OTA UPDATER WILL FC.
nprussell said:
All,
First things first:
This is a VERY EARLY ALPHA. It's been ported over from the latest CDMA Sprint Hero, and it's being referred to as a FINAL test build.
NANDROID BACKUP BEFORE INSTALLING
DO NOT FLASH THIS ROM EXPECTING IT TO BE COMPLETE. I'M WELL AWARE THAT IT ISN'T.
Who should flash this ROM?
- Anyone willing to help find all of the bugs/not working HW.
- Any developers looking to help
Definitely Working/Current Features:
- Calls in and out
- EXTREMELY FAST
- Data Connection
- Network Location
- Automatic Brightness
- All apps in market
- Very interesting 2.1 Rosie layout (I don't know if the guys over on the CDMA forums themed this or not...)
- All 2.1 Goodies expected (Friendstream etc)
Known Bugs right now:
- WIFI DEFINITELY DOES NOT WORK
- Graphical glitch when sending contact types
GPS & Bluetooth are untested
I am currently working on the fixes for this ROM. If you're a developer and find the fixes, please contact me...
CLICK HERE FOR DOWNLOAD LINK
Special thanks to:
Pulser, Behnam, RaiderX, Kendong, LennyUK and the guy that set up the bug tracker, whose name evades me.
Click to expand...
Click to collapse
Guessing this is from my release then
Awesome! On first boot now, looking good so far.
booting now, takes a loooonnnggg time
booting now..
why the nexus boot?
Hello, this version goes for Spanish heros? gsm?
Thanks
Sounds great, really looking forward to trying it. Think I'm gonna wait to read some feedback from the more adventurous guys before I flash it though
I can't access http://villainrom.co.uk/, get a server not found error. Could someone mirror it?
EDIT: Hm, it works fine from my phone...
any idea how to ifx the wifi? i can try it (maybe you can copy > past the fix behnaam send you?
should I avoid..
Clearly this is a port from cdma hero, I am on v4b2 right now and was not reflecting if it was a port for cdma or gsm, witch one is it ? Am I going to suffer any slowdowns in internet connection using the villain rom series... ? since the gsm radios utilize hsdpa they are suposed to give you quite a speed improvement for the internet connection right ?
Gipsyboy said:
Clearly this is a port from cdma hero, I am on v4b2 right now and was not reflecting if it was a port for cdma or gsm, witch one is it ? Am I going to suffer any slowdowns in internet connection using the villain rom series... ? since the gsm radios utilize hsdpa they are suposed to give you quite a speed improvement for the internet connection right ?
Click to expand...
Click to collapse
This is a GSM ROM. It's been ported FROM a CDMA ROM, which is why there will be some hardware bugs at first, but this is definitely meant for GSM Heros.
craig0r said:
This is a GSM ROM. It's been ported FROM a CDMA ROM, which is why there will be some hardware bugs at first, but this is definitely meant for GSM Heros.
Click to expand...
Click to collapse
Awesome, let the flashparty begin
thank you very much to prove.
Am I being over optimistic, but as this is a Hero build (albeit a CDMA one) does this mean we can use the kernal? Do we final have a kernal that won't kill our batteries?
damageless said:
Guessing this is from my release then
Click to expand...
Click to collapse
Indeed it is, and unfortunately I can't edit nathan's post to acknowledge you here. I have done so on the villainrom forums (www.villainrom.co.uk), as this ROM would not have been possible without DamageControl, so thanks
Credit added.
l0st.prophet said:
Am I being over optimistic, but as this is a Hero build (albeit a CDMA one) does this mean we can use the kernal? Do we final have a kernal that won't kill our batteries?
Click to expand...
Click to collapse
A bit optimistic I wouldn't try it, as it won't work, and it can apparently cause damage by frying your radio.
So don't try it, unless someone reliable can confirm why it would be different, and safe...
How's youtube working for everyone?
anon2122 said:
Indeed it is, and unfortunately I can't edit nathan's post to acknowledge you here. I have done so on the villainrom forums (www.villainrom.co.uk), as this ROM would not have been possible without DamageControl, so thanks
Credit added.
Click to expand...
Click to collapse
It's all good. Just wanted to make sure. I figured you guys could use this and was about to PM one of you, but looks like you figured it out.
Anyone fancy an untested potential (but unlikely) solution to no wifi?
The download has not been tried, will likely bootloop, but if you fancy trying it, nandroid first!
At your own risk: www.villainrom.co.uk/trythis-signed.zip
@damageless:
you got any ideas what could be causing our wifi not to work? Coming up wifi driver not initialised or something like that in logcat.
hello, just a quick message before i go bed
rom is really go so far, only bugs ive noticed are:
already said, no wifi
same gallery rotation bug
and the accelorometer doesnt seem to work
oh yes and i just got a force close on the weather widget.
its totally stable and fast apart from that
cheers and night!
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works now! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details .
Yay! No more "when is FRX07 coming out?" posts!
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner.
Woooohooooo!!! Thanks to all of the dev's on this, Stine, Hyc, Emwe, Arrrghhh (for putting up with all the BS!), and anyone else involved.
Can't wait to try this out. Thanks to all who contributed =)
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
Just to get a sense of things, is it too soon for a "when is FRX08 coming out" post?
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
bluenote73 said:
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ah yea... I need to test this on a RAPH800 I just got my hands on, thanks for reminding me!
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
wmg316 said:
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
Click to expand...
Click to collapse
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
arrrghhh said:
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
Click to expand...
Click to collapse
Thank you sir!
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
webxplore said:
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
Click to expand...
Click to collapse
Figured out...Had a corrupt zimage file. Able to launch now.
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
First Impressions
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:
WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet )
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works
maff1989 said:
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
Click to expand...
Click to collapse
+1
Come from FroyoB Hercules v2.
Any possible to run FRX07 on CWM?
FRX07 on cwm is being worked on by Eodun,wich sadly yesterday released FRX06 for cwm
rtrip said:
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
Click to expand...
Click to collapse
I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.
I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...
Hi everyone. Im one of the developers of SwitchMe, and app that allows multiple secure logins into separate installations of android on a single device. The pr is after the break.
I really need a few people to check into some issues people on some ROMs have been experiencing. There are some warnings involved:
- testers must perform a full nandroid backup before using the app, it is not our responsibility if you start getting boot loops
- if you report results or bugs, please use the "Write to us" function in the app whenever possible, and always describe the issue in the header of the logs you send
- if you post here, bes sure to include your device type and rom
- if you have apps installed on sd, be sure to mention that as well
--------------------------------------------------------------------
SwitchMe is a unique application for root users that allows you to log in and out of multiple installations of Android just as you would on a desktop computer.
The technology behind SwitchMe saves all of your applications and data, protects it and stores it as a file in memory. You can then log out of an
account and log into a fresh installation of Android or another account with its own unique content.
You may create as many profiles as the memory is capable of holding. Some of these may require very little free memory because they contain few apps,
others will be larger as they contain many applications and lots of cache and data.
Why is this functionality useful?
Privacy - the most obvious benefit is that you can securely share one device among multiple users, which gives you privacy and peace of mind.
Testing - if you are a developer, you can use profiles as clean sandboxes to test your applications and their interaction with the system.
Gaming – with multiple installations of Android on a single device, you can now play online MMOs as different characters.
Speed - the games your kids play slow down your tablet, but with SwitchMe you can easily create profiles without games or instant messengers.
Battery life - when the battery is low but there are important emails or documents to edit later, switch to a profile which only contains these essentials.
These of course are only suggestions - there are plenty of other uses for the functionality SwitchMe offers.
Market link:
https://market.android.com/details?id=fahrbot.apps.switchme
The Lite version allows the creation of two profiles, enough to test on.
Screens:
SwitchMe 1.2 has been rolled out and now includes a lockscreen replacement:
1.2
Added lock screen for logging in and out
More stable Fast switch implementation
Reworked UI colors
Now, its very important that we get some feedback on how this big new feature works, so please read up on it in the help and post your thoughts!
1.2.2 - HOTFIX 2
Reworked widget on qHD+ displays
Fixed widget text on HC and ICS
Fast switch improved on older devices
Nice, thanks!
Thank you! Any issues to report?
What do you think of yesterday's update?
1.4.3.7
Fixed device specific switch screen crashes and issues
Fixed UI bug in switch screen preferences
If anyohe had problems with superuser before, this should fix them. Please let me know if that is the case, its important we get some feedback here!
This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?
xethor said:
This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?
Click to expand...
Click to collapse
I dont see why not. Just make sure you back up your profiles to the SD card if you do a wipe.
They are in /data/.profiles. Next release will have an im-app backup function.
1.5.3.0
Enabled full support for MIPS and x86 architectures
Many root daemon code fixes and optimizations implemented
Sorry backup is relegated to the next release.
Thought I should let you guys know of the issue I had with the paid version of this earlier.
Running Hyperdroid Androidmeda 6.1.17, I rebooted my phone and SwitchMe would ask me to log in, however it wouldn't list the username, wouldn't log in when I put the info in myself, and wouldn't even say the password was wrong when I entered it wrong on purpose. I tried multiple reboots etc, the issue persisted.
Unfortunately I don't have a logcat or anything since I was in a rush to get my phone working properly (had to leave soon) so I restored a nandroid from before I installed SwitchMe
This was all before the 1.5.3.0 release btw, happened last week.
Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"
THANKS good
ftgg99 said:
Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"
Click to expand...
Click to collapse
thanks goo work
Enjoy! And spread the word
This thing is rock solid thanks very much
Thanks, by the way we released a new app today some of you might also find useful, you can find it here:
http://forum.xda-developers.com/showthread.php?t=1538222
PLEASE CHECK IT OUT AND BE KIND
Touch Blocker Beta - a simple but useful app that makes holding and using your device easier
There are two basic functions:
- create dead zones where touches do not register
- filter the screen when reading in low light
We are already in a relatively stable Beta release - whats left now is adding new features and making it all look pretty. You can follow this process at the thread here.
Please be sure to write suggestions - we are looking forward to engaging the community and building a useful and nifty application that many will enjoy!
Market link
https://play.google.com/store/apps/details?id=fahrbot.apps.touchblocker
Screens
Debugging
If you experience issues, the best way to help is by reproducing them and then clicking "write to us" - be sure to include a description of your error or we may not read the logs.
1.5.3.1
Fixed issue with lock on boot
Fixed some rare crashes on lock screen
Fixed MIPS and X86 Key compatibility
Any issues with the latest version?
I take it everything is fine?
Any issues to report?
Hello,
My phone is currently on Stock i927UCLJ3 with root, wifi teher and keyboard light fixes added.
The issue is that AGPS is not functional, location detection takes very long, every GPS start is like a cold start.
I have tried several times to sniff any network communication during GPS start, but only NTP packets, no requests to xtragps or google.
See attached image for my /system/etc/gps.conf file listing.
Is there any way to get it working with my current firmware?
I wonder if anybody has the same issues.
the problem is that you're on stock samsung rom, and not on AOSP. to tell you the truth, you wont get a fast gps lock until you flash a new rom, but it's worth it! for example cyanogenmod 10 is waaay faster in every details. gps, boot time, scrolling smoothness, etc. you really should flash it.
soadzoor said:
the problem is that you're on stock samsung rom, and not on AOSP. to tell you the truth, you wont get a fast gps lock until you flash a new rom, but it's worth it! for example cyanogenmod 10 is waaay faster in every details. gps, boot time, scrolling smoothness, etc. you really should flash it.
Click to expand...
Click to collapse
Anything not reliable on cyanogenmod 10 ?
Bluetooth is mentioned in the Dev forum.
Can the /etc/gps.conf and sirfgps.conf from cyanogenmod 10 be used on stock, or that wont work ?
Maruzko said:
Anything not reliable on cyanogenmod 10 ?
Bluetooth is mentioned in the Dev forum.
Can the /etc/gps.conf and sirfgps.conf from cyanogenmod 10 be used on stock, or that wont work ?
Click to expand...
Click to collapse
you can use the gps.conf from cm10, but I think it's not related to the problem,because it contains the same as on stock. The source of the gps issue is much deeper I think.
There are a few things that don't work on cm10. On skype, or viber (any similar progs) sound gets slow and it's not understandable. Also "face unlock" feature doesn't work, but who uses it anyway? With the keyboard and kbbacklight fix, it has no other issues I think.
cm10.1 is a different story, it has all the issues as cm10 has , plus keyboard backlight is not so good (it's related to the capacitive keys' lights, therefore it lights also when keyboard is closed. not so battery-friendly, but some fellows are already working on it). WiFi tethering also doesn't work, and correct me if I'm wrong,but I think there are some problems with bluetooth as well.
Long story short I (would) use cm10 with the related fixes (keyboard stuffs). I use the original version of dman's, because it contains the original kernel and I hated the "deep sleep bug" on thegreatergood's kernel, but I think it's already fixed (not uploaded though).
mr.Scamp said:
Hello,
My phone is currently on Stock i927UCLJ3 with root, wifi teher and keyboard light fixes added.
The issue is that AGPS is not functional, location detection takes very long, every GPS start is like a cold start.
I have tried several times to sniff any network communication during GPS start, but only NTP packets, no requests to xtragps or google.
See attached image for my /system/etc/gps.conf file listing.
Is there any way to get it working with my current firmware?
I wonder if anybody has the same issues.
Click to expand...
Click to collapse
Searching you will find many have this issue, not just on the Captive Glide but those also on ICS.
Have a look at this link: http://forum.xda-developers.com/showthread.php?p=24763092
This thread may help too: http://forum.xda-developers.com/showthread.php?t=2029120
I personally have fiddled with gps.conf and sirfgps.conf to try and get a faster lock, in particular from cold boot.
For me:
gps.conf = nothing seems to effect first lock time.
sirfgps.conf = some changes bring the first cold boot lock time from 4 mins down to 1 min (no amount of changes has ever brought the cold boot lock fix to faster than 1 min, if anything it made it longer the more changes I made), after the initial lock, it locks in 15 secs.
** Correction, if the GPS has not been used for more than a day, its goes back to taking 1 min to lock. **
My current gps.conf is default, I even left the NTP server to Canada, even though I'm in Australia, since it made no difference.
I've got no AGPS reference in there either, as again didnt seem to make a difference.
These are the changes I currently have in sirfgps.conf. They are slightly different to melvatron's in the other thread I've mentioned, as it seems that different options are better for some and not others.
SIRFGPS.conf (truncated, changed options only)
###
EXTERNAL_LNA=0
FREQUENCY_AIDING=1
SENSOR_AIDING=1
SSL_ENABLED=0
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=1
###
Maruzko said:
Searching you will find many have this issue, not just on the Captive Glide but those also on ICS.
Have a look at this link: http://forum.xda-developers.com/showthread.php?p=24763092
This thread may help too: http://forum.xda-developers.com/showthread.php?t=2029120
I personally have fiddled with gps.conf and sirfgps.conf to try and get a faster lock, in particular from cold boot.
Click to expand...
Click to collapse
Thank you for the links,
they helped me much.
I have tweaked my gps.conf and sirfgps.conf using the fixed files as examples.
Seems, it works for me, fix is much faster now.
I wonder why the default values are almost unusable in 4.0 Official ROM.
mr.Scamp said:
Thank you for the links,
they helped me much.
I have tweaked my gps.conf and sirfgps.conf using the fixed files as examples.
Seems, it works for me, fix is much faster now.
I wonder why the default values are almost unusable in 4.0 Official ROM.
Click to expand...
Click to collapse
Can u tell me what settings you have changed in both files that have helped the most ?
Sent from my SGH-I927 using xda app-developers app
Maruzko said:
Can u tell me what settings you have changed in both files that have helped the most ?
Click to expand...
Click to collapse
My current files:
Code:
# diff -urw /sdcard/sirfgps.conf /system/etc/si>
--- /sdcard/sirfgps.conf
+++ /system/etc/sirfgps.conf
@@ -23,16 +22,16 @@
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=0
-FREQUENCY_AIDING=0
-SENSOR_AIDING=0
+FREQUENCY_AIDING=1
+SENSOR_AIDING=1
SET_ID_IMSI=1
DEBUGGING_FILES=0
-SSL_ENABLED=1
+SSL_ENABLED=0
CERTI_VERSION=0
CP_RESPONSETIME=2
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
-ICS_NETWORK_OPERATOR=0
+ICS_NETWORK_OPERATOR=1
SGEE=0
EMC_ENABLE=1
LOG_PATH=/data
gps.conf differences attached as image, because of URL posting restrictions
Those tweaks did not work for me.
GPS fix was fast not because of new configs, but because of cache.
When I tried to use GPS some days later, time to fix was around 2 minutes.
Did you try FasterGPS from the market + reboot?
sbiricuda said:
Did you try FasterGPS from the market + reboot?
Click to expand...
Click to collapse
Tried, with no effect.
http://forum.xda-developers.com/showthread.php?t=2029120&page=2
10 days later gps locks in 17 seconds... ics4.0.4 uclj3
GPS works great on CyanogenMOD 10.1, so I suppose it was a firmware issue.
Some stats:
stock 2.3.5 - GPS ok
stock 4.0.4 - GPS very slow, looks like receiver sensivity is too low
cyan 4.2.2 - GPS ok
This is a no-frills thread.
I am looking for additional competent testers to provide proper feedback.
Testers are assumed to be experienced. Thank you.
Okay here it is.
Flash in order of appearance. Required.
cm_ivy-test_rebuild.zip
cm13_ivy_updater_system-etc.zip <--Fixes audio.
cm13_ivy_updater_bootimage_ round1.zip <-- Fixes external storage
Thanks @MotexT for initial testing and feedback.
So, working:
All CM apps; RIL; WiFi, Bluetooth; Theme Engine, Audio, Bluetooth/WiFI Hotspot work confirmed
Buggy:
Bluetooth (crashes of Bluetooth Share);
Camera (color bugs, frontal camera take photos with glitches);
Initial load/Load after reboot (glitches, performance loss - solving easy with locking/unlocking device);
AutoBrightness (small delay when switching brightness levels on the fly)
Screen Recorder
Not working:
NFC;
External SD Card;
OTG
Click to expand...
Click to collapse
Again this is alpha. This is for sinlge sim, you are welcome to test on dsds, i would be very interested in the results.
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52
Would have posted earlier but needed a smoke break *>cough<*
NOTE: this initial offering is in 3 parts due to limited bandwidth issues.
When i have resolved external storage i will upload a new build.
NFC may take a little longer.
Breathing Room
Reserved 2
@MotexT will be posting screens, as time permits, in post number 4.
Trolls will be burned.
Screenshots
Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
lukeaddison said:
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
Click to expand...
Click to collapse
Thanks,
If i can get you to specifically test and log screen recorder that would be great. [including during playback]
Currently it appears to function but when it comes to playback of the recorded file, playback breaks.
Thanks.
m
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Sent from my E6553 using XDA-Developers mobile app
So, a small report about this ROM. For now I'm using it two days in a row, and it's pretty stable - you can use main functions without any troubles: WiFi, RIL, Themes Engine etc. Bluetooth works great, crashes sometimes and automatically restarts - not a big deal. It's a really smooth for alpha build and could be used even as daily driver if you close your eyes on some small bugs with not so important stuff. Anyways, testers are welcome
KOALAaufPILLEN said:
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Click to expand...
Click to collapse
K, actually i don't know. But it's cool that you have a smart watch, would you mind be a tester/logger for that function in particular?
That would be great.
Thanks
m
Single sim
How to solve this？:crying:
Full selinux support is present.
MTP Enabled
installing '/sdcard/cm_ivy-test_rebuild.zip'...
checking for MD5 file...
Skipping MD5 check: no md5 file found
target:sony/cm_ivy/ivy:6.0.1/Nega_spork/76b3bfd6c4:user debug/test-keys
could not detect filesystem for /dev/block/bootdevice/by-name/system,assuming ext4
mount:failed to mount /dev/block/bootdevice/by-name/system at /system failed;no such volume
E:Error executing updater binary in zip '/sdcard/cm_ivy-test_rebuild.zip'
Error flashing zip '/sdcard/cm_ivy-test_rebuild.zip'
updarting partition details...
......done
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
moonbutt74 said:
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
Click to expand...
Click to collapse
it really works!Thank you
Ok cleaned this up a bit.
I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.
Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.
Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.
If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
@moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.
Thanks guys.
After looking thru all and speaking with the OP, I am closing this thread.