yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] pwnyourace:
I'm having a sound problem but it isn't distortion and it happens on every volume level and on every aosp rom I've tried. While listening to music if I do anything such as load a webpage in chrome or open an app or sometimes even just touch the screen it makes a loud annoying buzzing or screeching like noise it just glitches for a second and then plays normal again. Hoping maybe its a fix I've missed but I've tried using the project era sound mod and also experimented with viper4android to no avail. Does anyone know whats going on or can maybe help me fix it or if theres something needed from me I can provide. Logcat showed nothing interesting.
[One (M8) Original Android Development] nucky thomson:
Hey Guys,

just a quick question.

Is it possible to run CM11 on the HTC One E8, since it has indentical hardware as the M8? Anyone here using the E8 with CM?

Thanks!
[One (M8) Original Android Development] Captain_Throwback:
The M8 build of CM11 will not boot on the E8.
[One (M8) Original Android Development] Mohanned85:
lads before i install whats not working
[One (M8) Original Android Development] Clark Joseph Kent:
Huh from what I can tell....all is working.

But my apps differ from yours, so best for you, to try it yourself. Again IMO, all is good to go.

Judgment is near via my M8....
[One (M8) Original Android Development] kickassdave:
Sound is extremely loud and causes distortion by default.

Recommend you immediately decrease volume on boot and install V4A before applying the various recommended settings dotted around the forums!

^^ this should be in the OP!!
[One (M8) Original Android Development] mysticc:
"Extremly loud" is so true.

My speakers are now damaged after applying CM 11.

I put my Vodafone-StockRom on it to see whether it is only SW - no, speakers definitely are wrecked - distortion even on low volume remains.

Be aware !!!
[One (M8) Original Android Development] coldconfession13:
I'm shocked the speaker issue hasn't been fixed. It should have a causation about it on boot. Cm12 will suffer the same date unless it doesn't get fixed.
[One (M8) Original Android Development] adavit:
Has anyone on Verizon had problems with com.process.phone crashing with any update after the beginning of November? Any time I load anything after 11/6 I always end up with this error. Sometimes the device works fine for a day and other times it crashes in the middle of setup. I've done a dirty flash, a clean install, and even a clean flash immediateness following running a RUU. I want to be able to run the latest update so I would appreciate any help possible. Thanks!
[One (M8) Original Android Development] Ahmed Alshaali:
Same here i got damaged i think one month before so i change the rom and keep my phone in silent mod my down speaker is damaged till i repair it and i think i will sell my phone i give up with htc not so friendly with custom rom
[One (M8) Original Android Development] Mince69Meat:
Think you will find its error on the device driver code (the custom rom or more correctly the linux kernel) hardware is just that hardware and dose not discriminate between custom or noncustom roms as it dose not know the difference
[One (M8) Original Android Development] kickassdave:
I think he was stating that the loud speaker bug on CM/AOSP ROMs burst his speaker, but he thought it may just be a software bug. So installed another custom ROM only to discover it is permanently hardware damaged.
[One (M8) Original Android Development] Mince69Meat:
No he seemed upset with htc hardware instead off being outraged with cm11 software code and a long time known bug that caused the damage
[One (M8) Original Android Development] Darknites:
While there is an issue with sound it's only your own fault for keeping it loud when you can turn it down or go back to Sense or gpe.
[One (M8) Original Android Development] bill.allrobots.org:
In other words, to quote the OP:

;)

Edit: Also, before assuming your speakers are damaged, be sure to clean the speaker grille as discussed here.
[One (M8) Original Android Development] Ahmed Alshaali:
even if u silent the sound there was bug thats bezzzz wen the phone laging or somthing dont know the reason even after i change the rom but its fixed after i change to CM 12 but after what my speaker damaged its look like an old speaker wen u cut the paper from it for me i never volume high i dont like the high sound
[One (M8) Original Android Development] adavit:
So I'm assuming no one else has this issue period? If not, does anyone have an idea of why this is happening to just me?
[One (M8) Original Android Development] kickassdave:
Thanks for quoting the OP. The generic warning is in fact SO generic, I forgot it existed.

On to the speakers, again thanks for quoting the warning in the OP, can you quote the clear warning about incredibly loud and distorted sound on the speakers?

