FeliCa Dude

[FeliCa Dude @FeliCaDude]

@WeirdAlSuperFan @skydoki All you need is another Android phone with NFC support running TagInfo: disable support for everything except Type F in TagInfo, then use it on your Pixel 5.
If you see an IDm value, root plus device property modification may allow Osaifu Keitai to function.

[FeliCa Dude @FeliCaDude]

Both Pixel 6 Japan SKUs have IC type 0x18 in the PMm field just like the Pixel 5, so these are almost certainly Mobile FeliCa 4.1 devices.

Even if they were 0x19, they could still be version 4.1: Mobile FeliCa 3.0 had two type codes, and 2.0 had four.

https://t.co/ralQ3NQIlE

[FeliCa Dude @FeliCaDude]

@egg8362 @Kanjo On Mobile FeliCa 4.0 and later, if virtual cards are deleted, you will see 'unused': in that condition, the device can be transferred to a new owner and they will have no problems with it. This is what resale stores look for. Block usage data is only shown on 3.0 and below.

[FeliCa Dude @FeliCaDude]

@elevtechlift @Kanjo @Sony @sonyxperia @SonyXperiaCA No. The person making that statement has no idea what they are talking about and is blowing hot air. All NFC Forum certified devices should support FeliCa card read/write but Osaifu Keitai is necessary to emulate Suica et al. Sony devices sold outside Japan do not support that.

[FeliCa Dude @FeliCaDude]

@Kanjo Not ABT. It’s a commuter pass valid for one day between ‘virtual’ stations which define the pass. It uses the same blocks as those for commuter passes.

Those blocks aren’t readable without authentication but a gate agent can see them, even after expiry.

[FeliCa Dude @FeliCaDude]

New “F3” eSE domain on the Rakuten Hand 5G, with a new SEID pattern (seems to be neither eSE CPLC data or the eSIM eID). Still Mobile FeliCa 4.1.

[FeliCa Dude @FeliCaDude]

@Kanjo There’s a strong possibility that Mobile Safari is right.

[FeliCa Dude @FeliCaDude]

@Kanjo Second caveat about alternate name readings in passports is nonsense since they only appear in the VIZ. The application should only read the MRZ since that’s explicitly for OCRing. Reading the VIZ is also a bad idea as there is no standard layout or font.

[FeliCa Dude @FeliCaDude]

@skydoki That is probably correct.

You can see if FeliCa is enabled on your device by attempting to read it with NXP’s TagInfo in NFC-F mode.

If it responds, you should get an IDm value starting with 05.

Without the Osaifu Keitai application available, you cannot use it for anything.

[FeliCa Dude @FeliCaDude]

@Kanjo Dual mode has been available for a few months now. In-app, I don’t know about, and Suica recharges are exempt from the 2% cashback.

Boo to JR East as well for scrapping 1.5% cashback except on auto-charge: adhoc recharge with View now only attracts 0.5%.

Cashback is everything.

[FeliCa Dude @FeliCaDude]

@Kanjo She may be able to collect the bonus, but she didn’t earn it. Shades of 2019: https://t.co/zfgr5DYPUR

[FeliCa Dude @FeliCaDude]

@Kanjo Both nanaco and WAON have a points balance on the card itself, so Wallet is natively aware of it.
There's also a server-side 'pending' balance (from promotions etc) which can be downloaded to the card, at least in the feature phone/Android versions.
https://t.co/KQ54zEEv3W

[FeliCa Dude @FeliCaDude]

@Kanjo It's not JCB but Seven Card. They issue a combination nanaco+QUICPay card.

If the Apple Pay nanaco ingestion were not to take care of QP while telling users to discard the combo card, it could be used by a third party to make (postpaid) QP payments.

https://t.co/gUkzlIWm5O

[FeliCa Dude @FeliCaDude]

@Kanjo @TokyoJim That mark is a physical compatibility mark to indicate the antenna location and is a trademark of FeliCa Networks.

There are some devices that do not have it. The RC-S300 and RC-S380 display the NFC Forum N-Mark instead (older readers like the RC-S320 showed the FN mark).

[FeliCa Dude @FeliCaDude]

@AceJayDX Interestingly, QUICPay is also disabled by this migration (https://t.co/nPwgC1mxJC).

Whether this is done by writing to the QUICPay service blocks or by hotlisting the card (as if stolen) is unclear.

If QUICPay remained active, 'discard' would have to read 'securely destroy'.

[FeliCa Dude @FeliCaDude]

@elevtechlift @Kanjo FAST only applies to secure elements that need to host Mobile FeliCa. It doesn’t cover cards or FeliCa issuers outside Japan.

Nobody will choose FeliCa for a new transit card outside Japan. Singapore ditched it, HK is likely to follow.

Why? Politics, money, and Sony’s monopoly.

[FeliCa Dude @FeliCaDude]

@Kanjo In the end it just turned out to be another Mobile FeliCa 4.1 implementation on NXP hardware with the FN applet loading domain (F00001..) just like any other carrier device.

Not sure what the talk about a ‘bigger chip’ was about, unless the global model NFC vendor isn’t NXP.

[FeliCa Dude @FeliCaDude]

@Kanjo IC type code >0x18 may indicate a new version, but the Sony list only shows up to 4.1. FeliCa SD2 on mobile maybe eventually? I predict reuse of the G&D/ST eSE/eSIM but Thales also has FAST certified products now.

https://t.co/q1PU3WM9be

https://t.co/KdS1Mb6uQ2

[FeliCa Dude @FeliCaDude]

@Kanjo @timesfai Requirements: OpenMobile API for the Octopus app-SIM communication, C6 pin connected for SWP, and routing of FeliCa over SWP. Pixel 4+ seem to route FeliCa to the eSE on all models. MiLite115G (Japan) lets you choose eSE/SIM SE, confirmed works. To test, scan NFC-F with TagInfo.

[FeliCa Dude @FeliCaDude]

@cons_cell @Kanjo If you want to go that route you can get a straight 2% (used to be 3) from SMBC Card on the LINE Pay card until the next devaluation. But the point is that JR shouldn’t be treating its own cardholders this badly. House transactions cost them nothing, after all.