Well. you touched on most of the things that had occurred to me...
TS / "Morse code" tap sequence (gesture?) / amount of contacts
(it's a two point screen) - These are all the ones I had when I saw zero buttonage
internal jumper / pin /switch - These are the ones that were still lingering from the "But how do magic my dx"
Hadn't considered the port - which was a nice thought.
although determining protocols is out of my price range doesn't prevent a snuffling about with 'standard' toolsets.
Quote:
|
IF the case can be opened
|
I never met glue yet that could smack down a razor blade in a one on one... Assuming they haven't filled the back with it... Which would be daft and not very conducive to good heat operation.
so I would guess pressure screw fittings al la compaq and a dab of glue at the worst.
Given the nature of actually having hundreds of thousands (or millions) of devices to "service" (this device is supposed to be an "active service" unit after all) honestly would be surprised to see a completely inaccessible unit. (but I'm wrong a lot)
I look at the DX here and would sorely love to have a play but it's usage is so high. maybe one day when it is a bit more unloved it could be consigned to the poke and play pile. Big screen E-ink rules!
So. Um, I should really come up with an entry of my own... For the "Pool"
Let. me. think...
It's unlikely to be simply "maintain contact in one location" - it would happen too often by accident.
It might be "maintain contact in two obscure locations" - this kind of thing has provenance and more to the point would be less likely to happen as often by accident but still isn't infallible so still I think a "No" (with some reservations)
Also highly doubt the Morse code thing, multitap and gestures (now I think about it.)
That would require a far more "definite" knowledge of EXACTLY when the burned in code was going to make a test... (unless it was designed to be paired with the serial interface and one could monitor the boot messages, still, a crap system).
Not only is it generally not-fit-for-purpose, it would also require far swankier code than a simple test for a button.
Some of this reasoning is why I don't believe the DX (and thus the pw) uses ports etc.. the DX was one of the earlier devices.
IF they had some incredibly obfuscated wake via lan method in that device? Why bin it in favour of much simpler tests?
Hmm... *goes away and has more of a think* Don't wan't to waste my guess
RECAP:
Still seems like to me: making Amazon engineers crack a glued case and hook up internal connectors to merely invoke a boot state? Total madness.
So to that end... TBC...