Even if you carefully read the OP, you'd have to manually read the entire thread very carefully (hundreds and hundreds of pages) just to know there was a sound bug, as before people advise "use the search function" you kind of have to know what a bug like this is before you search.

And it's quite possible for someone to not notice initially on the handset and set the volume to loud before the ringtone or music itself causes the speaker to burst.

This bug and complete lack of warning is indefensible. Software bugs, meh, you should expect that with CM, and people generally don't complain, but those that could result in total hardware failure without a clear warning are really not as forgiveable.

Honestly, some people would defend a CM ROM over their own children if it came to it.
[One (M8) Original Android Development] Darknites:
Np dude happy to help lol. I don't know how you could not know about this bug unless you a tool that flashes stuff without reading anything. The issue has come up so many times its now boring to see. Also another thing, for speakers to break he would have had to play loud sounds for some time and not hear that it sounded crap and crackling.
[One (M8) Original Android Development] phoenix2217:
This again? Didn't I defeat this argument in another thread in general? If you flash anything on these forums and bad things happen, you cannot blame anyone but yourself. If you don't read and see that there is a long standing bug as everyone says, then it's your fault. Reading has been a rule of XDA since I've been here. If you can't take the time don't flash. It's in every aosp/cm thread. Generic or not, the warning extends to everything. It wouldn't matter if it was a sense ROM, or any other ROM. I'll defend it. If you flash, your responsibility and yours alone.
[One (M8) Original Android Development] Clark Joseph Kent:
We still talking of speakers breaking? Think we have heard enough.....I have been running these builds for some time now, and I have no issues at all. Not a CM fan, just enjoy the stable and smoothness of these builds. And yes the risk is always on the individual User/Member, if you dont want risk, stay stock, and there is nothing wrong with stock btw.

Thanks now let's move on, shall we...
[One (M8) Original Android Development] Mohanned85:
No updates in 2 days. Any idea why. Top work btw
[One (M8) Original Android Development] David 617:
Because the developers are hard at work on cm12...
[One (M8) Original Android Development] Mohanned85:
thanks pal
[One (M8) Original Android Development] Hedi86:
Yes, i neeeeeeed CM12!!!!!!! ;)
[One (M8) Original Android Development] MJPollard:
Myself, I do

not

need it until (A) it's more stable, and (B) the theme engine is included. Until then, CM11 (in the form of Carbon-KK) is my baby (with ringtones turned off due to the "ringtones cause a loud beep after answering a call and then the speaker just buzzes until the phone is rebooted" issue that I hope will be fixed in CM12).
[One (M8) Original Android Development] simonvfr:
Dual Sim

I know a lot of time has passed since you posted this - but did anything come of it? I am running Maximus on my dual sim M8, but would be very interested in trying CM, especially as I already use it on Samsung 10.1 Tab Pro
[One (M8) Original Android Development] Clark Joseph Kent:
Just got one last night.....although all was/is good to go.
[One (M8) Original Android Development] Captain_Throwback:
What do you mean, did anything come of it? I don't know; did anyone actually try it?

I mean I built a CM12 that might have Dual SIM support too, but I have no idea about that either. I don't have the device, so I only know what I'm told.
[One (M8) Original Android Development] badboy47:
Oh wow thanks for the warning. I am definitely staying away from cyanogenmod as far as I can. By now I was thinking it's probably fixed but I guess not. This is a very serious issue. I think this bug should be posted in the first post or at least warn user not to listen sound very loud.
[One (M8) Original Android Development] simonvfr:
Sorry to be unclear. What I meant was to ask whether you had any response to your suggestion that the poster should try your boot image with CM11. I realise that you can only know if it worked if someone had tried it and told you.
[One (M8) Original Android Development] Captain_Throwback:
Nope. Feel free to let me know if that CM12 build works for you, though.
[One (M8) Original Android Development] adavit:
I finally managed to get a log cat when my phone began to go into the crazy com.process.phone has stopped loop. I posted over in the CM forums, but I'm posting it here too just in case someone can look at it and give me an idea as to what caused it. Thanks!

http://pastebin.com/3LaYGB6X
[One (M8) Original Android Development] bill.allrobots.org:
Working on debugging this. I found where the nullpointerexception is happening, and there should probably be a check for null when the wrappedmessage is created, but I'd also like to track down what's actually going wrong, if possible. Are there any other errors above the FATAL EXCEPTION? Looking for any of these:

