That's weird...i just tested and they were working for me :-S. I'm forward porting our old headset patch from 4.1 and 4.0, hopefully this will get approved and will work to fix the issue.
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
- Thread starter h8rift
- Start date
-
- Tags
- development
That's weird...i just tested and they were working for me :-S. I'm forward porting our old headset patch from 4.1 and 4.0, hopefully this will get approved and will work to fix the issue.
Bluetooth Audio and Navigation
Very nice surprise to see this up, while I had it installed it ran very nicely! I had some issues with things that I use almost daily though.
My phone is not routing sounds to bluetooth. It connects to my bluetooth and determines its a media connection but playing music through apollo and pandora does not route sound to my bluetooth device.
I had the maps force closing issue after starting navigation on CM10 which I couldn't test since I did not get a gps lock after about 15 minutes of driving.
Very nice surprise to see this up, while I had it installed it ran very nicely! I had some issues with things that I use almost daily though.
My phone is not routing sounds to bluetooth. It connects to my bluetooth and determines its a media connection but playing music through apollo and pandora does not route sound to my bluetooth device.
I had the maps force closing issue after starting navigation on CM10 which I couldn't test since I did not get a gps lock after about 15 minutes of driving.
Don't worry, it's a known issue. Just keep waiting guys! I know you're all probably as anxious I am to get this booting on our phone!
Sent from my ASUS Transformer Pad TF300T using xda premium
D
Deleted member 3452239
Guest
got the headset patch up on gerrit now and built it...but i can't find any wired headphones w/mic to test with right now lol.... Wired headphones w/o mic play music just fine w/o any issues (tested pandora, phone call audio, etc.). Just need to test mic 
I've narrowed down the "no boot" for some evitas to where it is breaking, still digging on *why* its breaking....and why only certain evitas.
Definitely want to get 4.2 going on this rather smoothly ASAP as well.
I've narrowed down the "no boot" for some evitas to where it is breaking, still digging on *why* its breaking....and why only certain evitas.
Definitely want to get 4.2 going on this rather smoothly ASAP as well.
got the headset patch up on gerrit now and built it...but i can't find any wired headphones w/mic to test with right now lol.... Wired headphones w/o mic play music just fine w/o any issues (tested pandora, phone call audio, etc.). Just need to test mic
I've narrowed down the "no boot" for some evitas to where it is breaking, still digging on *why* its breaking....and why only certain evitas.
Definitely want to get 4.2 going on this rather smoothly ASAP as well.
h8rift,
Quick question. This is more of a 10.0/1 (JB) problem in general but it seems that the Voice to text and voice search function refuses to use any BT microphones when active. So, when I go to reply to a text by using Google Voice Typing, nothing happens because it doesn't revert to using the BT mic. I know you've had a lot of fun getting CM10 to work with the audience chip in this phone anyway, but I was wondering if it was something to do with this that might be making this fail? I haven't looked too closely, but it seems highly probable. Just going through msm_snd_2x, I seem to recall you having to tweak the microphones just to get Google Now to use the correct one.
sassafras
Last edited:
Please log an issue in the tracker for it w/Milestone-10.1 in the labels before submitting. I'll look into it once i finish up the issue im still working on regarding some evitas not booting.
I thought the 4.2 gapps would look better, I can't tell the difference lol
Sent from my One X using xda premium
Sent from my One X using xda premium
I haven't ironed it out yet....but the 4.2 gapps appear to be the reason why Voice Search is force closing. A file is missing or a drawable resource is missing within resources.xml of the Voice Search application. See below (specifically the bold lines):
Code:
E/AndroidRuntime( 3078): FATAL EXCEPTION: MicrophoneReader
[B]E/AndroidRuntime( 3078): android.content.res.Resources$NotFoundException: File res/raw/open.wav from drawable resource ID #0x7f080009[/B]
E/AndroidRuntime( 3078): at android.content.res.Resources.openRawResourceFd(Resources.java:982)
E/AndroidRuntime( 3078): at com.google.android.voicesearch.audio.AudioTrackSoundManager.loadSound(AudioTrackSoundManager.java:123)
E/AndroidRuntime( 3078): at com.google.android.voicesearch.audio.AudioTrackSoundManager.playSound(AudioTrackSoundManager.java:84)
E/AndroidRuntime( 3078): at com.google.android.voicesearch.audio.AudioTrackSoundManager.playSpeakNowSound(AudioTrackSoundManager.java:48)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.AudioController$3.get(AudioController.java:259)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.AudioController$3.get(AudioController.java:256)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.MicrophoneInputStream.startRecordingLocked(MicrophoneInputStream.java:116)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:93)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:147)
E/AndroidRuntime( 3078): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
E/AndroidRuntime( 3078): at java.io.InputStream.read(InputStream.java:163)
E/AndroidRuntime( 3078): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:191)
[B]E/AndroidRuntime( 3078): Caused by: java.io.FileNotFoundException: This file can not be opened as a file descriptor; it is probably compressed[/B]
E/AndroidRuntime( 3078): at android.content.res.AssetManager.openNonAssetFdNative(Native Method)
E/AndroidRuntime( 3078): at android.content.res.AssetManager.openNonAssetFd(AssetManager.java:450)
E/AndroidRuntime( 3078): at android.content.res.Resources.openRawResourceFd(Resources.java:979)
E/AndroidRuntime( 3078): ... 14 more
Has anyone tried otg? I plugged in my flash drive and it showed recognized but could not find it in esexplorer or cmfileexplorer? Used stickmount also to check and no dice...
Sent from my One X using xda premium
Sent from my One X using xda premium
I think Google removed (left out) OTG ability in 4.2. This is an issue on Nexus devices as well running the stock ROMs. On my Nexus 7, support had to be added back in by kernel/ROM developers. Not sure if this is present in CM 10.1 as I use Paranoid Android on the 7.
Sent from my One X
I actually posted a logcat on post #31 about this. I got the same exact exception/stack trace as you did. It's weird how others have not noticed this issue, maybe it's because they dirty flashed?
Pardon my ignorance
Google has something to do with USB otg? My hox shows its there in settings/storage, I just can't access it like I could on cm10. Just wondering if this should be operational. No biggie if not. :screwy:Sent from my One X using xda premium
Pardon my ignorance
Sent from my One X using xda premium
are you checking in the right directory? i think its /storage/usbdisk or mnt/storage/usbdisk
mnt! That was it. Thank you kind sir
Sent from my One X using xda premium
Well when I play a video or a game my phone becomes completely white or gray!?!?!? Why does it do that? An reboot fixes it though.
Sent from my One X using xda app-developers app
This is a development thread in a development forum. This Rom is a work-in-progress and is not intended for use as a daily driver. It is expected that there are issues with the Rom and an average end-user should stick to a more mature CM build until this Rom is considered "stable" and fully-baked. No support will be given to the end-user of this Rom.
If you find an issue that has not yet been identified, please submit a proper bug report along with a logcat. Let it be known that by using this Rom, your phone may explode into violent Orcs... but as of right now, it won't work just right. The developers are hard at work to fix any issues and to bring us a working build with all of the expected features. Until said build is complete, do not use this Rom as your daily driver unless you would like to assist with testing and bug reporting, or if you can live with the bugs without complaints.
Also, please consider donating to the good people who are working for free to bring us the CM 10.1 goodness. They do this for fun and should not be demanded to give anyone answers about causes of issues.
Thanks, and happy new year! :highfive:
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
