Results 1 to 8 of 8
Like Tree4Likes
  • 1 Post By Preemptive
  • 1 Post By Preemptive
  • 2 Post By Herrie
  1.    #1  
    I was going to revive this: webOS on Raspberry Pi? - webOS Nation Forums which is worth a read, but I decided to start a new thread. Why?
    Raspberry Pi 2 on sale now at $35 | Raspberry Pi

    This new version is ARM7 @900MHz with 1Gb of Ram. I don't know how the Broadcom chipset compares to Qualcomm, but the speed is almost that of a Pre2, 2/3 that of a Pre3 and double the RAM of both.
    Possibly, this will address the concerns about the device's power expressed in the previous thread. Additionally, this should be fully compatible with the earlier devices which have been greatly optimised since the first launch.

    So what are the potential benefits of porting webOS to RaspberryPi? Some thoughts:

    • Many are clamouring for Android on the Pi. There is a port, but Android is a stripped down OS for mobile and this isn't supported by Google or RaspberryPi. It runs so slowly that it is completely unusable. I'm not aware of any 'mobile-type' OS available for this computer and those seeking one might jump at the chance of webOS.
    • A common use of the RaspberryPi is as a media player or jukebox. We have seen the success of LGwebOS on TV's. A slick touchscreen interface could be very popular and easily adapted by developers.
    • RaspberryPi is intended for students, 'makers' and hackers. webOS is very open and hackable, so should be attractive to this group.
    • Compared to other mobile systems, webOS doesn't have a lot of apps, but it does have plenty of quality, mobile apps ready to be deployed. Moreover, creating new apps with HTML & javascript is supposedly fairly easy.
    • Any OS developments and apps from the RPi community could be available to the main OpenwebOS / LuneOS development.
    • To date, there is estimated to be 4.5million RPis (all types) sold. That approaches the numbers of LG webOS TVs sold and is a broad user base - most of whom are likely to be tinkerers / developers / software engineers.
    • A port has already been attempted. It is here: Raspberry Pi - WebOS-Ports You can see that Qt 4.8 was the stumbling block.
    • It seems that Qt5 has now been ported: RaspberryPi | Qt Wiki | Qt Project & Qt5 | Raspberry Pi

    Arguably, the RaspberryPi is not an ideal device for a port - certainly no one on the Raspbery Pi forums has completed one, but adding a touchscreen display offers a tablet style device or project control panel for which a webOS UI would be ideally suited. If a working version was made available, RPi users might quickly discover the ease with which apps and the platform itself can be developed.

    Before going further, I should point out that unless the process is as easy as assembling parts and running a machine that pops a working OS out of the other end, I don't have the skills, so it's very unlikely I will do this. My purpose here is to gather information and stimulate a bit of discussion that will hopefully inspire a skilled individual or group. I assume if it was that easy, someone will have put out a port over a weekend by now. Note that I'm also not suggesting that webOS ports should do this as they are still building the system on devices best suited to it.

    So, if the prerequisites appear to exist, what might prevent a port?

    • To work on existing devices, LunaSys manager had to be completely rewritten (LunaNext) to function on a layer of Android drivers. As previously noted, there are no Android drivers for the RPi and an attempted port is unusable. However, I think the drivers are a layer in a software stack. OpenwebOS will run on a PC and as Linux drivers clearly exist for the RPi, porting with the original LunaSys manager should work.
    • If the above is true, will LuneOS work with LunaSys? Or is it only compatible with LunaNext? Will a port be restricted to the 'barebones' of the original open-sourced code? Perhaps the missing parts relate largely to telephony. While there are RPi telephony or wireless projects, these will use different H/W and different drivers, so this can be probably be ignored or added according to use case. About other LuneOS parts, I'm not sure. (Update) According to eblade below, LunaNext may work on RPi with Qt5.

    Heres another list. My ignorant guess of what is required to make a port.

    My assumption is that having set up an environment to build an OS, assembling pre-existing parts and compiling them with a script is fairly straight-forward if you know your stuff. With a new build, the problems arise in the code - finding and fixing bugs and compatibilities so that the build works.

    More links:
    How to Make a Computer Operating System (with Pictures) - wikiHow
    Building and Installing Software Packages for Linux: Introduction
    Create Your Very Own Operating System With Linux From Scratch [Linux]

    So please correct my assumptions, tell me how easy this will be or how it will never work. Add your own knowledge so I can update this post and perhaps we will have solid enough information that someone will make an attempt!
    Last edited by Preemptive; 02/13/2015 at 06:56 AM.
    hfGermany likes this.
  2. #2  
    I don't have specific answers for you, but I suspect that Luna-Next will probably work without the Android interfaces, if fed a proper Qt 5 platform QPA. If it doesn't, then it probably should.

    The software stacks are MUCH more mature on Pi than they were the last time that I know this was attempted.

    I guess the first thing I'd be interested in... is there a touch-screen interface available for Pi2? Because at this point, I don't think anyone outside of LG has made a pointer based interface work in webOS. Emulator doesn't count, because it simulates a touch screen.
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    People asked me for a donate link for my non-catalog work, so here you are:
  3.    #3  
    Like this?
    Raspberry Pi touch cam Specifically:
    PiTFT - Assembled 320x240 2.8 TFT+Touchscreen for Raspberry Pi ID: 1601 - $34.95 : Adafruit Industries, Unique & fun DIY electronics and kits , It seems it requires Raspian & a stylus.
    Slimline point-and-shoot camera from Ben Heck | Raspberry Pi This seems to use fingers, but I think resisitive is like the old Palm screens - pressure rather than touch sensitive.

    Or by pointer-based, do you mean support for gestures rather than simply registering touches? Or are we talking magic remote type stuff? There is a mouse pointer type thing in this: XServer - Preware Catalog I don't recall it doing anything else! ;-)

    Not sure if this is relevant: Pointer Events W3C Spec.

    What's QPA?
    Last edited by Preemptive; 02/13/2015 at 06:57 AM.
  4. #4  
    Someone made a tablet out of a Raspberry Pi -

    Touchscreen doesn't work with the OS he installed, apparently.

    I sense the lines representing LuneOS maturity and homebrew hardware are starting to converge.
  5.    #5  
    Quote Originally Posted by George Mari View Post
    Touchscreen doesn't work with the OS he installed, apparently.

    I sense the lines representing LuneOS maturity and homebrew hardware are starting to converge.
    I got the impression that it was to do with compiling the drivers into the particular distro.

    Obviously as a tablet / phone OS, webOS would be ideal for this application and of course, almost any application requiring a touch screen interface. One particular idea that occurs is to make a 'set-top-box' for a dumb TV. Use Enyo moonstone and roll your own smartTV interface. Screen & STB are now independently upgradable and so is the software... no more stuck on version one!

    The PiPad is a nice looking project and the price is not huge, but as pointed out, a cheap Android tablet is probably more capable (but less upgradable or flexible). For open webOS to gain any future traction, it's main home must be on mass produced hardware. To begin with, that will be what is available and open (as now). However, the increasing commodification of this type of hardware may reduce the costs of making mobile devices, allowing smaller scale entrants to the market - possibly with smaller production runs. The RPi itself was first produced in a batch of 10,000.

    Nonetheless, even these relatively small numbers likely exceed the number of remaining and interested webOS users, so reaching out to the millions of RPi users who are also as a group most likely to contribute back to OS or app development seems a reasonable idea to grow the development and wider community who might then buy a community developed device. That will take a while.
    Last edited by Preemptive; 02/14/2015 at 10:23 PM.
  6.    #7  
    The code is now available:

    Note that this uses the official RPi touchscreen. Other screens may require additional coding to work.
  7. #8  
    Quote Originally Posted by Preemptive View Post
    The code is now available:

    Note that this uses the official RPi touchscreen. Other screens may require additional coding to work.
    We're trying to see if we can somehow make this an official build and include it in our supported targets. More to follow
    HP Veer (daily driver), HP Pre 3, HP Touchpad Proper 4G/LTE (Sierra MC7710), HP Touchpad 32GB WiFi, Palm Pre 2
    Preemptive and hfGermany like this.

Similar Threads

  1. Triple boot CM9, webOS/CE & LuneOS?
    By ryancell in forum LuneOS
    Replies: 88
    Last Post: 02/07/2017, 07:58 PM
  2. Enyo2 Maps for LuneOS and webOS
    By 72ka in forum webOS Development
    Replies: 45
    Last Post: 07/10/2015, 02:29 AM
  3. webos OpenEmbedded distribution renamed to luneos
    By webOS Ports in forum LuneOS
    Replies: 0
    Last Post: 01/09/2015, 09:31 AM
  4. webOS on Raspberry Pi?
    By gerzhwin in forum Open webOS General Discussion
    Replies: 28
    Last Post: 09/22/2012, 12:23 AM

Posting Permissions