Die4Ever

Die4Ever, 14 days ago

below 5W, then the charger is considered “slow,” and the message “charging slowly” is shown on the lock screen. If the power is above 7.5W, then it’s considered “fast,” and the “charging rapidly” message is shown instead. If the power is between 5 and 7.5W, then the charger is seen as “normal,” and the lock screen simply says the phone is “charging.”

Seems to be a purely cosmetic change. I was wondering if the OS has any different behavior when charging quickly (like being more aggressive with running background processes, and running updates/backups) but the article didn’t say anything about that.

If my phone was only charging at 5 or 6W I’d want to know the charger is garage. That might not even be enough to use the phone without losing battery. What they really need is to rename “slow” to “very slow”, and then 5W to 7.5W could be considered the new “slow”. The intent being that “very slow” is problematically slow (maybe the OS scheduler could pretend the phone is not charging). And “slow” charging would just be for mild inconvenience.

If only the phone could just tell me the actual number of watts it’s charging at lol. Even if it’s rounded and averaged.

Die4Ever, 14 days ago

then I wonder what the cutoff is for “low power charger” because I don’t think I’ve ever seen that, it could probably stand to be increased a bit

Die4Ever, 20 days ago

very interesting, I wonder if the difference is due to the Pixel 8 Pro having a variable refresh rate screen, maybe also because it has a higher resolution screen and different graphic drivers

but with Chrome being about 10x more efficient on P8P than P4a, I’m guessing the variable refresh rate is a big factor there that Firefox isn’t using as optimally

Die4Ever, 20 days ago (edited 20 days ago)

Yeah I did take the age into account, I just figured it’s over a 10x difference and not all of that would be due to battery age.

My mom is still using my release day Galaxy S9+ lol

Die4Ever, 3 months ago

I think the holdup is that previously SMS was paid for through your carrier, so Google can let any app use it and no one loses money. Now the main RCS instance is hosted by Google, and I guess Google doesn’t want other apps freeloading on their servers since you’re not paying for RCS directly like you are paying your carrier. It really sucks and I hope it gets resolved soon, especially with Apple joining in. We also need a good open source RCS server and client.

Die4Ever, 4 months ago

94 days (they said 2252 hours in the article) on 28,000 mAh? that means a more normal phone with 5,000 mAh would get nearly 17 days of standby time? I’ve never tried not touching my phone for a full day but I don’t believe that, not with Android running. Maybe if it was untouched and in airplane mode lol.

Die4Ever, 4 months ago

This is interesting. I think I’d rather it just keep my actual web browser app in RAM and always open that with a new tab instead of the basic system web view. Or can you change which web browser app is the default web view? Seems like a waste to keep the web view in RAM and also your web browser app

Die4Ever, 4 months ago

Android 15 DP1 has added the “notification cooldown” feature I first revealed in the Android 14 QPR2 beta for @AndroidPolice. This feature “gradually lower[s] the notification volume when you get many successive notifications from the same app.”

I’ve wanted a feature like this for so long lol

Die4Ever, 6 months ago

I wish they would just allow 3rd party share menus, like launchers

Die4Ever, 11 months ago

Dedicated buttons for copy, paste, and undo would be amazing. I don’t think Android has good support for undo though, it would be cool to undo accidental swipes like when you accidentally swipe away a notification, or if you accidentally tap the space around a dialog box and it disappears