yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Rouz.:
I am testing the 23 Oct nightly at the moment, and downloading 27 Oct nightly at the same time. All thanks to this guy > [MENTION=2906882]foamerman[/MENTION] who is kind enough to upload them for me one by one. I will report back as soon as I am done testing.

Update: Build 23 Oct is clear! But I'm gonna test it for a little longer before i flash 27 Oct.

Update 2: Yup, there is absolutely no buzzing sound in 23 Oct. I tested it long enough to be sure. That leaves us with 24-28 Oct. I'm gonna flash 27 Oct now.
[One (M8) Android Development] foamerman:
Hey guys I just did a clean install of the CM12 1/3 and my root checker pro says I lost root!! has anybody tried it yet and checked root everything else is good so far
[One (M8) Android Development] pauwie:
[MENTION=2906882]foamerman[/MENTION], i lost the root after yesterdays build. I also can not write to SD, am i the only one?
[One (M8) Android Development] pagoweb:
root on new cm12 builds

[MENTION=2906882]foamerman[/MENTION] [MENTION=1617895]pauwie[/MENTION]

root has been modified (and that is a good thing...at last):

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

to enable root now you'll have to go to dev options and enable root option.
[One (M8) Android Development] MJPollard:
Yes, it's very good to see, especially since the CM devs sure as hell don't seem interested in fixing it. Looks like it's up to us to do the job.
[One (M8) Android Development] foamerman:
Under dev options I have Root access then there is Disabled, apps only, ADB only, and Apps and ADB is that what you are talking about?

EDIT I figured it out I got root back thank you
[One (M8) Android Development] pagoweb:
yes.
[One (M8) Android Development] pauwie:
Thank you for the quick answer, got root back indeed.
[One (M8) Android Development] foamerman:
Yes I just checked Apps and ADB and did a reboot root came back :good:
[One (M8) Android Development] pagoweb:
[MENTION=2906882]foamerman[/MENTION] [MENTION=1617895]pauwie[/MENTION] since you have latest build, do you still have the infamous audio issue ?
[One (M8) Android Development] riaan0010:
Jip is still there
[One (M8) Android Development] pagoweb:
Too bad... i was hoping commits [MENTION=5046290]noname55804[/MENTION] picked were good fixes for that bug...
[One (M8) Android Development] foamerman:
No I did a clean flash and I do not that infamous audio issue
[One (M8) Android Development] riaan0010:
I had it on first call whereby i answer and as soon as I end the call. THE buzz Sound starts. Reboot

And it was on a fresh build ( Full Wipe etc. )
[One (M8) Android Development] Rouz.:
Check your PM, need your help

Some updates for everyone:

I am testing 27 Oct nightly for a while now, and there is no buzzing sound. But to be absolutely sure, I have asked [MENTION=2999456]riaan0010[/MENTION] to test it too. If he confirms that there is no buzzing sound on 27 Oct nightly, then it means that the commit has been added on 28 oct.

This proves that [MENTION=1307550]pagoweb[/MENTION] 's guess was right about this commit being the culprit.

I am going to test the nightly of 28 Oct as well, but for now, lets wait for riaan0010's confirmation.

Update 2: one LAST nightly to test! If we get the buzzing sound on this one, then we will be absolutely sure!
[One (M8) Android Development] pauwie:
[MENTION=1307550]pagoweb[/MENTION], i dont have the audio issue anymore, i did a dirty flash and cleared cache and now 10 phone calls further still no buzzing.
[One (M8) Android Development] kadirpasa:
When will a build with this feature working come out. Also had any one have a good gallery app where I can move photos to other folders
[One (M8) Android Development] dalingrin:
I hope one day we will get to the point where the community is HAPPY to do a modicum of testing/bisecting to help out the one or two people who devote their free time to porting AOSP/CyanogenMod support. It is obvious that people have no idea how much time device maintainers spend working on this **** for free.
[One (M8) Android Development] Rouz.:
We all know for sure that our (almost) fully working CM build in here is the result of devs and device maintainers' work. If we are testing these builds, its for one reason: help you guys to solve this issue. At the end of the day you are the ones doing the hard work. The best that we can do is to point out when the issue was started. And that's what we are doing now. We all appreciate the amount of time that you spend working on this for free.
[One (M8) Android Development] L1nuz:
So where do we sign up? Is there a forum for us to have direct communication with the devs?

I think the frustration and critique here, is based on lack of communication.

You could have an army of people willing to help out, if you allow us to :)
[One (M8) Android Development] pagoweb:
glad it works good for you...

but maybe your volume isn't high enough.... it has been noticed that buzzing occured above 60-80% of max vol.

