@Grench how does the nubs work as a mouse ?
The nubs...
The great: Right now the left mouse nub moves the pointer, and does so far more accurately than the Pandora ever could.
The OK: The right mouse nub manages left/right click. Nub left is left click, nub right is right click. Currently right nub up does not seem to be working as 'double click' (that is how Pandora works). I suspect that what we have now is a temporary solution to get it usable until the software can get sorted out.
The weird: My left nub lightly jingles when moving around. The right nub lightly clicks. It feels/sounds like there are springs inside that are stretching. It isn't bad, but is there. I'll take that for the greater accuracy.
*************************
Heat...
Last night I played Hostile Takeover (Warfare Inc) for about two hours straight. This is one of those single threaded games that will consume whatever CPU power is available to it. I.e. it pegs one core worth of CPU continuously. I can see this visually on Gkrellm. According to Gkrellm, after that play session, one of the Pyra's internal temp sensors was reading 51*C. The Pyra was warm to the touch. I pulled the battery - warm as well. I grabbed my laser thermometer and checked it. Battery was at 120*F (48*C). Pointing the laser inside the battery compartment at roughly where the CPU board sits yielded a reading of 125*F (51.6*C). During that play session my battery - as measured on the noted inaccurate OS battery meter - went from 92% to 57% and claims over 5 hours remaining.
An idea for less heat and lower battery use?
Does the .dbp system have any handles in it to -restrict- the CPU that a game like this can see/draw? I'm betting that the game itself would still be 'the same' with half a core as it does when it is consuming a whole core worth of processing. I'm wondering if we can have a setting in one of the .dbp files to control how much processing power that individual .dbp application is allowed to consume. There are a lot of games out there that simply let the 'AI' consume any and all CPU that the game can see whether it needs it or not. I don't want to throttle the whole system, just what any single .dbp application can see/use of the system. Thoughts?