You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue only seen at SGS2-ICS, and it happens at (not limited to) B2G commit id: 23ba75f
When this issue happens, not only screen swiping, but also the apps are getting very slow(near to stuck).
However, CPU usage of b2g process is normal, and other system process looked ok.
It happens on several(but not all) SGS2 phones, this issue seems device dependent.
How to reproduce?
1. Wait 1 minute after device boot (only reproducible after 1 minute from device boot)
2. Go to Clock app
3. Click "Start"->"Stop"->"Start"... repeatedly until issue reproduced
The above is just one way to reproduce easily. If also happens if you just swiping at homescreen,
or running Browser app then click home button repeatedly.
One thing interesting, after 1 minute from device boot, the dmesg shows cpu1 off, seems related to this issue.
I filed the same issue in bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=755568
So I can confirm this bug.
But I couldn't get a procedure to always reproduce it :)
It's been happening since I changed from Gingerbread to ICS.
Have you tried the above steps to reproduce by Clock app? I can always reproduce it on my device by this way.
Note that you need to wait 1 minute after device boot.
This issue only seen at SGS2-ICS, and it happens at (not limited to) B2G commit id: 23ba75f
When this issue happens, not only screen swiping, but also the apps are getting very slow(near to stuck).
However, CPU usage of b2g process is normal, and other system process looked ok.
It happens on several(but not all) SGS2 phones, this issue seems device dependent.
How to reproduce?
The above is just one way to reproduce easily. If also happens if you just swiping at homescreen,
or running Browser app then click home button repeatedly.
One thing interesting, after 1 minute from device boot, the dmesg shows cpu1 off, seems related to this issue.
The text was updated successfully, but these errors were encountered: