Admiral Patrick

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

Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

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

help-circle
  • See edits: Push is present and totally works; enabling it is just very different from K-9

    On K-9 Mail, it’s in Settings -> {Account} -> Fetching Mail -> Push Folders

    On Thunderbird Beta, the “Push Folders” option should be in the same place, but it is totally missing for me.

    Edit: If you go into Manage Folders and then Inbox (or any folder I guess), there is an “Enable Push” option. I enabled that, but it doesn’t seem to do anything.

    Edit 2: Ok, the folder-level enable push seems to work now. I had to grant the Alarms and Reminders permission before it could run in the background. It didn’t automatically get or prompt for that, but granting that in app settings fixed it


  • Is there any difference, currently? Aside from the logo, I can’t see anything different from K-9 Mail.

    One of the biggest draws is the ability to transfer from K-9 Mail to Thunderbird for Android

    I literally just tried that, and it failed. LOL. Ended up setting up the account manually.

    Edit: Also doesn’t seem to have the push mail option like K-9 has. It does have push, it’s just enabled very differently. Go into Folder Settings, select a folder (Inbox in my case), and then turn on “Enable Push”. You may also need to grant it Alarms and Reminders permission manually on newer Android versions if it doesn’t prompt for it.








  • I think OEM, non-carrier OnePlus phones do (someone correct me if I’m wrong or out of date). I just setup Lineage 21 on a OnePlus Nord N200 (ca 2021) and after enabling bootloader unlock in developer settings, I just had to pass the oem unlock command to fastboot. The carrier-branded ones require you to go through the unlock code request, and those take a minimum of one week (and can be cockblocked by the carrier for whatever reason).

    There may be some kind of Android check, though, because the “Allow OEM Unlock” developer option was greyed out until I connected the phone to wifi for a few minutes. Not sure what that’s about, but it’s common for most/all android devices. I don’t know of any device that lets you unlock the bootlaoder without first enabling that in dev options.




  • Admiral Patrick@dubvee.orgtoAndroid@lemmy.worldFond memories
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    19 days ago

    Technically true, and niche devices with QWERTY keyboard like the ones from PlanetCom still exist. But they don’t really benefit from economies of scale, are prohibitively expensive, and are usually at least a generation behind in hardware.

    Plus Apple started, and Samsung joined, the “thinness wars” that got us to where we are today. Slide out keyboards were definitely a casualty of that, and I still hold some hope, albeit slim, that those could still make a comeback.


  • It’s been a while, but I think that’s mostly how mine worked. You had to launch it from within Windows Mobile, but after that, only Android was running the device. Android booted from the SD card and basically kicked Windows mobile out of memory and took over from there. AFAIK, WM wasn’t still in the background, at least on the Froyo build for it. I want to say that’s the case since the TP2 didn’t have much RAM, and Android ran way too well to be sharing memory with Windows Mobile lol.

    Regardless, my interest in building and running custom ROMs was born the day I did that lol.


  • Admiral Patrick@dubvee.orgtoAndroid@lemmy.worldFond memories
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    2
    ·
    edit-2
    19 days ago

    I blame Apple (and then Samsung for copying Apple) for stealing this form factor from us.

    Didn’t have that one, but I did have the HTC TouchPro2 that came with Windows Mobile but was able to shoehorn a functional version of Android “Froyo” on it. Peak smartphone form factor limited by the technology of its time. Shame.


  • We have very similar device requirements lol. Though I can’t speak much for the camera portion (I’m not a shutterbug and deal with whatever).

    I just upgraded my trusty workhorse OP3 to a OP Nord N200. It’s a few years old, but that usually helps since the custom ROM support is more mature.

    OnePlus is usually pretty easy to unlock as long as you get an OEM model (e.g. not one branded / sold by a carrier). Been a while, but if you buy an OEM one, I think you can just unlock it without having to request an unlock code. I had to jump through hoops to convert this T-Mobile carrier model Nord into a global version, but after that I was able to unlock the bootloader with just the fastboot command (e.g. didn’t have to request and flash the cust_unlock.bin. Was still carrier-locked to T-Mob, but that’s who I use, so no biggie.

    Similar to what you’re seeing with ASUS, Motorola used to be, but I think their unlocking policy has gone downhill as of late. Haven’t messed with their hardware for a while.

    I haven’t used Nothing Phone at all, but they were contenders (and still are) when I was looking for a successor to my OP3.

    Same assessment of Fairphone: ideologically pure, but other issues ruled them out for me.


  • Should be pretty easy if you use Nginx. You can just proxy the full URI and params.

    Main network:  192.168.1.0/24
    Restricted network:  10.10.10.0/24
    ShellyPlug IP:  10.10.10.5  (assuming it's REST API is on port 80, but adjust if needed)
    Reverse Proxy IP:  192.168.1.10
    
    Nginx "conf.d/shellyplug_proxy.conf": 
    
    server {
      listen 80;
      server_name  shellyplug.lan;
      location / {
        proxy_pass http://10.10.10.5:80;
      }
    }
    

    As long as your reverse proxy (Nginx) on your main network can reach 10.10.10.5 port 80 on the restricted VLAN, it should work, and you should be able to use call the api from your main network at http://shellyplug.lan (or http://192.168.1.10) just as you would to it directly to the plug on its restricted network.

    HTH



  • Easer cannot switch Wi-Fi networks: I was hoping to use the Shelly Plug’s local access point (AP mode) for a more portable solution, but since Easer doesn’t have permission to switch networks, I’m restricted to my home network.

    What about setting up a reverse proxy on your main network that can then make the call to the Shelly Plug on its VLAN? I do this with my HomeAssistant and its devices which are all on an isolated network. The HA machine has internet access, but none of the other devices do (via firewall rules for that VLAN).

    You’d have to make a firewall rule to allow the reverse proxy to be able to reach the restricted network, but that’s pretty straightforward.

    Easer cannot start external apps: It also can’t trigger external apps that might help with network switching or more advanced controls.

    Not familiar with Easer (will have to check it out, though), but can it make an HTTP(S) call natively?