[ROM][unofficial] HTC One X CyanogenMod 12.0 (updated 2015-02-28)

Search This thread

Thömy

Senior Member
Aug 24, 2010
666
2,388
Stuttgart
Where exactly do I execute these commands?
In a terminal as root (there is a Terminal Emulator app, not sure if it's pre-installed) or through ADB.

I added a new init.d file with the command for fast charge... charging is still painfully slow. Any pointers? Is anyone else having this issue on CM12 on HTC One X ?
I think selinux currently prevents the execution of the userinit script. Check if it's still the case if you execute the command manually.
 

der_Greggy

New member
Feb 24, 2015
1
0
Whats means "Breaks compatibility with all existing ROMs, recoveries and boot.imgs"

Hallo,

Was genau heißt "Breaks compatibility with all existing ROMs, recoveries and boot.imgs". Heißt das auch, dass auch, dass ich nichtmehr zurrück auf CM 11 komme (Nach Factory Reset) wie bisher und ich danach für immer auf CM 12 bleiben Muss?
---
Means "Breaks compatibility with all existing ROMs, recoveries and boot.imgs" that I can't go back, after Factory Reset to CM 11 and that I have to stay in CM 12 for ever?

Greetings from franconia,

der_Greggy
 

cserba

Senior Member
Feb 20, 2011
66
1
Želiezovce
can not mount /data and storage

Hey guys.
I am flashing my HTC One X to CM12. I was following these steps during the flashing:
*Read the official wiki
*Read known issues and FAQs
*DO A BACKUP
*Unlock your device via http://www.htcdev.com if you haven't done so already
*Read post #3 and flash a recovery supporting the new storage layout
*DO A DATA WIPE / FACTORY RESET

After i had done the twrp flashing (latest version for lolipop) and made the factory reset I am stucked with a problem that I can not flash the new CM 12 ROM. It tells me: unable to find partition for path...

Thank you for your help.
 
Last edited:

GrizCro

Member
Feb 22, 2015
27
5
Šibenik
I'm using this rom as daily driver for last two days without any problems. However, since this morning I'm suddenly not able to install any apps on the phone.

If I try to install or update app through play store, I get error - "Unknown error code during application install: "-504"". (The app downloads completely, installation starts and then error message pops up after few seconds.)

If I try to install app from other sources, I just get "App not installed". I tried to clear cache and data of play store, play services and services framework - same thing. Reboots didn't help either.

Any idea what could be causing this?
 
I'm using this rom as daily driver for last two days without any problems. However, since this morning I'm suddenly not able to install any apps on the phone.

If I try to install or update app through play store, I get error - "Unknown error code during application install: "-504"". (The app downloads completely, installation starts and then error message pops up after few seconds.)

If I try to install app from other sources, I just get "App not installed". I tried to clear cache and data of play store, play services and services framework - same thing. Reboots didn't help either.

Any idea what could be causing this?

Had this issue too with the first build by thomy. Clean install solved the problem. I`ve even tried different package installers etc.
 

Black Shadow

Member
May 31, 2009
27
9
Saint - Petersburg
I constantly receiving an error message
Code:
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
Multiple times per minute. The phone never sleeps, and the battery is discharged very quickly. Anybody know how to fix this?
 

Thömy

Senior Member
Aug 24, 2010
666
2,388
Stuttgart
Hallo,

Was genau heißt "Breaks compatibility with all existing ROMs, recoveries and boot.imgs". Heißt das auch, dass auch, dass ich nichtmehr zurrück auf CM 11 komme (Nach Factory Reset) wie bisher und ich danach für immer auf CM 12 bleiben Muss?
---
Means "Breaks compatibility with all existing ROMs, recoveries and boot.imgs" that I can't go back, after Factory Reset to CM 11 and that I have to stay in CM 12 for ever?

Greetings from franconia,

der_Greggy
Du kannst wieder zurück zu CM 11 / Sense. Was damit gemeint ist, dass man nicht ohne Weiteres bisher existierende (alte) Recoveries und custom kernels mit den neuen ROMs nutzen kann.

I constantly receiving an error message
Code:
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
D/PGPSDownloader.SocketServer( 2479): Trying to connect to MSL
E/PGPSDownloader.SocketServer( 2479): java.io.IOException: Connection refused
Multiple times per minute. The phone never sleeps, and the battery is discharged very quickly. Anybody know how to fix this?
Delete the PGPSDowloader app from /system/app or /system/priv-app. Which build are you running? I thought I included a fix for that.
 
  • Like
Reactions: Black Shadow

Thömy

Senior Member
Aug 24, 2010
666
2,388
Stuttgart
Thanks, Thömy. I compiled cm-12 from sources. Cyanogenmod sources does not contains all of your patches?
No. There are some quick and dirty fixes I haven't merged or even uploaded to Gerrit.
In this particular case I had to replace proprietary GPS binaries and libraries with ones from another device. It makes the problem go away but I don't know if that causes other problems. I never really checked if that agps stuff really works. In theory one should see a difference in the time it takes to acquire a GPS fix.
 

Black Shadow

Member
May 31, 2009
27
9
Saint - Petersburg
No. There are some quick and dirty fixes I haven't merged or even uploaded to Gerrit.
In this particular case I had to replace proprietary GPS binaries and libraries with ones from another device. It makes the problem go away but I don't know if that causes other problems. I never really checked if that agps stuff really works. In theory one should see a difference in the time it takes to acquire a GPS fix.
I understand, thank you.
 

teemo

Senior Member
Nov 18, 2007
2,430
2,315
Kolding
No. There are some quick and dirty fixes I haven't merged or even uploaded to Gerrit.
In this particular case I had to replace proprietary GPS binaries and libraries with ones from another device. It makes the problem go away but I don't know if that causes other problems. I never really checked if that agps stuff really works. In theory one should see a difference in the time it takes to acquire a GPS fix.

I disabled pgpsdownloader this morning and had no problems with gps. But testing from a clean install is probably needed also.
 

Thömy

Senior Member
Aug 24, 2010
666
2,388
Stuttgart
I disabled pgpsdownloader this morning and had no problems with gps. But testing from a clean install is probably needed also.
The PGPSDownloader is only there to download some data that gets send to the nav services. The data is cached somewhere on the /data partition. Look for /data/rxn or something. I don't know why the app constantly checks the connection to the service and to the internet. Probably to spy on us :D.
 

Thömy

Senior Member
Aug 24, 2010
666
2,388
Stuttgart
No. There are some quick and dirty fixes I haven't merged or even uploaded to Gerrit.
In this particular case I had to replace proprietary GPS binaries and libraries with ones from another device. It makes the problem go away but I don't know if that causes other problems. I never really checked if that agps stuff really works. In theory one should see a difference in the time it takes to acquire a GPS fix.

I understand, thank you.

I disabled pgpsdownloader this morning and had no problems with gps. But testing from a clean install is probably needed also.

https://github.com/thoemy/proprietary_vendor_htc/commit/6a4461859fd5960ab4d730dd63ea5aa834690699
http://review.cyanogenmod.org/#/c/89826/
 

Top Liked Posts

  • There are no posts matching your filters.
  • 119
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
    Code:
    #include 
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */
    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


    IMPORTANT INFORMATIONS

    We will not support users and answer questions from users which:
    • are running a custom kernel
    • have flashed mods
    • modified system files
    • didn't follow our instructions word by word
    • are unfriendly

    WIKI

    Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Endeavoru_Info

    INSTRUCTIONS

    First time installing CyanogenMod 12.0 to your HTC One X (GSM), or coming from another ROM:
    • Read the official wiki
    • Read known issues and FAQs
    • DO A BACKUP
    • Unlock your device via http://www.htcdev.com if you haven't done so already
    • Read post #3 and flash a recovery supporting the new storage layout
    • DO A DATA WIPE / FACTORY RESET
    • Copy GApps and the CM 12.0 zip to your SD card
    • Boot into Recovery
    • Flash the CM 12.0 zip from SD card
    • Flash GApps for Lollipop from SD card
    • Flash the boot.img included in the CM 12.0 zip via Fastboot
    • Reboot (be patient, "optimizing apps" takes a while)
    • Don't restore system data using Titanium Backup!
    • Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!

    Upgrading from earlier version of CyanogenMod 12.0:
    • If you're coming from a pre-/data/media build read post #3
    • Copy the CM 12.0 zip to your SD card
    • Boot into Recovery
    • DO A BACKUP
    • Flash the CM 12.0 zip from SD card
    • Optionally flash the most recent GApps for Lollipop if you encounter problems
    • Flash the boot.img included in the CM 12.0 zip via Fastboot if necessary. If in doubt, flash it.
    • Reboot (be patient, "optimizing apps" takes a while)

    Upgrading from CyanogenMod 11.0: (untested and unsupported, see FAQ below)
    • Read the known issues and FAQs
    • DO A BACKUP
    • Read post #3 and flash a recovery supporting the new storage layout
    • Copy GApps and CM 12.0 ZIP to your SDCard
    • Boot into Recovery
    • Flash the CM 12.0 zip from SD card
    • Flash GApps for Lollipop from SD card
    • Flash the boot.img included in the CM 12.0 zip via Fastboot
    • Reboot (be patient, "optimizing apps" takes a while)

    DOWNLOADS

    Recovery: See post #3
    CM12.0 unofficial testing builds:

    Old layout:

    New Layout (read post #3):

    CM12.0 official stable builds: Not available
    CM12.0 official nightly builds: Not available
    Google Apps: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip

    CHANGELOG

    http://github.com/CyanogenMod & http://www.cmxlog.com/12/#

    2015-02-28
    • Synced with CM
    • Fixed an issue with some SIM cards
    • Fixed USB OTG
    • Fixed broken Wi-Fi after a soft reboot
    • Device encryption should work (make a backup first!)
    • Fixed Rezound Proximity Calibrator

    2015-02-14
    Uses new storage layout. Read post #3. New boot.img and a complete wipe is required!
    • Synced with CM
    • Maybe working Google Play Movies

    2015-02-03
    Fixed boot.img is not required but recommended.
    • Synced with CM
    • UMS situation unchanged from 2015-01-11
    • Included a fix to allow moving Apps to SD
    • Allow toggling NVIDIA smartdimmer under Settings -> Display -> Advanced settings -> Adaptive backlight (with fixed boot.img)
    • Allow toggling sweep2wake under Settings -> Display -> Advanced settings -> Double-tap to wake (with fixed boot.img)
    • Allow changing the vibrator intensity under Settings -> Sound & notification -> Other sounds -> Vibrator intensity (with fixed boot.img)
    2015-01-11
    • Synced with CM
    • Default to MTP for new installations (set it to MTP manually in the storage settings when coming from an older build)
    • Revert some custom UMS related fixes which restores the stupid pre 2015-01-02 auto-mount behavior. DON'T UPDATE IF YOU WANT TO USE UMS
    • Enable multi-user UI (and guest mode)
    • Fix setting maximum CPU frequency
    • Fix signal strength
    2015-01-02
    • Synced with CM
    • Fixed SD card / UMS mounting issues
    • Fixed tethering
    • Button backlight is now adjustable
    • Long press action for "Recents button" now available (back is still missing)
    • USB connection mode can now be set to MTP
    2014-12-17
    • First testing build

    KNOWN ISSUES

    Roughly in order of seriousness.

    • Outgoing calls & mobile data might be problematic
      • There is currently an issue with some SIM cards (MultiSim?) that don't work properly. You are able to receive calls and SMS messages but you cannot make calls or send SMS and mobile data does not work. The cause has been identified: http://review.cyanogenmod.org/#/c/88932/
    • No mobile data after disabling Wi-Fi
      • IP routes are not updated properly (check if "ip route")
      • Disable and enable mobile data to work around this
    • Recent App switcher is broken in landscape and may cause reboots.
      • Workaround: Select "Disable HW overlays" in the Developer options.
    • Using NFC with the Smart Lock feature causes a deadlock.
    • No device encryption possible.
    • No P2P/Wi-fi Direct.
    • Battery stats list Wi-Fi as always turned on even though it was disabled.
    • Audio may be problematic with MHL.
    • Sense 5 camera features not available (no burst, no zero-shutter-lag, picture quality seems to be worse).
    • Docking stations are not properly supported
      • Dock speakers do not work
      • Select "Disable HW overlays" in the Developer options to avoid crashes
      • Dock drains the battery
    • Proximity sensor issues (screen stays black after call, hardware issue, it may not affect you).
    • SD card might not be available or might be always shown as shared.
      • Workaround: unplug the phone from your PC.
    • Moving Apps to SD is broken
    • Tethering seems the broken
    • No MTP
    • Mobile signal display is incorrect.
    • Unable to change the maximum CPU frequency through the settings.

    FAQ
    • Can I dirty flash coming from CM 11.0?
      • It should work.
    • Do I need to update the recovery?
      • Please read post #3.
    • Where are the Sweep2Wake, Button Backlight Notifications and Fast Charge Settings?
      • Not accessible anymore from the settings. The functionality is still in the kernel. See second post for details.
    • When do the nightlies start? When do upload the next version? When do you fix XYZ?
      • I don't know.
    • Device not recognized in Windows (Recovery, UMS, MTP)
    • Xposed?
      • No.

    XDA:DevDB Information
    CyanogenMod 12.0, ROM for the HTC One X

    Contributors
    Thömy
    Source Code: https://github.com/CyanogenMod/

    ROM OS Version: 5.0.x Lollipop
    ROM Kernel: Linux 3.1.x
    Based On: AOSP

    Version Information
    Status: Testing

    Created 2014-12-17
    Last Updated 2015-02-28
    75
    That would be perfect. Would there be anything negative if we change layouts?
    I've written this some time ago: https://docs.google.com/document/d/18vQHROvkJIvrrfGV95EVcwbeWHU5rPwhwN4t3qebGk0/edit?usp=sharing

    I would like to switch. The problem is the confusion it can cause. All recoveries and ROMs that exist will become incompatible. If you have problems then there is no easy way to go back.
    38
    Here are instructions to enable or disable some features that were previously in the advanced settings menu. Currently untested with Lollipop!

    Button Backlight Notifications (enabled by default)

    Button backlight notifications are enabled/disabled by settings write permissions on a special file. To disable them remove the write permission for the sysfs file with
    Code:
    chmod 444 /sys/class/leds/button-backlight/slow_blink
    Only execute it while the lights are not currently blinking.

    The newest kernel also contains the ability to limit to the notification brightness. Do
    Code:
    echo 1 > /sys/class/leds/button-backlight/slow_blink_brightness_limit
    to limit the brightness to your normal button backlight brightness (which you can adjust in the settings).

    Fast Charge (disabled by default)

    Fast charging is disabled by default and can be enabled with
    Code:
    echo 1 > /sys/devices/platform/htc_battery/fast_charge

    Sweep2Wake (disabled by default)

    Code:
    # Enable s2w
    echo 1 > /sys/android_touch/sweep2wake
    # Adjust the needed swipe length. 325 for one button (default), 500 for two buttons and 850 for three buttons
    echo 500 > /sys/android_touch/s2w_min_distance
    # Disable direction independent behaviour
    echo 0 > /sys/android_touch/s2w_allow_stroke

    Nvidia SmartDimmer (disabled by default)

    Now called "Adaptive backlight". Setting was moved to the "Display & LED" menu.


    All settings where you manually have to execute a command are not persisted between reboots. You can use a third party app that supports toggling the settings or you can put the commands into /data/local/userinit.sh to apply them at boot.
    37
    The New Storage Layout

    To combat the space problems on Lollipop due to ART builds will be switched to the /data/media storage layout that is commonly used with newer Android devices.
    The new partition layout will change our internal SD card be the /data partition. The internal SD card will also be located in this partition under /data/media. This means the 25GB can now be distributed freely between Apps, Data, Music, Picutres, Dalvik cache, ... that were previously on separate partitions. Moving apps to SD is unnecessary now.

    The transition to the new layout requires a complete wipe including the SD card contents.

    Advantages
    • Free disk space problems are largely gone because the sdcard and /data share the same place
    • Properly supporting UMS and supporting moving Apps to SD is getting harder and harder. This change will make both unnecessary

    Disadvantages
    • 2GB (size of the old /data partition) are “lost”
    • Breaks compatibility with all existing ROMs, recoveries and boot.imgs
    • Hopping between Sense and CM based ROMs will be nearly impossible
    • No more UMS, only MTP

    Downloads
    Recoveries using the old storage layout.

    Recoveries using the new storage layout
    TWRP 2.8.4.3 (by @teemo, @Thunder07)

    Migration

    Basic steps for switching to the new storage layout.
    1. Flash a recovery using the new layout
    2. Reboot to new recovery
    3. Format /data (Wipe -> Format Data in TWRP)
    4. Flash ROM (don't forget the boot.img)

    SD Card Data Migration

    This guide uses TWRP 2.8.4.x to convert your phone without losing data.
    1. Boot into the TWRP recovery supporting the old layout
    2. Make a backup (only /data needed)
    3. Copy everything (including hidden folders) from the SD card to your pc
      • You can use UMS or MTP
      • This will include the backup
    4. Reboot to fastboot and flash the new TWRP recovery using the new layout
    5. Flash the boot.img from the ROM you are using
    6. Reboot to new recovery
    7. Format /data (Wipe -> Format Data)
    8. Go back to Mount and enable MTP if it is disabled
    9. Reboot the recovery
    10. Restore your SD card backup to the Internal SD card
      • Use the “Internal Storage” device
      • Execute “adb shell chown -R media_rw:media_rw /data/media/0/” to fix the permissions
    11. Restore your /data backup from the SD card
      • If you don’t see any backups then you might have to move /data/media/0/TWRP to /data/media/TWRP manually
    12. Flash the new ROM
      • adb push and flash it or use adb sideload, it’s your choice

    More Information

    You'll find more information in the New Storage Layout for HOX Endeavoru thread by @teemo and in the New Storage Layout document by myself
    30
    New build available

    ****, missed the 2015-02-03 (GMT +2) by a couple of minutes. So here's the new and already outdated build :)

    2015-02-03
    Fixed boot.img is not required but recommended.
    • Synced with CM
    • UMS situation unchanged from 2015-01-11
    • Included a fix to allow moving Apps to SD
    • Allow toggling NVIDIA smartdimmer under Settings -> Display -> Advanced settings -> Adaptive backlight (with fixed boot.img)
    • Allow toggling sweep2wake under Settings -> Display -> Advanced settings -> Double-tap to wake (with fixed boot.img)
    • Allow changing the vibrator intensity under Settings -> Sound & notification -> Other sounds -> Vibrator intensity (with fixed boot.img)