11/20/04
+
PM |
QUOTE |
PERMALINK |
REPORT
garylm
FN-K (toggles audible key clicks)
Holding down the battery test button for 30 seconds supposedly resets a tripped battery.
02/22/05
+
PM |
QUOTE |
PERMALINK |
REPORT
HDL
Hmm. I can't make Fn 2 do anything, except try to rename the last desktop item I used.
Fn M only kicked in after going into stand by and coming out again, but then behaved happily (I never had a problem with this before, but then I didn't put it in stand by by default at that point, either).
Testing out Fn J, I finally made the OQO have a heart attack by dropping it 6" and catching it, but had to reboot it to unfreeze it! Is there a way to know whether it the drop sensor is on or off?
And precisely what is the open/close sensor supposed to do?
edited: Feb 22 2005
+
PM |
QUOTE |
PERMALINK |
REPORT
Chekote
Fn 2 only works during bootup, just like pressing the BIOS entry key on a desktop.
You can tell whether a function is on or off by the beep it makes when you press its Fn-Key combination. If the combination makes a beep when you press it, you just turned it on. If it makes no sound then you just turned it off.
The open close sensor is just like the sensor on a normal laptop. You know the one where you can tell it to suspend the machine when you close the lid? But since the OQO has no lid as such it works a little different. The sensor triggers a "close" when you hide the keyboard by sliding the screen down. Obviously telling the OQO to go to sleep when you do that is a little silly. A while ago some people on these boards were asking if you could use such a sensor to trigger a portrait/landscape screen rotation. At the time we all thought the OQO had no sensor to detect screen open/close. But it does!
02/26/05
+
PM |
QUOTE |
PERMALINK |
REPORT
Chekote
Yeah I noticed the sound aswell. It just plays whenever the sensor is triggered.
Thats how I first found out the sensor was there. I accidentaly pressed FN-V once without realising it, and then I kept noticing my OQO was going to sleep every time I closed the screen. I was getting ready to request an RMA when I noticed that sound. So I just started pressing FN+whatever to see if I could get the sound to go away, lo an behold FN-V did it.
Its kind of weird that they make it beep whenever the sensor is tripped, but I am thankful for it because I probably would have sent it back otherwise.
06/15/05
+
PM |
QUOTE |
PERMALINK |
REPORT
garylm
I've been carrying around a couple of spare batteries in their padded envelopes for a couple of months. Last night I went to swap batteries, and one of the spares came up dead. Not just drained, but BIOS (FN-2 on powerup) said the battery wasn't even there.
I attached the power supply, but the battery's LED's did not indicate that it was charging.
I removed the battery from the OQO and held in the test button for 30 seconds. (Tech. support at OQO had once suggested this as a reset method.)
I re-installed the battery on the OQO and held in the test button again for 30 seconds with the power supply attached.
Still nothing.
I left the battery attached with the power supply plugged in and called tech. support.
While tech support was entering my information, I reached over and pressed the test button on the battery. The LEDs lit up full-scale! I then booted the OQO under battery power. No problem. And the power supply had only been attached for 5 minutes.
So I guess if your OQO is acting up, just call tech support, and the thing will magically heal itself.
The real solution seems to be mashing that test button for 30 seconds with the power attached and then waiting a few minutes.
edited: Jun 15 2005
+
PM |
QUOTE |
PERMALINK |
REPORT
fil
Other OQO quirks:
A "known" feature of the power supply is that it resets by tripping the AC adapter to reset itself and prevents the OQO from being powered or charging of the battery.
The trick is to pull the AC cord from the AC adapter (ACA), wait 30 seconds, and then the ACA will power up the OQO and charge the battery.
The other quirk I've noticed is that the battery doesn't charge after the ACA is connected to the OQO if the OQO is off. The ACA only starts charging the OQO when the OQO is turned on. I usually hold the power button down for 5 seconds to shut it down.
Is this normal?
06/15/05
+
PM |
QUOTE |
PERMALINK |
REPORT
garylm
fil,
I've tripped the AC adapter a few times by plugging it into the OQO at the last minute when the battery signals that it's low, and the fan is howling away under heavy CPU usage. It seems that the ACA can't handle that initial surge with the combination of a fully depleted battery and a maxed-out CPU. You're right, unplugging the AC side and letting it sit for awhile seems to do the trick. By the time the ACA resets, I've powered down the OQO, and the only load the ACA sees when I reconnect the AC side is the depleted battery. By the way, I've found that my spare ACA behaves the same way under this unusual scenario. I should probably power-down when the battery gets low.
Regarding the ability to charge with the OQO shut down, mine works fine. It charges fine when powered up too.
Now I try to minimize that initial surge when I first connect the ACA. With a fully depleted battery, I first shutdown the OQO and then connect the ACA with the OQO off, and then boot back up.
