[TESTING] - NAND OMGB (1.2.3) - Page 119

argenisaz · #**1181** (**permalink**) 02-02-2012, 08:29 AM

Quote:

Originally Posted by [ACL]

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

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

Just applied the new kernel.

Quick question: are any of these changes audio related?

Thanks a lot for your hard work, really appreciate it.

argenisaz · #**1182** (**permalink**) 02-02-2012, 08:50 AM

Quote:

Originally Posted by argenisaz

Just applied the new kernel.

Quick question: are any of these changes audio related?

Thanks a lot for your hard work, really appreciate it.

Answered myself, audio is working fine!

Ran a couple of tests and audio didn't die: answered phone call, missed phone calls, dismissed phone call, each and every time audio worked like a charm!!!

Thanks ACL, great job!

Posting logs in case you want to compare.

mbellot · #**1183** (**permalink**) 02-02-2012, 10:32 AM

Quote:

Originally Posted by [ACL]

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.

Hard lock-up, screen stayed on exactly where it died. I had to pull my stylus and stab the reset button to get it moving again.

I'll upgrade to the latest and keep testing.

milda25 · #**1184** (**permalink**) 02-02-2012, 03:53 PM

After one day of using last kernel update from 02022012 it seems problem with lost audio has been solved. Audio is now working correctly. Many thanks guys.

**[ACL]** · #**1185** (**permalink**) 02-02-2012, 05:22 PM

Quote:

Originally Posted by mbellot

Hard lock-up, screen stayed on exactly where it died. I had to pull my stylus and stab the reset button to get it moving again.

I'll upgrade to the latest and keep testing.

Ahh, so you manually reset it. Explains why the error kept happening and not crashing. If you run into that again, try to let the phone sleep just as a test. A minute or two idle should force a good nap time. If after that it does not come back up, then you can reset and redump the logs. It seems to happen to you alot, have you figured out a way to replicate it ?

mbellot · #**1186** (**permalink**) 02-03-2012, 12:39 AM

Quote:

Originally Posted by [ACL]

Ahh, so you manually reset it. Explains why the error kept happening and not crashing. If you run into that again, try to let the phone sleep just as a test. A minute or two idle should force a good nap time. If after that it does not come back up, then you can reset and redump the logs. It seems to happen to you alot, have you figured out a way to replicate it ?

OK, next time it happens I'll give it a couple minutes to settle before jamming the stylus in it's reset hole.

As far as reproducing it, not really. It seems to happen regularly but infrequently, but with no definite pattern (such as always checking email, or playing a game, etc). I've had it lock-up in an application, exiting back to the home screen and even when idle on a charger.

I'm beginning to wonder if it's Zeam Launcher since it's one of the few things I've loaded that deviates greatly from stock. I just like it so much better than the stock launcher...

Boominsvx · #**1187** (**permalink**) 02-03-2012, 05:40 AM

I knew the day would come that I couldn't boot into android which means no way into recovery. I can get in with fastboot boot recovery.img, but the buttons don't work. Only up and down. Much like a virgin, I can only get in that way the first time. No way to restore backups so my phone will sit in the corner and think about what it's done. I need sleep. I've never been able to get LK to work reliably. It pretty much does what it feels like doing. Just asking if anyone had any advice. It's covered in dust, so no worries. If not, Winmo, here I come... for a minute.

Starfox · #**1188** (**permalink**) 02-03-2012, 07:55 AM

Did you try using the keyboard? I recall being able to use arrow+enter to navigate.

-- Starfox

**[ACL]** · #**1189** (**permalink**) 02-03-2012, 12:15 PM

Quote:

Originally Posted by Boominsvx

I knew the day would come that I couldn't boot into android which means no way into recovery. I can get in with fastboot boot recovery.img, but the buttons don't work. Only up and down. Much like a virgin, I can only get in that way the first time. No way to restore backups so my phone will sit in the corner and think about what it's done. I need sleep. I've never been able to get LK to work reliably. It pretty much does what it feels like doing. Just asking if anyone had any advice. It's covered in dust, so no worries. If not, Winmo, here I come... for a minute.

Sorry to hear that. My advice is just winmo back and restart. THe buttons arent really handled by LK in recovery, so if you are having issues there you will also have them in android. Recovery has its own kernel.

I had this issue before and no matter how many times you update LK, something behind the scenes may be broken. Last time actually i was able to fix it by reflashing the radio and not going to winmo entirely.

Boominsvx · #**1190** (**permalink**) 02-03-2012, 04:01 PM

Wow, I can't believe I forgot the keyboard trick. For SHAME! Lol, I told ya I was tired. ACL, it only seems to happen at random times. Everything always works if I can get into android. The hardkeys seem to die if I go straight in from fastboot. No worries bro. Glad you guys are still truckin' with this.