yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] lucize:
it is happening to me too, they are saying that I speak low, I called myself on another phone and the volume is low, I cleaned the mic gap without much effect, I'll see if I can boost the mic gain in the sound kernel drivers.

If you hold the hand in front of your mouth directing the sound towards the mic the volume is really loud and clean so I don't know what to say at the moment.

Regards
[Motorola Droid 4] sharptv:
Thanks for the response, I shall definitely try your suggestion.
[Motorola Droid 4] LuH:
Sounds to me like it might be some noise cancelling related problem then... Is noise cancelling implemented in the ROM? Is it some low-level driver or can it be adjusted?

I never experienced this though, usually I'm the one hearing bad... I'm on GSM network.
[Motorola Droid 4] daniel_m:
Hm, I still suspect my launcher (Apex Pro) to restart often and thereby drain the battery. aCalendar also seems to restart its widget quite often. At least Apex Pro is set to stay in memory, so it should never ever have to restart.

Also, WiFi is draining the battery like crazy and mobile data too... but I asume that's normal :(
[Motorola Droid 4] sharptv:
there's an option to disable noise cancellation is the dialer settings, not sure if it makes any differnce though, still testing it.
[Motorola Droid 4] daniel_m:
Is anyone else still experiencing that the sim card is not recognised every now and then (sim card symbol with a question mark in the status bar)?

There were nightlies some months ago that had this problem several times a day. Now I seem to "lose" my sim card once a week/month. The service menu (*#*#4636#*#*) says that my phone is connected to a GSM network, but I can only do emergency calls (network error). So the modem seems to work but I need to hard-reboot in order to connect to a GSM network. Maybe it's only to submit the PIN again, but I don't know how to do that without a hard-reboot...

Of course I will try to capture a logcat. Problem is that it happens randomly and seldom. My last logcat was 400kb big and I couldn't find anything overly suspicious.

--------------------

Concerning battery usage, I saw a lot of crashed apps in my logcat. Is the memory-management killing apps, even though it shouldn't?
[Motorola Droid 4] sharptv:
I have never experienced this issue myself, I am using my droid 4 with mentor's gsm patch. Perhaps you could try flashing mentor's latest patch, 3.2.2, which was released on 29th july think.
[Motorola Droid 4] daniel_m:
Thanks, I will try out his new patch! :)
[Motorola Droid 4] sharptv:
＠stargo, is it possible for you to release a build with this commit: http://xdaforums.com/showthread.php?t=2754997

we have discussed this before but you were probably too occupied; it looks really promising. I tried a rom with this tweak on my old g2 and the difference is quite noticeable.
[Motorola Droid 4] bofis:
I'd like to second this request, if it's even possible with our phones on this rom, it sounds magical ;) Anyway, has anyone gone from a nightly up to the M9 release from today? I assume that the nightly from yesterday, 8/03, actually includes newer changes and fixes so I'm never sure if I should care about Milestones if I'm on the nightly track...
[Motorola Droid 4] daniel_m:
As far as I know, a snapshot might break your nightly settings and mess things up because it does not contain all changes of the latest nightlies. Probably good to make a nand-backup first. Apart from that, if you are happy with a nightly, why install a snapshot?
[Motorola Droid 4] rblanca:
someone realized that on snapshot M9 home wallpaper looks misplaced?. Thanks!
[Motorola Droid 4] sharptv:
i went from 0801 nightly to the m9 and everything's fine, no missing settings or whatsoever.
[Motorola Droid 4] rblanca:
Bump someone? I need to know because it's only me i have to make a full clean/install...it happend to me on 04/08 daily too.. Wallpaper is not centered. Thanks
[Motorola Droid 4] daniel_m:
Sorry, I have not updated to the newest nightly yet. But installing the M9 snapshot on a new safestrap slot is quickly done. And then you can file an official bug report to Cyanogenmod (they support snapshots).
[Motorola Droid 4] bofis:
So my phone is running an 8/06 nightly that is not even listed on the site...was it pulled and should I not be?
[Motorola Droid 4] Mentor.37:
Screen wakes up after 5 seconds in incoming calls

In M8 and in M9 I noticed that when I receive an incoming call the screen stays black for about 5 seconds and then wakes up to displaying the options to answer.

Has anyone else noticed this problem?

I'm sorry but i have never had this problem.

I'm only updating from M to M and I have never had this problem.

