Sure. I'll put up a warning label for it in OP now.
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
Sure. I'll put up a warning label for it in OP now.
No, the purpose of a thread is to discuss issues and make suggestions as well as to sing the praises of a ROM. The current build is 100% incompatible with phones running HBOOT2.14 and mrjayviper was simply suggesting that it would be a good idea to include this "compatability" information in the OP.
This seems to me like a perfectly reasonable suggestion and no reason to jump down his throat with some high and mighty spiel about patience.
It was misunderstood, looks like it's all sorted now.
Back to the ROM, are you sure the current build is 100% compatible with HBOOT 2.14? The OP was edited by h8 to include that touch screen doesn't work. This was also the concern of mrjayviper that led him to post what he did in the first place.
You are definitely extremely confused
HBOOT 2.14 IS COMPATIBLE WITH NOTHING BUT SENSE BASED JB ROMS
i figured how to get the notification light working, just set it to always on and it should work. Any other choices doesn't work.
I'm not the confused one, unless you quoted the wrong post. I was pointing it out to vanja in case he was confused, which he seems to be.
EDIT: obviously I'm the one who read vanja's post wrong to begin with, incorrectly trying to correct it, my mistake.
Last edited:
Great find!
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
My mistake! I read it as "compatible" initially and just wanted to clear it up. I definitely know the touch screen doesn't work lol but thanks for pointing that out. I agree it was a great request!
Report on the battery life, at least 30% better than the 4.1.2 nightlies, maybe more. The screen tearing isn't SO bad, it seems to have gotten better over the last few builds. Also, this may have been mentioned, but I can't seem to get slider shortcuts to ever appear. Widgets are pretty cool though, will definitely take some getting used to but they can definitely become more functional.
Last edited:
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL
That is 100% true and in no way do I think they are doing as good as they could, but I'm just glad they done what they were supposed to do, that's all.
Sent from my Nexus 7
That is 100% true and in no way do I think they are doing as good as they could, but I'm just glad they done what they were supposed to do, that's all.
Sent from my Nexus 7
Odp: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL
Where do you set this? I want to have it permanently off
Send from my One XL CM10.1
Where do you set this? I want to have it permanently off
Send from my One XL CM10.1
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL
Settings>System>Notification light
Sent from my One X using xda app-developers app
Settings>System>Notification light
Sent from my One X using xda app-developers app
First build from jenkins of cm10.1 (4.2.2) is on get.cm. Yes it is marked "Experimental" because it did not go through the normal nightly cycle.
But it is there and is ready for use. We are now official.
And for those wondering, yes, this has the working GPS again.
Enjoy!
-h8rift
But it is there and is ready for use. We are now official.
And for those wondering, yes, this has the working GPS again.
Enjoy!
-h8rift
Does this build have the kernel changes that fixed screen tearing, such as the latest AOKP build does?
You guys are beasts!!! I'm gonna try this right away. And soon we will have sweet sweet sweep2wake for this too!
Sent from my CM10ified Beast (a.k.a. HTC One XL)
I haven't seen any yet and there is a kernel upgrade, I will test some more and see.
The commit that rohan cherry-picked doesn't really fix the tearing (its realistically a refresh rate line). We are working on it still.
Ah ok, my bad
I assumed that the new kernel had a fix for it after reading rohans AOKP thread. The cherry-pick does help a lot EDIT: I still have some tearing, but it's a MAJOR improvement over the last build!
Last edited:
Just flashed and it seems to be great! Thanks for the great work!
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
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
