mctoey
24th January 2008, 11:26 PM
Has anyone encountered this problem? I am using current Ivan's v3.9 rom for the G4. Everytime my device wake up from sleep/standby, there will be some misalign on the touch screen (almost half the height of the number button in landscape phone mode), and can be solved by realigning the screen in Settings. However, waking up from standby or sleep, the misalign comes back.
Furthermore, I notice that after waking up from sleep/standby, the touch screen becomes unresponsive. This have to be overcome by tabbing the screen using more force, or using a finger pushing, with a bit of force, at the screen (usually at the top-left windows button) to make the screen work again; i.e., tabbable.
This is otherwise a perfect rom I find. I have had no other problem using this rom apart from this touch screen bug.
May it be because the rom is orginally designed for the qVGA device? Perhaps this thread might give you guys some useful information http://forum.xda-developers.com/show...gn#post1329097
See esp. message #10
I am not sure, but I do get a slight feeing that the degree of misalignment sometimes relates to the % level of battery.
P.S. I am using 128MB Ram G4. Hope this is not causing it.
Anybody please.
Furthermore, I notice that after waking up from sleep/standby, the touch screen becomes unresponsive. This have to be overcome by tabbing the screen using more force, or using a finger pushing, with a bit of force, at the screen (usually at the top-left windows button) to make the screen work again; i.e., tabbable.
This is otherwise a perfect rom I find. I have had no other problem using this rom apart from this touch screen bug.
May it be because the rom is orginally designed for the qVGA device? Perhaps this thread might give you guys some useful information http://forum.xda-developers.com/show...gn#post1329097
See esp. message #10
I am not sure, but I do get a slight feeing that the degree of misalignment sometimes relates to the % level of battery.
P.S. I am using 128MB Ram G4. Hope this is not causing it.
Anybody please.