Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Two very simple things:
- Playback resume after leaving the phone idle, same song, same time.
- Album name displayed in playlists.
Is it so very hard to implement?
Why yes, yes it is hard.
You see, I carry both an iPhone 5 and a Galaxy S3 and after using the iOS version I am fairly certain that nobody at Spotify uses an Android device. If Spotify could, they would stop developing for it. I've been sitting around for over a year waiting for AVRCP 1.3 to be implemented, and I still can't see what track is playing on the head unit in my car. Every single Android device worth buying today supports Bluetooth 1.3. What is the problem?
Another cool thing is we can no longer tell spotify where to put its offline data files - so it fills up the fast internal memory of the phone instead of allowing the user to store the music on the slower, more spacious external sd card. Sure there are hack workarounds, but literally all four of these features we talk about would take 10 minutes each to implement.
Actually, I'd pay $20 a month for spotify if they fixed the AVRCP issue. Are you listening, Spotify?
@user-removed wrote:
Why yes, yes it is hard.
You see, I carry both an iPhone 5 and a Galaxy S3 and after using the iOS version I am fairly certain that nobody at Spotify uses an Android device. If Spotify could, they would stop developing for it. I've been sitting around for over a year waiting for AVRCP 1.3 to be implemented, and I still can't see what track is playing on the head unit in my car. Every single Android device worth buying today supports Bluetooth 1.3. What is the problem?
Another cool thing is we can no longer tell spotify where to put its offline data files - so it fills up the fast internal memory of the phone instead of allowing the user to store the music on the slower, more spacious external sd card. Sure there are hack workarounds, but literally all four of these features we talk about would take 10 minutes each to implement.
Actually, I'd pay $20 a month for spotify if they fixed the AVRCP issue. Are you listening, Spotify?
There are a number of staff here that totally rely on their Android devices. I've been known to dabble, too.
In the last 8 months have any of you listened to music in your vehicle on an Android device?
I have.
So how come the iOS app is so much better? Is the more open platform more difficult to develop for? WIMP, the Norwegian alternative has a good android app. Time to change music supplier?
I am having a hard time believing that ANY of the Spotify staffers use a Android tablet. Then they'd see that the app is FUBAR.
Double post, deleted.
It would be nice if Spotify would be a bit more transparent about their dev cycle. Communicate what issues/features are currently in dev, that way people at least know if it's going to be fixed. Some of these issues/requests are so simple in nature it's mind boggling they haven't been addressed in the last 8 months.
As I've said before, I'd pay more money if it meant having a decent app. It's the same reason I dumped Slacker a year ago - their app was garbage.
Maybe some people at Spotify just love staring at "UNKNOWN" on their head unit? Maybe it fills them with inner peace and purpose?
Trumps - One of our Android devs, Mikael, actually commented on the development process here: http://community.spotify.com/t5/Mobile-Android/Are-the-Spotify-UI-engineers-smoking-crack/m-p/212542...
They're not doing nothing, I can assure you.
Didn't really tell us much...
Sam - I am not an android developer by trade, but in less than 2 hours I built a test project and figured out how to send metadata to my head unit based on information freely available to the public. This request has been out there for at least 8 months. What gives?
Some information on its priority/status would be nice, considering it takes all of about 15 total lines of additional code.
Sorry, but you're wrong. All the app has to do is check the API level to see if it's 14 or greater, and then use the RemoteControlClient.MetdataEditor class under android.media.
It's built into Ice Cream Sandwich.
There's actually some functionality built into Android that aren't in the iOS version of Spotify right now. For example, one of my favourites is the Audio Effects feature - EQ and the like.
Get Android - problem solved!
ANDROID FOREVER 😉
Which doesn't work on HTC phones running HTC Sense 3, 4 or 4+ (just got an update to Android 4.1.1 and HTC Sense 4+ and it still doesn't work).
It works nicely on my Sony Tablet S though 🙂
@SteveBrammer wrote:
Which doesn't work on HTC phones running HTC Sense 3, 4 or 4+ (just got an update to Android 4.1.1 and HTC Sense 4+ and it still doesn't work).
It works nicely on my Sony Tablet S though 🙂
Beats Audio thing? That's still a weird thing we know about. I'll chase that up now, actually.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…