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

Search This thread

jascination

Senior Member
Dec 1, 2008
72
3
I'm having issues with data dropping after wifi is turned off. Only solution is to restart the phone. I clean flashed and am running cm10.2.

Sent from my One X using Tapatalk 4
I've been having this issue since around early July with CM10.1. Also getting data dropouts all the time when moving from one location to another, although this might be wifi-related (e.g. when I leave my house where WIFI is connected and the phone switches to 3g, data is still shown as 'connected' but internet doesn't work at all, need to toggle aeroplane mode. Then when going from one part of the city to another it does the same thing (except just going 3g -> 3g, I assume it's connecting to a different tower or something?)).

Wondering how far back I have to go to a time where this wasn't a problem? Maybe the CM10 stable build? Or the M2?
 

aaronDroid80

Senior Member
Feb 24, 2011
473
133
Mechanicsburg, PA
I've been having this issue since around early July with CM10.1. Also getting data dropouts all the time when moving from one location to another, although this might be wifi-related (e.g. when I leave my house where WIFI is connected and the phone switches to 3g, data is still shown as 'connected' but internet doesn't work at all, need to toggle aeroplane mode. Then when going from one part of the city to another it does the same thing (except just going 3g -> 3g, I assume it's connecting to a different tower or something?)).

Wondering how far back I have to go to a time where this wasn't a problem? Maybe the CM10 stable build? Or the M2?

Take a look at this.
http://xdaforums.com/showthread.php?p=44896109

Sent from my One X using Tapatalk 4
 

silentheero

Senior Member
Dec 8, 2010
182
43
Follow up - My issue was solved by a quick apn change to the AT&T lte profile. Forgot about having to change that since I haven't clean flashed in a while. Thanks aarondroid for jogging my memory!

Sent from my One X using Tapatalk 4
 

falconfox

Member
Dec 19, 2012
24
1
Android Keyboard (AOSP) has stopped.

Hey guys. About 2 weeks ago, i've been getting the following error regularly:
Unfortunately, Android Keyboard (AOSP) has stopped.
I'm using the newest GAPPS (20130812).

Things I have tried:
  1. Flash the latest nightly with GAPPS
  2. Settings > Apps > Force Stop & Clear data

Neither worked. Does someone have another solution / suggestion?
 

beankid

Senior Member
May 21, 2010
315
16
Did I miss something? Did development stop for 10.1? No new nightlies have been posted since the 18th of this month.
 

Ezekial

Senior Member
Feb 6, 2011
92
24
Does anyone have a link to the latest 10.1 nightly? I need a full download so I can test fixing an issue I reported in the last page with installing a clean latest build of CM.

Looking at get.cm http://get.cm/?device=evita&type= all of the downloads are now for 10.2 or a very old (March) build of 10.1.
 
Last edited:

aaronDroid80

Senior Member
Feb 24, 2011
473
133
Mechanicsburg, PA
Does anyone have a link to the latest 10.1 nightly? I need a full download so I can test fixing an issue I reported in the last page with installing a clean latest build of CM.

Looking at get.cm http://get.cm/?device=evita&type= all of the downloads are now for 10.2 or a very old (March) build of 10.1.

RC1 just dropped, if you want to give that a shot.

Sent from my One X using Tapatalk 4
 

Ezekial

Senior Member
Feb 6, 2011
92
24
RC1 for 10.2?

Update: I was able to find a 10.1 download from the goo.im app. I also still had a full copy of my phone, which I didn't realize was the case even for a delta through CyanDelta. Anyways, after loading a fresh 4.2.2 tether worked just fine (the built in one, didn't try the other app). I then restored my ROM and for some reason, it was working! Strange, but either way I am pleased.

Ahh and I see 10.1 has an RC1. Interesting. Finally saw it (the only place I seen it) under the settings menu (About Phone).
 
Last edited:

JayDream

Senior Member
Feb 17, 2013
297
139
Palm Springs, CA
10.1 RC1 Massive battery drain.

I went to sleep last night with my phone fully charged, 8 hours later i checked it for battery drain. Battery was down to 71% without even using it all night. I checked wake lock detector and it shows 'Google Services' running all night keeping my phone awake for 8 hrs 15mins out of a total of 8 hrs and 20 minutes (screenshot Attached)

Sent from my One X using xda app-developers app
 

Attachments

  • uploadfromtaptalk1377884073301.jpg
    uploadfromtaptalk1377884073301.jpg
    79.9 KB · Views: 296

Spike15

Senior Member
Nov 1, 2009
520
3
Yeah, I and someone else found the same thing on the RC

Sent from my One X using xda app-developers app

Also seeing this.

Is there, or will there be, a fix for this, or is h8rift et al.'s idea of "release candidate" "has alpha-/beta-level bugs but we're through so here it is"?

Also: What radio are people using? I'm seeing mobile data disconnects (for ~30 seconds maybe once an hour) and wifi disconnects (for ~2 minutes maybe once every one or two days).
 

aaronDroid80

Senior Member
Feb 24, 2011
473
133
Mechanicsburg, PA
Also seeing this.

Is there, or will there be, a fix for this, or is h8rift et al.'s idea of "release candidate" "has alpha-/beta-level bugs but we're through so here it is"?

Also: What radio are people using? I'm seeing mobile data disconnects (for ~30 seconds maybe once an hour) and wifi disconnects (for ~2 minutes maybe once every one or two days).

Appears to be fixed in rc2

Sent from my One X using Tapatalk 4
 

JayDream

Senior Member
Feb 17, 2013
297
139
Palm Springs, CA
Also seeing this.

Is there, or will there be, a fix for this, or is h8rift et al.'s idea of "release candidate" "has alpha-/beta-level bugs but we're through so here it is"?

Also: What radio are people using? I'm seeing mobile data disconnects (for ~30 seconds maybe once an hour) and wifi disconnects (for ~2 minutes maybe once every one or two days).







Appears to be fixed in rc2

Sent from my One X using Tapatalk 4
Ya the problem was definitely something to do with flashing RC 1, I would avoid it like a case of herpes if I were u.. I ran the 3.18 RUU and this cleared the problem for me, but that may be too drastic of a move for some, so here try this http://xdaforums.com/showthread.php?p=45266303 see if that helps


Sent from my One X using xda app-developers app
 

Spike15

Senior Member
Nov 1, 2009
520
3
Ya the problem was definitely something to do with flashing RC 1, I would avoid it like a case of herpes if I were u.. I ran the 3.18 RUU and this cleared the problem for me, but that may be too drastic of a move for some, so here try this http://xdaforums.com/showthread.php?p=45266303 see if that helps


Sent from my One X using xda app-developers app

Reflashed 3.18RUU, on RC2, still getting WiFi cut outs once or twice a day, and ~60 second mobile drops 1-4 times per hour.

Advice? Is there a different radio I should be flashing?

EDIT: Tried 1.85, 2.2, 2.4, 3.17.841.9, 3.17.162.8, and 3.18 for radios. Mobile disconnects every ~15 minutes across the board. So pretty sure it's not the radio at this point...

EDIT: Can see the disconnects here.
 
Last edited:

jascination

Senior Member
Dec 1, 2008
72
3
Anyone else getting weird sound dropouts on last ~5 nightlies? Sound notifications/from youtube/browser just stop all of a sudden, don't re-work until resetting. Audio from Apollo plays fine though. Very odd.
 

JayDream

Senior Member
Feb 17, 2013
297
139
Palm Springs, CA
Reflashed 3.18RUU, on RC2, still getting WiFi cut outs once or twice a day, and ~60 second mobile drops 1-4 times per hour.

Advice? Is there a different radio I should be flashing?

EDIT: Tried 1.85, 2.2, 2.4, 3.17.841.9, 3.17.162.8, and 3.18 for radios. Mobile disconnects every ~15 minutes across the board. So pretty sure it's not the radio at this point...

EDIT: Can see the disconnects here.

Sorry I don't know nothing about radios. All I can do is vouch for what works for me and the above steps work like a charm without flashing any radios

Edit: I think this is your answer http://xdaforums.com/showthread.php?p=45516867

Sent from my Nexus 4 using xda app-developers app
 
Last edited:

sandys1

Senior Member
Jun 4, 2010
763
165
That's interesting that between all the 10.2 development, they managed to put out a stable build for 10.1. It's a tad late for that though, IMO. They should have done a stable for 4.3, but hey, hats off to them for doing so anyway!

Guys, can I please request someone to check the stable build for working USB tethering ? Right now I'm CM 10.2 and I'll downgrade if it's working on this.
 

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