Table of Contents
Copy in Files
First, you need to copy all of the PNGs for your icon pack into the
You can remove the placeholder PNGs that are already in there initially. If you plan on using the home page,
ic_web.png with a large version (preferably 512x512) version of your launcher icon.
Polar has file naming conventions which allow you to specify how the app's name will be displayed in the dashboard. Here are the rules:
- No changes: the first letter of the name will be capital.
- Single underscores: will become a space in the middle of a word, the next letter is capital. If it's placed at the beginning of the name, it makes the first letter lowercase.
- Double underscores: no space, makes the next letter capital.
- Triple underscores: makes the next word all capital.
Here are some samples:
- betternet.png will become Betternet
- google_chrome.png will become Google Chrome
- pay__pal.png will become PayPal
- _kaip.png will become kaip
- ___kaip.png will become KAIP
- ___npr_one.png will become NPR One
- material___os.png will become MaterialOS
drawable.xml file is located at
You need to make sure they are both updated at all times! This file is used by launchers, and the dashboard
to retrieve icons in your pack (along with categories they belong to).
This file is optional. If you want the dashboard UI to display different icons (or icons in a
different order) than
what you want to display to launchers, you can add a
which has the same structure
The appfilter.xml file is located at
You need to make sure they are both updated at all times! This is the most important file for an icon pack.
by launchers to associate your PNGs with actual apps. This file can also be used to apply masks along with
various configurations. There are apps like ApplicationReader
Mike Penz which can aid in finding
ComponentInfo for apps. But the
most efficient way to get a list of ComponentInfos to put in your appfilter would be to use the Icon Request
within Polar since it can do batch selection and email them to you.
The theme_resources.xml file is located at
/assets/theme_resources.xml. It's highly recommended that they are updated at all times (to
avoid upsetting your users)!
This file is very similar to appfilter.xml, however it's vital to have support for LG Home.
appfilter.xml, it contains icon-to-component associations, but it also contains info
like wallpapers, theme previews, etc. which are used by LG Home.