Palm has just updated its official developer blog with further information regarding the early access program for WebOS developers – here is what they had to say so far:


We’ve been thrilled and, frankly, awed by your response. As you may have seen on Twitter, @palm_inc recently tweeted that we’d received about a gazillion applications for early access, and that’s not far from the truth.

We let our first batch of developers in late last week, and another batch early this week. These folks are getting started, and we’re taking their feedback and learning from their experiences as we work to get the SDK ready for the rest of the world.

We expect to accept additional developers into the program each week. The SDK is still in active development, so we’re starting slowly — we need to make sure that our tools and support systems are ready before we scale. But we are eager to get the SDK into everyone’s hands, as we know that third-party applications will play a huge role in the success of webOS and Pre.

For those of you who have already applied, we thank you for your patience as we come up to speed. As noted in the program FAQ, we can’t provide status updates on individual applications, but we’ll do our best to give frequent public updates on this blog. If you haven’t applied yet, it’s not too late — you can submit your application here.

Thanks again!

The full post can be had here:
http://pdnblog.palm.com/?p=129

whatnow Palm Linux: TT3, TE2 and TC get suspend to RAMBootable implementations of Linux have been available for a variety of Palm handhelds for quite some time: the work of the hackndev boys is nothing short of amazing. Unfortunately, their efforts were cut short due to one basic eeker: you could not turn off a handheld running Linux.

Fortunately, this particular eeker has just been fixed for owners of Tungsten T3, E2 and Tungsten C handhelds:

PalmT|T3, T|C, T|E2: Suspend-to-mem without reflashing bootloader (UPDATED #2)
Submitted by Marex on 30 March, 2009 – 17:32.

It’s now possible to use suspend-to-mem without reflashing FlashROM on Palm Tungsten T3. How it’s done after the break. Also, PalmTC and PalmTE2 have similar loaders so it might not take too long to see suspend on them as well.

The wakeup loader source is here: http://marex.hackndev.com/palmtt3-wakeloader.S

As for the platform code, you’ll have to wait a while till I clean it up.
UPDATE: here is reference implementation for PalmTE2, it’s the same on T3: http://marex.hackndev.com/palmte2-reference-pm.patch

UPDATE2: PalmTE2 and PalmTC can wake up using this mechanism as well.

Master coder Marex has posted a very detailed writeup of the process at the URL below – if you have very good understanding of the ARM architecture (I don’t), hit the page and see what he has to say:
http://hackndev.com/node/280

Long press releases/statements usually mean that something is very fishy inside a company. Nevertheless, I have tried my best to dig through the full statement from Openmoko’s VP of Marketing, Steve Moshe – the key points are in bold:

During the last week Openmoko has had two great events. First the Embedded System Conference, ESC) and second, the OpenExpo in Bern. Those events could not have been more well timed for us because we had two major announcements to make: a thrust into the embedded systems market and the announcement of a new device, not a phone but an entirely new open device.
The launch into the embedded systems market is a case of the market finding the manufacturer. We designed the FreeRunner as an open phone. After it launched we started to receive requests from customers we never dreamed existed: Innovators who wanted to change the case or add in additional hardware. People who wanted to resell the phone with their software added. The collective creativity outside the company, dwarfed the creativity within the company. Our customers truly are an army of Davids. To seize this opportunity we decided to open up our CAD files, and open up our schematics. That way these new-found markets can develop for themselves products that we don’t have the resources to develop. So, over the next few months you’ll see us make a more focused effort in this market space. As a platform for embedded development, nothing compares to the FreeRunner: Open schematics; Open CAD; Open hardware; Open software.
At OpenExpo we had a keynote speech in the business track. This gave us the opportunity to explain some of the change in focus we’ve made in the past month. Our CEO Sean Moss-Pultz delivered the presentation and I’ll take some space here to explain in a bit more detail the background behind these exciting changes. Sean discussed three things:
1. Our successes.
2. Our mistakes.
3. Our challenges
It’s vitally important when addressing the challenges of the future to assess and understand your past success. Openmoko launched its first developer phone in July of 07 and the FreeRunner shipped in July of 08. Sales tripled. Not only did we build a phone; we built a company and distribution network in the process. We also helped others build their own businesses around the FreeRunner. Our takeaway lessons were as follows: Open Products can be successful in the marketplace; being Open multiplies everyone’s business opportunities. For our mistakes we identified these: Open Product design is very hard as there is a tendency to make too many changes. Our culture is not authoritarian. We also tended to view hardware with a “software” mentality, as something that could be easily changed or patched.
Our challenge going forward is to seize the opportunity we see in the embedded space and push forward the cause of open hardware. And we had to make some choices about how to spend the balance of 2009. There were essentially three projects going on inside OpenMoko: ongoing support of FreeRunner; Development of a follow on phone, the GTA03; and development of project “B”. From a resources standpoint we could pick any two. Given the traction we see in the embedded space and given our passionate commitment to current FreeRunner owners and developers it was easy to pick that project. Nine months after launching FreeRunner with tremendous support from the community the product is coming into its own with a diverse set of distributions that run on it, from android to debian. Then comes the choice between project “B” and the GTA03.
There were two paths:
A: Fulfill our promises on FreeRunner and launch GTA03
B: Fulfill our promises on FreeRunner and launch project B.
We will talk more about project B in the coming months, but these salient facts guided our decisions:
1. GTA03 was in constant flux as a design.
2. GTA03 schedule was consequently always slipping.
3. The resources required for GTA03 are 3X those required for Project B.
4. OM doesn’t have 3X resources

