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.
One if the better features on marshmallow was to allow the connection of Bluetooth head phones for audio, within regular apps this works flawlessly such as youtube, crunchyroll and the lean back launcher. Within Kodi there is always a silence gap of anywhere from a few seconds to 20 seconds at the beginning of anything been played, even if it does start to work as soon as you skip or pause the silence is back. I can see there were people complaining about this issue months ago and then nothing so I'm wondering if I've screwed something or people just don't use bluetooth headphones.
Currently I'm using the latest stock marshmallow and the official Kodi v16 (though I've tried them all with the same outcome). Also it happens with any file format.
Anyone have any suggestions?
Sent from my SM-G925F using Tapatalk
I have the same problem. I think it has something to do with the quality of the streams in kodi or the cache size. However, I have no idea how to resolve it. What I do is I start the movie with earphones turned off and once it is playing then I turn on the earphones and it works. If I pause I lose the audio again.
So, I just opened Dolby Atmos while my N7 music player was going, then I got the "Unfortunatly, Dolby has stopped". I've cleared all the data and cashe, restarted the phone and I get the same error.
I just spent over 2 hours downloading all my apps and setting it up, now I think the only option I have is to do a factory reset :crying:
Anyone have any tips on how to get it working again? It sounds really thin and lifeless without Dolby on.
[EDIT]
I just factory reset my phone, gonna start over.....ugh
tele_jas said:
So, I just opened Dolby Atmos while my N7 music player was going, then I got the "Unfortunatly, Dolby has stopped". I've cleared all the data and cashe, restarted the phone and I get the same error.
I just spent over 2 hours downloading all my apps and setting it up, now I think the only option I have is to do a factory reset :crying:
Anyone have any tips on how to get it working again? It sounds really thin and lifeless without Dolby on.
[EDIT]
I just factory reset my phone, gonna start over.....ugh
Click to expand...
Click to collapse
Oh yeah. Dolby Atmos and certain music player apps can't be used at the same time.
Go to Settings > Application Manager/Apps > All > Dolby, and force stop. Then wait and when it becomes available clear data. Restart the phone and see if Dolby will load then
icenight89 said:
Go to Settings > Application Manager/Apps > All > Dolby, and force stop. Then wait and when it becomes available clear data. Restart the phone and see if Dolby will load then
Click to expand...
Click to collapse
Tried that, didn't work... Only fix was uninstalling n7 music player, then doing that with Dolby.
So there seems to be a compatibility problem with n7. Poweramp locked it up, but didn't fc it.
Shuttle +, stock, and Google music all work fine
[UPDATE]
For what it's worth..
I tried replicating the issue so I could give the steps on how to get it working again.....So I downloaded n7 player again, started playing music and then went to Dolby and turned it on. I got the "force close" and went through my steps of removing n7, then going to the Dolby app (in settings) and doing a force stop, clearing the data and cashe - then rebooted and tried opening Dolby again, it did NOT open! I messed around with it for about 30 minutes and even went into the stock recovery and tried wiping the cashe (I think that was what I did). It reset all my apps and data, but didin't delete anything - Dolby still didn't open, so I had to perform a 2nd factory reset!
Luckily, I did find the backup data and backup apps in the settings, which took my setup down to about 25 minutes vs 1.5 hours.
***(NOTE TO SELF) - Don't install n7 music player, again!
tele_jas said:
[UPDATE]
For what it's worth..
I tried replicating the issue so I could give the steps on how to get it working again.....So I downloaded n7 player again, started playing music and then went to Dolby and turned it on. I got the "force close" and went through my steps of removing n7, then going to the Dolby app (in settings) and doing a force stop, clearing the data and cashe - then rebooted and tried opening Dolby again, it did NOT open! I messed around with it for about 30 minutes and even went into the stock recovery and tried wiping the cashe (I think that was what I did). It reset all my apps and data, but didin't delete anything - Dolby still didn't open, so I had to perform a 2nd factory reset!
Luckily, I did find the backup data and backup apps in the settings, which took my setup down to about 25 minutes vs 1.5 hours.
***(NOTE TO SELF) - Don't install n7 music player, again!
Click to expand...
Click to collapse
Yeah, Dolby isn't compatible with every music app. I turn it off while listening to power amp as it locks up. But with YouTube or Google play music, I turn it on. Good things there's a quick toggle
Sent from my ZTE A2017U using Tapatalk
osmosizzz said:
Yeah, Dolby isn't compatible with every music app. I turn it off while listening to power amp as it locks up. But with YouTube or Google play music, I turn it on. Good things there's a quick toggle
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I would forget to toggle and would jack it all up again.. Already performed 2 resets last night, not ready for a 3rd until the bootloader gets unlocked and I flash a custom ROM :highfive: ! So I'll just stick to compatible music apps. ....I like Shuttle+, just not as much as n7 or PowerAmp
Does anyone know if Dolby Atmos has any problem with VLC player?
celticchrys said:
Does anyone know if Dolby Atmos has any problem with VLC player?
Click to expand...
Click to collapse
Just tried it, works fine with VLC!
Dolby Atmos works with Neutron.
What about PlayerPro?
Spotify also works
I think the said apps must be updated by their devs or is it something related to Dolby itself?
If some brave soul with the phone is willing, I'd say re-test power amp.
Right after installing it, without playing any music, go to audio > advanced tweaks, and disable both direct volume control and Bluetooth Direct Volume Control. Just a guess, but similar to how ViperAudio functions, disabling those should make power amp play nice. Not sure about n7 thou, never used it.
icenight89 said:
If some brave soul with the phone is willing, I'd say re-test power amp.
Right after installing it, without playing any music, go to audio > advanced tweaks, and disable both direct volume control and Bluetooth Direct Volume Control. Just a guess, but similar to how ViperAudio functions, disabling those should make power amp play nice. Not sure about n7 thou, never used it.
Click to expand...
Click to collapse
Lol......I'm not brave enough! My phone has been running flawless now since Friday, but Thursday I had to do 2 factory resets... Not ready to "test" and have to do a 3rd just yet.
Maybe later this week, or weekend? I really miss n7, but I kind of forgot how nice (and simple) Shuttle+ is
Dolby Atmos works with Poweramp Alpha Build 703.
Just an update.... Dolbly Atmos no longer FC's on the B27 build while using n7, it just doesn't turn on at all when n7 is installed. The stock EQ works on n7, but you lose the system wide EQ of Dolby Atmos.
I wish there was a way to completely disable the EQ inside n7 player and just use Dolby Atmos. It shows "off", but somewhere in it's code it has something that Dolby Atmos recognizes and won't turn on until it's completely uninstalled.
tele_jas said:
Just an update.... Dolbly Atmos no longer FC's on the B27 build while using n7, it just doesn't turn on at all when n7 is installed. The stock EQ works on n7, but you lose the system wide EQ of Dolby Atmos.
I wish there was a way to completely disable the EQ inside n7 player and just use Dolby Atmos. It shows "off", but somewhere in it's code it has something that Dolby Atmos recognizes and won't turn on until it's completely uninstalled.
Click to expand...
Click to collapse
n7 Player October 19th release - UPDATE
Now, Dolby Atmost disables when the player is on and as long as it's in the recent apps list.... If you close the player, clear it out of the recent apps and make sure it's swiped out of the notification bar, then Dolby will work.
I tried turning off the n7 graphic EQ and other EQ's.......Dolby still didn't work. I then found a setting under "other" (still in the EQ menu) that had the Dolby options (Music, Movie, Talk, ect...)... When I set it to "Music", it sounded really good, but when I tried to open Dolby Atmos to adjust it, Dolby Atmos crashed....So I don't think it's the same "Dolby" and may be the reason behind all the conflicts. I had to uninstall n7 completely to get Dolby Atmos to work again.
Getting frustrated with this... I like Shuttle+ and I also found Rocket Player for $3.99 in the Amazon app store.....But I miss my n7 Player.
Foobar also works very well. I'm using it along with VLC, Spotify and Youtube for my media needs, and every app works with dolby.
disable 10 band eq in n7 it will work
Here's the only problem I have with my new Axon 7:
I'm listening to Beyondpod, and I switch Dolby Atmos on and set it to Voice (I usually have it off because Poweramp sounds better with it's own DVC).
I pause Beyondpod, press play again and Atmos immediately switches to Music mode. Every. Single. Time. Every time I press pause then play, BAM straight to Music mode. What kind of bug is this?
This has happened to me with Podcast Addict, but not whenever I pause. I think it's how the Dolby Atom app is programmed. Certain apps or types of apps seem to trigger certain modes.
Yep, same random issue... Seems better since B29 (USA model), but every so often it'll reset.
I'm rooted and tried a few different "sound mods" that disabled Dolby Atmos.... I liked them, but there must be something with the A7 audio chip that throws other mods off. V4a kept losing volume and resetting to flat (even though the faders showed my settings. A few others made it distort and sound bad. So, I restored my back up and am sticking with DA for now.
Forgot to say I'm stock, B29 A2017U.
Glad it's not just me. Hopefully a patch will sort it out. I really miss Viper, but if you're having problems with it too then I'm in no rush to root to get it back!
I also have this issue... each time a new song/video is played whatever the app used, dolby resets to music preset. It seems to be another glitch of MiFavor/dolby integration. I have also posted in this thread: https: //community.zteusa.com/thread/13346 to no avail. Some moderator advised to clear all the app data, didn't work for me. So it makes dolby quite useless as for me, and the sound output of the G model isn't really its trump card to begin with. I 'm on the B05 build by the way.
Hey guys.
I don't think I am the only one who experience audio stuttering while playing music, but couldn't find another thread about it.
So, initially I thought it's only via Bluetooth, but then it turned out audio skips for some miliseconds even while playing it on the speaker of the phone.
Is there any way to fix that? Please note that player priority DOESN'T have an effect. That's the first thing I've tried.
I am on Oreo.
Could you help somehow?
Thanks
celeronix said:
Hey guys.
I don't think I am the only one who experience audio stuttering while playing music, but couldn't find another thread about it.
So, initially I thought it's only via Bluetooth, but then it turned out audio skips for some miliseconds even while playing it on the speaker of the phone.
Is there any way to fix that? Please note that player priority DOESN'T have an effect. That's the first thing I've tried.
I am on Oreo.
Could you help somehow?
Thanks
Click to expand...
Click to collapse
What audio player do you use and have stuttering? With bluetooth there is a little delay in sound playing for example youtube vid if you dont have at least aptx connection (aptx not original supported by mia1 butpossible with a magisk module).
I use PowerAmp.
Also, I don't have AptX BT headset, but as I mentioned this issue is NOT only Bluetooth connected.