• 11 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • Honestly I’d disagree. Past the iPhone 4S, my iPhone 8 was fine through it’s life before being replaced with a 13 mini a year or two ago when it suffered a naked gravitational incident at my hands. My parent’s generally had hand-me-downs or used models and dad’s 6s is still kicking and performing alright and even got a security patch a month ago.

    They had that battery snafu which I will absolutely fault their lack of transparency for (good ol’ hide-the-workings-from-customers Apple) but I did encounter the issue it sought to trade performance for preventing in the past. (a worn battery causing random reboots on my 6s)

    Now my BlackBerry Priv? I miss that phone but I did not miss it’s combination of slowing down with age plus updates running out at 6.0.1. Worst of both worlds but I miss sliders and Blackberry’s additions. (not the size though)

    Similar in age (2015 models) but I doubt dad would be as tolerant of how it performed even a few years ago.





  • Mostly incorrect, entering the BIOS and having the toggle to switch between S0 and S3 (or, “Linux”) sleep does indeed exist but it is hard to identify what models have it (I hear Lenovo’s BIOS simulator helps) and it’s increasingly being removed in newer models or even removed in updates. Dell has no interest in putting it back and recommends hibernate or just powering off the machine when on-the-go.

    I made sure the ThinkPad I own personally had the toggle but my work-issued one does not so it is now a Hibernate-only machine. No setting can help that.






  • We don’t know any details. Google is trumpeting a success and indicating a willingness to assist but it doesn’t really tell us much of what it will look like. Apple is committing to RCS, the industry standard as it is (and I assume will be as I hope it breathes new life into the standard…) and not Google’s current RCS + proprietary bits implementation.

    When MS created a Windows Phone YouTube app, Google blocked it with requirements that were either arbitrary (it needs to be HTML5 for example despite iOS and Android apps being native) or impossible to meet. (requiring specific access that Google would not provide)

    So while Google framed it as “Microsoft just needs to do X, Y, Z and it’ll be all good!” - sounds good but it intentionally made said requirements impractical or impossible to complete.

    Since Google’s been conflating their RCS implementation with RCS the standard, I think it’ll be a funny (if unfortunate) monkey’s-paw result if Apple’s adopts RCS completely as the backup to iMessage but continued carrier and Google implementation fumbling results in no change and the iPhone having to resort to SMS/MMS anyway.

    (see: a while back when AT&T’s RCS could only be used between a couple AT&T Samsung phones - but I do hope it’s different this time, I got a group chat I rather take off Instagram.)



  • I don’t think Apple will need (or want) to do anything “malicious” since Apple is implementing RCS the standard which between the carriers and Google mismanaging and fragmenting messaging for years - see: X carrier phones can only send RCS messages to X carrier phones, Google’s implementation is not the RCS standard and is partially proprietary - it’ll take a while to get S.S. RCS, The Standard steered right.

    I hope Apple’s involvement is ironically a kick in the butt to get everyone on the same page and get a standard rather than the current “Google iMessage” solution.

    Edit: Typo







  • I’ve been firmly in iPhone-land quite a while and dabbled only a bit since my phone-switching days so my current perspective will be possibly dated and definitely from someone on the outside, casually following what’s new in Android but I did have a great time bouncing between platforms back in the day. (RIP webOS, BB10 and Windows Phone)

    I had a Moto Z Play back in the day (that battery life but like that and the Priv it replaced, a bit big for my taste) and I ditched it when a then-critical feature to me: “Ok Google with Screen Off” was removed around the time Google Assistant and the Pixel 1 was rolling out. It was a Play Services and/or Assistant/Google Now update that removed the option from settings, I uninstalled them to keep it temporarily and when I looked it up, all I could find was a curt official “the feature is not supported” response on some support board. I knew the Snagdragon-whatever chipset it had supported it, and I was using it just fine in the past - it felt like gaslighting, I saw people throwing around the “your battery life would suffer” excuse or that it was never supported despite it being the time when chipset support for hotwords when sleeping like Hey Cortana, Hey Siri were a notable feature and the Z Play had it.

    Imagine my reaction when I see that feature being advertised as a Pixel exclusive(? At least it was advertised as a Pixel feature) so that was it.

    in hindsight, Google’s shenanigans to promote their own in-house projects over Android as a whole seems pretty in-character now. Even as iOS features aren’t as big like “ooo iOS’s facsimile of multitasking!” there’s still the “that’s neat” or small QoL moments coming out like auto-deleting 2FA texts when they’re used. And I just don’t seem to see any of that in recent releases. I saw “AI color themes!” and a new time layout? and I’m not shortchanging the features already there like holding volume down to mute, but it just feels like they’ve decided base Android is good enough and slowed down or stopped in favor of figuring out whatever exclusive Pixel features and what to keep from the non-Pros.

    But with the move of so many things to Play Services, are features still coming out that way outside of the usual point release?