what feature ? root is present in this build, just not enabled by default.

to move photos you can use any app root capable (like a file explorer or why not a gallery app with root which idk if it exists).
[One (M8) Android Development] pauwie:
[MENTION=1307550]pagoweb[/MENTION], full volume 20+ phonecalls still nu buzzing.

Thanks for al the hard work, i use this rom as daily driver, stable enough imo. again thanks i'll keep flashing the new releases and give fedback.
[One (M8) Android Development] dalingrin:
Just to be clear, I am not doing much if any development on the M8 or any device right now. I come here as only a user.

The best way to get in contact is probably the #cm-htc channel on freenode. This channel is not officially a part of CyanogenMod or anything but several HTC device maintainers hang out there. Using this channel would be particularly useful if you've tested and have found a particular commit has caused a problem for you.

Many, perhaps even most, device maintainers tend to stay away from places like XDA. Users see this as frustrating, which is understandable, but from my experience it usually happens in order to keep the developer's sanity. Remember that many CyanogenMod device maintainers tend to work on several devices at the same time. The time to port and maintain one device can be burdensome but these guys are responsible for several devices.
[One (M8) Android Development] Rouz.:
Guys, I am now absolutely sure.

18 Oct: No buzzing sound (tested to the extreme)

23 Oct: No buzzing sound (tested to the extreme)

27 Oct: No buzzing sound (tested to the extreme) (same report by riaan0010 as well)

28 Oct: No buzzing sound (tested briefly)

29 Oct: BUZZING sound on FIRST TRY (same report by riaan0010 as well)

It must be this commit (as pointed out by pagoweb) which probably made its appearance in 29 October's nightly.

There is your culprit. Thanks to [MENTION=2906882]foamerman[/MENTION] , [MENTION=2999456]riaan0010[/MENTION] , and [MENTION=1307550]pagoweb[/MENTION] for making it possible to figure this out.

Happy fixing everyone.
[One (M8) Android Development] riaan0010:
New updates from dan panesan

Looks interesting

Link : http://review.cyanogenmod.org/83535
[One (M8) Android Development] riaan0010:
I emailed Dan Panensan this afternoon about the commit mentioned. Lokks like its been changed as per my previous post. Please can someone verify
[One (M8) Android Development] foamerman:
I'm just glad we could help out and we got it fixed :D :good:
[One (M8) Android Development] pagoweb:
those are already in noname55804's build.

i don't understand what should be verified ?

i'm not the one to be thanked on that one... you have to thank OP for today's build, and cm team for the fix. ;)
[One (M8) Android Development] riaan0010:
Hi Pagoweb.

Yes I know but it was updated again about an hour back
[One (M8) Android Development] Rouz.:
Are you guys absolutely sure that Dan Panesan's fix (today) is for the issue that we just found out?

I'm gonna give this new build a try. Fingers crossed.
[One (M8) Android Development] riaan0010:
No Im not 100% sure.
[One (M8) Android Development] Rouz.:
Looking at the commit that is causing the issue and today's fix, They seem to be touching different areas.
[One (M8) Android Development] pagoweb:
i think the update you've seen is because of this commit has been merged in cm-12.0 branch : no modification in code afaik...

---------- Post added at 10:32 PM ---------- Previous post was at 10:29 PM ----------

it seems to me they're all related to amps modification although in different project : device, kernel, qcom audio, ...

i really think it's (at least part of) a fix for buzzing issue which seems to be caused by bad levels or management of sound amplification ...
[One (M8) Android Development] Rouz.:
Downloading the new build now. I will report back,

Update: Dan Panesan's fix didn't solve the issue. I just got a really bad buzzing sound on 1/3
[One (M8) Android Development] krazie1:
Can anyone that knows how to revert a commit build a cm12 unofficial without this commit to check if this is causing it?

http://review.cyanogenmod.org/#/c/62582/
[One (M8) Android Development] noname55804:
If possible, i will, but this commit has been made on cm-11.0 does cm took all these commits over to cm-12.0 or did they started clean? If so there must be a similar patch on cm-12.0
[One (M8) Android Development] pagoweb:
i think this is the port of this patch for cm-12.0 : http://review.cyanogenmod.org/#/c/79958/
[One (M8) Android Development] krazie1:
They carried everything over so cm11 and cm12 have the same issues & fixes
[One (M8) Android Development] noname55804:
Thanks, then it´s easy to revert this.