So, we picked plan B. Focus on supporting the FreeRunner and launching the more modest project, project B. That decision entailed putting GTA03 on hold and rethinking how we do that product and that business in a better way: learning from our mistakes and building on our success. It also meant restructuring engineering and sales and marketing.
Now comes the question, what about GTA03? how do we get there? And when? and what is it?
First, we attend to the issues that still remain with the FreeRunner. Second we complete project B. When we’ve done that, then we get to eat dessert. Essentially, we agreed with the case made by users on our community list. They asked us: ”How do expect us to buy a GTA03 when the FreeRunner is not yet consumer ready?” We also listened to our distribution partners. They wanted to know how they could continue to sell the FreeRunner when the GTA03 was “just around the corner.” And finally, we listened to our engineers. Since all of our sales are to people who understand engineering, their opinion about market viability is very important to us.
All of those arguments said the GTA03 as defined made no sense. As it was defined, it is dead. So how do we get to a new GTA03? Two requirements: continue to improve the FreeRunner; deliver on project B. What is GTA03 and when do we get there? There are a number of independent volunteer efforts out working at defining the GTA03 and working at refining or revolutionizing the business model to make it possible. Going forward we are going to open those efforts entirely. Our community has consistently asked for a voice in the up-front design decisions, so we will build a mechanism to try to make that happen. Again, whenever we see a challenge or an opportunity our first reaction is to rely on our strength. The community. They have never let us down.
Specifically what can the community do to help with this challenge and seize the opportunities we are presented with?
1. Move FreeRunner code upstream.
2. Stay involved or get involved.
3. Continue work on applications and distributions
4. Buy a FreeRunner.
5. Get involved in GTA03 discussions. The mailing list will appear on Openmoko.org in the forthcoming days.

P.S. Just in case anyone of you currently works on a press release or statement: 300 words is ideal…

07042009027 Funky translation error   leave the goddamn fruit at homeAah, the joys of internationalization – if translators only were cheaper and languages were easier to learn. The temptation to take shortcuts is very real…but can lead to funky mishaps like the one pictured on the left side.

The German text is gravely insulting – in this context, the word gefaelligst does not mean kindly but rather god-darn, you a$$hole. Thus, the translated text would be as follows:

Dear Guests,
we kindly request our guests to eat them fruit only god-darn in our restaurant to eat.

While you and I are likely to see the translation error and laugh about it (or, in my case, blog it); more sensitive people will feel gravely insulted. I am aware of at least one person in this hotel who was heavily insulted by the sign and terminated his stay early.

Cutting a long story short: don’t save money on translations…

My recent post (inspired by a rant from the PalmInfoCenter) has resonated pretty badly with the many Palm employees reading TamsPalm: in case I haven’t stated that recently, thank you all for being here. I love you!

Donald C Kirker posted the following comment to the TamsPalm blog – he is definitely not the only one whko sent something like this in, but has IMHO summed it up the nicest. I have taken the freedom to break up the comment and insert my thoughts:

Or maybe the journalists could quit feeling like everybody owes them every bit of information?

We (at least the members of the Vienna Journalists Club) don’t think anyone OWES us information. However, we need information in order to do our job…see below.

When you are harassed with questions over and over again that would violate your NDA (especially when the same person is asking the questions), it gets rather old and annoying.

I’m not about to loose my job because some “journalist” wants to leak a release date, or some little tidbit.

I fully understand this. Everybody needs and should think about himself first.

People complained that a Palm rep in a video was rather rude for stating that she could not let a journalist hold the Pre. There is nothing wrong, or unprofessional, with saying, “I am sorry, I cannot let you do that.” Speaking for myself: I have an NDA to uphold, and I am NOT about to falter on that.

As dashford said, the iPhone was *UNDER GLASS* after it was announced. For 6 months.

Remember, when you ask “What is the release date?” after being told that information is not available, you are essentially saying, “Please put your job, your primary source of income, at risk so that you may provide me with a little tidbit of information that might make me or my site look better.”

This is the core difference. We do this for a living, too! For a tech journalist, getting in the latest scoop can make or break a career. Many of us work hours and hours on end for sometimes little pay…providing a service to the community.

If some of us snap because of pressure, I can only ask for understanding and apologize for the entire profession. We need to get our jobs done just like you folks…


My opinions are those of my own, and are in no way to be taken as the opinions of my employer, Palm, Inc., or those of my business, OpenMobl Systems, or those of anybody affiliated with either entity (either as another employee, or business parter).

I personally think that we all need one another: tech journalists need tech companies and vice versa. If we all start to understand one another a little better, life would be easier for all of us…doesn’t that sound like a deal?

OpenMoko’s FreeRunner series can be considered one of the longest-living Linux smartphone series on the market: this extremely open device has been for sale for quite a long time, with a very active community suggesting both hardware and software improvements (which even went as far as to port Android).

Unfortunately, the device can now see the white light coming closer: the Swiss BernerZeitung outlet reports that the CEO of the company behind the device has laid off about 50% of the work force and has furthermore given up on the FreeRunner.

Instead, his company will focus on a non-smartphone device he referred to as “Plan B”: while open-source based, it will probably not be open hardware and will be targeted to the mass market from revision 1.

Linux heads wanting to further work on the FreeRunner are requested to buy the box and contribute software updates, as they might return to the smartphone game one day…as if anybody still cares then (:)).

The boys in Orange have had huge problems with staff attitude in the past…and it looks like the buzz around the Pre didn’t help them too much. The screenshots below show messages from three popular online journalists:
0 Palm: attitude problems resurface
1 Palm: attitude problems resurface
2 Palm: attitude problems resurface

(post ends here…nothing to add)

TealPoint Software has been roaming the Palm OS business since the days of the Palm III – their latest product TealOS unfortunately was disliked by Palm’s top brass and quickly disappeared into oblivion.

Nevertheless, the boys did not give up – they used the experience gathered on TealOS to create TealWheel…and have provided TamsPalm with the first set of screenshots…which are below:

Essentially, we are looking at a graphical implementation of the hub-and-spoke pattern. Menus like this one have been seen in both Picsel Viewer and the TapWave Zodiac’s launcher, and can be very effective if done right:
wheel1 TealWheel: TealPoint strikes back

The webOS heritage can be seen in the “cards” – a screenshot of the last state of the program is shown when a card is tapped or otherwise selected:
wheel2 TealWheel: TealPoint strikes back

Finally, here are two shots showing the transition effect shown when the wheel is activated:
wheel4 TealWheel: TealPoint strikes back wheel3 TealWheel: TealPoint strikes back

TealPoint spokesperson Tex Tennison furthermore asked me to state the following:

It’s still in an early state and the look is by no means locked down, but we’re getting lots of positive feedback, with several beta testers liking it better even than TealOS!

I have to say that I personally like the idea very much, and am sure that it will turn out to be a lovely app – stay tuned!

0a StyleTap CEO: webOS Classic != StyleTapI have just received word from StyleTap’s CEO – Gregory Sokoloff is a long-term friend of mine and is known for his very short emails (which I have reposted below in its entity):

!=

Cheers,

Greg

On Thu, Tam Hanna wrote:

Hi Greg,
Wanted to ask if you were involved in el Pre emulator!

