Users went sad, when they heard the news that no official Jelly Bean will be released for the HTC Wildfire S. But thanks to other developers to develop CM 10.1 ROM. As in the title i have CyanogenMod-7.2.0-RC3-marvel-UNOFFICIAL-signed and after installing a few gapps i still can't get it to work. HTC Wildfire S Custom ROM Videos, Mobile Phone Tips & Tricks, Smartphones, Mobiles, Tablets. How to S-Off and Root the HTC Desire S, Sensation, Wildfire, Evo, Flyer HD - A step-by-step tutorial. How to install jelly bean on htc. HTC Wildfire s android(version) 2.3.7 with Cyanogenmod 7.2(ROM) HTC Wildfire. Have a ROM you want to share? Submit it and we'll add it to the site. ROM Name: Unofficial Cyanogenmod 7.2.0 ROM Created By: alquez Device: HTC Wildfire S.

As explained in my HTC Wildfire phone is now running version. The phone is pretty snappy with this image. I have not even felt the need for 'Google Apps' except for those parts that are connected with Google Maps (primarily NetworkLocator and Maps but also some support files for these). However, after installing Maps, I noticed that it was not able to get a tight fix on my location. (Note that Maps also gets a 'loose' fix by getting the co-ordinates of the nearest cell tower using the NetworkLocator.) Searching the web turns up thousands of 'GPS fix' therapies from all kinds of places. In, I had been wary of 'brick'ing my phone.

Now that it is working so well, I am doubly so! Hence, any solution which seemed to be reversible was acceptable and those which were not, were not.

Solutions that involved software changes alone would appear to be reversible. Hence, I tried: • Making changes to /system/etc/gps.conf, such as putting in in.pool.ntp.org in place of a European NTP server, or removing the SUPL entries etc. (All these changes were made after making a backup of this file and noting its exact permissions of course!) • Installing the GPSStatus application for Android and using it to reset the GPS internal state and download a-GPS data from the net. • Re-installing the earlier HTC 'stock' version of Android from backup, then reset-ting GPS internal state and finally booting back to Cyanogenmod 7.2.0 • Powering down, removing and re-inserting the battery. Clearing the cache from recovery.

All of these resulted in the following experience: • Immediately after cold-start (power-off, battery removal and re-insert and reboot), the GPS fix would be done in seconds. • About a minute or so later this GPS fix would be lost. • In a completely un-predictable way, the GPS fix would be re-gained at different times and places only to be lost in a minute or so again! One solution suggested in various places was to re-flash the radio. However, given the equally large number of warnings about 'brick'ed phones due to radio flashing, I was unwilling to give it a go. Moreover, the current radio on the phone is '13.55.55.24H_3.35.20.10' which appears to be the latest (and last!) version for this model.

Finally, I came across (see the fourth entry under Modifications to the System) that the file /system/lib/libgps.so from an earlier build (Froyo?) would fix the problem. Now, the file /system/lib/libgps.so on Cyanogenmod 7. Echo Sound System Software For Pc. 2.0 is actually the same as that on the HTC stock image that was backed-up from my phone. So, I was a bit disbelieving, but the change was easy and reversible, so why not? So I downloaded the by following a link on the same page and extracted the 96Kb file (from a 70Mb download;-)).

I then installed this file in place of the default /system/lib/libgps.so. Reboot the phone and GPS is working stably for 10 minutes! Go indoors for 5 minutes come back out and its back again! Now a hacker cannot just let this go! So what would happen if I put back the CM-7.2.0 version of /system/lib/libgps. Seagate Disc Manager Tool on this page. so? Surprisingly, the GPS continued to be stable! Perhaps there was something in the volatile memory, so do a cold-restart (power-off, re-insert battery and boot).