[ROM][4.4.3] CyanogenMod 11 for HTC One S

Search This thread

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
253
2/6 nightly

Spontaneous reboot just sitting on home screen.

---------- Post added at 10:23 AM ---------- Previous post was at 10:17 AM ----------

They claim the signal hopping is actually fast dormancy working

Read a few pages and didn't get that. One guy was trying to tweak with some IPv6 settings, and strangely, my APN was the IPv6 one, though switching it didn't stop the "RILJ" errors...I'll see how well the network works at noon.
 

eabinsan

Senior Member
Sep 24, 2009
78
26
0
You can test the USB PROXY patch by remounting /system and just pushing the patched snd_soc_msm_2x to /system/etc/snd_soc_msm/
I don't have a USB audio device to test this patchset with, so I'm unsure if it will actually fix your issue, or if I've missed a use case or two, thus I'd rather someone actually test it.
As for the other patchset, if you make a gerrit account and comment on it, I can fix the authorship for you, otherwise PM me an email and I'll fix it. as well.

So the device is not crashing anymore in the car dock, but there is no sound either. Not a big problem for me, because it connects to the bluetooth audio after that anyway. Do you have a suggestion for other settings I could test? Or can I change the setting in android somewhere?
 
  • Like
Reactions: Brushstroke

nicknc

Senior Member
Dec 10, 2009
1,156
331
83
S
Read a few pages and didn't get that.

It was one of the posts on the first page that comes up that made that claim.

I didn't read past the first page, though, so didn't see it went in a different direction.

Sent from my One S using Tapatalk

---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------

You might try upgrading to the 02/05 nightly. It looks like the camera problems were fixed.

Your tether working now?

Sent from my One S using Tapatalk
 

intervigil

Senior Member
Jun 5, 2009
347
1,309
0
Bay Area
So the device is not crashing anymore in the car dock, but there is no sound either. Not a big problem for me, because it connects to the bluetooth audio after that anyway. Do you have a suggestion for other settings I could test? Or can I change the setting in android somewhere?

May still be missing a use case. Got a logcat again?
 

eabinsan

Senior Member
Sep 24, 2009
78
26
0
May still be missing a use case. Got a logcat again?
Hm, I think it tries to route sound to a non-existent usb audio device

