Quantcast
Jump to content

[pivotCE] Official Release of LuneOS and Project Updates


Recommended Posts

blue-white-sphere-text_1It’s been a long while since we

link hidden, please login to view
back in June of 2013, but today after months of very hard work the webOS Ports team are very proud and happy to provide our latest release to the community now named “LuneOS”.

The first eye catching change is the new name we’ll be using for our project going forward. The distribution will be called “LuneOS” instead of “WebOS Ports Open webOS” because it wasn’t very catchy and we felt it important to specify we are separate from Open webOS which is it’s own project from HP and now LG. Lune is the French translation of moon and refers to the user interface we all love so much in legacy webOS, LunaSysMgr, which is named after the Latin/Spanish translation of moon.

The release model for LuneOS is a rolling one where each of the releases will get its own name from a list of coffee beverages. This first release is “Affogato”.

All work for each release is and users can also update to unreleased stages to support the developers with testing and bug fixing. Our overall aim is to deliver high quality software which is stable and satisfies the needs of our users. We plan to have a new release at the beginning of each month.

General focus

As a mobile operating system, we’re tailored for smartphones and tablets. Our main focus is not to add new devices as they appear on the market but instead to provide a stable, easy to use and easy to port software base. Porting OS pieces itself was never the real problem of our approach since we solved the most important bits by using . The actual problem we’re facing is to get applications software implemented and to add all the back-end functionalities to the system we love and need.

The main focus of LuneOS is to provide an operating system which is driven by the community and continues what we love(d) about webOS. We’re not trying to reach feature comparison with Android or iOS but rather building a system to satisfy basic needs in the mobile environment. Building a good quality mobile operating system from scratch is a hard job and is built in just the spare free time everyone involved in the project has. To get the best ratio between what we want and what we can do, we’re analyzing architectural decisions from both existing solutions we can base our work on and whether we have to write things from scratch.

Supported devices

We’re currently supporting the Nexus 4 and HP TouchPad. The Galaxy Nexus and Nexus 7 (2012 Wifi) are still supported with this Affogato release, but will not be actively maintained anymore by the project team for future releases. We would like someone to step up as maintainer for these devices. We also have started to write a to make it easier for community members to port LuneOS to other devices.

What works

Wifi!  We also have a working settings app which includes things like wifi, screen, developer mode, and about. Apps that work include a basic browser, Preware, mail (enyo1 but it’s working albeit a tad buggy because of screen size related things), accounts (with some minor issues), memos is fully working, a stubbed contacts app, initial calendar app with no real backend functionality yet, synergy connectors for a lot of endpoints (Google, Yahoo, i*, owncloud, and more) and initial work for a phone app.  Also, contacts sync is working along with better suspend/resume handling, and a bunch of other smaller things.

System/architecture improvements

After the Alpha 2 release we made the drastic decision to rewrite LunaSysMgr from scratch and name it Luna Next. This decision was made because LunaSysMgr distributed with Open webOS caused too many headaches, mainly due to the legacy device support and the overhead of code that was in there to support various things. Keeping LunaSysMgr would not allow proper hardware acceleration without a lot of work and would have made porting to other devices harder in the future.

Therefore, the team decided to start rebuilding the user interface from scratch using the latest technologies available (QT 5.2 / QML, WebKit 2, etc). This of course meant a lot of work, but also a lot of benefits because it provides design flexibility going forward. Where possible, existing code from LunaSysMgr was re-used.

As you can imagine, the rewriting has been a lot of work and there are many different scenarios to cover, so there might still be some bugs present. After this release we will focus on adding additional features to Luna Next.

Starting with this release, LuneOS has a built-in update mechanism which makes it easy for users to update to the latest build.  The implemented mechanism is similar to the one which was used in webOS before but has a different backend implementation. Right now there is no automatic notification when a new update is available. The user has to check on his own in the Settings app if a new update is available to install it.

Ecosystem

We’re still using Preware to provide application feeds which enables the community to distribute their applications. Currently we only support one feed which is built from purely open source applications. Submitting a new application is as simple as creating a pull-request against the relevant repository which sets up the feed. On the application side we have a reworked Preware application which is now based on Enyo 2. It is faster compared to the original Preware based on the Mojo framework due to the fact it can simultaneously download multiple feeds. However, it’s back-end is still based on the same code as in the legacy webOS system.

Improvements since Alpha 2

Overall there are a lot improvements since the last release.  Below is a list which doesn’t aim to be complete but gives a good overview what the team worked on and is still working on:

