Introduction
- Build your setup project. Open the setup.exe file use just build, File - Open - File. Right click the Icon node in the file explorer window and choose the Add Resource. Import the icon your want in the popup dialog, and make sure the ID of the icon is the smallest one. Hope this helps.
- Download 2,414 setup icons. Available in PNG and SVG formats. Ready to be used in web design, mobile apps and presentations.
Auto Repair Near You: Check out these coupons and discounts for an auto repair shop near you and save up to 50-90%! Synthetic Blend, or Full Synthetic Oil Change at Meineke Car Care Center (Up to 49% Off). Oil Change Services at Valvoline Instant Oil Change (Up to 44% Off). Within a few click, you can change many elements in social login like text, color, background color, image. Text - Color - Background Color - Background Image - Icon ### Adjust Social Login Buttons Order Fast & Easily Easily arrange social login buttons order and see changes immediately by dragging and dropping icons.
The launcher icon for your app (sometimes called an 'app icon') is the icon that a user taps to start your app. For commonality with Android, starting in Fire OS 5, Amazon uses icons from your APK. (This is a change from earlier versions of Fire OS, where the launcher used the launcher icon that you uploaded to the developer portal when submitting your app.)
As you create your launcher icons, be aware of the following guidelines and troubleshooting. Note that the following sections apply to Fire OS 5 and Fire OS 6.
Scaling
The launcher avoids scaling launcher icons, unless absolutely necessary. To display large and crisp icons on a device, the launcher fetches the icon with a density higher than that of the device.
Icon size and densities
Create a version of your icon at each of the following dimensions and include the images in your APK. Make sure that your icons are in the appropriate res folders so that the launcher can find them:
| Generalized density | Icon dimensions | Res folder | Requested by |
|---|---|---|---|
| xxhdpi | 144px x 144px | drawable-xxhdpi | xhdpi Amazon devices |
| xhdpi | 96px x 96px | drawable-xhdpi | tvdpi, hdpi Amazon devices |
| hdpi | 72px x 72px | drawable-hdpi | mdpi Amazon devices |
Icon File Format
Provide the images for your launcher icons in 24-bit PNG format.
Troubleshooting Your Launcher Icon
If your launcher icon is not displaying as expected, consider the following:
Problem: The wrong icon is displayed or the icon is scaled up or down and looks bad.
Solution: If you provide the launcher icon for a configuration such as drawable-large-mdpi, Android resource-resolution rules might select the icon from that folder instead of the appropriate folder.
See the Android documentation here for the Android resource resolution algorithm.
To help ensure that the launcher selects the correct icon, only include icons in the resource folders listed in the table on this page.
Problem: Your drawable-* folder was removed in build-time APK optimization.
Solution: Some tools build an APK for a specific density and remove other drawables. For example, the tools might remove the drawable-xxhdpi folder, even though Amazon uses the xxhdpi icon file on xhdpi devices. To help avoid this issue, use a mipmap-* pattern for folder names instead of drawable-*:
- mipmap-hdpi: 72px
- mipmap-xhdpi: 96px
- mipmap-xxhdpi: 144px
Fire OS 6 Device Support Table
The devices in the following table all run or support running Fire OS 6, which is based on Android N (Android 7.1.2, API level 25):
| Device | Fire OS 6 Source | General density | Density of fetched launcher icon |
|---|---|---|---|
| Fire 7 (2019) | Stock OS | mdpi | hdpi |
| Fire HD 8 (2018) | Stock OS | hdpi | xhdpi |
Fire OS 5 Device Support Table
The devices in the following table all run or support running Fire OS 5, which is based on Android 5.1, API level 22:
| Device | Fire OS 5 Source | General density | Density of fetched launcher icon |
|---|---|---|---|
| Fire HD 10 (2017) | Stock OS | hdpi | xhdpi |
| Fire HD 8 (2017) | Stock OS | tvdpi | xhdpi |
| Fire 7 (2017) | Stock OS | mdpi | hdpi |
| Fire HD 8 (2016) | Stock OS | tvdpi | xhdpi |
| Fire HD 10 (2015) | Stock OS | mdpi | hdpi |
| Fire HD 8 (2015) | Stock OS | tvdpi | xhdpi |
| Fire (2015) | Stock OS | mdpi | hdpi |
| Fire HDX 8.9 (2014) | OTA update | xhdpi | xxhdpi |
| Fire HD 7 (2014) | OTA update | hdpi | xhdpi |
| Fire HD 6 (2014) | OTA update | hdpi | xhdpi |
Legacy Device Support for Older Versions of Fire OS
The following table lists Amazon's legacy tablet devices and the corresponding OS supported by these devices.
| Device | Fire OS version | Screen resolution | General density |
|---|---|---|---|
| Fire HD 7 (2014) | Fire OS 4—based on Android 4.4.2, API level 19. Receives Fire OS 5 OTA update. | 1280px x 800px (supports 720p 'HD' resolution) | hdpi |
| Kindle Fire HDX 8.9' (2013) | Fire OS 4 (system update, available Nov 2014)—based on Android 4.4.2, API level 19 Fire OS 3—based on Android 4.2.2, API level 17 | 2560px x 1600px (supports 1080p 'HD' resolution) | xhdpi |
| Kindle Fire HDX 7' (2013) | Fire OS 4 (system update, available Nov 2014)—based on Android 4.4.2, API level 19 Fire OS 3—based on Android 4.2.2, API level 17 | 1920px x 1200px (supports 1080p 'HD' resolution) | xhdpi |
| Kindle Fire HD 7' (2013) | Fire OS 4 (system update, available Nov 2014)—based on Android 4.4.2, API level 19 Fire OS 3—based on Android 4.2.2, API level 17 | 1280px x 800px (supports 720p 'HD' resolution) | hdpi |
| Kindle Fire HD 8.9' (2012) | Based on Android 4.0.3, API level 15 | 1920px x 1200px (supports 1080p 'HD' resolution) | hdpi |
| Kindle Fire HD 7' (2012) | Based on Android 4.0.3, API level 15 | 1280px x 800px (supports 720p 'HD' resolution) | hdpi |
| Kindle Fire (2nd Gen) | Based on Android 4.0.3, API level 15 | 1024px x 600px | mdpi |
| Kindle Fire (2011) | Based on Android 2.3.3, API level 10 | 1024px x 600px | mdpi |
Last updated: Oct 29, 2020
Introduction
Running SABnzbd as a Windows Service can be helpful to those needing the program to operate in an 'always on' state. When installed this way, SABnzbd will start automatically as soon as Windows starts, even when no user account is logged in, and will remain running even when all users have logged out.
NOTE While the functionality of SABnzbd is generally the same when running as a service, there are some restrictions and limitations. Most importantly, you will need to take additional steps after installing the service if you use network shares for your download folders. Details on these steps, and other considerations when running SABnzbd as a service, can be found after the basic installation instructions, below.
Basic Installation
The following procedure will install SABnzbd as a service using the same settings used by the graphical web-based interface. This should satisfy most users' needs, but if you need to run the service with different settings than those used in the web interface, please read through the 'Specifying additional options' section that follows this section before proceeding.
- Open a DOS window with Administrative (elevated) privileges
- Click your Windows Start button
- Type
cmd - Right click 'Command Prompt' in the search window and choose 'Run As Administrator' in the drop-down menu that appears.
Access the directory in which you installed SABnzbd.
If you installed SABnzbd in its default location (C:Program FilesSABnzbd) just type (or paste) the below command exactly as it appears, then hit the RETURN key. If you installed it to a different drive or folder, however, make sure to edit the path to reflect that location.Install SABnzbd service, set it to automatically start, and launch it, by typing or pasting the below commands into the DOS command window and hitting RETURN after each.
NOTE The first command uses the
%localappdata%system variable to point to the LOCAL folder within your user's APPDATA folder, which should work on all versions of Windows. If for some reason that does not work on your system and you get asabnzbd.ini file not foundtype error you will need to replace the path portion of the above command to explicitly point to yoursabnzbd.inifile within yourC:UsersUSERNAMEAPPDATALocalsabnzbdfolder.NOTE If you used Powershell instead of Command Prompt you will need to use
$env:LOCALAPPDATAinstead of%localappdata%!
That’s it! SABnzbd is now installed and running as an 'always on' service!If all you need is to run SABnzbd as a service using the same settings used in the SABnzbd web interface-and you are not using network shares for your downloaded files-your work here is done.
However, if you want to customize the way that the service runs, or if you need to have SABnzbd access shared drives across the network, please read through the following sections for further information.
- NOTE SABnzbd will not present an icon in the Notification (lower right) area of the Windows screen when run as a service. This will not affect normal operation of the software.
- NOTE The Windows firewall will not warn you if it blocks SABnzbd as it does when blocking SABnzbd when running 'normally', so you may need to add it to the firewall exception list using the normal procedures for your version of Windows if you run into an access problem. However, if you have already run SABnzbd successfully before installing it as a service, using the same port number, it is likely the exception will already be in effect.
- NOTE Before upgrading SABnzbd, it is recommended you stop both services to ensure there are no problems overwriting busy files. See the section below for details on stopping the service via the command line or through the Windows Service Manager.
Specifying additional options
By default, installing SABnzbd as a service (as detailed in step 4 of the above installation instructions) will cause it to run using the same settings used by the SABnzbd web interface on your system.
You can, however, override many of these settings with command line parameters. Simply add the pertinent command to the line that installs the SABnzbd service. Be aware that not all of the available command line options are appropriate when SABnzbd is running as a service—for instance, parameters like –b (start browser) will be ignored even if specified.
NOTE Any parameter you set in the command line will override the equivalent parameter in the web interface and any changes to the interface settings will be ignored by the service for that parameter. For parameters not set through the command line, the service will use whatever was set in the GUI at the time the service is launched or updated.For example, the following will install the SABnzbd service with the -s host:port command to reflect a different server address:
In this example, the SABnzbd service will continue to use the specified port (8081) even if you subsequently specify a different port within the web interface. You would need to reinstall the service by re-entering the above command without the -s 127.0.0.1:8081 argument to have the SABnzbd service once again go back to using the value set in the web interface.
Updating the service settings
Each time the SABnzbd service starts, it reads the SABnzbd ini file for configuration options. If you change settings within the SABnzbd web interface you can force the service to reread the ini file by typing the following the command in an elevated DOS command window after changing directories to the SABnzbd folder. Of course, you can also simply reboot the computer to cause the service to restart and reread the ini file again.
Service actions
Removing the services
Change Setup Icon Advanced Installer Coupons
To completely remove the SABnzbd services, follow steps 1 and 2 in the Installation instructions above to open an elevated DOS command window and access the SABnzbd folder, then type or paste the following commands into it, hitting RETURN after each.
Software Installer Icon
Start the services
Stop the services
How To Use Advanced Installer
Enabling Network Share Access
By default the SABnzbd service will be installed to run as the 'Local System' account. This allows full access to local hard drives, but not to network shares.If you are using network shares within SABnzbd to save or process your downloads, the main SABnsdb-server service must run as a local user account with network privileges instead of 'Local System'. Here’s how to make that change:
- Install SABnzbd as a service using the instructions in the above Installation section.
- Launch the Windows Service Manager utility. (Typically that’s done by typing SERVICES into your Windows Start menu’s search and choosing SERVICES from the results list)
- In the Windows Services Manager, find the SABnzbd-service (it will be displayed as 'SABnzbd Binary Newsreader') in the list of services and double-click it to access its settings.
- Click the Logon tab.
- Specify a different 'Log on' account. (Make sure it is one that has administrative privileges and access to network shares).
- Apply the changes and close the Service Manager window.
NOTE When using network shares with the SABnzbd service, you must use network (UNC) paths (servershare) instead of drive letters (P:).
NOTE Even after doing the above to enable network share access, you will still be restricted to local drives only for the admin, log and incomplete folders due to limitations in those functions. Make sure, in your SABnzbd web interface configuration that those folders are not pointing to network shares.