[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
LTE stays default with the 2/17, thanks. One thing I'm curious about is the awake stats. CM 10.1 seems to show non-wake to the point where it's suspect. I have screen on and using apps and it doesn't show awake in the battery stats. Anybody else see this?
Sent from my One X using Tapatalk 2
Sent from my One X using Tapatalk 2
stuck on boot screen after doing all the right steps
So this is what happened to me
factory reset/erased system/cache/davlik
flashed boot.img exctracted from your ROM using .fastboot
rebooted into TWRP recovery and install your ROM and GApps
erased cache/davlik
rebooted
got stuck on boot screen (HTC developer edition).
Rebooted into TWRP recovery and restored older version of ROM
currently im on CleanROM 5.1 hboot 1.14
any ideas?
So this is what happened to me
factory reset/erased system/cache/davlik
flashed boot.img exctracted from your ROM using .fastboot
rebooted into TWRP recovery and install your ROM and GApps
erased cache/davlik
rebooted
got stuck on boot screen (HTC developer edition).
Rebooted into TWRP recovery and restored older version of ROM
currently im on CleanROM 5.1 hboot 1.14
any ideas?
I
Icarus1391
Guest
Maybe a bad download? Try redownloading the rom.
It was discussed in the last pages. It's not an issue, the led means that you have to connect the phone to a charger.
Sent from my HTC One X using Tapatalk 2
Here are some of my findings regarding issues with LTE
On the 2/17 build with Baseband 3.17, I noticed my phone wasn't connected to LTE by default. I checked phone info via *#*#4636#*#* and the "Set Preferred Network Type" is defaulted at WCDMA preferred. Changing it to LTE/GSM/CDMA auto preferred gets it connected to LTE. However a quick check back and it's LTE/GSM auto instead. Upon reboot, it goes back to WCDMA preferred.
I currently have AT&T PTA selected. Changing settings via Settings -> More -> Mobile Network Settings doesn't seem to have an effect as it's still set to WCDMA preferred on *#*#4646#*#* phone info.
On the 2/17 build with the default baseband , it is set to LTE/GSM auto by default on the phone info via *#*#4636#*#*. Changing it to LTE/GSM/CDMA auto preferred will only have go back to LTE/GSM auto. On Settings -> More -> Mobile Network Settings it says it's set to LTE/GSM/WCDMA but it might not really be the case.
Not sure what to do with knowing this. I'm going to keep the default baseband and see how the battery life is on it now.
On the 2/17 build with Baseband 3.17, I noticed my phone wasn't connected to LTE by default. I checked phone info via *#*#4636#*#* and the "Set Preferred Network Type" is defaulted at WCDMA preferred. Changing it to LTE/GSM/CDMA auto preferred gets it connected to LTE. However a quick check back and it's LTE/GSM auto instead. Upon reboot, it goes back to WCDMA preferred.
I currently have AT&T PTA selected. Changing settings via Settings -> More -> Mobile Network Settings doesn't seem to have an effect as it's still set to WCDMA preferred on *#*#4646#*#* phone info.
On the 2/17 build with the default baseband , it is set to LTE/GSM auto by default on the phone info via *#*#4636#*#*. Changing it to LTE/GSM/CDMA auto preferred will only have go back to LTE/GSM auto. On Settings -> More -> Mobile Network Settings it says it's set to LTE/GSM/WCDMA but it might not really be the case.
Not sure what to do with knowing this. I'm going to keep the default baseband and see how the battery life is on it now.
Just keep the default baseband. We're due for an update from 2.20's radio files to 3.17's radio files in the coming weeks.
We're working on a huge thing right now. 3.4 kernel, which means that we can basically shadow the nexus 4's updates step by step. its on the side from what we're doing on nightlies right now.
3.4 kernel has no screen tearing, we can probably stop hacking our camera HAL and use nexus 4's instead, as well as many other things.
Basically, if all goes well, this phone will become a nexus4 on the inside, and an HTC One XL on the outside (casing). Thank LG/Google for using the msm8960 platform for its nexus, as it would not be possible otherwise. This is very exciting.
:victory::victory::victory::victory::victory:
That would be so awesome. Thank you for your dedication to this project and this phone, h8.
Clearly, LG and Google knew deep down that the One X deserved to be a Nexus device
Good find! It is true that the 3.17 radio defaults to wcdma... This is not rom specific.. Just stick on an older radio if you want lte default... I have not had any issues with the default as lte/gsm
Sent from my One X using Tapatalk 2
H8 man...that's what I'm talking about
My blazingly fast as f*#k One XL fueled with CM10.1
+1 lmao.....I was thinking about buying a Nexus 4....think I might stay now
My blazingly fast as f*#k One XL fueled with CM10.1
would that fix the touchscreen problem on certain hboot versions or the fix has to come from the HTC JB kernel? thanks!
would that fix the touchscreen problem on certain hboot versions or the fix has to come from the HTC JB kernel? thanks!
Haven't ironed that out yet.
It may end up that i have to put up a pre-requisite that *everyone* update to the newest touchscreen firmware (via a flashable zip hopefully when i get there....but not the whole JB OTA w/new HBOOT) and we support the new firmware only. I dont know if its possible to do both....yet.
When we get this 3.4 kernel rocking (only thing broke right now is ril and camera) then we can hav a few JB OTA-takers try it and hope that it may work regardless.
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
