or 3. There was something using much more than 23% CPU which we ignored :)
The answer will become clearer after the fix for bug 1604029 hits devices.
or
3. There was something using much more than 23% CPU which we ignored :)
The answer will become clearer after the fix for bug 1604029 hits devices.