View Single Post
Old 09-25-2012, 05:41 AM   #23
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,991
Karma: 6314536
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by NiLuJe View Post
@ixtab: The S/N . For eInk devices, so far it's always been a 16 chars long hex string, beginning with B0XX, where XX is the device code . [Cf this & that].

And, obviously, we end up finding these in the header of an update package, official or not .
Which just happens to follow the same pattern as the ASIN for the device.

A bit of trivia I noticed going over the change notice to Amazon advertisement publishers that was sent out yesterday.
I was expecting the Kpw to be on the list of commission excluded devices for October, but it wasn't. (Anything Android still is.)
knc1 is offline   Reply With Quote