Since the most recent release of LuneOS called “Decaf” which includes Qt 5.9.2, support for 3rd party browser plugins (such as Adobe Flash and Google’s WideVine CDM) has been added to the Browser App and has been enabled by default.
However the source code of these plugin binaries is not available and therefore these binaries cannot be compiled and provided in the LuneOS images.
The users would therefore need to manually install (sideload) the required plugin files from a source that has them available. Luckily there are ChromeOS recovery images available for the ARMv7 instruction set which is the same instruction set used by our HP Touchpad, Nexus 4 and Nexus 5. Looking at the list of ChromeOS devices located here and checking their specifications I believe that the Samsung Chomebook from 2012 with Codename “Snow” is a suitable candidate for example. Others that might work are:
Samsung Chromebook 2 – 11″, codename “Pit”
Samsung Chromebook 2 – 13″, codename “Pi”
HP Chromebook 11 G1, codename “Spring”
HP Chromebook 11 G2, codename “Skate”
ASUS Chromebook Flip C100PA, codename “Minnie”
ASUS Chromebook C201, codename “Speedy”
AOpen Chromebase Mini, codename “tiger”
Asus Chromebit CS10, codename “Mickey”
AOpen Chromebox Mini, codename “fievel”
In order to get Adobe Flash & WideVine CDM support you need to do the following:
Download a ChromeOS ARM Recovery image, the best would be the one using the same Chrome/Chromium version, so 56. For example for the Samsung Chromebook codename “Snow” mentioned above as per this link.
Extract the “chromeos_9000.91.0_daisy_recovery_stable-channel_snow-mp-v4.bin.zip” file.
Once done, open “chromeos_9000.91.0_daisy_recovery_stable-channel_snow-mp-v4.bin” with a file archiver (for example 7-Zip on Windows).
Open the ROOT-A.img file.
Go to “/opt/google/chrome/”
Extract “libwidevinecdm.so” and “libwidevinecdmadapter.so” into a separate folder.
Go to “/opt/google/chrome/pepper/”
Extract “libpepflashplayer.so” to the same folder as under 6.
You will now have 3 files in this folder: “libwidevinecdm.so”, “libwidevinecdmadapter.so” and “libpepflashplayer.so”.
Open a command prompt and go to folder with the 3 files.
Now push each of the 3 files to “/usr/lib/chromium/” by means of “adb push libwidevinecdm.so /usr/lib/chromium/”, “adb push libwidevinecdmadapter.so /usr/lib/chromium/” and “adb push libpepflashplayer.so /usr/lib/chromium/”
Now go to https://shaka-player-demo.appspot.com/demo/ to see if WideVine works. It will show you the WideVine options in the dropdown in black instead of grey. When they show in black the WideVine plugin is properly installed and working.
Those following along will recall that the development team had moved onto a new version based on React.js and that this had potential implications for LuneOS.
The Enyo team have just begun a private beta of the next generation Enyo. What we know is that with LG’s TV arm as their main customer, the focus remains on TV sized apps. Though increased support for mobile is planned, it is currently limited. Also, the framework will have a new name when publicly released.
This next generation of Enyo will be of interest to those currently building apps with the platform, but may also attract developers already experienced with ReactJS.
For those engaging with this testing phase, we’d be interested in any comments. The webOS Ports team will no doubt also be interested in any app demos built with it too. You can comment at webOS Nation.
In the early days, webOS was at the cutting edge of using web technologies, but performance was not as responsive compared to more traditionally coded apps. Since the days of legacy webOS, many improvements have been made in app development frameworks and their implementation to bring speed up towards that of ‘native’ apps or at least fast enough for the user to see little difference. Increasing speed, power and multi-core processors have also helped, though performance is beginning to plateau as the physical limits of current hardware is reached.
The first (proprietary) development framework for webOS was called ‘Mojo’. After the purchase by HP, the (Open-source) ‘Enyo’ framework was introduced to target more varied screen sizes. Version 1 ran on the webOS 3.0 HP TouchPad and was back-ported to phones. Version 2 became a cross-platform framework also.
Of course, we all know about the end of hardware at HP and the eventual sell off of all parts of webOS. Officially, the Open-webOS project is still maintained by LG & HP and LG’s Silicon Valley lab have continued to develop the Enyo JS framework. The part used to make the UI for mobile apps is called ‘Onyx’. To make apps suitable for Television screens, LG developed a new UI library called, ‘Moonstone’. Enyo itself has developed through version 2.5 to now stand at version 2.7 and LGSVL now looks to the next generation of Enyo (Forum comments). But this brings with it potential problems for LuneOS.
We send our best wishes to our readers at this time of year. To those that celebrate Christmas, other seasonal festivals or none at all, be of good cheer for webOS still seems to be here for another year!
News crumbs is where we briefly note stories that may have some interest to webOS users. In light of the season, this one will be a little ‘fatter’. Let’s talk turkey.
The start of this month saw the arrival of a new app for webOS. The occasional app still appears along with the various fixes and patches that keep the system running despite the time that has passed since any official, corporate support from it’s creators. These gifts are usually unexpected, so pleasant surprises. DianBao, a client for the Telegram messaging service, may have brought an additional gift. Singaporean developer and forum member, ‘mrrekcuf’ originally created the app as a prize-winning entry for a competition to make a Blackberry 10 app. To port it to Legacy webOS has also meant porting the Qt5 cross-platform application framework. It is this up to date version that has allowed many of the new features of LuneOS, including a modern browser. It remains to be seen if this development will lead anywhere, but if one thing could bring yet another lease of life to Legacy webOS, a new browser would be it. Comment thread.
At webOS Ports, the build servers will be down for the last few days of 2016. Don’t panic! It is only for maintenance and upgrades. LuneOS developers take note.
For those developing apps for LG webOS televisions, note that LG’s developer website will also be shut down just after Christmas. Again, it is merely to allow for a new, improved site! Here’s the announcement. From the 27th the new web address will be: webostv.developer.lge.com
Over the years, webOS enthusiasts have experienced highs and lows from the Consumer Electronics Show. At this time of year we look to the start of January to see what items of interest may be exhibited in Las Vegas. One such item is the LG Probeam laser projector. While only a slight step to a new product category, this at least shows LG’s continuing commitment to webOS in their audio / visual products. Comment thread.
Remember Classic? It was the PalmOS emulator you could use to run old Palm apps on webOS. Those who follow us on Twitter, may have noticed a few retweets when former editor of webOS Nation, Dieter Bohn announced a redesign of his current site, The Verge. He rashly promised a sticker for the first screen shot of the site on a Palm Pre. Alan Morford is not one to do things by halves.
That’s it for now. See you in the new year with an announcement about pivotCE.
By now you’ve likely read about the 6000+ webOS apps we’ve managed to put together. The files are on my Box account and the link was shared A LOT. This was great but had its flaws. For instance, you can’t download the entire thing. It’s a limitation from Box. That problem has been solved as there is now a public ftp! We told you it was coming.
A public ftp solution is coming for the 6000+ #webOS app rescue effort. More details soon!