Welcome to LG webOS - Smart TV, Phone, Signage, Appliance User to User Support Forum

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

This message will be removed once you have signed in.

pivotCE

Members
  • Content count

    54
  • Joined

  • Last visited

  • Days Won

    1

pivotCE last won the day on September 11 2014

pivotCE had the most liked content!

Community Reputation

1 Neutral

About pivotCE

  • Rank
    Advanced Member
  • Birthday

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

3,986 profile views

  1. A bit later than expected but we’re back! Over 2 months passed since the last release and we’re finally back with a new release called “Cold Brew”. We have been working very hard behind the scenes in the past 2 months! So you’re asking what we have done? Most importantly we now have an initial setup for camera working on both the N4 and N5 with an initial version of the app written in Qt (QML). It’s still pretty rough, but it will do basics for now. Further improvements will come once we upgrade Qt to 5.7/5.8. Behind the scenes we’ve been working on getting our Yocto updated to Pyro. This brings quite some challenges due to glibc (2.24) not being compatible with linux kernels < 3.2. Also the newer systemd version (232) brings some challenges in terms of kernel requirements, but we’ve been able to work around those for now. For Mako (N4), Hammerhead (N5) this isn’t really a problem because we have a 3.4 based kernel, for the Tenderloin (Touchpad) there are 3.4 based kernels available as well, so we’ll be aiming to migrate to a 3.4 based kernel for Tenderloin. For Maguro (Galaxy Nexus) the situation is unfortunately more problematic because there’s no real working 3.4 based kernel available currently. It’s therefore likely that as of next release we will be forced to drop support for the Galaxy Nexus. We’re also taking part in in the Halium Project that was announced last week. There are already a lot of synergies between the various OS-es based on Android and also still quite some minor tweaks for each OS. By joining forces in the project we aim to have a common base for the various Android based OS-es. We have the following items on our to-do list to focus on: Work on Yocto Pyro upgrade QT 5.7/5.8 Upgrade Various UI tweaks Messaging improvements Camera improvements 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. Changelog Applications: Testr (org.webosports.app.testr): Adds test of HTML5 camera API (navigator.mediaDevices); Removes erroneous component from HTML5 camera test; Camera test works correctly with portrait video; HTML5 camera test: adds list of user media devices & requests rear camera. Camera (org.webosports.app.camera): Initial app writen from scratch in QT. System Level: qtubuntu-camera: add missing dependencies for Qt. packagegroup-luneos-extended: put the camera recipes in LIBHYBRIS_RDEPENDS. mobile-broadband-provider-info: Add LIC_FILES_CHKSUM. qtbase_git.bbappend: Use = for PACKAGECONFIG_DISTRO. hunspell: remove – it is in meta-oe. mesa: do not move around libGLESv2.so. qtvideo-node: Use webOS-ports repository. meta-webos-ports: Add org.webosports.app.camera and the camera infrastructure packages. 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 Maguro remain our focus for now, but the emulator & Grouper work too. Please note that in order to use the latest stable builds on the Galaxy Nexus (Maguro), 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), Galaxy Nexus (Maguro), Nexus 4 (Mako), Nexus 5 (Hammerhead), Emulator, and Nexus7 (Grouper) 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 with a new release! Related posts: LuneOS April Stable Release: Café au lait LuneOS February Stable Release: Chai Latte Next LuneOS stable release available: Antoccino View the full article
  2. EnyoJS is the javascript frame work used by webOS developers to create applications for both the legacy OS, LuneOS and LG’s TV OS. 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. Related posts: Introduction to Enyo, Minneapolis, 2nd May. More Enyo in Minneapolis, June 20th. Enyo 2.7 released, with next generation plans View the full article
  3. So that’s been a long while already! 2 months passed since the last release and we’re finally back with a new release called “Chai Latte”. We have been working very hard behind the scenes in the past 2 months upgrading our various builds & build infrastructure! So you’re asking what we have done? We have been doing lots of work to make our build & porting process more stable and straightforward. It’s now easier to create a new port for devices having a CM 12.1 (Android 5.1) based build available. Also initial work has been done in order to be able to use CM 13.0 (Android 6.0) based builds. We have updated our Galaxy Nexus (Maguro) and Nexus 4 (Mako) build to a CM 12.1 based build. For the Maguro this solved the garbled audio issue that was present on our previous CM 10.1 based builds. We also have a new target device running on CM 12.1 based build, the Nexus 5 (codename Hammerhead)! We are fully aware that Cyanogen Inc stopped development of Cyanogen OS and also supporting the development of CyanogenMod by the community and all builds have been taken offline. At the time of writing the successor of CyanogenMod, LineageOS, is still in early stages of their setup and has just it’s initial builds, however this is not available for all target devices (yet). We’ll be re-assessing our source for builds at some point in the near future. The change to support LineageOS and/or AOSP directly should be fairly straight forward. Our RaspberryPi2 and RaspberryPi3 builds are currently building again and are included in the release this time. The UI is still not working for the RaspberryPi devices, but at least you should be able to get it to boot and connect via console. Many other small items have been fixed as well, see below for more details of all the changes! 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. Changelog Applications: Messaging (org.webosports.messaging): Conversion to Enyo 2.7, package.json: Add missing icon.png, replaced Contact Picker with Address Picker, Renamed AddrModel to MsgAddrModel, Made Message Address Search list more compact (Mojo-style), return addr picker dynamically populated in threadview, fix back gesture, unified use of guillemets. Contacts (org.webosports.app.contacts): Fixed bug where first IM address wouldn’t have type, updated messaging service picker to align with supported account types, removed obsolete entries. Settings (org.webosports.app.settings): Clarify keyword: AutoCompletion->AutoCorrection. System Level: meta-rpi-luneos: Fix build issues. jenkins-jobs: Add Hammerhead as target v2.3.9. webos-telephonyd: telephonyservice_sms.c: Use timestamp in milliseconds for legacy compatibility. luna-sysmgr: autoCompletion->autoCorrection. webos-keyboard: autoCompletion->autoCorrection, fix various typos mSpellchecing -> mSpellchecking. luna-init: autoCompletion->autoCorrection. pulseaudio-modules-droid: fix build when using android-headers from Ubuntu. qt5-qpa-hwcomposer-plugin: fix build for 4.4.2 with Ubuntu’s android headers. nyx-conf: add hammerhead configuration. luneos-package: use KERNEL_IMAGETYPE for the image name. initramfs-boot-android: improve initrd’s kernel logging. luna-sysmgr-conf: externalize machine-specific configuration files. nyx-modules: externalize machine-specific configuration files. luna-next-conf: add hammerhead environment file. luna-sysmgr-conf: have better GridUnit for hammerhead. VoiceCall: Update to latest from upstream (28-Jan-2017). pulseaudio-modules-droid: Update to latest from upstream (28-Jan-2017). sensorfw: Update to latest from upstream (28-Jan-2017). mobile-broadband-provider-info: Switch to Mer variant & bump SRCREV. qtbase_git.bbappend: Use += for PACKAGECONFIG_DISTRO. hunspell: removed from meta-webos-ports using the one from meta-openembedded instead. libhybris: Bump SRCREV, together with fixes for issues. Add qtubuntu-camera as backend. 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 Maguro remain our focus for now, but the emulator & Grouper work too. Please note that in order to use the latest stable builds on the Galaxy Nexus (Maguro), 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), Galaxy Nexus (Maguro), Nexus 4 (Mako), Nexus 5 (Mako), Emulator, and Nexus7 (Grouper) 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 in March with a new release! We have the following items on our to-do list to focus on: Get the camera working Work on Yocto Morty/Pyro upgrade Investigate feasibility of QT 5.7/5.8 Upgrade UI tweaks Messaging improvements Image credit: And the prize for best dressed chai latte goes to… by Lachlan Hardy. Related posts: LuneOS October Stable Release: Caffè Latte LuneOS February Stable Release: Café Miel LuneOS December Stable Release: Cappuccino View the full article
  4. This article is unusual for pivotCE. Most of our articles are aimed at the general reader, but this one is specifically aimed at those with knowledge of javascript frameworks – specifically frameworks designed for app development. We hope this article will reach such people in our community and beyond in the hope that the LuneOS project can benefit from a range of experience and insight and even perhaps recruit some new contributors. Long time webOS fans will be aware that one of it’s features was the ease with which apps could be created using methods more associated with web design. Most (non-game) apps were in fact mixtures of HTML & javascript. This and the ‘synergy’ of connecting data from various remote services into common user interfaces is what gave the system the name of webOS. 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. To begin with, the various iterations of Enyo are not entirely backwards compatible. This is not a big problem as each version can be installed and recent versions are even able to package up modular parts of the framework with the app itself. But to take advantage of the latest improvements, each app needs some rewriting. At this time, apps written specifically for LuneOS are almost all system apps and have been written in whichever version of Enyo was current at the time. Secondly, the Enyo team are assessing developments in web app development and technology and considering where to next take the framework. This project is currently called, ‘Enyo-next gen’ and will be based in part on the React.js framework. This means that compatibility will again be broken – likely to a greater extent than previously. For this reason, updates of existing LuneOS apps have been put on hold until the Enyo situation becomes clearer. As the Onyx UI library is built on Enyo 2.x, it will not work on React.js unless it is re-engineered. The team’s priorities are obviously lead by LG’s webOS product line: Televisions (briefly a watch) and now refrigerators. It seems that the next generation Enyo will target mobile devices, but Onyx will not be part of the package. It remains to be seen what the replacement will be like. To avoid remaining in a backwater, LuneOS will need apps. The time is approaching when developer attention must turn from the core OS to the app ecosystem. Millions of apps aren’t needed, but a decent range of modern apps will be. LuneOS has a modern browser based on Chrome. All modern JS frameworks support it and therefore many web apps can be run on LuneOS: old Legacy favourites, apps from similar systems and standalone web apps. Of course, the latter examples won’t necessarily resemble or act like webOS apps and LuneOS will still need a framework for original apps; One that will ‘feel’ and hopefully look like webOS. In short, the LuneOS project needs to make a choice of javascript framework for the future and standardise upon it. What are the options? webOS Ports could stick with Enyo 2.7. It will be supported for a while. The problem is that this version will not be updated as technology moves forward and the Ports team lack the resources to maintain the framework in addition to the OS. If Enyo-next gen works well (It is certainly expected to be a contender), but lacks the UI elements suitable for LuneOS, the team could attempt to maintain a version of the Onyx or Mochi UI libraries for dedicated use, but again human resource issues mean this option will probably be overlooked in favour of a more ‘off the shelf’ solution. Enyo-next gen could provide an ideal solution, offering the option of creating webOS-style mobile apps. Another suitable framework may need to be found – one that can offer modern performance and which will be supported for the foreseeable future. A popular framework could also deliver a range of apps from sources beyond the small webOS community. The webOS Ports team are soliciting demo web apps that show the “feel” of webOS can be duplicated by candidate frameworks. What is needed from a javascript framework suitable for LuneOS? LuneOS developer, Doug Reeder of Hominid Software suggests some requirements: 1. A single app is usable on both phone- and tablet-sized screens. 2. A layout widget to organize multiple panes, like Enyo Panels, but possibly behaving differently. 3. A list with 500 items. 4. …whose items can be swiped left or right 5. …and whose items can be rearranged by dragging. A fuller list can be found at this wiki page. Most of our articles link back to the forum at webOS Nation, but in this special case, we are going to link to the archive of the webOS Ports mailing list and invite those interested to join the list and the IRC channel. Here are archives of the discussion so far: Enyo EOL 1, 2, 3. Choosing a new JavaScript framework and UI library 1, 2, 3. If you are familiar with JS frameworks, you are invited to share your experiences of development and performance and suggest candidates for testing. Please click here for information on the IRC channel and how to join the webOS Ports mailing list. Please share this article with anyone who may have useful insights. Image credit: Working on the Meccano Bridge by David Dixon. Related posts: Enyo 2.7 released, with next generation plans Job Listing: Staff Software Engineer for Enyo JavaScript/HTML5 Introduction to Enyo, Minneapolis, 2nd May. View the full article
  5. Shortly after the end of CES, I searched idly for any news from TCL. You may have read that they recently acquired the rights to make & sell Blackberry hardware. Longtime readers will recall TCL’s announcement at 2015’s CES that they had acquired from HP, the last remaining piece of Palm Inc: The brand name. To create an image for that story, I added Palm’s logo to the image on TCL’s website: Palm joins TCLSince that announcement, where TCL encouraged the ‘Palm community’ to participate in developing a device worthy of the name, there has been silence. Now, some have speculated that we could see some kind of combined Palm/Blackberry wonder device, but so far only a Blackberry has been revealed. If you click the link, you can see the familiar keyboard style & this points up the difference between the two purchases: One is a license to manufacture a branded product including hardware & the software that runs on it. The other is just a brand name. Of course, nothing prevents TCL from making anything it wants & calling it a Palm device, but despite it’s recent travails, the Blackberry brand is a going concern with up to date & current technology. Palm is not. In my search for TCL/Palm news, I of course visited the website & the image at the top of this story is from that site. My only change this time was to enlarge it. Note how the Blackberry logo has been added, then realise that the Palm logo doesn’t appear on their website & to my knowledge, never has. Two years on from the 2015 announcement, this likely tells us all we need to know about the future of the Palm brand, but there is one optimistic spin that can be put on this: TCL own the Palm brand. There’s a lot more direct benefit from the Blackberry arrangement, but it’s a licensing deal & one that has resulted from Blackberry’s problems in selling it’s own product. TCL’s Alcatel brand has long been an affordable, no doubt profitable, but unspectacular also-ran in the mass market. The team-up gives TCL access to a technology leader, a respected brand & enables Blackberry to concentrate on software, letting TCL worry about selling product to the masses. If TCL succeed, some of the profit will return to Blackberry. If they fail or the deal turns sour for some other reason, they have another brand ready to be painted on a high-quality handset; A brand unencumbered by licensing fees or any other external requirements: Palm. But really, don’t hold your breath! Related posts: Video: A feature comparison between webOS and Blackberry 10 HP is to Palm as Lenovo is to Motorola…Not Good Christmas News Crumbs, 2016 View the full article
  6. LG has had a few announcements at CES over the years and some of them have included webOS since the company unveiled it’s webOS smart TVs in 2014. The televisions are now on to version 3 of the OS. Late last year we saw stories that webOS would appear on a video projector and in the last few days a refrigerator. What did the CES presentation in Las Vegas have to offer? As ever, it was less than hoped (at least for webOS on mobile fans), but within the bounds of it’s presentation, what was shown was very impressive. Firstly, there was no sign or mention of the projector, so we’ll get back to that another time. The Presentation was introduced as usual by LG CTO, Dr Skott Ahn. Main presentation duties were once again handled by LG’s head of US marketing, David Vanderwaal. Of the products that made it onto the stage, two ran LG’s webOS operating system. Mr Vanderwaal began with the new refrigerator. In many ways, the Smart Instaview fridge is simply a combination of existing technologies from LG and elsewhere. It has a 29″ portrait format screen on one of the doors. Tapping on the door displays a view of the interior so that no energy is wasted in unnecessary opening and it has automatic power saving features. This view can also be sent to a smart phone so you can double check your list when out shopping. The fridge runs a version of webOS, with an interface clearly different from that on the TVs. It can play music and videos, track the freshness of products on the shelf, display noticeboard type messages, recipes and order fresh groceries online. LG have worked with Amazon to integrate their Alexa voice recognition system for control and ordering. The whole arrangement can hook up to to an Artificial Intelligence system called Deep ThinQ to anticipate the user’s lifestyle needs. The flag-ship fridge has almost every feature you could think to cram in and is an impressive item for the moneyed consumer. After a diversion into a pair of Schmoo-style robots, the focus moved to televisions. This year will see an update to LG webOS 3.5 including support for recording and 360 VR videos. Mr Vanderwaal started this section with improvements to their LCD display technology. LG uses nano cell technology to improve colour rendition up to 1 billion colours. Both luminance and viewing angles are improved. Mr Vanderwaal was joined on stage by representatives from both Technicolor and Dolby Labs. The new TVs will support both company’s systems for colour rendition and high dynamic range pictures among other formats. Some HDR processing can be applied to images with standard dynamic range. To compliment improved colour, brightness and contrast range, LG speaker systems also support Dolby’s Atmos sound system. Dolby’s Giles Baker stated that, “there is no better TV on the market today.” The support from these two big names in cinema technology is certainly impressive. The presentation finished with the flag-ship TV for 2017: The 77″ LG Signature W. This 4K OLED TV needs no back light so can be only 2.57mm thick. Mr Vanderwaal said this enables the TV to be magnetically mounted directly to the wall and claimed that this made the total thickness less than 4mm, casting such a minimal shadow that the TV appears to be part of the wallpaper – hence the ‘W’ in the name. There was brief mention of a new generation Blu-ray Ultra HD HDR player to compliment this screen, but there were few details. Here is the video (you may need to forward to the start): What was interesting was that there was no mention of mobile phones or tablets. It seems clear that this sector has somewhat reached saturation – at least in most developed countries. Though LG has produced consistently high quality devices, they have struggled to differentiate – even with experiments like their modular G5. After Samsung’s PR disaster with the Note 7, there may be an opportunity for LG to grab more market share. Well known is the rivalry between LG and fellow South Korean electronic manufacturers, Samsung. They often attempt to match and ideally top each other. As Samsung have attempted to avoid Google’s increasing control of Android by using their own Tizen system in other product categories, we have wondered if LG might follow – especially when Tizen on TVs so closely resembles LG webOS. Now as a refrigerator runs webOS, we can again wonder if a webOS IoT eco-system can be built. Whether this creates a path for a commercial webOS phone or even a webOS toaster remains to be seen. Maybe next year? Related posts: The LG Keynote at CES 2016 LG will show webOS TVs at CES 2014 Countdown to LG’s CES 2014 press conference View the full article
  7. Merry Christmas! And we’re finally back with a new release called “Cappuccino”, just in time for Christmas and the New Year. We have been focusing on improving the underlying system stability, adding new features and upgrading various system components. The release is a bit later compared to what you’re used to this which is due to a combination of some technical, logistical and personnel issues. We have worked hard to make the OS even more stable and smooth. We have been focusing on some of the back-end bits for Instant Messaging. Instant Messages aren’t working yet fully in our Enyo 2 rewrite of Messaging, but things start to look better with each change. We have also updated various IM plugins for Skype & Yahoo. We have also reworked the handling of the notifications to become a bit more snappier and we brought back some more features from LunaCE like “Card Zoom Gestures“. We have also re-worked the handling of the icons in the launcher a bit. We now have a Calendar icon showing the correct day for example. We have also started the work to migrate our Nexus 4 (Mako) build from Android 4.2.2 (CM 10.1) based to Android 5.1 (CM 12.1) based. The image for this is working, we’re now looking to integrate this into our build environment, which is scheduled for just after the holidays. This will also make new ports of more modern targets like the newer Nexus and OnePlus targets a lot easier. At the same time we’re also looking at updating our Yocto release from Krogoth to Morty, however we ran into some roadblocks there, so we’ll revisit that after we have completed our CM 12.1 build integration. Many other small items have been fixed as well, see below for more details of all the changes! 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. Changelog Applications: Contacts (org.webosports.app.contacts): Allow searching in Favorites, as in webOS 1.x and 2.x, cleanup of un-needed controls, width of search field is limited to about 14 characters, Tweaks visuals, increase targetWidth or search field. Added Enyo 2.5 People Pick from Messaging for future use. FirstUse (org.webosports.app-firstuse): Various graphic improvements 2, use #4db2ff as link color. Preware (org.webosinternals.preware): Refactors global functions & vars into local, removes unused code & generally cleans up. Messaging: org.webosports.app.messaging: Fix empty PalmSystem.launchParams, Use 13 digit Javascript timestamp to be legacy compatible, Fix JSON syntax errors & add contacts mock data, ThreadView.js: Fix Uncaught TypeError, Refactors and removes unused files, in preparation for Enyo 2.7. Preware (org.webosinternals.preware): Add systemd service file. User Interface: luna-next-cardshell: LaunchBar: Let Phone app depend on Settings.tabletUi instead, fix arrangement of icons like legaycy, CardView Correctly center the current card/group in the screen, CardView: take spread value from card group model, CardView: fix some issues when maximizing a card from a stack, CardView: Implement pinch-to-zoom on a single card, Notifications: Use the same swiping logics as for cards, LaunchBar: Dynamically populate icons & update application JSON files, LaunchBar: Have usefull apps for desktop testing, LaunchBar: Use a common ApplicationModel instance for all the launchers, CardView: avoid artefacts after card swiped out, LaunchBar.qml: Don’t use asc: true since it’s invalid, fix default-app-icon.png artifacts. System Level: build: Corrected upload path for builds. qtwebengine-chromium: add missing include, fix detection of MSVC 2015 Express, fix accessibility crash on view destruction, when a popup is open. webos-telephonyd: com.palm.mmsmessage:1 db kind & permissions for com.palm.& apps. qtwebengine: Update to latest from upstream 5.6 (22-Nov-2016). messaging-accounts: Update Yahoo template for new plugin, removed unneeded logging, removed MySpaceIM template. jenkins-job.sh: Show number of openssl archives before and after sstate-cache-management.sh, add few more extra archs to sstate cleanup. luna-sysmgr: Add default-dock-positions for filling QuickLaunch Bar. luna-webappmanager: BluetoothManager: Add paringDone function. qtsensors-sensorfw-plugin: Update to latest QT 5.6.2 code. luneos-components: Return locale as well while subscribing, add missing apps to test data, Test apps list: fix icon paths and ids to get correct launchers. meta-webos-ports: mojomail: drop patches and move to own fork, qt5-qpa-hwcomposer-plugin: switch to upstream and add rotation patch, sensorfw: Update to latest upstream (30-Oct-16), nemo-qml-plugin-dbus: Switch to mer git and bump SRCREV, mobile-broadband-providers-info: update to latest from upstream (02-Nov-2016), lxc: Update to 2.0.5, libhyrbis: update to latest from upstream (02-nov-16), https-everywhere: update to latest from upstream, hunspell-dictionaries: update to latest, hunspell: Update to 1.4.1, python-tz-native: Update to 2016.7, uriparser: Update to 0.8.4, Update Preware feed for Feedspider and use secure URL, purple-skypeweb: Update to latest from upstream (19-Dec-16), funyahoo-plusplus: Add recipe, More robust building & cleaner logging of enyo-dev apps, imaccountvalidator: Add new Yahoo plugin & remove old ones, imlibpurpleservice: Add new Yahoo plugin & remove old ones, 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 and Mako remain our focus for now, but the emulator, Maguro & Grouper work too. Installation instructions for TouchPad (Tenderloin), Galaxy Nexus (Maguro), Nexus 4 (Mako), Emulator, and Nexus7 (Grouper) 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] There will be a major upgrade of our build infrastructure over Christmas and New Year, so we’ll need some time to make sure everything is working properly during January, so there won’t be a release in January. We will see you in February with a new release! Related posts: LuneOS December Stable Release: Caffè Marocchino LuneOS June Stable Release: Caffè Tobio LuneOS May Stable Release: Café mocha View the full article
  8. 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. News that may be of interest to Palm fans is that TCL / Alcatel has signed a license deal with Blackberry to produce phones (the last couple of BB phones were rebranded TCL models). New products may well be exhibited at CES next month. Notable for us was TCL’s purchase of the ‘Palm’ brand almost two years ago. Since that announcement, there has only been silence… Comment thread. Another gift! This time it is for PalmOS users. Games company, Astraware have published the registration codes of games for PalmOS and other old systems. You will need to dig out the apps from your archive (or get them by other means), but you can now activate them on new or reset devices. 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. Related posts: News Crumbs – 15th AUGUST 2016 News Crumbs – 18th November 2016 News Crumbs – 13th JULY 2016 View the full article
  9. The traffic sucked all the way there but NDrive on Marc’s Pre3 got us there all the same. It took us through the city instead of around and it was a busy Saturday night so traffic was really bad. Pi Pizza was delicious as always. In the picture is Marc, then Gary, then Atif and I took the photo. I took the photo with my Yotaphone 2 mostly to show up the EPD screen and how it winks at you when it takes a picture but also to catalog the attendees. Gary wanted to know all of our Palm stories. Marc’s was the shortest with only coming over to webOS and the Veer. Gary’s and Atif’s were a bit more storied and mine I think is known at least to our readers. Marc passed around the Windsornot and a TS2. I passed around my 64GB Go and Palm branded Veer (which I was “driving” that day). The Windsornot was of course a highlight and a low point. Atif captured the mood well in his forum post. Marc sells a ton of Veers. He has quite the collection of Veer parts. He brought 4, “seen better days” Veers and gave them away as party gifts. Nice guy. Gary drove from New Jersey. Atif came from New York. Marc flew to visit me from Chicago and I planned the meetup since he was going to be here. That started the whole idea anyway. Related posts: webOS meetup, Bethesda, Maryland, November 5th St. Louis webOS Meetup Recap Chicago WebOS Meetup September 28th, 2014 View the full article
  10. Uh, the toaster needs another clean. Let’s shake it before those crumbs are too stale or burnt! webOS developer, Choorp either loves twitter or is frightened of it (actually, both is probably normal). He made this based on the logo of premier webOS twitter app, Project Macaw. We salute developer, Penduin for developing an app that only gets used once a year. Slashgear reports that TV’s running LGwebOS 3.0 now have online payment support for shopping & in-app payments. Set those parental controls! TechnoBuffalo is the latest Tech blog looking wistfully back. Are we the only one looking to the future of mobile webOS? You want webOS merchandise? Improvise! Former Palm employee, Lisa Brewster demonstrates what to do if you find yourself in the wild without a toaster. I don’t know about you, but for me, it’s time for teacakes. See you next time! Related posts: News Crumbs – 15th AUGUST 2016 News Crumbs – 9th November 2015 News Crumbs 16 November 2014 View the full article
  11. U.S. webOS fans in the Chicago area can once again meetup and chat over pizza. As usual it’s on a Sunday. November 27th this time – just as you’ve recovered from that big Thanksgiving meal!. 7pm is the time, Moretti’s Ristorante and Pizzeria, Schamburg is the place. Click here for directions. Bring your webOS and LuneOS devices, discuss developments and the future and exchange tips on keeping your phones and tablets alive and functional. If you need to know more or announce your attendance, here is the webOS Nation thread. 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, 22nd November webOS meetup, Chicago, 17th April View the full article
  12. We just bought the domain, weboscenter.com and set it up to redirect to this article. webOS Center was a fairly popular blog, but new posts stopped back in 2012 except for a blip in 2014 when the first webOS TVs were released by LG. If you got here via an old bookmark or are just curious, you can see the original site on the internet archive by clicking here. pivotCE continues to publish what news there is about legacy webOS and the new open-source version, LuneOS in addition to tips and tricks for using these mobile operating systems. Discussion forums are still active over at webOS Nation. You can see listings of available apps here. We hope to see old web sites and resources maintained and offer our own content to owners of webOS sites who wish to keep them updated. If possible, we are willing to take over old sites or re-host their original content. Where sites disappear, we will re-register old domains if they are affordable and relevant and redirect them here. We don’t expect to drive any significant traffic, but maybe a few old webOS fans will drift in and discover LuneOS. How long we hold on to any domains we obtain will depend on continuing affordability, but we could also pass domains on to any webOS / LuneOS projects that arise from the community. Remember, pivotCE is funded by donation. You can contribute using the box at the left of this page. Related posts: webOS meetup, Chicago, 22nd November Chicago webOS meetup this Sunday webOS meetup, Chicago, 17th April View the full article
  13. No release this month folks! We’re doing some long overdue maintenance on our build servers and related services. They were still running Ubuntu 14.04 so we have now updated them to the latest Ubuntu LTS release 16.04.1. Most of the updates went fine but we still have a few loose ends to address, specifically with some build issues for the Touchpad kernel. In the meanwhile we were able to fix some of the MediaWiki issues that happened after we upgraded MediaWiki earlier which broke templates and the change log. We have also started to do initial testing for migrating to the latest Yocto 2.2 release called Morty and initial (local) testing is underway for a Qt 5.7 migration as well. These are not expected to hit the next release yet, but it’s all work in progress for now. It’s not included in the nightlies yet for now. We are also venturing in paving the way for updating some of our builds to a CM 12.1 (Android 5.1) and CM 13.0 (Android 6.0) build. This should also help for future ports to more recent devices. In the meantime you can get our latest nightly releases and help us test and report your findings. We’re always looking for energetic volunteers to join the team. See you next month! Related posts: LuneOS Update for November LuneOS Update for July LuneOS Update for March View the full article
  14. Washington, District of Columbia houses the seat of government for the United States of America. Here, many meetings take place and many momentous decisions are made. In November of this year, the citizens of these states face a momentous decision: “Will I attend the webOS meetup in Bethesda?” (Hint: Yes) That’s right, a few short miles from the White House, Capitol and other notable sites is a branch of Pi Pizza. To be precise, it’s at 7137 Wisconsin Avenue Bethesda, MD 20814. Date: November 5th (next Saturday). Time: 6pm. Here is the discussion thread where you can confirm your attendance. Bring your webOS and LuneOS devices, discuss developments and the future and exchange tips on keeping your phones and tablets alive and functional. This meet up is organised by Alan Morford. Among the devices present will be a Windsornot, TouchStone 2 and a 64GB TouchPad Go. 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. Original Image: Jimmy Emerson, DVM. CC BY-NC-ND 2.0 Related posts: webOS meetup, Chicago, 27th November webOS meetup, Chicago, 23rd November webOS meetup, Chicago, 22nd November View the full article
  15. I bet you’ve seen topics on webOS Nation forums and our article here on pivotCE about Making Android More Like webOS. Well, webOS Nation forums user, Shuswap, just kicked it up a notch. He recently shared with me on Twitter that he’d made a pretty sweet Android mod to mimic webOS. I asked for a tutorial and he obliged! Read on for his great work and get ready to webOS-ify your Android! Overview This is a guide to adding webOS-style features to your Android device, complete with gesture area, gestures, and icons. Here is a quick video demonstrating the result: The tutorial below explains the process step by step. It assumes that you already know how to flash a ROM. In order to proceed, you will need to be running the Dirty Unicorns ROM, and will need several applications from the Play Store: Nova Launcher, GMD Gesture Control Lite, Wave Launcher, and Roundr. Before we webOS-ify… Before you can set up a webOS-ified Android, you need to do the following things: MAKE A BACKUP and then flash the Dirty Unicorns ROM (and a set of GAPPS, if you want them – if you don’t, you’ll have to find alternate methods of downloading Nova Launcher and GMD Gesture Control Lite). Note: first boot can take a very long time. Be patient.You need Dirty Unicorns specifically, because it has the Fling navigation bar, which you will use to create the gesture area. Check the supported devices section at http://dirtyunicorns.com/ to find out if they support your device. Downloads are available at the site as well, but it’s a good idea to check out the XDA thread for Dirty Unicorns on your device. The thread for the Nexus 4 is here: http://forum.xda-developers.com/nexus-4/orig-development/rom-dirty-unicorns-mako-edition-t3326301. After installing the ROM, proceed through the initial device set up and log into your Google account for Play Store access. Install Nova Launcher. Install GMD Gesture Control Lite. Install Wave Launcher. Install Roundr. Install a file manager. (Alan talking…I like Cyanogenmod’s File Manager which you can get by installing Cyan Apps or the immensely popular ES File Explorer is pretty good too.) Get the webOS icons and wallpaper you need. You can harvest them from a webOS device or doctor. There’s a good discussion at http://forums.webosnation.com/webos-discussion-lounge/325891-default-icon-location.html, and there are more icons in the app folders in /media/cryptofs/apps/usr/palm/applications/. Alternatively, you can find the icons online. See http://webos-ports.org/wiki/Graphics_Work and http://www.veryicon.com/icons/system/palm/. I found the launcher up-arrow icon in this set: http://flamemo.deviantart.com/art/Palm-web-OS-icons-122466330. The white line for the gesture area is here: http://imgur.com/a/sE5QS. You can find the wallpaper you want with a quick google search, or copy it from your webOS device. (Alan again…webOS backgrounds). Put the icon images and wallpaper in the “pictures” folder on your device. Step 1: Change the Launcher and Wallpaper Enter the app drawer. Go to Settings > Home and choose “Nova Launcher.” Press the arrow in the top left to return to settings. Select Display > Wallpaper > Gallery and navigate to the folder in which you saved your wallpaper. Agree with permissions dialogs if any appear. Press “Set wallpaper” at the top left of the screen. Back out of settings to the home screen and push the home button to start Nova Launcher. Step 2: Set the Swipe Up Gesture Enter the app drawer. Select the GMD Gestures App. Grant root access. Select the “Home” gesture (the top one). Select “Pinch Points” and change it to “Swipe UP.” Select “4 Touch Points” and change it to “1”. Press Okay. Select “Anywhere” and change it to “Bottom Border.” Select “Advanced Options” and make sure that “Active On Keyboard” is toggled on. Hit the arrow in the top left to go back one screen. Press the check mark in the top right of the screen to save your changes. Press and hold “Back” and select “Remove.” Repeat for all other actions (except “Home”). Select the three dots at the top right of the screen. Choose “Device Setup.” Set the Border Size to 10mm. Reduce the Gesture Size Adjustment to somewhere around -30. Press the check mark in the top right of the screen to save your changes. Select the three dots at the top right of the screen. Choose “Settings.” Select “Notification.” Choose “Hide Notification.” Select “Gesture Toast” and choose “None.” Under “Gesture Vibration,” you might want to slide the slider all the way to the left to get rid of the haptic feedback. Exit the app. Enter the app drawer. Go to Nova Settings > Gestures & inputs > Home button and select “App drawer.” Step 3: Create the Gesture Area Go to Settings > Dirty Tweaks > Navigation > Navigation Bar. Select “Navigation mode.” Choose “Fling” Select “Fling settings.” Select Right short swipe > Select custom action > Home Select Left long swipe > Select custom action > Back (“Left short swipe” should already be set to “Back.”) Select Single Tap Right > Select custom action > Recents Select Single tap left > Select custom action > Recents Select Right long swipe > Select custom action > No action Select Long press right > Select custom action > No action Any other gestures should be set to “No action.” Toggle off “Animate logo” Select “Custom logo image” and navigate to the folder where you placed the white line image for the gesture area. Toggle off “Show ripple” Toggle off “Enable gesture trails” Exit the app. Enter the app drawer. Select Nova Settings > Look & feel. Toggle off the “Transparent notification bar” setting. Exit Nova Settings. Step 4: Set up the Dock and Customize the Icons If you long press (press and hold) and then drag the icons on the dock, you can rearrange them. Move the app drawer icon to the far right. It may try to combine with another app icon and create a folder. Just keep moving it around until the other icons slide over to make room. If you long press the icons, a menu will appear. Long press the app drawer icon. Select edit. Tap the icon to the left of the App label. Select “Gallery apps.” Choose “Gallery.” Navigate to folder where you placed the up-arrow launcher icon for the app drawer. Select the launcher icon. Press “Done.” Press “Done” again. Long press and remove any unwanted app shortcuts from the dock. Long press and remove unwanted app shortcuts from the desktop. Wait to add any new shortcuts to the dock until later (step 19). Enter the app drawer and select Nova Settings > Dock > Dock Background. Set “Shape” to Rectangle. Under “Content” choose “Tint.” Select the blue-grey color (top row, second from left). Set the “Transparency” slider to around 70%. Exit “Nova Settings.” Enter the app drawer. Long press and drag to “Edit” at the top right any app you wish to change the icon for. Select “Gallery apps.” Choose “Gallery.” Navigate to folder where you placed the icon. Select the icon. Press “Done.” Edit the App label if necessary. Press “Done” again. Repeat for each icon you wish to alter. When you have finished editing the icons in the app drawer, long press and drag to the dock any icon you want on the dock. Step 5: Change the App Drawer Appearance Enter the app drawer. Select Nova Settings > App & widget drawers. Toggle off “Frequently used apps” Scroll down and select “Background” Select the blue-grey color (top row, second from the left) Select “Background” again. Set the “Transparency” slider to 7%. Backswipe in the gesture area to exit. Scroll down and select “Transition Animation.” Select “Slide up.” Press “Done.” Scroll down and toggle off “Search bar” Exit the app. Step 6: Clean Up the Desktop Enter the app drawer. Go to Nova Settings > Desktop. Toggle off “Persistent search bar” if necessary. Select “Page indicator.” Choose “None.” Exit the app. On the desktop, press and hold the Google search bar. Choose “Remove.” If additional icons or widgets appear on the desktop as a result of the above steps, press and hold them, and select “Remove.” Step 7: Move the Status Bar Clock Enter the app drawer. Go to Settings > Dirty Tweaks > Status Bar > Clock & date > Alignment. Select “Center clock.”Step 8: Eliminate Haptic Feedback (Vibration on Touch Events) (Optional) Enter the app drawer. Go to Settings > Sound & notification > Other sounds. Toggle off “Touch sounds” and “Vibrate on touch” if desired. Go to Settings > Language & input > Android Keyboard > Preferences. Toggle off “Vibrate on keypress.” Step 9 Set Up Wave Launcher Open Wave Launcher. Back swipe. Select settings. Ensure that the boxes for “Enable on startup” and “Soft keyboard has precedent” are both checked. Select “Number of apps.” Set to five (or the number of shortcuts you have in the dock). Scroll down and de-select “Auto advance on edit.” Back swipe to return to the main setup screen. Select “Calibrate.” Set the size and location of the launch trigger (shown in pinkish red). I set mine to the bottom left, so that it’s unlikely to be accidentally triggered. Back swipe to return to the main setup screen. Select “Edit wave.” Select the apps for each position. I mirrored my dock apps, so that it is most like webOS. After you have chosen an app, you can long press the icon on the wave launcher to bring up a menu and change the icon to match the customized icons on the launcher. If you want the app tray shortcut in the far right position, when you’re adding that shortcut, select the up-right arrow to the right of the android robot. Scroll down through the list and select “Nova Action” and then “App drawer.” Long press the icon on the wave bar and proceed to change the icon to the webOS launcher icon. Back swipe to return to the main setup screen. At this point, you may want to change the wave launcher transparency to match that of the dock. If so, select “Edit Colors” and adjust the slider marked “A” to your preferred setting. Exit the app. Step 10: Configure Roundr Enter the app. You might have to toggle “Enable Roundr” off and on to get the app to start the first time. Ensure that “Start on boot” is checked. Set the corner radius. Using my Pre3 as a guide, I set the corner radius at 18 on my LG G2, but different screen dimensions may call for a different setting. Uncheck “Hide on KitKat home.” Back swipe to exit the app. Step 11 (Optional, if you have Nova Launcher Prime): Create Tabs in the App Drawer (Alan again…Prime is totally worth it!) If you have the paid version of Nova Launcher, you can set up multiple tabs in the app drawer by going to Nova Settings > App & widget drawers and toggling on “Tab bar.” Select “Menu action icons” and uncheck all the choices. Press “Done.” Scroll down and select “Drawer groups” to create tab sections. After you create the groups, select each group, and use the check boxes to choose which apps to assign to the group/tab. You can also assign individual apps to tabs from the app drawer. Just enter the app drawer and long press and drag app icons to “Edit” at the top. You can assign the app to a particular group/tab in the edit dialog. Interested in Additional Tweaks? There are alternative, customizable task-switchers in Settings > Dirty Tweaks > Multi-Tasking > Recents. Unfortunately, neither provides a webOS-style card interface. Rather, they display running apps in a slide-out pane. I found that both the “OmniSwitch” and “slim recents” task switchers caused unwanted interference with the webOS-style gestures, but you may have better luck. If you discover a webOS-style card-based Android task switcher, you are obligated to report it in the forums at webOS Nation! Related posts: Making Android More Like webOS Guide: Coming (Back) to webOS in 2014, Part 1 Guide: Coming (Back) to webOS in 2014, Part 2 View the full article from pivotCE