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

Search This thread
By:
Advanced…
Z

zenkix

Member
Jul 16, 2013
12
0
I'm getting the audio skip during unlock too, but it's not really a big deal to me.

The only issues I see really is my wifi won't connect immediately all the time. It finds my signal and says it's saved, but it won't connect. Then after a minute or two (sometimes longer), it would finally obtain the IP address and connect.

Also I'm unable to search for network operators under mobile network. Says "errors searching for networks..". I'd really like to have this fixed so I can switch my preferred network mode to GSM/WCDMA. Right now it's locked to LTE and the signal from my office is so bad, it's unusable. With HSPA+ I get full bars and a steady 8MB/s mobile connection, but I can't switch to it at the moment.

I'm running the nightly from 7/16. Flashing a different radio might fix my mobile network problem.
 
exad

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
zenkix said:
I'm getting the audio skip during unlock too, but it's not really a big deal to me.

The only issues I see really is my wifi won't connect immediately all the time. It finds my signal and says it's saved, but it won't connect. Then after a minute or two (sometimes longer), it would finally obtain the IP address and connect.

Also I'm unable to search for network operators under mobile network. Says "errors searching for networks..". I'd really like to have this fixed so I can switch my preferred network mode to GSM/WCDMA. Right now it's locked to LTE and the signal from my office is so bad, it's unusable. With HSPA+ I get full bars and a steady 8MB/s mobile connection, but I can't switch to it at the moment.

I'm running the nightly from 7/16. Flashing a different radio might fix my mobile network problem.
Click to expand...
Click to collapse

You don't change network modes that way. I always receive the same error when searching for network operators, with any CM Rom, never tried with Sense. I assumed it was not a rom issue and didn't bother to find out why it errors since I don't need it. The setting your looking for is called Network mode, and not Network operators. it's 3 options up from Network operators.

*edit* Note: you may want to set an LTE quick toggle. I have and it's great for a quick switch when I am leaving the area LTE covers here.
 
Last edited:
Z

zenkix

Member
Jul 16, 2013
12
0
exad said:
You don't change network modes that way. I always receive the same error when searching for network operators, with any CM Rom, never tried with Sense. I assumed it was not a rom issue and didn't bother to find out why it errors since I don't need it. The setting your looking for is called Network mode, and not Network operators. it's 3 options up from Network operators.

*edit* Note: you may want to set an LTE quick toggle. I have and it's great for a quick switch when I am leaving the area LTE covers here.
Click to expand...
Click to collapse

My network mode is locked to LTE. If I try to choose GSM/WCDMA, it immediately switches back. I found the LTE quick toggle and got excited but it doesn't work...I believe it just switches the network mode and in my case, that is not working.
 
K

kotchishm

Senior Member
Jul 11, 2011
114
27
Washington DC
I'm still having a issues since the radios were taken out of CM. I can't get any bars to show up, networks aren't visible, and the APN list is blank. Wi-Fi will not turn on either. I've tried the last two CM nightlies. I've flashed both the regular 3.18 radio, the 3.18 with RIL radio, and the CM 3.18 radio and can not get anything to work. I've tried everything and it's driving me crazy. Anyone else having these issues?

I'm AT&T FWIW
 
A

Artood2s

Senior Member
Jun 4, 2007
596
127
If the APN list is blank, I suggest a clean reflash, or try to recreate the PTA APN.

Sent from my One X
 
Digital_Cameltoe

Digital_Cameltoe

Senior Member
Sep 4, 2012
453
142
Glendale, AZ
kotchishm said:
I'm still having a issues since the radios were taken out of CM. I can't get any bars to show up, networks aren't visible, and the APN list is blank. Wi-Fi will not turn on either. I've tried the last two CM nightlies. I've flashed both the regular 3.18 radio, the 3.18 with RIL radio, and the CM 3.18 radio and can not get anything to work. I've tried everything and it's driving me crazy. Anyone else having these issues?

I'm AT&T FWIW
Click to expand...
Click to collapse
Buddy, after all that flashing my best suggestion is to run the 3.18 RUU again. I'm assuming your S-OFF (which you definitely should be at this point) in which case just run the RUU (which will flash the most current AT&T radio to your radio partition), flash TWRP 2.6, go into recovery and wipe everything, then proceed to flash the latest nightly and gapps. If this doesn't work your hardware is probably faulty.
 
  • Like
Reactions: kotchishm
jrior001

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
Digital_Cameltoe said:
Buddy, after all that flashing my best suggestion is to run the 3.18 RUU again. I'm assuming your S-OFF (which you definitely should be at this point) in which case just run the RUU (which will flash the most current AT&T radio to your radio partition), flash TWRP 2.6, go into recovery and wipe everything, then proceed to flash the latest nightly and gapps. If this doesn't work your hardware is probably faulty.
Click to expand...
Click to collapse

He's not s-off. We had this discussion in the rootbox thread as well. That's his problem, he's got some adb work to do.

Sent from my One X using Tapatalk 2
 
S

sephiroth2k

Senior Member
Nov 10, 2012
125
101
MMS Size Limit

