• 1 Post
  • 163 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • JustEnoughDucks@feddit.nltoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    13 hours ago

    The few things I don’t like about flatpaks (which become a problem on atomic distros that use almost all flatpak by design):

    • Some types of embedded development is essentially impossible with flatpaks. Try getting the J-link software connected with nrftools and then everything linked to VScodium/codeoss

    • Digital signing simply doesn’t work, won’t work for the foreseeable future, and is not planned to get working,

    • Flatpaks sometimes have bugs for no reasons when their package-manager counterparts don’t (e.g. in KiCAD 8.0, the upper 20% or so of dialog boxes were unclickable with the mouse, but I could select and modify them with the keyboard, only the flatpak version)

    • The status on whether it is still being actively developed or not (at least I hear a fair amount of drama surrounding it)

    But besides those small things, it seem great to me.





  • XP-pen has much more cost-effective options that are just as good nowadays since wacom hasn’t innovated in like 15 years lol.

    They also work out of the box in Linux, but for all of the shortcuts, they also have driver packages for every distribution and if it isn’t available, support will package the newest version for you (in my experience) in your chosen format and then send it to you and update the driver downloads.

    The XP Pen Deco Pro Gen2 is an absolute beast for a drawing tablet.

    XPPen also has a android drawing pad but that is normal android I think.

    If OP wants the drawing tablet experience with a screen, they can also get XPPen Artist Pro display tablet series which of the few artists I know in real life, are what most of them use.

    An actual drawing pad is much better than even an IPad for drawing, and you can also use whatever program you want (like Krita), not just the neutered programs that come on iOS or android.





  • Different person, but I have had my Xperia 5ii for 4 years. It hasn’t gotten any updates for 2.5, but in Belgium, bank apps and a national identity authentication app HAVE to work because the national ID reading software doesn’t work on atomic linux distros so I can’t risk putting Lineage on it to extend its lifespan. The fingerprint sensor stops working 4-12 hours after a reboot due to a prolific software bug and the battery life has degraded quite a bit.

    Maybe the FP6 would be a good successor. FP5 actually got 3rd for me when I took the MKBHD blind photo test after the pixels, the camera seems quite good now.


  • Yeah, I’m sorry but also the policy of OSM to not update road closures (and also no standard way to do it) until they reach a few months to a half year makes it almost useless for navigation in places with multiple construction projects throughout a year

    I can get 20 minutes added to my 30 minute route trying to find a good detour because organic maps just keeps shoving me back to a closed route.

    There is construction in different places 6-7 months of the year here. If I can’t trust organic maps to get me to my destination, then it is useless as a car navigation tool and I can’t switch from map services that update their maps frequently.


  • I had the same thing on Bazzite just with the local network, not a VPN.

    I believe it has to do with the firewall. You have to open the port both incoming and outgoing for 53317.

    But you literally have to be on the same network, so for example if both devices are on the same local network (hence local in the name) and your phone is on a VPN but your computer is not on a VPN, then it won’t work.

    It should work if you VPN into your local network remotely so that both devices are on the same LAN, however, then that won’t work anyway because you have to have physical access to the device to accept the transfer (you could probably use a remote desktop to do that, but then it is getting complicated)





  • I use Code OSS with clangd and the nvim extension (because Microsoft disabled their c/c++ tools) because i want access to the nrfconnect extension pack as a beginner. I don’t have to go searching in the documentation and compiling, then recompiling 10 times to self-discover the required devicetree parameters and figure out what drivers are available vs mainline zephyr.

    Plus the debug interface works well.

    For everything else possible it is vim/neovim, but I haven’t been able to find good neovim setup for nrfconnect.


  • No, ssds have a ton of wear leveling where data is shifted around and not deleted. Deleting data wears out the SSD, so it is held as much as possible with the controller. SSDs are like 10% bigger than advertised just to prolong the life.

    Even if you write the whole thing with random data then zeros, it will still have blocks in unaccessible (to normal users) places that contain old data.

    Always best to use disk encryption or keep any sensitive data in filesystem encryption like plasma vaults or fscrypt.


  • Hmmm, I used littlefs for SD card writing at work with an STM32F0 chip. It was hell working with files when tons of essential functions like appending and seeking simply didn’t work in the STM HAL… Plus dealing with opening and closing files and appending files and having to seek in them to find what you want, parsing results, cleaning old files, etc… compared to simple circular buffer and a start and end address of relevant data that can be erased once every day or week depending on use. Even with a daily erase of the NOR chip, they are rated for 100k program/erase cycles which would be over 250 years before degradation starts. I am not dealing with a ton of data nor the flexibility of a full UI/ app storage where I would definitely just use littlefs.


  • Thanks for taking a look!

    Intuitively for me, steps + bpm should be next to each other because the compiler will use bpm as the padding for the 24 bit steps. I intentionally did it that way. At least when I checked the memory addresses when testing it that was the case (there was no padding added). Wouldn’t it be potentially more problematic to have a bit field with a weird bit number, 24, followed by a 16 bit member that can’t be “fit” into the 32 bits that the compiler wants to assign? or is that not how it works.

    I’m not quite sure what you mean by your last point. The flow would go: acquire data -> add to structure -> fill up a page worth of data (or a sector) -> write to memory. Then pulling it out would be: read from memory -> put in structure -> process -> send data via bluetooth. If I change the layout of anything, that would require a reflash of the MCU and previous data would already have been transferred over bluetooth (assuming end-user OTA flashing or just being in a vicinity of a phone and not out and about where memory saving is necessary) and would no longer be needed to be stored/pulled from memory. Or is there another case that I am totally missing?