I´m gonna do this tommorow. We have to see if this causes any disadvantages, if not i can upload the fix to cm´s gerrit
[One (M8) Android Development] noname55804:
Yeah but they´re using a completly different repo now ;)
[One (M8) Android Development] pagoweb:
here is a (non tested) build with this commit reverted : http://review.cyanogenmod.org/#/c/79958/

cm-12-20150104-UNOFFICIAL-m8
[One (M8) Android Development] riaan0010:
Okay Guys. just downloaded. Will test ASAP

First call okay. No issues
[One (M8) Android Development] GeektheMan:
Stuck in boot animation.

I flashed the latest CM12 nightly in system settings through the in built updater. Now I have been stuck at the spinning Cyanogenmod boot animation for more than a couple of hours. I'm certain that is not normal for an update to take that long. I can't use the hardware keys to even boot the device into recovery, and the device is heating rapidly. Please if anyone has a solution, or at least a suggestion, it would be greatly appreciated.
[One (M8) Android Development] riaan0010:
So okay, tested new build by Pagoweb for half an hour with emails calls etc.

Seems to me you guys found the culprit that was causing the buzzing sounds.

Well guys I appreciate all the hard work and efforts.

Will test further and give feedback if any problems occur.

Thanks again

---------- Post added at 07:25 AM ---------- Previous post was at 07:16 AM ----------

@Pagoweb, @krazie1 and @noname55804 thank you guys for helping the CM community sorting out the bugs
[One (M8) Android Development] Rouz.:
Wow this is really exciting! Downloading now! Thank you guys!
[One (M8) Android Development] Desaf:
Which one should I download?
[One (M8) Android Development] mattie_49:
Pagowebs 1/05 build above. No buzzing sound?
[One (M8) Android Development] Rouz.:
It's 1/04, I'm testing it now, so far no buzzing sound! I'm gonna test it a bit more before i can say for sure.
[One (M8) Android Development] amirfida:
Wow guys awesome work hats off to all the guys :), you guys are genius all the developers and testers :)
[One (M8) Android Development] Rouz.:
Buzzing Sound RIP

Congratulations guys! You have fixed it! No buzzing sound.

Words cannot describe how thankful I am for your hard work. Please submit the fix, and let's hope CM never breaks the audio again.
[One (M8) Android Development] kleptonez:
excellent stuff where is superuser?

great work!! just a qn, where is the superuser menu in the 20150104 build? do i need to flash supersu cuz i didn't flash in the 12-24 build.
[One (M8) Android Development] kadirpasa:
The update on that page is cm11 builds.

You have to now press and hold power and volume up until screen is ball than without letting power button go shift you finger off the volume up key and move it to volume down.
[One (M8) Android Development] kleptonez:
nvm, think i got it under developer settings.
[One (M8) Android Development] clay21:
You have to enable it from developer options.
[One (M8) Android Development] lotusboi:
?

Do I need s-off to do this and can I do it if i'm on android 4.4.2
[One (M8) Android Development] fdmitry:
It was great guys! The next long lasting problem is the Dt2W. In the past the commits, that cause the issue, were found:

http://xdaforums.com/showpost.php?p=56419016&postcount=3025

Perhaps we can revert them also in context of the current effort?
[One (M8) Android Development] lotusboi:
?

If im on 4.4.2 rooted and 3.4 kernel without s-off can i still do this?
[One (M8) Android Development] Rouz.:
This is interesting. Someone should try to revert those commits, and then we can test it to see if it fixes it.

You need a newer firmware. If you are s-on, you should go back to stock ROM and stock recovery and take the OTA to 4.4.4. Then you are good to go.
[One (M8) Android Development] noname55804:
Okay lets do this :)

Does the revert of the audio commit cause any disadvantages?
[One (M8) Android Development] Rouz.:
Thanks! I haven't found anything so far, I will continue testing and report back :)
[One (M8) Android Development] kadirpasa:
I don't have tap to wake issues in the new pagoweb build. I did on previous builds
[One (M8) Android Development] Rouz.:
In case anyone else had issues with titanium backup like I did, just flash the latest supersu from recovery.

Edit: [MENTION=5046290]noname55804[/MENTION] [MENTION=1307550]pagoweb[/MENTION] Here is what I tested so far:

Anything audio related works great. Including Ringtones and Notifications, Voice calls, VoIP Calls, Music playback, etc. I still haven't tested audio over bluetooth though. I will check that and report.

But it is safe to say that reverting that commit totally fixed the buzzing sound, without breaking anything.
[One (M8) Android Development] fdmitry:
Anybody else can confirm this?
[One (M8) Android Development] noname55804:
No commits were made on the responsible files so i think it isnt fixed
[One (M8) Android Development] smoki3:
Do you already started a commit on gerrit?

