5 ms·

On a similar note, I have a Motorola G8+, Android 10. It has 4GB of RAM, plenty of free space in storage, and the CPU isn't actually that bad still. The battery

On a similar note, I have a Motorola G8+, Android 10. It has 4GB of RAM, plenty of free space in storage, and the CPU isn't actually that bad still. The battery is in good condition. A brand new phone doesn't necessarily have any better stats. For some reason, it is slow. As in, it will still usually run apps at full speed, the framerate in a flight sim is just as high as before etc, but then it will just freeze up for seconds at a time, or suddenly do something really slowly for a while. Sometimes it will fail to respond to the power button short-press to turn the screen on, but if I try again a minute later it will be fine. I have experienced this with multiple Androids over time. My previous phone got so bad that it sometimes wouldn't actually respond quickly enough to be able to answer a phone call, which is when I got the new one. What causes this? Is there some build-up of junk lying around in the system that I could press a magic button and clear out, without having to reinstall all my stuff from scratch? I could buy a new phone. But given a new one wouldn't have much more resources than my current one, it very much feels like the wrong workaround for a problem that shouldn't exist.

timvisee 4y ago
I still use my OnePlus 5 which is now (almost) 5 years old! It has 8GB of memory with Android 13 and a custom ROM. It's still faster than some phones that are released today. I agree though that some apps are extremely resource intensive for the sometimes seemingly things they have to do.
- V1ndaar 4y ago
  Funny. I'm still on a OnePlus 6 and I see similar bizarre freezes as OP when I open the photo gallery. Or just when starting the camera often I have to wait 15-20s before the phone realizes that I have pictures. Sometimes when swiping through the gallery it will become excessively slow and stop reacting to panning / swiping / zooming. It's what is driving me close to grabbing a new phone at some point this year.
  - timvisee 4y ago
    Not fun! Using a custom ROM? I'm running LineageOS with minimal Google Apps.
    - V1ndaar 4y ago
      No. The OnePlus 6 was my first phone where I really didn't feel like bothering with the hassle of custom ROMs. Back in the HTC Desire and HTC OneX days, while fun, it was always such a gamble what feature might not be working on each ROM. I just wanted to not have to worry about working camera, bluetooth or GPS any longer. I'm not sure, but does the OnePlus 6 even have good LineageOS support nowadays? edit: Apparently yes it seems. Wow, maybe I'll give that a try one of these days and see what it's like.
  - mdiesel 4y ago
    OnePlus 6T here and finally thinking it's time to step up. My previous phone was the OnePlus 2T so seems right to go up to the 10T now and do every 4 versions. I've not had anything quite that drastic, but there are definitely a few small niggles I think I'll notice once they're not there. Main reason I think I'll upgrade is the usb port is becoming quite sensitive, it's 50/50 if it likes a particular cable now
    - bmicraft 4y ago
      They skipped the 4/4T series because of some superstition about the number 4, which makes the 6T 3 years behind 2T
  - deleted 4y ago
    [deleted]
londons_explore 4y ago
This is caused by the emmc storage inside getting slower due to wearing out. emmc firmwares are universally crap at wear levelling, so after a few years use a card that could read/write data at 200 Mbytes/sec before might now be as low as 2 Mbytes per second for reading the most read/written sectors. The effect is compounded by the fact that modern apps are larger, taking up more RAM and flash storage. That in turn means the emmc has to work much harder - since there will be less free RAM for caching, there will be far more random reads. The overall effect is a huge storage slowdown that makes the device unusable.
- mnw21cam 4y ago
  I just benchmarked the storage on my phone, and it seems fine. But I'm guessing the benchmark doesn't touch the most heavily-worn parts of the storage.
- mnw21cam 4y ago
  Is there an app that can tell me the wear stats from the storage device? A bit of googling tells me that a service called storaged processes them, but I can't immediately find an app that does this.
  - londons_explore 4y ago
    I don't think either android or iOS expose this info to apps. You might be able to get it from a rooted device - although if it is emmc based storage, then there isn't even a standard way for the OS to know - it depends on the manufacturer of the device using proprietary calls (if it collects stats at all).
    - joshspankit 4y ago
      The underlying “now” test seems reasonable: load a bunch of data off the storage and see how long it takes. You could even theoretically read all data and uncover slow sections (if there is such a thing). Writing would be harder of course.