createFromPdu: Invalid pdu, addr.numberOfDigits
createFromPdu: Invalid pdu, bearerDataLength
createFromPdu: conversion from byte array to object failed
SMS PDU parsing failed
SMS PDU parsing failed with out of memory

Some of them are in the radio log, I think, so you might need to do a radio logcat (adb logcat -b radio).
[One (M8) Original Android Development] adavit:
There's a lot of different errors listed. I've uploaded two logs that I gathered from the loop and uploaded to drive. https://docs.google.com/file/d/0B7C_ELk_9-7SaHgwWDc1ZnE5Qms/edit?usp=docslist_api

https://docs.google.com/file/d/0B7C_ELk_9-7SUEI2Z3EtX1AwYXM/edit?usp=docslist_api

Unfortunately I'm not at a computer right now, but when I get home I can switch back to the newer nightly and get a log when it crashes again. If you need anything else from me right now please let me know :) I wanna get this figured out as well :)
[One (M8) Original Android Development] bill.allrobots.org:
Okay, I have a bandaid patch uploaded here: http://review.cyanogenmod.org/#/c/81835/ which should at least stop the crash, but I'm still wondering why the PDU isn't parsing correctly, so a radio log of the crash would be appreciated.

If you have the expertise to compile CM, you can compile with this patch and let me know if it fixes your issue.

Edit: Also, please test whisperpush registration, as per Adnan.
[One (M8) Original Android Development] adavit:
Unfortunately I'm not knowledgeable with compiling so that's no help :( . by whisperpush, you mean the option located under privacy? If so I just registered. It seemed to go well and I received a verification code.
[One (M8) Original Android Development] adavit:
Alright, I managed to get the radio log finally. It continuously kept running, so I copied what was on the screen. Hopefully there is enough information in there for you :)

https://docs.google.com/file/d/0B7C_ELk_9-7SZHNUQVBLYUV5VHc/edit?usp=docslist_api
[One (M8) Original Android Development] bill.allrobots.org:
So you can register for WhisperPush successfully even with the new build?
[One (M8) Original Android Development] adavit:
I didn't try it with the new build (brain fart), I did it on the older build. Let me unregister and try again on the new build.

Okay, I'm back. Installed the 12/12 build and when I registered whisperpush, I received a verification code in my SMS app, however the whisperpush application timed out on the verify SMS stage and I was not able to complete enrollment.
[One (M8) Original Android Development] bill.allrobots.org:
When do the crashes start? As soon as you boot? After a specific thing happens? For instance, is it as soon as your phone tries to receive a multi-part text message?
[One (M8) Original Android Development] adavit:
I haven't noticed a specific time when it starts. Sometimes it will start immediately when I boot after installing, sometimes like when I did a fresh install it started right in the middle of setting the phone up. And sometimes it doesn't do it for a long period of time. One time I think it happened when I received a text message from amazon about my package shipping, but it wasn't a multi-part message.

When it happened the first time last night I was streaming google music, and then when I came home last night and switched from the 11/06 build to the 12/12 rom it booted right into the error.
[One (M8) Original Android Development] jakers1991:
Can I flash cm on gpe firmware or is it only on sense firmware?
[One (M8) Original Android Development] foamerman:
Is any one getting a Unfortunately Google Play Store has stopped on 12-17 or is it just me?

Edit well I think it was the recovery that I was using went back to TWRP 2.7.1.0 and I'm back in business YEA-HA
[One (M8) Original Android Development] bill.allrobots.org:
Thanks to a bunch of logs from adavit, I think I might have the SMS thing straightened out. Test build in progress.

Next issue that I'm trying to straighten out is audio, especially muffled or quiet mic in VOIP or sound recording. I think the mixer_paths are redirecting certain things to the wrong mic(s), so anyone who's noticed their mic is quiet, please post a link (pastebin etc) to a logcat recorded while you use the mic in an app that is too quiet.

Specifically, I'm looking for lines like this:

V/msm8974_platform( 240): platform_get_input_snd_device: exit: in_snd_device(voice-rec-mic)
D/audio_hw_primary( 240): select_devices: out_snd_device(0: ) in_snd_device(61: voice-rec-mic)

