On my last three phones (Nexus 5, 6, and 6P), my song track information in Spotify would display on my Honda Fit (2015) and my Sony head units over bluetooth. With the Axon 7, I no longer get Spotify track information displayed on the head unit. I've done a little research, and there were apparently issues connecting through AVRCP for Spotify a couple years ago, however the issue has been fixed (Fixify is now considered obsolete).
Has anyone else had issues displaying track info on their head units over bluetooth? If so, was there any fix?
yea I do on my Honda worked before but then did update doesn't do anymore no matter what player I use it sucks
Sent from my ZTE A2017U using Tapatalk
I'm dealing with this as well on my wife's Lexus. We had the Note 7, Spotify metadata appeared fine. Got rid of it and bought the ZTE Axon 7, and now it just shows "bluetooth audio connected" -- She's not the happiest in the world. it's weird, because in my 2015 GMC Sierra, it still shows all the song info just fine on my ZTE Axon 7....not sure what gives...
Im pissed cause it used to work on my Axon 7 when I got it but when i took the update it was messed up. Something in update messed it up cause it worked before
Sent from my ZTE A2017U using Tapatalk
I have a 2016 Honda CR-V Touring. When I first connected my Axon 7 to the vehicle, it worked and I got the metadata using Spotify. The next time I got in the vehicle and started the engine, the BT metadata no longer displays. I even had the problem where Spotify will stop playing when the phone goes to sleep. I had a 4 year old Samsung Galaxy Note 2 that worked fine on this same Honda. So after dropping almost $500 for the Axon 7 Limited Edition, I have a partially functioning Bluetooth setup. I'm not very happy and am trying to decide if I'm going to keep this phone since I'm still in the 30-day return period.
FYI -- this issue being discussed on ZTE community and appears to be related to NOUGAT 7.1.1 release. various reports are that 7.1.2 will (hopefully) fix connectivity, streaming, and metadata BT issues.
reference ZTE community thread HERE.
which references a NEXUS product support forum HERE.
Just in case: ZTE Axon 7 build B19 and B25 are both NOUGAT 7.1.1.
Related
Hello everyone,
First some background...every phone I've had up until this year has worked perfectly fine with my Eclipse Navigation Head Unit (Eclipse AVN726E) via Bluetooth. Can make and receive calls no problem.
However, this year I purchased the Galaxy S3 and I had a huge issue. The phone can make a call and the person can receive it, however, I hear nothing on my end. I can't hear the ringing, or the person answering the phone. Needless to say, this makes the bluetooth impossible to use in the car. The Galaxy Nexus worked perfectly fine, but now the Nexus 4 is exhibiting the same issues the Galaxy S3 did.
Clearly, it's an issue with the newer Bluetooth versions (firmware maybe), so is there anyway to program the phone to use older (more compatible) firmware for the bluetooth stack? Again, the Galaxy Nexus worked perfectly, but the new phones this year seem to all have the same issue.
Hopefully someone else has had this issue with their built in navigation or bluetooth head units. Ugh, so frustrating.
TIA.
I have the same issue with my 06 BMW 330i, factory head unit, with a twist.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution to this as well, as my Nexus S worked perfectly before the Nexus 4.
Yeah, it's not looking good w/ the solution.
Totally sucks that newer phone hardware is incompatible with head units that were manufactured prior to like 2010...at least that's what it seems like right now. Eclipse, my head unit manufacturer is less than responsive as well, so I'm not getting anything from that end.
I was hoping there was a way to downgrade the bluetooth firmware on the phone or something to make it compatible, but I don't even know if that's possible.
Nothing you can do most likely
Sent from my Nexus 4 using Tapatalk 2
surferdude73 said:
I have the same issue with my 06 BMW 330i, factory head unit, with a twist.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution to this as well, as my Nexus S worked perfectly before the Nexus 4.
Click to expand...
Click to collapse
Have you gotten the Android 4.2.1 update yet? It looks like there's some Bluetooth stuff in there.
Acuity said:
Have you gotten the Android 4.2.1 update yet? It looks like there's some Bluetooth stuff in there.
Click to expand...
Click to collapse
Yeah, I updated before the audio dropping issue.
Strangely enough, I have since made 3 calls through BT at 10, 15 and 25 minutes respectively with no issues. I'll continue to monitor.
Well, I have found my issue (and it's unsolvable so far). My car simply isn't compatible with any phones with the Qualcomm S4 Pro processor. I tested a few other phones. Droid DNA (S4), Galaxy S3 (S4), Nexus 4 (S4)...none of them work.
HTC One X+, Galaxy Nexus...both work fine. X+ uses Tegra 3 and GNex uses OMAP. So yeah...clearly it's an issue with the S4 processor and chipset getting audio from my phone to my head unit.
I can make calls, receive calls, everything, but no audio is transferred at all...I can't even hear the phone ringing. It's a shame too...because all of the best phones use S4s now. Grrrr.
Want to add this thread. i have had the same exact issue OP mentioned with Sprint variant Galaxy S3 and stereo Eclipse AVN726e.
Was so disappointed that i Installed customer CM10 at the time which wasn't even stable yet but did not solve problem. Gave up the last couple of months.CM10.1.0 Release is on the phone now and today to my surprise after pairing my phone back up to my AVN726e I was able to hear the voice of other party on the phone when it accidentally connected when I was on the phone and started my vehicle.
So for OP and others alike see if CM10.1 is the answer for you as well now.
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
cfn87 said:
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
Click to expand...
Click to collapse
I had a nightmare with my note 4 and it's bluetooth, it was awful.
I got a Note 5 and bluetooth was absolutely awful, I had to return it and got a new one and all is good. Very good bluetooth
Having bluetooth issues with my Note 5 and an my Chevy Equinox. The phone works perfectly with all my other bluetooth devices though. I think its the car but my wife's iPhone works perfectly with the car. Who knows.
I have a thread in the Troubleshooting sub-forum looking for help with my BT.
See here.
Any ideas would be greatly appreciated!
Also - OP - what carrier are you with?
I have a nexus 6 and thinking about getting a note 5 but I have never had any issues with Bluetooth on my nexus
About every 20 minutes mine chooses to disconnect from my bluetooth speaker.
I haven't had a single issue with BT yet in my car or with my speaker at home. I use both daily.
Bluetooth on this phone (A2DP streaming specifically) is fantastic. I have had problems with horrible sounding overly compressed bluetooth audio streaming in my car (old head unit, no Apt-x or anything supported) since Android switched bluetooth engines after version 4.1. All the nexus devices (I've had a few) apparently only support SBC streaming, so this leads to the horrible sounding audio with some receivers, I presume. I just returned a Nexus 6 because of this very issue. I couldn't tolerate it in the car, music sounded like garbage. This was an issue with the Note 4 when I bought it last year as well. I don't know what Samsung did on the Note 5, but BT audio sounds pretty damn good again. I'm so glad, because nobody seems to care about this issue so I had almost lost hope. Props to Samsung for improving it.
Thats great news! I was to the point of wanting to beat my Note 2 with a hammer after every bike ride with my Bluetooth headphones! - Every time I would turn my head they would cut out. I'm looking forward to trying with my new Note 5 on my ride tomorrow.
This is literally my only complaint on this phone so far and could very well be an easy fix. Looked around and couldn't find any posts on this.
I upgraded from an S4 to the MXPE. Since the upgrade my Metadata for Google music no longer transfers to my head unit (Sony XAV602BT) in my vehicle. Not all that big of a deal because the controls still work fine off the head unit. But, cmon, who wants to look at a blank radio screen? Least gimme the songs title or a damn album art.
Looking for any ideas or thoughts to get this working.
Sent from my XT1575 using Tapatalk
Your are correct. Beat up on a bit on Moto over on their forums. I have the same issue. It is a bug of some sort. Started this thread over it...
http://forum.xda-developers.com/moto-x-style/help/bluetooth-communication-to-head-unit-t3213836
It works some of the time.
https://forums.motorola.com/posts/b7b030ee52?commentId=987600#postComment
Irieone said:
Your are correct. Beat up on a bit on Moto over on their forums. I have the same issue. It is a bug of some sort. Started this thread over it...
http://forum.xda-developers.com/moto-x-style/help/bluetooth-communication-to-head-unit-t3213836
It works some of the time.
https://forums.motorola.com/posts/b7b030ee52?commentId=987600#postComment
Click to expand...
Click to collapse
Much appreciated, we shall see what comes with future updates... Hopefully they fix this little but, then I will be completely satisfied with purchase. For now, just mostly satisfied lol
We have Moto's attention. They are requesting logcats. Please head over to the Moto thread https://forums.motorola.com/posts/b7b030ee52
Your help is appreciated.
My headunits (in a 2012 Honda Odyssey, or 2013 Honda Civic or 2012 Toyota Rav4) are all showing the metadatas from both my audio players (player Pro) or my podcast player (PocketCast) when playing from the Moto X over Bluetooth.
Maybe it is an issue with the car or the application used for media playback?
timeToy said:
My headunits (in a 2012 Honda Odyssey, or 2013 Honda Civic or 2012 Toyota Rav4) are all showing the metadatas from both my audio players (player Pro) or my podcast player (PocketCast) when playing from the Moto X over Bluetooth.
Maybe it is an issue with the car or the application used for media playback?
Click to expand...
Click to collapse
It is happening with my Sony head unit in vehicle and a Denon home audio receiver. The newer versions of Bluetooth should also be backward compatible.
Saw that on the Moto forum earlier today, haven't had a chance to get a log yet. Will be taking car of tomorrow morning. Thanks!
Same issue.. I only get the time for the song playing.. but no title on the head unit. Had no issue before with my other phones. I'd rather have the song title instead of the time it's played.. lol..
jpinoy said:
Same issue.. I only get the time for the song playing.. but no title on the head unit. Had no issue before with my other phones. I'd rather have the song title instead of the time it's played.. lol..
Click to expand...
Click to collapse
I couldn't agree more! Go follow the instructions on the moto forum so send a log of the data. The more people helping should hopefully yield a fix for the problem!
Sent from my XT1575 using Tapatalk
Hey all, I own a 2017 Honda Civic with the Android based infotainment unit. The unit is quite slow and laggy at times when I have my apps I wish to have running on it installed (Google play services, Igo, PlayerPro & tunein radio)
So I am in the market for a good and reliable Android radio, preferably a unit with 2+gb or ram and a decent amount of internal storage.
Anyone else out there been looking? I've looked at Phoenix and ownice but I haven't gotten firm answers to my questions I've had and there hasn't been a lot on reviews after a few months of ownership.
In the past I've owned a offbeand rockchip unit, a crappy newsmy & Indash units. So I've done my share of owning horrible units and seeing how I plan to keep this car for a while I'd like to get a unit that will last a while as well.
Joying seems to be the brand I hear about often in here, sadly they don't have a unit for my year civic.
Edit. I did some searching and found this...
Dasaita 10.2" Android 8.0 Car GPS Radio Player for Honda Civic 2015-2016 with Octa Core 4GB 32GB Auto Multimedia Stereo video 4G
http://s.aliexpress.com/7bQFfI7n?fromSns=
It's running a px5 octacore. Seems like these guys seem to know their stuff from research?
Sent from my ONEPLUS A5010 using Tapatalk
Well I took a leap and bought the unit. Huge mistake. The unit is flawed. Horrible FM reception, the audio goes out completely on the radio whenever the automatic doors lock or unlock and have been totally left high and dry by the company and Quick Yaun who is the representative from them.
Flat out acoid this company and their garbage. Apparently Pheonix audio in the USA is the same company under a different name. So I would also avoid them as they are just a reseller of dasaita
Sent from my ONEPLUS A5010 using Tapatalk
kwalsh24 said:
Well I took a leap and bought the unit. Huge mistake. The unit is flawed. Horrible FM reception, the audio goes out completely on the radio whenever the automatic doors lock or unlock and have been totally left high and dry by the company and Quick Yaun who is the representative from them.
Flat out acoid this company and their garbage. Apparently Pheonix audio in the USA is the same company under a different name. So I would also avoid them as they are just a reseller of dasaita
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
That sucks man. I cant stand our radios. Old ass OS with just as old hardware in a brand new car.
It's true! My factory unit works OK with a few add-on programs but anything past having Igo & tune in radio installed the thing starts to lag badly. I attempted to put the store, music and services on the unit but that brought the thing to a crawl. For now I'm back using the 8 year old radio in my next to new car till the replacement mainboard comes for the dasaita unit. Here's hoping it works otherwise I wasted a good chunk of change in a radio that's a doorstop lol.
Sent from my ONEPLUS A5010 using Tapatalk
I believe the slowdown is coming from google play services, dont install Google Play Services as it i will deeply bog down the HU.
Hey guys, looks like this forum is pretty quiet for the Axon 7 mini but if you see this, I'm considering getting one as a media player (mostly music) in compliment to my Axon 7 which is my daily driver phone. Does the mini output bluetooth audio at hi res like it's big brother? I know it has an AKM DAC for the 3.5mm socket but I mostly use BT either in my car or on headphones now, so that is very important.
If not, I may as well just use my wife's old Oppo F1f when her new phone arrives. Performance is similar but not hi res audio.
Decided to get one anyway, so cheap, AU$149 new in box from retail store, grey one too, not keen on gold. I'll put my 128Gb card from the Axon 7 in it as I put a 256Gb in that recently.
My Axon 7 is stock and used for work but the mini can be anything I want
So, as to stock ROMs, what is the latest one you can root ok? I'm downloading 7.1.1 B15 for my G variant, it doesn't find any OTA updates from it's old original global ROM which is ZTE B2017G APV1.0.0B01
In Australia.
RobboW said:
Hey guys, looks like this forum is pretty quiet for the Axon 7 mini but if you see this, I'm considering getting one as a media player (mostly music) in compliment to my Axon 7 which is my daily driver phone. Does the mini output bluetooth audio at hi res like it's big brother? I know it has an AKM DAC for the 3.5mm socket but I mostly use BT either in my car or on headphones now, so that is very important.
If not, I may as well just use my wife's old Oppo F1f when her new phone arrives. Performance is similar but not hi res audio.
Click to expand...
Click to collapse
No hi-res bluetooth. Just aptX. If you install the one.
So far I tried three ROMs, cannot update it.
Buyers remorse kicking in.......
Maybe stuck like those variants in GB and Canada.
Edit: thinking about the process of updating Axon 7, maybe there is a road map for updating the mini too. Been searching the different ZTE support pages around the world and downloading some different ROMs. Found a later MM ROM to try before going N. Hoping that is the answer.
Edit: Looks like it's stuck on this very old ROM, the A in the version name is looking like the problem. A for Australia, and no updates for Australia. Booooo!
Can they be recovery forced? But then brick? I guess it would just refuse.
Edit: Did MM B12 update by recovery so got it to global rather than Australia. Now it's on the update road via SD method Going N B13 now, what's the latest I should go that can be rooted ok?
So once I got it away from the really old Aus ROM via recovery to MM B12 it all went very easy. Now on N B16.
For AU$149 new in box, the A7 mini is a bargain!
Guys, I think there's a myth I can dispell straight away between Axon 7 and Axon 7 mini. Having both now, I can tell you straight up, despite both having an AKM DAC the big brother absolutely destroys the mini with 3.5 jack output into a line in device. It's a MUCH louder amp. Could easily drive it's output directly into car hifi amp system without a HU.
Going between the two with a pair of decent 32 ohm buds is not quite as clear cut though, the A7mini has a nice and more balanced, clear sound, decent volume but the A7 still punches harder, it brings more depth into the bottom end so feels bigger and that's how I prefer it.
As to that crazy output to line in devices like a portable speaker with the A7, it's actually a bit too much and have to cut the volume level back at least two steps so for this purpose the mini is more sensible, but if you're driving cans, go A7 every time, especially if they're higher impedance than the normal 32 ohm stuff.
I still like the mini, it's a very nice phone and at the current runout price point nothing else gets near it, especially with that gorgeous AMOLED screen and premium external finish.
RobboW said:
Hey guys, looks like this forum is pretty quiet for the Axon 7 mini
Click to expand...
Click to collapse
Hi. This forum is quiet, but there is a lot of useful things about Axon 7 mini on the Russian 4PDA forum. http://4pda.ru/forum/index.php?showtopic=891109&st=1100#entry85892739
You can just use a google-translated version of this, I suppose.
nikaiako said:
Hi. This forum is quiet, but there is a lot of useful things about Axon 7 mini on the Russian 4PDA forum. http://4pda.ru/forum/index.php?showtopic=891109&st=1100#entry85892739
You can just use a google-translated version of this, I suppose.
Click to expand...
Click to collapse
Thanks for that, I'll have a look when I have some spare time, see if there's anything that takes my interest. I have to decide if I'll mod this phone to a custom ROM as we know it will never get another update from ZTE. Mine is on N B16 so that's end of the line.
I guess the biggest thing is if custom ROMs have the audio performance as good as with stock. I use mine in the car to play music through the 3.5mm jack. Got Next Track app to skip tracks back and forward with screen off by volume rocker. Works well. Sounds pretty good on bluetooth even, because Dolby Atmos does work and combined with gentle equalisation in Poweramp makes for a fairly well defined sound. My headunit doesn't do Hi Res bluetooth so this phone is ideal for the car. Despite the stock headunit, I've built a kick ass hifi off of it.
Liking the A7 Mini, doing much better on battery than expected. It idles quite efficiently. With light use I get it to go for two days on a charge. I ended up taking my personal SIM out of my Axon 7 and put it in the mini. Just my work SIM in the A7 now. That improved battery life on the A7 too.
Considering the better than expected battery range I'm not even looking at rooting or modding it.
Even got my brother an A7 Mini to replace his iPhone 6S which got the latest iOS update and made it useless..... Good one CrApple