Quantcast
Jump to content

[pivotCE] Guide: Saving Apps From The App Catalog Part 1: nodeleteipk patch


pivotCE

Recommended Posts

The time has come; HP has finally shut off the App Catalog payment service. This means that as of November 1, you can no longer purchase new paid apps from the App Catalog. However, you can still download apps that you have previously purchased and can acquire new free apps until January 15th. After that point, the App Catalog will be gone for good (at least the official one will…) and you’ll have no way to restore your apps. So, you’ll want to make sure that you’ve backed them up. This guide will walk you through the primary app backup method: saving IPKs when you download and update apps.

There are several ways to backup in webOS. Since this is just one of them, expect subsequent howto articles on other methods.

What is an IPK?

Named for their file extension (.ipk), an IPK is a package that contains all of the bits that make up an app, as well as all of the information necessary to successfully install the app on a webOS device. Its name includes the company’s name, the app name, the version of the app and the device architecture (ie. the IPK file for the latest version of the phone Facebook app is named com.palm.app.facebook_1.5.62_all.ipk). “com.palm.app” represents the company (Palm/HP), facebook represents the app name, 1.5.62 is the version of the app, and all of it means that this is a package that will run on all architectures that webOS will support.

When you download an app (either paid or free) from the App Catalog, your device will download the IPK from HP’s servers, install the app, and then remove the IPK so that it doesn’t take up extra space.

Why this method of backup?

This method is the preferred method because it allows you to take a backup of the “cleanest” version of the app – the package issued directly from the manufacturer. Other methods will attempt to rebuild the IPKs using data from an already installed app, so you run the risk of it not working quite right, especially if the app does something quirky as part of its setup process. So, they should only be relied upon if the IPK is not available from the App Catalog, or if you will lose critical data and do not have another device that you can download the IPK to.

Let’s Get Started

This guide assumes that you have followed the instructions in

link hidden, please login to view
, and that your device is ready for patching. Please note that we will be using webOS Quick Install for this process as Preware does not support installing patches that don’t come from an official feed.

Here’s what you have to do:

  1. Download and install the nodeleteipk patch.
  2. Check App Availability.
  3. Delete Apps.
  4. Re-download Apps.
  5. Save downloaded IPKs.

Step 1: Get the nodeleteipk patch

Typically, after installing an app, the App Catalog will delete the IPK that it came from. However, early last year, forum user GMMan learned that there was a configuration file option that would tell your device not to delete the IPK, allowing you to keep it for backup. He put together some detailed instructions, and also built a patch to make things nice and easy.

To install this patch:

  1. Download the patch from the first post of  and save it to a place that you can access.
  2. Plug your device into your computer and when asked if you want “USB Mode” or “Just Charge”, pick “Just Charge”.
  3. Launch webOS Quick Install.
  4. Make sure that your device shows up in the upper right hand corner. If this is your first time running the tool you may be asked to install novacom drivers. These are what the tool uses to communicate with your phone. In that case, just follow the prompts.
  5. Click on the green plus icon on the right hand side of the window, navigate to the file that you downloaded, and hit select.
  6. Click the “Install” button and wait for the tool to install the package. When it is done, the list of files to install will be empty, and you’ll be good to go.

Step 2: Check App Availability

In the meantime since you originally purchased the app, it may have been pulled from the App Catalog. Open the App Catalog app on your device and run a search for each app that you plan to back up. If the search comes up empty, the app has been pulled for some reason and is no longer available. DO NOT DELETE IT FROM YOUR DEVICE. There are other methods of backing up these apps, which will be covered in a later guide.

If you do find it, you are good to proceed.

Step 3: Delete Apps

NOTE: Deleting an app will remove all of it’s data from your device. This means that you will lose data such as game progress, logins, settings and other data when you remove it. Make sure that the application’s data is backed up before you delete it. If you do not have a way to back up the application data, there are other methods of backing up these apps, which will be covered in a later guide. As a start check out .

For each app that you plan to re-download, delete it. This can be done by:

  1. Opening the “Software Manager” application
  2. Scrolling to the application that you wish to delete
  3. Swiping right to delete
  4. Confirming that you would actually like to delete the app from the dialog.

On a phone you can also hold down the Opt key and touch the app you want to delete. A confirmation pop-up will appear. TouchPad users can also delete applications by holding their finger down on the application icon until a little “x” appears. They can then tap the “x” and confirm that they want to delete the app.

Step 4: Re-download apps

Open up the App Catalog app, search for any apps that you would like to re-download, and tap the download button beside them (on TouchPad) or open up the app’s details page and tap download (other devices). This will trigger the app to start downloading and installing, while saving the IPK.

Step 5: Save Downloaded IPKs

At this point, you should have a collection of IPKs stored on your device representing all of the apps that you wanted to save.

Plug your device into your computer, and when asked if you want “USB Mode” or “Just Charge”, pick “USB Mode”. The USB Mode icon will appear on your device’s screen, and a new drive with your device’s model name will appear where your USB drives normally do. (Desktop for Mac users, My Computer for Windows users).

Open up this drive and navigate to the “downloads” directory. This is where everything that your device downloads, including IPKs, gets stored. Copy any file that ends in IPK to your computer as a backup, and I also recommend copying them to an additional place, such as a CD/DVD, flash drive, or cloud storage drive, as a further backup.

At this point, you’re done. You’ve successfully backed up your apps, and can delete the IPKs from your device to clear up some storage space. Just make sure that they’re kept in a safe place in case you ever need them.

What’s Next?

Preware and webOS Quick Install allow you to take IPKs that you backed up from the App Catalog or downloaded from other sources (such as homebrew) and install them on your device, meaning that you will be able to reinstall your apps after the App Catalog shuts down.