Yes, me too I noticed this.
[Motorola Droid 4] thelolotov:
Is anybody else having problems on certain nightlies where sound just stops working entirely at times?
[Motorola Droid 4] rblanca:
Yes... It seems that it's fixed on next nightly ... but I don't know why but there are not newest nightlies since 0804 :S
[Motorola Droid 4] thelolotov:
I'm seeing an 8/08 nightly, downloading that now, what commit are you talking about? Glad to hear I'm not going crazy/my D4 isn't dying.
[Motorola Droid 4] thelolotov:
Still broken on 8/08.
[Motorola Droid 4] rblanca:
Yes it's still broken on 8/09 too...it's very annoying
[Motorola Droid 4] thelolotov:
Just glad it's not just me. Rebooting generally fixes, but it really sucks.
[Motorola Droid 4] sharptv:
to those using their droid 4 on gsm networks and are experiencing low in call microphone volume or muffled sound such as [MENTION=4772154]lucize[/MENTION] and myself, try adding "ro.ril.enable.amr.wideband=1" into your build.prop. Droid 4 is a hd voice capable device and that line has to be added into build.prop in order to enable it. I am not sure of its effects over cdma networks, but adding this line has definitely improved the situation over gsm networks.

p.s there's also a noise suppression option in the dialer settings, though i am not sure it makes any differnce.
[Motorola Droid 4] DiMacho:
In what line did you add "ro.ril.enable.amr.wideband=1" Want to try that, Vodafone NL supports hdvoice.
[Motorola Droid 4] sharptv:
I believe you can add it anywhere in build.prop
[Motorola Droid 4] bofis:
If Stargo or anyone else wanted to make a test build with that line added in, I could test how it affects the phone (if at all) on Verizon to see if that's a good change to just implement into the tree for everyone. Otherwise, I'm running the 8/11 nightly and my phone feels better than it has in the last week or two.
[Motorola Droid 4] sharptv:
You can just add it in yourself.
[Motorola Droid 4] joefuf:
How is that ROM overall?

Has there been a fix for that audio issue where the phone sometimes doesn't produce any sound?
[Motorola Droid 4] thelolotov:
As of today's build, still not. I'm backing up my slot and reinstalling from scratch.
[Motorola Droid 4] rblanca:
I was thinking in do the same, do you got any good result about sound issue?
[Motorola Droid 4] joefuf:
I haven't seen anything on the CMXLog page that addresses it. I always flash from scratch to be safe, but running the 7-31 nightly, I have the issue on my device.
[Motorola Droid 4] sharptv:
I am looking at the nightly change log and i notice this line:

Add an option in the InCall UI to perform call recording

does this mean that call recording will be integrated as a native function in the next build?

You can check the change log here: http://www.cmxlog.com/11/maserati/
[Motorola Droid 4] bofis:
I installed today's nightly and after making a phone call, I do not see any option to start recording the call. Perhaps our devices are not supported :-\

As for the audio bug, what exactly is happening, because I have not experienced any issues with audio playing on my phone, either out of it's speaker or via bluetooth, and I use my phone to play music on my stereo at night, and as an alarm clock every morning, and have not experienced any issues...
[Motorola Droid 4] rblanca:
The audio bug wich I'm talking about is this

https://jira.cyanogenmod.org/browse/CYAN-5004

I made the report and was assigned to stargos so let's wait to he take a look!
[Motorola Droid 4] apocalypse_bg:
I've went through the tread and can't get a definitive answer on what's the status/usability of the LapDock with this ROM. I'm interested in getting better performance from KitKat, ART and CM, but have a Lapdock 500 which I really enjoy using it. Unless Motorola doesn't share the source of Webtop 3.0, probably the experience with the docks won't be as good as with stock, I wonder whether using the webtop2 source might be of use, but still this leads to my question:

Can any current user with a Lapdock (preferably 500) share what's the status and what's missing/not working compared to the stock experience
[Motorola Droid 4] thelolotov:
From what I remember, you can force the resolution for the lapdock, and it works fine. Don't quote me on this. I would suggest just rooting, installing safestrap, and this ROM, and just try it!
[Motorola Droid 4] apocalypse_bg:
Actually just did that in the afternoon, but was on the move to edit the original post =)

From first glance, it looks like okay - phone is charing, keyboard is working, trackpad (mouse) is working, the SDcard is mounted, however i just get some thin lines on dark background. I suppose the issue is with the resolution as you suggested, will try to find about this "force hdmi" option
[Motorola Droid 4] thelolotov:
Believe it's somewhere in this thread, the instructions you need. I remember it being something you need to edit the build.prop to set.
[Motorola Droid 4] rblanca:
Has anyone tried nightly 08/15? Are background sounds are still broken? I know that https://jira.cyanogenmod.org/browse/CYAN-4665, wich I reported, it's fixed (thanks to Rajesh from CM)...but I don't know about background music/sounds and I can't test it ATM.
[Motorola Droid 4] stargo:
Yes, still broken (for many devices).