Core OS system improvements

  • Built upon libhybris to enable easy portability on available Android based devices where the followings things are currently re-used from Android:
    • Telephony system (rild)
    • Graphics drivers
  • We’re planning to utilize more things from Android soon like:
    • Hardware accelerated video/audio playback
    • Sensor integration
    • Functioning camera
  • There is currently no plan to support running Android applications within LuneOS like ACL or AndroidChroot do.
  • Using systemd as system init manager instead of Upstart, giving shorter boot times and easier control of tasks during boot.
  • Emulator based on VirtualBox is available for testing and development
  • Completely built by the community (OpenEmbedded build system)

Application improvements

  • Preware 2 is now working and enables users to install additional applications.
  • Various bugs have been addressed in the , and apps.
  • A new has been created based on Mozilla’s PDF.js implementation.
  • A basic application is available.
  • are still present but a little buggy at times; this needs to be fixed or replaced by new versions of the apps.
  • A system update mechanism is available to easily update to a new build once available.

Current work in progress for future releases

  • Native QML based phone application for speed & reliability
  • Media Indexer Support with legacy webOS compatible API
  • Support for audio and video playback
  • Tweaks support
  • Further Status Bar indicator support and updates
  • Further improvements to the keyboard layouts
  • Adding user interface features to Luna Next which were also available in webOS 3.x and LunaCE such as “Card Stacking”, “Mini Cards”, “Card Zoom Gestures”, “Stack Spread Gestures”, “Infinite Card Cycling”, “Tap-to-Maximize Edge Cards” etc.

Help needed

As LuneOS is a large project with just a small group of people working on it, we could use help with various things. Especially on the application development front. We have a lot of parts on the service side in place but the app UIs need a lot of work from creative people. If you like webOS, know how to develop on the web and enjoy working with an enthusiastic team on a new community built mobile operating system, don’t hesitate to contact us through the available communication channels (see ). Besides doing real development we also need people spreading the word about LuneOS, working on the website or documentation for others about how to participate in the project.

Here is a rough and unsorted list of things we need help with:

  • Fix bugs in existing applications (Settings, …)
  • Create replacements for old Enyo 1 based applications:
    • Contacts (first draft exists)
    • Calendar (first draft exists)
    • Messaging (with Synergy integration)
  • Create documentation and workflow for app developers to develop and submit new applications
  • Improve the project website with a better look & feel
  • Testing and bug reporting

If you’d like to get involved, !

Get started with LuneOS

Ready to start using LuneOS?  Great!  Here’s what you need to know:  there is still a lot of work in progress and the current state should be considered as being alpha even though it’s working quite nicely for the parts that are implemented already. Therefore, use is at your own risk. Currently BlueTooth, the accelerometer, camera and ALS are not implemented yet. Audio & wifi should work, though might be buggy. If you have a TouchPad you can start . You will want to use the “Release” version. Nightly is used for things that are being worked on and bug fixes for the next release.  If you need help installing it, go .  If you’d like to try the emulator go . And for the Nexus 4 go . All the supported devices can be found

Found some bugs?

Once you’re happily testing, it can of course happen that you will run into some bugs. Feel free to report them at  so the developers can look into it. Of course you’re free to help in solving existing bugs as well!

Have questions about the project?

