been running this since last night, anyone else noticing the phone getting warm with moderate use?? maybe its just me but i've never had anything close to heat issues with this phone.
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
Thanks, need to narrow this down. Its the same thing that will plague other 4.2 AOSP based ROMs as well. Need to get this bug squashed as soon as possible....but can find no common reason why its not working.
To all,
If this doesn't boot for you.... please flash back to a 4.1.2 AOSP rom and gather a dmesg after a fresh reboot and PM me with it. It may have some clues. How to pull a dmesg is in 3rd post or my signature now.
Aside from the Recent Apps hardware key from not working (and also not being able to remap it in the settings for that matter), everything is A-OK in this ROM after quite a heavy load of use. I'm experiencing way better battery life for 10.1 than 10 for some reason.
Also, the RIL issue. When cold booting, sometimes I don't need to toggle/re-toggle airplane mode to make voice/data work. It's random. Not really. I ran a test. Out of 30 cold boots, about 22 of them didn't need me to toggle airplane mode (not consecutively).
Also, the RIL issue. When cold booting, sometimes I don't need to toggle/re-toggle airplane mode to make voice/data work. It's random. Not really. I ran a test. Out of 30 cold boots, about 22 of them didn't need me to toggle airplane mode (not consecutively).
Created a issue tracker for the hardware key issue. Or app switcher key issue..
http://code.google.com/p/cm9-msm8960/issues/detail?id=167&thanks=167&ts=1356470754
Sent from my One X using xda premium
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
Also confirmed headphone jack not recognized for me. Used my 3.5mm vehicle jack a three different ear buds.
Sent from my One X using xda premium
http://code.google.com/p/cm9-msm8960/issues/detail?id=167&thanks=167&ts=1356470754
Sent from my One X using xda premium
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
Also confirmed headphone jack not recognized for me. Used my 3.5mm vehicle jack a three different ear buds.
Sent from my One X using xda premium
I have a problem. The ROM loads and works but when I lock the screen and try to turn it back on, it won't turn on. I turn it off as a attempt to restart it, then it just stays at the htc screen. Help?
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
Oh crap! I forgot to put "milestone-10.1" in that issue tracker label. I get an F for following instructions today. Sorry h8rift. And I truly hope your feeling better. Thanks for all the hard work. 
Sent from my One X using xda premium
Sent from my One X using xda premium
Dude this isn't really a daily driver yet. You are better off running cm10 until everything is working if you are having nothing but install problems.
Try one of the the Sense JB ROMS. They are all pretty damn stable
My wife says "grab your phone quick take a picture of the kids opening their gifts" uh...... "you screwing with your phone again?" me= "no its better". I didn't get to play had to flash back to 4.1 for now
Looked good for the 5 min I had it
Sent from my One X using xda premium
Oh man! You have no idea how often I hear that. It's become a common refrain for my wife to mockingly ask me if I am running any new ROMs lately. Every time I excitedly tell her why the newest/latest is the greatest and then she immediately finds the one bug that holds it back and makes fun of me for it.
Meh.
sassafras
Not sure if it's just my phone, but there is some judder (not quite tearing) along the top third or so of the screen when scrolling lists. It's really distracting, but not sure what is causing it.
sassafras
sassafras
i was just asking if people can get it booted on rev b since it hasnt for me. and since it hasnt booted for some of us, i decided to send h8rift a dmesg to help out. so back off my case
Yeah I'm having the same issue and it's pretty annoying
Sent from my One X using xda app-developers app
mlaws90
Senior Member
One thing I noticed is that the torch works in CM10.1 and in AOKP 4.2.1 is does not. Maybe you could help rohan get it working, not that he couldn't do it on his own but hey it's xda we share.
I look forward to seeing this ROM evolve, CyanogenMod has really improved some features and added some new ones. Thanks h8 I hope the camera and wifi tethering don't give you too much trouble
I look forward to seeing this ROM evolve, CyanogenMod has really improved some features and added some new ones. Thanks h8 I hope the camera and wifi tethering don't give you too much trouble
rohan32
Retired Forum Mod / Retired Recognized Developer
One thing I noticed is that the torch works in CM10.1 and in AOKP 4.2.1 is does not. Maybe you could help rohan get it working, not that he couldn't do it on his own but hey it's xda we share.
I look forward to seeing this ROM evolve, CyanogenMod has really improved some features and added some new ones. Thanks h8 I hope the camera and wifi tethering don't give you too much trouble
AOKP and CM have two entirely different torch implementations, but thanks for looking out
I should be able to fix that issue relatively easily.
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
188CyanogenMod 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)
- S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard)
- Update to 3.18 RUU
- Flash a custom recovery (TWRP/CWM)
- Download latest Nightly
- 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
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,
-h889I 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 app81Little 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
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
