[Eee Pad Transformer Android Development] timduru:
What kind of screen saver are you using ?

Also which kernel are you using, try to switch to KatKernel if you're using EOS4 default kernel, or vice-versa.

And yep, as I don't have these kind of issues I need all the logs you can gather ;)

Also make sure you test and reproduce the issue:

- without being overclocked

- without an SD in the dock

To gather the logs before the reboot run that in 2 different terminals before letting it go to sleep:

Terminal1:

cat /proc/kmsg > /sdcard/kmsg

Terminal2:

logcat > /sdcard/lc

And let these run until it reboots. (check from time to time that it's still running)

After the reboot grabs the /sdcard/kmsg and /sdcard/lc files.

There should be no differences performance wise between 134 and 136, just the mounting feature for CIFS & K.A.T..

Or if there's a speed difference it's a "good mistake" as I had made quite a few changes tests in between,

but they should have all been reverted back before I compiled 136 normally *g* ;)

So if there is really a speed improvement let me know quickly ;P

Yeah same for me, I used to have it occasionnaly in the very first JB versions, but it's fixed since then.

And I've not had any sound issues for a long time now.

It seems to be either for a few specific models / revisions (indicates your model versions in the report),

maybe like the few RR or SoD that are left too.

Actually that could be interested to try to see: the few having the sound loss left, do you also experience RR or SoD ?

My main Hypothesis however is that the few sound issues left are most likely caused by something specific on these user's tablet,

an app or the way they are using it.

Sound has changed again quite a bit in JB4.2.1, so if an app incompatible with JB4.2.1 is restored or used, that could definitely generate issues.

alizafar & just lou:

As you two seem to be able to reproduce the issue easily,

yep I'd need the logs from you.

Try to reproduce the issue

without restoring anything

on your tablet too.

The sooner you can reproduce the issue after you boot, and with the less stuff installed on your tablet,

the easier it'll be for me to try to see something in the logs.

Try to reproduce the issue without an SD in the dock in case you have one.

Just follow the "How to report" & "What to send" procedures in my sig.

Try to be as precise as possible in what you have been doing on your tablet from the boot to the sound loss.

the apps you have used, the apps that are loading on boot,

Also run this in addition after the sound loss:

katmix > /sdcard/km

cat /data/system/packages.list >> /sdcard/packages

cat /data/system/packages.xml >> /sdcard/packages

and post the /sdcard/packages & /sdcard/km in addition.

so that I can see which apps you have on your tablet:

Also describe what you call sound loss, is it "no sound at all" or "sound is of bad quality"

Does hitting reinit FM34 DSP alone on the K.A.T app brings it back or do you have to hit the apply profile button ?

One person who had also sound loss reported to me that after uninstalling the Music + Music FX apps

he didn't have any sound loss anymore.

Could you try that to see if that helps and report after you did ?

No it's better to not unplug or eject directly.

Unmount first :)

*g* good :)

Yep, see Known issues & workaround in my signature.

I think I'll try to work again on that next in background.

The thing is that we rely on binaries for that.

It's either the swipe feature or the autocorrection crash

Even if you have the choice by flashing it'd be better to get the default autocorrection back instead of swipe by default ?

What would you all prefer as default for the moment ?