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

Search This thread

BurntMyToast

Member
Oct 16, 2010
46
7
I've found AwesomeBeats to work. You should check that out.

Link

Does awesome beats increase volume out on phone? When I use auxiliary in my car with spotify or Pandora I can not get the volume to be "that" loud. Thanks in advance and if anyone else is having the same issue and has fixed it please respond. Thank you

Sent from my One X using xda app-developers app
 

Mentwar

Member
Aug 6, 2010
22
54
Sydney, Australia
@h8rift, rohan32: thanks for quick reply and Gerrit review, and also AOKP test build! Indeed mine was affected by the LTE issue (since CM10 prior to my patch).

Fix will be in next nightly, but I'm also uploading test CM10.1 build zip to Dropbox for those who want to flash sooner :p (Will post link later - uploading is slow) This build also contains one more change (will submit to Gerrit later) that enables signal icon in the status bar to show "H" icon when connected to HSDPA/HSUPA/HSPA instead of "3G". I'm unable to test this (where I live has mostly LTE and HSPA+ coverage so not affected), so if others can test this it would be appreciated.
 
I

Icarus1391

Guest
@h8rift, rohan32: thanks for quick reply and Gerrit review, and also AOKP test build! Indeed mine was affected by the LTE issue (since CM10 prior to my patch).

Fix will be in next nightly, but I'm also uploading test CM10.1 build zip to Dropbox for those who want to flash sooner :p (Will post link later - uploading is slow) This build also contains one more change (will submit to Gerrit later) that enables signal icon in the status bar to show "H" icon when connected to HSDPA/HSUPA/HSPA instead of "3G". I'm unable to test this (where I live has mostly LTE and HSPA+ coverage so not affected), so if others can test this it would be appreciated.

Waiting for the link :)

Sent from my HTC One X using Tapatalk 2
 

Mentwar

Member
Aug 6, 2010
22
54
Sydney, Australia
Last edited:

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
  • Like
Reactions: llambkin

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
Test build uploaded (after Dropbox taking several hours to upload zip... :p)

https://dl.dropbox.com/u/19376651/cm-10.1-20130217-UNOFFICIAL-evita.zip
MD5 Checksum: https://dl.dropbox.com/u/19376651/cm-10.1-20130217-UNOFFICIAL-evita.zip.md5sum

Gerrit: http://review.cyanogenmod.org/#/c/32039/

EDIT: @devs I just realised ville and jewel don't have H icon overlay either, does it make sense to put this into msm8960-common instead? I'll submit another Gerrit if that's the case.

I'm not sure sprint/vzw devices use "H" at all. I think they *do* use the 3G symbol since its technically correct. I'll ask later today about it.
 

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
I just did a clean install of cm-10.1-20130216-NIGHTLY, but sadly to report that LTE didn't stay default after reboot.

Same here...maybe the fix didn't get in?

My blazingly fast as f*#k One XL fueled with CM10.1

If I understand correctly it should be in the next nightly.

mikelebz is correct.

here's the newest nightly taht should have the LTE fix in it (its on get.cm):
cm-10.1-20130217-NIGHTLY-evita.zip
 
  • Like
Reactions: For1n

Mentwar

Member
Aug 6, 2010
22
54
Sydney, Australia
I'm not sure sprint/vzw devices use "H" at all. I think they *do* use the 3G symbol since its technically correct. I'll ask later today about it.

You're right, I just checked spec of jewel and it doesn't have WCDMA/HSDPA etc at all (since it's CDMA2000 device). On such devices setting config_hspa_data_distinguishable has no effect (and other CDMA devices in CM tree don't seem to set it); it's only relevant to evita and ville.
 
Last edited:

llambkin

Senior Member
Jul 5, 2012
63
11
Its not there yet (this is not done...)....But you can always go to Settings -> System -> Quick Settings Panel and add Torch as an Option. then pull down from lockscreen to enable / disable torch

I have done this as a workaround, I used to use a lockscreen gesture on CM7 :D, but the long-press home button is much easier. Good to know it will be worked on.

Cheers h8
 

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
@h8rift, rohan32: thanks for quick reply and Gerrit review, and also AOKP test build! Indeed mine was affected by the LTE issue (since CM10 prior to my patch).

Fix will be in next nightly, but I'm also uploading test CM10.1 build zip to Dropbox for those who want to flash sooner :p (Will post link later - uploading is slow) This build also contains one more change (will submit to Gerrit later) that enables signal icon in the status bar to show "H" icon when connected to HSDPA/HSUPA/HSPA instead of "3G". I'm unable to test this (where I live has mostly LTE and HSPA+ coverage so not affected), so if others can test this it would be appreciated.

I just need some user testimonials saying this works for them and im good to +1 it. I wont merge til i talk to intervigil to make sure he has no qualms with it. :)
 

shawnchalfant

Senior Member
Aug 6, 2008
332
81
Somewhere in Texas
Having performance issues.

I'm having choppy graphics in games, and Quadrant scores about 4700. Any settings I can tweak would help, also having vertical sync issues with scrolling. What are the best I/O and governors for CM kernel?
 

goldman007

Member
Jun 20, 2012
48
2
Anyone else having issues with Google Play Music? It wont display artwork/time if current song finishes and GPM is not in foreground. Also I sometimes have to close/restart it after plugging in headphones or it produces no sound...
 

shawnchalfant

Senior Member
Aug 6, 2008
332
81
Somewhere in Texas
OK, I understand about the benchmark numbers.

But screen tearing in games is real bad, Riptide especially. I know these are dev builds, but basic 3d performance issues need to be mentioned. How else will these be addressed?
 

subarudroid

Senior Member
Jun 18, 2011
1,545
677
SL,UT
But screen tearing in games is real bad, Riptide especially. I know these are dev builds, but basic 3d performance issues need to be mentioned. How else will these be addressed?

I just played heavy gunner and Sky's of glory, and I play a lot of spheres vs blocks... Im not sure how taxing that is, however they all did just fine. Perhaps my eye sight isn't what it should be.

Sent from my HOX w/CM10.1 :)
 

shawnchalfant

Senior Member
Aug 6, 2008
332
81
Somewhere in Texas
Regardless, of small issues.

Who could ask for anything more CM 10.1 4.2.2? Just wanted to put it out there about slow 3d performance and 2d tearing issues. Maybe devs have an idea of what I mean.
 
Last edited:

edditnyc

Senior Member
Jun 29, 2012
638
296
New York
www.eddit.net
[A] Issues Tracker

But screen tearing in games is real bad, Riptide especially. I know these are dev builds, but basic 3d performance issues need to be mentioned. How else will these be addressed?

The Issue Tracker?

http://code.google.com/p/cm9-msm8960/issues/list

---------- Post added at 11:01 AM ---------- Previous post was at 10:50 AM ----------

LTE shows up as default now :)

My blazingly fast as f*#k One XL fueled with CM10.1

+1 LTE FTW
 
  • Like
Reactions: mrjaydee82

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