Project

General

Profile

Forums » Devices evaluations »

HTC One X (endeavoru) and/or X+ (enrc2b)

Added by Linus Drumbler over 10 years ago

I'm suggesting two very similar devices in one thread.

  • Supported by CyanogenMod (http://wiki.cyanogenmod.org/w/Endeavoru_Info, http://wiki.cyanogenmod.org/w/Enrc2b_Info)
  • Installation is one of the trickier parts about these devices. The images themselves are flashed with recovery and the SDK, but the installation instructions for CyanogenMod (http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b) require the user to a) register on a certain website and b) use a file that may or may not be free (most likely not). However, I contacted Richard Stallman on this issue, and here's what he said: "I'd say it is a borderline case. It is not good that that program is needed. Once Replicant is installed, can you change it without those nonfree installers?" Since that is the case (I believe the file would be erased with the installation of Replicant), I think we are alright in this respect. We could even provide instruction on this.
  • The installation instructions are unclear, requiring the flashing of a certain non-free-image, so the kernel may or may not be signed. However, since both devices have their kernel source code available, I would conclude that custom kernels are possible on these devices.
  • Kernel sources available (https://github.com/cyanogenmod/android_kernel_htc_endeavoru, https://github.com/cyanogenmod/android_kernel_htc_enrc2b)
  • Network type is GSM for both devices.

One other, unofficial criterion: the platform for both devices is Nvidia Tegra 3. TargetsEvaluation mentions that newer versions than version 2 might be faster on Replicant; perhaps you should give that a try :).


Replies (4)

RE: HTC One X (endeavoru) and/or X+ (enrc2b) - Added by Linus Drumbler over 10 years ago

A freedom-related issue is that the battery of the X+ cannot be removed. I don't know if this makes it less of a target than its brother.

RE: HTC One X (endeavoru) and/or X+ (enrc2b) - Added by Linus Drumbler over 10 years ago

I may not own either of these devices, but I'll put my voice in as an interested party. These are high-end phones (some models have quad-core processors!) and Replicant needs to go beyond the Galaxy S3.

RE: HTC One X (endeavoru) and/or X+ (enrc2b) - Added by Paul Kocialkowski over 10 years ago

Usually, we get away with this by saying that the device must be ready to run CyanogenMod, so we don't have to provide these instructions ourselves. However, when the process is outrageous (for instance if it involves running a proprietary app on the host computer), we simply won't port to the device. In that case, it's a bit different, so we may still be interested in it.

I don't know if newer tegra platforms would be possible, but the very least I can say is that it requires many blobs, so a lot of work ahead and lots of missing hardware features, which is not very optimal.

RE: HTC One X (endeavoru) and/or X+ (enrc2b) - Added by Linus Drumbler over 10 years ago

You were right about "many blobs". See https://github.com/CyanogenMod/android_device_htc_endeavoru/blob/cm-10.2/proprietary-files.txt and https://github.com/CyanogenMod/android_device_htc_enrc2b/blob/cm-10.2/proprietary-files.txt.

Just look at that list for the X. Four hundred lines of blobs, nicely commented. Now, the actual number is probably not four hundred, but good grief. The Nexus 4 has 152, and you called that "too many" in TargetsEvaluation. (Surprisingly, the newer X+ has fewer.)

    (1-4/4)