I'm trying to identify which audio paths are weird. In the above example, voice-rec-mic is being used, which is set up properly to use the main mic. I've noticed that the Cord app for voice messaging uses handset-mic, which by default uses dual mics in an inverse arrangement, which sounds quiet and muffled and is almost certainly incorrect. Changing it to also use main mic makes the recorded messages much clearer, and matches the HTC stock paths. I'll be putting together a patch, but I want to know what other paths I should look closely at, before I submit (there's over 1000 lines, so I'm not going to check them all).

So, please send along logcats and the name of the app you are using where your mic is too quiet, so we can get these fixed (in cm-11.0 and cm-12.0).
[One (M8) Original Android Development] Rouz.:
I can't tell you how much i appreciate your effort on fixing this issue. It has been bugging me forever, especially in "Viber" and "Line" VoIP applications. I don't have the knowledge of making logcats, but i will google it to see if i can help. In the meantime, If you have any patch for testing, I will be glad to help!
[One (M8) Original Android Development] bill.allrobots.org:
Try this: View attachment test_mixer.zip. It will replace handset-mic, the path I already believe is wrong. Without a logcat to see what other paths I should look into, I don't want to mess with anything else.

If it doesn't work, just re-install CM over top of it; it will replace the changed file back to stock.
[One (M8) Original Android Development] Rouz.:
Tested it with Viber and it works like a charm! Super clear voice on the other end! I'm gonna test it with Line now.

Edit: It works with Line too! Finally a proper fix for VoIP! You must be a wizard man! what did you change exactly if I may ask? Can we do the same on unofficial cm12 builds?
[One (M8) Original Android Development] bill.allrobots.org:
The audio path that those apps are using (handset-mic) is set to use both mics, in reverse arrangement. I think this means it uses the rear mic primarily, with the front mic for noise cancellation. The stock HTC rom uses only the main mic (which makes more sense to me, for the use cases that handset-mic seems to be used for---the noise cancellation just makes everything murky in these cases). I just changed that audio path to be the main mic, to match HTC.

I'll submit a patch to cm-11.0 and cm-12.0, so you shouldn't have to use this for long. Other things have changed in this file for cm-12.0, probably, so I wouldn't install it there, but if you really need a stopgap I can make a version for 12 as well. The fix is the same.
[One (M8) Original Android Development] Rouz.:
This buzzing issue is real. It makes a weird and loud buzz sound (randomly, for a few seconds) once I receive a notification. Happens on both CM11 and CM12. I think that it might have something to do with the updated firmware (and OpenDSP), as I am on latest GPE firmware and I didn't have this issue with an earlier firmware, but again, I am no expert.

Can you guys confirm what firmware are you using? Hopefully someone can take a look at this.

Thanks for the Info! It makes me wonder why no one else did this earlier! A quick patch for CM12 would be sweet, but I guess I can wait for it to merge. Once again, many thanks for the fix!
[One (M8) Original Android Development] bill.allrobots.org:
Never a good bug report with complete logs, that I know of. I was putting one together when I realized what was actually going wrong and decided just to fix it myself instead.

Here's the same zip but using cm-12.0 mixer_paths as a base: View attachment test_mixer.zip
[One (M8) Original Android Development] Rouz.:
I can't thank you enough. XDA needs more guys like you.
[One (M8) Original Android Development] bill.allrobots.org:
I've submitted the patches for cm-11.0 and cm-12.0, and they are currently under review.

If anyone else has any VOIP issues with quiet mics, please collect a logcat so I can look into whatever audio path is being used (at this point, I suspect they're all using handset-mic, based on the three that were tested).
[One (M8) Original Android Development] bill.allrobots.org:
Please try this build, and let me know if the crash still happens, and try registering for whisperpush as well. Take a log if the crash still happens (radio as well as normal log). Thanks.

http://d-h.st/w8F
[One (M8) Original Android Development] adavit:
Alright, I will keep you posted :)
[One (M8) Original Android Development] bschmidy10:
No camera working in 12/19 for me
[One (M8) Original Android Development] bill.allrobots.org:
No changes to camera or anything related in 12/19. Working for me.
[One (M8) Original Android Development] bschmidy10:
I hadn't updated since 12/9. Perhaps that's why. Clearing the cache in recovery fixed the issue if anyone else runs into it
[One (M8) Original Android Development] bill.allrobots.org:
The VOIP mic fix was merged, should show up in the next nightly (or the next build if you're running unofficial cm-12.0).
[One (M8) Original Android Development] krazie1:
Great work, thanks for such a awesome fix
[One (M8) Original Android Development] adavit:
Been running for over 24 hours with no error, so hopefully it stays that way :)
[One (M8) Original Android Development] bill.allrobots.org:
Nice! That's long enough that if the problem were still there, it should have crashed by now, right?

