3 ms·
I just mesured. Between the moment you click the native browser (not even Firefox, which I use), and the moment you can start write a tweet, there is a gap of 2
by sametmax 10y ago
I just mesured. Between the moment you click the native browser (not even Firefox, which I use), and the moment you can start write a tweet, there is a gap of 23 seconds. 23 seconds to display a web page on a fresh system with no other app running. This is insane.
It is made much worse by the fact you can't open many apps at the same time. The OS frequently keels app you don't use, so you have to regularly wait another 23 second all other again if you multitask.
- fractallyte 10y agoI counted less than 10 seconds to Twitter on my phone. That's with one other app running. I can open many apps simultaneously, although I rarely go past 6 or 7. So clearly there are differences between phone models (if indeed my phone has some minor upgrades over previous ones), and/or OS versions.
- bruce_one 10y agoI don't _think_ the hardware's changed? My thought would be to try a btrfs balance (can be done through one of the menus); or trying to free some space from the internal storage. It made a large difference in how the performance felt on mine last time I did so. (A bit sad that it's often required, the fs is one of the main pain points ime.) (For reference, mine took ~15 seconds, but think that about 5 of that was network related -- because the browser was open and responsive at the 10 second mark. Had 4 other apps open at the time.)