[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
Haha yeah if I wanted it on the unlocked screen. I want it on the lock screen. I saw a ton of nexus 4 lock screen screen shots where it had the new clock style with the bolded hour. I don't want the ugly skinny font, I want the bolded font as the main clock on the lock screen.
Sent from my One X using xda premium
---------- Post added at 10:47 PM ---------- Previous post was at 10:36 PM ----------
Never mind. Figured it out. Had to delete the stock clock after adding chronic. Thanks though.
Sent from my One X using xda premium
EDIT: You found it. Pretty cool UI for the lockscreen. Now to look up all those 4.2 lockscreen widgets...
Last edited:
If you swipe from the left on your lock screen and add the clock of your liking you will notice a lock icon on the bottom of the new lock screen. Tap it and it will shrink the lock screen section down and will reveal the lock slider. This should remain your main lock screen j til you tap the lock icon on another screen. You can also completely remove the original by tap holding and dragging it to delete.
Sent from my One X using xda premium
Gave it another shot, this time I let it boot once before I flashed gapps and wouldn't you know it booted up
Sent from my One X using Tapatalk 2
Booted up the first time on my Rev B phone, no problem.
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
Tested NFC with my wife's SGSIII works great. Tried three different headsets and they all work fine including the 3.5mm jack in the car.
Sent from my HOX w/CM10.1
Sent from my HOX w/CM10.1
The cm update on 4.2.1, does it still reference the older cm10 updates or are they v4.2.1 updates from the cm10 repo?
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
I couldnt get a lock either. also the gps source is missing in settings to enable you to "use internal gps"
back to Good old trusty CM10
Good god man. I can't believe how quick and smooth this is. Trebuchet made some major changes for the better, but I'm using the newest updates of nova launcher and its just simply amazing. Once the camera gets fixed I'll have to change my drawers every time I use the phone haha :what:
Sent from my One X using Tapatalk 2
Sent from my One X using Tapatalk 2
Looks promising, can't wait until a few of the bugs are worked out. Back to CM10 for a while though.
I couldnt get a lock either. also the gps source is missing in settings to enable you to "use internal gps"
back to Good old trusty CM10
My GPS locked just fine. Off about 40 yards but not a huge deal.
Sent from my One X using xda premium
quick suggestion i've been thinking about lately (not sure if this is the right place)
an option to allow 2(or more) notifications to be expanded by default would be great. stock android, by default, expands the top notification automatically.
but i use an app called notification weather, which leaves an expanded notification in my shade at all times, so now any other notifications i get will never be expanded by default, since the weather one is
if i could set it to 2, then my most recent notification would expand like it would normally if i didnt have that weather one in there
an option to allow 2(or more) notifications to be expanded by default would be great. stock android, by default, expands the top notification automatically.
but i use an app called notification weather, which leaves an expanded notification in my shade at all times, so now any other notifications i get will never be expanded by default, since the weather one is
if i could set it to 2, then my most recent notification would expand like it would normally if i didnt have that weather one in there
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
