• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • It’s very spring here in the south, so I’m outside tending to the yard-wide flower bed we set up last year. I’ve been battling the grass growing back in it for a while and almost gave up after the brutal summer last year killed off half of my plants. I found that using saved up cardboard and mulch keeps a lot of the grass at bay. So that’s been my project for a few weeks now, slowly filling the whole bed and revitalizing the whole thing.
    As a small reward for the progress I’ve made, I picked up a few perennials at the store the other day: salvia, lantana, and some consumables - dill, basil, and peppers. They look really nice in the parts of the bed I’ve already tended to :)










  • Adding on to a bit from your comment that I missed, it’s not affecting the car itself. The article should have used the word “phone” instead of “device”.
    All Android Auto is a screen for your phone that also hooks into car buttons. Your phone does all the hard work with projecting data to the screen. If your phone is too old, Android Auto might not work because apps don’t work properly with the base framework by Google.
    You can use a new phone on an older car that officially supports Auto/CarPlay. That’s never been a problem.


  • If you don’t update Android Auto, maybe. Apps still rely on the framework that makes it work, so you are likely to have those break if they use features that Android Auto didn’t have at the update freeze.

    The version they’re cutting off is really old, relatively speaking. You have to be on Oreo or later (8.0+), which came out in 2017.
    Many apps you would use Android Auto will likely bump up to this break point soon. Waze, for example, is 7.0+. You’re bound to run into issues being on Nougat or earlier soon, if not already.