---------- Post added at 01:10 PM ---------- Previous post was at 01:01 PM ----------

I have a issue with lte signal indicator on the GSM Version.

If the signal goes under 140db it jumps to -1 ASU255 .

Heres the log

http://pastebin.com/AjB7sB46
[One (M8) Android Development] alershka:
WiFi Loss of Connectivity

I have noticed this pretty much since I have been on CM12. During the day, I have no issues with WiFi. Every night, I leave my phone on and charging and when I wake up in the morning, I am no longer connected to Wifi. I get a "Wifi Authentication Problem" when I look at the status in settings. I usually just on/off WiFi and it comes back. Any one else see this?

I did a logcat and found at just after 4am this morning, the following:

01-04 04:00:59.559 D/WifiService(754): New client listening to asynchronous messages

01-04 04:00:59.679 D/ConnectivityService(754): reportBadNetwork(NetworkAgentInfo [WIFI () - 103]) by 10018

01-04 04:00:59.729 D/ConnectivityService(754): NetworkAgentInfo [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from CONNECTED to DISCONNECTED

01-04 04:00:59.729 D/ConnectivityService(754): NetworkAgentInfo [WIFI () - 103] got DISCONNECTED, was satisfying 2

01-04 04:00:59.819 D/ConnectivityService(754): notifyType LOST for NetworkAgentInfo [WIFI () - 103]

01-04 04:00:59.819 D/CSLegacyTypeTracker(754): Sending disconnected broadcast for type 1 NetworkAgentInfo [WIFI () - 103] isDefaultNetwork=true

01-04 04:01:02.249 D/ConnectivityService(754): NetTransition Wakelock (NetworkAgentInfo [WIFI () - 103] cleared because we found a replacement network

01-04 04:01:05.529 D/WifiService(754): New client listening to asynchronous messages

01-04 04:01:10.539 D/WifiService(754): Client connection lost with reason: 4

After that, I have a whole bunch of "D/WifiService(754): acquireWifiLockLocked" messages and some sort of failed attempt to take a screenshot due to network connectivity.

01-04 07:46:58.388 I/WindowManager(754): Screenshot max retries 4 of Token{fab606e ActivityRecord{3017abe9 u0 com.android.settings/.Settings$WifiSettingsActivity t2521}} appWin=Window{25fae6f5 u0 com.android.settings/com.android.settings.Settings$WifiSettingsActivity} drawState=4

I have a Netgear WNDR4000 N router with 2.4 and 5 ghz radios. It is running the latest firmware (V1.0.2.4_9.1.86) I've tried both networks and the problem occurs on both. I am using WPA2 PSK security and am have DCHP on and use that for IP addresses on the M8. On the M8, I have the following under advanced WiFi:

Network Notification - On

Scanning always available - Off

Keep WiFi on during sleep - On

Avoid poor connections - Off

Wifi Frequency Band - Automatic

Also, thanks to all who have been troubleshooting the buzzing. :good: I have had the problem as well but I only receive a call or two a day so it was a tolerable inconvenience for me. I used to use the profiles extensively in CM11 so my work profile had the ringer set at like 30%. Since I am at work most of the time, that is probably why the issue didn't crop up too much for me. On CM12, I keep the volume at 50% and the buzzing does happen every once in awhile. I don't use the profiles because it doesn't seem like the play well with the new three notification modes and to a certain extent, the new modes superseded what I was using profiles for (turning off notification sounds, a silent mode, a vibrate mode, etc.).
[One (M8) Android Development] jureca:
Can not be installed ROM, you can indicate how to do, Google stock firmware 4.4.4, 2.8.1.0 TPRW recovery thanks
[One (M8) Android Development] mertokyay:
So far ROM is very stable on my end. There are some missing features like Tap&Pay with NFC and bluetooth smart lock. Wifi connection seems to weaken sometimes but again, its not a big deal as this is pre-nightly. If there is a way to make tap&pay work, I'll be pleased to learn!
[One (M8) Android Development] mcnaget:
Contact

Cant add a new contact any one with same issue.

THX

regards
[One (M8) Android Development] PhillyFlyer:
Contacts fc. Mehh
[One (M8) Android Development] Von Ropen:
Just instales and seems that work pretty well. Not problem with wifi nor data nor gps... Did not tested Bluetooth on my car...

Can someone tell me how can I make a capture of the screen???
[One (M8) Android Development] mcnaget:
Capture screen

PWR button and volume down button.
[One (M8) Android Development] Von Ropen:
Thanks for your reply, but seems that it not work... tryed power and home and does not work....
[One (M8) Android Development] mcnaget:
Capturen screen

pwr button and volume down button both at the same time works for me without any problems.
[One (M8) Android Development] RPG720:
No Root Access

Can't seem to get root working on this ROM. Tried to change the Access mode in the file manager's settings, which normally requires root, but no luck, not even a prompt or dialog box asking me to approve it. I also tried doing something that would prompt a root access dialogue in a play store application that I have used before (App Master) but no root permissions allowed to it, or prompt asking the user to make a decision. :(
[One (M8) Android Development] sardroid:
No problems with contacts-build 23112014:
[One (M8) Android Development] superior888:
How is batterylife?
[One (M8) Android Development] Von Ropen:
Ahhh I have to hold more time than with sense... Thanks
[One (M8) Android Development] RPG720:
Pretty good on my end. Better then Sense for sure.
[One (M8) Android Development] luttman:
i cant get sdcard to work :S any one lese with that problem?
[One (M8) Android Development] sardroid:
No problem here:
[One (M8) Android Development] jureca:
You can specify the installation? Gives me error in installation, thanks
[One (M8) Android Development] Von Ropen:
Instalo gapps and reboot
[One (M8) Android Development] jureca:
Thanks!,??
[One (M8) Android Development] luttman:
what firmware are you using?
[One (M8) Android Development] sardroid:
3.28.401.9
[One (M8) Android Development] lotusboi:
I thought HTC or at&t cancelled the 4.4.4 update on the htc one m8 because of bugs?
[One (M8) Android Development] pagoweb:
http://review.cyanogenmod.org/#/c/83040/

it seems that fix for t2w is on this way... in this fix, there is indeed some sep 16 commited changes that has been reverted (latest patch)....

imho no need to revert fo this one atm... better to pick this commit (@noname55804 already did in one of his builds) or wait for it to be merged...
[One (M8) Android Development] noname55804:
Yeah i did, i rebooted this morning and t2w still works, we´ll if this is the fix.

BTW all sensor related issue are due to the Sep 16 changes on this specific file

Here´s my fix:

http://review.cyanogenmod.org/#/c/83777/
[One (M8) Android Development] pagoweb:
not surprised... i was pretty sure this revert would be rejected...

indeed, we picked the easy way... a new feature (use of amplifiers was introduced with that 28th oct commit). this new feature introduced the buzzing issue (although this issue seems to be pretty random and seems to affecto only m8).

easy way : get rid of new feature ... how much time will it last till we need this new feature for other purposes....

hard (good) way : correct this new feature to get rid of the buzzing issue... so what are those amplifiers introduced in cm11 M11 for ? anyone knows ?
[One (M8) Android Development] Rouz.:
I thought this commit was device specific (only for m8). Which made me think they did this in an attempt to fix the speaker distortion.

I would choose the easy way. Honestly I think missing a yet-to-be-announced feature is a lot better than having those creepy buzzing sounds.

Just my two cents
[One (M8) Android Development] noname55804:
It´s not rejected yet :p

I´ll try removing the amplifier from the device tree now and see if that helps

I love easy ways :P
[One (M8) Android Development] pagoweb:
It is not device specific, it is hardware specific -> it's qualcom hard audio repo. and commits log and comments don't suggest it is a fix... yet i don't have history for this matter.

I can understand that ;)

so builders will have to revert this one manually (and eventually resolve merge conflicts) till there's viable fix for our device...
[One (M8) Android Development] noname55804:
It´s a device specific bug which is caused by a SOC related repo. i think it´s because the m8 is the only phone with dual speakers which uses msm8974 soc
[One (M8) Android Development] pagoweb:
wasn't talking about the bug... was talking about the commit (sep 29th which introduced amplifier use), the commit is hardware related i think
[One (M8) Android Development] fdmitry:
So once this patch, along with the reverting for the sound bug, are merged, we will get a pretty stable build, suitable for a first nightly. Do we have any other serious issue?
[One (M8) Android Development] noname55804:
Ah ok ;)

This is already included in my builds
[One (M8) Android Development] Rouz.:
Thanks for the explanation. It makes sense now. I just hope other builders revert this too. Believe it or not, this is the first CM12 build that I am actually using as a daily driver. CM was a no-go for me since the M12.

Please share the build once you did that. I can test to see if it works.
[One (M8) Android Development] noname55804:
Building right now
[One (M8) Android Development] heavymetall66:
Is it possible to make menu button working in your Rom?
[One (M8) Android Development] young440:
Does anyone know where I can find a newer bootloader version? The rom aborted the install because my bootloader was out of date. Bonus question, whats the easiest way to install the bootloader?