I mostly use apps installed from F-Droid, so I’m not sure how I’ll use the phone, except that it’s sometimes required as a contact method.

  • rosco385@lemmy.wtf
    link
    fedilink
    arrow-up
    5
    ·
    5 hours ago

    I’ve been using GrapheneOS for a while, which should minimise disruptions, but I’m also hoping the Linux phone ecosystem improves before Google locks down Android completely.

  • Echolynx@lemmy.zip
    link
    fedilink
    English
    arrow-up
    11
    ·
    9 hours ago

    If it really interferes, same thing as when YouTube started enshittifying: use it less and likely be better off.

  • Hexadecimalkink@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    5 hours ago

    OniroOS hopefully will be out by then. If not then PostMarketOS. Harmony OS is rumoured to be launching globally in 2026 but I doubt.

  • rustyricotta@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    Well because of this, I bought a new phone and am now using GrapheneOS. I’m hoping to last at least 5 years with this, and hopefully by the time I want a new phone, grapheneos will have made a deal to have more compatible phones.

    • brax@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      6 hours ago

      Isn’t Graphene still Android? What’s stopping Google from turfing AOSP so you won’t be able to sideload to them either?

      We need something completely independent from Android. Would be great if phone manufactures would make their pocket computers easier to interface like tradition PCs.

      • Axolotl_cpp@feddit.it
        link
        fedilink
        arrow-up
        1
        ·
        4 hours ago

        I think (thought i am not sure) that this thing will be made with google services so just removing them should do, if not, you can just fork and modify

    • CCMan1701A@startrek.website
      link
      fedilink
      arrow-up
      4
      ·
      8 hours ago

      You mean convince more people to not buy android phones. Man we used to be able to run custom kernel code on the palm pre to try and get more performance out

  • Aeri@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    11 hours ago

    Be fucked? I don’t know I already hate most phones on the market and I’m going to need to buy a new one at some point, not looking forward to it…

  • SuperDuperKitten@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    10
    ·
    14 hours ago

    I’m currently using GrapheneOS on my Pixel phone I brought secondhand so think I should (for now) be okay?

    Otherwise, Linux phone looks interesting but it just relearning both another OS (like iPhone users trying to learn Android and vice versa) and also just I have low income so buying new tech is just expensive.

    I don’t want to throw myself a deepend to an OS that I not as familiar with beside on my desktop and Raspberry Pi. Personally, I prefer to know what’s there before I just go blind so at least I can manage my expectation than expected it to do 1:1 stuff that I do on my phone right now.

  • Hemingways_Shotgun@lemmy.ca
    link
    fedilink
    English
    arrow-up
    21
    ·
    16 hours ago

    I feel embarassed to say this as someone who is fairly techy, but I’m a little confused by the whole brouhaha.

    Is Google making changes to Android, or to AOSP?

    If Google is making changes to the Android fork they put on their own phones, then fuck 'em. Use Graphene. Use e/OS/, use Lineage…use something that forks their own branch of AOSP and Google can pound sand because those forks are in no way obligated to make the same changes as Google. AOSP is open source for that very reason.

    If Google is making those changes to AOSP itself, which means that anyone who uses AOSP as a base have those changes by default, then isn’t Google obligated to keep those changes as Open Source, in which case anyone else who uses AOSP can just remove them from their own fork?

    Someone explain like I’m a particularly dim five-year-old, please.

    • kixik@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      6 hours ago

      If you want to keep using google playstore and services, you no longer will be able to use f-droid, whether google or any aosp rom. grapheneOS claims it won’t be affected given their sandboxed google play and services. Though I’m not sure if eventually google would come up with a counter measure or it won’t ever care. They want to enforce that if anyone uses their proprietary stuff the apps interacting with it must be from register developers, which automatically exclude any libre/free app storage on which developers don’t want to register to google. GrepheneOS being the exception.

      If you use microG with any custom rom, I guess that might work through fake registrations, but can’t be sure. But any custom rom without google play and services is supposed to be ok with f-droid. The thing is that google knows most if not all users need one app that depends on their stuff, perhaps bank apps, payment apps, and so on…

    • ☂️-@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      10 hours ago

      iirc they are enforcing this on the play services level, using the play protect system. so if you use a custom rom, with google play, you are likely cooked too.

      that is if the roms don’t implement a system to circumvent it.

    • Chulk@lemmy.ml
      link
      fedilink
      English
      arrow-up
      7
      ·
      14 hours ago

      I’ve also been confused about this, but this is my take on it.

      You’re correct that they are making these changes to Android and not AOSP. This means that an OS like Graphene or e/OS/ will still be able to use sideloaded apps and other appstores like F-Droid.

      I think the reason everyone is freaking out about this, is that it hurts appstores like F-Droid. It has a chilling effect on apps that are released to alternative app stores and may cause those stores to fail over time, thus killing FOSS apps at the point of distribution.

      That said, this is also over my head technically, so I would love if someone more knowledgable could weigh in.

  • thax@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    3
    ·
    11 hours ago

    4/5g card in mPCIE slot until I source a more portable device to do phone things. Yes, there are m.2 options as well. If the supply chain eventually dries up, for expansion cards and/or FOSS phones, then I’ll only communicate via my ISP or local mesh nets, until my computers break.

  • The Hobbyist@lemmy.zip
    link
    fedilink
    arrow-up
    6
    ·
    15 hours ago

    Google can’t control the device if you’re not running Google. GrapheneOS will still work like before, allowing you to run the apps you want. But the jury is still out on how long… I hope we can have a long term GrapheneOS solution regarding hardware.

  • dregs@lemmy.ml
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    20 hours ago

    Staying on Graphene for the time being. AFAIK should be able to still install apps whatever way I see fit.

    Graphene’s team has stated that they are looking into OEM’s to potentially work out a solution to make a suitable device to run GOS, since Google is locking things down.

    If it really comes to it, (long term), I’ll make the jump to a Linux mobile device, whether that’s a phone or a custom solution.

    Just because corpo’s are making things difficult, doesn’t mean I’m going to cave. I started this privacy journey 6 years ago and I’m not about to undo it because of greed and inconvenience.