Quantcast
Jump to content

[pivotCE] Two weeks with LuneOS: An app sideload test


Recommended Posts

Here we are two weeks into the LuneOS initial release and I find myself staring at the install on my HP TouchPad wanting it to do more.  Don’t get me wrong, I’m patient enough to wait for a functioning OS of core app integration.  And I’m not in a hurry for all of the “I wish it had <app name>” whining.

Although, since LuneOS supports Enyo apps, isn’t it possible that it could run current webOS apps built from the technology?  I set out to find out.  Read on for the results.

Finding some apps to test

I was able to backup all of my apps some time ago using the

link hidden, please login to view
from webOS Nations forums user, GMMan. So I just browsed through my collection looking for Enyo apps and here’s what I found:
1.
2.
3.
4.
5.
6. HP App Catalog 5.0.3500
7.
8.
9.
10.
11.
12. 13. 14.

Setup

Now that I had some apps to test I needed to get the .ipk files onto my TouchPad.  Uh, wait…plugging in the USB cable to my laptop netted me a media device called TouchPad but when I open it there’s nothing there.  Copying over files results in an error message.  Well poo.  Oh yeah!  LuneOS uses a certain amount of Android “magic” soooo in command line on my PC I tried:

adb push nameofmyapp.ipk /media/internal/downloads

Success! I then opened up Preware, hit the menu, clicked Install Package, browsed for and selected the file, and hit Install.

I’ll note here that installation always worked but some apps caused Luna-Next to restart. Despite the glitch the app always installed. Also, the Preware success dialog still sports a back button which isn’t necessary since the gesture area is there and the spinning “working” symbol never quits. Just minor issues for now.

For the results, I divided them into 3 categories: Fully Functional, Partially Functional, and Non-functional.

Non-functional

As I mentioned, every app installed fine but this category means the app won’t open.  Those apps were the HP App Catalog (duh no surprises there), Communities, and Facebook Tablet. Facebook disappointed me since it’s such a great example of what an enyo app can look like and do but no dice.   for a while anyway so even if it had opened it wouldn’t be very usable. Bummer.

Partially Functional

This category is a bit wider in interpretation but essentially if tapping on the app icon gained a card, that was enough for me to say it at least did something. This means that the app opens or you can tap, move, or manipulate the UI in some way. Those apps were Apollo, Maps, ACL Documentation, Just Draw, QuickChat for Facebook, Shortcut Launcher, Box for TouchPad, USA Today, FeedSpider, and Project Macaw.

  • Apollo only opened the card and never progressed beyond the splash logo.
  • Maps opened and immediately showed a “could not locate” notification below which is no surprise since the WiFi TouchPad I’m using to run these tests didn’t ship with GPS functionality. Everything seemed great until I swiped away the notification and the app suddenly scrunched into super widescreen view. Closing the app, reopening it, and leaving the notification there let the app display properly. Search and directions all worked fine.
  • ACL Documentation opened and displayed properly but many of the buttons did not work. Presumably it’s because of the webkit changes in LuneOS over webOS.
  • Just Draw opened but that’s about it. The page to draw in is a small box in the upper left corner which didn’t draw and the color selector won’t select color.
  • QuickChat for Facebook opened and showed the top line of what I remember from my webOS devices to be the web view of the “authorize app on Facebook” page. That view doesn’t populate but again most likely because of the webkit changes.
  • Shortcut Launcher opened fine and the buttons functioned and the fields took text input but browsing didn’t go well. No amount of backswipe worked and the app remembers your last directory! So reopening the file browser function only allowed you to go a level deeper and never back up. That’s a problem as you can imagine. So I could never try to add a shortcut.
  • Box for TouchPad opens but that’s it. The login screen is halfway on the screen and the input boxes do nothing. That’s another app that is anyway.
  • USA Today opened, pulled down new stories, scrolled properly and I thought I had a 100% functional winner! Oh! But videos didn’t play.  So close. I have always liked that app though. Pretty neat implementation with Enyo 1.
  • FeedSpider works amazingly well. I was able to get an early copy and I was impressed. The interface is clean and familiar from his previous work and I could log in and pull down new stories with ease. It’s on the partial list though because the back swipe didn’t take me back and some things just haven’t been coded yet. VERY promising indeed. Perhaps this will find its way into a release of LuneOS in the future. Yup, it’s that good and it’s not even done.
  • Macaw is an early build of the enyo version but everything seemed kosher there too. There were some visual glitches but something tells me that’s LuneOS since it surrounded the virtual keyboard use. Multi-account use was a bit wonky but overall the app functioned to view and post to Twitter rather well. It’s not done either but it’s pretty darn good as it is so I imagine the final release product will be amazing.

Fully Functional

That leaves Neato! Neato opened, logged in, and not only could successfully send text or URLs to my webOS devices and browser but if you sent a message to the TouchPad, Neato would display the page! Cool!

This is what I’ve done with LuneOS over the last 2 weeks. Do you have an Enyo app I didn’t try? Let me know your results in the comments below.

#webosforever



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 pivotCE
      It appears Future Publishing US have decided to “Sunset” the WebOS Nation forums. This term could mean anything from ceasing product support, through archiving to full closure. Whatever the term means in this case, the process is due to begin in early January.
      pivotCE was originally created some years ago to fill the gap in webOS news when
      link hidden, please login to view stopped publishing stories, but the forums continued until this day. Many of pivotCE’s stories were originally sourced from the forum. Both parts of webOS Nation contain a wealth of data and history about the webOS project and it’s successors. It’s hoped that this information can be preserved in some way. If you have a comment or can offer help, .
      You may want to consider joining the discord instance at the .
      The post first appeared on . Related posts:

×
×
  • Create New...