Hello Everyone
I have had my 7135 since May 2003 and I loved it. I was adding new
programs,I was online,using the MP3,hotsynced with no problem etc.I
had absolutely no problems untill last month. On 11/13 my phone DIED.
I had NOTHING,the screen was blank. I couldn't turn it on. When I put
it in the cradle to charge it wouldn't charge. I could do nothing
with the phone. The next day I went on the Kyocera web site and found
the help area. I followed the instructions which were to unplug the
charger from the outlet, connect the charger to the phone and then
plug it in...well that worked but I lost ALL of my information. I
ended up with the basic palm as if I just took it out of the box.
Everything I downloaded was gone..phone numbers, personal info
everything!!!!!!!!So I figured all I need to do is a hotsync.....Well
I figured wrong because now I can't hotsync. When I try to hotsync I
get a error message on my palm stating that the hotsync failed
because my palm could not connect with my computer. I used to hear
beeps when the connection was made and that dosn't happen anymore.
Also when I click on the Palm7135 desktop icon I get a error message
that says Exerpert Module cannot be found---what is that???
I was also getting the Com Port error message that the com port was busy.
I found the backup folder and moved it from the palm folder. I removed the
program and installed it again but I continue to have the same
problem.
I have changed com ports, uninstalled-reinstalled,changed speeds etc.
Can anybody help me??????
Thanks

Try putting your phone in the cradle and use the on-screen hotsync instead of the button. My 7135 will not sync when I hit the button for some odd reason, but it syncs fine when i do it manually.
Good Luck
-Gotwalp

I've noticed this happen from time to time as well, but once I HotSync through the phone, the button usually starts working again. I have also found that taking the phone out of the charger, doing a soft reset, and then placing it back again will make the button work.

I'm not sure what the exact cause of this is, but it didn't start happening until after I made a copy of the ROM using the app that comes with the Palm Emulator. Anyone know if it's related?