Cyanogen (Steve Kondik) is working on it now: https://jira.cyanogenmod.org/browse/CYAN-5004

Cheers,

Michael
[Motorola Droid 4] Khiraji:
Well, something finally broke for me in the 8/16 nightly... no apps could access the camera (stock camera app would FC and every other app would say "unable to access camera" or some variant thereof) and phone was crashing a lot. I did a full fresh install with the 8/16 nightly, to see if it was something in the ROM or an app, and lo and behold everything worked perfectly... and great googly moogly how fast my phone is!! Re-loaded all my apps with Titanium and now everything is working great, but that got me thinking: every 10 or so nightlies this seems to happen to me - something borks and I end up re-building everything from the ROM slot up. It's annoying, even with apps like Titanium.

Is there a way we should be upgrading to a newer nightly? Wiping cache (and/or something else) every time? Why is it that my phone seems to become incrementally slower (all-around sluggish performance, slow coming out of deep sleep, etc.) with each nightly I flash? What am I doing wrong here?
[Motorola Droid 4] thelolotov:
Good news, everyone! If you've watched Futurama, you'll read that in the professor's voice!

But seriously, supposedly Steve Kondik has fixed the issue! Should be fixed with the merge of

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

and

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

Last of which was merged at 1:55 PM on the 18th, so the 8/19 build should have the fix. Just hang in there, or if you really can't wait, you can always build it yourself!
[Motorola Droid 4] rblanca:
For me it's still broken on nightly 0819....
[Motorola Droid 4] thelolotov:
Well, that sucks.
[Motorola Droid 4] joojoobee666:
Confirmed. Just lost audio with supposed fix. Lost ALL audio. Killed mediaserver and back in business but this is definitely still unresolved (no need to reboot). :eek:
[Motorola Droid 4] stargo:
Hi,

@ everyone with audio-dropouts (not non-looping background-music): do you have "ok google" hotword-detection enabled and can you try disabling it?

Thanks,

Michael
[Motorola Droid 4] joojoobee666:
Never heard of it, but looked it up...definitely not. I'm using bare bones google services so maps and play store work but the search bar is disabled and Google Now/Search are not even installed here. Everything was fine on my last build from 7/31 at 3:37pm EST.

On a side note: I recall having to restart mediaserver process all the time on the initial KitKat builds but haven't for the last few months...until I tried a new build last night at 11pm.
[Motorola Droid 4] stargo:
Hi,

Hmm, ok. That would have been too easy ;)

Yeah, I fixed the problem which caused the dropouts the last time, but this is definitely something different...

Do you (or anyone else) have a way of reproducing it?

Does anyone remember when the problem really started? I saw some posts dating 0808, did it also happen earlier?

Thanks,

Michael
[Motorola Droid 4] joojoobee666:
I'll stay on these newer builds and see if I can find any common denominators, and if around a PC I'll get some logcat goodies. When it occurred this morning, I was switching from a game that had constant background audio to Firefox. When I switched back, the audio was gone (I did not exit the game).
[Motorola Droid 4] joefuf:
Disabled it and I'm 3/3 on reboots with working audio. Is that a known issue?

I am running the 7/31 nightly and I had this issue until I disabled "OK Google" hotword detection.
[Motorola Droid 4] thelolotov:
Can confirm, am also using "Ok Google" hotword detection... Damnit, I enjoyed that feature. Will try disabling.
[Motorola Droid 4] bofis:
I'm using "Okay Google" detection everywhere and have yet to experience a drop in audio. As in, phone audio, bluetooth music, and my morning alarms always play fine. Is this issue limited only to background music in games? Because that's just strange, and I rarely listen to or enable game music anyway on my phone.
[Motorola Droid 4] rblanca:
In next nightly 0821 app's sound/music issues should be fixed and also include stargo's fix to cam crash with "Ok Google" (thanks michael)...
[Motorola Droid 4] stargo:
Hi,

the fixes in 8/21 will most likely not solve the system-wide audio-drop which seems to be (at least partially) caused by the hotword-detection.

For this to be fixed I need your help!

If you experience missing audio the next time please do the following:

1. Run "tinymix >/sdcard/lost-audio.txt" via adb or local terminal while there should be sound-output (start an audio-player before doing so, for example).

2. Reboot to get sound back

3. Run "tinymix >/sdcard/working-audio.txt" via adb or local terminal while there is sound-output (same application as before would be best).

