Over the air software customization for Linux mobile

happygeek 0 484 Views

A specialist mobile software management company, , has today announced what it claims to be the first Linux based mobile phone complete with fully over the air customizable software. The breakthrough has been made possible by partnerships with companies such as Digital Airways, Opera, Synchronica, Trolltech and Zi, and has been used to showcase the deployment and updating of applications using the Red Bend vRapid Mobile technology concept.

The handset itself is not actually available to purchase though, but remains firmly in the realms of concept fantasy. Red bend refer to it as a MAST, short for Master key, which is meant to symbolize the milestone of open access updating during the life-cycle of the device. MAST is based on the Trolltech Qtopia application platform for Linux and is implemented on Trolltech's Qtopia Greenphone. The Synchronica Device Management Server provides the device management server connection from which software is provisioned in a secure and reliable manner using the Open Mobile Alliance (OMA) Device Management protocol. If you want to get hands-on with the MAST phone then you'll have to wait a couple of weeks until the Mobile World Congress in Barcelona where Red Bend will be demonstrating it live between February 11 and 14.

It could be worth the wait, especially if features such as being able to update the Opera mobile web browser without needing to update the entire firmware image, and enabling network operators to customize a generic handset and promoting services via the Digital Airways' Kaleido interface when a customer inserts an existing SIM into a new phone work as well as they promise to.

"Until now, the entire mobile value chain has struggled to find a solution to enable post-sale, over-the-air customization of mobile software, especially for feature phones where core applications and services are embedded in ROM," said Yoram Salinger, CEO of Red Bend Software. "vRapid Mobile solves this need today, and we have joined efforts with major players in the industry to show how new revenue streams can be realized through mobile software management."

Dani AI

Generated

highlighted an important shift: moving from whole-firmware flashes to modular, post‑sale customization on Linux-based handsets. That demo-style approach raises a predictable set of engineering questions and tradeoffs. The notes below pull together practical, tech-focused guidance and sane defaults for anyone designing or auditing an OTA customization system; they also respond to 's point about native ARM binaries by calling out ABI and runtime concerns.

  • Update granularity and packaging: prefer application-level packages (signed manifests, version, size, checksums, deps) rather than forcing full image rewrites. Use a compact package format that supports atomic install and sensible postinstall hooks.
  • Secure delivery and verification: deliver over TLS with resume support, and verify package signatures on the device before any write. Keep the updater confined to minimal privileges; never run unverified scripts as root.
  • Delta updates and bandwidth: implement binary deltas (bsdiff/xdelta) for large binaries to save bandwidth. Server-side generation of deltas + client-side patching is standard for constrained links.
  • Atomicity and rollback: design for failure. Use A/B partitions or an atomic overlay/symlink swap so a failed update can be rolled back on next boot. Maintain a small, immutable recovery image.
  • Operator customizations: namespace operator packages and keep operator overlays separate from system-owned files so swapping system images does not clobber operator assets when a SIM triggers provisioning.
  • Testing and observability: stage rollouts (canary -> wider), simulate power loss and low-storage conditions, and capture structured update logs for remote diagnostics.

Example (minimal pattern) — verify, unpack to a staging directory, then atomically switch the active symlink:

gpg --verify update.tar.gz.sig update.tar.gz
mkdir -p /opt/updates/new
tar -xzf update.tar.gz -C /opt/updates/new
ln -sfn /opt/updates/new /opt/apps-active
sync
systemctl restart app-service

Key cautions: keep ABIs stable or ship compatibility libs for native ARM apps; avoid relying on long-term network availability during critical updates; and always include a small recovery partition. Mentioned demos show feasibility, but resilience, signing, and rollback are what make OTA customization safe for real users and operators.

Member Avatar for patelmiteshb
patelmiteshb -3 Newbie Poster

Great Job Guys !! Thanks. i am also software Developer please visit my site at snip

Edited by happygeek because: spam link deleted
commented: spam -3
Member Avatar for madihaghafoor
madihaghafoor 0 Newbie Poster

Windows Mobile support typical application binaries as found on personal computers with code which executes in the native machine format of the processor (the ARM architecture is a dominant design used on many current models).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview