yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Thorin_Stone:
I'll will fill in the information later when I get a chance but I will tell you now i do not get it the sound issues at all. But nothing has changed from when I did have it till now.

The first time I got it I had it with all sounds on the phone and that was with nonames old build. (I don't know which one) then I flash pangowebs build and only got it with some sounds (BTW I dirty flashed between the builds.)

The last time I got it was when hanging up a call, I rebooted and never got it again. I honesty don't think it is a build issue because I have seen the same thing happen to people on many ROMs.

But then again I'm new to all this so I don't really know.
[One (M8) Android Development] L1nuz:
Many ROMs is based on CM
[One (M8) Android Development] droid1980:
Yes but i tried flashing it ib twrp. I realize now that i need to flash it via fastboot. Currect me if i am wrong, which i am thinking i might be.
[One (M8) Android Development] L1nuz:
You flash all roms and do backups and restore them via "recovery" - in your case twrp.

There are lots of guides and tutorials of how you do that.. either flashing a new rom or restore a nandroid backup.

---------- Post added at 12:53 AM ---------- Previous post was at 12:41 AM ----------

Why is your build containing a kernel with name "dirty" and "hacker-engine"?
[One (M8) Android Development] droid1980:
confused

I have tried to flash my nandroid back up, twrp always fails to flash my nandroid backup. Any ideas as to why it would not work for me? Ive seen it done but cant do it via my nandroid.
[One (M8) Android Development] L1nuz:
I have given you other options already... Install a new recovery and a stock ROM that fits your firmware. Have you given it a try?
[One (M8) Android Development] droid1980:
flash rom
[One (M8) Android Development] L1nuz:
No offence buddy, but you have done this already if you have rooted and installed twrp. Why don't you do some Google and basic research? There are tons of guides here on xda as well. No one can have an answer to your specific problem without knowing more. Ive asked the simplest of questions to try to help you, like what carrier you are on but no answer... I've given you links and suggestions but it seems you haven't even tried them out. Read up some guides. Google and use YouTube. Sakitech have a good channel.

Now, I expect you to make some progress till next time ;)
[One (M8) Android Development] droid1980:
Sorry man, I know we've been here before. I just want to make sure I understand the process before undertaking the steps. I found all my files, recovery, and nandroid backup, I have SDK tools installed on my pc, and cmd is in fastboot as I type. I've even done a few dry runs to make sure it all works. I will report with my progress. Sorry for the headache but that you for your patients.
[One (M8) Android Development] PhillyFlyer:
Sorry to ask a question that seems completely n00bish..BUT...is there no way to enable a status bar message preview? Ya know some text from the incoming message on status bar? Hmph
[One (M8) Android Development] L1nuz:
Its ok! ..as I replied to you in private message.. I don't think Im qualified to give you support since like 2 weeks ago I had never rooted a phone before. But before I did.. I did hours of research.. collected useful guides so if anything happened I would have a plan b... it is a big learning curve to take in new terminology and processes..

Why it doesn't work to restore a nand backup for you is very hard (for me and I guess anyone) to give a straight answer to. If you're not willing to provide us with all necessary information... what can you expect from us then!? I do hope you can find a solution to your problem... and I'm convinced that you can! Ive heard is really hard to "hard-brick" a S-On htc m8.

My unqualified guess is that you just need to redo the process of flashing a new recovery and a new rom. I would even suggest to flash a RUU if you have S-Off, if something happend to your partitions.

Please anyone.. correct me if Im wrong :)
[One (M8) Android Development] thelangosta:
I'm not on cm12 but do you have settings> interface>status bar>scroll down to advanced and look for notification ticker. I think that's what you are looking for. If it's not there then they haven't implemented it yet.
[One (M8) Android Development] droid1980:
Sorry for the lack of information. I am on a rooted HTC one M8 Att. Twrp recovery, running unofficial cyrangenmod 12, I am S-on. I was going to try and fastboot flash the stock recovery then ROM see what happens.
[One (M8) Android Development] Bobbi lim:
Is the beeping sound issue still around? I make phone calls daily so I cant afford to have it beep every time I finish a phone call...

Is the sound distortion issue fixed?
[One (M8) Android Development] droid1980:
Yes beeping sound is still an issue. Happens more and more with time.
[One (M8) Android Development] Bobbi lim:
Doesn't that mean that I have to reboot constantly if I take phone calls on a regular basis? :rolleyes:
[One (M8) Android Development] L1nuz:
I guess its different from unit to unit. But I noticed, after I do a new flash, I'll get the noise issue after hanging up a call and after a reboot it works normal for me. But I flash ROM to every new update so I wouldn't know how it is in the long run
[One (M8) Android Development] Bobbi lim:
D2w still isn't working properly... I locked the screen and tap the screen to turn on and the first try, it did turn on! But subsequent tries wasn't so lucky, it didn't worked...
[One (M8) Android Development] L1nuz:
Works for me so far. The other builds have failed t2w after the second day or so.
[One (M8) Android Development] rexmortus:
Bug tracker?

After having flashed a firmware update, installing the nightly was no problem - just like everyone advised.

Thanks for taking me through it, I learned a lot and feel comfortable ****ing around with my phone now.

I have a question for the developers:

How do you handle bug reports? Should I post things I notice here? Or do you have a dedicated tracker someplace.

Thanks again for your incredible work.
[One (M8) Android Development] Bobbi lim:
Reflashed the rom and it worked for an hour or so and stopped working...

Do you think that CPU governor has anything to do with this? :confused:

During that hour here d2w works, battery seems to be dropping faster than with it off so its better to have it off :p

I actually prefer kernel-based s2w and d2w, they're not just nice to use but battery efficient as well ;)
[One (M8) Android Development] Darknites:
If you finding battery life better with it off then that's more down to the fact the sensor not working for d2w to work.
[One (M8) Android Development] Bobbi lim:
But having d2w is a very convenient way to unlock the device. I don't want to break my power button as well :cool:
[One (M8) Android Development] Darknites:
I get that but what I'm saying is d2w is still running but it don't work since the accelerometer/gyroscope sensor stops working.
[One (M8) Android Development] noname55804:
hacker-engine is the name of my computer and dirty might be because i stoped the build and started it later again ;)

Yeah for me as well

Okay weird
[One (M8) Android Development] 429cj:
Ringtones

Anyone else having trouble with the changing of the default ringtone to a music file? If I leave the default ringtone at ORION it works fine, but if I change it to a music file, when my phone gets a call all I get is a vibrate and a beep??

I am on the 12-29 version, it was that way with the 24th version also. I am running the 3.11.1700.5 firmware. and I am on the AT&T network.

I first did a dirty install, but last night I did a complete factory wipe and reinstalled, with the same issue.

I am not having the issue with the noises on the phone thou.

Everything else seems to be working very well.

Thanks
[One (M8) Android Development] pagoweb:
cm-12-20141230-UNOFFICIAL-m8 (sync'ed at 9 AM UTC)
[One (M8) Android Development] L1nuz:
I think you have a point! After a phone call, and you lower your phone from the ear... its still black. I need to wake up the screen with pwr button and then hang up the call.
[One (M8) Android Development] Darknites:
Yep and screen won't rotate.
[One (M8) Android Development] L1nuz:
Oh those lazy devs.. can't do anything useful... .. lol ;)
[One (M8) Android Development] riaan0010:
Thanx to Rouz for testing : http://xdaforums.com/showpost.php?p=57840188&postcount=3292

I got the M10 build up and running. What do you want me to do now?

Update 1: No beeping / buzzing sound on M10 as expected. It's actually really stable! I wish the M12 was as good as this

I'm going to try M11 now.

Update 2: I got M11 up and running, so far no beeping/buzzing sound.

Nope, I did some more testing. There is no beeping / buzzing on M11

Going to try M12 now.

Update 3: I flashed the M12 and I immediately got the beeping / buzzing sound after hanging up the first phone call.

So here is the summary:

There is NO buzzing / Beeping sound on M10 and M11.

There IS buzzing / beeping sound on M12

So the issue must come from a commit that has been added AFTER the M11 build (and before the M12) That would be in the following duration:

2014-10-08 to 2014-11-12

I am not a dev guys. This was all I could do to help in order to fix this issue. I hope someone finds it useful.

Please can someone help with this issue as it it narrowed down
[One (M8) Android Development] Desaf:
Where can i find m11?
[One (M8) Android Development] riaan0010:
https://download.cyanogenmod.org/?device=m8&type=snapshot
[One (M8) Android Development] krazie1:
Wrong Thread
[One (M8) Android Development] joemommasfat:
To those of you building unofficial nightlies, has anyone tried configuring persist.call_recording.enabled ? This was the flag to enable call recording on cm11. I was curious if this was still included in cm12.
[One (M8) Android Development] alakeg31:
Good work

Hey guys I had data with ability to call and receive calls all the way through 12-27 build on Sprint HTC One M8 . Every build I've tried since that build, I have LTE data but cannot make or receive calls. Also, no notification for voicemail. I haven't had a problem with buzzing on sound in any build up to 12-27. Thanks for the hard work dev. I'm using 12-27 and have no bugs other than the no sim notification on the lockscreen that is in all the builds and no voicemail notifications.
[One (M8) Android Development] Trollzero:
I'm having the same issues on my TMO m8 with S-OFF. This ROM is awesome besides those two minor flaws. Thanks OP
[One (M8) Android Development] droid1980:
cm9 to cm12

I have to agree I went back to stock HTC sense 6. I was rocking it the cm Rom, just didn't like the fact that there are way to many problems or bugs on simple things like the Google music play back bug and the call buzzing, not to mention the demon cry that everyone would cring at, the long defining beep after calls or unplugging headphone jack I am surprised I did not blow my speakers or ear drums out. I mean really, this Rom is purely all esthetics if you ask me. Not really a practical Rom at all not even to dev on. I loved the lollipop look but I'd rather wait another month to have the official HTC one m8 lollipop. Don't get me wrong awesome work but needs way more development. For as long as cm had been around , you'd think they would have fixed the playback bug at some point. Or maybe they just don't care about the quality they put their names upon. Thank you again xda for your amazing advice.
[One (M8) Android Development] mattie_49:
My sentiments exactly. I'm back on stock debloated. Really runs ,very nicely. And I was in the gas station the other day with a cm build and my phone literally sounded like the time sequence had started and was gonna blow. Everyone was looking. I believe I heard somewhere we were getting official lp on the 3rd. Let's keep our fingers crossed. And let's all remember cm isn't building these ,others are..... Verizon m8
[One (M8) Android Development] L1nuz:
So you managed to get back to stock... nand backup?! Great news anyhow, was wondering how it went for you...

I guess the experience is different for everyone.. Im not suffering from all those bugs, Im having a decent daily driver and it works well.. perhaps because Im on GPE firmware.

Hope you'll get a better experience soon!

As for the critique of devs... there are volunteers working on cm12 in their spare time.. it requires a huge amount of man hours to get this project anywhere so patience is a thought ;)

But yeah.. some issues seems quite banal to fix, but could take hours of digging and testing to get it to work. Debugging is not the first thing that comes to your mind after work and weekends I suppose.
[One (M8) Android Development] pagoweb:
fresh build