Code:
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _disdev value Speaker
D/alsa_ucm(  255): disdev: device Speaker not enabled, no need to disable
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice(  255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/ALSADevice(  255): route: devices 0x800 in mode 0
D/ALSADevice(  255): No valid input device: 0
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice(  255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _verb value HiFi
D/alsa_ucm(  255): Set mixer controls for USB PROXY Rx enable 1
D/alsa_ucm(  255): acdb_id 45 cap 1 enable 1
D/alsa_ucm(  255): Set mixer controls for HiFiUSB PROXY Rx enable 1
D/alsa_ucm(  255): Setting mixer control: AFE_PCM_RX Audio Mixer MultiMedia1, value: 1
D/ALSADevice(  255): close: handle 0xb89cf918 h 0x0
D/ALSADevice(  255): open: handle 0xb89cf918, format 0x2
D/ALSADevice(  255): Device value returned is hw:0,0
D/ALSADevice(  255): handle->format: 0x2
D/ALSADevice(  255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice(  255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
D/AudioUsbALSA(  255): Creating USB Playback Thread
D/AudioUsbALSA(  255): PlaybackThreadEntry
D/AudioUsbALSA(  255): getCap for Playback:
E/AudioUsbALSA(  255): ERROR: failed to open config file /proc/asound/card1/stream0 error: 2
E/AudioUsbALSA(  255): ERROR: Could not get playback capabilities from usb device
E/AudioStreamOutALSA(  255): pcm_write returned error -5, trying to recover
D/ALSADevice(  255): close: handle 0xb89cf918 h 0x0
D/ALSADevice(  255): open: handle 0xb89cf918, format 0x2
D/ALSADevice(  255): Device value returned is hw:0,0
D/ALSADevice(  255): handle->format: 0x2
D/ALSADevice(  255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice(  255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
 

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
253
I will try to find out what increased delay and why we have music stuggling when unlocking Phone...

Sent from my One S using XDA Premium 4 mobile app

I think the answer was posted a page or so back. Kondik broke something (that bootloop build from last week), patched it, but the patch added 350ms delay. Promised to fix soon in the commit notes. I think the music glitch crept in with the last performance governor changes.
 
Last edited:
  • Like
Reactions: Aeonxul

blinksilver

Senior Member
Sep 23, 2007
366
54
0
Ok, I know for that. But we have music stuggling when unlocking phone or when it rings while it Is in sleep mode. I think that I know what causing that, i "just" need to figure out how to fix it. Just to get back my fujitsu from service, i have burned motherboard and HDD... :'(

Sent from my One S using XDA Premium 4 mobile app

Would you be willing to explain what the issue really is? Like why does it take so long to wake up, kondik's recent change aside, the wake time before then were bearable, but far from ideal. I'm not asking anyone to work on it further, or anything of the sorta, I'm just wondering what the deal is.
 

AKToronto

Senior Member
Nov 19, 2012
650
702
0
Toronto
I think the answer was posted a page or so back. Kondik broke something (that bootloop build from last week), patched it, but the patch added 350ms delay. Promised to fix soon in the commit notes. I think the music glitch crept in with the last performance governor changes.

Hard to see that being an issue. I thought the recent kernel commits were to ondemand gov and the cm kernel defaults to interactive anyway doesn't it? I may be wrong

Sent from my One S using Tapatalk
 

intervigil

Senior Member
Jun 5, 2009
347
1,309
0
Bay Area
Hm, I think it tries to route sound to a non-existent usb audio device

Code:
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _disdev value Speaker
D/alsa_ucm(  255): disdev: device Speaker not enabled, no need to disable
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice(  255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/ALSADevice(  255): route: devices 0x800 in mode 0
D/ALSADevice(  255): No valid input device: 0
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice(  255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/alsa_ucm(  255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _verb value HiFi
D/alsa_ucm(  255): Set mixer controls for USB PROXY Rx enable 1
D/alsa_ucm(  255): acdb_id 45 cap 1 enable 1
D/alsa_ucm(  255): Set mixer controls for HiFiUSB PROXY Rx enable 1
D/alsa_ucm(  255): Setting mixer control: AFE_PCM_RX Audio Mixer MultiMedia1, value: 1
D/ALSADevice(  255): close: handle 0xb89cf918 h 0x0
D/ALSADevice(  255): open: handle 0xb89cf918, format 0x2
D/ALSADevice(  255): Device value returned is hw:0,0
D/ALSADevice(  255): handle->format: 0x2
D/ALSADevice(  255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice(  255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
D/AudioUsbALSA(  255): Creating USB Playback Thread
D/AudioUsbALSA(  255): PlaybackThreadEntry
D/AudioUsbALSA(  255): getCap for Playback:
E/AudioUsbALSA(  255): ERROR: failed to open config file /proc/asound/card1/stream0 error: 2
E/AudioUsbALSA(  255): ERROR: Could not get playback capabilities from usb device
E/AudioStreamOutALSA(  255): pcm_write returned error -5, trying to recover
D/ALSADevice(  255): close: handle 0xb89cf918 h 0x0
D/ALSADevice(  255): open: handle 0xb89cf918, format 0x2
D/ALSADevice(  255): Device value returned is hw:0,0
D/ALSADevice(  255): handle->format: 0x2
D/ALSADevice(  255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice(  255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8

There may be something else missing for USB audio in the kernel.
 

mikronac.ns

Senior Member
Apr 25, 2012
1,169
981
0
Novi Sad
Started compiling kernel to see if I fixed music stuggling when unlocking phone... Compiling on Intel(R) Celeron(R) CPU G1610 @ 2.60GHz... :crying:


I found what caused problem... I will upload Bubba kernel tommorow to test it... :)

I dont have PC at home for few days more, just on work... And I am going home now :p
 
Last edited:
  • Like
Reactions: nicknc and Hai96

darius359

Senior Member
Aug 19, 2010
74
3
0
I'm unable to send MMS. I tried changing my APN but it seems to be stuck on the MetroPCS LTE settings. Is there a way to set it to the T-Mobile option?
11-20140202 Nightly
Sent from my One S using xda app-developers app
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 112
    logo.png

    CyanogenMod 11 is a free, community built distribution of Android 4.4.3 (KitKat) which greatly extends the capabilities of your phone.

    Index:
    1st Post: Official Nightlies for HBOOT 2.15
    2nd Post: Unofficial Builds for HBOOT 2.16
    3rd Post: Changelog


    Installation Instructions (These are all required)
    • Download or Build from Source
    • Download Gapps
    • Wipe Data
    • Flash ROM in Recovery
    • Flash Gapps in Recovery
    • Incase you don't have S-OFF, fastboot flash boot boot.img

    Not Working:
    • You tell me

    Downloads (HBOOT 2.15):
    Official Nightly Builds HBOOT 2.15 Only.
    Google Apps

    Recovery (HBOOT 2.15):
    Beginning with nightly 20140501, several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires kernel support in recovery for CyanogenMod packages to install. Your current recovery is almost guaranteed to not support this change, yet... welcome to bleeding edge!
    Please read THIS
    TWRP | Mirror


    Credits:
    intervigil, h8rift, xkonni, toastcfh, deck, rohan32, flemmard and all the HTC-MSM8960 Team Members.

    XDA:DevDB Information
    CyanogenMod 11, ROM for the HTC One S

    Contributors
    RockR172, intervigil
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Hboot 2.15.xx, S-OFF, Unlocked Bootloader, Custom Recovery
    Based On: CyanogenMod

    Version Information
    Status: Stable

    Created 2013-11-15
    Last Updated 2014-06-09
    49
    CyanogenMod 11 for HBOOT 2.16

    CyanogenMod 11 is now available for HBOOT 2.16

    NOTICE: Due to lack of free time and also not owning an HTC One S anymore, I can no longer compile builds for HBOOT 2.16.
    Worry not, @cikoleko does Nightly builds for HBOOT 2.16 which can be found HERE
    25
    Changelog:

    Latest, more accurate Changelog for Nightlies/Unofficial Builds can now be found HERE.

    cm-11-20131207-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Android 4.4.1

    cm-11-20131206-UNOFFICIAL-ville.zip

    cm-11-20131202-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Hardware Button Configuration is now back

    cm-11-20131129-UNOFFICIAL-ville.zip
    • Latest CM Source

    cm-11-20131125-UNOFFICIAL-ville.zip
    • Latest CM Source - New boot animation and more stuff!

    cm-11-20131122-UNOFFICIAL-ville.zip
    • Latest CM source - Re-introduces Quick Settings and Notification drawer settings
    • Other misc changes to device and kernel sources
    • AOSP release 4.4_r1.2 KRT16S

    cm-11-20131119-UNOFFICIAL-ville.zip
    • Can now be flashed on regular recoveries like TWRP
    • Cherry picked new Audio patches
    • Latest CM source

    cm-11-20131117-UNOFFICIAL-ville.zip
    • Camera App now actually works
    • Some other fixes

    cm-11-20131116-UNOFFICIAL-ville.zip
    • Audio Fixed
    • Bluetooth Works
    • Video Playback

    cm-11-20131115-UNOFFICIAL-ville.zip
    • First Release
    • Fixed SD Card
    • Fixed WiFi
    19
    Okay, with a heavy heart I have to say that I can no longer do builds for hboot 2.16.
    I have too much college work, assignments, practicals n stuff and can't afford to spend time compiling builds in Linux.. :(
    I did try to do builds past few days, but couldn't..
    My advice is, downgrade your hboot to 2.15 and get daily official builds from CyanogenMod. It is not really that difficult/scary to downgrade. I have done it a couple of times when i wanted to test my hboot 2.16 builds when i was on hboot 2.15.
    Also, if anyone wants to do builds for 2.16 feel free to post it in the thread..
    Sorry guys, I tried my best. :)
    Big ups to intervigil and rest of the CM team, you guys rock! \o/ \m/
    18
    Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.

    It's kind of disheartening to see so many people ascribe so many shady ulterior motives to the company (we have no plans for world domination, and it really is discouraging to see so many people knee-jerk react negatively), but ville support hasn't been so great lately, so I figure I owe you an explanation.
    CM Inc is my day job, device support mostly remains a side project for me. The company and open source organization (which are two separate things) has little to do with deciding which devices get support, and to what degree. Device maintainers are largely responsible for the kernels and device trees that actually determine how well most of the device hardware is supported.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone