I downloaded it with WiFi on cm updater just fine this morning.
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
GPS Issue
Has anyone had an issue with the GPS where apps can still use it even after GPS is turned off?
I have this problem with both the GPS test and facebook apps. If either of those is the last app to use the GPS before I turn it off, it will continue to access it somehow, and drain the battery. See the attached picture.
Google maps is the other app I use that accesses the GPS, but it doesn't have this problem.
If anyone wants me to provide logs I'll be happy to.
Cheers.
Has anyone had an issue with the GPS where apps can still use it even after GPS is turned off?
I have this problem with both the GPS test and facebook apps. If either of those is the last app to use the GPS before I turn it off, it will continue to access it somehow, and drain the battery. See the attached picture.
Google maps is the other app I use that accesses the GPS, but it doesn't have this problem.
If anyone wants me to provide logs I'll be happy to.
Cheers.
Last edited:
+1
Sent from my One X using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
What gapps version are you using? First time I have seen Facebook suck on the battery. Using gapps march version and all my issues were resolved.
Sent from my One X using xda app-developers app
Just kinda curious as to why the newest nightlies still flash the older radio?
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
I heard once the 3.4 kernel is implemented, the new radios will be included.
Sent from my One X using xda app-developers app
I have experienced this with "My Tracks" which is interesting because I think that it is based off Google Maps (it is a google app itself).
There is an application called AT&T messages which integrates vvm as well as others in one app. It worked for me although I'm not a big fan of it though... I prefer having vvm only.
Does anyone find the ROM quite picky with the wifi hotspots in can connect to?
I've setup my macbook running windows7 and freebsd9.1 as wifi hotspots. And my iOS devices and TF700 running cm10 have no problems connecting to it. I had a OneX(tegra3) running cm10 in the past and had no problems connecting to the FreeBSD hotspot.
My OneXL running viper have no problems connecting to the windows7/FreeBSD wifi hotspots. But when I installed cm10.1, it can't connect anymore to both hotspots.
Any ideas on how to fix it? Are you getting the same experience as I am? thanks!
I've setup my macbook running windows7 and freebsd9.1 as wifi hotspots. And my iOS devices and TF700 running cm10 have no problems connecting to it. I had a OneX(tegra3) running cm10 in the past and had no problems connecting to the FreeBSD hotspot.
My OneXL running viper have no problems connecting to the windows7/FreeBSD wifi hotspots. But when I installed cm10.1, it can't connect anymore to both hotspots.
Any ideas on how to fix it? Are you getting the same experience as I am? thanks!
h8,
Rolled back to the M2 release last night and the media storage crash is none existant compared to the 130306 nightly.
Alarm didn't go off this morning as i had AM/PM backwards, going to test tonight and will know tomorrow morning (Aussie time).
Any reason that this would not work on nightlies before M2, work on M2, but then not work on nightlies after M2?
I also can't log a bug report on CM Jira as this issue doesn't exist on the M2 :|
I've encountered two issues that have been present since the 3/6 build. One is that if I'm listening to music using any app, and I open chrome the music app closes. If I reopen it and go back to chrome all is well. It's only present when starting a new session. The other is that sometimes if I take the phone away from the side of my face, the screen will turmn on, then immediately off not letting me end the call, which has gotten me in a little trouble. Instead when I press the on button, the capacity button lights blink twice and do nothing. It's like the phone is telling me to go **** myself 
and it always happens when I accidentally call someone I don't want to and try to immediately end the call.
and it always happens when I accidentally call someone I don't want to and try to immediately end the call.I just flashed the 3/11 build yesterday coming from M2 and my alarms worked perfectly this morning.
Sent from my HTC One X
Latest nightly the headphone jack does not work. Audio only pumps out from the phone speaker.
Sent from my One X using xda app-developers app
Sent from my One X using xda app-developers app
I have noticed that WiFi connectivity is generally finicky, i.e. it will drop good connections or not recognize a router within inches of the phone. It does usually connect when prompted and eventually resolves the connection itself (although may drop it again).
I know there was discussion of this in the thread prior to M2, but not certain it was tracked or resolved.
dbd
I've encountered two issues that have been present since the 3/6 build. One is that if I'm listening to music using any app, and I open chrome the music app closes. If I reopen it and go back to chrome all is well. It's only present when starting a new session. The other is that sometimes if I take the phone away from the side of my face, the screen will turmn on, then immediately off not letting me end the call, which has gotten me in a little trouble. Instead when I press the on button, the capacity button lights blink twice and do nothing. It's like the phone is telling me to go **** myself
I get an odd issue with music as well where, if I just plug in my headphones and play, it will almost always play silent. I need to pause, get out, recent apps, clear it, reopen, play (even same track right from where it was paused) and all is well. This is Google Play Music, Apollo doesn't do much of anything well.
Now for the calls, I can almost be 100% sure it's your proximity sensor and not the ROM. I had the same thing and it was mirrored across any ROM. Do you notice in NATURAL light the problem (basically) isn't there?
Try this app: https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
It's called Rezound Proximity Sensor Calibrator, but it works with tons of devices. Worked like a champ for me. Adjust the top bar until sensor says FAR, I added 5 numbers to when I saw FAR appear after pressing + a bunch of times (it changed to FAR at 20 so I set it to 25, no problems since). Try to do it in a not-so-well lit place to have the most consistency.
All the best!
Sent from my CM10ified Beast (a.k.a. HTC One XL)
I will definitely try that, but would that account for me being unable to turn the screen on manually?
DURING a call yes, proximity sensor is king when a call is in progress. I had to PUSH onto the top-left of the screen (I guess to lower the sensor closer to the board for better light sensing?) for the call to realize that I'm "FAR" from the sensor until I'd see the end call screen. Only then the phone would return to home screen or lock screen only AFTER that, and this could be a minute or two after the call was ended on the other caller's side.
Last edited:
It's not included in the ROM. You'll have to flash a camera/gallery zip separately.
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
