Sabitlenmiş Tweet
Adam
9K posts
Adam
@thinkaliker
I do things on the internet // Co-host @ACESCases // Software Engineer // he/him // Team @SpaceBitsRUs // @[email protected]
San Diego, CA Katılım Kasım 2009
905 Takip Edilen149 Takipçiler
@PacSurfliners What's the status of NB Train 777 from SOL tomorrow? The Pacific Surfliner website shows different information than Amtrak's alert bulletin in-app.
English
Last year I travelled to Japan and had a great time! I managed to pick up some #Arknights merch...and it just so happened to be the LAWSONS x Arknights collab. They came with furniture codes, but unfortunately, they are for the JP server only.
#アークナイツ
English
The following tweets will be aimed at a very specific audience and will look really weird, but I couldn't really think of another way to give these codes out. So, with that out of the way, the next post will be in English, and the following will be Google Translated to Japanese.
English
@Kanjo As soon as I heard that I literally went oh great, so that means it was literally a business decision to not go through the certification process/pay licensing...which means it'll never happen. On the other hand, Apple did pay up, I guess. It's like IP certifications...I guess.
English
@thinkaliker It’s preloaded on all Pixels but kneecapped on non-JP models which means it’s certified…sorta…I guess🤷♂️
Ota-ku, Tokyo 🇯🇵 English
@Kanjo Well, according to my source at Google, apparently the reason that non-JP Pixels never got Suica support, is...licensing (as of 2020). Apparently certifying SE for all Android devices is a big decision. My read on that is that it means it'll likely never happen then.
English
@Kanjo @madebygoogle Fitbit was a particularly strange case, shame it wasn't better. Worked for Tokyo area trains, but a number of vending machines with the IC logo did not. Topping it up worked for about a week then started erroring out with an unhelpful message. Didn't work at all outside Tokyo.
English
@thinkaliker @madebygoogle Really bad, and Google has yet to update Pixel Watch as promised so that all models can add Suica.
Ota-ku, Tokyo 🇯🇵 English
The TL;DR of my Japan Android Suica adventure is that:
- US Fitbit worked OK in Tokyo until it stopped letting me add money
- Fitbit failed to work outside of Tokyo
- An old iPhone 8 worked perfectly in every other case
This is really embarrassing, @madebygoogle.
cc @Kanjo
English
@Kanjo Thought I'd send this your way. No particularly new info, but the documentation is good and the Github link (github.com/kormax/osaifu-…) is an interesting read.
Mishaal Rahman@MishaalRahman
Modders have figured out how to make Pixel phones purchased outside of Japan compatible with the country's mobile payment system, Osaifu-Keitai. By default, only Pixel phones bought in Japan are compatible with Osaifu-Keitai, but this is a software and not a hardware limitation. Shown below is a global Pixel 7 Pro (model ID GP4BC) purchased in Germany using Osaifu-Keitai in Japan. For a bit of context, Osaifu-Keitai is the "de facto standard mobile payment system in Japan" as noted on Wikipedia. It's used for everything from electronic money to ID cards, loyalty cards, transit cards, and more. Osaifu-Keitai uses Sony's FeliCa RFID smart card technology. FeliCa is the standard technology for Japanese smart cards, and it's also used in other APAC markets. To support FeliCa, phones either ship with a mobile FeliCa IC or a NFC chip that supports the NFC-F (JIS 6319-4) standard. (Graphic is from: felicanetworks.co.jp/en/mfelica_pf/…) The Pixel 7, for example, ships STMicroelectronics' ST54K IC, a single-chip NFC controller and secure element. Pixels (as well as many other Android phones) use host card emulation (HCE) to essentially emulate a FeliCa RFID smart card that talks directly to the NFC reader. This hardware is present on Pixel 7 phones globally, which means no matter where you buy the Pixel 7, it should be able to support Osaifu-Keitai. However, the Osaifu-Keitai app seems to implement multiple checks to see if FeliCa is supported on the device. One of those checks (on Pixel phones) ends up seeing if the device's SKU is found on an allowlist of Japanese-specific Pixel phone SKUs contained within the system "PixelNfc" app. If your device's SKU is on that list, then you're able to use Osaifu-Keitai on your phone. If it isn't, then you're out of luck unless you root your phone to bypass this restriction (either by spoofing the SKU, modifying the FeliCa configuration file, or patching the PixelNfc app). Or, you buy a new, Japan-specific version of your phone. As for why this limitation exists, I don't really know. Sony apparently has patents/earns licensing income from the use of FeliCa chips, so that could be one reason. This isn't an issue for iPhone, as any iPhone you buy can use Osaifu-Keitai, but it is an issue with many Android devices and is why Japan-specific SKUs for many phones exist. For more info on this mod/issue, check out this great GitHub page by user kormax (which is where the screenshots come from): github.com/kormax/osaifu-… And this AOSP document: Host Card Emulation of FeliCa: source.android.com/docs/core/conn… H/T @AndroPlus_org
English
Google. Please. Global FeliCa on Pixels. It's like one line of code. If you're not going to pay the licensing fee at least let US pay the fee.
Quppa@quppa
@Kanjo @thinkaliker In summary, Android users get the short end of the stick once again. Non-JP iPhone/Apple Watch: any recent model will work (except for Visa payments). Non-JP Android phones: won't work at all. Non-JP Fitbit devices: only AmEx payments (with the attendant fees) work.
English
@thinkaliker @Kanjo My American Express credit card has a 3% international transaction fee (compared to 0% for my Mastercard credit card and debit cards and Visa debit cards), so I hadn't bothered testing it. Still, it's good to know that it's an option.
English
@thinkaliker @quppa Thanks. Guess this means the only Google Pay option is AMEX as VISA and Mastercard payment networks are blocking non-JP cards for Mobile Suica recharge.
Suginami-ku, Tokyo 🇯🇵 English