Then send me both files from the sd-card.

I'm pretty sure that a mixer-toggle gets in the wrong state and is not reset until the mediaserver is killed or its value is forcibly changes (by switching to speakerphone and back for example).

Looking at the experiments I did some time ago, I woul guess that mixer 67 or 68 gets set to a wrong value.

Regards,

Michael
[Motorola Droid 4] rblanca:
I would be happy to help you michael but it never happend to me...but i never used "Ok Google"....I'm going to enable "OK Google" to see if I can reproduce it...meantime lets hope someone affected by this issue can show his logs.
[Motorola Droid 4] thelolotov:
Regardless of whether it *should* fix it, it seems to have helped.
[Motorola Droid 4] rblanca:
After a day using "Ok Google"...i'm still getting sound... people who lost audio, are you using any xposed modules or xomething like that?
[Motorola Droid 4] daniel_m:
Michael, would you be interested in looking into the XPrivacy freeze issue due to the a lock in/by the activity manager?

Sorry to spam you both by private messages and here in the forum :rolleyes:

It's just that XPrivacy is the most important app to me and it would be great to see it doing it's job without the on-demand pop-ups being frozen sometimes. Apparently some other ROMs (based on AOSP?) don't have this issue.
[Motorola Droid 4] thelolotov:
I was having the issue, but I've never used Xposed or anything particularly extreme.
[Motorola Droid 4] joefuf:
The only module I am using is Wakelock Terminator for the NlpCollectorWakeLock issue. Everything was resolved for me after I disabled the OK Google option from any screen.
[Motorola Droid 4] rblanca:
After almost 2 days being using "Ok Google" I'm still getting sound, music, etc...I haven't any issues....I'll stop using "OK Google" because I only enabled it to test that issue and it's usseles for me (I always have much noise arround me). Would be great if those who are having that issue turn on OK Google and give to michael the logs that he ask. Thanks
[Motorola Droid 4] joefuf:
I'd be happy to post my log if someone could explain what this means.I don't know if tinymix is an app or a ROM tool or anything.
[Motorola Droid 4] rblanca:
"tinymix", it's a command console, in this case, using the apk "Terminal" (that apk it's included by default on CM)...you have to type what stargos and hit enter....

When you lost sound, open Terminal apk and type:

tinymix >/sdcard/lost-audio.txt

When you hit enter, that command will create a file named lost-audio.txt in you sdcard folder...aka internal memory of the phone.

Then restart your phone and you sould get sound working again and then like you did before open Terminal apk and type:

tinymix >/sdcard/working-audio.txt

When you hit enter, that command will create a file named working-audio.txt in you sdcard folder...aka internal memory of the phone.

Finally you post or send those two files working-audio.txt and lost-audio.txt to stargo's...and that's all :)

P.S.: Sorry 4 my crappy english...
[Motorola Droid 4] daniel_m:
Did anyone notice that sounds are louder with the latest nightlies? I don't know if the maximum volume is higher, but the lower volume levels seem to be much louder. I used to have the ring and notification tones on 4, and now I have it at 1 and still think it's kind of loud ...
[Motorola Droid 4] croolyc:
Hi!

