PalmOS on Raspberry Pi
pmig96.wordpress.com
pmig96.wordpress.com
For the second hand T3 I bought a Lithium Poly battery with slightly higher capacity and replaced the original one (there was a huge thread about the procedure on BrightHand at the time), and used that T3 most of the time for many years, until the battery gave out. So now the other one is the one I use - and the battery is still fine.
In the past I used the T3 for many things, with a wifi adapter it was my wireless email/network gadget, I used TomTom software for navigation, etc. But now it's just that TimeSheet application, and I'll probably continue using that for years to come.
During the day I may have to work on a number of projects, for shorter or longer periods. I have a list of those projects and work packages in TimeSheet. When the time comes to input all of that into the corporate time system TimeSheet presents me with the total sum of all work packages for each day (and other ways, if I need them).
It's extremely simple. I just can't find anything with the same easy functionality on Android or elsewhere. They seem to have a different focus, and way too many clicks to go through.
Reading Brighthand reviews was my introduction to tech lust. Terrible shame the only archived versions are text-only.
"Another negative feature with this specific model is the poor battery life. The m125 requires 2 AAA batteries (included), however they only last aprox. 2.5 weeks under normal use (compared to the 1-2 months of the m105 and most other PDA's)."
I don’t know his exact Twitter handle but you can find him under “foone”
I follow him too. He's a treat and always so interesting. Happy to give him a bit of extra publicity. His links always show up on HN.
But that's entirely different from replacing the battery itself with an expensive bench power supply. That can definitely work, especially if it's a high-end source/measure unit capable of being programmed to emulate the discharge curve of a real battery.
Every laptop I've ever owned will run with the battery disconnected.
Except the Macbook, of course.
The simple fact of the matter is that Apple routinely makes design decisions that are not only questionable, but compromise the usable life of the device in the process. And keep repeating the same mistakes over and over.
https://www.youtube.com/watch?v=AUaJ8pDlxi8
Having reduced or nonexistent performance after removing the battery was never normal. It's bad design. Period.
https://www.engadget.com/2008-11-22-macbook-and-macbookpro-s...
Sounds like an attempt to handwave away bad design principles.
Smaller devices like phones tend to be paired with downright tiny chargers, but modern smartphone SoCs can draw a lot of power in short bursts (cf. all the controversy about Apple trying to prevent brown-outs when operating the phone with a worn-out battery). Apple's laptops are usually paired with power bricks that roughly match the maximum sustained power draw of the laptop. Windows gaming laptops tend to ship with power bricks that are 2-3x larger than any Apple power brick.
It was a wonderful piece of technology though, especially in the pre smart phone days
I switched to PocketPC/Windows Mobile shortly after that, though. Dell Axim, IIRC. The screens were nicer. They had CF card slots for removable storage and peripheral devices. The WiFi wasn't as flaky and it even had a basic 3D graphics accelerator. I could program for it in C#, and it was very easy, no more difficult than programming on desktop. Actually, I experimented for a while with writing apps that ran on both desktop Windows and Windows Mobile and it was quite a fascinating experience.
That was a problem with PalmOS. If you wanted to develop for them, you either got stuck using J2ME (which was hot garbage), or you had to pay to get access to a C compiler. PocketPC and .NET Micro Framework were significantly much lower barrier to entry. Completely unlike trying to figure out Android development today. I think that's why I never really bothered to learn Android development. I've never really had an impetus to push me to chug through the learning curve, plus I already knew it didn't have to be that stupid. I've rathered stick to webdev and make whatever I need as mobile responsive PWAs.
I look at my smartphone today and it has never felt as good as that CLIÉ or Axim.
The earliest PalmOS systems had gcc, don't remember there being any commercial tools, this was before Java had been released.
However J2ME was not really an option. By the point Java existed, gcc prc-tools already did.
Programming on j2me was like 7x better after that...
Different times.
It is because it made sense. Not just a convention, the graffiti gestures are a convincing set of compressed (minimal full information, simplest one line per character) glyphs.
I had no business sense to figure out how to sell the thing. I also was a young 20 something year old...
"The application “thinks” it is running on a PalmOS device, but instead it is running natively on Linux."
It's sad how much source code is rotting in a vault somewhere, long past the point where it's useful to anyone but hobbyists.
Or is the ARM in the Pi just too radically different to be helpful?
Palm was influential on me as was Symbian on Psion for how things could be. I loved the pre-touch Blackberry devices.
For business communication these devices simpler easier and (from memory) more robust than what we use today. Entertaining? No. Dull? Yes. Efficient and productive? Hell yeah!
Palm OS came out 25 years ago.
One--how much I liked my TX. (One of the first little devises you could get on the internet with. I was a Goodguy's Liquidation sale. They had 500 Halo 2 Collector's editions for $5.00/piece. I needed the price on ebay. Everyone had a dumb phone. I went to a closed public library, and logged on with no password. I saw a high of 50 bucks. Went back and bought them all. I thought I had a upper hand in pricing stuff at auctions, etc. A year later, and it seemed like everyone had a smart phone.
two--dissapointment over how this company was mismanaged to the ground.
With Android 11, I've noticed that sometimes it "locks" up and I need to switch to the Samsung keyboard for a couple of characters and then switch back. (This could be a Samsung issue, as I never had a problem with my Sony phones.)
I have been using graffiti since I use Android, and I use it with fingers more frequently than with a stylus: no problem. You do not need the stylus.
(But I use a modified application with the option to set the graffiti area height - that may be an enabler on some systems.)
pardon the pun, but they had the mobile market in the palm of their hand. They could have exploded as a smartphone provider had they evolved. Instead they faded to nothing. So frustrating.
Yeah I can remember seeing this yesterday.
Damn thing only lasted for about two hours of eBay use so I couldn't even make it through a full morning of garage sales.
You've said that twice on this thread. I honestly don't remember; is there a story somewhere? Wasn't there another company (Treo) also building hardware with Palm OS?
Handspring (later bought by Palm) and Sony were the most notable third-party vendors, although there were many others: https://en.wikipedia.org/wiki/List_of_Palm_OS_devices