Last night my gf asked me "How do I turn media sounds on? Youtube and my games aren't working." All the volumes (notifications, system, media) are turned all the way up, and nothing. Notifications, ringtones, and alarms work just fine - definitely NOT a hardware issue; media only plays through the headphone jack though. That would be annoying but apparently media includes in-call volume...I can hear her but she can't hear me; she can use the phone on speaker or with an earbud stuck in one ear but it's not exactly practical. She wants to take it in to Verizon, but what little info I've been able to find on the Razr M specifically is showing it to be a software problem that just keeps happening and happening.
I've tried all the fixes I've found in the Maxx/HD/general Razr forums; wiping the cache, killing Play Music, unrolling Play Music updates, putting phones in and taking them out, pretty much everything possible without rooting and trying a sound routing app. We have an available upgrade on a third line but I'm trying to hold that one out for the springtime Big Thing, any help here would be AWESOME!
If it's still stock and under warranty, I'd just take it into Verizon. I mean, if they'll replace it, then why not?
freak4dell said:
If it's still stock and under warranty, I'd just take it into Verizon. I mean, if they'll replace it, then why not?
Click to expand...
Click to collapse
I figured it was probably a software issue (the speaker works fine, all other sounds play, just not media) and she was getting a little neurotic about even the few days for an exchange...so I SBF'ed back to 4.0.4 and wham, fixed nothing.
The new one will be here tomorrow.
Related
So the bluetooth ROM leak issue is definitely fixed. I can reboot the phone and it is still paired with my car, and I am able to make & receive calls perfectly.
However, when I try to play music or podcasts via the bluetooth speakers, absolutely nothing is heard. The music app/podcast player (BeyondPod) both show that they are playing, but nothing is heard. When I turn bluetooth off, both apps play their respective files perfectly through the phone speaker.
Whats REALLY weird is that when trying to play through bluetooth, they both are playing super fast i.e. for every second that passes in reality, the player says that it has played about 4 seconds (almost like its in fast forward).
Although its great that bluetooth can now pair perfectly and stay paired, Im now completely unable to play any media.
Would like to know if anyone else is experiencing this and/or has any ideas.
This is the ONLY issue I now have with the Hero and Im determined to get it sorted...
Thanks for all the help/comments
dom2114 said:
So the bluetooth ROM leak issue is definitely fixed. I can reboot the phone and it is still paired with my car, and I am able to make & receive calls perfectly.
However, when I try to play music or podcasts via the bluetooth speakers, absolutely nothing is heard. The music app/podcast player (BeyondPod) both show that they are playing, but nothing is heard. When I turn bluetooth off, both apps play their respective files perfectly through the phone speaker.
Whats REALLY weird is that when trying to play through bluetooth, they both are playing super fast i.e. for every second that passes in reality, the player says that it has played about 4 seconds (almost like its in fast forward).
Although its great that bluetooth can now pair perfectly and stay paired, Im now completely unable to play any media.
Would like to know if anyone else is experiencing this and/or has any ideas.
This is the ONLY issue I now have with the Hero and Im determined to get it sorted...
Thanks for all the help/comments
Click to expand...
Click to collapse
I have two CDMA Heros in my household, one rooted and one not. The unrooted phone went through the OTA update without problem and it played music over bluetooth speakers without any problem, just as it did before the OTA update.
I think it's an app setting of some sort. Some apps allow you to turn BT audio on and off. Try another app, like ACast or something.
jonnythan said:
I think it's an app setting of some sort. Some apps allow you to turn BT audio on and off. Try another app, like ACast or something.
Click to expand...
Click to collapse
is there a setting in the stock music player for this? Im thinking not
Fresh ROM Bluetooth Issue Confirmed - Prevents Media Being played throgh B/T Speakers
OK, so Ive just confirmed that the Fresh 0.4 ROM has an issue with playing media through bluetooth speakers, and Sprint/HTC are 100% NOT responsible for it.
Originally, I restored back to my original Sprint ROM, updated to Fresh 0.4, and all worked perfectly; except for the fact that I was unable to play any media whatsoever through bluetooth speakers (making and receiving phone calls worked fine and all bluetooth ROM leak issues were fixed). What was weird was that the music app and podcast app i was using (BeyondPod) showed that they were playing, but they looked as if they were playing in fast forward i.e. for every second that past, 4 seconds of the song/podcast were played according to the app. NB: The phone and the speakers showed that the link was established perfectly (for whatever thats worth)
I then decided to go back to when I first got the Hero i.e. use the Sprint RUU to unroot and got back to original ROM. Then did the OTA MR.
Playing media through the speakers worked 100% perfectly.
So bottom line, something has been changed/removed in the Fresh ROM that messes up media via bluetooth.
I havent come across anyone else talking about this, but any additional info would be great.
All the best.
I have done a fresh clean (started with Sprint RUU) to a fresh 0.4 update (not from modaco) and i also have this issue. I also tried the above check and i got the same results. Please if you have this issue, contact the makers of fresh rom and let them know of the issue if they do not already know.
Ok this is an issue that's plagued this phone since 2.2 came out(at least that's when I noticed it) and I'm asking if anyone knows of a workaround, fix, or otherwise to resolve this. My issue is that when I have headphones plugged in, listening to music, playing a game or whatever, I want(and expect) notification sounds(ringers, new text, new e-mail, etc.) sound to play through, and only through, the headphones. Instead what I get is that it plays through the external speaker(huh?) AND the headphones. I would expect that with anything plugged into the 3.5mm jack that the external speaker is entirely muted and remains that way until whatever's plugged into it is removed.
I work in a fairly quiet environment and sometimes forget to turn my ringer off when I get to the office. I am almost always listening to a podcast with my headphones though and it's disturbing to those around me and startles me, lol, when my phone rings, blasting it out to those around me. I have experienced this issue on the official 2.2 froyo build(and it's patches). I installed SFR(all versions) hoping it might do the trick but so far no. Is this something that might be fixed in a different kernel? I know I have options to run a different one and am not averse to trying it out if this is fixable. SFR has Voodoo control pre-installed which I checked to see if it had any settings for this type of thing and found none.
Help?
This is an issue with Android itself (all versions) and it is the same on every phone. I think Cyanogenmod is the only "solution."'
I received my device a couple of days back and today I encountered a very weird problem. Sometime phones uses the front speaker and sometimes it uses the rear loud speaker. I got a call, received it and turned the speaker on..the other person on call couldn't hear my voice but I could listen to hers. The a minute later the phone was playing everything from the front speaker rather the than rear. Be it audio songs, videos song anything. When I was pressing the volume rocker, there was no sound coming from any speaker. Finally, I restarted the phone and it's back to normal. What went wrong, any idea? As this might happen again.:s
My phone's condition: Totally stock. No root. No ROM. No kernel change. All stock. Running 4.2.2
Guess I was suppose to post it in Q&A forum. If so, mods, please move it there.
BigDig said:
What is wrong is....that there's no front speaker on that phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The EAR PIECE that 'can' be called a Front Speaker (as inside the earpiece is a speaker), which goes without saying.
-----------------------
Anyhow, back to the topic.. Has anyone encountered this issue on his/her device?
Seeing responses like the above quoted comment, I might add my phone rattles, but I don't find it an issue. As long as such things aren't affecting the usability of the device, I am completely OK with it. But 2 problems have really bothered me. One is well known, the camera can't focus at all and second is the subject of this thread. So, I really want to inquire if anyone came across this earpiece/speaker problem that I faced and how it was fixed, permanently.
RMA that sucker. Hardware fault.
Sent from my Nexus4™
^lol
I had a similar problem.
I would play music from the back but eventually it would play music in the earpiece. I forgot what I did prior, but it had to do with using a modified google play version.
I just re-flashed the rom and it worked fine after that.
intekmdma said:
I had a similar problem.
I would play music from the back but eventually it would play music in the earpiece. I forgot what I did prior, but it had to do with using a modified google play version.
I just re-flashed the rom and it worked fine after that.
Click to expand...
Click to collapse
Alright, thanks for the response.
I am playing music from the built in Music Player. And I am totally stock. Although it didn't happen again but I was hoping if I could know what to do (besides restarting) when it happens the next time.
Just came across a disturbing report in a very recent Droid Life review of the Note 3 (from a list of N3 reviews posted on this forum) concerning "Audio Jack Issues". Anybody who treasures their hearing and uses their phablet for audio material (including movies, music, audiobooks, etc), especially using earbuds or headphones, might want to "listen up." The following is an excerpt from the review:
"...When listening to music through the 3.5mm jack, you are sometimes met with a very weak sound. It’s as if the sound of the music isn’t “full” or quite loud enough. Then, after a few minutes without touching anything while at full volume, the volume just explodes and you are left deafened by the surprise volume attack. Some people are pointing towards low-impedance headphones being the issue, but I have had the problem on multiple pairs of headphones, in-ear buds, through car decks, and everything else. It’s a very frustrating and reoccurring issue that I wish Samsung would find a cure for. Until then, I fear listening to music out of this device because I don’t want to go deaf. It might sound crazy, but it’s a very real issue that I experienced over the course of time I had the device."
I've had 3 Samsungs: a flip-phone a few years ago, a Fascinate 2 years ago, and currently Galaxy S3, and just preordered a Note 3. Of the three previous phones, two had infrequent but definitely-occurring audio issues where the volume changed unexpectedly. The flip phone blew out my ears once, and swore after that would never buy another Sammy (what a kidding-myself that turned out to be). What's unnerving is this seems to have appeared intermittently in multiple samsung phone models (the article reports yet another audio jack issue in the S4).
Chatted online with a VZW customer service rep. about this, who was really no help (wasn't her fault, i guess). She just regurgitated the company standard lines--14 days to return, restocking fee, can get a replacement if the problem occurs, etc. But she pretty much stated if there turns out to be a Note 3-specific issue, the customer is stuck with that model of phone; don't expect help from the carrier other than replacing with an identical unit might likely have the same problem; if you enjoy any kind of audio produced by the phone's audio jack, use it at your own risk. (Even more dicey is that it's intermittent--no guarantee you'll be able to demonstrate it to the carrier's service rep.)
Furthermore, i was one of those who got a free continuation of unlimited plan (thanks to the VZW ordering "system glitch" last weekend), which has been reported in the last day that VZW is going to honor contracts which show unlimited data. This rep completely contradicted that and claimed my data will be capped at 2gb at activation time. So with this diametrically-opposed chatter from VZW, what is one supposed to believe? Really suggests getting a satisfactory resolution from any carrier on a brand-specific phone problem like this to be wishful thinking.
Any thoughts or has anybody experienced thru-the-audio-jack sound issues with sammy phone products? My take is i'm not going to be on the bleeding edge of this one, too much of a hearing risk, cancelling preorder and wait for more reports on the N3 as time goes by.
For sure something is wrong with mine. (tmobile N3) The output levels are maybe half or less what my N2 can put out. I have carefully setup audio systems in my house and car, and it is unusable. Its also not USB compatible with the new Kenwood KMM 100u deck that plays FLAC files. It must be a glitch they can fix, i hope! The jack SQ sucks right now.
I hope mine won't have this problem.
*wierd double post an hour later*
dareo said:
For sure something is wrong with mine. (tmobile N3) The output levels are maybe half or less what my N2 can put out. I have carefully setup audio systems in my house and car, and it is unusable. Its also not USB compatible with the new Kenwood KMM 100u deck that plays FLAC files. It must be a glitch they can fix, i hope! The jack SQ sucks right now.
Click to expand...
Click to collapse
I got that the first time you said it.
im experiencing this too with an AU Telstra Note 3.
ive tested it a bit and it seems like its 2 separate things to me, but I could be wrong.
firstly it seems like all EQs either crash or just lose their settings at random moments. this can be things like between track changes or when the 3G signal drops out. if you go back into the EQ panel it will kick in again, almost like it was off and you've launched it again.. very annoying. ive verified this with both the stock EQ and noozxoide. the difference in volume is minimal though, its more quality / bass / whatever EQ you use.
the second part with the volume dropping out completely only happens to me between track changes. if i pause the music for a couple of seconds then play it again, it will play at normal volume. fast forwarding between tracks is the most obvious since every other track will be minimal volume, and the ones in-between normal volume.
ive only tested this with google music. although my phone isnt stock now, the same behaviour was there out of the box. using etymotic earbuds with reasonably high impedance but i doubt thats the issue since pause/replay fixes it.
Doesn't happen to me on N7player or PlayerPro. (nor on videos in Dice, MX or VLC.)
Try not using stock apps if you have the issue. Might just be a stock problem.
I can't test Google music, I disabled that. Stock player itself is too annoying for me to try.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
kanemari said:
im experiencing this too with an AU Telstra Note 3.
ive tested it a bit and it seems like its 2 separate things to me, but I could be wrong.
firstly it seems like all EQs either crash or just lose their settings at random moments. this can be things like between track changes or when the 3G signal drops out. if you go back into the EQ panel it will kick in again, almost like it was off and you've launched it again.. very annoying. ive verified this with both the stock EQ and noozxoide. the difference in volume is minimal though, its more quality / bass / whatever EQ you use.
the second part with the volume dropping out completely only happens to me between track changes. if i pause the music for a couple of seconds then play it again, it will play at normal volume. fast forwarding between tracks is the most obvious since every other track will be minimal volume, and the ones in-between normal volume.
ive only tested this with google music. although my phone isnt stock now, the same behaviour was there out of the box. using etymotic earbuds with reasonably high impedance but i doubt thats the issue since pause/replay fixes it.
Click to expand...
Click to collapse
Got the same here. N9005 with Google Play Music. Sometimes it's also (it seems) input-triggered. Sometimes when I push Menu or Back button, volume goes down and when I open Browser volume goes up. I know this sounds like voodoo and I'm completely crazy but I got this situation some times now.
With original sound files this problem came very often but after installing sound mod, it became seldom but not solved.
Annoying!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Silberpfeil3110 said:
Got the same here. N9005 with Google Play Music. Sometimes it's also (it seems) input-triggered. Sometimes when I push Menu or Back button, volume goes down and when I open Browser volume goes up. I know this sounds like voodoo and I'm completely crazy but I got this situation some times now.
With original sound files this problem came very often but after installing sound mod, it became seldom but not solved.
Annoying!
Click to expand...
Click to collapse
I actually moved to the stock sammy app since it was irritating me so much. i have to say though, that if you can be bothered syncing a playlist to your phone that the sound is much better through that... hard to pick fault with.
i set up galaxy adaptive sound first, which is the one that plays high med low tones through left and right channels on your headphones independently and lets you tune it. found a much more balanced tone coming out after that, to which I then applied higher bass EQ settings from within the sammy music player and it sounds pretty good. some distortion on really heavy bass tracks at high volume, but very nice otherwise. MUCH BETTER than variable bass and audio volume on the google music player.
i think samsung neglected to test the standard music APIs and borked them, but their own proprietary ones work fine. the adaptive music filter doesnt work in any player apart from the sammy one I read.
since i cant cross-flash regional roms without voiding knox warranty i havent tried the updated EU roms, but maybe they fix it there?
Experiencing same problem on my AT&T note 3. Google Music tracks will randomly apply a shoddy EQ setting that is either too loud or too soft. Then the next track will be normal. It explodes my ear drums constantly. I have the EQ set off also, but that doesn't seem to matter. Also unplugging and re plugging the headphone jack "fixes" the issue as well. I'm pretty annoyed by this problem.
So I have this Note 3 which I like a lot. Big screen to watch series in the train, although after a while I got pretty fed up with the chord of the earphones, expecially when I had to get up, swiched to music and had to stuff my phone in some pocket.
So I looked around for some nice Bluetooth headphones and came across a nice deal on the Sennheiser MM 550-X. Just stating the model for any chance that someone is aware of some faults in this product.
Now, overall the sound quality is fine, which you would expect because of the apt-X thing which both devices support. But what really annoys me, is the following.
While listening to the native musicplayer, the music sort of studders. Not all the time, but like one or a few times per minute and then not at all for a few minutes. Some faults sound like pops, but some are real pauses for like half a second. Especially with those longer pauses I can distinctly hear that the music really 'pauses' and that it is not just the connection which fails while the music on my Note plays on.
So I suppose it has something to do with the apt-X coding. I already tried rebooting, killing background processes, switching off wifi and mobile data. I also tried different music players. Nothing seems to help.
The only time when I have almost no problems is when I'm at home, with te phone lying still on the desk.
I have a stock rom.
Does anyone have an idea how I can fix this?
duduscoke said:
So I have this Note 3 which I like a lot. Big screen to watch series in the train, although after a while I got pretty fed up with the chord of the earphones, expecially when I had to get up, swiched to music and had to stuff my phone in some pocket.
So I looked around for some nice Bluetooth headphones and came across a nice deal on the Sennheiser MM 550-X. Just stating the model for any chance that someone is aware of some faults in this product.
Now, overall the sound quality is fine, which you would expect because of the apt-X thing which both devices support. But what really annoys me, is the following.
While listening to the native musicplayer, the music sort of studders. Not all the time, but like one or a few times per minute and then not at all for a few minutes. Some faults sound like pops, but some are real pauses for like half a second. Especially with those longer pauses I can distinctly hear that the music really 'pauses' and that it is not just the connection which fails while the music on my Note plays on.
So I suppose it has something to do with the apt-X coding. I already tried rebooting, killing background processes, switching off wifi and mobile data. I also tried different music players. Nothing seems to help.
The only time when I have almost no problems is when I'm at home, with te phone lying still on the desk.
I have a stock rom.
Does anyone have an idea how I can fix this?
Click to expand...
Click to collapse
Try them with another phone?
FeralFire said:
Try them with another phone?
Click to expand...
Click to collapse
That's difficult, because I don't have a phone which supports apt-X available.
duduscoke said:
That's difficult, because I don't have a phone which supports apt-X available.
Click to expand...
Click to collapse
Most phones these days support it.
Maybe a friend's?
Maybe the problem is something else entirely. You need to troubleshoot it.
I am just guessing, though. Never used bluetooth headsets myself.