General FAQs

What is the HTC Developer Center?

The Developer Center provides a set of tools and resources for developers, including the HTC OpenSense SDK, sample code, technical documentation, tutorials, Kernel Source Code downloads, and the Unlock Bootloader web tool. New material and updates will be posted to the site over time, so be sure to check back with us frequently!

Why are Power saver and Extreme power saving mode both grayed out on my HTC One (M8)?

This happens when you turn on High performance mode under Developer options in Settings. High performance mode requires additional battery power to maximize CPU performance. In this mode, both the Power saver and Extreme power saving mode features won’t be available. If you want to use these features, turn off High performance mode.

Can a developer use Eclipse versions other than the recommended version in the Quick Start guide?

HTCDev has tested and verified the SDK using the latest Eclipse version. HTC recommends developers use the latest version of both the Android SDK and Eclipse to guarantee compatibility.

Do I need to have an Android SDK installed in my machine before installing HTC SDK?

Yes. The developer is expected to have a bare minimum Android SDK installation which can be downloaded from the Android developer site. Please see Android Basics for information on setting up your development environment and the necessary prerequisites.

Are there any HTC device skins available with the SDK?

When creating an AVD, the developer may select from numerous HTC devices in the skins drop-down options, otherwise the default skin will be used to launch the AVD.

Why do I have to log in multiple times when navigating throughout the site? Why does my request for the unlock code fail?

Our site requires a single IP authentication, and if you are behind a more complicated network that may alter your IP depending on loading, certain features may not work as intended. We suggest you connect to our site via a direction connection, such as via a home network. We are sorry about the inconvenience and thank you for your patience.

What are the minimum site specifications?

We recommend that this site be viewed in the latest versions of Internet Explorer, Firefox, Chrome and Safari on MacOS or Windows at a resolution of 1280 x 1024 pixels. Performance may vary with the use of other browsers, operating systems or display resolutions.

Why hasn’t HTC released the source code for some drivers?

HTC will release source code in accordance with any applicable open source license terms, i.e. GPL v2.0.  Other source codes, which are not required to be disclosed by the open source license terms, unfortunately cannot be disclosed by HTC as they may be proprietary to HTC or its licensor.

Why are drivers for exFAT (Extended File Allocation Table) missing from kernel source code?

The drivers are subject to non-GPL third party licensing terms and therefore are not included in the kernel

Why doesn’t the exFAT SD card work after loading modules built from this kernel source code onto my device?

exFAT driver code is not included in the kernel, the version numbers and singed signature of the exFAT module on the device and the modules built from the kernel do not match. exFAT module will also not work if developers modify any of the kernel data structures, types or functions that exFAT module uses.

What is CONFIG_MODVERSIONS, and what does it mean?

CONFIG_MODVERSIONS is a notion thought up to make people’s lives easier. In essence, what it is meant to achieve is that if you have a module, you can attempt to load that module into any kernel and be safe in the knowledge that it will fail to load if any of the kernel data structures, types or functions that the module uses have changed. If your kernel is not compiled with CONFIG_MODVERSIONS enabled, you will only be able to load modules that were compiled specifically for that kernel version and that were also compiled without MODVERSIONS enabled.

Why does my debug APK sometimes fail to install or run on my device and how to recover?

HTC devices with Lollipop 5.0.0 or 5.0.1 may experience this issue and we suggest retrying the installation step for workaround. HTC will prepare the solution to address the issue on Lollipop MR1.