In the meantime, you have two and a half months to get anything that is both free and interesting from the App Catalog. Download and back up whatever you can.

While will continue to be available through the , for most of these apps, when January 15th rolls around, they will be gone for good. Save them while you can.



Link to comment
Share on other sites

  • Similar Topics

    • By svsrama
      Hi,
      I have my LG 4K Smart TV -Model : 43UJ632T.
      I could not able to use the Wireless Keyboard ( Logitech K230) with Builtin Apps like Youtube, Amazon Prime or in Netflix to search. I could able to use only thru Magic Remote. 
      But the same Keyboard is working fine in Google Movies & SunNXT apps.
      Could you please help me in fixing the same.
      Thanks,
      Sriram.
    • By pivotCE
      Sooo that was a really long time since a release, but
      link hidden, please login to view are still around and active as ever! We have continued making updates and producing testing images. But a lot happened that resulted in us not putting out a proper release out in the past few years.
      Those who have stayed in touch with the community will know there has been some turmoil with the closure of the webOS Nation forums last year. Things stabilised over the last year as people converged around the and made plans on the associated . Much of the old information from webOS Nation was preserved thanks to the and can still be accessed, if imperfectly. We have now set up a that largely replicates the old layout and is ready for fresh content.
      If you are eager to find out what we’ve been working on and to try out the new release, read on…
      The (Jenkins) builder infrastructure we had available previously decided to have a number of malfunctions, leading it to be no longer available to us. So for now we’re back to our own builders for building all the images, which isn’t great, but at least we’re still building and providing images! We are now using , which means newer base components like systemd, pulseaudio and wayland.
      Since the last release LuneOS has gone through a major rework under the hood. To summarize:
      We moved from Qt5 to (6.5.2 included in this release). We have moved away from our own compositor (luna-next) to the one provided by LG in called luna-surfacemanager. We are now using LG’s WAM (WebAppManager) instead of our own custom one together with LG’s fork of Chromium (94). A major rebase of all components shared with webOS OSE to be based on the now. This included a migration to Enhanced ACG which provides a lot tighter security for LS2 calls from apps and services. This all was an enormous amount of work behind the screens but little visible to the end user, however this does offer clear benefits going forward being:
      A shared code-base with LG, which means less custom components and maintenance. Years of field tested code on LG production devices which offers more stability. In this process we were able to keep backwards compatibility for apps and services. Easier to upgrade to latest OSE components, since we have migrated almost all remaining components that were still not based on the latest webOS OSE or on Open webOS. (125 components were migrated in total, 15 components are still to be migrated). In the meanwhile we have also been working hard to support the newly released devices such as the PinePhone, PinePhonePro and PineTab2 which are affordable devices which can run a very close to mainline kernel and a multitude of OS-es. We now support booting off on Pinephone.
      The new close to mainline kernel for the Pine64 devices allows them to run things like out of the box!
      All other supported Android devices are now based on 9.0.
      So what is ahead for the near future?
      Our focus will be on the mainline devices and emulator (), however we will try to keep support for the Android/Halium based targets as well.
      Upgrade to latest Chromium 108 released by LG recently Work on audio & multimedia infrastructure provided by webOS OSE to get it working in LuneOS Work on camera infrastructure Try to get a mainline kernel working for Tenderloin, Hammerhead, Mido and Tissot. Improve/add QML components and add new basic apps to be used such as Camera, Flashlight, Audio Player, Video Player Piggyback off some of the work done by the . Provide a GSI image for newer Android (9.0+) based devices, this would allow a standard image to boot on most modern Android devices v.s. building a device specific one for each device. Known issues:
      Battery usage is on the high side No audio in webapps (we decided not to spend time on this, seeing we plan to update Chromium soon anyway) The Usual:
      Sign up for. Get involved and [ UPDATE https://pivotce.com/2014/09/22/webos-ports-help-wanted/ ] Feel free to download the updated builds to get started. Currently supported targets: PinePhone, PinePhonePro, PineTab2, Qemux86-64 (Virtualbox), all with mainline kernel. Tenderloin, Hammerhead, Tissot, Mido, Rosy, Mako (Android 9.0/Halium based with their respective Android kernels (3.4 and newer)). RaspberryPi 3 and RaspberryPi4 might work too, however we haven’t tested this ourselves.
      . And remember we don’t do timelines.
      Don’t forget to contact us with any questions and feel free to join the discussion on the . Catch us on Twitter @webosports on IRC: Libera:#webos-ports, or email [email protected].
      We will see you shortly again with a new release!
      Picture credit: from Pixabay
      The post first appeared on . Related posts:

    • By pivotCE
      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
      link hidden, please login to view and/or 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  to see current issues. Find an area where you think you can help and then find us on or (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 , 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 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: 
      IRC (Libera):
      Telegram:
      Issue Tracker: 
       User Support Forums
      Join the forum .
      The post first appeared on . Related posts:

    • By pivotCE
      Have you been wondering what LG will do with webOS next?
      According to
      link hidden, please login to view, a since pulled website has arisen (here are the cached pages from Google  and ) detailing info about LG’s all new platform supposedly called ““. It is thought that this is going to rival Samsung’s Tizen, maybe even in retaliation to Apple’s new smart watch. Hopefully our loyal fan-base will make it popular! According to pictures pulled from the site (see below), the SDK for the said smart watches, will supposedly be released with the announcement of LG’s plans to move webOS to the Smart watch platform. To see the other banners pulled from the site click
      .


    • By AlP
      Please add above apps to WebOS
×
×
  • Create New...