Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

Special skills include: Knowing all the “na na na nah nah nah na” parts of the Three’s Company theme.

I also develop Tesseract UI for Lemmy/Sublinks

Avatar by @[email protected]

  • 12 Posts
  • 268 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle
  • Yeah, I found that out when I was using my old phone with T-Mobile. It was listed as supported, and it mostly worked, but there was at least one LTE band it didn’t support.

    T-Mobile uses multiple bands in the same area: one higher frequency, higher bandwidth, lower range one for fast data and a lower frequency, lower bandwidth higher range one to fill in the gaps. My phone didn’t support the lower frequency one so I would lose coverage if I was too far away from a window in my house (despite living close to 3 towers).

    Not to mention, they can and do reallocate spectrum periodically so while you may be fine for a while, if they reallocate and the device doesn’t support the new bands, you may suddenly lose service.


  • TL;DR: If it’s listed as Verizon-incompatible, treat it as such.

    It should work, technically, but there’s no guarantee. While Verizon shut down their CDMA network in 2023 and everything uses 4G/VoLTE now, it may have other limitations that prevent it from working as expected.

    You’d need to make sure the LTE bands it supports are used by Verizon in your area. If it doesn’t support the bulk of Verizon’s bands, you may find yourself (artificially) without coverage.

    Verizon may also refuse to allow it if it’s not on their compatibility list (though you can possibly SIM-swap into it from an already activated device). It’s been a while since I dealt with them, but from memory, they’re pretty strict about what devices they allow on the network.




  • Good. May other retailers and grocery chains follow.

    I hate those things - they treat you like a thief by default. I rarely use them and prefer to wait in line for the 1-2 cashiers, but I did the other day because I only had a few bottles of water to check out, and it was unsurprisingly horrible.

    Scanned and bagged all my stuff. More slowly than I’d have liked, but otherwise uneventfully. I unpocket my wallet to get my shopper’s card and debit card out. “Oh no, you didn’t!” the machine said as it called for backup. Cue waiting 3-4 minutes for the attendant to get to me.

    The machine asked the attendant if I was stealing and showed a replay of what it assumed must be me trying some Ocean’s 11 level of grand larceny. In the video? It was me getting my wallet out to pay.

    Absolutely no time was saved. Nothing was more convenient, and to top it off, I was once again accused of stealing by a bathroom scale with delusions of grandeur.







  • Admiral Patrick@dubvee.orgtoLinux@programming.devKaiOS
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    2 months ago

    I looked into it, but more for development purposes than installing it onto anything.

    Seems like it would be easy to develop for, but the ecosystem seems to be pretty locked down due to the permissions model. There’s some ability to jailbreak devices, but it’s not a huge list of supported models.

    For basic apps it’d be fine. But if I wanted to make custom applications for SMS, use bluetooth, make a new default dialer (e.g. to add SIP dialing), etc, it wouldn’t be possible since only OEMs can “bless” those. Even the next permission level down (Privileged) requires the apps to be signed by an authorized KaiStore.

    Since my goal at the time was to make a lightweight Meshtastic client, I just gave up since I wouldn’t have the necessary permissions to make it work.