Edit: also, were you able to register for whisper push?
[One (M8) Original Android Development] adavit:
Sorry, forgot all about that, I was super excited that the build was working lol. Just registered for whisperpush and it went through and registered. :) I'm assuming all the builds from now on are going to contain this fix so I shouldn't have problems updating?

Also, thanks again for your help! Glad we were finally able to get this sorted out :)
[One (M8) Original Android Development] bill.allrobots.org:
Cool, thanks for the report. The change hasn't been merged yet, I just sent you a custom build with it compiled in. We were waiting to see that it solved the problem (I couldn't reproduce it, so I wasn't 100% sure) and didn't break other things (hence the whisperpush test). I'll report back on gerrit, and I expect it should get merged soon, unless something comes up with it.
[One (M8) Original Android Development] adavit:
Alright, sounds good :) Glad I could be helpful :)
[One (M8) Original Android Development] Rouz.:
Logcat for Speaker beeping / buzzing

Do any of you guys have the speaker buzzing / beeping issue that sometimes happen?

It happens on both CM11 and CM12, and I saw a few others reporting it as well.

Here is a logcat of it happening on a clean install of CM11. (no V4A, mods, apps, etc)

These are three logcats, I took them while hearing the beeping sound, and right after it finished. I am quoting myself on how it is happening:

I came to the conclusion that it does not happen for everyone, but hopefully the logcats contain valuable information for getting it fixed.

If there is any additional info that I can provide to help further with identifying this issue, please let me know!
[One (M8) Original Android Development] MJPollard:
Yes, and it became such an annoyance that I set the default ringtone to "none" and disabled every custom ringtone until this issue is fixed. Having my phone on vibrate-only when a call comes in is a hassle, as I have to be extra vigilant so as to not miss a call, but better that than hearing squawking and buzzing and having to reboot the phone (or, worse, risk damaging the speakers).
[One (M8) Original Android Development] bschmidy10:
Merry Christmas! / happy holidays!

I have a question about the camera.... So what is the current state of the dual camera stuff? Is there a way to actually use it or is it done automagically? Or is it just using the one main camera? I know htc open sourced the software so that's why I'm curious. Thanks for any information!
[One (M8) Original Android Development] Rouz.:
It's ironic, M10 was as stable as rock. But,

- M11 introduced double tap to wake issues

- M12 introduced the buzzing / beeping issues

I wish they could revert all the changes to M10 and build the CM12 based on that.
[One (M8) Original Android Development] Mince69Meat:
then it wouldn't be lollipop it would be jelly bean , why not just stay on cm10 oh that's right u want new features that create new bugs

Sent from my One M8
[One (M8) Original Android Development] bschmidy10:
Cm10≠M10
[One (M8) Original Android Development] Rouz.:
Read it again.

I said "M10" (cyanogenmod 11 M10)

I didn't say "CM10"
[One (M8) Original Android Development] pwnyourace:
I get the bzzz bug on my m8.

If more logcats would help I can provide.
[One (M8) Original Android Development] Rouz.:
It seems that there is nothing useful shown in the logcats. In other words, the issue is going to stay, at least for now.

To save some time for the others, let me share this: If you are having the buzzing / beeping sounds, don't waste your time by trying different firmwares or full GPE RUU conversion. I have tried them all and it doesn't make a difference.

If you are not experiencing this, then consider yourself very lucky.
[One (M8) Original Android Development] MJPollard:
There's always my solution: set the default ringtone to "none" and disable all custom ringtones, and enable the "vibrate when ringing" option. It's not a solution, but it avoids the issue and prevents the need to reboot the phone after answering a call and triggering the beep-then-buzz. (The major downside, of course, is that you have to be more vigilant for incoming calls, since you won't hear a ringtone.)

Let's hope that this issue is fixed eventually. It's absolutely ridiculous that such a powerful phone is being plagued by such a silly bug.