I suppose i can't claim true 100% hardware support without having it work and it doesn't seem much trouble so i think i'll add it as an edev and the user can decide what to do with it.
Now that i am thinking about it, There should be nothing stopping you from mapping a specific finger to either wipe data or load into a decoy. I'll look into this.
EDIT: Confirmed, the reader gives the ID of which print was matched, so a userspace implementation for per finger macros should be possible, this goes beyond unlocking or duress too, in theory any script could be called from a specific finger?
I did look at charging-sdl but since it was removed in 2023 I thought it would be better to start fresh then inherit a legacy codebase, if the upstream team wants this to go into charging-sdl instead of a new package I will be happy to oblige.
If i understand correctly this is a zero tolerance policy, which is why I haven't send any patches to pmos yet, while it is allowed in the linux kernel which is why im currently upstreaming everything there.
If you're looking for a fully functional phone i would recommend getting the Fairphone 6 with my image, it is almost fully functional and i will make it so in the coming days.
You can also purchase these trough my shop if you want, but the image is open source and free to download, so any fp6 will do.
And yes, if I do end up making the riscv phone (or any other hardware) everything will be open source, the hardware and the software.
Should I get to the point where i will be selling them ill probably sell them as both kit and fully build.
But one can just take the files and order the parts themselves and assemble for no cost.
I do have to say again that actually making this is still very much an unknown, the FP6 will be available much faster. But i can promise that if a catcrafts original phone will be brought out it will be fully open in all aspects to the maxium of my ability. (For example modem firmware is closed and signed so while i really want to open source it i myself don't even have the source)
Op basis van onze beoordeling hebben we vastgesteld dat je onderneming een risiconiveau heeft dat buiten onze acceptatiecriteria valt. Zoals beschreven in artikel 4.1 van onze Gebruikersovereenkomst kan Mollie haar diensten weigeren of beëindigen wanneer een onderneming niet voldoet aan onze risicovereisten.
Translation:
Why has my account been closed?
Based on our assessment, we have determined that your business presents a level of risk that falls outside our acceptance criteria. As set out in clause 4.1 of our User Agreement, Mollie may refuse or terminate its services if a business does not meet our risk requirements.
I guess they are referring to this paragraph in 4.1:
Mollie may also decide, at its own discretion, to decline products and services that are not explicitly mentioned on the list, but which pose an unacceptable risk to Mollie based on its internal policies.
But I have no idea why i am considered unacceptable risk?
I suppose i can't claim true 100% hardware support without having it work and it doesn't seem much trouble so i think i'll add it as an edev and the user can decide what to do with it.
Could probably also make it a sequence of several fingers to reduce risk even further.
No, it currently does nothing. No idea if its even in the DTS.
Well that's not really under my control as i don't make the sensor, but it does expose an accuracy value, so the user can set their own threshold.
Well then there's not much point to a fingerprint sensor is there xd
Now that i am thinking about it, There should be nothing stopping you from mapping a specific finger to either wipe data or load into a decoy. I'll look into this.
EDIT: Confirmed, the reader gives the ID of which print was matched, so a userspace implementation for per finger macros should be possible, this goes beyond unlocking or duress too, in theory any script could be called from a specific finger?
Sounds like a cool feature!
Looks like he beat me to the punch, but this proves it is possible atleast. Coming soon to a fp6-img near you!
My version is also mostly ready. So expect a post about it soon.
I hope more people take this chance to leave X for good.
Well the biggest issue is the battery boot loop of death.
It takes time to initialize the USB-PD, so before that it gets very little power.
If before that it already sags the battery causing it to shut down again then it never charges.
Is this true?
I mean funny meme hahaha windows sux but isn't the license agreement of Linux GPLv2? not to mention the license of the distro and all the packages?
https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
Heyo! Thank you!
I did look at charging-sdl but since it was removed in 2023 I thought it would be better to start fresh then inherit a legacy codebase, if the upstream team wants this to go into charging-sdl instead of a new package I will be happy to oblige.
I'll be happy to upstream everything I can but I am currently not doing so to pmos in adherence of https://docs.postmarketos.org/policies-and-processes/development/ai-policy.html
If i understand correctly this is a zero tolerance policy, which is why I haven't send any patches to pmos yet, while it is allowed in the linux kernel which is why im currently upstreaming everything there.
Sort of, when I said that I haven't looked into yet, I would say it's mostly functional already but that is also a preliminary guess.
It's more functional then most things in this bringup but the judgment on how functional is still out until I do something with it.
Guess i forgot how to read lmao, somehow i tought the comment i replied to said "as the car beside them then turns the red"
Mom, i can i have podman?
Mom: we have podman at home.
Podman at home: rootless docker
All of it, they are software compatible.
https://wiki.postmarketos.org/wiki/Fairphone_(Gen._6)_(fairphone-fp6)
If you're looking for a fully functional phone i would recommend getting the Fairphone 6 with my image, it is almost fully functional and i will make it so in the coming days.
You can also purchase these trough my shop if you want, but the image is open source and free to download, so any fp6 will do.
And yes, if I do end up making the riscv phone (or any other hardware) everything will be open source, the hardware and the software.
Should I get to the point where i will be selling them ill probably sell them as both kit and fully build.
But one can just take the files and order the parts themselves and assemble for no cost.
I do have to say again that actually making this is still very much an unknown, the FP6 will be available much faster. But i can promise that if a catcrafts original phone will be brought out it will be fully open in all aspects to the maxium of my ability. (For example modem firmware is closed and signed so while i really want to open source it i myself don't even have the source)
Shop: https://catcrafts.net/shop
Image: https://forgejo.catcrafts.net/Catcrafts/fp6-img
This is what they sent me:
Translation:
I guess they are referring to this paragraph in 4.1:
But I have no idea why i am considered unacceptable risk?
Yeah, but it's more of the same as far as I understand, a closed scheme that requires a payment processor to enter.
It's also not available in the Netherlands yet.
I mean if it's just a question of work i would do it, but it costs a ton of money as you said.