[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
At least y'all get your data back after a restart. I didn't have a data problem at all (though I use to very bad) and today while I was in a area with no service my data went away and it hasn't came back. Switched airplane mode, Reboot, flash different radio, dirty flashed the entire ROM again (didn't clean flash because I was sitting in line at Walmart and didn't want to be in the middle of it while checking out). My cell data hasn't came back since. I'll clean flash tonight and pray to the mod gods that I get data back.
Sent from my One X
Just curious, do you guys flash a radio afterwards? I didn't even check to see which radio h8 includes. I'm on 3.18 and occasionally have data issues. Fyi: I make sure I'm on the correct APN
Sent from my Nexus 7 using Tapatalk HD
I use to, but this radio was working better for me than before (it's the same radio that it has been in recent times).
Sent from my Nexus 10
No. It varies from user to user but for me I don't see a substantial benefit to running another radio over the stock radio.
---------- Post added at 09:59 PM ---------- Previous post was at 09:47 PM ----------
Ok I updated the touchpanel and pushed the openrecovery-twrp-2.5.0.0 and it works! Maybe it's the 3.18 RUU and upgraded touchpanel but I didn't have any problems flashing the nightly and gapps.
Can't guarantee that it'll work for everyone but I'm going to run with this recovery for now. Cool story.
Last edited:
I updated touch panel firmware too, Working great.
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
Everyone with data issues, make sure you're on the correct APN. I was having issues and realized I was on the incorrect APN. The phone chose the wrong one for me. I chose the correct one and rebooted. Haven't had a data issues since.
Last edited:
I was on the right APN.
Just finished with a clean flash and setting everything up. We'll see how my data holds up over the next week.
Sent from my One X
Yes, you have to re-lock the bootloader. This is not a problem if you have S-OFF. Naturally it helps to have the unlock token you got when you first unlocked it handy afterward.
I did not have to relock anything
Just make sure you're in the boot loader when running the ruu. Not recovery. Not the android os. The boat loader
I have S-off as of today, but I unlocked it last year. No way I still have the key. Do you have to go through all of the steps again to unlock after re-locking it, or will fastboot oem unlock just work?
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
I have S-off as of today, but I unlocked it last year. No way I still have the key. Do you have to go through all of the steps again to unlock after re-locking it, or will fastboot oem unlock just work?
edit: I do still have the key. Looks like this won't be too much of a problem. Thanks
I'm one of those "have data issues" people. My APN is set to ATT LTE, the setting seem right from what I've seen. I found another thread on XDA with actual settings and the only thing I changed (just to try was add "hipri" to the APN type. Network mode is LTE/GSM/WCDMA - all the usual stuff. The only thing that Happens is it's bouncing from H, to H+ to 3G and I never get any data connection (I'm not in an LTE area at the moment). I've tried all the other APNs that are listed but no dice. I can see that data is being sent out, but I'm not getting anything back. Any suggestions?
This was on top of me having an issue where after I do the RUU and re-unlock, and flash TWRP, it was not able to mount the /data partition for some reason, even after rebooting. I had to reload a backup and that seemed to get things going again for some reason (I'll have to downgrade the touchscreen drivers to actually use it however).
*edit* - After a few more reboots (needed gapps) it seems to have found it's way to get data. I'll keep a watch on it. Thanks for the ROMs h8rift and everyone else for all the help and suggestions for everyone else like me!
This was on top of me having an issue where after I do the RUU and re-unlock, and flash TWRP, it was not able to mount the /data partition for some reason, even after rebooting. I had to reload a backup and that seemed to get things going again for some reason (I'll have to downgrade the touchscreen drivers to actually use it however).
*edit* - After a few more reboots (needed gapps) it seems to have found it's way to get data. I'll keep a watch on it. Thanks for the ROMs h8rift and everyone else for all the help and suggestions for everyone else like me!
Last edited:
Issue had been created for broken USB tethering
https://code.google.com/p/cm9-msm8960/issues/detail?id=240
https://code.google.com/p/cm9-msm8960/issues/detail?id=240
I too have seen the data issue twice now, once on the new build. This is in addition to the first time troubles, where it seemed set correctly, but did not work until I switched it away and back again. Both other times it has happened have been in the car, when coming out of the car dock. I have a tasker script that does a few things when going into (or out of) the dock, the one that seems likely to be causing this is toggling wifi back on when coming out of the dock. Data is working while in the dock, as I am streaming music, so the disconnect must happen after that. The only thing that happens from that point, is removing from the dock, and toggling BT off and wifi on.
To fix this, in my case, did not involve changing the APN or network mode, though that is what I tried first, along with airplane mode toggle. I had to reboot, and it came back. This has happened only twice, but it was the same situation where the data dropped. This was after clean install from the first 3.4 kernel build, with yesterday's flashed on top. To be clear, my phone shows it is connected to data with a non-blue icon at 4g (or H if I change network mode), but it cannot get anywhere, while this problem was in effect.
To fix this, in my case, did not involve changing the APN or network mode, though that is what I tried first, along with airplane mode toggle. I had to reboot, and it came back. This has happened only twice, but it was the same situation where the data dropped. This was after clean install from the first 3.4 kernel build, with yesterday's flashed on top. To be clear, my phone shows it is connected to data with a non-blue icon at 4g (or H if I change network mode), but it cannot get anywhere, while this problem was in effect.
I also encountered the data issue. When I leave my home and turn off wifi, the phone switch to 4G but it keep in grey color. Even I toggle the 4G, it does not help.
I'm a bit lucky that, the connection will become ok by toggling airplane mode.
My phone is on 26/6 nightly. i also deleted those unrelated APN, but no help.
I'm a bit lucky that, the connection will become ok by toggling airplane mode.
My phone is on 26/6 nightly. i also deleted those unrelated APN, but no help.
So just installed the latest nightly. Really big improvement since earlier versions. Glad to finally be back on aosp. One problem is that the app 3d image live wallpaper doesn't work. I believe it has something to do with opengl. Is that not working yet? The app moves the wallpaper as you tilt the device
Edit: to be clear, that's what the app is supposed to do it's just very choppy. On sense it's butter smooth
Sent from my One X using xda app-developers app
Edit: to be clear, that's what the app is supposed to do it's just very choppy. On sense it's butter smooth
Sent from my One X using xda app-developers app
Last edited:
I thought the same till I cleaned the grille out with a toothbrush. Now I have to turn down volume in the middle of a fab shop
Sent from my One X using Tapatalk 2
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
