{"id":567191,"date":"2010-05-17T15:40:07","date_gmt":"2010-05-17T19:40:07","guid":{"rendered":"16393 at http:\/\/www.precentral.net"},"modified":"2010-05-17T15:40:07","modified_gmt":"2010-05-17T19:40:07","slug":"webos-firmware-carrier-approval-by-the-numbers","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/567191","title":{"rendered":"webOS firmware carrier approval by the numbers"},"content":{"rendered":"

\"\"<\/p>\n

We’ve had a good idea of how the update process works for webOS<\/a> for some time now, but the exact lag between when Palm submits a firmware update to a carrier and when that carrier finally green-lights the update for release to its subscribers has remained something of a mystery, until now.  Thanks to some clever sleuthing done by Rod Whitby (who founded and leads the webOS Internals Group), we’re finally able to gain some insight into carrier turn around times.<\/p>\n

Rod discovered that by comparing the build date of the webOS Doctor image (found in \/etc\/palm-build-info), which is presumably when the update is submitted to the carrier, to the date in the webOS Doctor URL (all of which can be found by way of the webOS Internals Wiki<\/a>), which is presumably when the carrier gave the OK for release, we can get an idea of how long it takes each carrier to approve firmware by device. <\/p>\n

To decipher the firmware codes in the left hand column:  the first 4 characters represent the model number, with p100 being the Pre and p120\/p200 being the Pixi.  The next three characters represent whether the device is North America bound (eww) or Europe bound (ueu).  The rest denotes carrier and firmware version. <\/p>\n

\"\"
<\/i><\/p>\n

It’s interesting to note that there isn’t a huge discrepancy between most of the carriers when it comes to the turnaround time on major OS releases. The big difference is in the service updates – 1.4.0 to 1.4.1.1 took a full 27 days on Verizon, compared to only 7 days for Sprint.  <\/p>\n

In all, Palm has done a great job so far in maintaining OS parity across all of the carriers with which it does business – it’ll be interesting to see how the newly introduced AT&T variable will affect this.<\/p>\n

\n<\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a>\n<\/div>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

We’ve had a good idea of how the update process works for webOS for some time now, but the exact lag between when Palm submits a firmware update to a carrier and when that carrier finally green-lights the update for release to its subscribers has remained something of a mystery, until now.  Thanks to some […]<\/p>\n","protected":false},"author":691,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-567191","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/567191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/users\/691"}],"replies":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/comments?post=567191"}],"version-history":[{"count":0,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/567191\/revisions"}],"wp:attachment":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/media?parent=567191"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/categories?post=567191"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/tags?post=567191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}