No problem!  Send us an email to [email protected] or tweet to us .  If you’re excited about the project, use the hashtag #LuneOSishere and spread the word!



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Topics

    • By pivotCE
      link hidden, please login to view hold a number of events. This year’s will be of interest to fans of webOS phones, tablets and other computing devices of the past. The festival is held at the and runs over three days from the 12th to 14th of April. The festival includes three elements:
      – some with modifications to function in the modern environment. and . . For readers of this blog, representation of webOS devices will be in two of those areas. Jon W of the is attending over the weekend and will give a 50 minute talk at 900am on Saturday the 13th. The consignment shop will have a small selection of webOS devices for those who are interested.
      So if you are in the area, why not go along?
      If you can’t make it, you can follow along via the and TouchPads are available remotely at
      Discussion is at the . You can read more .
      Picture Credit: .
      The post first appeared on . Related posts:

    • By pivotCE
      Sooo that was a really long time since a release, but
      link hidden, please login to view are still around and active as ever! We have continued making updates and producing testing images. But a lot happened that resulted in us not putting out a proper release out in the past few years.
      Those who have stayed in touch with the community will know there has been some turmoil with the closure of the webOS Nation forums last year. Things stabilised over the last year as people converged around the and made plans on the associated . Much of the old information from webOS Nation was preserved thanks to the and can still be accessed, if imperfectly. We have now set up a that largely replicates the old layout and is ready for fresh content.
      If you are eager to find out what we’ve been working on and to try out the new release, read on…
      The (Jenkins) builder infrastructure we had available previously decided to have a number of malfunctions, leading it to be no longer available to us. So for now we’re back to our own builders for building all the images, which isn’t great, but at least we’re still building and providing images! We are now using , which means newer base components like systemd, pulseaudio and wayland.
      Since the last release LuneOS has gone through a major rework under the hood. To summarize:
      We moved from Qt5 to (6.5.2 included in this release). We have moved away from our own compositor (luna-next) to the one provided by LG in called luna-surfacemanager. We are now using LG’s WAM (WebAppManager) instead of our own custom one together with LG’s fork of Chromium (94). A major rebase of all components shared with webOS OSE to be based on the now. This included a migration to Enhanced ACG which provides a lot tighter security for LS2 calls from apps and services. This all was an enormous amount of work behind the screens but little visible to the end user, however this does offer clear benefits going forward being:
      A shared code-base with LG, which means less custom components and maintenance. Years of field tested code on LG production devices which offers more stability. In this process we were able to keep backwards compatibility for apps and services. Easier to upgrade to latest OSE components, since we have migrated almost all remaining components that were still not based on the latest webOS OSE or on Open webOS. (125 components were migrated in total, 15 components are still to be migrated). In the meanwhile we have also been working hard to support the newly released devices such as the PinePhone, PinePhonePro and PineTab2 which are affordable devices which can run a very close to mainline kernel and a multitude of OS-es. We now support booting off on Pinephone.
      The new close to mainline kernel for the Pine64 devices allows them to run things like out of the box!
      All other supported Android devices are now based on 9.0.
      So what is ahead for the near future?
      Our focus will be on the mainline devices and emulator (), however we will try to keep support for the Android/Halium based targets as well.
      Upgrade to latest Chromium 108 released by LG recently Work on audio & multimedia infrastructure provided by webOS OSE to get it working in LuneOS Work on camera infrastructure Try to get a mainline kernel working for Tenderloin, Hammerhead, Mido and Tissot. Improve/add QML components and add new basic apps to be used such as Camera, Flashlight, Audio Player, Video Player Piggyback off some of the work done by the . Provide a GSI image for newer Android (9.0+) based devices, this would allow a standard image to boot on most modern Android devices v.s. building a device specific one for each device. Known issues:
      Battery usage is on the high side No audio in webapps (we decided not to spend time on this, seeing we plan to update Chromium soon anyway) The Usual:
      Sign up for. Get involved and [ UPDATE https://pivotce.com/2014/09/22/webos-ports-help-wanted/ ] Feel free to download the updated builds to get started. Currently supported targets: PinePhone, PinePhonePro, PineTab2, Qemux86-64 (Virtualbox), all with mainline kernel. Tenderloin, Hammerhead, Tissot, Mido, Rosy, Mako (Android 9.0/Halium based with their respective Android kernels (3.4 and newer)). RaspberryPi 3 and RaspberryPi4 might work too, however we haven’t tested this ourselves.
      . And remember we don’t do timelines.
      Don’t forget to contact us with any questions and feel free to join the discussion on the . Catch us on Twitter @webosports on IRC: Libera:#webos-ports, or email [email protected].
      We will see you shortly again with a new release!
      Picture credit: from Pixabay
      The post first appeared on . Related posts:

    • By pivotCE
      The webOS community may be a bit smaller these days but it’s no less devoted to the platform. WebOS Ports is a small team of developers. As you can imagine, it is a few people to maintain a full OS that consists of thousands of components. Things are starting to come together for LuneOS, with the current major rebase and stable release. But we still need your help.
      As nice as it is to have some additional folk contributing, developing, and working on issues, we still need more developers to get involved to make this community project really take off.
      “Our focus is core functionality”
      We cannot stress enough that we are building an OS focused on core app integration that is simple, beautiful, and user-centric. Right now, function comes first. If we had a penny for every developer that knew some web code and could make a beautiful static mock-up of an app that didn’t do a thing in the backend and then said “I did my part, it’s up to you to make it work”…well, we’d have a lot of pennies.
      Developer requirements
      Once core app integration happens we will need HTML/CSS smart people. But to be an asset to the team, you need to have a good grasp on any or all of these technologies:
      Javascript C node.js C++ QML Qt Yocto Graphics design Are you decent at some of these, but might need help from time to time? That’s fine!  We’re a community, remember?  Hit up the
      link hidden, please login to view and/or channel and ask! Get the bugs out!
      We have several applications already available but many are placeholders or have basic functionality. Some of the apps are almost fully functional like Settings. But even Settings has bugs and can use refinement.  OK there are bugs everywhere! (If only it were as easy as a can of Raid to fix them)!  We’ve received lots of questions about how to get plugged into the project quickly.  Easy! Head over to our  to see current issues. Find an area where you think you can help and then find us on or (see below) to talk about it.
      Some examples of areas that need bug fixing are:
      Email: Some minor bug fixes Settings: Add Settings when needed Phone: Further polishing Calendar: Google C+Dav integration needs updating to adopt for Google’s changes Browser: Rework UI to be more webOS/LuneOS like And more. Core Apps/Features/Backend magic
      The Open webOS project released several core applications that were Enyo1 based.  These apps are in LuneOS
      Messaging: Needs a rework or rewrite to give proper functionality similar to legacy webOS PDF needs converting to QML. LuneOS also needs a media player app (maybe reuse/rework the webOS OSE app for this?). The C+Dav connector is there, but it needs updating for various changes by Google. It also needs testing for other providers. Additional IM connectors would be good to implement (Telegram, Signal) etc, there are existing plugins exist for Pidgin/libpurple that can be used. Looks aren’t everything
      As you can see, to really make stuff work first, most of what we need is in the backend.  It’s the old battle between form and function. Which comes first?  Designers will argue form!  But Ports is focused on the core functionality that has to work first and look pretty later. It’s a hard pill to swallow and we get that, but when building an OS, it’s the most important thing. If it looks pretty but doesn’t work, the project loses potential users. If it works but doesn’t look pretty it will at least show promise and that encourages positive feedback. And with a community led project, if you don’t have good feedback you’ve already lost.
      Additional help wanted
      Ports is looking to expand our public relations presence. If you are located outside of the United States or more specifically speak a different language than English and would like to help us advertise and direct interested people toward LuneOS and WebOS Ports, please let us know.
      We are also looking for a WordPress “expert” for a new site we’ll be setting up soon. Are you good at making tutorials?
      We have several “How to install LuneOS guides” on the wiki. If you’d like to make friendly guides, that’d be great!
      And finally, we need a “wiki-meister”. Someone that really knows the ins and outs of running a mediawiki!
      Get involved
      Everyone can help in some way. We need testers and bug reports! Sign up on the , contact us to let us know that you signed up and what your username is, and we’ll upgrade your account so you can post issues.
      Developers please join us on and/or drop by the IRC channel
      How to Contact WebOS Ports
      Want to get involved? Have a question? Get in touch with us.
      [email protected]
      Twitter: 
      IRC (Libera):
      Telegram:
      Issue Tracker: 
       User Support Forums
      Join the forum .
      The post first appeared on . Related posts:

    • By pivotCE
      Have you been wondering what LG will do with webOS next?
      According to
      link hidden, please login to view, a since pulled website has arisen (here are the cached pages from Google  and ) detailing info about LG’s all new platform supposedly called ““. It is thought that this is going to rival Samsung’s Tizen, maybe even in retaliation to Apple’s new smart watch. Hopefully our loyal fan-base will make it popular! According to pictures pulled from the site (see below), the SDK for the said smart watches, will supposedly be released with the announcement of LG’s plans to move webOS to the Smart watch platform. To see the other banners pulled from the site click
      .


    • By Alex
      There's been a lot of frustration over the years since LG aquired webOS and moved it into all their TVs, specifically around software updates. After a year or so, updates are not always available, mostly due to model and hardware limitations. Now come teh 2024 webOS TVs and LG is promising to keep you updated for at least five years! That's quite a turnaround from years past..

      The news is part of the recent 2024 QNED Announcement:
      LG 2024 QNED TVs also elevate the home entertainment experience with versatile personalization and increased convenience. With the webOS Re:New program,* LG is offering an upgrade to the latest version of its webOS smart TV platform to give more smart TV owners the most up-to-date user experience for the next five years. This notable offer comes to LG QNED Mini LED 8K models launched in 2022 (QNED99 and QNED95 series) and will be extended to additional models in the QNED TV lineup worldwide in the future.
×
×
  • Create New...