egzthunder1 · Oct 18, 2012 at 05:00 pm

Victory – HTC Releases Closed Source WiFi Drivers for HTC Amaze 4G!

Manufacturers and developers have a long standing love/hate relationship that has kept the fragile ecosystem where we spend most of our free time intact. The dance beat is somewhat the same across all brands and, for the most part, all devices as well. Most manufacturers out there are held against certain standards (either due to their own internal procedures and codes or due to contractual obligations with carriers) that force them to do certain things on the devices they make that keep most of us away from exploiting them and unlocking their full potential. This comes in the form of locking of bootloaders, pseudo-impossible to crack signature verifications, and secretive documentation that more often than not, has a tendency to foil the efforts of people with the required skills to fix the inevitable issues that arise on every device.

The HTC Amaze 4G was a device that came out about a year and change ago that fell under some of these categories. One of the most crucial ones was the fact that the device’s WiFi drivers were out of reach of our developers. While the wlan TI drivers are part of the kernel (which is GPL licensed), there are certain parts of it that are normally not licensed under this particular model, and this driver was the case. The missing code gave most developers on the device headaches simply because without this code, WiFi on custom ROMs (and even stock ones) was lousy (if functional at all). Because of this and all the issues generated from it, a petition was started about 7 months ago by XDA member aj_2423. The petition essentially asked HTC to release the sources for the drivers so that devs could work on them, fixing the remaining bugs (after thousands of hours of reverse engineering). However, the petition, which reached over 500 signatures, seemed to have fallen on deaf ears.

Just today, HTC Global Online Communications Manager Jeff Gordon told us that after lots of deliberation and going back and forth with TI, both companies had agreed that the required sources could be released to the public. HTC had gone rather silent as of late in the developer world, as many people were becoming increasingly dissatisfied with the lack of cooperation with the dev community, despite their continued promises. It seems to be that even though the company was falling out of grace with devs, they are beginning to try and renew their efforts by showing signs that they are still trying to get us on their side.

Well, HTC, you have made the right choice. Developers may only represent a small chunk of your overall user base, but you must understand that we (devs, hobbyists, and enthusiasts) tend to have very large spheres of influence. And in this very technological world of ours, it is a very important thing to have influential, indirect sales people, boasting the glory and overall awesomeness of your products. So, while our numbers may be small on a first impression, we are legion! It is this writer’s sincere hope that during your internal discussions to release these docs, the idea and concept of better, faster support for the developer scene was a factor being discussed, because this could easily sway a LOT of people over the manufacturer fence once again.

Once again, this is a great day for renewd relationships, particularly between developers and HTC. Keep up the good work, guys. We’ve missed you!

You can find the original petition in this thread and the sources by going over to HTCDev.

Want something published in the Portal? Contact any News Writer.

[Thanks Jeff for the tip and the great news!]

Note from the author: The article has been corrected to reflect the original author of the petition.


_________
Want something on the XDA Portal? Send us a tip!
Emil Kako · Jan 31, 2015 at 02:59 pm · 2 comments

Do You Prefer Physical or on Screen Buttons?

More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.

DISCUSS
Pulser_G2 · Jan 31, 2015 at 02:08 pm · no comments

New AOSP Branch Details Potential Build System Upgrades?

While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...

XDA NEWS
GermainZ · Jan 30, 2015 at 09:29 pm · 1 comment

Send Links to Any Nearby Device with CaastMe

There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...

XDA NEWS