Database Develop

[Q] Touchscreen sensitivity issues in CM9/CM10 (but not webOS)... any advice?

Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.

To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.

thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.

As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!

Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.

Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.

[Q] No Sound in CM9 or CM10

Hi community! Thanks to all the developers who make this project fly!!!
I fear I have a resistant Touchpad that does not want to output any audio in Android CM9 or CM10.
It has sound in WebOs so I don't think it is a hardware problem.
I've tried CM9 (123012) and heard some soundtap noise after a reflashed gapps, but then the sound went away, I think
when the wifi started (?).
CM9 was extremely slow and the system would be very laggy and freeze when I tried to change the volume by using
the volume buttons. Many times I'd have to do a power+home button shutdown.
CM10 (121612) on the other hand was very responsive, quick and smooth and there was no lag or freeze on pressing the
volume button- but still no audio.
I used ACMEuninstaller to remove CM9 and used:
ACMEInstaller3, CWM6, moot 0.35 for both installs, flashed cache and dalvik, and fixed permissions.
Is there anything else I can try?
Thanks!

Briefly hold the power button to bring up the menu and make sure it isn't set to mute should be the bottom Line with a line under the speaker on the right .

I brought up the screen, and it shows the speaker icon on the right side with the line under it.
It looks like volume is on and not mute, but still no sound.
Thanks for the suggestion.
Thinking it was something to do with WebOS 3.05, I used the thread in this forum to bring back the Touchpad to WebOS 3.00, and
then 3.04 and still the same issue appears in Android.
I'm now thinking that this 32GB Touchpad may not have the same hardware for the audio codecs to work in android?
(Actually, I'm clueless and just guessing, and, hope I'm wrong.) :fingers-crossed:

Well it was worth a try, it shouldn't be anything to do with webos (I'm on 3.05) . Do the headphones work as it has been suggested that the socket my be causing problems .
Otherwise I'm also clueless .

Good to know that it isn't WebOS 3.05 related.
I tried the headphones and no sound either. So I rebooted with the headphones plugged in and no sound.
One other thing I can't figure out is why would CM10 be more stable than CM9 on this device, when the consensus seems to be
that CM9 is much more stable?

No idea , I'm using Oat's at the moment but also have a backup of jcsullins so that I can test out things on both and have stopped using CM9 completely .
I take that you get no sounds when typing and that the volume cursor moves when you use the rocker switch .

Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).

north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
Try going to settings > sound > volumes, and see if the settings are correct.
If I think of something else, I'll post it.

I have the exact same problem. Tried all the resolutions mentioned above, no result. Wiped out android and used WebOS doctor for full recovery, then installed the latest nightly (24 Nov 2013) still no sound. Somewhere it was mentioned that it is due to a firmware (A6) problem but I don't know how to downgrade or upgrade the firmware.
Any help is appreciated.

Hp Touchpad on CM9 and CM10
I have also tried for nth times but my touchpad 16GB has no audio output (including 3.5mm jack) on CM9 or CM10......... somebody help

I have the same problem, but can install older CM9 builds and have sound. 6/12/2012 nightly is one that has sound for me.

My problem ended up being the head phone jack. I rapidly inserted/removed the headphones several time and my speakers came back to life.
Still very odd that I had audio in WebOS and older cm9 builds the whole time, but I'll refuse the question that logic and am thankful that I was able to get it working.

north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.

CJMax said:
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
Click to expand...
Click to collapse
Have you guys considered submitting alogcat to the developers? It might be more productive than just stating that you have a problem. Submitting a logcat might help to get the problem fixed. I remember hearing issues with 64GB Touchpads not playing sound with CM9 Roms. Flashing the audio libs helped a few of those users.

I created a log on pastebin: MyfU2DDU (not allowed to post full urls yet). Who should I send it to? At the beginning of the log, sound was still working, then (I think line ~1280) sound stopped. Afterwards, I'm getting out of memory errors. Running CM10, same problem in CM9 and CM10.1.

Had the same prob and now back on cm-9-20130512 and disabled system sounds. It works now.

[Q] Absolutely awesome!!!!

Extreme kudos and awesomeness and gratitude to jcsullins and all the folks involved with developing CM10/Android for the TP. Thank you.
I had been watching the forums to figure out a good time to "jump in" and yesterday I took the moments to install CM10.1 (4/18/13) on my TP. I was amazed at how seamless and flawless the installation was. It seemed it took less time to do the install than it did to download CM10 (download was ~100kb (kB?)/s). CM10 came up running without any problems.
Of course, it wasn't without some issues After confirming CM10 was functional (along w/Wi-Fi, etc.) I installed gapps and that's where the problems began. I first tried gapps-jb-20130409-signed (which did not get installed with CM10). After it was installed, I lost the keyboard app (kept getting messages about the keyboard no longer working). I tried suggestions of default/reset and clearing both caches. Didn't fix the problem. Wasn't sure how to uninstall gapps, so I did a complete CM10 reinstall and tried gapps-jb-20130409-signed again. Still no good. I thought maybe it was a compatibility issue (I could never be absolutely clear which gapps would work with which CM version). So, I went with gapps-jb-20130301-signed. Same problems. I then came across gapps-jb-4.2-Gapps-And-Extras-Signed (I changed the name to be sure it would work with ClockWorksMod) mentioned in a posting. This seemed to do the trick. Keyboard remains fully functional.
I'm curious if there are any log files kept on the TP from the install. Each time I installed CM10, I noticed in the messages rolling up the screen that certain directories couldn't be found. And I think a few of them were related to gapps installation. I'd be interested to see what that was about.
The only problem I've noticed in the short time I've played with it is that the Wi-Fi went inactive (and not temporarily). I went into settings and tried to turn it off and then back on. Once I turned it off, I wasn't allowed to turn it on. There are prob'ly 1/2 a dozen or more Wi-Fi sites nearby, but the TP couldn't see any of them. I ended up doing a power down/reboot and that brought back Wi-Fi.
Anyway, I am very pleased with the new OS. And happy to be independent from WebOS, since its future is unknown.
Cheers....Steph

A two years old device with the latest Android, yeah, its definitively a great work!

Log files are saved in the back up and/or in /cache/recovery/last_log . Also do you have the "Keep Wi-Fi on during sleep" setting set to Never? That might be why your wifi is having issues, because I had the same issue when mine was set to Never. Now I usually keep mine set to Always and it hasn't had that issue and doesnt seem to use the battery too much.
Surge1223

Im curious, were you testing CM10 or CM10.1?

Go and read a guide again, you're installing the wrong gapps. The ones it specifically says not to use.
You need this one:
http://goo.im/gapps/gapps-jb-20121011-signed.zip

[Q] Problems with Touchpad CM

Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/

iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.

chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning

Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..

iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.

chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.

I use milaq's nightlies, and for my needs, it's more than adequate.

[Q] Audio stops working from time to time

Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!

This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app

I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?

Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app

Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.

I don't use bluetooth at all, but I'll try Earpiece, thanks

the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards

lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?

For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app

lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)

I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app

I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening

Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards

Definitely better, yes So you're using CM11? Any problems?

Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards

Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.

Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too

CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore