Quantcast
Jump to content

Recommended Posts

Posted

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!



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
      I’m pretty sure it’s safe to say there are more HP TouchPads left in the world than there are their matching original barrel chargers. This means if you have a TouchPad today, you’re probably using a TouchStone, a computer, or any other random USB A charging brick to (very slowly) charge your 13 year old device. And it means you’ve seen the error message in the image above every time you’ve plugged it into anything other than the original barrel charger or a computer. Fun fact, you can trick the TouchPad into charging normally and not feeding you the message by creating your own custom micro USB or USB C cable if you’ve
      link hidden, please login to view. Stuff You’ll Need
      Assuming you have a micro USB (ie. non USB C modified TouchPad) you’ll need:
      1. A 4-wire micro USB to USB A cable
      2. and 1/4 watt resistors (1 each per cable)
      3. Soldering iron and solder
      4. Heat shrink or electrical tape
      If you’re making a USB C cable but only want to use it with a USB A charger then you’ll need:
      1. A 4 wire USB C to USB A cable
      2. Items 2-4 above
      If you’re making a true USB C to USB C cable that you plan to use with a USB C 3.1 charger you’ll need:
      1.
      2.
      3. Any 2-wire cable or a 4-wire cable that you’ll cut the data wires out of (green and white typically) and that you’ll cut the ends from
      4. Items 2-4 from the first section above
      Prepare the Wires
      Regardless of which cable you’re making, the end that goes to the TouchPad will need all 4 wires and the resistors. So grab the 4-wire cable of your choice and strip the ends, and I recommend pre-tinning them with some solder.
      Build the TouchPad Side of the Cable
      See the image below for how to arrange the resistors. If you’re making a USB A cable, go ahead and cut into two pieces, set aside the USB A side, and grab the micro or USB C for this part.. It doesn’t matter how far away from either end you go, it’s your choice. Strip the wires back so you have enough bare wire to work with.
      1. Solder the ground (black) wire to one side of the 300k resistor.
      2. Solder data- (green), data+ (white), the other side of the 300k resistor and one side of the 250k resistor together.
      3. Then solder the other end of the 250k resistor to the red (power) wire.
      Build the Charger Side of the Cable
      If you’re making a USB A cable, then all you have left to do is reconnect power (red) and ground (black) to their corresponding colors on the TouchPad side of the cable, trim off the data lines from the USB A side, clean it all up with some heat shrink or electrical tape and you’re done!
      If you’re making a USB C to USB C cable grab the USB C board I linked above and your 2-wire cable (or 4-wire that you’ve trimmed the data lines from). You’ll also have to cut the end off to make room for the new connector.
      1. Pre-tin the board on the two outside pads marked as VCC and Gnd in the image below.
      2. Solder on the red (power) wire to VCC and then black (ground) to Gnd. If you bought the housing and boards together, don’t forget to the housing on the wire before you start soldering. You also may need some super glue to keep the plastic housing from coming apart.
      3. Back at the TouchPad side of the wire, take the other end of your 2-wire cable and attach red and black to their corresponding ends, clean it up with some heat shrink or electrical tape and you’re done!
      Final Thoughts
      You should now be able to use any charger you want to and the TouchPad will believe you’re plugged into a normal battery charger and will allow the normal charge rate flow through.
      Note, you’ve effectively removed the ability to use this cable for Data since the data lines are no longer connected.
      Also, for those who modded the TouchPad with USB C, the port already has 5.1k resistance but cannot communicate that to a USB C 3.1 charger with the added resistance on the data lines. This is why the TouchPad end of the USB C cable must be a “dumb” 4-wire USB C cable and the charger end needs the 5.1k resistance to tell the charger on that end to send power. This also means that you must remember which end is which, but don’t worry. Picking the wrong direction won’t hurt anything as the USB C charger won’t allow power since the wire doesn’t tell it to. I marked the TouchPad side of the USB C cable with a dab of orange paint pen.
      Finally, I hope you found this helpful or at the very least entertaining! I had fun exploring the different ways of making this work and so feel free to give it a watch.
      #webos4ever
      The post first appeared on . Related posts:

    • By pivotCE
      Well, it’s 2024 and technology continues to advance. The TouchPad isn’t new by any means, but that doesn’t mean it can’t be slightly modernized to be more convenient today. Specifically, it is entirely possible to convert the TouchPad’s Micro USB port to USB C for charging and USB storage access. I’ll show you how.
      This is a tough mod which requires micro-soldering and modifying a PCB which you will have a hard time sourcing a replacement for without buying another TouchPad. Proceed at your own peril.
      Tools for the Job
      To do this mod you’ll need a few things for tools and parts. Here’s a list of what I used:
      – Needle nose pliers/tweezers
      – USB C boards with 5.1k resistors
      link hidden, please login to view
      – Soldering iron, solder, flux and a hot air station
      – Flush cuts
      – Dremel with cutting or sanding wheel
      – 28 AWG wire or smaller. 30 AWG is pretty good but any wire around 0.25mm to 0.5mm should work.
      – Small file and screwdriver set
      – Painter’s and kapton tape
      – Metal spudger Disassemble the TouchPad
      This is where you’re going to want to get that metal spudger out and be very careful not to snap clips. I can’t explain it better than iFixit already did so go check out their and then come back here.
      Modify the USB Connector Board by Removing the Micro Port
      There are a few ways to remove the Micro USB port. I added a bunch of flux and coated all the connectors in fresh leaded solder and then used a hot air station set to 800 degrees while wiggling the port very slightly with needle nose pliers. You don’t have to be particularly careful here so if you want to cut the port off with the dremel or the flush cuts or just rip it off with the pliers, (I don’t recommend it but…) that’s fine. We’re not using the pads it’s soldered to anyway. You should STILL be careful not to crack the board. Go slow. Be patient.
      Trim the USB C Board
      We need to expose the USB C port a bit on this board so let’s cut it down. Grab the painter’s tape and flip the USB C board upside down. You’ll see a small trace between the front and rear anchor points on the right side, which we don’t want to cut. Mark the tape just on the other side of that trace like I did. Dremel along the tape line until you get to the port. You can then use needle nose pliers, a flat file, and/or flush cuts to remove the rest of the board from the bottom of the port.
      Prepare the USB Connector Board for the USB C Port
      We need to slide the port into the old space so grab the painter’s tape again and mark off the area I marked to make room for the USB C port. You can place the port up to it like I did and use that as a guide. Grab your dremel again or a similar tool and cut out what you marked off. When you’re done, the USB C port should slide easily into the groove. It will fit tighter when we add the kapton tape in a later step.
      Make Room in the TouchPad for the Added Thickness of the USB C Board
      The USB C board will sit underneath the USB connector board so we have to make room by trimming away the plastic underneath. For this you’ll need to use flush cuts or any other tool you have to chip away. You could use the dremel for this if you’d like. Be careful to not go beyond the first inner layer. Beyond that is the outer shell of the TouchPad. There’s no real method here, just cut out the screw posts and chip away. Use the pictures below as a guide.
      Cut the USB C Hole from the Old Micro USB Hole
      To open the micro USB hole enough to fit the USB C port, take a rounded file to the left and right of both sides and just file a little bit at at time. Use a small flat file to widen the top and bottom of the port. This process is just trial and error. File a little and then grab the USB C board to test. The port will need to fit inside the hole a bit so you can push it through from the outside to test the hole size if that’s easier. Note: the USB C board will likely not rest on the bottom of the TouchPad and will float a little. This is good because it makes room for your wires and a little kapton tape underneath.
      Tape the USB C Board
      Since we hacked away at the USB connector board it’s possible we’ve provided the perfect environment for creating shorts! Oh no! So get out the kapton tape because we’re going to add a layer on both sides. You’ll see how I did it on one side below. Do it on both sides. You’ll also notice how I did not cover those two small square contacts just at the bottom of the tape. That’s because we need them.
      Where To Get Power and Data
      You’ll see the diagrams below which I’ve marked with VBUS (power), data in, data out, and ground. Obviously the old port is gone and most if its pads, but I wanted to show that both sides of the board have the connections. You could possibly do this mod differently, and if you so choose, hopefully these help.
      A quick note: this mod can be done with a 4-pin USB C port. That would give you power and data just like with the USB C board I’m using in this guide, however, a 4-pin USB C board will not charge with a USB C charger (ie USB 3.1). The board I’m using in this guide provides the ability to use any charger because it comes pre-built with 5.1k resistors wired to CC1 and CC2 to ground. This is the trick that tells the USB C chargers to send power to the device.
      Solder the USB C Board into the USB Connector Board
      This isn’t a “how to solder tutorial” so hit up youtube and find a good tutorial that works for you. In general though, use flux, pre-tin the VBUS, Ground, D-, and D+ pads on the USB C board as well as the points on the bottom of the USB connector board.
      Now for the tricky part, I didn’t list it in the Tools section above, but it would really help to have magnification or a digital microscope for this. I have these things and I used both. You might have steadier hands and better eyes than me. The picture below was my first attempt of the three TouchPads I modded, and it’s not my best soldering work, but fundamentally, this is what yours should look like.
      Put the Pieces Together
      You can use a bit of kapton tape to secure the wires in place a bit more if you’d like but it’s not required. It won’t short since it’s only plastic underneath. This is all press fit into place, but if you’re uncomfortable with that, you can add a little hot glue under the board as you put it back into the TouchPad. You don’t have to put the metal shield back into place if you don’t want to. It’s all a pretty tightly fit and if you find the TouchPad screen isn’t as flush as you want, just leave the metal shield off. A little kapton tape right on top would be fine instead.
      Congrats, You Now Have USB C
      I did this mod on three TouchPads and each one works fine with any USB charger I could find, including USB C port having USB 3.1 chargers. I can also confirm the data connection works just like it should to connect via USB mode on PC. Sadly, this doesn’t do anything to stop webOS from telling you the charger you’re using isn’t the original TouchPad barrel charger, but you can make a custom cable to stop that which I’ll cover in a future article on pivotCE.

      #webOS4ever

      The post first appeared on . Related posts:

    • By News Reporter
      Company’s Industry-Leading LG UltraGear Gaming Monitors to Support the World’s
      Top Pros at Global Festival of Esports in Riyadh

      SEOUL, June 26, 2024 — LG Electronics (LG) has been announced as the official partner of the Esports World Cup (EWC) 2024, set to take place in Riyadh, Saudi Arabia, from July 3 to August 25. Formerly known as Gamers8, EWC is an annual international esports tournament. This year’s edition – the first under the EWC name – will host competitions for 21 of the world’s biggest online games, including League of Legends, Overwatch and Fortnite. The exclusive gaming monitor of the event for the third consecutive year, the LG UltraGear will take center stage at EWC 2024, supporting the world’s top gamers as they battle for victory in Riyadh.
      Boasting the largest prize pool of any esports tournament, EWC 2024 promises eight weeks of thrilling gaming action, featuring over 1,500 professional athletes. The acclaimed LG UltraGear OLED gaming monitor (model 32GS95UE) will be prominently featured at the event. Additionally, more than 990 UltraGear gaming monitors will be utilized during league matches and showcased at LG’s booth at EWC.
      LG UltraGear, the company’s premium gaming brand, provides next-level gaming experiences for both professional athletes and amateur enthusiasts alike. These gaming monitors offer high refresh rates, rapid response times, and vibrant, crystal-clear images; a combination that drives gaming immersion to dizzying new heights.
      Along with its premium self-lit screen, the 32-inch LG UltraGear OLED gaming monitor (model 32GS95UE) features the world’s first VESA-certified dual-mode technology, ensuring an optimized gaming experience at both UHD 240Hz (ideal for visually stunning, narrative-rich games) and FHD 480Hz (a great choice for fast-paced FPS, MOBA and racing titles). It also incorporates LG’s Pixel Sound technology for more realistic and three-dimensional in-game audio.
      LG’s involvement in EWC 2024 is part of the company’s ongoing efforts to advance esports worldwide. In addition to EWC and its predecessor, Gamers8, LG sponsors and actively participates in major gaming competitions such as the League of Legends Champions Korea and the League of Legends EMEA. Through consistent engagement with the gaming community and the exceptional performance and features of its UltraGear gaming monitors, LG has become a respected name in the world of esports.
      EWC 2024 attendees can visit LG’s booth to try out the same UltraGear gaming monitors used by their gaming idols throughout the tournament. They can also improve their own gaming skills by taking part in coaching sessions run by the LG-sponsored Gen.G Global Academy. Furthermore, visitors to LG’s booth can win prizes by participating in exciting competitions and events.
      “Saudi Arabia’s premier esports festival, EWC is the new destination for esports fans,” said Mohammed Al Nimer, Sales Director at EWCF. “We’re excited to work with partners like LG, who share our passion for gaming and esports-culture, and to have LG UltraGear as the official gaming monitor of the inaugural EWC.”
      “It’s a real honor for LG UltraGear to be named the official gaming monitor brand of an esports event as momentous as EWC 2024,” said YS Lee, vice president and head of the IT business unit of LG Business Solutions Company. “Designed to satisfy the needs of both professional and casual gamers, LG UltraGear OLED gaming monitors are tailor-made for next-level gaming experiences.”
      For more information about EWC 2024 and the latest LG UltraGear gaming monitors, check out and follow LG UltraGear (
      link hidden, please login to view). # # #

    • 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:

    • Solution For That Pollution
    • 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:

×
×
  • Create New...