• mistermodal@lemmy.ml
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    5 days ago

    RIP Samsung infiltrated by the Chinese I guess. IDK seems like a pretty clear throughline from this battery-management-that-doesn’t-save-battery on the bloatware to charging devs to use battery power

      • mistermodal@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        5 days ago

        I run a lot of shit in the background so yes I did notice when Samsung was killing automatic up/downloads at 82% which took altogether too long to reach that point, even when it was “pinned”, even when it was literally focused with the screen on, the app developer had an error message that clarified it was killed by the system. Do you think that repeatedly killing a process that needs to be completed like file backup (while plugged in and on wifi to boot) is a good way to preserve the battery health of the device?

        Oh also I tried exempting it from the memory cleanup alone (a setting I found by accident because I enjoy wandering the menu labyrinths, almost leading me to believe there may be One Weird Trick hidden in there somewhere) still didn’t help. Of course it was unrestricted battery etc. Enhanced processing on power saver off. WHAT MORE DO YOU WANT FROM ME SAMSUNG

        • Pycorax@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 days ago

          Man how many things do you have running in the background and how much ram do you have that this is becoming a problem?

          • mistermodal@lemmy.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            5 days ago

            That was on a 6gb RAM device and it didn’t seem like an abnormal amount of ram ever got used. We aren’t talking about stuff simultaneous with web browsing or games etc, just running lightweight open source shit. I did cycle through all of the available Samsung troubleshooting options you know, because I wanted shit to work? Would have noticed if there was a huge background RAM process. Considering that Chinese phones I see such as Oneplus and I assume newer Galaxies have 12-16gb RAM should be fine even with browsing etc and background processes but it’d eat battery for sure

            If the phone had fucking completed the backup ONCE when scheduled then it would not have spent so much time trying to repeat it and there would be less background activity :^] my phone does not get hot these days

            • Pycorax@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 days ago

              Hmm I wonder if I haven’t had these issues because I’m on a flagship. 6 GB seems rather low unless it’s a midrange device?

              • mistermodal@lemmy.ml
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                1
                ·
                edit-2
                5 days ago

                Yes it was from 5 years ago as well, but my point is running a lightweight backup service doesn’t consume that much RAM, and every Android developer complains about Samsung. “Teehee sorry you bought the lower end model so now basic services don’t work unless you cave and use Google Drive or other baked-in featurs that won’t be “battery saved”” is not acceptable to me and my device no longer does anything of the sort. Thinking about how I am so fastidious with my activity that I was able to get away with under 500-1gb cellular data a month at the time and the backups were a way to use offline shit more just makes me madder at samsung. Altho giving employees cancer would be a more noble reason

                • limerod@reddthat.comOPM
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  arrow-down
                  2
                  ·
                  5 days ago

                  You are complaining about a 5year old phone. Modern day Samsung phones do not have this issue. I can vouch for Oneui 4 and Oneui 5. Compared to MIUI/hyperOS samsung is very tame.

                  • mistermodal@lemmy.ml
                    link
                    fedilink
                    English
                    arrow-up
                    2
                    arrow-down
                    1
                    ·
                    5 days ago

                    You’re never going to believe how old the 5 year old phone was several years ago… as for which manufacturer is the worst offender, take that issue up with the open source devs who put these little complaint pages in my apps calling Ssung and others out. I really despise this variety of unsolicited “your problem never existed/doesn’t matter” tech support