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

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

[tacotoy]

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

Originally Posted by rpierce99

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.

you got it right, when the phone is sleeping it will ring, the screen will never come up but it will vibrate and ring. if i get a call while i am using the phone ( i e screen is on) then i can answer it just fine.

running the latest panel reint, and mannieko's modded rootfs with FRX04. i oc, but i have been oc'ing since it was available. this issue started once i loaded the most recent panel reint kernel. ill boot back to winmo and see if that makes a difference


edit: after booting back and then rebooting with no oc it works fine for a bit, but if i get a bunch of programs running, close them down ( ie eat up available memory) then it doesn't work, so seems like there is a memory leak. so over time as programs autoload then it prevents the phone from waking to answer the phone. oc'ing just seems to exacerbate the issue

[arrrghhh]

Originally Posted by tacotoy

edit: after booting back and then rebooting with no oc it works fine for a bit, but if i get a bunch of programs running, close them down ( ie eat up available memory) then it doesn't work, so seems like there is a memory leak. so over time as programs autoload then it prevents the phone from waking to answer the phone. oc'ing just seems to exacerbate the issue

Well if the phone is working hard, waking the panel isn't so easy for it.

However, it seems you are experiencing many more 'failed wakes' than anyone else - I hardly ever get failed wakes anymore, and unfortunately the problem is in the framebuffer. Not sure where they're at on fixing that piece, but WisTilt2 said his panel init code was basically done. Now we just need all the other pieces to play nice...