[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by anish88

Even the 3.5mm will start working too?

As ACL stated, the 3.5mm jack not working is not related to any userland audio routing problems, it is a kernel issue.

[anish88]

Originally Posted by [ACL]

No, 3.5mm is not working because we aren't initializing some hardware. Its a bit confusing because the interrupts for the gsensor are the ones that drive the 3.5mm detection (crazy htc guys).

But its on my list of things to do.

Ok let me know if I can do anything to help

[huckl3b3rry]

Originally Posted by [ACL]

There is a ticket opened about this.

Issue 6 - rhodium-nand - bluetooth incoming audio during phone call not working - Touch pro 2 on NAND - Google Project Hosting

Not sure if you are talking about the same thing.

I am talking about the same thing. So this would be the Bluetooth "headset" profile is what is not working correctly working. Just thought it might help for you to know that the "A2DP" bluetooth profile works properly (at least to my A2DP capable stereo) if you didn't know that already. So I can listen to music from my phone through my stereo via bluetooth just fine. I just don't get audio from phone calls (headset profile) as stated in the ticket you referenced.

[huckl3b3rry]

Actually let me clarify that a little better, I test the was technically trying the "hands-free profile" because I was doing in my car, but "hands-free" has the same audio routing issue that the "headset profile" has. It's only the "A2DP" profile that is working.

[huckl3b3rry]

Boy, you wouldn't know from that last post that English is my first language. Guess I shouldn't type these things while I'm trying to work.

[sykosoft]

Originally Posted by sykosoft

PM me your address, and I'll pop a spare bluetooth headset I have in the mail to you.

Michael

No interest here? Just trying to assist.

Michael

[[ACL]]

Originally Posted by sykosoft

No interest here? Just trying to assist.

Michael

hey sorry just been really busy. I'll pm you when i get a chance.

[[ACL]]

Originally Posted by mbellot

Two catastrophic crashes today, unfortunately I was out the whole day.

Pulled logs and /proc/last_kmsg anyway, just in case. I found three /data/system/dropbox/system_last_kmsg files. Stupid me, I forgot they were UPPERCASE, so I might have been missing them previously.

First crash was around noon (11 hours ago). LED showed orange, panel was dark, no response from phone.

Second crash happened around 8:30pm, phone would not come out of sleep (SOD? - LED remained green regardless of power button activation).

ACL - I don't know if they'll show anything, but you're welcome to them.

dood. I put up a test kernel for the rho100 folk but i also smuggled in some code to fix the devastating mdp issue you had that one time.

http://rhodium-nand.googlecode.com/files/update_kernel_12_12_part2.zip

Give it a try and see if it happens again. To apply just update it using the recovery.

[mbellot]

Originally Posted by [ACL]

dood. I put up a test kernel for the rho100 folk but i also smuggled in some code to fix the devastating mdp issue you had that one time.

http://rhodium-nand.googlecode.com/files/update_kernel_12_12_part2.zip

Give it a try and see if it happens again. To apply just update it using the recovery.

Gonna try it now because my device has gone total batshit crazy. It's spontaneously rebooted six or seven times in the last hour, two SODs and at least one waking freeze.

I pulled logs (attached) and the separate /proc/last_kmsg is from the latest waking freeze. I see what looks like another flinger crash near the end.

Hopefully something will show up in all this...

[mbellot]

Nope. Spontaneous reboot within minutes. Logs attached again.

Time to wipe data or ???