This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/simtrace@lists.osmocom.org/.
Kevin Redon kevredon at mail.tsaitgaist.infoHi, If you have a corrected firmware and it works with another phone/card, then I can provide some experience with a similar problem I got. Sometimes I did get random garbage instead of the correct APDU. The problem was hard to find but obvious: it was because of EMI. I used SIMtrace on a NFC capable phone and used the NFC. Because the FFC is not shielded (hard to do for such a flat cable) and the cable runs under the NFC antenna which is in the back cover of the phone, it interfered with the SIM traffic. The solution is to remove the cover, or if you still need to use the NFC to cover the NFC antenna using 1mm copper tape in the inside, so to protect the cable. good luck, kevin Excerpts from jeremy brookfield's message of Mon Jan 16 18:05:34 +0100 2012: > > On Jan 10, 2012, at 7:23 PM, Holger Hans Peter Freyther wrote: > > > > i think this is known[1], what happens is that ATR and the first APDU end in the same USB message and then on the host the apdu_split does not work correctly, the hack to prevent this is below. > > > > Thanks for the suggestion which I have been trying to implement - but without success. > > I am experiencing the same problem as Ben reported in > http://lists.osmocom.org/pipermail/simtrace/2012-January/000227.html >