Hi all, I got tired of my outgoing MMS being so tiny/compressed so I adjusted the limits. If anyone else wants to you can do so by decompiling /system/app/mms.apk using apktool, edit /res/xml/mms_config.xml to your desired size/dimensions (I use 1Mb on AT&T), recompile, sign, drop back in /system/app/ set permissions rw-r--r-- and reboot. Or you can use the attached apk based off 7/18 nightly ;). According to AT&T 600Kb is the maximum size but mine have been going through fine.

PHP: 
<?xml version="1.0" encoding="utf-8"?>
<mms_config version="4">
    <int name="maxMessageSize">1024000</int>
    <int name="maxImageHeight">3264</int>
    <int name="maxImageWidth">3264</int>
    <string name="userAgent">PJ83100</string>
    <string name="uaProfUrl">http://www.htcmms.com.tw/Android/ATT/PJ831/ua-profile.xml</string>
</mms_config>

EDIT: I've said it before with the "Thanks" button, but thank you h8rift and crew for all your hard work. You rock, and CM for evita has come a long way!
 

Attachments

  • Mms.apk
    2.6 MB · Views: 27
Last edited:
  • Like
Reactions: edditnyc, For1n, jacobas92 and 3 others
jluke86

jluke86

Member
May 2, 2011
32
6
zenkix said:
...Also I'm unable to search for network operators under mobile network. Says "errors searching for networks..". I'd really like to have this fixed so I can switch my preferred network mode to GSM/WCDMA. Right now it's locked to LTE and the signal from my office is so bad, it's unusable. With HSPA+ I get full bars and a steady 8MB/s mobile connection, but I can't switch to it at the moment.

I'm running the nightly from 7/16. Flashing a different radio might fix my mobile network problem.
Click to expand...
Click to collapse

I've been able to select GSM/WCDMA on all the recent nightlies. I have my APN set to "ATT LTE".

Sent from my One X using xda app-developers app
 
S

sephiroth2k

Senior Member
Nov 10, 2012
125
101
MMS Quality Increase, now with flashable zips

These will improve outgoing MMS quality by increasing the size limit from 300Kb. The method used is in my previous post. I'm using 1.2Mb on AT&T and it works fine, the resolution is overkill but hey why not. Flash in recovery, I wipe cache + dalvik but idk if it's necessary.
 
  • Like
Reactions: TinyRK, zeroth, For1n and 11 others
vaggolena

vaggolena

Member
Aug 19, 2011
40
7
NYC
I have to say that this ROM is getting smoother and smoother but the past two nightlies I am getting random sleep of deaths. My phone simply won't wake up and I have to hold the power button to restart.

Sent from my One X using xda app-developers app
 
L

loraque

Senior Member
Jan 18, 2010
367
62
Good afternoon everyone. The bottom mic on my hox is broken, and I want to enable the other mic for use when I am without BT. I recall way back when when h8drift had to fix it to use the lower mic, so I am guessing it is possible to change back to let me ride out my contract with a half working phone :)

What do I need to edit to make this change?

Sent from my HTC One X using xda premium
 
vaggolena

vaggolena

Member
Aug 19, 2011
40
7
NYC
exad said:
Serious guys if you're not developing or helping development POST IN THE Q&A THREAD.

Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

What I posted was not a question and has to do with this ROM and its development. If it's not the right place it can be moved. :)

Sent from my One X using xda app-developers app
 
exad

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
No it won't be moved. Even the mods don't get paid to be here. I don't see a logcat posted by you.. Post in Q&A first. If it's appropriate, it will get moved here.

Sent from my One X using xda app-developers app
 
NguyenHuu

NguyenHuu

Senior Member
Nov 14, 2007
1,753
128
California
vaggolena said:
I have to say that this ROM is getting smoother and smoother but the past two nightlies I am getting random sleep of deaths. My phone simply won't wake up and I have to hold the power button to restart.

Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

for 19, 20, and 21 I've been getting reboots like crazy. Also it doesn't charge properly. I went back to the 18th and all seems fine for now.
 
You must log in or register to reply here.

Similar threads

h8rift
[ROM][4.1.2] CyanogenMod 10 for HTC One XL
Replies
8K
Views
2M
exad
exad
Scott
  • Locked
[ROM][12/13/13] - CleanROM 7.0R2 -★| Android 4.2.2! | Sense 5! | Clean! | Stable! |★-
Replies
12K
Views
2M
Scott
Scott
Turge
  • Poll
[ROM][SEP 22] Team Venom ViperXL 4.2.0 | Sense 5 | Venom Tweaks | OTA Updates
Replies
19K
Views
2M
T
Tmobilefan906
h8rift
CyanogenMod 11.0 for AT&T HTC One XL - evita
Replies
2K
Views
447K
jrior001
jrior001
kennethpenn
  • Locked
[ROOT] One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux)
Replies
870
Views
773K
orangekid
orangekid

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 188
    h8rift
    h8rift
    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.
    View
    98
    h8rift
    h8rift
    TonyStark said:
    @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
    Click to expand...
    Click to collapse

    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
    View
    89
    h8rift
    h8rift
    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
    View
    81
    h8rift
    h8rift
    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.
    View
    77
    h8rift
    h8rift
    Desertman123 said:
    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
    Click to expand...
    Click to collapse

    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
    View

New posts