I've been having the 2-sec wait problem that some others have reported. I decided to go ahead and clear my FlashROM, perform a hard reset, and try installing the driver fresh.

I found that I still have the 2-sec problem! I even soft reset after installing the driver and before actually using it.

So for those out there that believe it's the fault of a system patch, don't bother testing a hard reset.

Wasn't there more than one version of the G700 keyboard? Could it be that there's a version that just won't work with this driver?

For reference, the model # on my G700 is F8Y1501

Maybe someone who has a fully functional driver wouldn't mind posting the model # of their G700?

Well, there are two separate keyboards for Palm models and CLIE models, but I don't know about model number wise. My number is the same as yours, Dark79.

Model #'s
 

I haven't seen any other model. I have two of them purchased at different times (same model as yours) and both have the 2 second problem with this driver. I was hoping for some sort of a manufacturing difference, but oh well...

2 second off solution!!!!!!
 

turn beam receive on!!!

Yes this corrects the problem!!!
 

have played with input now with beam receive on and it works like a charm....finally, a functional keyboard for my NX!!!!!!!!! Bada-Bing!!!!!!!!!

Beam receive on of off, I still get the same results.

Re: 2 second off solution!!!!!!
 

Thanks.

This tip works with my G700/NX60

I'm starting to think it's a problem with the NX, not the keyboard. My keyboard has the same model version as the one mentioned above.

My NX is one that was purchased only a few months ago, serial no. 4036601. Did you guys having problems purchase your NX early?

My NX is like my TG; when the driver is turned on, the backspace key fails to work (on the clie's keyboard, that is). No biggie, though.

I hope we can get this to work for everyone, it's one of the best things to happen for OS5.

Actually, I just tried to do the reverse of the above poster. Mine's working, so I tried to turn off beam recieve. The keyboard stopped working in a few secs. Turned it back on, and it started working again. Good job, redbeard!

I concur. I was able to replicate the problem by setting 'Beam Receive' to off. Enabling beam receive seems to be a small price to pay for the functionability of this driver. Nice work on troubleshooting!

Cheers, Rich

Beam receive fixed mine, too!
 

Thanks !!

Hi Sneez--

My NX70 S/N is is 4002782, and I'm not experiencing any problems. Beam receive = 'on' for me.

I just tried out the new driver and everything seems to work great; speed much faster, no problem with sleep after not typing for a bit, no problem with hot sync (Thanks for the soft reset reminder that was posted - the driver load doesn't prompt you to do that anymore so you'll have to remember to do it yourself). Also checked it with docs to go and don't seem to be running into any lock up issues.

I still have a slight problem with the space bar right side - but I think it's mechanical on mine and I'll just have to figure out how to make it more sensitive.

The only request I have now is that the option to switch the shift and up arrow keys be added back in - I really need that to make it truly touch typable. Any thoughts from the developers?

Great update so far, though.
ruby

Hmm, well, it's good to know people are getting it to work. When I tried installing after the hard reset, it didn't work and a hard reset automatically turns beam receive on by default.

I also thought to try turning it off when I installed. Then on before I tried using it. Still the same problem.

One a side note, is the icon for the driver supposed to just be a blank blue dot? That's all mine shows. Thanks for the help all. I'll continue to try to figure this thing out.

Driver Icon
 

Hi dark79

Now that you mention it, that's all mine is too.