Conversation

Notices

1. Embed this notice
   Pawlicker (pawlicker@makai.chaotic.ninja)'s status on Friday, 11-Oct-2024 05:20:41 JST Pawlicker

   It's interesting to see the difference between ewaste in the early 2010s and ewaste today.
   
   I had a Fire Phone (fire sale edition) back in the day before I gave it away to someone. People online were passing around guides on how to install Android ROMs on it, or to install Google Play Services if you didn't want to gamble with a custom ROM (since custom roms sometimes had "funny" side effects from experience). People would openly buy orphaned devices back when tablets and phones were still $$$ to mess with them and make them more usable.
   
   The whole culture of "buying an i-opener just to mod it" and "modding an Xbox as a fuck you to MS" was still around. You also didn't need to login to say, some network system to "activate" a device or force firmware updates (iPhone, Xbox One, Oculus Quest 2, increasingly more these days) and Android/similar devices back in the day were usually not locked down.
   
   Then Google and carriers put an end to that and big corporations did too in the name of security. Sure your phone might be vulnerable to shit like Stagefright or Heartbleed, Dirtycow, and many other Linux kernel bugs, or stuck on an old SSL version, but hey at least the bootloader is locked so you won't be running tampered software, right?
   
   What's going to happen to all the Quest 2s if facebook pulls the plug?
   
   RE: https://makai.chaotic.ninja/notes/9z4smmy0k5

   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 11-Oct-2024 05:20:40 JST 

     in reply to
     @Pawlicker >since custom roms sometimes had "funny" side effects from experience
     I remember some guy on /app/ complaining about how his wallpaper got randomly changed to swastika on some custom ROM, apparently it was in celebration of some Indian holiday or something.
   • Embed this notice
     Pawlicker (pawlicker@makai.chaotic.ninja)'s status on Friday, 11-Oct-2024 05:23:25 JST Pawlicker

     in reply to

     • 

     @mint@ryona.agency all I got was "cameras not working after flashing" which happened twice at least.

      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 11-Oct-2024 05:24:45 JST 

     in reply to
     @Pawlicker I owned some Xiaomeme phone for a while, broke its screen and had it replaced, which for whatever reason resulted in touchscreen not working. Apparently it works on official ROMs but not most of custom ones unless you flash a kernel that has a patch for it.
   • Embed this notice
     Pawlicker (pawlicker@makai.chaotic.ninja)'s status on Friday, 11-Oct-2024 05:26:40 JST Pawlicker

     in reply to

     • 

     @mint@ryona.agency sounds about right for some of that shit (different driver/similar weirdness)

      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 11-Oct-2024 05:27:46 JST 

     in reply to
     @Pawlicker Yeah, Xiaomi is notorious for picking different suppliers for parts and then patching it in firmware, like with FPC/Goodix fingerprint scanners (the latter of which also happened not to work with SELinux in Enforcing mode).