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

[arrrghhh]

Originally Posted by Recursion

Update: Airvana seems to be an issue. I unplugged it, and haven't had a reboot since (1.5 days now). Still testing, but I also run WinMo at times. Notably, WinMo randomly wakes up (screen comes on) in WinMo with the Airvana, so this might be related. Possible data going from Evdo to 1x and back. I've seen it switch between them when on Airvana.

If this is the case, then
(1) damn...I really dig having 1.7/.7 data throughput & solid signal in the house & will miss it; and
(2) damn...latest kernel kix ass!

Good things come to those who wait...

WisTilt2 has been out of town the last few days, but I did some more testing of his new RIL... and it's going very well. Still not nearly stable enough to release for general testing (sorry!) but I'm hoping soon... still lots of commands to flesh out, and WisTilt2 found that Android wasn't properly initializing the modem - so bugs getting squashed left and right, and I'm hopeful that with it these SoD bugs will go away. The reboots are a little more perplexing, but perhaps another symptom.

[ffkip911]

Originally Posted by arrrghhh

Good things come to those who wait...

WisTilt2 has been out of town the last few days, but I did some more testing of his new RIL... and it's going very well. Still not nearly stable enough to release for general testing (sorry!) but I'm hoping soon... still lots of commands to flesh out, and WisTilt2 found that Android wasn't properly initializing the modem - so bugs getting squashed left and right, and I'm hopeful that with it these SoD bugs will go away. The reboots are a little more perplexing, but perhaps another symptom.

are we talking FRX or GB boss??

[arrrghhh]

Originally Posted by ffkip911

are we talking FRX or GB boss??

RIL is build-agnostic my friend!

Edit - To clarify, I have been testing on Froyo, but the RIL should be able to be used on any of our builds.

[fishingmedic]

Excellent to hear about the RIL Arrrghhh. And ffkip, yes, airave/airvana are one in the same, there are older ones typically referrred to as airaves and newer ones sometimes referred to as airvanas. I have both and both have caused me issues and although I still occasionally have some SOD's, I believe they are due in part to the original reason I needed an airave/airvana, crappy signal in areas in my house, so I do drop signals here and there in the house, and that may cause the problems, but they are much less since shutting off my airave/airvana.

[Recursion]

Originally Posted by ffkip911

@Recursion: is Airvana like Airave??

Yes & No. It's the same idea, but the latest version that supports EVDO. The company that makes it for Sprint is "Airvana," hence the name.

Originally Posted by arrrghhh

Good things come to those who wait...

WisTilt2 has been out of town the last few days, but I did some more testing of his new RIL... and it's going very well. Still not nearly stable enough to release for general testing (sorry!) but I'm hoping soon... still lots of commands to flesh out, and WisTilt2 found that Android wasn't properly initializing the modem - so bugs getting squashed left and right, and I'm hopeful that with it these SoD bugs will go away. The reboots are a little more perplexing, but perhaps another symptom.

Well, I'm still holding out. But I'm running outta beer ...
Good news, re: the new RIL in the works. Yeah, the reboots are weird, no noticeable pattern yet. It happens to fresh reboots, virgin setups, older setups, at different times. Like I mentioned, the only things that jump out screaming at me are (1) the weird "wake-ups," and (2) the 1x/EVDO Toggling WinMo exhibits when in range of the Airvana. And as I also mentioned, I haven't had a reboot yet with the Airvana unplugged. These tend to support a likely Airvana-sumhowphknitup situation. I'll chime in if & when I get another reboot.

Thanks again for your time on this project, bro. I know it takes a lot of time & effort...so cheers.

[fishingmedic]

Arrrghhh, here's the dmesg and logcat from my freeze earlier today. As you know, it wasn't a SOD because stuff was still going on behind the scenes, more of a failed wake, was originally kinda frozen screen w/ orange led, screen lit up, I hit back on the hard keys and it went to blinking green LED and from the bottom of the logcat file, you can see what I was still receiving texts but couldn't look at them.

[arrrghhh]

Originally Posted by fishingmedic

Arrrghhh, here's the dmesg and logcat from my freeze earlier today. As you know, it wasn't a SOD because stuff was still going on behind the scenes, more of a failed wake, was originally kinda frozen screen w/ orange led, screen lit up, I hit back on the hard keys and it went to blinking green LED and from the bottom of the logcat file, you can see what I was still receiving texts but couldn't look at them.

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 .

[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?

[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.

[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 .