cm-12-20150102-UNOFFICIAL-m8 (sync'ed at 11 AM UTC)
[One (M8) Android Development] Rouz.:
Stupid audio glitches on cm. I'm not a Dev, but I tried to provide as many meaningful data as I can, hoping that someone could use them and fix this issue. But no one seems to care. I guess CM is not about quality anymore.

I'm not expecting them to fix what is broken as i know it can be really hard to fix some stuff.

I do however, get mad at them for breaking the stuff that used to work great (like audio, profiles and double tap to wake).

The whole purpose of the nightlies is to identify rogue codes and stop them from getting merged into stable releases and milestones.

However these weird issues are being merged and they find their way into snapshots and they are being carried over from CM11 into CM12.

That is why i say CM is not about quality anymore. I guess they have changed their business model. Sorry for my long rant, I hope I haven't offended anyone.
[One (M8) Android Development] droid1980:
I realise the man hours that go into open source romming, just seems like the sound quality could have been worked on asap. Thank you for all your hard work.
[One (M8) Android Development] kadirpasa:
Pago .. I went to the system update page and downloaded 20150102 from there and it wouldn't boot after installation. Any thoughts?
[One (M8) Android Development] L1nuz:
System update in phone? All I can see is CM 11 updates there
[One (M8) Android Development] kadirpasa:
Well it's obvious.. I'm a moron lmfao
[One (M8) Android Development] Rouz.:
Happens to everyone
[One (M8) Android Development] L1nuz:
Yeah.. I wish they would fix those pesky bugs and push out nightly soon xD

I can't do any "dirty" flash.. for some reason it doesn't preform as it should.
[One (M8) Android Development] L1nuz:
m8: libril: Shut up already

Possible buzzing sound fix?

http://review.cyanogenmod.org/#/c/83438/

http://review.cyanogenmod.org/#/c/83437/1

xD
[One (M8) Android Development] krazie1:
Reading comments they say that's a fix for MMS
[One (M8) Android Development] kadirpasa:
My screen is constantly turning on and off without touching it. And I don't have any notifications
[One (M8) Android Development] droid1980:
Go back to stock Rom, cm12 is way to buggy.
[One (M8) Android Development] fdmitry:
This has been known already:

http://xdaforums.com/showpost.php?p=57737642&postcount=946

Can someone identify the NIGHTLY build by binary search? We can spread the search by several people to speedup the process. It would really help and I can try at least to build CM without the commits from this nightly. We can also throw the commits that cause D2W issue as they are known (see my post).
[One (M8) Android Development] Rouz.:
How should we do the binary search? Please forgive my ignorance as I don't have any experience with this. But if there is anything that a noob like me can do to help, please let me know!
[One (M8) Android Development] pagoweb:
is there an opened issue in cm jira for this audio bug ? i didn't see one in this thread. if so can someone post a link ?

EDIT : is that it ?
[One (M8) Android Development] fdmitry:
The idea is the following we know that:

cm-11-20141008-SNAPSHOT-M11-m8.zip - works fine

cm-11-20141112-SNAPSHOT-M12-m8.zip - has the beep issue

We need to identify the nightly build where the issue was appeared the first time. The fastest algorithm for this is the binary search. It can do anyone who can flash the rom. The algorithm itself will look as follows:

1. Take the nightly build between 20141008 and 20141112 exactly in the middle and test it. For example 20141026.

2. If it has the issue, then we need to take a build between 20141008 and 20141026 and test it the same way.

3. If it works fine, then we need to take a build between 20141026 and 20141112 and test it.

and so one until we find the exactly build the causes the issue.

The only problem I noticed now that the old nightlies are unavailable. :( Perhaps someone has a backup? Otherwise it will require to rebuild them and make things very slow.

---------- Post added at 02:13 PM ---------- Previous post was at 02:03 PM ----------

This one, submitted by me for a long time ago.
[One (M8) Android Development] Rouz.:
Okay, it is a bit time consuming, but fairly easy. I can start doing that in my free time. The only problem (as you said) would be to find the nightlies that are not available to download anymore.

But I'm pretty sure someone should have a copy. Can anyone upload them?
[One (M8) Android Development] riaan0010:
Guys,

I still have 29/Oct, 7 Nov , 10 Nov and 11 Nov

Will test them
[One (M8) Android Development] Rouz.:
Thanks! that would be great! please share the results. (Damn, I'm out of thanks today, can't thank you ;( I'll do that tomorrow)
[One (M8) Android Development] riaan0010:
Ok Guys.

The 29 Oct build has the beep and buzzing noise after taking calls.

After reboot all is gone again. Checked with 5 calls still okay.
[One (M8) Android Development] Rouz.:
Thanks for testing! If it happened even once, it means that the issue was there from before 29 Oct.

Does anyone has any build earlier than 29 Oct?

Edit: I made a post in the original CM11 thread to see if anyone has a copy of a nightly earlier than that.
[One (M8) Android Development] R4INS:
Or check gerrit around those dates to see what may do it.

If its a device based changed it would maybe be one of these (look at dates)http://review.cyanogenmod.org/#/q/s...nMod/android_device_htc_m8,n,003117b400012bee

If its a kernel problem maybe one of these http://review.cyanogenmod.org/#/q/s...android_kernel_htc_msm8974,n,0031d14e00014015

Can always try reverting one at a time ans building to find the culprit.
[One (M8) Android Development] fdmitry:
Of course we can rebuild. But here are several issues:

1. It is slow comparing to just flash and one should have an environment and knowledge for this.

2. Again it is better to do git-bisect or other approach with binary search otherwise you end up spending linear time on number of commits. It is very slow considering that you need to reproduce the beep every time.

May be we can ask to rebuild nightly builds on CM servers?

Or someone with fast cpu can do this and share here the builds, then people can test them?
[One (M8) Android Development] Rouz.:
[MENTION=2906882]foamerman[/MENTION] was kind enough to upload the build for 18 October for us to test. Thanks to him. He says he has all the October nightlies.

I am downloading it now to test, but here is the link in case anyone wants to beat me to it. (I am on a very slow connection at the moment)

Thanks for those links. I don't understand anything from it, but I hope someone can find something out of it.
[One (M8) Android Development] noname55804:
New build uploaded!!!

First of all, Happy new year to everyone :)

Repo was synced about 2-3 hours ago

It also includes the following changes from CM:

http://review.cyanogenmod.org/#/c/83536/

http://review.cyanogenmod.org/#/c/83551/

http://review.cyanogenmod.org/#/c/83552/

http://review.cyanogenmod.org/#/c/83535/

http://review.cyanogenmod.org/#/c/83401/

This is ported again:

http://review.cyanogenmod.org/#/c/83040/

There are some audio specific changes build in so test if the buzzing sound is still there.

As always this build is untested as i am about to flash it now ;)

Now have fun with the update and a nice first weekend of 2015​
[One (M8) Android Development] R4INS:
A high end machine can build in minutes. Specially if you dont have to clobber the build environment. Flashing a bunch of builds only helps narrow down a specific date not the actual problem. Its easy to pick which of those commits is audio based theres only a few.

Or track down and find every build from every date, flash it, then still have to pick the commit, revert it, and build to see if it was the problem.
[One (M8) Android Development] Rouz.:
What you are saying does make sense. And there are indeed very few changes during that period. I hope someone can make a few build without those commits so that we can test. This would make it a lot easier.

On a side note, I can't see anything related to audio during that time. I know you have more knowledge with this. Do you have any idea if any of these can be related?
[One (M8) Android Development] fdmitry:
If you are a dev you should know, that sound related bug can be not related to sound specific commit :)

I glad if anyone with build environment can spend a time and try to revert various commits. The time showed no one wants to do this. There are though a lot of people that can help without knowledge of the build process. Figuring out the nightly build makes it trivial to figure out a commit by a dev. In particular I can do this, but I don't have time reverting bunch of commits, do you?
[One (M8) Android Development] Rouz.:
Okay guys, it is now a bit easier to find the culprit.

I have tested the 18 October's nightly, and there is absolutely no buzzing sound there.

[MENTION=2999456]riaan0010[/MENTION] has tested the 29 October's nightly , and he said that there is buzzing sound there.

Which means we should look for something in between 18 October to 29 October.
[One (M8) Android Development] foamerman:
Hey if you need anymore I have them let me know :D :good:
[One (M8) Android Development] Rouz.:
Thanks man! If you have some extra free time, please upload the 23 October
[One (M8) Android Development] foamerman:
According to my download's there was not a 25th one posted

Sorry wrong date crap LOL I'm downloading it now sorry to much party last night
[One (M8) Android Development] Rouz.:
Haha its okay man! Thanks a lot :)
[One (M8) Android Development] pagoweb:
you should try 27th or 28th build directly as this one looks like the commit you're looking for
[One (M8) Android Development] Rouz.:
Wow, i think you found it! That's great! Can you make a build without this commit? Would it be possible?
[One (M8) Android Development] foamerman:
Rouz I sent you a pm with Oct 23
[One (M8) Android Development] pagoweb:
idk if this is the commit that causes the audio bug although it seems related. plus idk know if reverting it is easy ... i think you should first keep trying cm11 build close to this commit just to be close to sure (28th or 27th ...) as i understood 29th build has the bug.
[One (M8) Android Development] Rouz.:
Thanks a lot man! I am downloading it now. If you can upload the 27th october's nightly, it would help a lot. but only if you have some extra time to spare ;)

I am on it, right now I'm downloading 23rd, if it was fine, I will test 27. I really hope we can find it this time!

If anyone can help me with this, I appreciate it!
[One (M8) Android Development] riaan0010:
Wow guys this is exciting stuff, thank you all for testing
[One (M8) Android Development] krazie1:
Great collaboration everyone
[One (M8) Android Development] ambivalent-one:
In the last 3 builds I continue to have bluetooth audio issues. works after a reboot. The problem is that it will work, then when I get back in my car later it doesn't work. Bluetooth is connected. Sometimes pausing the track and playing again causes a few seconds of working audio and then it cuts out again.

Going to clean flash again and try with this build.