How to enable led in charching??
[Motorola Droid 4] bofis:
While that option is present in CM11 for some devices (such as the Razr M) it does not appear to show up for our device. Possibly there's an xposed module or you could try Light Flow
[Motorola Droid 4] joefuf:
Thanks man. I'll have some time either tomorrow or Thursday to give this a try.
[Motorola Droid 4] thelolotov:
I turned on Ok Google detection and had an audio drop after several days of no problems.
[Motorola Droid 4] thelolotov:
Is anyone else having a problem with everything crashing, and the ROM constantly soft-rebooting? On build from yesterday.
[Motorola Droid 4] joefuf:
When I try to do this, I get an error that says "Failed to open mixer"
[Motorola Droid 4] rblanca:
Same for me lets waits to [MENTION=3457922]stargo[/MENTION] to take a look :S ...
[Motorola Droid 4] stargo:
Uhm, my fault :(

You have to be root for tinymix to be able to access the mixer, so run "su" first.

Regards,

Michael
[Motorola Droid 4] joefuf:
Cool, that made a txt file, but it's blank. Tried it to my sdcard and sdcard-ext to see if that'd make a difference, but no change.
[Motorola Droid 4] apocalypse_bg:
Anyone any success in using the Lapdock 500??? I still can't find the HDMI fix that someone mentioned upwards.
[Motorola Droid 4] sm4rty:
yeah me neither. im looking for it too for using my lapdock.
[Motorola Droid 4] xantanion:
Look at the work of lucize for the hdmi tweaks.
[Motorola Droid 4] apocalypse_bg:
Tested the 24.07.2014 kernel from him with the m9 snapshot, maybe it works with regular TVs (don't have a microHDMI to full connector yet), but not with the Lapdock :(
[Motorola Droid 4] stargo:
Hmm, did you first ran "su" as command or did you just prepend it to the command-line?

Please use two commands, as when running it as one command (su -c ...) breaks line-feeds for some reason.

su
tinymix >/sdcard/working.txt

Verify (cat /sdcard/working.txt):

root@cdma_maserati:/ # cat /sdcard/working.txt
Mixer name: 'motsnd'
Number of controls: 107
ctl	type	num	name value
0	ENUM	1	DL1 Equalizer Flat response
...

Cheers,

Michael
[Motorola Droid 4] joojoobee666:
Stargo, I had the audio cut out on me again today while using waze. Unfortunately, I forgot to get the logs but something peculiar happened that may assist; after I killed Medaiserver and all the audio that didn't play all played at once. Basically, it was all queued. This would seem to kindicate that it was simply not responding to any audio playback requests (hung) as opposed to the volume getting set to 0. Maybe it helps? I'll get logs the next time it occurs.
[Motorola Droid 4] joefuf:
Thanks man. I didn't realize I needed to give Terminal superuser permissions like that.

Here is a working audio txt, but I've re-enabled OK Google from any screen, and I've been rebooting all afternoon trying to get an instance where the audio doesn't work, but it has been fine so far. I will update if it happens, and I'll post the txt for that.

This txt was from before I re-enabled OK Google, so it should be a true showing of a working phone.
[Motorola Droid 4] stargo:
Ugh, that's probably the same problem I solved with sound-output getting stuck now caused by the input. I can't find an obvious second call to poll which would cause this, though...

If you loose sound again, could you also please try to see where mediaserver is actually hanging before killing it?

su
strace -p XXX >/sdcard/mediaserver-strace.txt
(wait a few seconds)
ctrl-c (ctrl is mapped to OK in VX connectbot)

XXX is the PID of mediaserver

Thanks, your working.txt looks fine :)

Cheers,

Michael
[Motorola Droid 4] joefuf:
Got one! I don't remember 100% for sure, but the audio may have been working fine on this reboot. I went back and checked the phone just now and I could not play any music with Apollo and I could not hit the volume rocker and here the little "blip" as I progressed from Vibrate to Ring.

Not-Working log txt attached!
[Motorola Droid 4] joojoobee666:
Will do.:good:
[Motorola Droid 4] shaka_yonqui:
greetings

Why I can not install the versions of late August and September? I get error in the partition ...
[Motorola Droid 4] bofis:
What slot are you installing it into? I use the Stock slot and am running 9/02's nightly without any issue. In fact, battery life has never been better since I wiped data and started from scratch this weekend.
[Motorola Droid 4] sweetsuicide:
Hi guys, I installed the latest milestone and I was trying to test the HDMI functionality, but it seems like it's not working. Could someone help me?
[Motorola Droid 4] daniel_m:
I connected my Droid (running the 20140905 nightly) to my PC-screen yesterday and the display rotated into landscape mode and got mirrored right away. Don't know if audio works since my screen doesn't have loudspeakers.
[Motorola Droid 4] bustr85:
I've been having the same problem for a while, currently I'm on the 10th of September nightly, still no improvement. Making the phone pretty unusable.
[Motorola Droid 4] thelolotov:
Couldn't take it anymore, I just started from scratch, issue went away. Was overdue for a clean install anyway.
[Motorola Droid 4] joefuf:
A clean install was all it took to fix your issues? I've been thinking of upgrading to the latest nightly, but your reboot problems were one of the reasons holding me back.

I'm on a 7-21 ROM. Any improvements/deficienciees worth noting since then?
[Motorola Droid 4] bofis:
YES! You can now assign something like long-pressing on the Menu key to swap to "last app" in the settings, which is amazing. Also there have been millions of changes and fixes since 7/21. I am running yesterday's nightly with no issues at all, and also recently did a fresh install which fixed any lingering issues, including speed. My phone used to lag a bit more before doing a fresh install, and I think it had to do with old governor and CPU settings. Since reinstalling, I have not even gone into the Performance section in Settings, and feel like whatever defaults are set, are better anyway.

Unfortunately, even with the option enabled, call-recording does not seem to work for our device. The dialer just writes a silent file into the call recording folder.