cristox
Head-Fier
- Joined
- Jun 6, 2008
- Posts
- 94
- Likes
- 19
.
Last edited:
This was in response to criticisms of the M9 on its thread, but is relevant to this thread. Just the M6 has no 2.5mm balanced output. Are there many satisfied users of the M6?
Nothing is simply one problem and in the case of the M9, altlough there are a few small problems, it suits my needs well. I like it a lot. It's clear though that the M11 is way better, but its just too big for me. As long as, in my case, I keep the cache cleared every couple of days in the M9 when using Spotify, it's way fast enough to use and listen to. The music plays at the same speed as a $1000 DAP and sounds great. It sounds pretty amazing with my 2.5mm balanced iems and fine with 3.5mm single ended. It is loud. LDAC works perfectly in most situations and I can use it along with the FiiO BTR3 even connected to my hi-fi. I have an APTX-HD receiver also for playing to my hi-fi. I can play Spotify wirelessly over WiFi, to my HiFi, and get the highest level of sound whether through Spotify or Local files. I have a World Music Radio App. Many more apps are about to be white-listed (slow FiiO). Plus it does its most basic function well....it plays local music files to my IEMs with power to spare. All it's little problems do not stop me loving it, and the sound is exceptional. I don't stop using it.....and it is small. I can't carry a large M11 DAP and a large phone around at the same time. I fully accept the M11 is way better, but I bought the M9, and the M6, and I would still recommend them, and their form factors are great. For me they sound good and function well.
I might have discovered something awesome here. I've been able to install apps with their own icon on the dashboard, without having to change the AndroidManifest.xml package name.
You still need to decode and repack the APK, but I've even found some that install without doing any prep work!
If you wanna try it out, here's the general battleplan. Please note, I don't take any responsibility if your player breaks!
I'm running Arch Linux, but I'm sure the tools necessary also work on Mac and Windows, but you'll have to do that homework yourself.
Might go without saying, but all of this is taking place in the terminal/commandline.
Tools you need:
apktool
jarsigner
keytool
adb
Google is your friend
First off, enable USB Debugging on your M6. Go to Settings > General > About Device, then tap Build Number until it says "You are now a developer!". Go back to Settings, hit Developer Options and enable USB Debugging.
Now, grab apktool by following these instructions: https://ibotpeaches.github.io/Apktool/install/
Then, put your apk in a folder. For this guide, I'll use "playerpro.apk" for the apk, "app" for the folder. Substitute with whatever you're hacking with.
Go into "/app", and run this command to install the framework:
"apktool if playerpro.apk"
Then decode the apk:
"apktool d playerpro.apk"
The decoded files will appear in "app/[apkname]", so in my case that'd be "app/playerpro"
This is where you'd usually edit "playerpro/AndroidManifest.xml", replacing the package name with a whitelisted app. No more!
Immediately after decoding, build it again:
"apktool b playerpro"
After a little while, it should spit out a bunch of text, ending with "I: Built apk..." - if not, your APK will most likely not work.
Copy or move the apk you just rebuilt from "app/playerpro/dist/playerpro.apk" into "app/playerpro2.apk" (the residing folder of the apk and decoded folder).
Here's where the magic happens. Run "keytool" to generate a keystore to sign the APK you just built.
"keytool -genkey -v -keystore fiio.keystore -alias fiio -keyalg RSA -keysize 2048 -validity 10000"
It'll prompt you for a password. You can enter anything, just be sure to remember it. It'll also ask you a bunch of things like Company Name and Country, just hit enter through it all for the default value of "Unknown". Note that, at the end, you're required to type out "yes".
Once you've got your keystore generated, you need to actually sign the apk with "jarsigner".
"jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore fiio.keystore playerpro2.apk fiio"
When that's done, you just need one, final command to install it. Plug in your M6 with USB and run "adb install playerpro.apk". You need to be in the "app" folder for this, btw.
I don't actually know why this works, but either it's installing through ADB (unlikely, as it has failed before), the act itself of signing the apk again (why doesn't the original apk work?) or simply by naming the keystore alias "fiio".
In either case, this has been working for PlayerPro and Pulsar+. PlayerPro's DSP pack installs directly with "adb install" without any signing or decoding!
Give it a shot! Worst case scenario, it doesn't install. If you got any questions or errors, send me a PM.
I am planning on buying a M6 as my second, smaller portable dap.
I will simply play flac albums (no playlists) from the SD card as well as play Tidal albums (no playlist) offline.
Are there any glitches I should be aware of? In other words, is the current firmware good and stable enough for my use? And is the wifi connection reliable and strong enough to navigate Tidal online and download albums?
p.s. my previous Fiio experience, with the X7 1st gen.... has taught me to be cautious....
Thanks for the info, Salla45!
And how is the wifi connection (stable/strong) to download Tidal albums?
Is the Tidal app working well to play albums offline?
I used with Qobuz, not Tidal, never had problems with cached play. Cancelled my account with Qobuz due to lack of use however, now I am using local files only.
That is all well and good but shouldn't they focus on making their own Music Player better? I mean it has their name on it for god sakes and for us M7 owners our only option. It's like saying hey our competitors make better apps than us so use their products and not ours. M6 owners may feel neglected but M7 owners are completely forgotten at this point without a Fiio Music Player update.
Well said.