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

[fishingmedic]

Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?

Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?

Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.

So far so good with clean FRX04...

[anonymity]

Originally Posted by arrrghhh

New kernel folks, panel detect! Please read the first post...

I have gotten responses back from a bunch of different 100's, a 300 and a couple of 400's.

So if you have a RHOD210 (TMobile) or RHOD500 (VZW) please grab your dmesg and look for those two lines about the type of panel. Thanks!

I'd love to help you out. I have downloaded your latest kernel and it's running fine so far, seems quicker than previously used kernel. I can't speak for stability yet as I've been running it for all of 5 minutes.

I have a RHOD500 but don't know how to get you my dmesg log.

[arrrghhh]

Originally Posted by anonymity

I'd love to help you out. I have downloaded your latest kernel and it's running fine so far, seems quicker than previously used kernel. I can't speak for stability yet as I've been running it for all of 5 minutes.

I have a RHOD500 but don't know how to get you my dmesg log.

I'm already thinking I know what it'll say, but the more logs the merrier. Do you have adb installed? Droid Explorer is the easiest way to get it working in Windows.

If not, there's an app on the market called "OSMonitor". You can pull dmesg and logcat with this app AFAIK. You then have the added fun of trying to get the log off of the phone - hence the reason I prefer adb, makes everything so much easier IMHO.

There's apps that can help you get stuff off the phone as well, like the DropBox app..

[rpierce99]

Originally Posted by anonymity

I'd love to help you out. I have downloaded your latest kernel and it's running fine so far, seems quicker than previously used kernel. I can't speak for stability yet as I've been running it for all of 5 minutes.

I have a RHOD500 but don't know how to get you my dmesg log.

I'm going to assume you're running Windows, if not let us know.
Install guide for ADB HERE: [SOLVED] ADB Setup for Windows - xda-developers
Set up adb, at the point where you've verified you can run adb, run the following command:

adb shell dmesg > dmesg.txt

This will create a file called dmesg.txt in whatever folder command prompt says you are in. Attach that file here or upload the contents to Pastebin.com - #1 paste tool since 2002!

EDIT: arrrghhh beat me to it

[tacotoy]

k so if an incoming call comes in while the screen is off, it will ring and such, and then give me my gv vm notification but the screen will not come on, or even have the backlight kick on. if i wait for it to go to sleep then the screen will come back up. i have to wait to get another call to duplicate this, can i pull a dmesg once i get the screen to come back up for this event or do i need to reboot?

[arrrghhh]

Originally Posted by tacotoy

k so if an incoming call comes in while the screen is off, it will ring and such, and then give me my gv vm notification but the screen will not come on, or even have the backlight kick on. if i wait for it to go to sleep then the screen will come back up. i have to wait to get another call to duplicate this, can i pull a dmesg once i get the screen to come back up for this event or do i need to reboot?

I guess I'm missing something here.

So when the phone is sleeping... it wakes on a phone call.

When the phone isn't sleeping, it doesn't wake for the phone call? I haven't really had any failed wakes on incoming calls, unless the processor was being slaughtered by some other process (not only system_server can cause issues, just that system_server issues would run without stopping).

We have the same phone, what build are you running? Overclocking? Need... more... info...

[rpierce99]

Originally Posted by arrrghhh

I guess I'm missing something here.

So when the phone is sleeping... it wakes on a phone call.

When the phone isn't sleeping, it doesn't wake for the phone call? I haven't really had any failed wakes on incoming calls, unless the processor was being slaughtered by some other process (not only system_server can cause issues, just that system_server issues would run without stopping).

We have the same phone, what build are you running? Overclocking? Need... more... info...

It sounds like tacotoy is saying the phone rings, but the screen never comes on with the slide to answer, so he can't answer the call.

The only time I've experienced that is when system_server was running rampant. If you haven't already I'd try dropping the newly fixed rootfs on the system and seeing if you get any better results.

[anonymity]

@arrrghhh: Pastbin dmesg from rhod500

Edit: now maybe someone can explain to me what panel detection is.

[arrrghhh]

Originally Posted by anonymity

@arrrghhh: Pastbin dmesg from rhod500

Edit: now maybe someone can explain to me what panel detection is.

[ 1.206878] Panel type detected: 14 <---- thanks!

Means you have the EID panel, which the vast majority of our phones do. Seems a few RHOD100's have a different panel type, AUO. Which means the commands to wake and collapse that panel are going to be slightly different - and if the proper panel is not detected in the kernel, then the phone will have problems .

[anonymity]

Originally Posted by arrrghhh

[ 1.206878] Panel type detected: 14 <---- thanks!

Means you have the EID panel, which the vast majority of our phones do. Seems a few RHOD100's have a different panel type, AUO. Which means the commands to wake and collapse that panel are going to be slightly different - and if the proper panel is not detected in the kernel, then the phone will have problems .

Well I'm glad I could participate. So the "panel" that this references is the actual display panel (or its controller)?