Screen Timeout during Call (on Super Clean)

[abowlofsoda]

After installing the Super Clean ROM I find that the screen times out after 2 seconds instead of staying awake- IF I'm on speaker phone...

I looked thru all the settings but could not find a way to change this

Does anyone know?

 

[chrisexv6]

I just noticed this myself. Didnt notice any settings for it, I kind of figured it wouldnt be something you could set but maybe?

-Chris

 

[abowlofsoda]

There has to be a way to change it if it was awake on stock. Maybe from the hidden menu? I'll have to go looking for that thread

 

[chrisexv6]

What apps do you have installed? Maybe its an app and if we compare lists we can possibly eliminate them.

 

[SOTK]

I hope you find something out. Noticed this as well. I hate how fast the screen sleeps while on speaker phone or while using Bluetooth.

 

[abowlofsoda]

I haven't found out anything yet.. I did however post the same question on the Super Clean release thread over at XDA. Hope to find out soon- will let you know.

 

[chrisexv6]

Interesting thing is that I powered the phone down and then turned it back on again and the problem seemed to go away.

Note that I was also seeing this issue using the phone normally, not with just speakerphone enabled.

 

[chrisexv6]

I just updated to the 11/10 non-voodoo kernel (wiped the whole phone and started over), and it *still* did the funky screen timeout thing, until I did a shutdown and reboot.

Makes me wonder if the issue exists even in stock form too?

 

[abowlofsoda]

Interesting thing is that I powered the phone down and then turned it back on again and the problem seemed to go away.

Note that I was also seeing this issue using the phone normally, not with just speakerphone enabled.

If its happening outside of speakerphone then go into Settings > Sound & Display > Screen Timeout and set it to something like 2 minutes.

 

[chrisexv6]

FWIW someone on Android Forums has this same issue with a stock phone. It was thought the Fast Reboot app might be the culprit but Ive experienced it even after wiping and putting a new kernel on and NOT reinstalling Fast Reboot (unless maybe the data is still there somehow?)

 

[chrisexv6]

I haven't found out anything yet.. I did however post the same question on the Super Clean release thread over at XDA. Hope to find out soon- will let you know.

Do you happen to have the System Panel app installed?

Read that it might be killing off a process it shouldnt (com.samsung.phoneinfo)

Ive excluded that app from being mucked with and will watch how it works from now on. Note that after a hard reboot last night I have not had the keylock issue show up since.

 

[pavlentey]

Hard Reboot worked for me

 

[mezatown]

That worked for me too but only for a short period of time its not a permanent fix

Sent from my SCH-I500 using Tapatalk

 

[pavlentey]

I agree. My phone started acting up again

 

[Cory Streater]

I've had this happen on a stock phone with no 3rd party apps, & no custom ROM's or other tweeks. It happens randomly and a power cycle always fixes it for an undetermined amount of time. It think the proximity sensor gets confused and thinks you're holding it up to your ear when you aren't.

 

[Chris Kerrigan]

This has also happened to me with my original Droid, and a buddy of mine also complains it happens to him on his Droid X at times. I haven't had it happen to me yet on the Fascinate but I'm sure it might be only a matter of time. I agree with Cory on the proximity sensor getting confused.

Doesn't seem to be just limited to the Fascinate though. So maybe it's even an unresolved Android issue?