Related
Hi, I'm having issues with my brand new, just bought today Motorola S9HD bluetooth headphones. I am having three issues so far:
First Issue: The headphones seem to work with the Google Music player (stock, but newest version via market), but I cannot use seek controls, play/pause.
FIRST ISSUE SOLVED BY REMOVING WP7 MUSIC PLAYER AND ONLY HAVING STOCK ON THE DEVICE.
Second Issue: While I'm listening to music, I sometimes want to make a quick call. I assume with these I should be able to hit the call button, which goes to voice commands, then I say who I want to call, and boom, done. BUT! whenever the screen is off and I'm listening to music, then click the call button, it gives me three or so beeps but never quits playing music and never goes to voice commands. THE ANNOYING SOLUTION THAT I FOUND: When I turn on the screen, I am able to click the call button and go into voice commands, call whoever, etc.
SECOND ISSUE NOT SOLVED EVEN AFTER SWITCHING TO STOCK GOOGLE MUSIC PLAYER.
Third Issue: For some reason, I will get a random space (0.5 seconds to 1 second) randomly of no music, then it resumes. BUT sometimes it just all together stops playing music. I have left it for a couple minutes to see if it'll resume, but it doesn't. Then I look at the phone and it says it's still working, and the only way to make it play music through the headphones again is to restart bluetooth via the phone.
THIRD ISSUE POSSIBLY SOLVED BY USING STOCK GOOGLE MUSIC PLAYER INSTEAD OF WP7 MUSIC PLAYER. BUT SUGGESTIONS ARE STILL WELCOME.
Thanks for all your help!
2nd issue: did you tell it the first time what voice control you want to use? Like Vlingo, google voice, google search, etc.
3rd issue: no clue, mine does that too and it is annoying. I notice it gets worse if the battery is 2 or so hours without a charge.
Thanks for the reply. I'll try assigning the voice commands app.
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
muy issue with my Moto S(HD is that I continually have to re-pair every time I try to use them. anyone know why?
Regarding item #3, I think this is more related to the bluetooth stack on the Atrix crashing than it is related to the S9HDs. I don't have that problem with my S9HDs, but I routinely get it when paired to my car stereo. Probably happens once a week with my car stereo, whereas I've only seen it once in several months with my S9HDs. I'm hoping the bluetooth stack has been improved when we get gingerbread shortly.
I've a nokia BH503 BT headset ATM and never had those issues. It works with EVERY app on the phone, even the emulators, games and notifications sounds through the bluetooth headphones. I luv it.
Before my motorola atrix I used a Blackberry Storm + motorola S9HD BT headphones, and had exactly the same issues u report...
I have the S9HDs and I get pauses too. The thing that frustrates me is that it depends on where I have my phone. I have a jacket in wear when I bike ride that has a pocket on the inside. If I put the phone in there it constantly pauses. If I put my phone in my pants pocket it doesn't pause at all.
It seems like an easy solution, keep the phone in my pants pocket, but I wear workout type pants when riding and they are not deep pockets so I'm afraid the phone will fall out. It just doesn't make sense that the farther I put the phone from the headphones the better it works.
Sent from my MB860
I use these, and play music with PlayerPro............have no issues. Don't call often with the headphones, but have not had problems with them there either.
I routinely have my phone in my pants pocket while I walk around the office listening to music, and never lose my connection.
Not much help I know, but there are I guess some of us who don't experience bluetooth issues.
I installed playerpro, and I'm liking it so far.
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
S9 HD's reception is really bad. And I tell you cuz I had those. I mean, u can´t use the phone on your pants' pocket without lil skips... Nokias' reception rocks, and the battery last longer.
The problem with the s9 hd cutting out is reception. I have been using this headset for about 2 years while riding my motorcycle, with three different phones. They all had the same problem. With phone in my front pants pocket the problem persists. With phone in my shirt pocket, or in a backpack behind me, it never cuts out.
Posted from Atrix running gingerblur 4.5
There are several threads now detailing a problem with playing music, mainly reported when using the Google Music app. To be more specific here are some examples:
When playing music and then multitasking, the phone crashes and requires a battery pull and reboot.
Another is when playing music and then turning the screen off, the music is jerky and stutters.
People have reported this happening with apps other than Google Music, so it would appear that this isn't a problem with the Music app, but either the phone or ICS.
I wanted to start a poll to gauge how many people have this problem and establish whether it's everyone or not.
Here are some links to what I'm referring to:
http://forum.xda-developers.com/showthread.php?t=1381413
http://forum.xda-developers.com/showthread.php?t=1380773
http://forum.xda-developers.com/showthread.php?t=1379600
http://code.google.com/p/android/issues/detail?id=22669
Your poll is a bit flawed. My experience so far is that these crashes are a bit more random than being attributed to any specific apps right now. I've experienced the crash, but long story short, I am not convinced it was related to the exact app that I was using at the time.
Well just because you have experienced an unrelated crash it doesn't mean my poll is flawed, just that you have a separate issue
People have spoken of this happening repeatedly when trying to use Music and multitask so I think it is definitely an issue of it's own. Usually it is said that the sound/screen goes corrupt and then requires a battery pull. Are you not referring to a random reboot or something?
i have a couple of problems with PowerAmp, no problems with google music though.
1. PowerAmp can't see playlists that were created in google music
2. PowerAmp stutters when the screen goes to sleep. (does the clock speed lower when the screen goes off?)
i've read that increasing the buffer size in poweramp options fixes no. 2. I havent tried it due to no.1.
i'm just using google music at the moment.
WinAmp i found would often have slight cracks in the music (i.e. stop and start again quickly, almost like it was being disturbed/cpu high).
doubletwist is fine though, as is Music player
This is such a huge problem I can't believe more people haven't responded :S
I've had Google Music, Rhapsody, and Pandora all crash at one time or another.
str355 said:
i have a couple of problems with PowerAmp, no problems with google music though.
1. PowerAmp can't see playlists that were created in google music
2. PowerAmp stutters when the screen goes to sleep. (does the clock speed lower when the screen goes off?)
i've read that increasing the buffer size in poweramp options fixes no. 2. I havent tried it due to no.1.
i'm just using google music at the moment.
Click to expand...
Click to collapse
increasing the buffer size in power amp fixes no.2
Sent from Mobile..
problem number 2 here for me. songs with high bit rates tends to trigger the stutter problem after the phone goes to sleep. tried on google music and playerpro
Google Music 4.0.1 (ICS stock) often crashes within a minute after I reboot the phone - without me actually using it.
Obviously it's trying to do something in the background on start-up and fails. Miserably.
Did not crash while I was using it so far, but I didn't run it for any lengths of time either. No problems with other apps crashing, just Music.
rayvioli said:
problem number 2 here for me. songs with high bit rates tends to trigger the stutter problem after the phone goes to sleep. tried on google music and playerpro
Click to expand...
Click to collapse
Yes I notice it too, it's very annoying especially since I payed so much for this phone and a good set of headphones just for my high bit-rate music to constantly stutter; hopefully google fixes this. I seem to only notice this on the stock music player, but I prefer to use it over others due to its integration with the lockscreen and notification pulldown bar, especially considering the nice visuals it now has.
my 2 cents:
i can recreate the crash consistently by doing the following:
1. reboot the phone and connect a pair of headphones
2. stream a song (i.e., a song that's not already saved to the phone) using google music
3. use the home button to leave the google music app and return to the homescreen
4. while the song is playing, try to increase or decrease the volume of the music with the volume buttons and then almost immediately the phone reboots automatically.
i haven't been able to recreate the issue once with the headphones disconnected. also, the issue doesn't seem to occur if you connect the headphones after you start playing the music. i need to test that theory some more though.
I noticed this right away when I got my phone (launch day)
Since I constantly stream music from google music, I noticed pops and weird noises all the time. Very weird and SUPER annoying
The stock music app is not able to find my music at all. I use PowerAMP now and that works fine.
Music also crashes when not actively in use at all. When I open a lot of apps, i.e. multi-task a lot, Music often just force closes after a while.
I'm using PowerAmp now to listen to music stored in either .flac or the highest quality .mp3 files lame could produce. Some are 320kbps cbr others are vbr. In PowerAmp I set the process to the highest priority possible but left the buffer on auto.
I have never had any reboots or studering when locking the screen and I've been listening to music for over 3 hours now while doing some home work. Just to test it I put on one of my flac files and quickly locked and unlocked the screen. The phone took it like and champ with no studers at all.
No problems with music apps crashing, or needing to pull the battery. The only issue I have is with music or podcasts played through the native music player or Google Listen stopping at random intervals. Happens using wired speaker/headphones or bluetooth audio.
Frustrating, but not a dealbreaker yet.
I called Verizon for no other reason other than trying to create a record of the issue... They claimed to have not heard of this... Is there any way to let Samsung know directly? I know there is a google code ticket open, but Google hasn't "owned" the issue yet... I'd also say if you have the issue to let VZW know so they can get things in motion on their side as well.
kptkill said:
I called Verizon for no other reason other than trying to create a record of the issue... They claimed to have not heard of this... Is there any way to let Samsung know directly? I know there is a google code ticket open, but Google hasn't "owned" the issue yet... I'd also say if you have the issue to let VZW know so they can get things in motion on their side as well.
Click to expand...
Click to collapse
It seems they don't give a ****, unfortunately. Just have to live with it..
WinAMP - today while playing an album with the screen off paused (twice). I had to turn on the display, and hit the play button to continue. There was a bit of a lag (I got the FC screen, but when i hit wait the app returned a few seconds later)
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
I have the same problem, running stock 4.2.2 on my Galaxy Nexus. I think it's a device problem, not an app/background process problem.
I don't use TuneIn so I can't speak to the quality of its streams, but I have used Rdio, Slacker, Pandora and Google Play Music and they all play flawlessly.
ONLY Spotify plays audios with occasional snaps, crackles and pops, like a bowl of Rice Krispies. Some songs will play without a blip, some with a few, some with many. The songs are not interrupted...just marred by this defect. And it's never the same way twice with the same song.
It happens whether the song is streaming, or playing locally.
My guess is that the Nexus has difficulty playing Ogg Vorbis files, which is the format for Spotify streams and downloads. As far as I know, the other services I mentioned stream in AAC or MP3. While the Nexus supports Ogg Vorbis, it appears it does not support it very well. I'm going to test this theory by transcoding one of my Apple Lossless audio files to Ogg and then uploading it to the Nexus. My hunch is that it will demonstrate the same issues.
I guess we should consider ourselves lucky; before Jelly Bean the Nexus suffered from more dramatic playback problems. Do a Google search on "Music Stutters when playing long files and screen off: Galaxy Nexus" and read through it. There are a couple of posts that deal specifically with Ogg playback.
I've decided to live with it. I've been hopping from music service to music service trying to find the right one, and I always come back to Spotify. As long as the issue doesn't become more severe, I think I can re-program my brain to tolerate it.
Skyh said:
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
Click to expand...
Click to collapse
---------- Post added at 11:20 AM ---------- Previous post was at 11:02 AM ----------
My theory was incorrect. I used XLD to transcode Boston's "Hitch A Ride" from Apple Lossless to Ogg Vorbis (VBR, quality 4.0), then put the file on my phone. I used Winamp to play the file and it played beautifully.
So I'm thinking there's something specific with Spotify's encoding that the Nexus doesn't like.
What's odd is that I have run Spotify on other mobile devices and have never had an issue. That's why I have trouble putting the blame on them.
OP, after checking many Google leads, posts, etc. I believe--for Spotify anyway--I have found a way to stop (or at least greatly reduce) the Rice Krispies.
If you have Google Play Music on your phone, make sure it's fully updated and then launch it.
Within Play Music, go to Settings, then select Equalizer.
Turn the equalizer on, select the Normal preset, and move the Bass Boost and 3D Effect sliders all the way to the left to turn them off...unless you like them on.
Back out of Google Play Music to the home screen, then launch Spotify.
Go to Settings within Spotify, choose Audio Effects and verify the Equalizer is OFF in that app.
Using this combination of settings/conditions, I have heard just a couple of pops over a string of a half-dozen songs. I'm keeping my fingers crossed that it lasts.
I'm guessing that having the Google Play Music equalizer on, some additional processing is taking place that alleviates whatever is causing the popping to occur.
Good luck!
Hi guys, here is the problem that for some reason popped just recently, started maybe 2 weeks ago or so. I'm using Jay bird blue buds x as my main wireless headphones with my tab s. Everything was working fine but now whenever I connect the headphones and either start listening to music, music player or Google play music, or listen to a video clip, be it from YouTube, gallery or Google play video, the headphones cut out after 30-60 seconds. Now I did test the headphones with other tablet, an Asus one, and with my audio setup I use with my pc and I can use them without any problems for hours at a time. Which kinda led me to a conclusion that it's not the headphones but the tab itself. Now my question is, did anyone experience something similar? Any chance it's a Bluetooth driver mixup of some sorts that came with most recent tab update? Any help would be appreciated. I'm running complete stock with the most recent update, with just a couple of apps "turned off" in application section.
Jaybirds work with stock and skyhigh kernel.
VittoCornelius said:
Hi guys, here is the problem that for some reason popped just recently, started maybe 2 weeks ago or so. I'm using Jay bird blue buds x as my main wireless headphones with my tab s. Everything was working fine but now whenever I connect the headphones and either start listening to music, music player or Google play music, or listen to a video clip, be it from YouTube, gallery or Google play video, the headphones cut out after 30-60 seconds. Now I did test the headphones with other tablet, an Asus one, and with my audio setup I use with my pc and I can use them without any problems for hours at a time. Which kinda led me to a conclusion that it's not the headphones but the tab itself. Now my question is, did anyone experience something similar? Any chance it's a Bluetooth driver mixup of some sorts that came with most recent tab update? Any help would be appreciated. I'm running complete stock with the most recent update, with just a couple of apps "turned off" in application section.
Click to expand...
Click to collapse
Well, my Samsung HS3000 Bluetooth headphones work w/o a problem, but I just encountered an issue with a bluetooth gamepad I bought. It started to lag every 30s - 2 minutes for like 10 seconds and than worked normally again. On the Nexus 7 of my girlfriend it worked for hours w/o a problem. I ended up factory resetting and updating to a newer firmware only to find out (just now) that one of my apps with accessibility access is responsible, probably Tasker or some of its modules / plugins.
Since your issue sounds a bit similar, you might want to investigate in that direction.
TheGoD said:
Well, my Samsung HS3000 Bluetooth headphones work w/o a problem, but I just encountered an issue with a bluetooth gamepad I bought. It started to lag every 30s - 2 minutes for like 10 seconds and than worked normally again. On the Nexus 7 of my girlfriend it worked for hours w/o a problem. I ended up factory resetting and updating to a newer firmware only to find out (just now) that one of my apps with accessibility access is responsible, probably Tasker or some of its modules / plugins.
Since your issue sounds a bit similar, you might want to investigate in that direction.
Click to expand...
Click to collapse
Sounds like you might be right, tho I am not using Tasker atm. I'm thinking maybe it's one of the apps I turned off.
The past few weeks I've been having Bluetooth issues when playing music on my Note 4. I'll be playing stuff either on my PowerBeats2 or UE Boom and all of a sudden the music will stop playing, I'll hear a hiccup of sound a few seconds laters and that's it. When I check, the bluetooth on the phone is still on and still connected to the devices. The devices don't notice a drop connection either. I look at the music players and it LOOKS like they are still playing sometimes but there is no sound going through the bluetooth connection and nothing is coming out of the phone speakers either. What I end up having to do is turn off the Bluetooth on the phone, turn it on again and then manually force the connection on again between the two then hit play. It happens with Google Music player and the Samsung Music player and Musicmatch so it's not a particular app. Strange this is, it doesn't happen when I'm in my car and the charger is connected to it. It happens with songs on the internal memory and the microSD card so I don't think it's the microSD card going bad. What I do notice when it happens though is that it seems the phone completely lags out. Like it's pausing right before it happens. Screen response time can be nonexistant or laggy all of a sudden. Anyone else having this problem? I've wiped the cache and everything as well and this still happens.
I've also noticed my phone be quite laggy lately actually. It didn't happen originally when Lollipop was installed nor did the Bluetooth problems. I've been pulling apps off my phone and checking data and battery use to see if it's some app that's messing up but can't seem to pinpoint anything. I ordered a new battery because I've had it drop from 25% to like zero within a few minutes sometimes. I'm also considering wiping the whole phone and fresh installing Lollipop from scratch instead of sticking with the upgrade from KK that came through. I'm not sure if it's software or hardware related these problems. Any ideas or suggestions?