[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix!

[orangekid]

Originally Posted by arrrghhh

Hrm... interesting. I'm certainly no expert, but these logs show some serious issue. I just wish I knew what the issue was .

Logcat seems to show that the CPU is pegged, and can't do anything. I also see where the kernel tanked, probably the reason for the SoD. Interesting that adb worked - I don't think this condition was created from poor signal.

Edit - I suck at following logs . What were you doing right before it started acting haywire? I see a bunch of stuff like a task killer running, twitdroid, some SMS messages...

No matter how you slice it, in your logcat there's a TON of "CPU pegged" messages, blocking stuff&things from happening .

what governor are you using?


I know from doing this on HD2 that the radio makes a BIG difference in things like SOD and freezes, have you guys tried flashing different radios and noting logcat differences in the cpu as well as SOD?

[arrrghhh]

Originally Posted by fishingmedic

I was using the phone talking, got off and hit the power button which is remapped to hang up per F22's rootfs and startup.txt addition, have used it in the past and no issues. As far as sms messages, they may have been coming in along with twitdroid getting messages, I do have taskiller also. And I agree, there were tons of CPU pegged all thoughout it. I wasn't even pressing a ton of buttons on it trying to make it do a million things at once. Maybe I'll try removing taskiller and see if that improves it at all, although this isn't a regular occurrence.

I'm not saying the task killer is the culprit, I just saw that running in the middle of the mess .

Originally Posted by orangekid

what governor are you using?


I know from doing this on HD2 that the radio makes a BIG difference in things like SOD and freezes, have you guys tried flashing different radios and noting logcat differences in the cpu as well as SOD?

What do you mean by governor? I don't think we have tried different radio versions - I assume you mean radio firmware, flash radio firmware thru bootloader/WinMo right? I don't know if anyone has done any experimentation on radio firmware, but our RIL is extremely borked - you HD2 folk have it easy, phh just wrote a wrapper so you guys don't even have your own RIL code . We're using the Vogue RIL, modified to work for our devices. It is in the process of being overhauled, which I am ridiculously excited for .

[orangekid]

Originally Posted by arrrghhh

I'm not saying the task killer is the culprit, I just saw that running in the middle of the mess .



What do you mean by governor? I don't think we have tried different radio versions - I assume you mean radio firmware, flash radio firmware thru bootloader/WinMo right? I don't know if anyone has done any experimentation on radio firmware, but our RIL is extremely borked - you HD2 folk have it easy, phh just wrote a wrapper so you guys don't even have your own RIL code . We're using the Vogue RIL, modified to work for our devices. It is in the process of being overhauled, which I am ridiculously excited for .

I'm talking about the CPU governor built into the kernel, and I can tell you flashing a different radio firmware could have some huge effects at some point, if you know something is borked like the ril then yeah it's no mystery as to what is messed up.

can't wait to see the new ril and it's only going to get better from here on out that's for sure.

[fishingmedic]

Originally Posted by orangekid

what governor are you using?


I know from doing this on HD2 that the radio makes a BIG difference in things like SOD and freezes, have you guys tried flashing different radios and noting logcat differences in the cpu as well as SOD?

Are you referring to different radios in winmo?

[fishingmedic]

Originally Posted by arrrghhh

Hrm... interesting. I'm certainly no expert, but these logs show some serious issue. I just wish I knew what the issue was .

Logcat seems to show that the CPU is pegged, and can't do anything. I also see where the kernel tanked, probably the reason for the SoD. Interesting that adb worked - I don't think this condition was created from poor signal.

Edit - I suck at following logs . What were you doing right before it started acting haywire? I see a bunch of stuff like a task killer running, twitdroid, some SMS messages...

No matter how you slice it, in your logcat there's a TON of "CPU pegged" messages, blocking stuff&things from happening .

I was using the phone talking, got off and hit the power button which is remapped to hang up per F22's rootfs and startup.txt addition, have used it in the past and no issues. As far as sms messages, they may have been coming in along with twitdroid getting messages, I do have taskiller also. And I agree, there were tons of CPU pegged all thoughout it. I wasn't even pressing a ton of buttons on it trying to make it do a million things at once. Maybe I'll try removing taskiller and see if that improves it at all, although this isn't a regular occurrence.

[fishingmedic]

Originally Posted by orangekid

I'm talking about the CPU governor built into the kernel, and I can tell you flashing a different radio firmware could have some huge effects at some point, if you know something is borked like the ril then yeah it's no mystery as to what is messed up.

can't wait to see the new ril and it's only going to get better from here on out that's for sure.

That's interesting....maybe we should list radios that we're using to see if particular ones r causing issues.


Sent fro my FRX05 using Tapatalk

[orangekid]

Originally Posted by fishingmedic

That's interesting....maybe we should list radios that we're using to see if particular ones r causing issues.


Sent fro my FRX05 using Tapatalk

I think you should because like on HD2 if you use a 2.07.xx radio you get SOD a lot, if you use 2.12.50 radio you get better battery life in WP7 and more drivers work, and if you use 2.15.00 radio you get really good stability and battery life in Android...

wouldn't be a bad idea to try different radios along with fixing the RIL

[fishingmedic]

Thanks for the info. I'm currently in android right now but later tonight will reset to winmo and see what radio I'm on, and try one of the others and see how it goes.

[orangekid]

Originally Posted by fishingmedic

Thanks for the info. I'm currently in android right now but later tonight will reset to winmo and see what radio I'm on, and try one of the others and see how it goes.

just for grins you might do something like make a spreadsheet and put some logcat reads as well as mah drain and SOD frequency or something with 2 or 3 radios and see if anything significant turns up.

[ndno]

Wow, ghost town around here for the past 5 days. I just got back from a snowboarding trip to Mammoth Mountain. Awesome snow conditions but had to drive on snow cables (not even chains) for 20 miles at 30 mph Yeah, i don't have a 4 wheel drive. It was freakin' cold... 15 deg F... i know how you feel now, fishingmedic. Awesome conditions for snowboarding; thank goodness only a few kids and their families decided to show up during their spring break because there were no lines on the lifts and gondola. Wished I could stay another day snowboarding, oh well, next year.

Back OT, can't wait for the RIL fix, frx05 has been running fine with this kernel with the occasional reboot to winmo (happening to me more than normal now); I had to switch back to winmo while I was at mammoth because I needed something more reliable.

BTW, just got me a new Android toy: the Viewsonic G-tablet (same processor as the Xoom); I got it at www.woot.com for $285! (by way of slickdeals.net). Planning to flash it with VEGAn (http://www.youtube.com/watch?v=I27zrnBoI14 - check out the quadrant score at the end, I think it's 2422!); this will smoke the Ipad 2 at half the price. Waiting for the HoneyComb port!

Sent from my FRX05-ized TP2