• 3 Posts
  • 157 Comments
Joined 1 year ago
cake
Cake day: October 11th, 2024

help-circle



  • IMO Snikket (XMPP) is the easiest all-in-one solution with audio/video chat at the moment. Pretty good on resources too.

    I currently host a Matrix Synapse server, but:

    • Matrix seems to be expanding in the corporate / institutional direction, more services are expected for regular functionality
    • Element X (upcoming client) breaks calls compatibility with old Element, now requiring Element Call. It’s kind of a mess, I presume this is to support group calls, but makes it a PITA to use currently.
    • Even with small number of users, Synapse DB grows in size due to state_groups_state table, non-deletable users, and copying ALL data from other servers’ rooms (this one is by design but still…)


  • Yaky@slrpnk.nettoSelfhosted@lemmy.worldxmpp and iphone
    link
    fedilink
    English
    arrow-up
    3
    ·
    13 days ago

    I ran prosody server and used Siskin IM as a client, it worked pretty well. But as others mentioned, since this is Apple, the client developer has to run a push server, no background processes and long-polling allowed. Some other XMPP clients (Secret Messenger I think) did not have that set up and do not have notifications.



  • Looks like BM818 in Librem5 supports VoLTE, but might have issues with some networks.

    PinePhone’s (and one of Mudita’s phone’s) EG25 modem technically supports VoLTE, but was very flaky for me (in a mid-low signal area)

    FuriLabs (FLX1) seems to have VoLTE working.

    Ubuntu Touch explicitly states that it does not support VoLTE.





  • WDYM soft-bricked?

    Here’s what I did: I had a OnePlus (before there was a Lineage image for it), rooted it, disabled Google Play, which made all apps scream at me repeatedly (although still worked), then installed MicroG, which made the screaming stop, and most apps continued to work fine (except a specific one that used Google Maps API on a page - MicroG was not enough for some reason)






  • “Android is Linux” is a bit oversimplified.

    What the is issue, still simply, the way I understand it:

    • Linux kernel contains drivers for the specific hardware used in devices (processors, modem, memory, display, camera, etc.)
    • Each Android smartphone has different hardware configuration
    • Hardware manufacturers want to guard their secrets, so they sign contracts and NDAs with phone manufacturers
    • Phone manufacturers create a unique, dead-end fork of a Linux kernel that contains drivers and is configured specifically for that model. (There are exceptions, but generally)

    So yes, Android uses a Linux kernel, but in most cases, a very specific one.

    Why not replace it? This requires:

    • Access to the bootloader and ability to read/write to internal storage on low level, and manufacturers lock it down.
    • Knowing the hardware and the drivers. As mentioned, manufacturers will provide drivers only to their contracts. So someone would need to write a driver.
    • Once someone writes a driver, it can be added to mainline Linux, available to all.
    • That is why “mainlining” a device is a big deal - that means that the kernel for that device can be built, and going forward, that device will be supported for all future kernel versions.