---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
yep, that is "screen on bug during call" for me that is only bug on cm7 (it seems that prox.sensor stop working at moment-sleep). i dont know what is a problem, but nobody know how to fix it, too bad. probably we must live with it all custom releases is based on cm7 but on normal defy works ok.
Someone can test "set min CPU Freq to 400mhz" to solve this bug? Developers, this bug can be relationed to "CPU frequence on call after off the screen"!!! Please check it!In my opinion don't is proximity bug, because the button lights on at the moment the proximity sensor is uncovered. May be bug on lcd or cpu driver or some incorrect parameter to defy+...
Sent from my MB526 using xda app-developers app
Whitch option in the boot menu (overclock) is the frequence during a call? Or this setting is in kernel?
Edit 1: i used this config: 300:33 600:48 800:54 1000:58 without success. Someone can test too?
Edit 2: I'm testing (bootmenu) min cpu at 400mhz vsel 33 and interactive governor and until now success, without this bug!!!
Last edited: