-
We are moving to xdaforums.com!
Posts made between now and when the migration is complete will not be carried over.
You will be automatically redirected once the migration is complete.
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
LOL!!! There's a cricket in my basement chirping at this very moment. I almost fell off my chair when I scrolled down and saw this.
First major issue that I've had with this Rom, and unfortunately, I'm not in a position where I can grab the necessary files. Flashed the 0816 nightly this morning (while still on charger), and everything was fine. Happened to glance at my phone later and saw that it was rebooting. Battery was at 89% when it started up. Then it just went into boot loop. Got it into recovery and flashed back to 0813 and things are ok again. Anybody else get this?
Sent from my One X using Tapatalk 4
Sent from my One X using Tapatalk 4
Maybe its karma from "crying wolf" yesterday0816 working just fine for me.
That wasn't crying wolf, it was crying katydid.
Sent from my One X using Tapatalk 4
That wasn't crying wolf, it was crying katydid.
Sent from my One X using Tapatalk 4
Touche!
I did a clean install and it worked perfectly fine. Maybe you dirty flashed?
The only problem I'm having (with CM10.1/.2 nightlies w/ 3.4 kernel and maybe its just me) is that the battery or cpu gets really hot when I'm gaming (Clash of Lords). It gets up to 120+ degrees according to GSam. Went back to Viper 3.2.8 and it doesnt heat up that high (around 105 degrees) with the same amount of time and with all the same apps install. Again, this might be just me, but any advice/methods of troubleshooting would be appreciated.
Looks like the data drop issues may be fixed tonight. http://changelog.bbqdroid.org/#/evita/next *fingers crossed*
---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------
Yeah, I dirty flashed it. I haven't had any issues in the past dirty flashing nightlies, but there's a first for everything. I doubt that this had anything to do with the boot looping, but when it started, I was in a basement with little-to-no signal. Afterwards, there were some strange things happening with reception in general, but I'll attribute that to the building I was working in.
---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------
Touche!
I did a clean install and it worked perfectly fine. Maybe you dirty flashed?
The only problem I'm having (with CM10.1/.2 nightlies w/ 3.4 kernel and maybe its just me) is that the battery or cpu gets really hot when I'm gaming (Clash of Lords). It gets up to 120+ degrees according to GSam. Went back to Viper 3.2.8 and it doesnt heat up that high (around 105 degrees) with the same amount of time and with all the same apps install. Again, this might be just me, but any advice/methods of troubleshooting would be appreciated.
Yeah, I dirty flashed it. I haven't had any issues in the past dirty flashing nightlies, but there's a first for everything. I doubt that this had anything to do with the boot looping, but when it started, I was in a basement with little-to-no signal. Afterwards, there were some strange things happening with reception in general, but I'll attribute that to the building I was working in.
Hmmm... Maybe the data is what's killing my battery and heating it up. We will see tomorrows! =) Thanks for the heads up!:good:
It's normal on non-Sense roms, well in my experience it is.Touche!
I did a clean install and it worked perfectly fine. Maybe you dirty flashed?
The only problem I'm having (with CM10.1/.2 nightlies w/ 3.4 kernel and maybe its just me) is that the battery or cpu gets really hot when I'm gaming (Clash of Lords). It gets up to 120+ degrees according to GSam. Went back to Viper 3.2.8 and it doesnt heat up that high (around 105 degrees) with the same amount of time and with all the same apps install. Again, this might be just me, but any advice/methods of troubleshooting would be appreciated.
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
We should probably delete our posts and move to the other thread, since the mods don't like having this kind of stuff on the dev thread.
---------- Post added at 02:57 AM ---------- Previous post was at 02:47 AM ----------
You should try the INFINITY Engine and Adrenaline Injector. My screen on time has increased by an hour or more and have noticed that my games are smoother
Newb here, with regards to CyanogenMod. I have been on ViperX and/or CleanROM since I got the phone in April 2012. After 2 self destructing installs of the current ViperX (twice now I have rebooted and the GUI won't load, though I can use ADB to backup data and prepare for a wipe) along with general bloat of Sense I decided to finally try out Cyangenmod. Have to say, I have been BLOWN away at how damn good this ROM works!!!! Especially for not having source! Big props to the devs. Anyways... to my question.
I started out on August 1st nightly and then delta flashed to the 11th. I cannot get wireless tether to work (on both the original install and delta). Every single thing works great otherwise. I have tried both the built in AND the Wifi Tether app (https://code.google.com/p/android-wifi-tether/) which I have used for a long time now. I have tried many different configurations of WiFi Tether, including the configuration I have used on Sense ROMs for the past 1.5yrs (routing fix, generic ICS/JB WLAN1, auto). I have also tried WPA2 as well as Open. It appears the device tethering will pull an IP (192.168.43.X) but has no internet access. The phone never looses connectivity (verified with a ping running). Ideas?
:Edit
Looks like there have been several updates in the past few weeks. I'll do a backup later and flash the delta to see this helps.
:update
I tried 08-18 delta update from Sunday, this did not help. The situation as I can quickly describe is:
* Built in Tether - I can connect to the hotspot from my tethered device, I get an IP, I can ping the phone gateway ip (in this case, 192.168.43.1), but I cannot connect to any Internet address. Running a tracert to 4.2.2.2 stops at 192.168.43.1 from my tethered device.
* WiFi Tether app - Using device-profile Generic ICS/JP (wlan0) or (wlan1) only works when I also use Setup-Method "Native Framework Tether". Doing that though does not use the SSID I configured, but instead creates the hotspot "TetherFallback" but does retain my WPA key. Same results as built-in.
* WiFi Tether app - All other Setup-Methods either fail to "start tethering" with a notification to check the logs OR will appear successfully start in the app, but there is never a WiFi signal for me to connect to (netd method for example does this).
* Open Garden app - Similar to the WiFi Tether app just above, or will actually crash the whole app. One of the crash error messages is "couldn't install file - /data/data/og.android.tether/bin/dnsmasq!". The app is ROOT enabled.
Here is my catlog.
I started out on August 1st nightly and then delta flashed to the 11th. I cannot get wireless tether to work (on both the original install and delta). Every single thing works great otherwise. I have tried both the built in AND the Wifi Tether app (https://code.google.com/p/android-wifi-tether/) which I have used for a long time now. I have tried many different configurations of WiFi Tether, including the configuration I have used on Sense ROMs for the past 1.5yrs (routing fix, generic ICS/JB WLAN1, auto). I have also tried WPA2 as well as Open. It appears the device tethering will pull an IP (192.168.43.X) but has no internet access. The phone never looses connectivity (verified with a ping running). Ideas?
:Edit
Looks like there have been several updates in the past few weeks. I'll do a backup later and flash the delta to see this helps.
:update
I tried 08-18 delta update from Sunday, this did not help. The situation as I can quickly describe is:
* Built in Tether - I can connect to the hotspot from my tethered device, I get an IP, I can ping the phone gateway ip (in this case, 192.168.43.1), but I cannot connect to any Internet address. Running a tracert to 4.2.2.2 stops at 192.168.43.1 from my tethered device.
* WiFi Tether app - Using device-profile Generic ICS/JP (wlan0) or (wlan1) only works when I also use Setup-Method "Native Framework Tether". Doing that though does not use the SSID I configured, but instead creates the hotspot "TetherFallback" but does retain my WPA key. Same results as built-in.
* WiFi Tether app - All other Setup-Methods either fail to "start tethering" with a notification to check the logs OR will appear successfully start in the app, but there is never a WiFi signal for me to connect to (netd method for example does this).
* Open Garden app - Similar to the WiFi Tether app just above, or will actually crash the whole app. One of the crash error messages is "couldn't install file - /data/data/og.android.tether/bin/dnsmasq!". The app is ROOT enabled.
Here is my catlog.
Last edited:
so nightlies look to have moved on to 10.2 now (20130820 latest as of this post). Are they relatively safe to flash yet? I've heard lots of brick stories with 10.2
The brick issues appear to have been fixed, no new bricks reported since before nighties started for 10.2.
I've been running 10.2 since h8rift posted the experimental build with the brick fix, I've had zero issues and my phone is faster all round. If you are super paranoid about bricking feel free to wait some more, otherwise I'd encourage you to try out the 10.2 nighties.
Sent from my One X using Tapatalk 4
I'm having issues with data dropping after wifi is turned off. Only solution is to restart the phone. I clean flashed and am running cm10.2.
Sent from my One X using Tapatalk 4
Sent from my One X using Tapatalk 4
I'm not sure which nightly I was on last, but possibly that one... My phone started boot looping or restarting soon after boot at random last night. The 10.2 upgrade went badly for me twice and I had restored back to 10.1. After the boot loops, I went with a fresh install of 10.2, which is now working fine.
Sent from my Nexus 7 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
