𝒍𝒆𝒎𝒂𝒏𝒏

Hey! Please contact me at my primary Fedi account: @[email protected]

https://lemmy.one/u/[email protected]

  • 12 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle




  • Free google play credit, I usually get an email every year for it

    But I do pay for Plex, despite Jellyfin being a thing. If I like something and it’s worth it to me personally, why not 🤷‍♂️… but you will never find me defending their kinda crappy decisions like the new Discover feature, removal of “All Songs” from the plex apps in favor of moving people to Plexamp, removing the Gallery sync a few years ago etc.

    Some people want their software to be 100% FOSS all-eyes-on-the-codebase, others just do a balancing act based on their personal values.

    I value my software to be “transparent enough” in how it operates, “just work”, and hackable to some extent - if I really wanted to I can swap out the ffmpeg binary that Plex uses for transcoding to something else (doesn’t remove the Plex Pass limitation for those curious), I can hook into the server API to change ambient lighting colour based on the cover/background of whatever media is playing, I can create speakers running a Linux board to cast Plex media to, etc. But once that hackable ship sails, then I will look to FOSS alternatives.

    For Niagara, everything “just worked”. No noticeable bugs, fast search, consistent feel and design, useful contextual info (e.g. next calendar event shows under the clock), and gestures that made sense for its overall UX. Using it felt less like you were using a “launcher”. The yearly sub was cheap enough that I wouldn’t mind covering for it if I didn’t get credits, and having a single person working on software usually comes with a high level of attention to detail (particularly in performance and UX) but it does have the downside that the experience may be more opinionated and closed compared to if it was a community-driven FOSS project instead IMO.

    Alas, google didn’t send credits this year, Niagara made less sense for value/worth-it compared to Kvaesitso, so I abandoned it.

    For me, Kvaesitso does everything in a slightly different, much more customizable way, and being FOSS was one of the things that made it particularly attractive as a replacement






  • I was pretty careful in specifically not naming this a “win”, just “great”. A true “win” would be a recent model as you mention.

    Personally however, it’s not 1980s/90s anymore where recieving a service manual with your purchased property was the minimum standard - I feel the bar is pretty low in general when discussing companies’ attitudes providing owners with the full documentation and firmware for their property

    I thought this was noteworthy, taking into account Tesla’s previously horrible attitude towards people who repair and rebuild totalled teslas, where the company subsequently remotely disables onboard features such as autopilot and the ability to use a supercharger as soon as they find out. This car has neither of those features of course, but it at least hopefully sets some kind of precedent.

    Despite the age and production quantities, it’s still extremely rare for any company/manufacturer to actually release these materials to the public IMO - particularly including the firmware and diagnostics tools on GitHub, meaning owners don’t need to waste time reverse engineering their own vehicle, or be stuck paying someone else to figure out why it isn’t working…

    Hopefully this move helps encourage more auto manufacturers to start releasing resources for their vehicles to the public, instead of restricting these to specific dealers (some of which thankfully leak some to the public 👌)




  • I’m assuming you’re using Android 14.

    Do you actually see your lockscreen or your launcher, or are you just dumped to a “Android is Starting” dialog after the boot animation goes? I’d try to get an adb logcat up to see what the device is doing/gotten stuck on, but you would have needed to authorize your device beforehand…

    Are you using Magisk for root or riru? Seeing as you’re using a very recent version of Android, I’d say try a dev build of Magisk and see if that works any better. I would have also suggested using an older version of magisk that doesn’t exploit via zygote injection, but your version of android is too new. Have a poke around on the github Issues tab and see if anyone else has gotten stuck with the same issue as you.

    Another thing would be to try changing your phone’s boot slot in fastboot (don’t flash, just change slot) - maybe something for the zygote injection is missing from the boot slot your device defaulted to?