I finally tracked down the problem with the phone I was given on the second day, after quite a while figuring out how to get the testing program downloaded, compiled, running, and not pre-empted by the phone, and basically no LJ posting :). After a couple of iterations it seemed a memory chip was (a) dead (b) unstuck or (c) not there or (d) was intended to return zero whenever read from.
The actual "OK, I know it's broken because this" took about 30 seconds, most of which was clicking on "safely remove hardware." I wonder if I'll maintain this ratio of work :)
Things about my job that could plausibly be described as good free perks if you were optimistic:
The actual "OK, I know it's broken because this" took about 30 seconds, most of which was clicking on "safely remove hardware." I wonder if I'll maintain this ratio of work :)
Things about my job that could plausibly be described as good free perks if you were optimistic:
- Free sandwiches, crisps, fruit, etc.
- Free mobile phones with doom on
- Free laptop without doom on
- Free oriental holidays
- Debugging a program on a mobile device requires a lot of fiddling with (a) disk swapping and adaptors or (b) soldering.
- Free oriental holidays with no notice