[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL

Search This thread

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
CyanogenMod 10 is a free, community built distribution of Android 4.2.2 (Jelly Bean) which greatly extends the capabilities of your phone.

This is the official Nightly Build of CM10.1 for the AT&T HTC One X / HTC One XL.

To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
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.
 */

Installation Instructions (These are all required)
  1. S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard)
  2. Update to 3.18 RUU
  3. Flash a custom recovery (TWRP/CWM)
  4. Download latest Nightly
  5. Download and flash GAPPS

Nightlies return! Keep an eye on http://get.cm/?device=evita

List all Questions and Off-Topic discussions here

Changelog

Huge thanks:
intervigil, xkonni, toastcfh, deck and rohan32 - Great team to work with for the HTC MSM8960 device family.
 
Last edited:

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
Issue Reporting
  • Report device specific bugs to the Issues List. Please make sure to mark the issue with the Label "Milestone-CM10.1" so we can keep versions of CM issues separate.
  • Report CyanogenMod specific bugs to CyanogenMod's Jira Tracker.

NOTE:
Do not expect support if you have issues after you:
  • Use applications like CyanDelta
  • Restore data from Titanium Backup
  • Flash custom kernels
  • Use random flashable mods on top of CyanogenMod (except Google Apps)
Those things alter cyanogenmod and no one can expect me to support add-ons / random apps / etc. along with keeping our device maintained. Please keep this in mind. If you have an issue, remove all mods, remove all custom kernels, flash the kernel that comes with the cm.zip. At that point, please reply with issues.

FAQs:
* Q: Why don't i have Reboot -> Recovery/Bootloader any more?
* A: Read this

* Q: I'm having Google Play Music Issues! What do I do?
* A: Go to Settings -> Apps -> All. Disable Apollo, reboot your device, and then clear app data in Play Music. See this issue for details.

Screenshot_2012-12-25-12-29-37.png
Screenshot_2012-12-25-12-30-50.png
 
Last edited:

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
How to gather helpful data for troubleshooting

Pre-requisites:
  • ADB setup and minor knowledge on how to use it. (See here if you do not have such knowledge)
  • Have an open command prompt or terminal window.

How to obtain a full logcat
Code:
adb shell
su
logcat > /sdcard/logcat.txt
exit
exit
adb pull /sdcard/logcat.txt

How to obtain a targeted logcat for a particular issue
Code:
adb logcat > logcat.txt
  • Immediately reproduce the issue
  • CTRL + C out of the running logcat.

How to obtain a dmesg (helpful for catching kernel issues on a running build)
Code:
adb shell
su
dmesg > /sdcard/dmesg.txt
exit
exit
adb pull /sdcard/dmesg.txt

How to obtain a last_kmsg (helpful for catching kernel issues from last kernel boot-up such as bootloops)
Code:
adb shell
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
 
Last edited:

inphamous36

Senior Member
Aug 8, 2012
702
230
Baltimore
Have been using CM10.1 on my Galaxy Tab 2 and it's been awesome. Can't wait to try this out

Sent from my faster than Chuck Norris, One XL
 

Mike724

Senior Member
Jul 8, 2012
139
44
I love you so much h8rift. I'm going to flash this immediately. Happy holidays! :)

Update: It runs! everything is looking great at the moment
I'm on hboot 1.09 and I did the following:
- Factory reset
- Wiped system (redundant?)
- Wiped cache
- Wiped dalvik cache
- Installed cm10.1
- Installed 4.2 gapps
- Rebooted
(in that order)