deleted 4y ago
[deleted]
Vrondi 4y ago
Especially during something like gaming, this could be overheating. Very common with gaming on phones.
29083011397778 4y ago
The common theme in all the comments below yours, including mine, is those with much beyond a minimal number of Google Apps report "All's good on my device". That's why I started using OSM and the web version of Google Maps on my previous handset: Google apps and services framework get heavier every year by a decent amount. Without them, my current Pixel 2 is fast, responsive, and the battery lasts 2 days (after replacing it six months ago). More actionable though: Settings > Developer Options > Running Services on your device likely has lots of things running, all with their own interrupts. Worse, unless you keep a close eye on what else is allowed to run all the time, and *especially accessibility services*, the exact type of power-user apps people here are likely to install are the most likely to kill performance due to system hooks - though I will always blame Google Services first.

timvisee 4y ago

I still use my OnePlus 5 which is now (almost) 5 years old! It has 8GB of memory with Android 13 and a custom ROM. It's still faster than some phones that are released today. I agree though that some apps are extremely resource intensive for the sometimes seemingly things they have to do.

V1ndaar 4y ago
Funny. I'm still on a OnePlus 6 and I see similar bizarre freezes as OP when I open the photo gallery. Or just when starting the camera often I have to wait 15-20s before the phone realizes that I have pictures. Sometimes when swiping through the gallery it will become excessively slow and stop reacting to panning / swiping / zooming. It's what is driving me close to grabbing a new phone at some point this year.
- timvisee 4y ago
  Not fun! Using a custom ROM? I'm running LineageOS with minimal Google Apps.
  - V1ndaar 4y ago
    No. The OnePlus 6 was my first phone where I really didn't feel like bothering with the hassle of custom ROMs. Back in the HTC Desire and HTC OneX days, while fun, it was always such a gamble what feature might not be working on each ROM. I just wanted to not have to worry about working camera, bluetooth or GPS any longer. I'm not sure, but does the OnePlus 6 even have good LineageOS support nowadays? edit: Apparently yes it seems. Wow, maybe I'll give that a try one of these days and see what it's like.
- mdiesel 4y ago
  OnePlus 6T here and finally thinking it's time to step up. My previous phone was the OnePlus 2T so seems right to go up to the 10T now and do every 4 versions. I've not had anything quite that drastic, but there are definitely a few small niggles I think I'll notice once they're not there. Main reason I think I'll upgrade is the usb port is becoming quite sensitive, it's 50/50 if it likes a particular cable now
  - bmicraft 4y ago
    They skipped the 4/4T series because of some superstition about the number 4, which makes the 6T 3 years behind 2T
- deleted 4y ago
  [deleted]

londons_explore 4y ago

This is caused by the emmc storage inside getting slower due to wearing out. emmc firmwares are universally crap at wear levelling, so after a few years use a card that could read/write data at 200 Mbytes/sec before might now be as low as 2 Mbytes per second for reading the most read/written sectors. The effect is compounded by the fact that modern apps are larger, taking up more RAM and flash storage. That in turn means the emmc has to work much harder - since there will be less free RAM for caching, there will be far more random reads. The overall effect is a huge storage slowdown that makes the device unusable.

mnw21cam 4y ago
I just benchmarked the storage on my phone, and it seems fine. But I'm guessing the benchmark doesn't touch the most heavily-worn parts of the storage.
mnw21cam 4y ago
Is there an app that can tell me the wear stats from the storage device? A bit of googling tells me that a service called storaged processes them, but I can't immediately find an app that does this.
- londons_explore 4y ago
  I don't think either android or iOS expose this info to apps. You might be able to get it from a rooted device - although if it is emmc based storage, then there isn't even a standard way for the OS to know - it depends on the manufacturer of the device using proprietary calls (if it collects stats at all).
  - joshspankit 4y ago
    The underlying “now” test seems reasonable: load a bunch of data off the storage and see how long it takes. You could even theoretically read all data and uncover slow sections (if there is such a thing). Writing would be harder of course.

deleted 4y ago

[deleted]

Vrondi 4y ago

Especially during something like gaming, this could be overheating. Very common with gaming on phones.

29083011397778 4y ago

The common theme in all the comments below yours, including mine, is those with much beyond a minimal number of Google Apps report "All's good on my device". That's why I started using OSM and the web version of Google Maps on my previous handset: Google apps and services framework get heavier every year by a decent amount. Without them, my current Pixel 2 is fast, responsive, and the battery lasts 2 days (after replacing it six months ago). More actionable though: Settings > Developer Options > Running Services on your device likely has lots of things running, all with their own interrupts. Worse, unless you keep a close eye on what else is allowed to run all the time, and *especially accessibility services*, the exact type of power-user apps people here are likely to install are the most likely to kill performance due to system hooks - though I will always blame Google Services first.