That would make sense. TheMightyCat did say it would be a while before his additions would make it into the stable branch.
I recall one of his recent posts talking about the call audio routing issue and how he was able to solve it, but who knows, maybe an issue will pop up somewhere or I’m misunderstanding what he said in his posts.
Thanks for the links. It’s interesting to me that they still have some, when Fairphone doesn’t sell them anymore.
More expensive and older. Yeah, that’s a tough justification.
Thanks for letting me know about the wrong link, should be fixed now.
FP6+ makes sense. I initially figured you wouldn’t go for the FP5, because I don’t immediately see it for sale on the Fairphone website or anywhere else.
By the way, I think it’s really cool you’re going to be offering FP6 w/ PostMarketOS in the near future. My phone is still in good working order (and don’t want to create needless e-waste), but not excited about the Google lock-down, so may be looking to switch out in the next year. Depends if I can get any decent price for my phone, otherwise probably ride it until its closer to death or the google lock-down becomes too rough.
Looking at the PostMarketOS Wiki for Fairphone 5, it looks like audio, camera, calls, nfc, and fingerprint are all partial or broken.
themightycat@ani.social has been able to get audio, calls, and NFC working on the Fairphone 6. According to him, he is currently working on the camera(s) with another developer and also going to try and get the fingerprint reader working too).
I’m not sure how compatible they are, but it might be worth asking if he could look at porting the Fairphone 6 to Fairphone 5 for people. Alternatively, all his additions are open source, so someone else could take a look and see if they are portable.
Edit: corrected TheMightyCat’s code repository link.
Looks like in maybe a month there will be a viable fairphone 6 with PostMarketOS (via user TheMightyCat):
Haha. No worries, happens to us all :)
We are past my knowledge on the subject (thunder vs voyager opening link methods).
Hmm. Is your setting “open links in app” (general settings menu). I’m on Voyager version 2.47.4, Android 16.
Interesting, thanks for sharing.
FYI, link works on desktop, but errors on mobile via voyager (“This site can’t provide a secure connection”, “ERR_SSL_PROTOCOL_ERROR”).
I am not knowledge in the area, but wouldn’t it be better to work to add a Linux build to comaps, rather than starting from relative scratch?
Tldw: He mentions the new beta version of Ubuntu touch solved many problems. And he’s going to use it as a daily driver going forward.
The problems he had were banking apps, photo sync, copy-paste from waydroid to Ubuntu touch, and notifications between waydroid and Ubuntu touch. He shows the waydroid to/from Linux works in KDE. So, probably a relatively quick fix for those 2 problems.
Edit: spelling.
It might be a little short. I’d say 2 full days at a location is probably a good place to be, as long as you have rest in between (your travel days).
I think on later trips you could stay longer in areas you really liked or explore further in those areas.
Have fun on your trip :)
I know nothing about the space, but if you set up a subsidiary in the US/Canada, would that get around the issue? Like ship to subsidiary with your insurance and then the subsidiary gets US/Canadian insurance for the final leg to the customer.