Issues noticed so far:
- Google Now (specifically the voice search aspect) crashes -------- FIXED
- CRT animation is SUPER fast (I'm not sure if this is a bug or how it is supposed to be) -------- Not a bug
- One time when turning off the screen, the screen displayed a tan-ish color (I haven't been able to reproduce this though) -------- Nothing wrong
That is all for now, I would post this on the issue tracker, like you stated--but I want to see if it's just me having these issues or if it's everyone.

Thank you for all your hard work on this, h8rift and the rest of the team.
 
Last edited:
  • Like
Reactions: ragesoss
D

Deleted member 3452239

Guest
Thanks h8, let's hope s-off plays through as well. Amazing Christmas presents

# su
 

ps3kev

Senior Member
Apr 19, 2012
289
30
i flashed it and got it to boot, i know some are having issues getting it to boot. well i got booted in everything worked but i had to reboot phone and once i did it was stuck on the htc screen and i couldnt find any way around it. :(
 

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
Issues noticed so far:
- Google Now (specifically the voice search aspect) crashes
- CRT animation is SUPER fast (I'm not sure if this is a bug or how it is supposed to be)
- One time when turning off the screen, the screen displayed a tan-ish color (I haven't been able to reproduce this though)
That is all for now, I would post this on the issue tracker, like you stated--but I want to see if it's just me having these issues or if it's everyone.

- just tested google now w/o issues :-S.
- CRT animation is supposed to be that fast :).
- Not sure what could be causing that tan-ish stuff, keep an eye out. maybe there's a slight race condition where colorspace isn't loaded before display turns on. Either way, shouldn't be anything serious.
 
  • Like
Reactions: Tinyboss

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
i flashed it and got it to boot, i know some are having issues getting it to boot. well i got booted in everything worked but i had to reboot phone and once i did it was stuck on the htc screen and i couldnt find any way around it. :(

if you can get it booting again, get me a last_kmsg:

  • adb shell
  • su
  • cat /proc/last_kmsg > /sdcard/lastkmsg.txt
  • then PM it to me if you dont mind (don't post it in case it may have some sort of personal data in it like your email addy, etc.)
 
  • Like
Reactions: Tinyboss

ps3kev

Senior Member
Apr 19, 2012
289
30
i cant get it booted. my question is why it does this. i got 4.1.2 aosp rom booted up just fine after this happened

---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------

it only booted once which is so weird. and then i rebooted it and boom stuck on htc screen
 

Mike724

Senior Member
Jul 8, 2012
139
44
- just tested google now w/o issues :-S.
- CRT animation is supposed to be that fast :).
- Not sure what could be causing that tan-ish stuff, keep an eye out. maybe there's a slight race condition where colorspace isn't loaded before display turns on. Either way, shouldn't be anything serious.

That's weird about Google Now issue. If I click the microphone icon or say "Google", it immediately crashes. I'll try again with a new copy of gapps.
 

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
i cant get it booted. my question is why it does this. i got 4.1.2 aosp rom booted up just fine after this happened

May have to do with some of the necessary kernel changes to get 4.2 going (and vsync, for that matter). getting a kernel msg for one or more of these breaking should help narrow down what is missing/broken so we can fix it or ifdef it in or what-have-you.

When we tested the mass kernel change towards vsync a couple of months ago, this happened.

I'm going to look back on what needed to be changed/removed and see if anything jumps out at me, but i'll need folks help who this is busted for as well.
 
  • Like
Reactions: Tinyboss

Top Liked Posts

  • There are no posts matching your filters.
  • 188
    CyanogenMod 10 is a free, community built distribution of Android 4.2.2 (Jelly Bean) which greatly extends the capabilities of your phone.

    This is the official Nightly Build of CM10.1 for the AT&T HTC One X / HTC One XL.

    To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
    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.
     */

    Installation Instructions (These are all required)
    1. S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard)
    2. Update to 3.18 RUU
    3. Flash a custom recovery (TWRP/CWM)
    4. Download latest Nightly
    5. Download and flash GAPPS

    Nightlies return! Keep an eye on http://get.cm/?device=evita

    List all Questions and Off-Topic discussions here

    Changelog

    Huge thanks:
    intervigil, xkonni, toastcfh, deck and rohan32 - Great team to work with for the HTC MSM8960 device family.
    98
    @h8rift please check PM

    Thread has been cleaned out. While I realize Development has slowed, I have created an OT thread in the General section HERE For all to decompress ;)


    Lets try to stick with CM talk here.

    Thank you

    Thanks Tony, and sorry for the very late reply to your PM. You did what I would have asked :).

    Development is still going on for this device, but we're trying to work on m7 (HTC One) and this family and get them merged so they always stay up to date with eachother. Its a fun, but daunting task...so please bear with me :). Once we get this kernel cleaned up it *does* have working HDMI and no refresh lines too. So basically, it will be near perfect and solid for this device. Just need some time as alot of us have had work stuff, personal stuff, (and myself) medical stuff going on.

    We still love our S4 8960 devices, so they aren't forgotten :). We're learning alot about things we can fix here from what we are learning about the m7, so its a great experience for us and for you, the user. So kick back and relax and I will definitely put a noticable post up when nightlies return to normal and we move on to the other kernel which drops the lib that got us DMCA'ed.

    Thanks everyone,
    -h8
    89
    I believe everyone is correct and a status update is required at this point. This was my first CM device to maintain and I have a deep love and respect for it.

    We just merged up our 3.4 stuff to CyanogenMod and each of the four devices in the family have a few leftover issues before we start nightlies again.

    Here's the scoop on our phone on 3.4 at this moment:

    All features work except:
    *720p/1080p video
    *random reboots
    *increased battery drain over 3.0 kernel as it is not optimized or has a stale process chewing battery. Its nothing catastrophic, but noticeable.

    Issue-by-issue:
    #1: this is broken on all four devices at the moment and as all of you remember from cm9, cm10, cm-10.1 w/3.0 kernel....we do camera last. Stability first, features second, polish third.

    #2 I bricked my Evita while fixing this issue so it could be released in an alpha status to you all. Luckily, XsMagical has been very very kind and offered to donate me a new motherboard ($150) to revive my device. It should be in the mail coming my way on Monday. We believe we found the fix, I just need to validate.

    #3 this issue will be addressed after reboots and camera are up. Hell it could be the camera or reboots causing it. That's why we polish last.

    **Sidenote: in 6-8 months I will most likely get whatever new htc device is out there and maintain it too if its on at&t. Why? Because our 4 (now 6) man squad are all CM has for HTC development officially. Period. There's nearly 10 people on the GS3 and GS4 series of phones just by themselves. No one wants or loves htc devices more than us so damn right I will do my hardest to maintain as much and as many as I can. Every new device I encounter the mire I learn how to fix up the others. We figured out HDMI out for this device by working on the HTC One, for example. We are also looking at merging kernels so that yes, thus device will be continually carried through new versions of android as well as the newer devices.

    Some Evita users moved to the HTC One already and I was already there having their back. I would feel more appreciative that you get an easy-going, hard working person like me to give up all this time to work on devices knowing dang well that if you upgrade to another AT&T HTC device, you can expect me along with it. I feel I am dependable and actually listen to complaints, kudos, and feedback and respond appropriately, while other developers might not really care to respond to anything. My PM box fills up daily with questions and queries about how to build android from source for random devices like Huawei, or older devices like the HTC Flyer tablet. I literally work 45 hours a week at work, then put in another 5 hours minimum every night (or 10-15 on weekends). If you have been wondering what I have done with my 25 hours on android this week it has been trying to find a way to un-brick my Evita before that motherboard arrives so I can get to work this weekend. Rohan has been helping out a lot since my device died but he is very busy at the moment.

    Last but not least. As soon as I can confirm the random reboots every 5-10 minutes are gone and it is a stable phone (I'm talking voice and data, because phone call availability is #1 priority...I mean...its a phone for crying out loud...), I will be blowing this thread up with test builds to see if we catch other bugs.

    But I would rather see you on a stable build from March than an unstable build today and something happens to a family member and you don't get the phone call. Or maybe you get hurt badly and your phone reboots in mid-dial.

    That's what I think about. That's why there are no test builds yet. Be patient, I want to see everyone excited again once this is released again. Lord knows I could use a few hours break by having all the devices on nightlies so I can work out bugs!

    Sorry for the length, but that's what's on my mind after I read the last few posts so I wanted you to know *everything* that is going on.

    Thanks,
    -h8





    Sent from my One using xda app-developers app
    81
    Little update for you guys, the remaining issues are almost done for the 3.4 kernel. the permanent black screen unless USB is plugged in is gone now. We are now dealing with a screen on / off delay of a half a second and getting camera working again :).

    Sit tight, eat some popcorn, you will enjoy the update when its available (then nightlies will start up again shortly after, bc we wont need the file that got us DMCA'ed). This also sets us up for quick updates to the next version of android since we're mostly CAF, with minor HTC bits needed to run the vendor-specific hardware.
    77
    H8 is never late, nor is he early. He arrives precisely when he means to.

    Sent from my One X using xda app-developers app

    We're making major headway on our 3.4 kernel. No tearing and such, super smooth. Only problem right now is Camera, screen on/off delay, and if you dont have a USB cable plugged in, after about 10-15 seconds, the screen will not turn back on until you plug a usb cable back in. Otherwise its pretty much fully CAF code :).

    Sorry haven't been around, we took a break for about a week, we'll still waiting on our vendor repo to come back. That break did us well, we're making major progress now.

    There is no "giving up", its just "how long will it take". We are going to miss M3 but are trying to be ready for cm-10.1 stable. We'll just have to see.

    Thanks guys!
    -h8rift