Archive:Android FAQ: Difference between revisions
Jump to navigation
Jump to search
>NedBot m (Robot: Cosmetic changes) |
|||
Line 4: | Line 4: | ||
{{-}} | {{-}} | ||
==General FAQ== | == General FAQ == | ||
:<big>''See also: '''[[XBMC all platforms FAQ]]''' for FAQs that apply to all versions of XBMC.''</big> | :<big>''See also: '''[[XBMC all platforms FAQ]]''' for FAQs that apply to all versions of XBMC.''</big> | ||
{| width="100%" | {| width="100%" | ||
Line 12: | Line 12: | ||
| Question= Will this really do 1080 and all that stuff the desktop can do? | | Question= Will this really do 1080 and all that stuff the desktop can do? | ||
| Answer= | | Answer= | ||
*Yes! This is a full port of XBMC! It is not a thin client or lite version! | * Yes! This is a full port of XBMC! It is not a thin client or lite version! | ||
:: {{note|Hardware video decoding support is very limited right now, so most devices will have to use software decoding. Expect support for hardware decoding to improve with time.''}} | :: {{note|Hardware video decoding support is very limited right now, so most devices will have to use software decoding. Expect support for hardware decoding to improve with time.''}} | ||
*The initial aim for the Android port is to get XBMC working on inexpensive Android set-top-boxes. Phones and tablets will be supported as well for those who want XBMC on-the-go. | * The initial aim for the Android port is to get XBMC working on inexpensive Android set-top-boxes. Phones and tablets will be supported as well for those who want XBMC on-the-go. | ||
}} | }} | ||
Line 22: | Line 22: | ||
| Answer= | | Answer= | ||
{{Main|HOW-TO:Install XBMC for Android}} | {{Main|HOW-TO:Install XBMC for Android}} | ||
*<big>'''Special test builds (official and unofficial) for hardware video decoding and more can be found on the [http://forum.xbmc.org/forumdisplay.php?fid=184 Android testing forum]'''. </big> | * <big>'''Special test builds (official and unofficial) for hardware video decoding and more can be found on the [http://forum.xbmc.org/forumdisplay.php?fid=184 Android testing forum]'''. </big> | ||
*If you've bought a device that was advertised to run XBMC, such as the Pivos XIOS, G-box, MiniX Neo, etc, then you should check with their respective websites for a final v12 Frodo build. Many of these devices need specific builds for hardware decoding and won't work correctly with the generic build released on xbmc.org | * If you've bought a device that was advertised to run XBMC, such as the Pivos XIOS, G-box, MiniX Neo, etc, then you should check with their respective websites for a final v12 Frodo build. Many of these devices need specific builds for hardware decoding and won't work correctly with the generic build released on xbmc.org | ||
*A basic v12 build of XBMC for Android (APK) can be found here: http://mirrors.xbmc.org/releases/android/ . XBMC for Android will eventually come to the Google Play application store once there is support for more Android devices. | * A basic v12 build of XBMC for Android (APK) can be found here: http://mirrors.xbmc.org/releases/android/ . XBMC for Android will eventually come to the Google Play application store once there is support for more Android devices. | ||
*[[Nightly builds]] can be found here: http://mirrors.xbmc.org/nightlies/android/ | * [[Nightly builds]] can be found here: http://mirrors.xbmc.org/nightlies/android/ | ||
*Unofficial builds can be found here. These include non-neon builds (i.e., Tegra 2): http://forum.xda-developers.com/showthread.php?p=29737205 | * Unofficial builds can be found here. These include non-neon builds (i.e., Tegra 2): http://forum.xda-developers.com/showthread.php?p=29737205 | ||
}} | }} | ||
Line 33: | Line 33: | ||
| Question= Is XBMC for Android different from normal XBMC? | | Question= Is XBMC for Android different from normal XBMC? | ||
| Answer= | | Answer= | ||
*The current version of XBMC for Android is based on XBMC v12.1 [[Frodo FAQ|Frodo]], and is based on the same code as XBMC for all the other supported platforms. | * The current version of XBMC for Android is based on XBMC v12.1 [[Frodo FAQ|Frodo]], and is based on the same code as XBMC for all the other supported platforms. | ||
}} | }} | ||
Line 64: | Line 64: | ||
| Question= Add-ons and skins | | Question= Add-ons and skins | ||
| Answer= | | Answer= | ||
*XBMC for Android is a full version of XBMC and will be able to use all non-platform specific [[add-ons]] and [[skins]]. More feature rich (CPU demanding) skins like AEON Nox might not run smoothly on lower powered systems, so keep to "lighter" skins for those boxes. | * XBMC for Android is a full version of XBMC and will be able to use all non-platform specific [[add-ons]] and [[skins]]. More feature rich (CPU demanding) skins like AEON Nox might not run smoothly on lower powered systems, so keep to "lighter" skins for those boxes. | ||
*If you are using a touch screen device and the build you are using did not include it, you can manually instal [[Add-on:Touched]] for better touch screen support. | * If you are using a touch screen device and the build you are using did not include it, you can manually instal [[Add-on:Touched]] for better touch screen support. | ||
}} | }} | ||
Line 92: | Line 92: | ||
| Question= Google TV | | Question= Google TV | ||
| Answer= | | Answer= | ||
*Google TV devices are currently not supported. | * Google TV devices are currently not supported. | ||
}} | }} | ||
Line 99: | Line 99: | ||
| Question= Launching Android apps from within XBMC | | Question= Launching Android apps from within XBMC | ||
| Answer= | | Answer= | ||
*XBMC can launch other Android apps by going to "Programs" (on the home screen) and selecting the app you want to run. | * XBMC can launch other Android apps by going to "Programs" (on the home screen) and selecting the app you want to run. | ||
}} | }} | ||
Line 106: | Line 106: | ||
| Question= Automatically start XBMC | | Question= Automatically start XBMC | ||
| Answer= | | Answer= | ||
*You can automatically start XBMC when your Android device boots up using an application such as [https://play.google.com/store/apps/details?id=imoblife.startupmanager Startup Manager (free)] | * You can automatically start XBMC when your Android device boots up using an application such as [https://play.google.com/store/apps/details?id=imoblife.startupmanager Startup Manager (free)] | ||
}} | }} | ||
Line 113: | Line 113: | ||
| Question= Why can other players work with HD video but not XBMC? | | Question= Why can other players work with HD video but not XBMC? | ||
| Answer= | | Answer= | ||
*HD video (720 and 1080 resolution files) requires what's known as hardware video decoding, using special chips that handle video playback, in order to run smoothly on most ARM/Android systems. Some Android systems have powerful enough CPUs that they can playback some HD video without hardware decoding, but most will require it. | * HD video (720 and 1080 resolution files) requires what's known as hardware video decoding, using special chips that handle video playback, in order to run smoothly on most ARM/Android systems. Some Android systems have powerful enough CPUs that they can playback some HD video without hardware decoding, but most will require it. | ||
*Unlike most OSes, hardware decoding on Android isn't standard across different manufacturers and chip makers. | * Unlike most OSes, hardware decoding on Android isn't standard across different manufacturers and chip makers. | ||
*Hardware video decoding is still under very active development in XBMC for Android, and it is expected that XBMC will be able to support a large selection of devices. | * Hardware video decoding is still under very active development in XBMC for Android, and it is expected that XBMC will be able to support a large selection of devices. | ||
*Other players have hardware video decoding because they've signed NDAs or are using closed source code, which are not options for XBMC. | * Other players have hardware video decoding because they've signed NDAs or are using closed source code, which are not options for XBMC. | ||
}} | }} | ||
|} | |} | ||
==Troubleshooting== | == Troubleshooting == | ||
{{see also|Troubleshooting}} | {{see also|Troubleshooting}} | ||
{| width="100%" | {| width="100%" | ||
Line 139: | Line 139: | ||
The userdata folder and debug log is located on external storage/sdcard at one of the following locations (depending on your device): | The userdata folder and debug log is located on external storage/sdcard at one of the following locations (depending on your device): | ||
;[[userdata folder]] | ;[[userdata folder]] | ||
*/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/ | * /Android/data/org.xbmc.xbmc/files/.xbmc/userdata/ | ||
*/sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/ | * /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/ | ||
*/data/data/org.xbmc.xbmc/files/.xbmc/ | * /data/data/org.xbmc.xbmc/files/.xbmc/ | ||
*Be sure to have hidden folders set to be shown in your file explorer. | * Be sure to have hidden folders set to be shown in your file explorer. | ||
;[[debug log]] | ;[[debug log]] | ||
*/Android/data/org.xbmc.xbmc/cache/temp/xbmc.log | * /Android/data/org.xbmc.xbmc/cache/temp/xbmc.log | ||
*/sdcard/Android/data/org.xbmc.xbmc/cache/temp/xbmc.log | * /sdcard/Android/data/org.xbmc.xbmc/cache/temp/xbmc.log | ||
*/data/data/org.xbmc.xbmc/cache/temp/xbmc.log | * /data/data/org.xbmc.xbmc/cache/temp/xbmc.log | ||
}} | }} | ||
Line 156: | Line 156: | ||
| Question= How to hide the Android navbar | | Question= How to hide the Android navbar | ||
| Answer= | | Answer= | ||
*Since Android v4 (aka, Ice Cream Sandwich), Android has changed how their navigation bar works. On some Android devices that do not have physical buttons, the navbar cannot be normally hidden, but only "dimmed". Some Android set-top-boxes have this "no buttons" flag set, and will not hide the navigation bar when using XBMC or any other full screen videos. | * Since Android v4 (aka, Ice Cream Sandwich), Android has changed how their navigation bar works. On some Android devices that do not have physical buttons, the navbar cannot be normally hidden, but only "dimmed". Some Android set-top-boxes have this "no buttons" flag set, and will not hide the navigation bar when using XBMC or any other full screen videos. | ||
*'''To remove the navbar:''' | * '''To remove the navbar:''' | ||
**You can use "[http://ppareit.github.com/HideBar/ HideBar]" (Has a free version, and is open source if you wish to compile yourself) | ** You can use "[http://ppareit.github.com/HideBar/ HideBar]" (Has a free version, and is open source if you wish to compile yourself) | ||
**The app "[https://play.google.com/store/apps/details?id=de.tsorn.FullScreen Full!Screen]" is free and should also work. | ** The app "[https://play.google.com/store/apps/details?id=de.tsorn.FullScreen Full!Screen]" is free and should also work. | ||
**A custom Android ROM can be installed to correctly handle the navbar on set-top-boxes. | ** A custom Android ROM can be installed to correctly handle the navbar on set-top-boxes. | ||
**There's some other tricks you can do if you have rooted the device {{editor note|I keep hearing this, but haven't found any of these tricks yet. If someone finds one, please note it here.}} | ** There's some other tricks you can do if you have rooted the device {{editor note|I keep hearing this, but haven't found any of these tricks yet. If someone finds one, please note it here.}} | ||
}} | }} | ||
Line 189: | Line 189: | ||
* Turn off thumbnails, XBMC > Settings > Video > File and deselect 'generate thumbnails'. | * Turn off thumbnails, XBMC > Settings > Video > File and deselect 'generate thumbnails'. | ||
* h.264 Hi10P will not work as there are no ARM processors powerful enough to software decode it, and no hardware decoders exist for it. | * h.264 Hi10P will not work as there are no ARM processors powerful enough to software decode it, and no hardware decoders exist for it. | ||
* If your TV/receiver supports it, enable various [[Settings/System# | * If your TV/receiver supports it, enable various [[Settings/System#Audio output|audio passthrough options]] to reduce the load on the CPU. | ||
* If RSS feed is enabled, disable it in settings. This makes the main menu a bit faster. In fact, having rss enabled is probably the single-biggest battery-killing cpu-draining thing you can do. | * If RSS feed is enabled, disable it in settings. This makes the main menu a bit faster. In fact, having rss enabled is probably the single-biggest battery-killing cpu-draining thing you can do. | ||
}} | }} |
Revision as of 16:07, 27 April 2013
Frequently Asked Questions for Android.
General FAQ
- See also: XBMC all platforms FAQ for FAQs that apply to all versions of XBMC.
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
|
Troubleshooting
See also: Troubleshooting
| ||||
| ||||
| ||||
| ||||
| ||||
|