[–] 2 points 1 year ago (2 children)

We are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified.

Isn't this what we wanted?

  • source
  • [–] 1 point 1 year ago (1 child)

    Yeah no idea about the Pixel 6a or how difficult it is to swap batteries, but 400 cycles is at least a couple of years, right? If the swap isn't a big hassle, just do it again. Or for that matter if the old battery is still good after 400 cycles and the phone wants a replacement, just take the old one out and put it in again.

    It doesn't look too bad:

    https://www.ifixit.com/Guide/Google+Pixel+6a+Battery+Replacement/152516

  • source
  • parent
  • context
  • [–] 3 points 1 year ago (1 child)

    I don't have an answer for you, but I took mine to a repair shop for battery replacement and the wait time for a replacement battery is 4 to 6 weeks. I mean it's nice that people are replacing the batteries rather than just getting a new phone, but that must be a LOT of bum batteries to make them so scarce.

  • source
  • [–] 11 points 1 year ago

    This will make it more difficult and dangerous to make and publish the apps needed by people who work against oppressive regimes and cynical businesses. Bad megacorp, Google

  • source
  • [–] 1 point 1 year ago

    What you describe are feature requests not issues.

    The reason you don't find them is simple: many projects don't want q myriad of form based user requests. Depending on the specific project it's either vote based or non existent in my experience.

    AOSP as specific example is mainly maintained by Google who are notorious for being very ... Wet in their own ways on how to do feature roadmaps.

    I think you're naked by both your life and that of the projects you want to support tougher by thinking about these things as issues. Just a rule of thumb m: it's an issue if it's not working as documented or behaving in a way that can be described in terms of "right" and "wrong", not preference.

    Otherwise it's a feature request.

    Your points for example are all aimed at quite advanced users. I'm not an AOSP dev but just looking at the way they developed their menus over TR years I'd be surprised if they'd share your evaluation.

  • source
  • [–] 1 point 1 year ago

    Just to herd a warning then from a Dev perspective: you want to remove them before interacting, not just opening.

    I can send files without ever opening them and the sharing would keep the meta data if you'd not open the files manually with the cleanup tool.

    Personally I've had a camera app a while back that I could configure which meta data it saved but I simply stopped sharing photos on social media and so this become s non issue for me :)

  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    Can't wait to see what security features this will come with by default.

    honestly, how many people use large displays attached to a phone. I think I connected mine to a TV once to watch a movie with friends.

  • source
  • [–] 5 points 1 year ago*

    I'm not denying anything that you outlined and also share your concerns about Google exploiting the FOSS community.

    GrapheneOS seems to be able to side-step Google's fuckery while also having an Android OS that keeps Android's most important functions usable.

    I guess we'll see over time if the projects that don't have the funding that GOS has will be able to keep up with an increasingly hostile AOSP.

  • source
  • parent
  • context
  • view more: ‹ prev next ›