[TESTING] - NAND OMGB (1.2.3)

[eurohunter]

Originally Posted by arrrghhh

I'll try to recreate this on HaRET as well, now I'm curious...

On Haret this issue i think was fixed on the latest update with kernel .27. I tried all kinds of calls (missed, ignoring, answering several times). ringtone and sound were still fine.

[arrrghhh]

Originally Posted by eurohunter

On Haret this issue i think was fixed on the latest update with kernel .27. I tried all kinds of calls (missed, ignoring, answering several times). ringtone and sound were still fine.

Hey, thanks for doin my work for me .

Better yet, do you know which commit on .27 it was...? Or perhaps approximately when it was fixed? I don't recall this one in particular.

[[ACL]]

Originally Posted by arrrghhh

Hey, thanks for doin my work for me .

Better yet, do you know which commit on .27 it was...? Or perhaps approximately when it was fixed? I don't recall this one in particular.

Its most likely this one

Commit in linux-msm in Linux on Qualcomm's MSM - Gitorious

I'm responsible for the main .27, but this acoustic branch that emwe has this commit picked from .35. It's worth a try i suppose.

[detule]

Originally Posted by [ACL]

Its most likely this one

Commit in linux-msm in Linux on Qualcomm's MSM - Gitorious

That's to address the root of all evil (from milda25's log):

[ 4128.015228] snd_set_device -1 1 0

[[ACL]]

Originally Posted by detule

That's to address the root of all evil:

[ 4128.015228] snd_set_device -1 1 0

Lol, root of evil is right. This should be handled in user-land, but extra protection in the kernel does not hurt i suppose. Thanks dood.

[eurohunter]

Originally Posted by arrrghhh

Better yet, do you know which commit on .27 it was...? Or perhaps approximately when it was fixed? I don't recall this one in particular.

Maybe I am outdated, but I am using the kernel that you uploaded together with the latest bundle on Jan 18. The kernel info is 2.6.27.46-01365-gc8b9a4c.tar.gz, modified on Jan 13, 3:55 pm. When I tried the kernel that you uploaded with your 12/31/11 bundle, the sound would mess up when I ignored calls with the slider. so basically u fixed it on ur latest release
I did have trouble with the ringtone on other kernels like 3.1 and 3.0, but i guess this isn't the right thread to discuss it. (heck, this whole post isn't supposed to be here, lol)

[arrrghhh]

Originally Posted by eurohunter

Maybe I am outdated, but I am using the kernel that you uploaded together with the latest bundle on Jan 18. The kernel info is 2.6.27.46-01365-gc8b9a4c.tar.gz, modified on Jan 13, 3:55 pm. When I tried the kernel that you uploaded with your 12/31/11 bundle, the sound would mess up when I ignored calls with the slider. so basically u fixed it on ur latest release
I did have trouble with the ringtone on other kernels like 3.1 and 3.0, but i guess this isn't the right thread to discuss it. (heck, this whole post isn't supposed to be here, lol)

Heh, no worries.

I think they found it above (er, on the previous page). Thanks!!

[mbellot]

Had a waking lock-up, in the middle of reading some email. last_kmsg attached, even though nothing jumped out at me...

FWIW - I'm not having any of the audio problems reported by some of the others. In fact, it seems about the best yet. No calling myself after a reboot to kickstart audio, no crazy loud earpiece, etc.

[[ACL]]

Originally Posted by mbellot

Had a waking lock-up, in the middle of reading some email. last_kmsg attached, even though nothing jumped out at me...

FWIW - I'm not having any of the audio problems reported by some of the others. In fact, it seems about the best yet. No calling myself after a reboot to kickstart audio, no crazy loud earpiece, etc.

damnit its that damn MDP error again. So it just restarted on its own or was there panic and just froze? The log itself is missing the panic portion thats why i ask.

[[ACL]]

http://rhodium-nand.googlecode.com/f...E-02012012.zip

Uploaded a new update. Just kernel changes recommended by muzling and Detule.