Tam

Looks like the folks at Palm’s didn’t appreciate StyleTap too much after all :) .

Longterm followers of TamsPalm will probably still recall Fossil’s infamous WristPDA – this PalmOS-powered device failed miserably, but paved the road for other devices which succeeded it. In China, such devices have been for sale for quite some time…and the Canadian firm Neutrano seems to be hell-bent on importing them to the USA and Europe and getting them certified.

They are currently evaluating various models in price ranges from 300 to 400$ – hit this link to see a little gallery of what they are working on!

My trusty Jaybird JB200 bluetooth headset did not survive a recent surprise encounter with a washing machine…while I was perfectly happy with the headset, I decided to give wired headphones another shot. As Apple’s headphones were reasonably cheap and included a microphone, I wanted to give them a shot.

Plugging them in required an unnatural amount of force, and getting them back out of my device turned out to be impossible due to the soft and rubbery finish of both plug and cable. But they were detected as headset at the least.

Unfortunately, this recognition did not mean much. Audio was tinny all the time except when I kept the center button of the remote firmly pressed…the moment I let go of the button, tracks once again sounded like they were being played back through a thick wall of fog.

From my point of view, the 30 Euros invested turned out to be a major waste – 5 Euro headsets will likely deliver better audio quality than these when paired up with an X1 or similar non-Apple handset. Apple: this pair of headphones goes straight back to the shop where I bought them. In case anyone of you is in a similar situation: stay far away from Apple’s Earphones with Remote and Mic.

PhoneScoop has just released the video below, which shows…a Palm Pre running Palm OS applications:

The three-minute video shows the Palm launcher running on the Pre – it has to be controlled via a separate set of keys (the Pre’s 5way rocker seems to be inoperable). Downloading files off the internet seems to work fine (hey, folks – think about tIRC), while the PIM system does not seem to be integrated with the Pre’s native one.

Weirdly, the emulator goes by the name “Classic” and is said to be made by MotionApps rather than the StyleTap boys – an email has already been sent to Gregory Sokoloff seeking further information!

P.S. The product’s web site has just gone live – fint it here:
http://www.motionapps.com/classic/

Apparently, the folks at Palm’s have now understood that a few token developers are not worth pissing off the entire developer community…and have thus begun to provide “regular” developers with access to the webOS.

Of course, this being Palm, getting in is not too easy a task:

We are happy to announce our new early access program for developers interested in creating applications for the Palm webOSTM. The early access program is an opportunity for developers to test-drive and provide feedback on the Palm MojoTM SDK prior to its public release.

Admission to the program is by application – we’ll admit a small group of developers to start and gradually increase the size of the program as the tools mature. We’d like to let everyone in, but we want to make sure that we can provide a solid development experience and attentive developer support before we scale up. We are eager to get the SDK into developers’ hands and will expand the program as quickly as we can.

The program will continue until the SDK is officially released to the public, at which point any developer will be free to download the SDK. No, we’re not announcing the date that will happen yet.

If you wish to to apply to the early access program, complete and submit this application form. If you want to learn more about the program, we have a page of common questions and answers you can read.

If you’re admitted into the program, you’ll be able to download the Mojo SDK, which includes the tools you need to develop and test apps for the webOS platform. You’ll also have access to the early access program portal, where you’ll find documentation, sample code, and community forums where you can share experiences, tips and tricks with fellow early access developers. Because this is early access, all program participants will be required to accept an SDK Agreement which will require you to maintain confidentiality until the end of the early access program.

We are very excited about the expansion of access to the SDK, and can’t wait to see what you are going to build.

Further information can be had here:
http://pdnblog.palm.com/?p=107

Dear Readers, dear Syndicators,
I have received quite a few concerned emails regarding our Aprils fools post about Nokia taking over a now-bancrupt Palm Inc. This post is devoid of any and all real and factual information and was intended as an Aprils fools joke.

Please allow me to explain: in Germany and Austria, tech news agencies traditionally run a humorous piece of news on the 1st of April. While we have mostly refrained from such gags, we felt that this time a story could be planted which would amuse Palm heads all over the world.

In case some of you have felt offended, please accept our most sincere apologies
Tam Hanna

© 2012 TamsPalm - the Palm OS / web OS Blog Suffusion theme by Sayontan Sinha