I've used the Treo 600 for about a week now. It's more-or-less OK (despite my previous complaints), but I still prefer the 7135. So I just moved my number from the Treo to the refurbished 7135. So far, so good.
If I get SRCP yet again, then I may finally give up on the 7135. If that happens, perhaps by the time it does, Palm will have fixed the memory issue with the Treo 650 and perhaps Verizon will carry it.
I have 23 more days to return the Treo 600, so I might as well hang on to it during that time just in case.
I noticed that Hotsync had been absent from the forum for 6 months, and then recently posted on another thread, "Are they pulling the 7135", an interesting comment.
Quote:
Originally posted by HoTSynC They are still around. There isn't anything yet on the horizon. Still weighing the options in the balancing act known as hybrid devices and what OS they should have....
I'll be staying the 7135, because for my needs there isn't anything that I see to replace it yet. But HotSync's comment points toward Kyo not having anything to replace the 7135 for a long time.
Originally posted by Breeze_S ... Kyo not having anything to replace the 7135 for a long time.
I personally don't care too much who the manufacturer is. I do, however, prefer Palm as the manufacturer because they know their OS the best. You can also download updates directly from them for the Treo rather than having to go to a Verizon store to get them to do it.
Kyocera should release an 8135 that is a PalmOS 5 device, has a bright screen like the Treo, but is still Grafitti and a clamshell.
__________________
- Paul
Last edited by pauljlucas : 12-19-2004 at 11:56 AM.
I had though about checking out the Treo 650, but with its goofy memory model decided against it.
I'm keeping my 7135 as long as possible. It suits my uses, and I need its analog signal capability for traveling in remote (i.e. no digital signal) areas.
Originally posted by SilvrDrgn I had though about checking out the Treo 650, but with its goofy memory model decided against it.
It's not goofy in concept, just execution. Palm made the block size too big (512 bytes). You have to wonder how they would not have anticipated problems. They're supposedly working on a fix. A block size of 128 or even 64 would be much better.
Login
Panel
