Quantcast
Jump to content

  • Join Today, It's Simple and FREE!

    Register now to gain access to our webOS user support forum. Once registered and logged in, you will be able to post a user to user support request topic to this site or reply to existing topics posted by other users. You can also take part in our other webOS user forums. You'll be able to customize your profile, receive reputation points, while also communicating with other members via your own private inbox, plus much more!

Sign in to follow this  
pivotCE

[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 donotdelete IPK patch from webOS Nations forums user, GMMan. So I just browsed through my collection looking for Enyo apps and here’s what I found:
1. Apollo 1.2.5
2. ACL Documentation 1.3.2
3. Neato 2.0.0
4. Shortcut Launcher 2.0.2
5. QuickChat for Facebook 1.0.11
6. HP App Catalog 5.0.3500
7. USA Today 1.2.0
8. Just Draw 1.2.0
9. Communities 1.0.8
10. Project Macaw (enyo) 2.2.12
11. Box for TouchPad 1.0.21
12. Facebook Tablet 2.0.35
13. Maps (Bing) 3.1.32
14. FeedSpider (enyo) 2.0.0

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.  Communities has been broken 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 broken 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



View the full article from pivotCE

Share this post


Link to post
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Forum Topics

    • [pivotCE]LuneOS November Stable Release: Doppio

      The very long wait is over #LuneOS and #webOS fans! We’re finally back with a new release called “Doppio” which we believe will be a milestone in terms of developments and the way forward! So you’re wondering what we’ve been up to for the past year? Well, actually a whole lot to be honest! We have upgraded the bluetooth stack from BlueZ4 to BlueZ5 which required quite some work to the kernels. This has been successfully completed for the Nexus 4 (Mako) and Nexus 5 (Hammerhead); unfortunately to date we haven’t been able to get this to work on the Touchpad (4G) (Tenderloin). We have been working closely together with the Halium project and have made further integrations between LuneOS and Halium reducing duplication between the projects and using a single source where possible. This all to be more easily integrated, and to facilitate ports to newer devices. We have upstreamed our kernel patches (mainly to fix GCC 5/6/7/8 compatibility) to Halium so we can use a shared kernel for our targets. Talking about new devices we’ve been working on: Since Google dropped the (budget) Nexus line and launched the (premium) Pixel line, we’ve been looking for other targets that are easily available, budget friendly and have good community support. We quickly ended up with Xiaomi which makes phones with decent specs, unlockable bootloader (the process is a bit tedious, but it’s do-able) and the phones give very good value for money. This has resulted in us independently working on 3 different Xiaomi devices being the RedMi Note 4x (Mido), RedMi 5 (Rosy) and Mi A1 (Tissot).  These are all Aarch64 devices using the Snapdragon 625 chipset. We didn’t have any Aarch64 devices before and also they are based upon Halium 7.1 (Android 7.1) while all our previous targets were based upon Halium 5.1 (Android 5.1), so this brought a whole bunch of new challenges. There are still a few rough edges, but audio, sensors, wifi and bluetooth are now working. There was also quite some porting work done for some of the other Halium supported targets such as the OnePlus X (onyx), Google/Huawei Nexus 6P (angler) and Motorola G4 (athene). These are currently in various stages of development, whereby OnePlus X is the most mature. The Xiaomi Mi A1 is a strategic device for us which we chose in cooperation with LG to work on to get LuneOS working and also as a target for LG’s webOS OSE (Open Source Edition). LG’s release of webOS OSE came as a surprise to us, however it has great potential. Though the initial release of webOS OSE was very limited and therefore limited use case for people not being very familiar with webOS, it does offer a lot of potential for us. webOS OSE is basically 5 years of development of the core webOS bits since Open webOS was released. It has been deployed in millions of LG TV’s since and offers great improvements in terms of reliability and functionality. The big downside however is that there’s no record of the changes between Open webOS and webOS OSE, so this is making the migration a bit more challenging. Early June the LuneOS team met with LG in Paris to discuss collaboration between our teams. As a result of this we have chosen the Xiaomi A1 as a device to port LuneOS to. This is now at a level similar to our other targets. After this release we will therefore focus on migrating our Open webOS components to the updated components provided by webOS OSE. This will bring quite some challenges and hurdles along the way, however we’re positive that we can complete this migration and it will bring a lot of improvements in terms of code quality, stability, functionality and reducing the need for maintaining a lot of these components ourselves since we can share a common codebase with LG’s webOS OSE going forward. LG has a very clear vision in mind for webOS. Since the initial release in March, a roadmap has been published and LG has pushed out 4 releases since the original release of webOS OSE. The following items on our to-do list will be where we focus next: Migration of Open webOS components to the newer webOS OSE components. Make the VirtualBox image work with a newer MESA. Migrate to Yocto Sumo/Thud release. Messaging improvements. Camera improvements. Fix known issues on the various targets. Bring back official support for Touchpad 4G (current build works on Touchpad 4G but only WiFi). Known issues: Node-SQLite3 is currently not working. Components using Node-SQLite3 have switched to an alternative storage method for now. Focus bug on input fields. You can work around this by hiding the virtual keyboard and pressing the input again. Random issue with virtual keyboard not showing on Aarch64 devices. Changelog Applications: Settings: Add QML variant, enable manual time and date in Setings. org.webosports.cdav: Add CLEANBROKEN User Interface: luna-{sysmgr,sysmgr-common,appmanager,next}, mediaindexer: fix build with Qt 5.11. luna-{webappmanager,qml-launcher} org.webosports.app.{browser,firstuse}: fix build with Qt 5.11. luna-next-cardshell: add runtime dependency on qtmultimedia-qmlplugins, luneos-components. luneos-components: drop build time dependency on qtwebengine, switch to Mer’s bluezqt System Level: luna-next: Add config for onyx, Add QT_OPENGL_NO_BGRA and remove QT_ENABLE_GLYPH_CACHE_WORKAROUND android-gadget-setup: fix functionfs test android-tools: fix compatibility with adb 5.1.1 android-tools-conf: Fix the machine check, Don’t patch script for tenderloin base-files: provide a common fstab for all LuneOS devices bluez: switch from bluez4 to bluez5 bluez5: Fix patch so it will work for RaspberryPi3, make firmware search case insensitive connman: Add connman-tools, connman-tests and connman-wait-online, Update to 1.35 distro: luneos: switch release name to Doppio environment.conf: Add QT_ENABLE_GLYPH_CACHE_WORKAROUND=1 fingerterm: Update to upstream and drop patch, use LiberationMono font funyahoo-plusplus: Bump SRCREV https-everywhere: Bump SRCREV hunspell-dictionaries: Update to latest version imaccountvalidator, imlibpurpleservice: Drop unsupported protocols initramfs-boot-android: add A/B partition support, boot into built-in recovery when no skip_initramfs, get Halium’s init script from GitHub, improve panic scenario in init.sh, use /userdata instead of /android/userdata, Various fixes to init.sh kf5bluezqt-mer: fix package content with empty QT_DIR_NAME libconnman-qt5: fix initial value of “connected” property libhybris, qtbase: don’t use += together with _append libhybris: Bump SRCREV, Set –enable-arch=arm64 for aarch64, Drop –with-default-hybris-ld-library-path and bump SRCREV libpbnjson: use Unix Makefils OECMAKE_GENERATOR lsb: fix luneos-version content luna-(web)appmanager: use /etc/luna-next/qtwebengine.conf luna-init, luna-sysmgr: Bump SRCREV and adjust file installs luna-init: Fix incorrect {, Install CustomerCareNumber.txt and cust-preferences.txt luna-prefs-data: Bump PV to be in sync with luna-prefs luna-sysmgr: Cleanup recipe luna-sysmgr-conf, nyx-modules: fix rosy values, Add initial files for athene and onyx target, Cleanup recipe and fixup defaultPreferences-platform.txt luna-universalsearchmgr: inherit webos_systemd luna-webappmanager: bump SRCREV luneos.inc, connman: Build & deploy VPN plugins luneos: inherit remove-libtool luneos: update SANITY_TESTED_DISTROS luneos-dev-image: tell Halium to mount rootfs rw luneos-emulator-appliance: update a bit luneos-features, connman: Add support for NFC using neard luneui-example-image: add few more packages, add more packages for testing, add vboxguestdrivers, v86d, add very small (fast to build) test image maliit-framework-qt5: set XDG_RUNTIME_DIR in conf file meta*: enable gbm meta-webos-ports: Add configuration files for Tissot, Update classes with info from webOS OSE mido, tissot: Fix path for CHARGER_AC_SYSFS_PATH mido: Initial configuration files mobile-broadband-provider-info: Bump SRCREV mojomail: bump SRCREV to fix build with boost-1.67.0, Switch back to webOS-ports/master branch nemo-qml-plugin-dbus: Update to latest version from upstream, fix package content with empty QT_DIR_NAME node-sqlite3: Bump version nyx-conf: do not let keys module watch over the touchpanel nyx-modules: Fix devices names in cmake files ofono: Update to latest version from upstream and enable Python 3 tests onyx: Enable power button packagegroup-luneos-development: include QML settings app packagegroup-luneos-extended: add android-kernel-bootimg, Add qtconnectivity, Add WIP targets and more documentation, Build bluez5 for all targets, include libpci for qemux86, move android-kernel-bootimg phonesim: Fix build with empty QT_DIR_NAME, refresh patches with devtool, update to latest revision from git pidgin-sipe: backport a patch to fix build with gcc8 pulseaudio-distro-conf: Add support for Xiaomi A1 (tissot), Add webos-system.pa for mido target pulseaudio-modules-droid: bump to 10.0.73, refresh patches with devtool, remove tenderloin CFLAGS purple-skypeweb: Bump SRCREV python-tz-native: Update to 2017.2, Fix typo in SRC_URI qt5: upgrade to 5.11, upgrade to 5.11.1 qt5-qpa-hwcomposer-plugin: fix package content with empty QT_DIR_NAME, hwcomposer_backend.h: Fix cast from ‘void*’ to ‘unsigned int’, remove tenderloin CFLAGS qtbase: Add patch to fix quirks with newer Adreno GPU’s, refresh patches, remove TLS patch on Halium 7.1 targets, temporary fix for SIGBUS crash on Android devices qtlocation: refresh patch qtscenegraph-adaptation: Bump SRCREV qtsensors-sensorfw-plugin: fix build with empty QT_DIR_NAME qtvideo-node: fix package content with empty QT_DIR_NAME qtwayland: add qwayland-server-surface-extension.h, wayland-surface-extension-server-protocol.h to sync.profile, bring QWaylandExtendedSurface back for luna-next, drop patch applied in 5.9.3, refresh patches for 5.11.2 qtwebengine: add libpci to RDEPENDS, Drop patch for libEGL and libGLES2, fix filename in SRC_URI, Fix patch for additionalFeatures, refresh patches, Remove PalmServiceBridge, replace EXTRA_QMAKEVARS_CONFIGURE with PACKAGECONFIG, squash a few of chromium patches for easier maintenance recipes: drop unnecessary FILES_${PN}-dbg variables, use oe.utils.conditional instead of deprecated base_conditional sensorfw: Bump SRCREV and drop patches now merged upstream voicecall: Update to latest version from upstream webos-systemd-services: Drop installation of luna universalsearchmgr.service android-headers: Add headers for Halium-7.1, common recipe for Halium-5.1 headers, make it possible to tweak android-config.h per machine, Use Halium Headers android-headers-halium: set preferred version android-headers-tenderloin: fix patches to match Halium’s android-kernel-bootimg: dedicated recipe for creating boot.img, minimal support for A/B partitions android-system: Add missing groups, also mount /persist when it exists, cleanup old hal-hybris overlay code, don’t manage ramdisk unpacking, fix lifecycle of lxc container, Remove installation of non-existing files, simplify usage of Halium, start sensorfwd after android container, use pre-start.sh from Halium, wait a bit for the sensors to be ready android-system-image: use system.img directly, Change wop into luneos, convert the sparse image if needed, create /userdata, Update halium bits to halium version numbers base-files: use system.img directly android-tools: remove, since now in meta-oe base-files,android-system: Android partitions are now mounted by Halium’s initrd base-files: add /system/lib64 in LD_LIBRARY_PATH hammerhead, mako: Add NFC as machine feature
      Include android-kernel-bootimg for each MACHINE that needs it initramfs-android-image: make it possible to add content libhybris: provide also virtual/mesa and set PREFERRED_PROVIDER for all android devices linux-lg-{mako,hammerhead},linux-hp-tenderloin: backport 2 changes to fix build with gcc8 mako, hammerhead: Use upstream kernels which now have our patches included mako: Fix the kernel build meta-*: set PREFERRED_PROVIDER for libgl and libgbm for all android devices meta-{asus,hp,huawei,lg,motorola,oneplus,xiaomi}: remove fstab overload meta-android: initramfs-android-recovery: add inc, remove leftover from android-tools removal meta-hp: migrate tenderloin to use Halium’s init meta-oneplus: Fixes for onyx target to make build work meta-smartphone: Add meta-huawei layer with Angler target, udev-extraconf: Uniform naming scheme for device udev rules and update udev rules meta-xiaomi: add initial support for rosy (Redmi 5), Get image for Tissot building, Initial work for Xiaomi A1 (tissot), mido fix persist partition number in fstab, mido use correct wlan module name, tissot: add initramfs-android-recovery, tissot: enable permissive SELinux, tissot: ignore other parameters from bootloader, tissot: switch to cm-14.1 kernel to fix wifi Migrate LuneOS targeted machines to using android-kernel-image systemd-machine-units: fix bluetooth for hammerhead, fix bluetooth for mako The usual 1. Sign up for the bug tracker 2. Get involved and 3. Join the mailing list Download and Install Feel free to download the updated builds to get started. Tenderloin, Mako, Hammerhead and Tissot remain our focus for now, but the emulator, Mido & Rosy work too. Please note that in order to use the latest stable builds Nexus 4 (Mako) and Nexus 5 (Hammerhead) you need to flash the CM 12.1 images first using CWM/TWRP. In order to do so, you might be required to do a “factory reset” or at least “wipe cache”. CWM/TWRP will indicate when this is needed. After successfully flashing CM 12.1, make sure to boot it at least once before going back to CWM/TWRP to flash the latest LuneOS image! We have provided links to CM 12.1 for these 3 images on our device pages below. Installation instructions for TouchPad (Tenderloin), Nexus 4 (Mako), Nexus 5 (Hammerhead) and Emulator are on the wiki. 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 webOS Nation forums. Catch us on Twitter @webosports on IRC: Freenode:#webos-ports or email [email protected] We will see you shortly again with a new release! Picture Credit: Chevanon. Cropped & flipped. Text added. Related posts: LuneOS July Stable Release: Cortado LuneOS February Stable Release: Chai Latte LuneOS September Stable Release: Decaf View the full article

      By pivotCE, in pivotCE News

      • 0 replies
      • 114 views
    • Question: because I can not install or update apps?

      Hi people,
       
      Recently bought one 49LF6350 and one 43LF6350 and the two models have the same problem, whenever I try to open an application, informs me that I have to update (required update, you must update this app to launch it. the update may cause data to be stored deleted.), and when I try to update, it gives an error message (application has not Been instaled. try again). It happens to apps also store to at new install. what may be occurring?
       
      software version: 3:03:04
      WebOS TV version: 2.0.2-3928 (behive-badlands)
       
      thanks.

      By Vanilton Coelho, in LG webOS Smart TV App Questions

      • Awaiting best answer
      • 0 votes
      • 14 answers
    • webOS 4.0 confirmed within iOS and Android App Release Notes

      Thanks to @Peter Alexander and @SSM we have confirmation of webOS 4.0 compatibility within the release notes and information listed for their respective apps in the below topic.   We've confirmed the iOS version changes:   We've also confirmed Android: Both version updated were added this week. We are waiting for an official webOS 4.0 press release from LG and additional information on what models are supported.

      By Alex, in LG webOS Smart TV Discussion

        
      • 3 replies
      • 6,411 views
    • Question: how to "forget/skip" wrong XPLAY update

      Hello,   I've read on the XPLAY forum about various problems with the latest version, so I decided to postpone the update until the issues are solved. I really don't know where the problem is but the developer said: "They have approved a quiet old version what has no online update functionality and the only way to fix anything or add new functionality is to send it to LG QA team … but they arrrrr soooooo much slow. Ive send them (on several days ago) version latest dev version with online update functionality. It will allow me to react to bugs much faster …"   My setup is: TV: LG 55EG920V, WebOS 2.0, Software version 04.25.70 XPLAY: 20180322.1.2.8 (ONLINE) PLEX: 1.13.8.5395   The version available for update in LG content store is 2.189.171 (08.10.2018). Many users complained they couldn't login anymore after upgrading to this version.   Could you please tell me what is the correct version should I update and when it'll be available for my TV? Also, is there any way to skip this update?  I just want to avoid an accidental update which would broke the functionality...   Kind regards,

      By Mihai B., in LG webOS Smart TV Questions

      • Awaiting best answer
        
      • 0 votes
      • 12 answers
    • Question: How can I install different/older version of webos on the tv ?

      I want to choose my version .. how to do that ?

      By Youssef Mohamed, in LG webOS Smart TV Questions

      • Awaiting best answer
        
      • 0 votes
      • 1 answer


×