yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] saiftheboss7:
Here's the log: modem+kernel log

The sound bug is very irritating.. :(can't listen to music and videos. There's also no beeping when a third call comes while talking. See if you can fix it Krystian. However, this is only present in the last two builds. It is not present in the past builds.
[Atrix 4G Android Development] rhcohen:
Will test and post logs tonight U.S. time (for voice recognition and skype failures). Meanwhile -- I sent you (@krystianp) p.m. re config diffs between Jan 18 kernel where voice recognition worked and next one (Jan 26) where it didn't (on CM10.1). I also noted there that your post about how to find pinmux settings in kernels (look in /d/tegra_pinmux) doesn't work for me as that file is empty (zero length). Can anyone tell me if there is another way to determine these settings for one of the past kernels (without access to the source)?
[Atrix 4G Android Development] todobarato:
Hello,

my kernel.log, I take after Skype failure.( the mic doesn't works by start the call, but if you change the sound to speaker-phone, the Mic start to work, it is like this all the time).

Radio.log, it worked data connection some hours OK, later by make speed test it loss the data connection and only comes back with reboot. The GSM connection doesn't drop and works all the time correctly.

Best regards.

Edited: kernel used was date: 02.14-18.09 on CM10.1
[Atrix 4G Android Development] tonglebeak:
Hi. Not sure of the relevance, but I'm getting complete audio drops on the entire system now. Speaker will stop working until I do a reboot. A dmesg is attached if that helps.
[Atrix 4G Android Development] bobmorsy:
About the complete audio drops I had this issue too, and I couldn't even hear the ringing beep whenever I called someone, and the call waiting beep as well..I fixed this by reflashing the ROM and the the latest kernel..so I guess it was the ROM messed up.
[Atrix 4G Android Development] rhcohen:
logs attached

I've attached 4 logs showing 4 variations on the problems I observe. All are on the 02_14 (latest) kernel, with epinter CM10.1 from December. All are running the indicated app following a fresh reboot. The 02_14 kernel was installed following wipe cache & dalvik.

dmesg5.txt: Google voice typing failure, using GV typing to type a note with Catch Notes. (The time to first failure seems to have gotten shorter with the more recent kernels, but maybe this is related to passage of time rather than the kernel changes??)

And the following 3 with Skype, calling the Skype call testing service, where you record something and skype plays it back to you:

dmesg6.txt: Audio drop-outs seemingly related to proximity sensor (screen blanking). Never did get to hear playback of my voice.

dmesg7.txt: Keeping phone sufficiently away from body that screen doesn't blank. Uninterrupted audio from Skype, but what should have been playback of my voice is white noise.

dmesg8.txt: Using speakerphone. Skype works perfectly in this case; including log for comparison.

Note all dmesg logs were generated via the Terminal Emulator, immediately following running the apps as described above.

The only thing I see looking at the dmesg logs that might suggest trouble are lines like:

binder: 509:887 transaction failed 29189, size 216-0

in all of the files.
[Atrix 4G Android Development] krystianp:
I prepared new kernel, only for audio related issues. It might work differently (not necessarily better). I'm waiting for your comments on it. Also logs will be welcomed.
[Atrix 4G Android Development] rhcohen:
Are you considering the voice recognition (Google Voice Typing, Google Voice search, etc) problem as "audio related"? I am wondering whether to take logs related to that or just Skype for this latest kernel. (I have had issues with Skype since before the voice recognition issue started, and in fact on all kernels I've tried, though the nature of the problem would change from kernel to kernel.)
[Atrix 4G Android Development] krystianp:
Google voice is audio related issue but I don't know if it's pinmux related or not. Best way to find out if it's pinmux related is to watch life kernel log via adb and look for any ALSA MOTSND and tegra_pinmux_set_tristate (CDEV1, DAP1-4).
[Atrix 4G Android Development] rhcohen:
[MENTION=4641721]krystianp[/MENTION], your latest variation is quite interesting: first, it seems to have fixed google voice recogntion/google voice typing. However it seems for me to have broken a number of audio related issues: It appears that on a fresh reboot I can do one thing involving sound: make a skype call, do google voice typing, make a regular phone call. After that, google voice typing continues to work, but if I make another phone call, skype call, etc, I get no sound (and the other side can't hear me -- I tried calling my landline).

I am attaching one log, dmesg9.txt, following successful test of google voice typing into a Catch note (same as in the last batch of logs I sent). I need to do other things now but will create a more systematic set of tests and logs tonight (U.S. time) if that is still of interest.
[Atrix 4G Android Development] iko11:
With the last couple kernels sometimes all system audio goes off how i can get these logs after audio went off i am running epinter's CM10.1

MB860 cihazımdan Tapatalk kullanılarak gönderildi
[Atrix 4G Android Development] krystianp:
New kernel with audio fixes is ready (previous is deleted). I'm waiting for audio bug reports (and logs).
[Atrix 4G Android Development] bobmorsy:
I have no audio at all with last 2 kernels...this one and the one deleted.

earpiece, speaker don't work using any app, even in call.

only mic works, but it didn't work on the deleted kernel.
[Atrix 4G Android Development] saiftheboss7:
Here's The New Log For You Krystian. Sound has gone wrong in this build

kernel-2014_02_16_23_42_cm10_1 has gone wrong completely. I cannot even listen the call voices or the call's ringing. No phone audio also. Can't report Random Reboots/Modem drops because I have to switch back now.
[Atrix 4G Android Development] rhcohen:
[MENTION=4641721]krystianp[/MENTION], the latest kernel is also very interesting. With this kernel things seem to work consistently until I go to make an ordinary cell phone call. That is, skype in one of speakerphone/no speaker phone modes but not the other (see below), google voice typing, playing back sound from a recording app. Even GrooveIP, a VOIP service that uses Google Voice. I can do any of this repeatedly. But if I try to make a phone call using cell voice, I hear nothing, the other side hears nothing (as reported with the deleted kernel), and thereafter I can't use any of the other services. It seems as though the phone is grabbing and not releasing the audio (some pinmux that should be, but isn't, reset on conclusion of phone call?)

I briefly re-installed the earlier (deleted) kernel. I think my earlier description was a bit wrong -- I'm not sure there is any consistent difference between the behavior of these kernels, for me.

With either kernel Skype seems to not have predictable behavior -- sometimes speakerphone mode works, some times non-speakerphone mode works. When a mode doesn't work I get white noise on playback of the Skype test call. There seems to be a correlation between speakerphone mode working and the volume control having an effect on speakerphone volume.

The thing that is consistent with both of these kernels (for me) is that an ordinary cell call never works, and once I attempt to make one everything else to do with audio is broken. The other thing noteworthy is that if I don't make a cell call, google voice recognition works as it should -- so something you changed between 02_14 and 02_16 seems to be the key to that problem that we've been having on CM10.1

Too tired now to gather kernel logs. Will do that tomorrow if there is still interest.

I am wondering if the other people who have reported audio problems with this kernel tried testing audio before trying a phone call.

---------- Post added at 02:01 AM ---------- Previous post was at 01:39 AM ----------

Small update: Google Translate, it appears, is just as effective as making a phone call in crashing the audio apps. That is, if I run Google Translate, it will translate on the screen but will not speak the translations, and thereafter no other audio apps work (just like using the phone as a phone). Will take log of this tomorrow (oops, I mean later today) if of interest.
[Atrix 4G Android Development] todobarato:
Same here, no sound at all...
[Atrix 4G Android Development] lightlord:
Same, here. No sound on call, reverted back to 2212.
[Atrix 4G Android Development] krystianp:
New kernel, again ONLY audio related.
[Atrix 4G Android Development] iko11:
Now after a call system audio has no problem but during a call no voice, no ringing tone on call also the person who i called can hear me but i cant hear them

Logs: https://www.dropbox.com/s/6sk5oe0dqzmhwak/Logs.zip

MB860 cihazımdan Tapatalk kullanılarak gönderildi
[Atrix 4G Android Development] krystianp:
Another kernel update. Maybe this time calling will work.
[Atrix 4G Android Development] iko11:
I wil try now and let you know

EDIT: During call no problem, after call no system audio problem yes now it works you are great :)

+I am not sure if its kernel related but i couldn't record video more than five seconds it was freezing and always there was an empty file but now i am able to record videos with last kernel

MB860 cihazımdan Tapatalk kullanılarak gönderildi
[Atrix 4G Android Development] krystianp:
We need some more testing. Various apps, configurations, modes with bt, headphones, speaker etc. But I'm glad things are getting better.
[Atrix 4G Android Development] todobarato:
Hello,

With 02-17_14-57-CM10 sound works again, on call, music plays, but in Skype the Mic bug still present (for working Mic you need to change to speaker phone and start to work).

Sent from my MB860
[Atrix 4G Android Development] sandeep1415:
Sound is working fine during calls....will update the progress as the testing goes on(with headset bt and different apps)
[Atrix 4G Android Development] rhcohen:
Skype issues

I will test the latest kernel shortly; but based on some tests I did last night, I think the Skype issue may well be ROM-related, not kernel -- are you on CM10.1 (as I am)? (No entry for which ROM from you in the spreadsheet).

That is to say, I have had these issues with Skype on every kernel I've tried since the current CM10.1 came out (and maybe on previous epinter releases, can't recall). I had thought the behavior (whether Skype was working with speakerphone on, noise with speakerphone off, or the oppposite) was changing with kernel. But last night I found that with repeated attempts to call the Skype test calling service I could get the problem to more or less randomly switch. It seemed like (but I'm not sure) I could always get speakerphone to work by fiddling with the volume control while the greeting was on, until the volume control actually changed the volume (often when I first start up skype, the speakerphone volume seems to be loud independent of where the volume is set; rocking volume up and down seems to fix that, and then skype will work on speakerphone.) Whereas I have no recipe for it working without speakerphone, seems random. But always skype drops out if I get the phone near my body so the proximity sensor blanks the screen.

So, [MENTION=4641721]krystianp[/MENTION], should logcats should be taken with regard to skype mic problems, and if so where posted? Maybe at the CM10.1 forum? I guess the answer to where post depends on whether anyone has these problems on an ICS ROM.

---------- Post added at 10:20 AM ---------- Previous post was at 09:46 AM ----------

With the latest (02_17) kernel, everything I've been able to test in 10 minutes of use seems to be working, except for the Skype mic problems. Phone. Google voice recognition (for Google Voice typing, google translate, etc), GrooveIP (VOIP app). A recording app (can record and play back). I can go back to any of these and they still work. Very nice! So, probably no need for dmesg logs?

The one thing still broken (so far) is the Skype mic problem, and I am suspecting this is not a kernel problem (see my post from about an hour ago), or if it is, something completely unrelated to what [MENTION=4641721]krystianp[/MENTION] has been changing in any of the kernels in 2014, as I am realizing that the behavior has pretty much been the same for all kernels. I have two separate issues with Skype, one being working with speakerphone vs non-speakerphone, which I think started with some version of CM10.1 (can't remember if it is the current one), and the problem of the sound blanking out when the screen is blanked by the proximity sensor, which I think has been a problem for me going back even to CM10.
[Atrix 4G Android Development] todobarato:
Hello,

In CM9 is present too, so isn't ROM related.

rhcohen: (But always skype drops out if I get the phone near my body so the proximity sensor blanks the screen.)

This is one bug but on new Skype, it is present on CM7 too, I have reported to Skype but you know, old phone, I dont think that it will be fixed. I use the last old version that works OK and is the 3.2.0.6673.( note: if you have installed the new one, uninstall it before install the old one, it start to make strange thinks.)

Best regards,

Edited: Bluetooth music streaming works Ok.
[Atrix 4G Android Development] ubunthero:
The latest kernel is perfect for me, no sound problems anymore (but I never use skype)
[Atrix 4G Android Development] Voldemort:
No audio problems during standard phone calls, but Google voice is not working at all on the latest kernel (at least it worked for 5-10 seconds before).

Candy crush now works (didn't work with the other recent kernels) :rolleyes:

I will test Skype later and post dmesg results.
[Atrix 4G Android Development] krystianp:
Candy crush had audio issues?
[Atrix 4G Android Development] Voldemort:
Nope, it had screen tearing issues, but only on february kernels. Now it works as it used til january.

I think I mentioned it back when epinter was still releasing rom updates and some of them gave me the same issue, but I never thought it was important because it's just a silly game...
[Atrix 4G Android Development] krystianp:
Thanks for clarification. I did two changes related to clocks of dsi. It looks that is has some effect after all (I was planning to remove this change).
[Atrix 4G Android Development] Voldemort:
In this case I'd say leave it as it is :)

I found it strange that no one had issues like me on Candy Crush (considering how many people play it), but after all it's just a game and probably no one really complains on the kernel thread if a game doesn't work.

Once again, thanks for all your effort :good:
[Atrix 4G Android Development] tonglebeak:
The only game that gives me audio problems is Bouncy Seed. Basically, in gameplay, whenever a sound is suipposed to be played, the game will freeze most of the time for a second or two, then the sound plays and the gameplay resumes. Rinse and repeat. I will say that the problem exists only after flashing to CM10.1 though. It did not exist on CM9. Likely a ROM issue, but figured I'd throw this in there too.
[Atrix 4G Android Development] rhcohen:
voice recognition issue

Very interesting -- Voice recognition seemed to be working for me all day yesterday following installation of the latest kernel, but this morning (U.S. time) I see that it is broken for me as well! I guess I just didn't test it for long enough yesterday. Everything else with audio seems to be working for me, except for the Skype problem which has been there all along. And in 24 hours no reboots, phone hangs, etc.

So I guess my summary for [MENTION=4641721]krystianp[/MENTION] is that this latest kernel behaves for me about the same as those from Feb. 5, Feb 10 and Feb 12.

I just tried one of the kernels with broken audio from this weekend (Feb 16) to see if voice recognition is restored. It is! [MENTION=4641721]krystianp[/MENTION], how many changes did you made between the last two kernels? it seems that one of them is likely related to the voice recognition problem.

[MENTION=462587]Voldemort[/MENTION], I am curious if you have access to one of the kernels from Feb 14-16, and if so can you flash it and see if voice recognition works for you? And do you have access to a kernel from before January 26 that you could try for the same purpose?

Unfortunately the third person who had seen this problem is [MENTION=1567750]txtsd[/MENTION], and he is having other issues which are rendering his phone unusable, so at least for now we won't have data from him.

It would be nice to know if anyone running CM10.1 can actually use Google voice recogntiion for an extended period of time with the latest (or any recent) kernel.

---------- Post added at 10:59 AM ---------- Previous post was at 10:12 AM ----------

Another clue: after going back to the Feb 16 kernel (which restored voice recognition) and then back to the latest (feb 17), google voice recognition is still working. So something in those kernels with the broken audio resets something in the phone so voice recognition works for a while. This is NOT the case for the earlier (before Jan 26) kernels -- I could switch back and forth between a pre-Jan-26 kernel and a Jan-26-or-later kernel and the voice recognition problem would toggle between "off" and "on" with not much time required for the problem to recur on the post-jan_26 kernels.
[Atrix 4G Android Development] iko11:
Candy Crush has screen tearing for me too even i flashed the latest kernel but i don't like playing games so it doesn't matter if it works

MB860 cihazımdan Tapatalk kullanılarak gönderildi
[Atrix 4G Android Development] douglasroos:
Can someone report about the using of Zello app? I can't send a voice message because the audio does not work at all after that.
[Atrix 4G Android Development] rhcohen:
which version of ROM and kernel are you on?
[Atrix 4G Android Development] douglasroos:
I'm on AtrICS 2.0 and using latest kernel from dropbox. It works sometimes but after that it loose the audio at all. This app for me is essencial

Enviado desde mi MB860 mediante Tapatalk
[Atrix 4G Android Development] metalci melek:
My problem is battery life. Its too short.

MB860 cihazımdan Tapatalk kullanılarak gönderildi
[Atrix 4G Android Development] jisse44:
Hi.

I reported few days ago that screen is waking up regulary when charger is plugged. I don(t know if it's kernel related, in my memories december kernel was ok.

Here's the logcat, from charger plug to screen wake up at lines 02-19 08:04:55.636:
[Atrix 4G Android Development] krystianp:
Phone doesn't go to deepsleep when charged.
[Atrix 4G Android Development] saiftheboss7:
Is it normal? I mean, do all phones not go into deepsleep while charging? :)
[Atrix 4G Android Development] ravilov:
All Atrixes are like that.
[Atrix 4G Android Development] krystianp:
When phone is in deepsleep, usually only modem is working. Most of other hardware is shutdown. There is a bunch of hardware IRQs that can wake up the phone (modem, key, usb, sensor) and those are staying on (if needed). I suspect it would be possible to make external power provider for battery that would charge without waking the phone but is see no reason for that (after all you are providing power, so there's no need for extreme power saving).
[Atrix 4G Android Development] renoob:
Hi,

May I ask what rom you are using in this screenshot?

I see Blur ICS in your signature, is it the leaked one?

Thank you
[Atrix 4G Android Development] jisse44:
So screen on/off every 4-5mins during charging is normal ?

Weird.....

Send from my Atrix 4G
[Atrix 4G Android Development] Feche:
AFAIK, all Android phones don't go to ds when they are charging.
[Atrix 4G Android Development] sunaku:
I've had a pretty good experience with kernel-2014_02_10_01_49_cm10_1 and kernel-2014_02_17_14_57_cm10_1 on the MIUI ROM (see http://xdaforums.com/showthread.php?t=2605995 for details) and I have posted my feedback on the modem drops spreadsheet. :cowboy:

The only problem I've had is that sometimes the screen doesn't wake up from sleep immediately. Only the hardware buttons light up and the screen stays off. In such cases, I have to press the power button again to turn off the hardware button lights, wait for 5 seconds and then press the power button again to turn on the screen. :angel:
[Atrix 4G Android Development] ravilov:
Well, not exactly. The phone never goes to deep sleep while charging (like Krystian said, there is no need for that much power saving), but the screen should remain off the whole time, unless you turn it on yourself. The screen coming on like that is most commonly a sign of some app misbehaving.
[Atrix 4G Android Development] rhcohen:
Hello, your post says "wait for 5 seconds" but your entries on the spreadsheet say "wait for 2 minutes". 5 seconds seems not so bad; 2 minutes is very different. Which is it, or am I getting confused?

Also -- have you tried anything involving voice recognition (Google voice search, voice-composed emails, Google Translate,...) with your combinations of ROM and kernel? Several people running CM10.1 (including me) have had problems, though a first instance of the problem seems to require a long batch of voice recognition (e.g. voice-typing a long email message). I seem to be doing OK on the 2014_02_17 kernel with short messages.

I am also curious, was there something broken with just the flash of the MIUI ROM that was fixed by the recent kernels?
[Atrix 4G Android Development] BigJeff:
Don't use this kernel because I no longer use my Atrix, however I'd like to share a project I'm working on. Breaking down my Lapdock and turning it into a Monitor!!! http://xdaforums.com/showthread.php?t=2654929 Tutorial comes when my cable arrives! BTW shout out to krystian!
[Atrix 4G Android Development] sunaku:
Sorry for the confusion. :o When the problem does occur, the "wait for 5 seconds" method usually suffices. However, a few times even that did not work: I tried again after a few minutes and the screen turned on. I think this is all related to how the phone wakes up from sleep: if it has been sleeping for a long time, say half a day, then it takes longer to wake up. At least, that's what I've observed. :cyclops:

Per your instruction, I just tried out Google Voice Search and Google Translate and both of them worked fine for short messages. :victory: But I did not try longer e-mail dictation because I don't want people to hear :o my e-mails. :eek:

Yes, the MIUI ROM uses an older version of this new 3.1 kernel which has an annoying bug: the screen does not wake from sleep every time. The "wait for 5 seconds" method was the only work-around. But thankfully, Krystian's newer kernels have largely eliminated this problem! :angel:
[Atrix 4G Android Development] rhcohen:
Thanks for the clarification!

RE voice recogntion, can you try a long email dictation with something you don't care about? You don't have to actually SEND the email :). (or alternatively enter text in a note-taking application or text editing application). It will be really interesting if the combination of MIUI ROM and latest kernel fixes what still seems to be a bug with the epinter ROM and latest kernel.
[Atrix 4G Android Development] sunaku:
Alright, I did a longer (roughly 3 minutes) test and there were no crashes or kernel bugs. :victory:

The only unsatisfactory result was the inaccuracy of Google's voice recognition system: :silly:

Let me know if you need any more information.