Related
Liberation
"Free yourself from your carrier"
Features:
[ROM Base] HTC Droid Incredible 4.08.605.2
Android 2.3.4
De-bloated
Deodexed
Battery percentage
4-in-1 advanced power menu
Removed E911 location icon
Red scrollbar and overscroll glow to complement the Incredible's looks
Zip-aligned for optimal memory management
CDROM.ISO removed (prevents that annoying Verizon install prompt when connected via USB)
Uses edify script, will flash in Clockwork Recovery 2.x and 3.x.
Removed Apps:
Adobe Flash Player (install from Android Market if you want it)
Adobe Reader (install from Android Market if you want it)
Amazon MP3 (install from Android Market if you want it)
CityID (annoying 3rd party bloatware)
Facebook (install from Android Market if you want it)
Slacker Radio (install from Android Market if you want it)
QuickOffice (for those who want a free Office reader, try Documents to Go from the Android Market)
Verizon Bloatware (My Verizon, VCAST App Store, Verizon Navigator, Verizon Skype, Verizon Backup; most can be installed via Android Market)
Youtube (install from Android Market if you want it)
Downloads:
Liberation v3.0 - 143.08MB
MIRROR (provided by BrettApple)
Changelog:
v3.0 (January 6, 2012)
Based on the latest official RUU - 4.08.605.2 (Android 2.3.4)
Red scrollbar and overscroll glow to complement the Incredible's looks
v2.0 (September 20, 2011)
Based on the latest official RUU - 4.06.605.3 (Android 2.3.4)
System hardware information corrected in about phone (bug with official OTA)
Removed Sprint section/tile from Market, replaced with Verizon (bug with official OTA)
Only 688MB available to user (see explanation in FAQ)
No longer patched to block Android Market malware (Android 2.2.2 and above are immune by default)
v1.1 (June 25, 2011)
Added battery percentage meter.
More efficient compression (smaller file size)
v1.0 (May 19, 2011)
Initial Release based on November OTA (3.21.605.1)
FAQ:Q: What was the difference between the standard and enhanced versions of Liberation?
A: In simple terms, Liberation Enhanced was deodexed, while the standard version was not. However, since the Gingerbread update, HTC has deodexed the /system/app folder, but has left framework odexed. I've decided to just deodex everything instead of having two separate versions with minimal differences in available storage, but vast differences in customization.
Q: Why is the Android Market outdated!?
A: If I insert the latest market, it won't update on its own, meaning more work for you. The version of the market I'm using is outdated, but auto updates. It will update in the background the first time that you run it, and should be updated within 2-5 minutes depending on your connection. You'll need to exit and re-launch the Market for the update to take effect.
Q: Some of my Google Apps (such as Gmail) are an old version, but don't show up on the Market as installed or needing an update. How do I fix this?
A: This is a bug or "feature" of the stock ROM, I'm not sure which. However, it as a very easy fix. Simply open Gmail from the Android Market. From there, scroll down to "Developer Info" and select "View Applications." This will display all of Google's apps in the market. Scroll down and update every app that shows as needing an update (they'll all display correctly from here). You may also want to disable automatic updates from here.
Q: Why isn't <insert app here> removed, I consider it to be bloat!
A: HTC did their best to put together an experience utilizing their Sense software. I left that intact as every user will get something out of it. Some use Friend Stream. Some use only Facebook/Twitter/Flickr. There is no perfect combination as every user wants something different. My goal was to present a stock experience without the carrier bloat. There are ways for you to remove unwanted apps yourself if you'd like.
Q: Why aren't there any screen shots?
A: It's a stock ROM. I've done nothing to differentiate this ROM in appearance from what your carrier/OEM ships.
How to customize Liberation BEFORE you flash:
Materials
Windows - 7-ZIP
Linux - nothing
Mac OS X - nothing (note, I have not done this on Mac OS X, so I cannot support this OS)
Steps
Download the above mentioned file(s) for Windows. You can use a different archive manager if you'd like, but my guide is based on using 7-ZIP.
On your desktop, create a folder named "Test." You can name it whatever you want, but I'll be referring to it as "Test" in this guide. If you are new at this, you need to follow the guide to the letter.
Find your downloaded ROM and extract it to the Test folder. The easiest way to do this on Windows is to open the ROM, highlight all of the folders/files (CTRL-A), copy (CTRL-C), then open the Test folder and paste (CTRL-V). Give it a minute to extract the contents.
Once you complete step three, modify the ROM to your hearts content (see details below). Once complete, proceed to step five.
Open the Test folder and highlight everything (CTRL-A). Right click and select "Add to Archive." This will open 7-ZIP's archive manager. On Linux or Mac OS X, just right-click (or equivalent) and select "Compress."
In the options menu that comes up, leave everything at default except the following. The filename should be Test.zip (change Test to whatever you want). Archive format should be zip. Compression level should be ultra. That's it.
Once done, you can copy this zip to your SD card and flash as normal. Keep in mind that I am not responsible for any changes that you made in this ROM, so make sure you Nandroid BEFORE you flash.
Specific Modifications (using the above instructions):
Ringtones - While the ROM is unzipped, open the test folder and look for /system/media/audio. Within this folder you'll see several more folders (Ringtones, Alarms, Notifications). Any should files you put here will show up in the system when you go to change your ringtone (or whatever corresponds to the folder). The benefits to this modification include; no storage space used up in internal, phone, or SD storage; ringtone works even if SD is USB mounted, no errors when the SD card corrupts or is in use. The ringtones (alarms/notifications) are stored in a partition that does NOT count towards your file storage
Replacement "stock" applications - If you use a differnent web browser (like Dolphin HD or Firefox), or a different SMS/MMS program (like Handcent or Chomp), then it is recommended that you remove the stock applications before flashing. This prevents conflicts, slowdown, memory usage, and the annoying popup where you have to constantly re-choose your default application. In these examples, you are looking for /system/app/browser.apk and mms.apk.
Add/Remove apps you don't want - Navigate to /system/app, and remove any APK files that you don't want. If you don't know what app it is, do NOT remove it
Modify Bootup Animation/Sound - Navigate to the /system/customize/resource/ folder. In there, you will see two files; VZW_bootanimation.zip an VZW_Droid.mp3. These files are the bootup animation and "Droid" noise. Simply delete the MP3 if you want a silent bootup. It really is that easy. Replace the ZIP File with another zipped animation (must give it the same name) to replace the animation with one of your own. NOTE: Make sure you verify compatibility. If unsure, don't do it.
Files needed for UOT Kitchen:
Download - framework-res.apk
Download - com.htc.resource.apk
Download - SystemUI.apk
The above files are needed for the UOT Kitchen. Ask questions in this thread if don't know how to use them. UOT Kitchen allows you to change visual elements of your phone's stock interface in a way that no launcher app ever could.
jaykresge, you gonna get anything going with this gingersense leak?
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
josh0426 said:
jaykresge, you gonna get anything going with this gingersense leak?
Click to expand...
Click to collapse
I'll mess with it.
tjrocks91 said:
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Need to have the stable release out before the test/beta releases
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
rosser725 said:
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Liberation is uploading right now, should be available in a few minutes. Enhanced is still cooking, might be another 30 minutes or so. As for the "cool idea," this is actually just a renamed update to an existing ROM. See below.
tincbtrar said:
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
Click to expand...
Click to collapse
I'm cooking Liberation Enhanced right now, then I'll immediately start playing with the leak. We've seen a few developers upload flashable versions already. I can't commit that I'll release anything on this leak at this point. Let me play with it some and then I'll comment on it.
Both 1.0 ROMs are up based on the November OTA. Currently toying with the leak, will update.
Re-cooking then uploading the beta for 2.00 based on today's Gingerbread leak. Use at your own risk.
I agree with tincbtrar.
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
jaykresge said:
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
Click to expand...
Click to collapse
Downloading now, Thanks.
I'm liking some of the changes. Reboot time (after initial flash) is insanely fast. HTC Car Panel now works in both portrait/landscape, however, most other apps still don't. Feels smoother than 2.2 (and I just did clean flashes of all of my ROMs, it's definitely smoother).
Let me know what you think, but so far, feels good for a beta. I'll make it my daily driver for the next few days and see what happens.
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
BrettApple said:
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Click to expand...
Click to collapse
Just an FYI, it works fine with the existing radio. I won't be pushing users to update radio/hboot/etc. until the official release comes out.
tincbtrar said:
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Click to expand...
Click to collapse
I'm going to work on getting an Evo camera working for it. As for flashing Liberation, it's just Nothing Special under a new name (and the minor change of Car Home switched for Car Panel). All of the mods you used on NS will work here
cabjmb said:
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes.
AGPS Patch Incredible S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
veitograf said:
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
Click to expand...
Click to collapse
Did you try v1.3? It's at the top of the post under "Downloads".
crypted said:
Did you try v1.3? It's at the top of the post under "Downloads".
Click to expand...
Click to collapse
1.3 works like a charm
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
baste07 said:
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
Click to expand...
Click to collapse
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
crypted said:
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
Click to expand...
Click to collapse
thanks i'll try this out!
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
itandy said:
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
Click to expand...
Click to collapse
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
crypted said:
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
Click to expand...
Click to collapse
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
itandy said:
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
crypted said:
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
Click to expand...
Click to collapse
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
crypted said:
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
Click to expand...
Click to collapse
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
-------
Also,
In preparing for the next iteration of the GPS patch, I'm trying to get a better grasp of the suplrootcert's on various devices. So far I have Verisign and TMobile. If anyone would be willing to check their phone and let me know if they have a different one (via private message here on xda)that would be great!
You can find "suplrootcert" as a file in /etc/ just like where the gps.conf is located.
To see which you have, open it up as a text document. It will look like jibberish. But, the top portion will say a company name within the jibberish. If you don't see Verisign or Tmobile, I would like to get ahold of the one on your device!!!
crypted said:
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
Click to expand...
Click to collapse
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Sent from my HTC Incredible S using Tapatalk
itandy said:
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Click to expand...
Click to collapse
Did it work fine before the patch, though? Can you get a screenshot of GPS Status after running for about 2 minutes?
I'm sorry I can't quickly resolve your phones issue. I'm curious about its hardware and whether it was greatly stable beforehand, or what...
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
BWA80 said:
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
Click to expand...
Click to collapse
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
crypted said:
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
Click to expand...
Click to collapse
HEHEHE, good one!
Actually anything above 0 celsius is summer for us, how sad is that..
No case, my baby is totally naked. wifi not enabled. I´ll do the GPS status sit and run tomorrow, too dark now and the wolves are howling.
Will report back.
Thanks!!
Sorry if this issue is not important to you^^
-------------------------------
Is it possible to use Google Maps with Samsung Chinese TTS when Traditional Chinese is chosen?
-------------------------------
I'm using Google Maps 6.9.0 [Ownhere Mod + World Navigation Activated], and it works!
At the same time, Samsung Chinese TTS also does it job just fine.
But when I try to activate Chinese vocal navigation with Google Maps, it says nothing but a sound effect, ding-ding to be precise.
The only workaround so far is changing Language on the setting panel of Language and Input to Simplified Chinese from Traditional Chinese, which I am using.
BIIIIIIIIIIIIIIIIIIIIG thanks for your kind help!
===========================
[update]
After the same question was put on XDA and Mobile 01, probably the most popular 3G forum in Taiwan, the solution was provided within 24 hours.
BIG thanks to patrickkk, a real dev, from Mobile 01 in Taiwan!
Not only a zip for flash but also detailed instructions for modifying the apk are provided.
Check it out here >> http://www.mobile01.com/topicdetail....&t=2856946&p=1
Though cwm, simply flashing a tweaked samsung tts apk makes everything perfect!
del
Please post on the right thread if you want to get help and avoid being stoned. Develepment is for "development" we have a q&a section for your question.
Sent from my GT-N7000 using xda premium
Sgs -> gtab 7" (overcome 4.0) -> sgy (stock) + sgn (kingdroid v3 + S3 mod + franco ics kernel r5)
Ha!! I posted the question without checking if i was putting it on the correct place^^"
Anyway, after the same question was put on XDA and Mobile 01, probably the most popular 3G forum in Taiwan, the solution was provided within 24 hours.
BIG thanks to patrickkk, a real dev, from Taiwan!
Not only a zip for flash but also detailed instructions for modifying the apk are provided.
Check it out here >> http://www.mobile01.com/topicdetail.php?f=568&t=2856946&p=1
Though cwm, simply flashing a tweaked samsung tts apk makes everything perfect!
After long testing I can confirm that process /system/bin/kiesexe.
Description:
All Samsung ROM's and most of custom based on stock including file
/system/bin/kiesexe.
This is system service needed for KIES functionality, that started at system startup before other Android staff loaded. Sometimes it execute Linux shell for some reason.
After execution completed proper cleanup not performed and zombie processes remains in memory.
It happens even if you newer use KIES. It may happen if you've other KIES related staff removed from your firmware.
Memory, used by it's child processed can't be released by Android task killers and you may have you phone running low of memory after some more or less long uptime.
It seems to be, that shell execution may be triggered by network activity. Since no authentication performed, I suspect a back door in this process that can give to intruder complete control on your phone.
Provided script will remove eXecute permissions from the file, so it will not be launched.
Side effect: You cant use KIES after tis script installed.
Notes:
1. Flashing new ROM, or applying some patches, or any kind of "Fix Permissions" will remove the mod, and you should re-install it.
2. You need not this mod for any kind of AOSP/AOKP/CM based ROM's.
3. This mod - a workaround for small but nasty bug in Samsung software. It definitely not best way to fix this issue. real fix should come from Samsung. Please report it and I'll be happy ro close this thread when real fix will be released.
Wrong section. Dev close please.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Why wrong ?
This is not question, this is real fix.
It works.
If I'll provide CWM enabler/disabler - will it be wrong section ?
I can tell more:
1. Most of custom ROM authors provide option not to include Kies, but leave this file inside and it really eats 5-50 M in a hour that can't be released by Android task killers.
2. Activity of this process with USB disconnected tel me that it listening network, so it consumes battery power and there is danger of unauthorized access to your data.
If you don't believe:
Let phone run several hours with Wi-Fi or 3g connected.
Open task manager, see amount of used RAM.
Then kill kiesexe process and lok at used RAM again.
You will be surprised.
Also you can see many zombie processes named [sh] (sometimes hundreds of) in process list if kiesexe is running.
File erased [just tu be sure], but still my MIUI takes over 700MB after reboot. Looks like problem with ROM itself :-/
10x
Thx for your research!
Off topic : Who is using Kies?
mietekxxx said:
File erased [just tu be sure], but still my MIUI takes over 700MB after reboot. Looks like problem with ROM itself :-/
Click to expand...
Click to collapse
1. I'm sure, you will notice that you phone do not freeze any more after long system uptime with stock ROM, but I'm not sure, tat MIUI also has this bug.
2. Did you kill the process ? It may remain running also after file deleted.
d8389 said:
2. Did you kill the process ? It may remain running also after file deleted.
Click to expand...
Click to collapse
Yeah, I reboot phone.
It don't take much RAM after reboot, but it cause low RAM issues after some uptime. Probably new siyah beta will help you.
Currently I'm running this kernel with kies enabled and with 100m of zram + 256m on classic swap. I'll try to run it as long as possible.
Currently I've 200+ M free after 4 hours. I've lot of apps and widgets and usually my free RAM 100-140 M with kiesexe off and I can't run GPG navigator after 24 hours uptime if kiesexe running unless I kill it from terminal or adb.
This is main reason for not releasing cwm scripts hat will disable and re-enable it. I can't test them now.
Just installed this. I will report again after awhile. Let's what happens. Rom using wanamlite 2.0
Sent from my GT-I9300 using xda premium
m3dd0g said:
Wrong section. Dev close please.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
Too early to judge I guess.
Op: nice work, thanks for sharing!
Sent from my GT-I9300 using xda premium
Actually i think it is the right section. This also is not a guide. It is a ready cwm flashable fix, therefore dev section.
Sent from my GT-I9300 using xda premium
This cleared about 100mb or ram on wanamlite 2. I've changed the file permissions from Root Explorer then killed the process using Android Terminal Emulator. I'm on SiyahKernel S3-v1.5beta4.
Thanks for your research!
Just flash zip in cwm and reboot?
Is there anything else that breaks? Or does it just break Kies?
Sent from my GT-I9300 using Tapatalk 2
With this work on the jelly bean ROMs as well?
ceoesquad said:
With this work on the jelly bean ROMs as well?
Click to expand...
Click to collapse
umm the current JB roms probably dont have this file as they are AOSP and kies is a samsung thing
d8389 said:
Why wrong ?
This is not question, this is real fix.
It works.
If I'll provide CWM enabler/disabler - will it be wrong section ?
I can tell more:
1. Most of custom ROM authors provide option not to include Kies, but leave this file inside and it really eats 5-50 M in a hour that can't be released by Android task killers.
2. Activity of this process with USB disconnected tel me that it listening network, so it consumes battery power and there is danger of unauthorized access to your data.
If you don't believe:
Let phone run several hours with Wi-Fi or 3g connected.
Open task manager, see amount of used RAM.
Then kill kiesexe process and lok at used RAM again.
You will be surprised.
Also you can see many zombie processes named [sh] (sometimes hundreds of) in process list if kiesexe is running.
Click to expand...
Click to collapse
youve done great cleared over 100 mb doing this thanks heaps
d8389 said:
I can't understand, why Samsung still have not fix this stupid bug.
Click to expand...
Click to collapse
'cause Samsung can't program Kies-related stuff for ****. They insist to plod on with the .Net-based ****hole (on the computer side - I used computers that only had 2GB RAM for years, so I'm a little cranky when it comes to memory usage. [It was only a few months ago that I finally got a computer with an acceptable amount of RAM.]) Huawei, on the other hand, got it right with their HiSuite - a nice, relatively light Qt-based solution that has always been stable for me.
It was fixed, but see this: http://sh4ka.fr/android/galaxys3/from_0perm_to_INSTALL_PACKAGES_on_galaxy_S3.html
You can also remove it from ramdisk:
init.rc
service KIES-daemon /system/bin/kiesexe
class main
user root
group system radio inet net_raw
Are the zip files working via cwm
Sent from my GT-I9300 using Tapatalk 2
Well I got permission from zarboz to use this kernel, but having problems with WiFi. Tried with sun_dream sense 5. Tried wiping cache and factory reset still same problem going to try on stock. Well tried on medusa Rom same problem. Must be in kernel. Any help would be appreciated and welcomed.
https://www.dropbox.com/s/rzsbypd1ft758ir/Myst_4.2.zip?dl=0
Sent from my HTC first using XDA Free mobile app
The more info we can gather the easier it will be to find a fix for this. So if someone can test this out and give us some feedback, thank you very much .
Is there any other kernel for this phone that has WiFi working? Maybe I could try to get the WiFi piece from the good one and put it into this one.
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
after flashing this kernel, could you do this for me:
1. Flash UKM http://forum.xda-developers.com/android/software/zip-synapse-script-universal-kernel-t2736986
2. Install "synapse" (its an app), reboot
3. Go into synapse, you should now be able to configure the kernel (if you still cant, refer to the link above).
4. Post screenshots of EVERYTHING
5. Upload your build.prop (/system/)
i wish i had a first i could go through the file system myself.
Edit:
Hopefully stock android filesystems stay the same from version to version. im on 5.0 at the moment on my nexus but try some of these things too:
1: delete this folder /data/misc/wifi/ And /data/misc/dhcp and system/etc/wifi reboot. (try deleting 1, then reboot, then if it doesnt work, delete the first 2 folders, reboot, if that doesnt work, delete all 3. try different combos).
(and/or)
2: force stop Bluetooth Share (i think you can go to apps>all> and find it there. reboot
3: drain the battery to 0. like make sure the thing is DEAD and wont boot even into recovery. let it sit for some time. plug in your charger and turn it on at the same time.
here is some additional info. if you want to try this. go right a head!
jpsflores said:
Hello all!
I registered here so that i could share a possible solution to the stuck wifi problem. On my nexus the BT was also stuck most of the time.
Been having the problem for about two weeks and was about to do a clean install and, if the problem persisted, call Google support. Thing is, I had the feelling it was software related and that the hardware was ok.
I´m not sure if BT, Wifi and NFC use the same hardware but the fact was that wifi worked for a few days, BT for a few more and NFC was always functional.
I did some extensive research thru the web and it seemed that this problem was not nexus unique and seemed to be related with wpa_supplicant.conf or wpa_supplicant in the bin file.
On this page, mind you the text is pretty old and not entirely android related:
http:_//_blog.linuxconsulting.ro_/2010/04/porting-wifi-drivers-to-android._html (I can't post links yet so just copy past and remove spacing)
I found this little snippet that caught my attention:
Seems that you can add ap_scan=1 to your wpa_supplicant.conf depending on the drivers you have.
After some more research on the subject of ap_scan i found that:
It seems that addind ap_scan=1 imposes that wpa_supplicant.conf handles the scanning and AP selection. IF there's something wrong with the driver, and not with wpa_supplicant as i originaly thought, this could bypass the problem.
So I added ap_scan=1 just before the device identification lines in wpa_supplicant.conf, reeboted, and now the wifi and bluetooth toggle normaly. I've tried ap_scan=0 (the driver handles the scanning) and the problem returns, so ap_scan=1 does allow you to toggle the wifi and BT on.
I can't yet verify that the phone actually connects to a wireless network and has the same stability and range as before as I'm at work and there's no wireless here.
Therefore I ask for your help to verify this "fix" and thoughts on this.
Sorry if the post is a mess. Both english and programming aren´t my native languages...
My device is a Nexus 5 with stock 4.4.4 KitKat and root.
Greets.
---------- Post added at 10:29 AM ---------- Previous post was at 09:46 AM ----------
So, quick update:
Managed to find an wireless network around and connected to it. Some time later, no sure how much, the phone rebooted.
Some time after that the wifi and Bt were stuck again. Accessed wpa_supplicant.conf and deleted the new wireless network information. Rebooted and all was functional again.
Seems the fix is incomplete as any rewrite of the wpa_supplicant.conf reinduces the initial problematic behaviour...
____________________ Extra Update_______________________
Ok, so it seems that the wpa_supplicant.conf is suposed to have ap_scan=1 by default.
After boot and when I connect to a wifi network my file resets and shows without ap_scan=1 and instead of:
ctrl_interface=wlan0
its
ctrl_interface=data/misc/wifi/sockets
Wifi with a conf. like this never works. If I manualy "correct" the file and reboot, the wifi toogles on, but after a wifi connect gets busted up again.
by now I've done:
- copy wpa_supplicant (the bin file) from a stock 4.4.4
- Check file permissions for all wpa_supplicant files
- dirty flash the stock build (it's my original build so less harm done i guess)
- 2 Clean installs
- 6 factory resets
And the problem persists.
I've called google support and they are sending a new phone as we speak. Now I'm not sure if it's a software or hardware problem (maybe a combination of the two?) but I figured it would be better to reroll a device instead of trying to fix this one as this problem is cleary out of my league.
Thank you all!
Click to expand...
Click to collapse
Cannot download synapse playstore is incompatible ugh..
Sent from my HTC first using XDA Free mobile app
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
blafree64 said:
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Yeah all end correct. Try the steps I posted to fixing Wi-Fi hopefully it will work
BTW. Are you running android 4.4? I thought HTC first is only 4.1
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
blafree64 said:
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Is everything working?
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Alright.
If you need any more help let me know
I'll do my best