Correct, on my profile here on DT i have a discount code linked that has a blanket discount on my entire store on tindie. even if it isnt DT related.
DT Club members get special treatment. If you want to exchange, reply to your order email and weāll sort it out.
As much as I love the idea of the Mega I gave it some thought and I think that the Mega is just too big to be comfortable on the wrist and I would prefer to keep my flex implants there for the time being.
Thank you for the offer!
and a 22pf capacitor
I think I will try that out when I have time to breathe again, thanks!
NB: You might get lucky with the tuning, or you may need a VNA., which makes it mor expensive than just buying a #HammyResonantRepeaterJammyā¢
I was kinda considering getting a NanoVNA anyway so⦠lol
Thank you for the offer @Hamspiced, I will try the DIY option before bothering you with anything tho.
I remember sending the logs on the forum somewhere but do not see it here⦠Weird.
Will look for those and send them your way.
iPhone is currently completely dead and wonāt turn on for a while so I will send the iOS version alongiside a link to the logs.
Also sorry for completely disappearing like that and reappearing later. Life gets in the way lol
I sadly have the implanter ready and even enthusiastic about implanting all this stuff into me, but it is still all in a box and in their sterile bags because I do not want to implant something that I cannot really use.
What is sad is I just got a swimming pool pass that I cloned into a 5577, so I would have had a use if I implanted that one at least lol⦠Now Iām tempted to just implant the syringe one into me right now to weird out people at the pool.
Hmm. I just received my Apex Flex and Iām having the same issue on my Samsung Galaxy S23 Ultra. I can connect the Fidesmo Links but not FIDO Security.
The OTP seems to instantly fail as well. The app doesnāt even give me time to scan the implant like the Fidesmo Links App does, both just instantly fail. Is that normal?
Update: tried installing all apps. I could only connect to Fidesmo Links, and BoB Nordic Public Transit. All others fail. And BoB doesnāt give me the option to destroy.
The FIDO applet is large and requires multiple rounds of communication exchanges between the phone and the chip. It took me multiple attempts to get it to install.
I would also install the FIDO applet before you install anything else to rule out a storage issue.
Is your Apex implanted yet or are you trying to install applets on it through the packaging? I had very poor luck using my Samsung S23 Ultra to add applets to my Apex while it was still in the the plastic. The only way I even got close was to set my phone face down, place the plastic bag with the Apex in on top of it with the chip in a mostly vertical orientation on the back lower portion of the phone, then use some paper to lightly apply pressure to the back of the bag. I would then have the phone hanging slightly off the edge of the desk so I could tap the start button.
Also, Iāve experienced some weirdness with NFC on the S23. It seems that having a bad/failed read will sometimes stop NFC from operating until you close the app and/or stop and start NFC again. Iāve experienced this with both the Apex Manager app and the Yubikey app. My process now is that after every failed applet install I go to settings and turn NFC off and back on before trying again.
It is much easier to install applets into the chip using a USB reader and a PC. Another forum member recommended the ACS ACR1252U reader and it works very well. You can use Fidesmoās fdsm tool to install applets from a computer. Iāve only used it on Windows, but I believe it will work on Mac and Linux as well
EDIT
@GrimEcho beat my post by 1 minute.
I just read it, and thereās some great advice in there.
anyway, hereās some bread crumbs
just received and still in the packaging, or Is it under the skin?
Any further updates from 3 hrs ago?
Still the same issues?
Did you try a manual deploy/ destroy?
Through the package.
I got the acr1252u. Wasnāt getting the best of reads with it, but now that I have the fdsm tool link, Iāll try that tomorrow.
Yeah, same issue. Phone is vibrating, so I know itās reading it.
Manual destroy worked, Thanks!
Tried the manual install_fido2, but got an error service was not found. Changed service ID to just āinstallā and the correct app came up (maybe want to confirm with someone smarter, and update it on that part of the forum for future reference lol). But unfortunately still a no go. Iāll try the 1252 tomorrow at work.
Heading to bed lol, might hit the gym in morning before work.
If you are running on Windows, you have to be in an administrative command prompt to install the FIDO2 applet (the others seemed to install fine with a normal command prompt).
.\fdsm.exe --verbose --run cc68e88c/install
and
.\fdsm.exe --verbose --run cc68e88c/destroy
I only learned this after posting a few days ago, which is why I ended up making a bunch of attempts to install the applet using my phone.
I made a mistake in my earlier reply. Iāve been having the most success on my S23 Ultra by placing the chip horizontally on the phone, not vertically.
Just to confirm, you launched the cmd window using āRun as administratorā?
Oh also what does apex manager say you have for free space⦠assuming you have free memory app loaded.
Yes.
Unfortunately, that wonāt install either.
Odd, Iām getting similar behavior now. Iāve tried installed several applets via fdsm and they all are immediately failing.
Also, when I try and install/connect a service using the Fidesmo Android app, I get a failed message even before I tap the chip to the phone. I think something is going on with Fidesmoās servers right now.
For reproducibility ā
- Close Fidesmo app and open it again
- Tap Apex to phone
- See list of installed applets.
- Connect a service
- Pick anything (I selected VivoKey SmartPGP), tap connect
- Watch debug output (downloads cap file from server) - now on the install screen
- Tap āConfimā without chip being anywhere near phone
- Status briefly says āplease waitā, then I immediately get a āFailedā message.
It fails right where it should normally say āConnect ā Put the wearable against the back of the phone and hold onā¦ā.
Thanks for bringing this up. Applet deployment seems to be broken in general, I see errors on my test devices as well. I think this is a Fidesmo issue. I will investigate tonight.
Update: Its a problem on Fidesmos servers. We are working with them to resolve the issue.
Thanks for the update!
I swear I didnāt brake it ![]()
The issue has been resolved, app installation should work again. If you still encounter issues, please let me know.
All good in da hood! Successful via the app. Much appreciated.
Iāll play around with the FIDO2 after lunch
@SomeGuySomewhere did you ever manage to install?
Iām having your same Fido2 issue when trying to install from my Pixel 6
There seems to an issue with the FIDO2 app on Fidesmo. I will investigate. Thanks for bringing this up.
Edit: deployment still works using the fdsm cli. Try to use another smartphone if you can - did it work before?
Edit: The issue appears to have been transient. Deployment works on my phone again. If you still have issues, please send me the logfiles of the Fidesmo App.
Thanks for checking: itās still failing for me.
Got 40% free, so Iām positive I have enough space.
Will probably try desktop/cli, but Iām confess Iām slightly afraid of bricking the chip, not knowing why itās failing.
Hereās the log:
Start delivery! AppID: cc68e88c, ServiceID: install, CIN: 0000E60B6E2134
SetSingleUserAnswer! ID: SetupRequirementConfirmation = 1
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: talkingToServer
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToServer
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToDevice
Command: 00A4040008A00000015100000000
Command: 8050300008B632FE3543D5B13A00
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToServer
Command: 6F108408A000000151000000A5049F6501FF9000
Command: 000003234126562000943003706D3DFB80A2C7791877C865A0E21A2A7C00002D9000
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToDevice
Command: 848203001086A0366F534E684E232322DF9A691F3E
Command: 84F2100218ECC328192B32BE4738599053C5DE813E7572B4CC4309E41F00
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToServer
Command: 9000
Command: E3254F07A00000015153509F700101CE02FFFF8408A000000151535041CC08A000000151000000E3354F0FA000000396545300000001000D01009F700101CE0201008410A000000396545300000001000D000000CC08A000000151000000E3354F0FA000000396545300000001000406009F700101CE0201008410A0000003965453000000010004000000CC08A000000151000000E3474F0FA000000396545300000001000609009F700101CE0201008410A00000039654530000000100060000008410A0000003965453000000010006000010CC08A000000151000000E32C4F06A000000003109F700101CE02016310
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToDevice
Command: 84F2100318951D735DF936A78F32DF3A6C6D207F7F937122D87333FB9000
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToServer
(Bunch of commands which seem to move data; cutting to fit message size)
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: apdusToServer
Command: 9000
Command: 009000
Command: 009000
Command: 6A84
Command: 6985
(The command gets repeated a shitton pf times)
Command: 6985
Session ID: : d65a5ad8-9de4-49e6-9314-81e86503d003
OperationInProgress! Direction: talkingToServer
Delivery finished! ServiceStatus(success=false, instanceElement`Preformatted text`s=null, message=Installation failure. You may not have enough free space for the FIDO2 applet and the attestation certificate. You might consider removal of another app to create more storage space., scriptStatus=null, clientMetadata=null)

