Screen get to Bright and stop communicate

[aqwarty]

Don't know how to name my problem, so...
when I'm writing messages, sometimes screen get to bright and I cannot send, cannot phone, nothing. When I turn off Uni, and turn it on again, it ask me for a password - I don't have any password.

I tried to slow down CPU, I tried to minimize file system cach... still don't know, where's the problem. Now, I think, the amout of messages mayby the problem. So, I deleted half of them and wait, what happened.

Does anyone have similar experience?

[aqwarty]

I've realised that the problem is caused by outlook (mean sms|emails messanger). The program is named tmail.exe. When I shut this program by taskmanager, the screen get normal and other function too. Even phone (lastly i forgot to write, when I get this bug, and try to open phone, i get error message (this program does not cooperate)).
I found, that this ROM - Tomal (Ranju) 7.7 is made from Wizard ROM - maybe this is the prob.
Does someone know what's happening? And how to get it normal. I think (but have not prove it yet), that after flash it is normal. And couple of days after, all is getting worse. Only what I've installed after flash was SPB pocket plus and Tom Tom 6. No other programs.

[dreamtheater39]

i had the same problem in one of the earlier roms i tried....

It can be quite frustrating for sure! Try other roms and see what works, I couldnt find what the problem was and i just moved on to another rom!

San

[aqwarty]

I tried also TOMAL 8.2 rom. And the problem doesn't dissappear.
Maybe it's collision between SPB pocket plus and WK task manager. So I turn off Wk task manager (which is preinstalled with TML rom) and see what happend.

[aqwarty]

So... noone has suggestions?

[l2tp]

i have seen this in every rom i used. somewhere here somebody even posted photos of his uni while this happened. probably reason for this is a some low-level os bug which lead to this thing, maybe overflow of some cache because for me this happened only when i was typing a lot, no matter which program i used, the result was the same. the only solution i found is to soft-reset your device every hour even if everything seems to be ok at that moment.