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 modified your TouchPad. 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. 250k and 300k 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. A 4-wire USB C cable 2. A USB C board with 5.1k resistor and the housing for it 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 live streamed it on Twitch so feel free to give it a watch. #webos4ever The post Guide: Create an “Original Barrel” Charging Wire for your HP TouchPad first appeared on pivotCE. Related posts: Guide: Converting the TouchPad’s Micro USB Port to USB C Putting a Touchstone in My Car: A Walk Through My Process Guide: Saving Apps From The App Catalog Part 1: nodeleteipk patch View the full article

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 Amazon – Soldering iron, solder, flux and a hot air station – Flush cuts Amazon – 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 disassembly guide for the USB connector board 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. Talk about it on the Legacy webOS Forum #webOS4ever The post Guide: Converting the TouchPad’s Micro USB Port to USB C first appeared on pivotCE. Related posts: UPDATE: webOS Ports surprises with TouchPad port, name/logo change, Nexus 4 Guide: Coming (Back) to webOS in 2014, Part 1 View the full article

The Vintage Computing Federation hold a number of events. This year’s VCF East festival will be of interest to fans of webOS phones, tablets and other computing devices of the past. The festival is held at the InfoAge Science Center, 2201 Marconi Rd., Wall, New Jersey, 07719 and runs over three days from the 12th to 14th of April. The festival includes three elements: Exhibition of various old computer systems – some with modifications to function in the modern environment. A programme of talks and discussion. Sales of devices and other collectables. For readers of this blog, representation of webOS devices will be in two of those areas. Jon W of the webOS Archive 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 VCF video channel and TouchPads are available remotely at Tindie Discussion is at the VCF East forum thread. You can read more about the InfoAge museum. Picture Credit: Apc106, Wikimedia Commons. The post webOS Talk at VCF East first appeared on pivotCE. Related posts: Calling East Coast (USA) Enyo Developers webOS meetup, Chicago, 17th April webOS meetup, Chicago, 3rd June View the full article

Sooo that was a really long time since a release, but webOS Ports 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 webOS Archive and made plans on the associated Discord server. Much of the old information from webOS Nation was preserved thanks to the internet archive and can still be accessed, if imperfectly. We have now set up a new community forum 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 Yocto “kirkstone”, 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 Qt6 (6.5.2 included in this release). We have moved away from our own compositor (luna-next) to the one provided by LG in webOS OSE 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 webOS OSE release 2.23.0 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 Pine64 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 tow-boot on Pinephone. The new close to mainline kernel for the Pine64 devices allows them to run things like Waydroid out of the box! All other supported Android devices are now based on Halium/Android 9.0. So what is ahead for the near future? Our focus will be on the mainline devices and emulator (qemux86-64), 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 LG TV homebrew community. 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 the bug tracker. Get involved and [ UPDATE https://pivotce.com/2014/09/22/webos-ports-help-wanted/ ] Download and Install 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. Installation instructions 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 Lives forums. Catch us on Twitter @webosports on IRC: Libera:#webos-ports, Telegram or email [email protected]. We will see you shortly again with a new release! Picture credit: roDesignment from Pixabay The post LuneOS February Stable release: Eiskaffee first appeared on pivotCE. Related posts: LuneOS February Stable Release: Chai Latte LuneOS November Stable Release: Doppio LuneOS October Stable release: Eggnog Latte View the full article

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 IRC and/or Telegram 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 Issue Tracker to see current issues. Find an area where you think you can help and then find us on IRC or Telegram (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 WebOS-Ports Issue Tracker, 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 Telegram 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: @webosports IRC (Libera): #webos-ports Telegram: LuneOS Developer Community Issue Tracker: WebOS-Ports Issue Tracker webOS Forum User Support Forums Join the forum conversation. The post LuneOS: Help Wanted 2024 first appeared on pivotCE. Related posts: A future JavaScript framework for LuneOS – Demos wanted! webOS Ports: Help Wanted LuneOS November Stable Release: Doppio View the full article

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 webOSNation.com 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, head over to the thread. You may want to consider joining the discord instance at the webOS Archive. The post Sunset of the webOS Nation Forums first appeared on pivotCE. Related posts: UPDATE: Forums and Communities fixed (webOS 2.x and up) for webOS Nation browsing LG tests webOS on a Nexus 5 Project updates – Open webOS hits Alpha 3, ACL for webOS pushes pre-release View the full article

Picture credit: pxhere.com Happy Halloween! The long wait is finally over #LuneOS and #webOS fans! We’re back with a new release called “Eggnog Latte” which is a milestone in terms of developments and paves the way forward! So you’re wondering what we’ve been up to since our previous stable release at the end of last year? We have done many major upgrades to a large number of components of our stack being: Migration of Open webOS to webOS OSE components. We are almost half way there in terms of the migration of old Open webOS components to their webOS OSE replacements. This was a monumental task due to the fact that webOS OSE code was released without any history. So every component needed to be analyzed to understand what was changed in the years of development inside of LG Electronics. Our custom changes needed to be re-assessed and re-implemented into the new components where applicable. A change of direction in certain aspects in terms of architecture made the whole exercise even more complicated. We do however believe that we’re in a good state now in terms of migration. There are still quite some components to migrate and we’ll get through that in the next releases. Qt: We migrated from Qt 5.11.3 to Qt 5.12.5 which included an update for Chromium from 65 to 69 amongst other improvements. Yocto upgrade: We upgraded from the no longer supported Yocto Pyro release, via the intermediary Rocko, Sumo and Thud releases to the latest Yocto release called Warrior. We have been working closely together with the Halium, Mer and PostMarketOS projects and have made further integrations between LuneOS and the various projects 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 and more devices. We have also worked on support for devices which use a mainline kernel instead of an Android based kernel. As you might have seen, we have been working on support for the Pinephone which uses a mainline kernel. We also have been testing with the Nexus 5 (hammerhead) using a mainline kernel. All our setup has now been adjusted so we can work with both Android based targets and kernels as well as mainline kernels. LG has a very clear vision in mind for webOS OSE as can be read on their blog posts. Since the initial release of webOS OSE 1.0 in March last year, there has been a total of 11 releases of webOS OSE already with a lot of improvements and added features added with each release. This month LG has released webOS OSE 2.0.0 with a lot of new features and also a new roadmap. The following items on our to-do list will be where we focus next: Migration of remaining Open webOS components to the newer webOS OSE components and assess where further synergies could be achieved. Migrate to Yocto Zeus release. Update to Qt 5.13. Migrate Nexus 5 (hammerhead) to use mainline kernel. Finalize port for Pinephone. Work on support for Halium 8/9/10 in order to support newer targets. 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. Telephony not working on the Xiaomi Android 7 based targets. We have found the root cause, but haven’t been able to solve it yet. Virtual Keyboard sometimes randomly doesn’t appear. Changelog Applications: Preware IPKG Service: use postinst_ontarget Tweaks: Fix for LS2 from webOS OSE Camera: Remove RDEPEND on libhybris FirstUse: Fix for LS2 from webOS OSE Maps: Fix Google API calls Messwerk: Add testing app for various sensors Phone: Fix calling Settings: Fix displaying of device information, fix compatibility with LS2 from webOS OSE Update: Fix parsing of JSON files with update information. CDav: Fix issues after migration to webOS OSE User Interface: Various minor fixes for status bar & indicators in emulators System Level: Yocto upgrade from 2.3 Pyro to 2.7 Warrior Qt upgrade from 5.11 to 5.12 Pinephone support added activitymanager: RDEPENDS on bootd add meta-qt5-compat layer Add VIRTUAL-RUNTIME_android-initramfs-scripts variable in machines conf alsa-lib: update the patches for 1.1.8 alsa-utils: Rename bbappend to match new version from oe-core anbox, ashmem, binder: bump SRCREV; add COMPATIBLE_MACHINE restriction; Add elfutils to DEPENDS to solve QA issue; Add some RDEPENDS,RRECOMMENDS; fix build with boost 1.71.1; fix parallel build issue; restrict COMPATIBLE_MACHINE a bit more anbox-data: add recipe for retrieving android image 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: use API 22, patched to match tenderloin specific content; fix patches to match Halium’s android-kernel-bootimg: append DTB when specified; dedicated recipe for creating boot.img; minimal support for A/B partitions android-property-service, mtp-server, pulseaudio-modules-droid, qtubuntu-camera, qtvideo-node, qt5-qpa-hwcomposer-plugin, qtscenegraph-adaptation, qtsensors-sensorfw-plugin sensorfw, nyx-modules-hybris, org.webosports.app.camera: restrict to halium MACHINES; add dependency on virtual/android-headers 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; only start after main partitions are mounted; 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-: bump to 20180311 Halium build; skip already-stripped QA android-system-image,base-files: use system.img directly android-system-image: Add symbolic link for wifi; Bump Halium images; bump mako,tenderloin,hammerhead; Change wop into luneos; convert the sparse image if needed; create /userdata; make \”symbols\” directory optional; Update halium bits to halium version numbers android-system-image-athene,onyx,mido,angler: bump PV android-system-image-mako: fix install; fix install script; fix typo android-system-image-rosy: use build from webos-ports android-system-image-tenderloin: bump PV; Fix checksums; Update Android image; Use a Haloum 5.1 based Android build android-system-image-tissot: bump PV; Bump PV to fix adb; Bump PV to kill qseeproxydaemon on Android side; bump to 20180302-18 android-tools: move the changes to meta-oe android-tools: remove android-tools-conf: provide whole android-gadget-setup instead of patching it in do_install; use backported recipe angler, hammerhead, mako, athene, onyx, mido, rosy, tissot: stop building ext4 images by default angler,athene,onyx,mako,hammerhead: systemd-machine-units: add rfkill unblock wifi app-services, configurator: Bump SRCREV; fix LS2 for webOS-OSE ashmem, binder: move udev rules to kernel-module--linux package and empty PN base-files,android-system: Android partitions are now mounted by Halium’s initrd base-files: add /system/lib64 in LD_LIBRARY_PATH bootd: introduce recipe from webOS-OSE; Fix systemd service file busybox: also build telnetd module; also create by-label entries with mdev; mdev: use /dev/disk/by-partlabel instead of by-partname; mdev-partname.sh, mdev.conf: drop trailing spaces; mdev-partname.sh: remove probablly unnecessary ACTION assignment; mdev-partname.sh: use 4 spaces for indentation instead of mix of tabs and spaces; provide busybox-mdev with custom partname symlinks; use 4 spaces for indentation instead of mix of tabs and spaces and BPN in FILESEXTRAPATHS cmake-modules-webos-native: Add back PV; add missing quote; Bump PV com.webos.service.pdm: Remove inherit webos_machine_impl_dep configurator: Move to webOS OSE version; Bump SRCREV connman: move PACKAGECONFIG modification to .bbappend, remove dependency on xl2tp in signature; refresh patches to apply cleanly; update to v1.36 cpushareholder-stub, luna-sysmgr-ipc-messages, luna-webkit-api, rdx-utils-stub: inherit allarch before webos_cmake cpushareholder-stub: Migrate from OWO to OSE db8, filecache: Bump SRCREV, app-services: Bump SRCREV and cleanup recipe db8, nyx-modules: Minor fixes after OSE rebase db8: Add back dropped PV; Bump SRCREV and drop patch now merged in repo; cleanup a bit; fix db8-tests runtime depends; fix LS2 for webOS-OSE; Update to latest revision and remove references to com.webos.service.attachedstoragemanager dbus-cpp, process-cpp, properties-cpp: Switch to GitHub & latest commits dbus-cpp: fix compatiblity with boost 1.66.0 defaulttunes.inc: return accidentally dropped last line; use armv8a-crc-crypto for both raspberrypi[34]-64;use cortexa8thf-neon for currently supported 32bit arm MACHINEs;use different TUNE_PKGARCH_64 for raspberrypi3-64 MACHINE directfb: Drop .bbappend distro: luneos: switch release name to Eggnog Latte downloadmanager: Remove recipe event-monitor, event-monitor-network: Add recipes from OSE exiv2: Update to 0.27.1 extra-cmake-modules: Bump to latest from upstream filecache: Bump SRCREV Fix meson bbappend Fixup line endings funyahoo-plusplus: Update to latest from upstream Further work on webOS OSE migration; Further changes for webOS OSE; Further migration for webOS OSE gcc: restore gcc-7.3 from Yocto 2.6 Thud geoclue: backport gtk-doc.bbclass changes from Yocto 2.8 Zeus to make GTKDOC_MESON_OPTION work in Yocto 2.7 Warrior; Fix typo;fix unknown-configure-option QA issue; Rename .bbappend to be generic; Update to 2.5.3; use backported recipe; Add to meta-webos-ports for fixes & upgrade glib-2.0: Rename bbappend to match new version from oe-core; update 0001-gdbus-codegen-replace-plus-also-with-underscore.patch to apply on 2.58.0 version; update patch to apply on 2.54.2 version; add work around for broken ld-2.29.so when gold is used; drop bbappend; export LDFLAGS glm: use 0.9.9.3 version from meta-oe glmark2: disable wayland-gles2 GnuTLS: Fix missing system trust gstreamer1.0-plugins-base: disable egl gtest: don’t rdepend on ${PN} from ${PN}-dev; export LDFLAGS hammerhead kernel: delay wifi init hammerhead, mako, tenderloin: Use Halium image built with Ports repos; use WOP builds of Halium hammerhead, mako: Add NFC as machine feature hammerhead.conf: use initramfs-scripts-halium hammerhead: temporarily disable gobject introspection https-everywhere: Update to latest from upstream hunspell-dictionaries: Update to latest from upstream; use backported recipe icyque: Add recipe Ignore generated pycache directory iio-sensor-proxy: introduce recipe imaccountvalidator, activitymanager, db8, filecache, sleepd, luna-service2: Bump SRCREV imaccountvalidator, imlibpurpleservice: Add icyque plugin imlibpurpleservice, org.webosports.service.messaging, webos-telephonyd, app-services, core-apps, nodejs-module-webos-sysbus: Bump SRCREV Include android-kernel-bootimg for each MACHINE that needs it Initial work for webOS OSE migration initramfs-android-image: make it possible to add content; make sure that ANDROID_EXTRA_INITRAMFS_IMAGE_INSTALL is expanded initramfs-android-recovery-tissot: skip file-rdeps QA as well initramfs-boot-android: cosmetics; disable busybox extreme symlink checks; fix image identification for rootfs on partition; import Fix-userdata-mount-options.patch from meta-hp; init.sh: be less verbose for initial user data copy; mount /dev/pts for cases when enable_adb is used; put .firstboot_done in a rw folder; reset uevent_help when stopping mdev; split halium and generic version; use mdev instead of udev initramfs-boot-android: fix tenderloin’s boot; Move initrd RDEPENDS from ANDROID_EXTRA_INITRAMFS_IMAGE_INSTALL to initramfs-boot-android recipe; put .firstboot_done in a rw folder; split halium and generic version; tenderloin: mount /boot as ro; tenderloin: use correct folder for media data initramfs-scripts-android: improve init scripts; switch from RNDIS to CDC-ECM initramfs-scripts-halium: move Fix-userdata-mount-options.patch to the right directory; specify needs through RDEPENDS initrdscripts: fix tenderloin initial data (wallpaper) jemalloc: Switch to OSE repo kernel.bbclass: drop backported bbclass; remove backported bbclass; import from oe-core/pyro and backport one fix from oe-core/rocko kernel: tenderloin, mako, hammerhead, onyx bump SRCREV for GCC8 kernel_android, android-kernel-bootimg: use pkg_postinst_ontarget kernel_android.bbclass: fix path to the KERNEL_DEVICETREE; use ${KERNEL_PACKAGE_NAME}-image instead of kernel-image kernel_android: update for new KERNEL_* variables from oe-core; use the bbclass again keymanager: bump SRCREV kf5bluezqt-mer: set QT.BluezQt.module to fix compatibility with Qt 5.12 layer.conf: Update to warrior release name series leveldb: move bbappend to the matching directory leveldb-tl: downgrade to gcc-4.7 branch; provide native version libbson: Bump to latest upstream release libcamera: introduce recipe libdrm: add vboxvideo to tested modules; update the patch to apply for 2.4.96 libglibutil: fix LICENSE and LIC_FILES_CHKSUM libhybris, wayland: use wayland-egl from libhybris again libhybris: bump SRCREV and resolve the review comments; fix build with glibc-2.26; fix mido build flags; fix tenderloin build flags; provide also virtual/mesa and set PREFERRED_PROVIDER for all android devices; refresh patch; remove the already applied patch from SRC_URI; restrict COMPATIBLE_MACHINE to halium MACHINEs; use older SRCREV for tenderloin; don’t install wayland-egl; drop SRCREV libpalmsocket: fix build with openssl-1.1.1 libpbnjson: restore PV and OECMAKE_GENERATOR fix libpng: Bump to 1.6.37 librolegen: Add DEPENDS; Switch to OSE version + patches libsandbox: Migrate from OWO to OSE libsensmon: blacklist due to newer vala incompatibility libshr-glib: blacklist because of random failures libvpx: enable thumb to work around issue with -halium appended to TUNE_PKGARCH linunx-lg-mako: bump SRCREV linux-: don’t use ANDROID_BOOTIMG_CMDLINE for built-in kernel cmdline linux-{oneplus-onyx,lg-mako}: fix branch parameter linux-hp-tenderloin: bump SRCREV; use a 3.4 kernel linux-lg-{mako,hammerhead},linux-hp-tenderloin: backport 2 changes to fix build with gcc8 linux-lg-hammerhead: bump SRCREV; fix some minor defconfig values linux-lg-mako: send patches upstream and bump SRCREV; switch to old ubp-5.1 branch with just 1 fix for gcc-8 from cm-14.1 branch linux-oneplus-onyx: switch to old cm-14.1-los branch with just 1 fix for gcc-8 from luneos/cm-14.1-wip branch linux-xiaomi-rosy: bump SRCREV linux-xiaomi-tissot: bump SRCREV linux-yocto: add own defconfig; backport 5.0 from master and switch from linux-yocto-dev; drop backported fixes for compatibility with older Yocto; enable few more drm drivers; squashfs: add squash kernel module for anbox; use own virtio.cfg and reinclude kernel-module-virtio-gpu as a module linux-yocto-dev: add bbappend also for -dev version; enable vboxguest in the kernel and blacklist vboxguestdrivers again lsb: rename bbappend to match any version luna-applauncher: JustType: use a relative margin for main field (got broken after Qt 5.12.5 upgrade) luna-appmanager: Bump SRCREV; fix LS2 for webOS-OSE luna-downloadmgr, applicationinstallerutility: Add recipes luna-downloadmgr: Drop MACHINE specific configuration luna-next: Bump SRCREV; LS2 fix for webOS-OSE luna-next-cardshell: bump SRCREV; merge webosose branch to master luna-next-conf: fix possible conflict between evdevtouch and evdevkeyboard; fix VBoxTouch parameters for qemu; rosy: give input devices to evdevkeyboard; update VBoxTouch params and enable input and cursor; use drm+eglfs_kms for qemux86 luna-prefs-data.bb: Fix Lune OS name to LuneOS luna-qml-launcher: fix LS2 for webOS-OSE luna-service2: bump SRCREV; re-enable default LS2 security policy; remove webos_machine_impl_dep inherit imported from OSE luna-service2-security-conf: Switch to own fork luna-sysmgr: explicitely put RDEPENDS on powerd; Fix branch; fix LS2 for webOS-OSE luna-sysmgr-common: Bump SRCREV luna-sysmgr-conf, nyx-conf, nyx-modules, luna-next-conf: add support for raspberrypi4(-64) luna-sysservice, nodejs-module-webos-sysbus, nyx-utils, luna-service2, nyx-lib, pmloglib, pmloglib-private: Bump SRCREV luna-sysservice: Add back dropped PV; bump SRCREV; fix LS2 for webOS-OSE luna-systemui: Bump SRCREV luna-webappmanager: bump SRCREV; fix LS2 for webOS-OSE luneos.inc: drop kernel-module-virtio-gpu; enable image-buildinfo; exclude DATETIME from IMAGE_NAME, KERNEL_IMAGE_BASE_NAME, MODULE_IMAGE_BASE_NAME vardeps; include all default WARN_QA in ERROR_QA; replace uvesafb with vboxvideo; set WEBOS_TARGET_MACHINE_IMPL only in webos_machine_impl_dep; simplify PREMIRROR configuration; use linux-yocto-dev also for qemux86-64; use new oe-core variable IMAGE_VERSION_SUFFIX luneos: add rpi-sdimg.gz IMAGE_FSTYPE; reinclude luneos-recipe-blacklist-world.inc and update it for Yocto 2.7 Warrior; use linux-yocto-dev for qemux86 luneos_image.bbclass: remove the webos_swap_hook function luneos-{package,emulator-appliance}.inc: remove extra dash in filenames luneos-components: bump SRCREV and switch to qt-5.12 branch luneos-dev-image, luneui-example-image: drop mesa luneos-dev-image: add libdrm-tests; add more packages for testing luneos-emulator.ovf: move to qemux86 subdirectory and restrict to qemux86; refresh to ovf-2.0 format with VirtualBox-6.0.8; update OSType for qemux86-64 luneos-emulator-appliance.inc: include ${IMAGE_NAME_SUFFIX} in source VMDK filename; use pigz-native instead of zip-native; switch from default VBoxVGA to VBoxSVGA luneos-image: add WKS with syslinux config file without serial luneos-package.inc: bump android-update-package SRCREV; fix SRCREV; include ${IMAGE_NAME_SUFFIX} in source rootfs filename; work around tar being killed by OOMK; work around tar being killed by OOMK even harder luneos-preferred-providers.inc: remove VIRTUAL-RUNTIME_bash; use busybox as a provider for bash and stat luneos-preferred-versions.inc: downgrade gcc from default 8 to 7 luneos-recipe-blacklist-world.inc: blacklist remmina; use weak assignment luneui-example: add emulator-appliance and android package images luneui-example-image, packagegroup-luneos-extended: add Anbox for qemux86-64 luneui-example-image,luneos-dev-image: include glmark2 only for qemuall lxc: ignore stringop-overflow= errors with gcc8 make, hammerhead, tenderloin: use mesa-gl as virtual/mesa provider; use kernel sources from shr-distribution/linux.git and fix build with gcc-7; use our Halium image mako, hammerhead: Use upstream kernels which now have our patches included mako: Fix the kernel build maliit-framework-qt5: set QT_QPA_PLATFORM=wayland mediaindexer: Bump SRCREV; Switch back to master branch mesa: backport 19.0.5 and mesa-demos 8.4.0 from oe-core; drop backported PROVIDES; enable gallium only for target builds; update old recipe; use latest mesa from oe-core mesa-gl: remove ${includedir}/KHR/khrplatform.h when using libhybris meson: override 0003_native-bindir patch with a fixed version; drop backported fix, now in oe-core revision we’re using messaging-accounts: Bump SRCREV meta-: add LAYERSERIES_COMPAT to layer.conf files meta-: add LAYERSERIES_COMPAT to layer.conf files; set PREFERRED_PROVIDER for libgl and libgbm for all android devices meta-{asus,hp,huawei,lg,motorola,oneplus,xiaomi}: remove fstab overload meta-acer, meta-asus, meta-aurora, meta-fso, meta-geeksphone, meta-htc, meta-nokia meta-openmoko, meta-osmocombb, meta-palm, meta-samsung, meta-shr-distro, meta-shr: Remove unsupported layers meta-android, meta-hp: respect IMAGE_NAME_SUFFIX variable meta-android: add FREESMARTPHONE_GIT; initramfs-android-recovery: add inc; remove leftover from android-tools removal; use separate PACKAGE_DIR for Halium-based packages meta-android-halium.inc: add halium OVERRIDE; blacklist virglrenderer, cogl-1.0, clutter-1.0, mx-1.0, clutter-gst-3.0, clutter-gtk-1.0 meta-hp: initramfs-boot-android: move Fix-userdata-mount-options.patch to meta-webos-ports; migrate tenderloin to use Halium’s init meta-luneos-backports-2.8: add layer for backports from Yocto 2.8 Zeus; Add pidgin 2.13 meta-motorola: Athene, use our own fork for now.; Fixes for athene target to make build work; Initial work for athene target meta-oneplus: Fixes for onyx target to make build work; Initial work on layer; linux-oneplus-onyx: Use herrie82 branch pending upstream merge; Update kernel for onyx (OnePlus X) meta-qt5-compat: remove meta-shr, meta-fso: remove blacklisted recipes meta-smartphone: Add meta-huawei layer with Angler target; udev-extraconf: Uniform naming scheme for device udev rules and update udev rules meta-webos-ports: Add pinephone machine meta-xiaomi: add initial support for rosy (Redmi 5); Further updates to make things work; Get image for Tissot building; Initial work for Xiaomi A1 (tissot); Initial work on layer; linux-xiaomi-mido: Fix incorrect RAM_BASE addresses; Mido enable WLAN as module; mido fix persist partition number in fstab; mido use correct wlan module name; rosy minor fixes; 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 mmsd: Bump SRCREV mobile-broadband-provider-info: Bump SRCREV module-base.bbclass: import from oe-core/pyro and backport the fix to support newer kernels; refresh from rocko module-base: remove backported bbclass mojo: Switch to webOS-ports/webOS-OSE branches mojomail, pmcertificatemgr: bump SRCREV mojoservicelauncher: bump SRCREV; temporary drop nodejs-module-webos-dynaload and nodejs-module-webos-sysbus mpeg2dec: ignore textrel QA issue in libmpeg2 mtp-server: bump SRCREV; fix build with glog-0.3.5 nemo-qml-plugin-dbus: Bump to latest from upstream node-gyp-native: upgrade to 4.0.0+git; fix branch parameter nodejs-enyo-dev-native: Bump SRCREV nodejs-module-webos-{dynaload,sysbus}: bump SRCREV nodejs-module-webos-dynaload: Move to OSE version nodejs-module-webos-pmlog: Add fix from upstream OSE nodejs-module-webos-service: Add recipe from OSE nodejs-module-webos-sysbus: Bump SRCREV; Fix installation of role files.; Fix work directory; Migrate to webOS OSE version; restore old security schema novacomd: Remove upstart init script; Switch to OSE version ntp: Add an empty ntp-kod file numptyphysics: fix file-rdeps QA nyx-conf: add pinephone power key config nyx-modules, nyx-conf: Fix pinephone setup nyx-modules: bump SRCREV; Changes for new nyx modules from OSE;’disable security and security2 modules and return to the image; fix build for tenderloin; fix rosy’s cmake; fixes for webOS-OSE rebase; qemux86(-64) update copyright and specify modules to build; reintroduce nyx-modules-hybris for Halium based targets; toro & toroplus: Update copyright & hybris modules; Update copyright nyx-modules-hybris: bump SRCREV for nyx-lib compatibility fixes ofono: Drop patches that are no longer used.; Update to latest from Mer; use more recent version omhacks: blacklist openssl: update openssl.cnf u-a configuration openssl, gtest, leveldb: drop EXTENDPRAUTO openssl10: remove the bbappend and blacklist instead opkg: Rename bbappend to match new version from oe-core packagegroup: temoporary drop certmgrd, pmcertificatemgr, mojomail-imap, mojomail-pop, mojomail-smtp, nyx-modules packagegroup-luneos-extended: add messwerk app; Drop downloadmanager in favor of luna-downloadmgr; include DISTRO_EXTRA_RDEPENDS to install necessary kernel modules; include rng-tools for qemu*; re-enable nyx-modules-hybris; replace wireless-tools with iw; Add event-monitor & event-monitor-network PATCH] athene, mido, onyx: Fix display size and add ANDROID_HEADERS_DEFINES pdm & pdm-plugin: Add various bits to build & include in images. phonesim: Bump to 1.21 pidgin, leveldb-tl, extra-cmake-modules, pmloglib-private: don’t rdepend on ${PN} from ${PN}-dev pidgin: Make bbappend version independent; remove the backported recipes; update purple-OE-branding-25.patch to apply cleanly; Update to 2.13; use backported recipes pidgin-sipe: Update to latest release from upstream pmloglib: Add back PV pmloglib-private: Add back PV powerstat: Update to latest upstream properties-cpp: add sha265sum, fix runtime dependencies pulseaudio: rename bbappend to apply on new version from oe-core; update patches to apply on 11.1 version pulseaudio-modules-droid: adapt folders for PulseAudio 11.1; bump SRCREV for 12.2 compatibility; update PULSEAUDIO_VERSION to 12.2 purple-skypeweb: Update to latest release from upstream python-tz: Bump to 2019.1 qemu: don’t enable spice for target; drop virglrenderer from target qemu as well; enable sdl and virtfs as well; enable virglrenderer spice libusb usb-redir gtk+ qemux86: use wic.vmdk qt5: refresh the patches for 5.12.3 version qt5-plugin-generic-vboxtouch: bump SRCREV; switch to new version from Tofee qt5-qpa-hwcomposer-plugin: bump SRCREV and fix build; fix compatibility with qtbase 5.12; remove unneeded patch qtbase: allow to easily select different QPA; update PACKAGECONFIG xkbcommon-evdev -> xkbcommon qtlocation-luneos-plugin: replace qtlocation patch; Update plugins dir and PV qtvideo-node, org.webosports.app.camera: fix PV qtwayland: don’t use wayland-brcm; drop drm-egl-server and libhybris-egl-server PACKAGECONFIGs; fix QWaylandShellPrivate inheritance; Fix window properties; refresh patches for 5.12; fix the last patch filename in SRC_URI; update patches for 5.12.5 qtwebengine: enable wayland-brcm for rpi, drm-egl-server for qemuall and libhybris-egl-server for the rest; fix 0001-WebContents-provide-additional-features-from-window..patch; fix patch directory; fix Sync call patch; refresh patches for 5.12; refresh patches for 5.12.5 raspberrypi4-64: fix TUNE_PKGARCH_64 rdxd: Drop stub and add the real thing.; Add missing PROVIDES README: update to depend on master branches Remove AOL & ICQ protocol plugins Revert \”hammerhead: temporarily disable gobject introspection\” Revert \”meta-hp: initramfs-boot-android: move Fix-userdata-mount-options.patch to meta-webos-ports\” SANITY_TESTED_DISTROS: drop ubuntu-16.04 sdl2-opengles-test: build only sdl2_opengles2_test for all rpi MACHINEs; Fix typo in license file.; Switch to new repo and update to latest version sensorfw: bump SRCREV and make it more generic; fix orientation matrix for pinephone serviceinstaller: Switch to OSE version + our patch shadow-sysroot: rename bbappend to match new version sleepd: add powerd as RDEPENDS snappy: import from OSE and add as a dependency to leveldb; use newer 1.1.7 version from meta-oe storaged: Add PV Switch from branch= to WEBOS_GIT_PARAM_BRANCH systemd: disable networkd and resolved.; fix boot for old kernels; fix build without resolved; rebase patches to apply on 237 version; rebase patches to apply on 241; update Disable-ProtectHome-and-ProtectSystem-for-old-kernel.patch to apply on 239 version; Update mmc patch; update persistent-storage-rule-mmc-partname.patch to apply on 234 version systemd-conf: disable key handling in logind.conf systemd-machine-units: regroup xiaomi identical service files; fix bluetooth for hammerhead; fix bluetooth for mako; mido: fix Bluetooth; rosy: fix Bluetooth; rosy: fix wlan module loading; tissot: fix Bluetooth systemd-serialgetty: disable SERIAL_CONSOLES on LuneOS’s qemu; drop weird bbappend tzdata: rename bbappend to apply on renamed recipe ubx-utils: fix file-rdeps QA udev-extraconf: override automount.rules with empty rules file; tissot, rosy: add touchscreen0 rule unused: remove long unused recipes and bbclasses uriparser: Upgrade to 0.9.3 Various components: Move back to webOS-ports fork Various fixes for systemd vboxguestdrivers: backport 5.2.22 from meta-oe; unblacklist but install only vboxguest and vboxsf modules VoiceCall: Bump SRCREV & drop patch; Bump version to latest from upstream and refresh patches; Drop patches since our changes are merged upstream; fix DEVICELOCK handling wayland: limit do_install_append only for target webos_{lttng,pmlog_config}.bbclass: move to the right layer webos_configure_manifest.bbclass, webos_system_bus.bbclass: replace some warnings with notes webos_configure_manifest.bbclass: move to the right layer webos_nyx_module_provider.bbclass: enable NYXMOD_OW_MSMMTP by default webos_test_provider.bbclass: move to meta-luneui webos-connman-adapter: bump SRCREV webos-initscripts, org.webosports.cdav, app-services, bootd, com.webos.service.pdm, db8, enyo-1.0, mojoservice-framework, mojomail: Bump SRCREV webos-initscripts.bb: Fix inherit webos-initscripts: don’t include systemd-machine-units in sstate signature; fix startup sequence for webOS-OSE; Fix whitespace issues webos-keyboard: fix LS2 for webOS-OSE; Bump SRCREV wifi-module-load: fix sleep call in systemd service luneos-components: Update Qt version to 5.12.5; Add stub for ieee8021x wifi network 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, Hammerhead and Tissot remain our focus for now, but the emulators, Mako and Mido 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! Related posts: LuneOS October Stable Release: Caffè Latte LuneOS February Stable Release: Chai Latte LuneOS July Stable Release: Cortado View the full article

Happy Halloween! The long wait is finally over #LuneOS and #webOS fans! We’re back with a new release called “Eggnog Latte” which is a milestone in terms of developments and paves the way forward! So you’re wondering what we’ve been up to since our previous stable release at the end of last year? We have done many major upgrades to a large number of components of our stack being: Migration of Open webOS to webOS OSE components. We are almost half way there in terms of the migration of old Open webOS components to their webOS OSE replacements. This was a monumental task due to the fact that webOS OSE code was released without any history. So every component needed to be analyzed to understand what was changed in the years of development inside of LG Electronics. Our custom changes needed to be re-assessed and re-implemented into the new components where applicable. A change of direction in certain aspects in terms of architecture made the whole exercise even more complicated. We do however believe that we’re in a good state now in terms of migration. There are still quite some components to migrate and we’ll get through that in the next releases. Qt: We migrated from Qt 5.11.3 to Qt 5.12.5 which included an update for Chromium from 65 to 69 amongst other improvements. Yocto upgrade: We upgraded from the no longer supported Yocto Pyro release, via the intermediary Rocko, Sumo and Thud releases to the latest Yocto release called Warrior. We have been working closely together with the Halium, Mer and PostMarketOS projects and have made further integrations between LuneOS and the various projects 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 and more devices. We have also worked on support for devices which use a mainline kernel instead of an Android based kernel. As you might have seen, we have been working on support for the Pinephone which uses a mainline kernel. We also have been testing with the Nexus 5 (hammerhead) using a mainline kernel. All our setup has now been adjusted so we can work with both Android based targets and kernels as well as mainline kernels. LG has a very clear vision in mind for webOS OSE as can be read on their blog posts. Since the initial release of webOS OSE 1.0 in March last year, there has been a total of 11 releases of webOS OSE already with a lot of improvements and added features added with each release. This month LG has released webOS OSE 2.0.0 with a lot of new features and also a new roadmap. The following items on our to-do list will be where we focus next: Migration of remaining Open webOS components to the newer webOS OSE components and assess where further synergies could be achieved. Migrate to Yocto Zeus release. Update to Qt 5.13. Migrate Nexus 5 (hammerhead) to use mainline kernel. Finalize port for Pinephone. Work on support for Halium 8/9/10 in order to support newer targets. 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. Telephony not working on the Xiaomi Android 7 based targets. We have found the root cause, but haven’t been able to solve it yet. Virtual Keyboard sometimes randomly doesn’t appear. Changelog Applications: Preware IPKG Service: use postinst_ontarget Tweaks: Fix for LS2 from webOS OSE Camera: Remove RDEPEND on libhybris FirstUse: Fix for LS2 from webOS OSE Maps: Fix Google API calls Messwerk: Add testing app for various sensors Phone: Fix calling Settings: Fix displaying of device information, fix compatibility with LS2 from webOS OSE Update: Fix parsing of JSON files with update information. CDav: Fix issues after migration to webOS OSE User Interface: Various minor fixes for status bar & indicators in emulators System Level: Yocto upgrade from 2.3 Pyro to 2.7 Warrior Qt upgrade from 5.11 to 5.12 Pinephone support added activitymanager: RDEPENDS on bootd add meta-qt5-compat layer Add VIRTUAL-RUNTIME_android-initramfs-scripts variable in machines conf alsa-lib: update the patches for 1.1.8 alsa-utils: Rename bbappend to match new version from oe-core anbox, ashmem, binder: bump SRCREV; add COMPATIBLE_MACHINE restriction; Add elfutils to DEPENDS to solve QA issue; Add some RDEPENDS,RRECOMMENDS; fix build with boost 1.71.1; fix parallel build issue; restrict COMPATIBLE_MACHINE a bit more anbox-data: add recipe for retrieving android image 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: use API 22, patched to match tenderloin specific content; fix patches to match Halium’s android-kernel-bootimg: append DTB when specified; dedicated recipe for creating boot.img; minimal support for A/B partitions android-property-service, mtp-server, pulseaudio-modules-droid, qtubuntu-camera, qtvideo-node, qt5-qpa-hwcomposer-plugin, qtscenegraph-adaptation, qtsensors-sensorfw-plugin sensorfw, nyx-modules-hybris, org.webosports.app.camera: restrict to halium MACHINES; add dependency on virtual/android-headers 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; only start after main partitions are mounted; 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-: bump to 20180311 Halium build; skip already-stripped QA android-system-image,base-files: use system.img directly android-system-image: Add symbolic link for wifi; Bump Halium images; bump mako,tenderloin,hammerhead; Change wop into luneos; convert the sparse image if needed; create /userdata; make \”symbols\” directory optional; Update halium bits to halium version numbers android-system-image-athene,onyx,mido,angler: bump PV android-system-image-mako: fix install; fix install script; fix typo android-system-image-rosy: use build from webos-ports android-system-image-tenderloin: bump PV; Fix checksums; Update Android image; Use a Haloum 5.1 based Android build android-system-image-tissot: bump PV; Bump PV to fix adb; Bump PV to kill qseeproxydaemon on Android side; bump to 20180302-18 android-tools: move the changes to meta-oe android-tools: remove android-tools-conf: provide whole android-gadget-setup instead of patching it in do_install; use backported recipe angler, hammerhead, mako, athene, onyx, mido, rosy, tissot: stop building ext4 images by default angler,athene,onyx,mako,hammerhead: systemd-machine-units: add rfkill unblock wifi app-services, configurator: Bump SRCREV; fix LS2 for webOS-OSE ashmem, binder: move udev rules to kernel-module--linux package and empty PN base-files,android-system: Android partitions are now mounted by Halium’s initrd base-files: add /system/lib64 in LD_LIBRARY_PATH bootd: introduce recipe from webOS-OSE; Fix systemd service file busybox: also build telnetd module; also create by-label entries with mdev; mdev: use /dev/disk/by-partlabel instead of by-partname; mdev-partname.sh, mdev.conf: drop trailing spaces; mdev-partname.sh: remove probablly unnecessary ACTION assignment; mdev-partname.sh: use 4 spaces for indentation instead of mix of tabs and spaces; provide busybox-mdev with custom partname symlinks; use 4 spaces for indentation instead of mix of tabs and spaces and BPN in FILESEXTRAPATHS cmake-modules-webos-native: Add back PV; add missing quote; Bump PV com.webos.service.pdm: Remove inherit webos_machine_impl_dep configurator: Move to webOS OSE version; Bump SRCREV connman: move PACKAGECONFIG modification to .bbappend, remove dependency on xl2tp in signature; refresh patches to apply cleanly; update to v1.36 cpushareholder-stub, luna-sysmgr-ipc-messages, luna-webkit-api, rdx-utils-stub: inherit allarch before webos_cmake cpushareholder-stub: Migrate from OWO to OSE db8, filecache: Bump SRCREV, app-services: Bump SRCREV and cleanup recipe db8, nyx-modules: Minor fixes after OSE rebase db8: Add back dropped PV; Bump SRCREV and drop patch now merged in repo; cleanup a bit; fix db8-tests runtime depends; fix LS2 for webOS-OSE; Update to latest revision and remove references to com.webos.service.attachedstoragemanager dbus-cpp, process-cpp, properties-cpp: Switch to GitHub & latest commits dbus-cpp: fix compatiblity with boost 1.66.0 defaulttunes.inc: return accidentally dropped last line; use armv8a-crc-crypto for both raspberrypi[34]-64;use cortexa8thf-neon for currently supported 32bit arm MACHINEs;use different TUNE_PKGARCH_64 for raspberrypi3-64 MACHINE directfb: Drop .bbappend distro: luneos: switch release name to Eggnog Latte downloadmanager: Remove recipe event-monitor, event-monitor-network: Add recipes from OSE exiv2: Update to 0.27.1 extra-cmake-modules: Bump to latest from upstream filecache: Bump SRCREV Fix meson bbappend Fixup line endings funyahoo-plusplus: Update to latest from upstream Further work on webOS OSE migration; Further changes for webOS OSE; Further migration for webOS OSE gcc: restore gcc-7.3 from Yocto 2.6 Thud geoclue: backport gtk-doc.bbclass changes from Yocto 2.8 Zeus to make GTKDOC_MESON_OPTION work in Yocto 2.7 Warrior; Fix typo;fix unknown-configure-option QA issue; Rename .bbappend to be generic; Update to 2.5.3; use backported recipe; Add to meta-webos-ports for fixes & upgrade glib-2.0: Rename bbappend to match new version from oe-core; update 0001-gdbus-codegen-replace-plus-also-with-underscore.patch to apply on 2.58.0 version; update patch to apply on 2.54.2 version; add work around for broken ld-2.29.so when gold is used; drop bbappend; export LDFLAGS glm: use 0.9.9.3 version from meta-oe glmark2: disable wayland-gles2 GnuTLS: Fix missing system trust gstreamer1.0-plugins-base: disable egl gtest: don’t rdepend on ${PN} from ${PN}-dev; export LDFLAGS hammerhead kernel: delay wifi init hammerhead, mako, tenderloin: Use Halium image built with Ports repos; use WOP builds of Halium hammerhead, mako: Add NFC as machine feature hammerhead.conf: use initramfs-scripts-halium hammerhead: temporarily disable gobject introspection https-everywhere: Update to latest from upstream hunspell-dictionaries: Update to latest from upstream; use backported recipe icyque: Add recipe Ignore generated pycache directory iio-sensor-proxy: introduce recipe imaccountvalidator, activitymanager, db8, filecache, sleepd, luna-service2: Bump SRCREV imaccountvalidator, imlibpurpleservice: Add icyque plugin imlibpurpleservice, org.webosports.service.messaging, webos-telephonyd, app-services, core-apps, nodejs-module-webos-sysbus: Bump SRCREV Include android-kernel-bootimg for each MACHINE that needs it Initial work for webOS OSE migration initramfs-android-image: make it possible to add content; make sure that ANDROID_EXTRA_INITRAMFS_IMAGE_INSTALL is expanded initramfs-android-recovery-tissot: skip file-rdeps QA as well initramfs-boot-android: cosmetics; disable busybox extreme symlink checks; fix image identification for rootfs on partition; import Fix-userdata-mount-options.patch from meta-hp; init.sh: be less verbose for initial user data copy; mount /dev/pts for cases when enable_adb is used; put .firstboot_done in a rw folder; reset uevent_help when stopping mdev; split halium and generic version; use mdev instead of udev initramfs-boot-android: fix tenderloin’s boot; Move initrd RDEPENDS from ANDROID_EXTRA_INITRAMFS_IMAGE_INSTALL to initramfs-boot-android recipe; put .firstboot_done in a rw folder; split halium and generic version; tenderloin: mount /boot as ro; tenderloin: use correct folder for media data initramfs-scripts-android: improve init scripts; switch from RNDIS to CDC-ECM initramfs-scripts-halium: move Fix-userdata-mount-options.patch to the right directory; specify needs through RDEPENDS initrdscripts: fix tenderloin initial data (wallpaper) jemalloc: Switch to OSE repo kernel.bbclass: drop backported bbclass; remove backported bbclass; import from oe-core/pyro and backport one fix from oe-core/rocko kernel: tenderloin, mako, hammerhead, onyx bump SRCREV for GCC8 kernel_android, android-kernel-bootimg: use pkg_postinst_ontarget kernel_android.bbclass: fix path to the KERNEL_DEVICETREE; use ${KERNEL_PACKAGE_NAME}-image instead of kernel-image kernel_android: update for new KERNEL_* variables from oe-core; use the bbclass again keymanager: bump SRCREV kf5bluezqt-mer: set QT.BluezQt.module to fix compatibility with Qt 5.12 layer.conf: Update to warrior release name series leveldb: move bbappend to the matching directory leveldb-tl: downgrade to gcc-4.7 branch; provide native version libbson: Bump to latest upstream release libcamera: introduce recipe libdrm: add vboxvideo to tested modules; update the patch to apply for 2.4.96 libglibutil: fix LICENSE and LIC_FILES_CHKSUM libhybris, wayland: use wayland-egl from libhybris again libhybris: bump SRCREV and resolve the review comments; fix build with glibc-2.26; fix mido build flags; fix tenderloin build flags; provide also virtual/mesa and set PREFERRED_PROVIDER for all android devices; refresh patch; remove the already applied patch from SRC_URI; restrict COMPATIBLE_MACHINE to halium MACHINEs; use older SRCREV for tenderloin; don’t install wayland-egl; drop SRCREV libpalmsocket: fix build with openssl-1.1.1 libpbnjson: restore PV and OECMAKE_GENERATOR fix libpng: Bump to 1.6.37 librolegen: Add DEPENDS; Switch to OSE version + patches libsandbox: Migrate from OWO to OSE libsensmon: blacklist due to newer vala incompatibility libshr-glib: blacklist because of random failures libvpx: enable thumb to work around issue with -halium appended to TUNE_PKGARCH linunx-lg-mako: bump SRCREV linux-: don’t use ANDROID_BOOTIMG_CMDLINE for built-in kernel cmdline linux-{oneplus-onyx,lg-mako}: fix branch parameter linux-hp-tenderloin: bump SRCREV; use a 3.4 kernel linux-lg-{mako,hammerhead},linux-hp-tenderloin: backport 2 changes to fix build with gcc8 linux-lg-hammerhead: bump SRCREV; fix some minor defconfig values linux-lg-mako: send patches upstream and bump SRCREV; switch to old ubp-5.1 branch with just 1 fix for gcc-8 from cm-14.1 branch linux-oneplus-onyx: switch to old cm-14.1-los branch with just 1 fix for gcc-8 from luneos/cm-14.1-wip branch linux-xiaomi-rosy: bump SRCREV linux-xiaomi-tissot: bump SRCREV linux-yocto: add own defconfig; backport 5.0 from master and switch from linux-yocto-dev; drop backported fixes for compatibility with older Yocto; enable few more drm drivers; squashfs: add squash kernel module for anbox; use own virtio.cfg and reinclude kernel-module-virtio-gpu as a module linux-yocto-dev: add bbappend also for -dev version; enable vboxguest in the kernel and blacklist vboxguestdrivers again lsb: rename bbappend to match any version luna-applauncher: JustType: use a relative margin for main field (got broken after Qt 5.12.5 upgrade) luna-appmanager: Bump SRCREV; fix LS2 for webOS-OSE luna-downloadmgr, applicationinstallerutility: Add recipes luna-downloadmgr: Drop MACHINE specific configuration luna-next: Bump SRCREV; LS2 fix for webOS-OSE luna-next-cardshell: bump SRCREV; merge webosose branch to master luna-next-conf: fix possible conflict between evdevtouch and evdevkeyboard; fix VBoxTouch parameters for qemu; rosy: give input devices to evdevkeyboard; update VBoxTouch params and enable input and cursor; use drm+eglfs_kms for qemux86 luna-prefs-data.bb: Fix Lune OS name to LuneOS luna-qml-launcher: fix LS2 for webOS-OSE luna-service2: bump SRCREV; re-enable default LS2 security policy; remove webos_machine_impl_dep inherit imported from OSE luna-service2-security-conf: Switch to own fork luna-sysmgr: explicitely put RDEPENDS on powerd; Fix branch; fix LS2 for webOS-OSE luna-sysmgr-common: Bump SRCREV luna-sysmgr-conf, nyx-conf, nyx-modules, luna-next-conf: add support for raspberrypi4(-64) luna-sysservice, nodejs-module-webos-sysbus, nyx-utils, luna-service2, nyx-lib, pmloglib, pmloglib-private: Bump SRCREV luna-sysservice: Add back dropped PV; bump SRCREV; fix LS2 for webOS-OSE luna-systemui: Bump SRCREV luna-webappmanager: bump SRCREV; fix LS2 for webOS-OSE luneos.inc: drop kernel-module-virtio-gpu; enable image-buildinfo; exclude DATETIME from IMAGE_NAME, KERNEL_IMAGE_BASE_NAME, MODULE_IMAGE_BASE_NAME vardeps; include all default WARN_QA in ERROR_QA; replace uvesafb with vboxvideo; set WEBOS_TARGET_MACHINE_IMPL only in webos_machine_impl_dep; simplify PREMIRROR configuration; use linux-yocto-dev also for qemux86-64; use new oe-core variable IMAGE_VERSION_SUFFIX luneos: add rpi-sdimg.gz IMAGE_FSTYPE; reinclude luneos-recipe-blacklist-world.inc and update it for Yocto 2.7 Warrior; use linux-yocto-dev for qemux86 luneos_image.bbclass: remove the webos_swap_hook function luneos-{package,emulator-appliance}.inc: remove extra dash in filenames luneos-components: bump SRCREV and switch to qt-5.12 branch luneos-dev-image, luneui-example-image: drop mesa luneos-dev-image: add libdrm-tests; add more packages for testing luneos-emulator.ovf: move to qemux86 subdirectory and restrict to qemux86; refresh to ovf-2.0 format with VirtualBox-6.0.8; update OSType for qemux86-64 luneos-emulator-appliance.inc: include ${IMAGE_NAME_SUFFIX} in source VMDK filename; use pigz-native instead of zip-native; switch from default VBoxVGA to VBoxSVGA luneos-image: add WKS with syslinux config file without serial luneos-package.inc: bump android-update-package SRCREV; fix SRCREV; include ${IMAGE_NAME_SUFFIX} in source rootfs filename; work around tar being killed by OOMK; work around tar being killed by OOMK even harder luneos-preferred-providers.inc: remove VIRTUAL-RUNTIME_bash; use busybox as a provider for bash and stat luneos-preferred-versions.inc: downgrade gcc from default 8 to 7 luneos-recipe-blacklist-world.inc: blacklist remmina; use weak assignment luneui-example: add emulator-appliance and android package images luneui-example-image, packagegroup-luneos-extended: add Anbox for qemux86-64 luneui-example-image,luneos-dev-image: include glmark2 only for qemuall lxc: ignore stringop-overflow= errors with gcc8 make, hammerhead, tenderloin: use mesa-gl as virtual/mesa provider; use kernel sources from shr-distribution/linux.git and fix build with gcc-7; use our Halium image mako, hammerhead: Use upstream kernels which now have our patches included mako: Fix the kernel build maliit-framework-qt5: set QT_QPA_PLATFORM=wayland mediaindexer: Bump SRCREV; Switch back to master branch mesa: backport 19.0.5 and mesa-demos 8.4.0 from oe-core; drop backported PROVIDES; enable gallium only for target builds; update old recipe; use latest mesa from oe-core mesa-gl: remove ${includedir}/KHR/khrplatform.h when using libhybris meson: override 0003_native-bindir patch with a fixed version; drop backported fix, now in oe-core revision we’re using messaging-accounts: Bump SRCREV meta-: add LAYERSERIES_COMPAT to layer.conf files meta-: add LAYERSERIES_COMPAT to layer.conf files; set PREFERRED_PROVIDER for libgl and libgbm for all android devices meta-{asus,hp,huawei,lg,motorola,oneplus,xiaomi}: remove fstab overload meta-acer, meta-asus, meta-aurora, meta-fso, meta-geeksphone, meta-htc, meta-nokia meta-openmoko, meta-osmocombb, meta-palm, meta-samsung, meta-shr-distro, meta-shr: Remove unsupported layers meta-android, meta-hp: respect IMAGE_NAME_SUFFIX variable meta-android: add FREESMARTPHONE_GIT; initramfs-android-recovery: add inc; remove leftover from android-tools removal; use separate PACKAGE_DIR for Halium-based packages meta-android-halium.inc: add halium OVERRIDE; blacklist virglrenderer, cogl-1.0, clutter-1.0, mx-1.0, clutter-gst-3.0, clutter-gtk-1.0 meta-hp: initramfs-boot-android: move Fix-userdata-mount-options.patch to meta-webos-ports; migrate tenderloin to use Halium’s init meta-luneos-backports-2.8: add layer for backports from Yocto 2.8 Zeus; Add pidgin 2.13 meta-motorola: Athene, use our own fork for now.; Fixes for athene target to make build work; Initial work for athene target meta-oneplus: Fixes for onyx target to make build work; Initial work on layer; linux-oneplus-onyx: Use herrie82 branch pending upstream merge; Update kernel for onyx (OnePlus X) meta-qt5-compat: remove meta-shr, meta-fso: remove blacklisted recipes meta-smartphone: Add meta-huawei layer with Angler target; udev-extraconf: Uniform naming scheme for device udev rules and update udev rules meta-webos-ports: Add pinephone machine meta-xiaomi: add initial support for rosy (Redmi 5); Further updates to make things work; Get image for Tissot building; Initial work for Xiaomi A1 (tissot); Initial work on layer; linux-xiaomi-mido: Fix incorrect RAM_BASE addresses; Mido enable WLAN as module; mido fix persist partition number in fstab; mido use correct wlan module name; rosy minor fixes; 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 mmsd: Bump SRCREV mobile-broadband-provider-info: Bump SRCREV module-base.bbclass: import from oe-core/pyro and backport the fix to support newer kernels; refresh from rocko module-base: remove backported bbclass mojo: Switch to webOS-ports/webOS-OSE branches mojomail, pmcertificatemgr: bump SRCREV mojoservicelauncher: bump SRCREV; temporary drop nodejs-module-webos-dynaload and nodejs-module-webos-sysbus mpeg2dec: ignore textrel QA issue in libmpeg2 mtp-server: bump SRCREV; fix build with glog-0.3.5 nemo-qml-plugin-dbus: Bump to latest from upstream node-gyp-native: upgrade to 4.0.0+git; fix branch parameter nodejs-enyo-dev-native: Bump SRCREV nodejs-module-webos-{dynaload,sysbus}: bump SRCREV nodejs-module-webos-dynaload: Move to OSE version nodejs-module-webos-pmlog: Add fix from upstream OSE nodejs-module-webos-service: Add recipe from OSE nodejs-module-webos-sysbus: Bump SRCREV; Fix installation of role files.; Fix work directory; Migrate to webOS OSE version; restore old security schema novacomd: Remove upstart init script; Switch to OSE version ntp: Add an empty ntp-kod file numptyphysics: fix file-rdeps QA nyx-conf: add pinephone power key config nyx-modules, nyx-conf: Fix pinephone setup nyx-modules: bump SRCREV; Changes for new nyx modules from OSE;’disable security and security2 modules and return to the image; fix build for tenderloin; fix rosy’s cmake; fixes for webOS-OSE rebase; qemux86(-64) update copyright and specify modules to build; reintroduce nyx-modules-hybris for Halium based targets; toro & toroplus: Update copyright & hybris modules; Update copyright nyx-modules-hybris: bump SRCREV for nyx-lib compatibility fixes ofono: Drop patches that are no longer used.; Update to latest from Mer; use more recent version omhacks: blacklist openssl: update openssl.cnf u-a configuration openssl, gtest, leveldb: drop EXTENDPRAUTO openssl10: remove the bbappend and blacklist instead opkg: Rename bbappend to match new version from oe-core packagegroup: temoporary drop certmgrd, pmcertificatemgr, mojomail-imap, mojomail-pop, mojomail-smtp, nyx-modules packagegroup-luneos-extended: add messwerk app; Drop downloadmanager in favor of luna-downloadmgr; include DISTRO_EXTRA_RDEPENDS to install necessary kernel modules; include rng-tools for qemu*; re-enable nyx-modules-hybris; replace wireless-tools with iw; Add event-monitor & event-monitor-network PATCH] athene, mido, onyx: Fix display size and add ANDROID_HEADERS_DEFINES pdm & pdm-plugin: Add various bits to build & include in images. phonesim: Bump to 1.21 pidgin, leveldb-tl, extra-cmake-modules, pmloglib-private: don’t rdepend on ${PN} from ${PN}-dev pidgin: Make bbappend version independent; remove the backported recipes; update purple-OE-branding-25.patch to apply cleanly; Update to 2.13; use backported recipes pidgin-sipe: Update to latest release from upstream pmloglib: Add back PV pmloglib-private: Add back PV powerstat: Update to latest upstream properties-cpp: add sha265sum, fix runtime dependencies pulseaudio: rename bbappend to apply on new version from oe-core; update patches to apply on 11.1 version pulseaudio-modules-droid: adapt folders for PulseAudio 11.1; bump SRCREV for 12.2 compatibility; update PULSEAUDIO_VERSION to 12.2 purple-skypeweb: Update to latest release from upstream python-tz: Bump to 2019.1 qemu: don’t enable spice for target; drop virglrenderer from target qemu as well; enable sdl and virtfs as well; enable virglrenderer spice libusb usb-redir gtk+ qemux86: use wic.vmdk qt5: refresh the patches for 5.12.3 version qt5-plugin-generic-vboxtouch: bump SRCREV; switch to new version from Tofee qt5-qpa-hwcomposer-plugin: bump SRCREV and fix build; fix compatibility with qtbase 5.12; remove unneeded patch qtbase: allow to easily select different QPA; update PACKAGECONFIG xkbcommon-evdev -> xkbcommon qtlocation-luneos-plugin: replace qtlocation patch; Update plugins dir and PV qtvideo-node, org.webosports.app.camera: fix PV qtwayland: don’t use wayland-brcm; drop drm-egl-server and libhybris-egl-server PACKAGECONFIGs; fix QWaylandShellPrivate inheritance; Fix window properties; refresh patches for 5.12; fix the last patch filename in SRC_URI; update patches for 5.12.5 qtwebengine: enable wayland-brcm for rpi, drm-egl-server for qemuall and libhybris-egl-server for the rest; fix 0001-WebContents-provide-additional-features-from-window..patch; fix patch directory; fix Sync call patch; refresh patches for 5.12; refresh patches for 5.12.5 raspberrypi4-64: fix TUNE_PKGARCH_64 rdxd: Drop stub and add the real thing.; Add missing PROVIDES README: update to depend on master branches Remove AOL & ICQ protocol plugins Revert \”hammerhead: temporarily disable gobject introspection\” Revert \”meta-hp: initramfs-boot-android: move Fix-userdata-mount-options.patch to meta-webos-ports\” SANITY_TESTED_DISTROS: drop ubuntu-16.04 sdl2-opengles-test: build only sdl2_opengles2_test for all rpi MACHINEs; Fix typo in license file.; Switch to new repo and update to latest version sensorfw: bump SRCREV and make it more generic; fix orientation matrix for pinephone serviceinstaller: Switch to OSE version + our patch shadow-sysroot: rename bbappend to match new version sleepd: add powerd as RDEPENDS snappy: import from OSE and add as a dependency to leveldb; use newer 1.1.7 version from meta-oe storaged: Add PV Switch from branch= to WEBOS_GIT_PARAM_BRANCH systemd: disable networkd and resolved.; fix boot for old kernels; fix build without resolved; rebase patches to apply on 237 version; rebase patches to apply on 241; update Disable-ProtectHome-and-ProtectSystem-for-old-kernel.patch to apply on 239 version; Update mmc patch; update persistent-storage-rule-mmc-partname.patch to apply on 234 version systemd-conf: disable key handling in logind.conf systemd-machine-units: regroup xiaomi identical service files; fix bluetooth for hammerhead; fix bluetooth for mako; mido: fix Bluetooth; rosy: fix Bluetooth; rosy: fix wlan module loading; tissot: fix Bluetooth systemd-serialgetty: disable SERIAL_CONSOLES on LuneOS’s qemu; drop weird bbappend tzdata: rename bbappend to apply on renamed recipe ubx-utils: fix file-rdeps QA udev-extraconf: override automount.rules with empty rules file; tissot, rosy: add touchscreen0 rule unused: remove long unused recipes and bbclasses uriparser: Upgrade to 0.9.3 Various components: Move back to webOS-ports fork Various fixes for systemd vboxguestdrivers: backport 5.2.22 from meta-oe; unblacklist but install only vboxguest and vboxsf modules VoiceCall: Bump SRCREV & drop patch; Bump version to latest from upstream and refresh patches; Drop patches since our changes are merged upstream; fix DEVICELOCK handling wayland: limit do_install_append only for target webos_{lttng,pmlog_config}.bbclass: move to the right layer webos_configure_manifest.bbclass, webos_system_bus.bbclass: replace some warnings with notes webos_configure_manifest.bbclass: move to the right layer webos_nyx_module_provider.bbclass: enable NYXMOD_OW_MSMMTP by default webos_test_provider.bbclass: move to meta-luneui webos-connman-adapter: bump SRCREV webos-initscripts, org.webosports.cdav, app-services, bootd, com.webos.service.pdm, db8, enyo-1.0, mojoservice-framework, mojomail: Bump SRCREV webos-initscripts.bb: Fix inherit webos-initscripts: don’t include systemd-machine-units in sstate signature; fix startup sequence for webOS-OSE; Fix whitespace issues webos-keyboard: fix LS2 for webOS-OSE; Bump SRCREV wifi-module-load: fix sleep call in systemd service luneos-components: Update Qt version to 5.12.5; Add stub for ieee8021x wifi network 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, Hammerhead and Tissot remain our focus for now, but the emulators, Mako and Mido 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: pxhere.com The post LuneOS October Stable release: Eggnog Latte first appeared on pivotCE. Related posts: LuneOS October Stable Release: Caffè Latte LuneOS February Stable Release: Chai Latte LuneOS September Stable Release: Decaf View the full article

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

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 get LuneOS running on it 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. The post LuneOS November Stable Release: Doppio first appeared on pivotCE. Related posts: LuneOS July Stable Release: Cortado LuneOS February Stable Release: Chai Latte LuneOS September Stable Release: Decaf View the full article

There’s a new Palm phone. It’s due to be released next month. Now, if you are a long time Palm enthusiast (and reader of this blog) you will no doubt be telling your heart not to beat too quickly because to put it mildly, things have not worked out well in the past. We already knew that TCL / Alcatel had bought the brand (only). The possibility of a new phone running webOS was dismissed. The speculation on the webOs Nation forum was that we would be seeing a standard Android slab with the Palm logo stuck on, though no one could figure out quite how that would be a success. In August, there were some leaks that seemed both intriguing and potentially disappointing. A small phone? OK! A low specification? Uh… You don’t have to wonder any longer. The curtain has been almost fully raised and we can confirm that the new phone is… both intriguing and potentially disappointing. Here are some bullet points: It appears that the new Palm is in fact a startup that approached TCL with their plan. TCL backed them and handed them the Palm brand. “Pepito” was a codename. It’s just “Palm”. The reason the specs look like a ‘weekend’ phone is because it’s a weekend phone. It is in fact a ‘companion’ phone to your other, big phone. We are just a little webOS blog, so we have no inside sources or review model. There is an apparently regurgitated press release on Fast Company. You can then read what Dieter Bohn has to say at The Verge. A number of webOS community members have done valuable work in maintaining popular services on our old webOS devices (not to mention keeping them working at all). But given the number of services that no longer work on webOS, using one of the original phones has much the same effect as the ‘Life Mode’ (AKA aeroplane mode) offered by this new device. However, I’m not going to condemn it. The potential criticisms are obvious: Why not just sell a smaller phone? It’s only available as an add on device, only on Verizon in the U.S. It costs $350. It’s true that there seems to be an increasing desire for phones that are smaller and for services that respect a balanced life rather than attempting to addict us to various feeds. There are few choices available for those that want these options. Within that context, the new Palm phone is different and distinctive. As a ‘lifestyle phone’, it is possible that it will appeal to trendy and fairly well-off people and actually sell. However, the Verizon exclusivity may limit access even to that particular demographic. If enough are sold to keep Palm in business, they could extend the concept to other networks and countries. It’s possible that the next model could build on that. Pepito2 could have better specs and be able to stand alone, usable as a companion device or a daily driver. Of course, I’d say that an ideal OS for some kind of synchronizing connectivity across devices would be webOS, but that’s NEVER GOING TO HAPPEN, unless the boot-loader is unlocked and we install it ourselves. So I wish the new Palm luck. In historical terms, there’s very little about this product that’s new, but it seems that it could fill a niche that’s opened up in the current smartphone market. This pricey life-style toy could evolve into the smaller, simpler phone for the many, but only time will tell and yes, I’m doubtful. Those are my thoughts. What are yours? Here’s your comment thread. Related posts: TCL’s Palm phone will run android…duh HP is to Palm as Lenovo is to Motorola…Not Good TCL, Blackberry & Palm View the full article

There’s a new Palm phone. It’s due to be released next month. Now, if you are a long time Palm enthusiast (and reader of this blog) you will no doubt be telling your heart not to beat too quickly because to put it mildly, things have not worked out well in the past. We already knew that TCL / Alcatel had bought the brand (only). The possibility of a new phone running webOS was dismissed. The speculation on the webOs Nation forum was that we would be seeing a standard Android slab with the Palm logo stuck on, though no one could figure out quite how that would be a success. In August, there were some leaks that seemed both intriguing and potentially disappointing. A small phone? OK! A low specification? Uh… You don’t have to wonder any longer. The curtain has been almost fully raised and we can confirm that the new phone is… both intriguing and potentially disappointing. Here are some bullet points: It appears that the new Palm is in fact a startup that approached TCL with their plan. TCL backed them and handed them the Palm brand. “Pepito” was a codename. It’s just “Palm”. The reason the specs look like a ‘weekend’ phone is because it’s a weekend phone. It is in fact a ‘companion’ phone to your other, big phone. We are just a little webOS blog, so we have no inside sources or review model. There is an apparently regurgitated press release on Fast Company. You can then read what Dieter Bohn has to say at The Verge. A number of webOS community members have done valuable work in maintaining popular services on our old webOS devices (not to mention keeping them working at all). But given the number of services that no longer work on webOS, using one of the original phones has much the same effect as the ‘Life Mode’ (AKA aeroplane mode) offered by this new device. However, I’m not going to condemn it. The potential criticisms are obvious: Why not just sell a smaller phone? It’s only available as an add on device, only on Verizon in the U.S. It costs $350. It’s true that there seems to be an increasing desire for phones that are smaller and for services that respect a balanced life rather than attempting to addict us to various feeds. There are few choices available for those that want these options. Within that context, the new Palm phone is different and distinctive. As a ‘lifestyle phone’, it is possible that it will appeal to trendy and fairly well-off people and actually sell. However, the Verizon exclusivity may limit access even to that particular demographic. If enough are sold to keep Palm in business, they could extend the concept to other networks and countries. It’s possible that the next model could build on that. Pepito2 could have better specs and be able to stand alone, usable as a companion device or a daily driver. Of course, I’d say that an ideal OS for some kind of synchronizing connectivity across devices would be webOS, but that’s NEVER GOING TO HAPPEN, unless the boot-loader is unlocked and we install it ourselves. So I wish the new Palm luck. In historical terms, there’s very little about this product that’s new, but it seems that it could fill a niche that’s opened up in the current smartphone market. This pricey life-style toy could evolve into the smaller, simpler phone for the many, but only time will tell and yes, I’m doubtful. Those are my thoughts. What are yours? Here’s your comment thread. Image credit: Palm.com The post The New Palm phone is revealed. first appeared on pivotCE. Related posts: TCL’s Palm phone will run android…duh HP is to Palm as Lenovo is to Motorola…Not Good TCL, Blackberry & Palm View the full article

It’s been over a year since there was a webOS meet up in Chicago, but it’s happening next month! There are many fun things to do in Schaumburg, but the highlight of your visit will of course be the chance to sit down with fellow webOS enthusiasts to enjoy pizza and good conversation. The 2018 webOS meetup will be on Sunday June 3rd 2018 at 7pm. The place is Moretti’s Ristorante and Pizzeria, 1893 Walden Office Square, Schaumburg, IL 60173. Bring your old webOS devices, your new LuneOS devices and your Raspberry Pi running webOS OSE (but maybe leave your webOS TV at home). Click here for directions to Moretti’s. Any questions? Here’s the forum. The team at pivotCE remind you that if you are planning a meet up, let us know! We are interested in promoting your events (it might even increase attendance!). We are also interested in reports and pictures from webOS events. Related posts: webOS meetup, Chicago, 23rd November webOS meetup, Chicago, 27th November webOS meetup, Chicago, 17th April View the full article

It’s been over a year since there was a webOS meet up in Chicago, but it’s happening next month! There are many fun things to do in Schaumburg, but the highlight of your visit will of course be the chance to sit down with fellow webOS enthusiasts to enjoy pizza and good conversation. The 2018 webOS meetup will be on Sunday June 3rd 2018 at 7pm. The place is Moretti’s Ristorante and Pizzeria, 1893 Walden Office Square, Schaumburg, IL 60173. Bring your old webOS devices, your new LuneOS devices and your Raspberry Pi running webOS OSE (but maybe leave your webOS TV at home). Click here for directions to Moretti’s. Any questions? Here’s the forum. The team at pivotCE remind you that if you are planning a meet up, let us know! We are interested in promoting your events (it might even increase attendance!). We are also interested in reports and pictures from webOS events. The post webOS meetup, Chicago, 3rd June first appeared on pivotCE. Related posts: webOS meetup, Chicago, 23rd November webOS meetup, Chicago, 27th November webOS meetup, Chicago, 17th April View the full article

Android Police broke the story earlier today that TCL will launch a Palm branded phone via Verizon sometime in the 2nd quarter this year. And surprise…it runs Android. Sadly that’s all we know for now. It’s taken TCL a long time to do anything with the Palm brand. We first talked about it 3 years ago. It started as an unveil of sorts at CES in 2015 when they announced they had purchased the Palm brand and they’d be crowd-sourcing from “Palm’s very own community” what to do with it. No idea what they meant by that… They even launched a website placeholder that directed palm.com to mynewpalm.com. Both of which are no longer doing anything. But trust me when I say I’ll be hammering the refresh button for the near future on palm.com. Fun fact: This topic was also the fourth to last article written on the now silent webOSNation.com to give you a reference for how long it took TCL to do something! At any rate, I’m glad the wheels are turning and I’ll hold judgement until I see what they release though the carrier exclusivity announcement makes my eye twitch. Even former Palm CEO Jon Rubinstein knew carrier exclusivity aided in the death of webOS and the remnants of Palm. “I think the deal we had with Verizon really hurt us, but who knew that at the time? These things are all hindsight.” TCL can use hindsight for historical evidence though. Hopefully they’re crunching the numbers… #PalmForever Related posts: HP is to Palm as Lenovo is to Motorola…Not Good The Next webOS Phone? (Part I) The Second Day of webOS-mas – Print from your phone View the full article

Android Police broke the story earlier today that TCL will launch a Palm branded phone via Verizon sometime in the 2nd quarter this year. And surprise…it runs Android. Sadly that’s all we know for now. It’s taken TCL a long time to do anything with the Palm brand. We first talked about it 3 years ago. It started as an unveil of sorts at CES in 2015 when they announced they had purchased the Palm brand and they’d be crowd-sourcing from “Palm’s very own community” what to do with it. No idea what they meant by that… They even launched a website placeholder that directed palm.com to mynewpalm.com. Both of which are no longer doing anything. But trust me when I say I’ll be hammering the refresh button for the near future on palm.com. Fun fact: This topic was also the fourth to last article written on the now silent webOSNation.com to give you a reference for how long it took TCL to do something! At any rate, I’m glad the wheels are turning and I’ll hold judgement until I see what they release though the carrier exclusivity announcement makes my eye twitch. But I agree with Mr. Bohn. The fact that TCL is partnering with Verizon to make the new Palm-branded phone is too much. Literally the carrier that put the dagger in the heart of webOS by pulling support is going to get a nostalgia bait money grab device likely filled with bloathttps://t.co/R5QOz656tU — Dieter Bohn (@backlon) March 28, 2018 Even former Palm CEO Jon Rubinstein knew carrier exclusivity aided in the death of webOS and the remnants of Palm. “I think the deal we had with Verizon really hurt us, but who knew that at the time? These things are all hindsight.” TCL can use hindsight for historical evidence though. Hopefully they’re crunching the numbers… #PalmForever The post TCL’s Palm phone will run android…duh first appeared on pivotCE. Related posts: The New Palm phone is revealed. The Next webOS Phone? (Part I) New Palm OS Software Archive View the full article

Dig around in your closet, dump out that side table drawer, and wade through boxes in your garage. Do whatever you have to do to find those old Palm OS devices because there’s a new software archive in town! Reddit user, Yiddish, established the archive and is adding to it via donations from Palm fans. (Check out /r/Palm by the way!) If you have files to add, reach out to Yiddish via the Reddit post or on the twitter page for @ArchivePalmOS. Shalom! #PalmOSforever Click the pic above for a recent /r/Palm post from andymememe. The post New Palm OS Software Archive first appeared on pivotCE. Related posts: TCL, Blackberry & Palm TCL’s Palm phone will run android…duh Forty Years of Tech Exhibit Showcases first Palm PDA View the full article

Dig around in your closet, dump out that side table drawer, and wade through boxes in your garage. Do whatever you have to do to find those old Palm OS devices because there’s a new software archive in town! Reddit user, Yiddish, established the archive and is adding to it via donations from Palm fans. (Check out /r/Palm by the way!) If you have files to add, reach out to Yiddish via the Reddit post or on the twitter page for @ArchivePalmOS. Shalom! #PalmOSforever Click the pic above for a recent /r/Palm post from andymememe. Related posts: Forty Years of Tech Exhibit Showcases first Palm PDA TCL, Blackberry & Palm HP attempts to sell Palm patents – again. View the full article

The release of fresh webOS code from LG in the form of webOS Open Source Edition was unexpected. There’s been some interest in what exactly it is. Fortunately, web developer, Garrett Downs has the Raspberry Pi 3 needed to run the code and we have a guest post with his first impressions: What’s that? Pining for webOS? Build and install on your Raspberry Pi! https://t.co/3Eslofgb1x and https://t.co/GxY3yWnJlz — webOS DevRelations (@webOSdev) March 20, 2018 When I saw a tweet from @webOSdev announcing webOS OSE was available to install on a Raspberry Pi 3, I knew what I’d be doing that night after work. Unfortunately, the process to build it requires hours of time and a computer running Linux natively (virtual machines are not recommended). I didn’t have either of those things. Luckily, someone had already built it and made the image available to download. Sweet! I put the image on a SD card, loaded it into my Pi, and powered it up. After booting, you’re greeted with a nice splash screen with the webOS OSE logo in the corner. The recommended first thing to do is go into settings and connect to ethernet or Wi-Fi, so that’s what I did. That’s actually the only thing you can do in the settings right now. The only other section contains some basic info about the OS and that’s it. Alright, how about apps? As this is the very first version of the project, I wasn’t expecting much here. Pressing F1 on the keyboard triggers the app menu to slide in from the right side of the screen. There are three “apps” in there, but they’re nothing more than website wrappers. ‘Enact’ and ‘webOS OSE’ will bring you to two sites with lots of info about the OSE project and how to get started developing. The third is ‘YouTube’, which is obviously a YouTube app. I haven’t tried signing into my Google account, but videos on the landing page work just as they should. The interface doesn’t have cards like we know them from old webOS or the small tiles of webOS TV. I’m not sure how webOS OSE handles switching between apps. They only really told us how to open the app list. I’m curious to learn more about this. I’d say that this is a pretty barebones OS in its current form. It seems to be the TV OS with a lot of the stuff removed (or just not accessible yet?), like the apps along the bottom of the homescreen, content store, most of the settings, etc. I think it’s enough for developers to start poking around though. I don’t know if it’s touchscreen-enabled, but I would assume so. So, that’s all there is to see for now, at least from an end user’s point of view. If you happen to be an app developer like me, there are already some tools on the webOS OSE site to get started tinkering. I’ve had some limited success getting a couple of my apps up and running. If you’re looking to dig deeper than app dev, the entire project is open source so feel free to dive right in! The documentation for app development seems to be pretty decent considering how new this project is. If you don’t want to bother setting up a Raspberry Pi, I made a short video showing most of what I mentioned above. The post A Quick Tour of webOS OSE on the Raspberry Pi first appeared on pivotCE. Related posts: The First Day of webOS-mas – webOS Quick Install Enyo Next-Gen enters private beta testing webOS meetup, Chicago, 17th April View the full article

The release of fresh webOS code from LG in the form of webOS Open Source Edition was unexpected. There’s been some interest in what exactly it is. Fortunately, web developer, Garrett Downs has the Raspberry Pi 3 needed to run the code and we have a guest post with his first impressions: What’s that? Pining for webOS? Build and install on your Raspberry Pi! https://t.co/3Eslofgb1x and https://t.co/GxY3yWnJlz — webOS DevRelations (@webOSdev) March 20, 2018 When I saw a tweet from @webOSdev announcing webOS OSE was available to install on a Raspberry Pi 3, I knew what I’d be doing that night after work. Unfortunately, the process to build it requires hours of time and a computer running Linux natively (virtual machines are not recommended). I didn’t have either of those things. Luckily, someone had already built it and made the image available to download. Sweet! I put the image on a SD card, loaded it into my Pi, and powered it up. After booting, you’re greeted with a nice splash screen with the webOS OSE logo in the corner. The recommended first thing to do is go into settings and connect to ethernet or Wi-Fi, so that’s what I did. That’s actually the only thing you can do in the settings right now. The only other section contains some basic info about the OS and that’s it. Alright, how about apps? As this is the very first version of the project, I wasn’t expecting much here. Pressing F1 on the keyboard triggers the app menu to slide in from the right side of the screen. There are three “apps” in there, but they’re nothing more than website wrappers. ‘Enact’ and ‘webOS OSE’ will bring you to two sites with lots of info about the OSE project and how to get started developing. The third is ‘YouTube’, which is obviously a YouTube app. I haven’t tried signing into my Google account, but videos on the landing page work just as they should. The interface doesn’t have cards like we know them from old webOS or the small tiles of webOS TV. I’m not sure how webOS OSE handles switching between apps. They only really told us how to open the app list. I’m curious to learn more about this. I’d say that this is a pretty barebones OS in its current form. It seems to be the TV OS with a lot of the stuff removed (or just not accessible yet?), like the apps along the bottom of the homescreen, content store, most of the settings, etc. I think it’s enough for developers to start poking around though. I don’t know if it’s touchscreen-enabled, but I would assume so. So, that’s all there is to see for now, at least from an end user’s point of view. If you happen to be an app developer like me, there are already some tools on the webOS OSE site to get started tinkering. I’ve had some limited success getting a couple of my apps up and running. If you’re looking to dig deeper than app dev, the entire project is open source so feel free to dive right in! The documentation for app development seems to be pretty decent considering how new this project is. If you don’t want to bother setting up a Raspberry Pi, I made a short video showing most of what I mentioned above. Related posts: The First Day of webOS-mas – webOS Quick Install Enyo Next-Gen enters private beta testing webOS meetup, Chicago, 17th April View the full article

Yo! We heard you like open sourced webOS so LG open sourced the open source of webOS! Ok, so that’s not entirely accurate since LG purchased the closed source webOS code from HP after they open sourced…well…bits and pieces of it back in 2012. So no, you’re not stuck in a Doctor Strange time loop. webOS has been open sourced before but not by LG. This news comes as a shock to the current legacy webOS community still rocking Pre 3s and waiting for LuneOS to reach “driver” status. The community hasn’t poured through the code as of yet but it immediately begs certain questions: Will the work on LuneOS be helped or hindered by additional LG open source code which LG had already been committing too for some time (though they have missed some of their promised bits for a while)? What hardware limitations are there for use of the software? Still looking for that webOS toaster… How flexible (read: portable) is it? How complete is it? HP’s open source webOS was decidedly incomplete… We’ll keep you updated on the developments on this as they become available. For now, the conversation has started on the forums so feel free to chime in. #webOSforever The post Open Source webOS now brought to you by LG first appeared on pivotCE. Related posts: Enyo Team Open Sources Mochi UI, Feels like webOS 3.1 Open webOS Running on a WiFi Router Open Letter to LG #1 View the full article

Yo! We heard you like open sourced webOS so LG open sourced the open source of webOS! Ok, so that’s not entirely accurate since LG purchased the closed source webOS code from HP after they open sourced…well…bits and pieces of it back in 2012. So no, you’re not stuck in a Doctor Strange time loop. webOS has been open sourced before but not by LG. This news comes as a shock to the current legacy webOS community still rocking Pre 3s and waiting for LuneOS to reach “driver” status. The community hasn’t poured through the code as of yet but it immediately begs certain questions: Will the work on LuneOS be helped or hindered by additional LG open source code which LG had already been committing too for some time (though they have missed some of their promised bits for a while)? What hardware limitations are there for use of the software? Still looking for that webOS toaster… How flexible (read: portable) is it? How complete is it? HP’s open source webOS was decidedly incomplete… We’ll keep you updated on the developments on this as they become available. For now, the conversation has started on the forums so feel free to chime in. #webOSforever Related posts: Enyo Team Open Sources Mochi UI, Feels like webOS 3.1 Open webOS Running on a WiFi Router Open Letter to LG #1 View the full article

It’s been quite a while since our last release and we’ve been keeping quiet lately. Some of the team members have also enjoyed some well deserved time off in the meanwhile as well. The majority of what we’ve been working on hasn’t been and isn’t ready for public consumption. But quite a lot of things have happened in the past couple of months. Here’s what we’ve been working on since the previous release: -Updated various underlying OS bits: IM plugins such as SkypeWeb, YahooPlusPlus. -Update from BlueZ4 to BlueZ5. This one is a major upgrade that requires all our targets to have major rework on low level code and this has been taking a long time but is now complete for the Nexus 4 and Nexus 5. This also required us to rework our Settings App plugin for BlueTooth. Since we were never really happy with the plugins and their negative impact on the performance combined with the still uncertain future of the Enyo framework, we decided to start rewriting the Settings app in QML. This will also bring back the individual Settings icons back to the launcher, like they were available on legacy webOS 2.x and 3.x. -Added various bits and initial work for VPN plugin support for ConnMan. -Cleanup various configuration files. -Changed the default wallpaper to a nice new high quality LuneOS one! Thanks to Hans Kokx (aka HaDAk for the great photos!) -Various minor tweaks to configuration. We’ve been working on some new porting targets as well. Seeing that Halium is now available for a large number of target devices (50+ at the time of writing), users/developers have come along wanting to try LuneOS on their Halium supported device too so we’re trying to assist those in getting LuneOS working. This is still a lot of work in progress, but results look promising in general. This also would mean we will support Android 7.1.x based devices and Aarch64 bits architecture (ARM 64 bits chipsets). New targets we are currently developing for are: Xiaomi Redmi Note 4x (mido), OnePlus X (onyx), Google/Huawei Nexus 6P (angler) and Motorola G4 (athene). These are in various stages of development currently. We’ve also been assisting the PostmarketOS guys in getting LuneOS running on their build system and targets with great success so far! There are still bits to be added and polished but it’s already a great start to see how far they have been able to come in such short time! We’re also looking into integrating more with Halium , allowing more and easier ports of the LuneOS! We plan to be back with a new release in due course, in the meanwhile you can always check our our latest nightlies! Related posts: Official Release of LuneOS and Project Updates LuneOS July Stable Release: Cortado LuneOS Update for May View the full article

It’s been quite a while since our last release and we’ve been keeping quiet lately. Some of the team members have also enjoyed some well deserved time off in the meanwhile as well. The majority of what we’ve been working on hasn’t been and isn’t ready for public consumption. But quite a lot of things have happened in the past couple of months. Here’s what we’ve been working on since the previous release: -Updated various underlying OS bits: IM plugins such as SkypeWeb, YahooPlusPlus. -Update from BlueZ4 to BlueZ5. This one is a major upgrade that requires all our targets to have major rework on low level code and this has been taking a long time but is now complete for the Nexus 4 and Nexus 5. This also required us to rework our Settings App plugin for BlueTooth. Since we were never really happy with the plugins and their negative impact on the performance combined with the still uncertain future of the Enyo framework, we decided to start rewriting the Settings app in QML. This will also bring back the individual Settings icons back to the launcher, like they were available on legacy webOS 2.x and 3.x. -Added various bits and initial work for VPN plugin support for ConnMan. -Cleanup various configuration files. -Changed the default wallpaper to a nice new high quality LuneOS one! Thanks to Hans Kokx (aka HaDAk for the great photos!) -Various minor tweaks to configuration. We’ve been working on some new porting targets as well. Seeing that Halium is now available for a large number of target devices (50+ at the time of writing), users/developers have come along wanting to try LuneOS on their Halium supported device too so we’re trying to assist those in getting LuneOS working. This is still a lot of work in progress, but results look promising in general. This also would mean we will support Android 7.1.x based devices and Aarch64 bits architecture (ARM 64 bits chipsets). New targets we are currently developing for are: Xiaomi Redmi Note 4x (mido), OnePlus X (onyx), Google/Huawei Nexus 6P (angler) and Motorola G4 (athene). These are in various stages of development currently. We’ve also been assisting the PostmarketOS guys in getting LuneOS running on their build system and targets with great success so far! There are still bits to be added and polished but it’s already a great start to see how far they have been able to come in such short time! We’re also looking into integrating more with Halium , allowing more and easier ports of the LuneOS! We plan to be back with a new release in due course, in the meanwhile you can always check our our latest nightlies! The post LuneOS project still progressing first appeared on pivotCE. Related posts: Official Release of LuneOS and Project Updates LuneOS July Stable Release: Cortado LuneOS September Stable Release: Decaf View the full article

Have you ever wanted (or needed) to create your own app for webOS? I did. My aim was to create custom apps to launch websites or local html/css/javascript files. Read on for… What I did: Since I knew nothing about Mojo or Enyo, I went looking for a simple template app that I could customize as required using nothing but a text editor and Jason Robitaille’s IpkPackager. But if such a template exists, I couldn’t find it. So I created one. You can get it over at GitHub. Go explore the template app! The template app contains a set of detailed instructions and the files are commented to make them easy to understand. The app also contains instructions for launching local files rather than a website. The idea is to make it as simple as possible to create apps for webOS using regular html, css, and javascript. If the learning curve isn’t as steep, perhaps more users will be able to help themselves. If you make improvements to the template, please fork the repository and contribute! If you have questions or comments, visit the story thread over at webOS Nation. Related posts: 6000+ Apps, Abandonware, and More to Come Preserving webOS apps Skype shutting down 3rd-party apps in December View the full article