Support and General Use > Theming and Appearance Customization
Cover Art on barebones 1080x1920 WPS
AidanSonoda:
NM, should have searched harder before posting …
http://www.rockbox.org/irc/log-20141114
cleared that up: I needed "libtool-bin" package installed as well - perhaps this is a Debian thing (guide was written with Ubuntu in mind). In any case, rockboxdev script runs without errors now.
AidanSonoda:
--- Quote ---ERROR: You need the Android SDK installed and have the ANDROID_SDK_PATH environment variable point to the root directory of the Android SDK
--- End quote ---
So, it seems I will need to wrestle AndroidSDK into place … perhaps tomorrow. Going to call it for tonight though.
It seems from reading through --this-- that I'll also need to install JavaJDK and maybe some 32-bit libraries (I am running 64-bit Debian Testing). Let me know if I'm barking up the wrong tree here.
[Saint]:
Uuuuuugh,
I really should have covered this in depth for you to save you wasting your time. You would never have figured this out on your own, even with the cookie crumbs I've left scattered throughout the forums over the years...well, maybe, you seem like a capable fellow. Perhaps never is a bit harsh.
On the upside, you can now build for a bunch of additional Rockbox targets you may or may not own, but, not Android.
:-\
We don't actually use our own toolchains for this, so rockboxdev.sh is entirely irrelevant.
Compiling for Android is somewhat of a black art, I should do either one or both of two things - detail this in the wiki, and/or fix up rockboxdev.sh to actually set up an environment capable of building Rockbox for Android.
OK - so, you have our build essential tools installed, that's a great start.
Now, you're going to need to install a Java runtime and Software Development Kit. You mention Debian, so:
--- Code: ---sudo apt-get install openjdk-7-jdk openjdk-7-jre
--- End code ---
You are also going to need the Android SDK and Android NDK. We can do this with a relatively simple set of commands.
Lets assume we're doing all this in a directory called "development" in our home directory, so:
--- Code: ---mkdir -p ~/development/android
cd ~/development/android
wget http://dl.google.com/android/android-sdk_r24.0.2-linux.tgz
wget http://dl.google.com/android/ndk/android-ndk-r10d-linux-x86_64.bin
tar zxvf android-sdk_r24.0.2-linux.tgz
chmod a+x android-ndk-r10d-linux-x86_64.bin
./android-ndk-r10c-darwin-x86_64.bin
--- End code ---
Now we have downloaded, and extracted, both the Android SDK and Android NDK. Lets add them to our $PATH and export some environment variables we'll need later to compile Rockbox for Android:
--- Code: ---sudo echo "export ANDROID_NDK_PATH=~/development/android/android-ndk-r10d" >> ~/.bashrc
sudo echo "export ANDROID_SDK_PATH=~/development/android/android-sdk-linux" >> ~/.bashrc
--- End code ---
And some paths that will make things easier for us down the line by way of exposing some Android tools to the $PATH (we're mainly interested in the Android SDK manager and adb binaries):
--- Code: ---sudo echo "export PATH=${PATH}:~/development/android/android-sdk-linux/tools" >> ~/.bashrc
sudo echo "export PATH=${PATH}:~/development/android/android-sdk-linux/platform-tools" >> ~/.bashrc
--- End code ---
Now we'll run the Android SDK Manager and download the required tools:
--- Code: ---./development/android/android-sdk-linux/tools/android
--- End code ---
This will open a GUI session to uninstall/install components of the Android SDK, manually select if not already installed or selected the following packages:
--- Quote ----Tools
--Android SDk Tools
--Android SDK Platform-tools
--Android SDk Build-tools 19.1
-Android 4.4.2 (API 19)
--SDK Platform 19
-Extras
--Android Support Library
--- End quote ---
Any other packages that are pre-installed may be un-installed if desired.
One last thing, as of this writing our build system looks for zipalign in the wrong place, but we can address this trivially with a simple symbolic link:
--- Code: ---ln -s ~/development/android/android-sdk-linux/build-tools/19.1.0/zipalign ~/development/android/android-sdk-linux/tools/zipalign
--- End code ---
And...we're done. We can now reboot our system to apply the changes to the $PATH, and make the environment variables live. We could do this manually, but rebooting is easier to type from my point of view.
--- Code: ---sudo reboot now
--- End code ---
We should now have a system that is entirely capable of compiling Rockbox for Android. Lets check this out (after our reboot), by navigating to where we want to be building Rockbox for Android. To keep things clean in our git checkout, lets build "out-of-tree":
--- Code: ---mkdir -p ~/development/rockbox/build-dir
cd ~/development/rockbox/build-dir
--- End code ---
I'm going to make an assumption here about the path to your Rockbox git repository, edit this command to reflect your own system path:
--- Code: ---~/development/rockbox/tools/configure
--- End code ---
Select build type ID 201 for Android
Select your desired horizontal and vertical resolution
Now lets compile Rockbox and build our .apk:
--- Code: ---make
make apk
--- End code ---
Hint: instead of using 'make' use 'make -J N' where N == 'number of cores on the host system * 2'
Assuming your Android device is plugged in to the host and the Android Debug Bridge (adb) is configured to run on the device and give access to the host, you can install the apk directly with:
--- Code: ---adb install ~/development/rockbox/build-dir/*.apk
--- End code ---
For subsequent installations use:
--- Code: ---adb install -r ~/development/rockbox/build-dir/*.apk
--- End code ---
And we're done here. Let me know if you have any issues with any of the points in this guide.
[Saint]
ploco:
--- Quote ---tar zxvf http://dl.google.com/android/android-sdk_r24.0.2-linux.tgz
--- End quote ---
typo? should be
--- Code: ---tar zxvf android-sdk_r24.0.2-linux.tgz
--- End code ---
also
--- Quote ---sudo echo "export PATH=${PATH}:~/Development/android/android-sdk-linux/tools" >> ~/.bashrc
sudo echo "export PATH=${PATH}:~/Development/android/android-sdk-linux/platform-tools" >> ~/.bashrc
--- End quote ---
to
--- Code: ---sudo echo "export PATH=${PATH}:~/development/android/android-sdk-linux/tools" >> ~/.bashrc
sudo echo "export PATH=${PATH}:~/development/android/android-sdk-linux/platform-tools" >> ~/.bashrc
--- End code ---
ZincAlloy:
--- Quote from: [Saint ---
Now regarding album art in your WPS, were I to put my speculation hat on (its my favourite hat), I would say that the issue is almost certainly overflowing the fixed buffer space. Now, I could get into a deep and meaning{ful|less} conversation about why having a static buffer allocation for all application targets, regardless of screen resolution is a hilariously bad idea, but I won't.
--- End quote ---
There's hardly any graphics in that WPS. I've got 570x570px album art running fairly well on a 720x1280 screen (doesn't load when the track changes, just when I select a track manually). I guess it might be something else..
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version