- Ordered from: Amazon UK
- Price paid: £10.52 (about $13.82)
- Advertised capacity: 32GB
- Logical capacity: 31,058,821,120 bytes
- Physical capacity: 31,058,821,120 bytes
- Fake/skimpy flash: Skimpy (2.94% skimp)
- Protected area: 83,886,080 bytes (inaccessible)
- Speed class markings: Class 10, U1*, V1
- CID data:
- Manufacturer ID:
0x27
** - OEM ID:
0x5048
(ASCII:PH
)** - Product name:
0x5344333247
(ASCII:SD32G
) - Product revision:
0x60
- Manufacturer ID:
* This manufacturer ID/OEM ID is pretty well known to belong to Phison.
** The U1 marking appears on the package, but does not appear on the card itself.
Discussion
This particular brand is one that I found thanks to an online survey I found, where someone was asking which microSD card had the highest endurance. One of Integral Memory’s cards was listed as one of the options. Neither Amazon nor AliExpress had them available for sale — but Amazon UK did, and for a price that was within my parameters.
Looking at the CID data reveals that this is likely produced for Integral by Phison. So far, Phison’s cards have performed decently well, so I’m expecting good things out of this card.
All performance metrics were above average, with random read speeds being more than one standard deviation above average. In fact, this card did well enough on random I/O performance that it would have qualified for the A1 marking. Alas, Integral chose not to put this label on the card. Sequential write speeds were only just slightly above average — in fact, as far as sequential write speeds go, this card is the worst performing Phison card that I’ve tested so far. However, these results are only based off the results from a single card — so we’ll have to wait until I’m able to test the other two to see how they do.
As far as endurance testing goes:
- Sample #1 was doing quite well for the first 4,331 read/write cycles; but during round 4,332, it experienced a…strange sort of data verification failure: the same 16 sectors’ worth of data was repeated over and over again — 526 times, to be exact. I’m not sure where the data came from either, as it failed CRC checks (meaning that it wasn’t the data my program wrote to the card). However, during round 4,333, it decided to stop responding to commands altogether.
- Sample #2 has completed 3,004 read/write cycles and has not yet experienced any errors.
- Sample #3 has completed 3,326 read/write cycles and has not yet experienced any errors.
January 26, 2025 (current number of read/write cycles is updated automatically every hour)