Related
Disclaimer: I've searched the forums day after day and have found nothing that helps me in any way.
Hey guys, I'll get right down to this:
I've got a Moto X VZW MM 32GB, initially shipped with 4.2.2 and running 4.4 as soon as I got it activated.
Everything on the Moto X works great, fluid graphics, fast app opening, battery (for the most part). But I've got a bone to pick with bluetooth, as well as Android OS.
First off, the bluetooth bugs, or what I'd like to call, The Blues.
Problems
- I have Pioneer Premier FH-P800BT, running great for the past 6 months or so. I originally had a Galaxy Nexus from VZW, with CM10.2 on it and bluetooth worked flawlessly, save for an obvious quality issue with phone calls/echo cancellation. A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
- On all bluetooth devices with A2DP, sometimes the quality is great, sometimes it does what I like to call a "stucho" aka a stutter/echo. The best way I can explain it is if you've ever heard a record skip back and keep playing the same part, multiply that by like 100x. Or better example, for you Galaxy Nexus users (other phones too, if they do it) when your phone would freeze from being overloaded, and it ultimately crashed (non responsive to anything, screen won't come on, or maybe stuck on) and the audio get's hung. The sound does that on the Moto X, but it continues playing the track without pausing/skipping. It's extremely annoying, and mostly occurs when surfaceflinger is active (I'd assume that's what it is), as it's when anything animation-wise caused by user input occurs. I've also had the audio deteriorate in the same manner, but after it does the weird stucho effect, the audio slows down a bit, noticeable, like, listening to "We Found Love" by Rihanna sounded like a man singing it, and then it will speed up and go too fast after about a minute, and then resume normal playback. Despite completely pausing on my Galaxy Nexus, that phone never did have the audio issues this Moto X does, and it occurs on every A2DP device I've tried (BMW iDrive, Hyundai Sonata factory radio, Philips SBT series, my Pioneer headunit).
Second issue I'm having: Android OS
- I've tried ART and running Dalvik as the runtime, and on both, after weeks of running them, I notice that throughout the day, 3-4% battery drain per hour, with nothing in recent apps, wifi on, and all VZW software except for backup assistant disabled. I'm not complaining because I tend to make it to the end of the day with 2 1/2 hours SOT and and about 10% left on battery, but I'm curious as to why it's not making it any further. I don't have much installed. Dropbox, Facebook, Exchange account, Wallet, and other programs that don't run in the background (OS Monitor, Dots (game), etc). While my SOT can show 2 1/2 hours, it's only taking like 35% of the battery while Android OS shows like 20% or more, and shows CPU time around 1:45 hrs.
Any insight on either of these issues would be appreciated. I love the phone, everything else is perfect, but these 2 things are kinda irking me because I know this isn't the way the phone should be operating, moreso with the bluetooth bug.
Bump
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Glad to hear that yours is working great, mine usually does. I'll also add that call quality is top notch over bluetooth, much cleaner than on my Gnex. It's just A2DP sometimes will do the above mentioned, and it's so annoying. Using the headphone jack it is fine, it's specific to bluetooth.
As for battery tips, I've tried a good portion, short of rooting the device and greenifying it. I ran my Gnex forever, and I kid you not, swapped/flashed at least 60 roms, so I know what I'm doing in terms of de-bloat and rooting and such, but if not for these bugs, I'd be happy with the phone itself.
Thanks for the tips though I'll look, but in the mean time, anybody else ever noticed what I'm talking about?
kj2112 said:
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
I don't have stutter/echo problems but after taking a call on it and trying to go back to music the app acts like it is playing but no music is heard. I have to cycle BT on/off or cycle the power on the adapter. This is on a car adapter, the Kinivo BTC450. The adapter was flawless with an iPhone 5s and pretty good with a nexus 5. I am hoping it is 4.4 bugs and 4.4.2 will clear it up. It is supposed to launch Feb. 1 in Europe with 4.4.2 so hopefully we'll all see an update. I'm tinkering with the idea of going back to 4.2.2 to see if it is any better.
Sent from my XT1053 using Tapatalk
Well, I've solved 2 of the 3 problems I was having. Android OS no longer takes over my battery, and thankfully, more people today had posted that Snapchat was a battery hog on 4.4 (or on any OS version for that matter). And I wasn't just hallucinating, considering at 50% battery, SOT was ~ 1 hr while Android OS showed like almost 2 hours of being active, and percentages were like 33-35% for SOT, and 20-25% for Android OS. So I think now that 33mins of SOT at 90% battery and Android OS only showing 5% usage, issue's resolved
Bluetooth stuttering was seemingly with all audio services on my phone, but after I tinkered, I found anything that passed through the built-in EQ was stuttering when surfaceflinger was active. And oddly enough, only with bluetooth, and not even all the time. So in short, disabling the EQ on the phone seems to have fixed the weird jerking/echo/stucho sound period. I'll test a bit further, but so far that seems to be good.
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
I can confirm that for the past 2 days, with the Audio Effects/EQ disabled, I have no stutter with audio over bluetooth, it plays much smoother now. Also, uninstalling Snapchat has 100% resolved my Android OS battery drain. I was only getting an hour and a half of SOT with 30% battery left before, and now I successfully hit 50% battery with right at 2 hours SOT, so it's definitely made a huge difference. That's with dropbox, exchange account, facebook, and a few other random apps running. Worth a shot to see if it really does it for you, but YMMV
murso74 said:
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
balleron24z said:
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
Click to expand...
Click to collapse
Any resolution on this? I have the exact same problem with my Pioneer head unit. So annoying having to repair every time!
Only problem I'm having with Bluetooth in my car is that incoming phone calls break my audio connection. Instead of resuming, the audio ceases and i have to unpair and repair to get my audio back.
balleron24z said:
A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
Click to expand...
Click to collapse
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Se7enLC said:
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Click to expand...
Click to collapse
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices. My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
JoeSchmoe007 said:
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices.
Click to expand...
Click to collapse
It was actually 4.2 where Android switched from BlueZ to BlueDroid. In 4.3 and 4.4 there were significant developments to "finish" that implementation. On my Nexus, 4.2 was worthless, but 4.3 and 4.4 worked great. It's certainly possible that Motorola botched something with their upgrade to 4.4 - or maybe Motorola had their own Bluetooth stack separate from AOSP.
My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
Click to expand...
Click to collapse
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Se7enLC said:
...
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Click to expand...
Click to collapse
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Here is another quote from now deleted thread:
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
If you have tested and working instructions on how to downgrade from 4.4.2 to 4.2.2 on 1053 I really would like know them.
JoeSchmoe007 said:
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Click to expand...
Click to collapse
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
To answer a few questions regarding this:
1: You most certainly CAN flash any ROM you wish to a DE Moto X, you just need to unlock the bootloader. When the BL is unlocked, it allows you to flash whatever you want. Look it up and do your homework, it's essentially a Nexus, without the AOSP out of the box.
2: The if 4.4 had so many bluetooth bugs, then why did my Gnex running AOSP 4.4 (the hacked together one that had driver bugs) work PERFECT, and I mean legit PERFECT with bluetooth on all devices I used? The point is moot with the bluetooth stack being bugged. Obviously Google tested this on MANY of their internal devices before releasing to Nexus devices and the AOSP branch. Y'all have no logic if you believe otherwise. I DO, however, agree that it's possible that Moto is using a non-standard or non-AOSP bluetooth stack, or they have modified the bluetooth config to the point where it doesn't work.
4.4.2 for the Moto X didn't fix my problem, although it supposedly did fix some bluetooth bugs. I can still use the phone with a 2013 Hyundai Sonata Limited's bluetooth, and it pairs perfectly every time. This seems to be a hardware-specific issue, as I see people with older model Pioneer/Kenwood/etc. Bluetooth 2.0 headunits having issues, as well as with some hands-free BT units too. But on newer vehicles, some radios don't have the problem. I'm gonna file another ticket with Moto and see if I can provide proof to the problem.
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
No moto x is a nexus. There is no downgrading the bootloader without heavy risk. The stories you've read here about downgrading bricks WILL happen to the dev edition just like the other unlocked moto's. Mark my words.... please.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------
Careful who's advice you follow here guys....unless you have money to burn.
And yes...totally agree with the above.....do your homework.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:39 PM ----------
Se7enLC said:
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
Click to expand...
Click to collapse
No. Downgrading is a HUGE brick risk. Trust me.
Moto x's are nothing like a nexus when it comes to the bootloaders.
Dev edition is like the rest....but you keep warranty. That's all!
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
Click to expand...
Click to collapse
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
Click to expand...
Click to collapse
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
Click to expand...
Click to collapse
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Se7enLC said:
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Click to expand...
Click to collapse
I can't speak for what dev edition means on other phones....but for the Moto x, Dev edition means you can unlock bootloader, same as many other models....though your warranty is still good......and once unlocked, its EXACTLY the same as any other unlocked Moto x as far as flashing rules and RISKS.
I don't claim to be an expert on precisely why and what causes a brick, but I've read more than enough on here lately to know that downgrading from 4.4.2 is playing with fire. LOL
Funny....I just went to flash a 4.2.2 rom on my Nexus 7 the other day and got an error about incompatible boot loader (I was on 4.4.2 at the time) and I remembered, crap...that's right! So I flashed the previous bootloader version....then the 4.2.2 rom. Done ...10 minutes and zero issues. LOL. Not sure why Motorola had to make things harder/different.
Sent from my Nexus 5 using Tapatalk
Back to the original topic - I took the upgrade to 4.4.2 last night:
- Disabled things like XPosed
- Re-flashed stock recovery (using fastboot)
- Applied update
- Re-flashed CWM recovery
- Re-applied root and xposed
I didn't do anything else, apart from app upgrades that happened to come in. When I got in my car this morning it immediately automatically connected. Could be a coincidence, or maybe that upgrade fixed the bug.
EDIT: I was in and out of the car probably half a dozen times today, works perfectly now, auto-connected every time!
So my radio came in today and android auto doesn't work. It says my phone was not compatible. I have a rooted note 4 running android 5.0.2 (cm 12). I also used my fiancée sg5 with the new stock 5.0 and it still doesn't work! Anybody care to help?
Anybody?
Did you try calling pioneer?
I'm having the same issue. I have a rooted T-Mobile LG G3 running 5.0.
I thought I was the only one
smalltownbird said:
Did you try calling pioneer?
Click to expand...
Click to collapse
Close on the weekend
There are YouTube videos of car audio installers using it so it has to work
Same here, I have an HTC One M8 rooted and its not working for me either. I read the manual and apparently you need a CD-MU200 interface cable from pioneer. Don't know if that's bulls**t or not, but we'll find out. I have the USB setup so that I can use the built-in port in my car. I don't know if that's what the reason is or not. I'll have to call pioneer on Monday.
Sent from my HTC One_M8 using Tapatalk
Well that's three people with the same problem
I think you need the Google apps loaded for one thing, and having an account enabled may be even better.
Lollipop is essential at this time, and I think 5.1 is even better.
Nexus also has a better chance of working.
I am trying to get developer mode working and I am mainly using my Nexus 7 2012 w/ 5.1 because my 2013 N7 and N9 both are still on 5.0.
But its just about api21 that AA runs on. 5.1 has api22 and its confirmed AA is working on "normal" lollipop, I mean 5.0.x
I'm running 5.0.1 on my M8 and Android Auto isn't working
Sent from my HTC One_M8 using Tapatalk
Also it's important to have latest GMS installed.
http://www.apkmirror.com/apk/google-inc/google-play-services/
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)
brainscollector said:
Also it's important to have latest GMS installed]
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)
Click to expand...
Click to collapse
Thanks for the help. Unfortunately it didn't work for me. I went on the reviews for android auto app on Google play and it seems a lot of other people are having the same issue.
Theres a new update on pioneer site, but didn't fix problem.
Maybe
You can generally find the Android Auto button located on the home screen of your car's digital display. How to navigate to the home screen will vary by manufacturer, so check your car's user guide.
I plugged in my phone, found the Android Auto button, but it won't open.
If this is the first time you’re using Android Auto in a particular car, be sure to unlock your phone and accept the terms and conditions on your phone’s screen after you’ve connected and touched the Android Auto button on your display.
Also, make sure that the "Only connect to known cars" setting in the Android Auto app is unchecked.
The voice command button takes me out of Android Auto.
My USB cable isn't working.
Not all USB cables will work with all cars. Your car's user guide should have information about the best USB cable to connect your phone to the display.
Click to expand...
Click to collapse
https://support.google.com/androidauto/
killa2009 said:
Theres a new update on pioneer site, but didn't fix problem.
Click to expand...
Click to collapse
Update for what ? Pioneer firmware ? Can you link ?
mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
Pioneer nex 4100 radio
mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^
brainscollector said:
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^
Click to expand...
Click to collapse
Yup, I still updated but no change.
Today I installed a new Sync update in my 2011 Lincoln MKS, and when I tried to pair my Nexus 6 (running the AICP ROM), the phone (or was it the car?) asked (for the first time) if I wanted the car to read my messages. I replied Yes, and it caused the phone's Bluetooth share service to force close. I had to clean flash the ROM and gapps, delete the device from the car, and re-pair the phone and the car but tell it No do not read messages. Don't know why I got the FC or why I couldn't undo the damage. Don't know what Ford/Lincoln did to Sync, but beware.
@almahix,
My stock, rooted N6 (5.1) pairs without problems with my 2015 MKC. And yes, it reads SMS messages.
Don't know if the problem is your ROM or the Sync update.
cam30era said:
@almahix,
My stock, rooted N6 (5.1) pairs without problems with my 2015 MKC. And yes, it reads SMS messages.
Don't know if the problem is your ROM or the Sync update.
Click to expand...
Click to collapse
Interesting. I'll have to try it with stock.
Yeah let me know, now that I know there is an update I'd like to install it but want to make sure it works, if it ain't broke don't fix it.
ChristianJay said:
Yeah let me know, now that I know there is an update I'd like to install it but want to make sure it works, if it ain't broke don't fix it.
Click to expand...
Click to collapse
After extensive testing today, the problem was traced back to CM 12.1 and ROMs derived thereof. AOSP based ROMs and stock do not exhibit this anamoly. Sorry for the premature alarm.
almahix said:
After extensive testing today, the problem was traced back to CM 12.1 and ROMs derived thereof. AOSP based ROMs and stock do not exhibit this anamoly. Sorry for the premature alarm.
Click to expand...
Click to collapse
Not premature, and no reason to apologize. People need to know.
I went for it and no problems, I'm running stock though. Great much needed update.
Unbelievable.
almahix said:
Today I installed a new Sync update in my 2011 Lincoln MKS, and when I tried to pair my Nexus 6 (running the AICP ROM), the phone (or was it the car?) asked (for the first time) if I wanted the car to read my messages. I replied Yes, and it caused the phone's Bluetooth share service to force close. I had to clean flash the ROM and gapps, delete the device from the car, and re-pair the phone and the car but tell it No do not read messages. Don't know why I got the FC or why I couldn't undo the damage. Don't know what Ford/Lincoln did to Sync, but beware.
Click to expand...
Click to collapse
Man, no update for years and now this. Has of last week I tore out the sync system in my car because it was giving me problems with lollipop and text messages. I was not sure that Ford would ever update the system, it hadn't since 2012. I really thought they left us in the cold. Damn, wish they would communicate with their customers a little more and keep timely updates. Now I'm pissed but thanks for the heads up.
I only stumbled upon it by visiting the Lincoln owner's website. I had no problems with SYNC on any of my phones or Android versions with the original 2010 SYNC or the update, except the CM 12.1 issue I found.
Sent from my Nexus 6 running AICP 9.0
Not the same for me.
almahix said:
I only stumbled upon it by visiting the Lincoln owner's website. I had no problems with SYNC on any of my phones or Android versions with the original 2010 SYNC or the update, except the CM 12.1 issue I found.
Sent from my Nexus 6 running AICP 9.0
Click to expand...
Click to collapse
My only problem was with the sms text reader and responder program I was using. When I was streaming Pandora and a SMS would come in, the program would ask me if I wanted it read, when I responded yes, it would read the Sms. But after that when it would give up the feed back to whatever streaming service I was using I'l always get the error,
"Bluetooth sharing as stopped working. Have to reboot to have the phone function with my ole sync system.
Hi all, Since I upgraded my stock unrooted Verizon N6, my Bluetooth does not pair with any device at all. Does anyone else have this issue? I searched for a similar thread, but could not find one, so my apologies if this is duplicative. Any help is appreciated.
johnplopez said:
Hi all, Since I upgraded my stock unrooted Verizon N6, my Bluetooth does not pair with any device at all. Does anyone else have this issue? I searched for a similar thread, but could not find one, so my apologies if this is duplicative. Any help is appreciated.
Click to expand...
Click to collapse
will try now with my anker bluetooth speaker..
im on stock mmb29k...
il let you know if i have the issue
edit
mine paired
What do you mean by upgraded? OTA update, or did you flash a rom? The only issue I've ever had is Bluetooth disconnecting/ reconnecting. Has become an alarm saying I should reboot, lol. Works fine afterwards.
It was an OTA update. Cannot pair with any Bluetooth device.
Larzzzz82 said:
What do you mean by upgraded? OTA update, or did you flash a rom? The only issue I've ever had is Bluetooth disconnecting/ reconnecting. Has become an alarm saying I should reboot, lol. Works fine afterwards.
Click to expand...
Click to collapse
I noticed my Plantronics Legend connecting/disconnecting a lot yesterday and a reboot fixed it too. Sounds like that is a good gauge.
JimSmith94 said:
I noticed my Plantronics Legend connecting/disconnecting a lot yesterday and a reboot fixed it too. Sounds like that is a good gauge.
Click to expand...
Click to collapse
So I went to the Google Forums page, wiped cache. Didn't work. Factory reset the device and did not restore previous settings. Treated it as a new phone setup. Problem solved. It appears as though a 3rd party app conflicts with the Bluetooth. I've been kind of picky which apps I reinstalled, so so far, so good.
Does anyone know where i can get a ZIP of the latest OTA update for the ATT version of the axon m. My phone will not get software updates over the air and idk why.
Having the same issue now, always giving "Network unavaliable".
Running CN 1.9 and I'm located in The Netherlands. The ZTE website barely functions and I can't find any .zip with the update
I'm no longer using the axon m as a daily driver due all the bugs and issues I'm experiencing with this device. The hardware is solid but the software sucks
smiba said:
Having the same issue now, always giving "Network unavaliable".
Running CN 1.9 and I'm located in The Netherlands. The ZTE website barely functions and I can't find any .zip with the update
I'm no longer using the axon m as a daily driver due all the bugs and issues I'm experiencing with this device. The hardware is solid but the software sucks
Click to expand...
Click to collapse
Good morning, I confirm, I have the same issue from UAE. It looks like server for updates are offline.
I don't want think about what's happening about the USA blocks....
---------- Post added at 01:40 AM ---------- Previous post was at 01:35 AM ----------
Here it is the link I found: https://www.leakite.com/2018/03/zte-axon-m-blade-z999-firmware.html
but also here... March is the latest one.
sev7en said:
Good morning, I confirm, I have the same issue from UAE. It looks like server for updates are offline.
I don't want think about what's happening about the USA blocks....
---------- Post added at 01:40 AM ---------- Previous post was at 01:35 AM ----------
Here it is the link I found: https://www.leakite.com/2018/03/zte-axon-m-blade-z999-firmware.html
but also here... March is the latest one.
Click to expand...
Click to collapse
Same for me here. It's apity because they promised we will get Oreo in may. Let's hope, that they bring the servers online again some time.
Server for updates and forum down... stuck on 1.11.
Till now offline...
Been trying to figure out whats up with the updates, the following error is logged:
com.zte.zdm.g.a.k: Unable to resolve host "dmcn.ztems.com": No address associated with hostname
Seems like someone changed the DNS at ZTE without realising some services might depend on it .......
I really do love this device, but I think at this point it's best if I offload it for as much money as I can recoup because I doubt this thing will get any future development, let alone updates.
Till now blocked and... Did you see also the ZTE Market is out of range?
Servers seem to be back online. No "network unavailable" error anymore!
Can confirm, servers are back online
Huge 3.2GB Update arrived!
Axon M CN 2.0
Downloading now...
Hi,
I confirm. Yesterday the CN 2.0 with Android 8.1.0 was installed via OTA for my chinese Axon M ... putting disorder in my custom GAPPS installation.
And this update drain the battery very fast, 5 times faster but is very nice and ... faster. I am searching why (for the battery) reinstalling GAPPS, mainly the accurate Google Service.
MJ
MadMax_7 said:
Hi,
I confirm. Yesterday the CN 2.0 with Android 8.1.0 was installed via OTA for my chinese Axon M ... putting disorder in my custom GAPPS installation.
And this update drain the battery very fast, 5 times faster but is very nice and ... faster. I am searching why (for the battery) reinstalling GAPPS, mainly the accurate Google Service.
MJ
Click to expand...
Click to collapse
I can confirm every point. Except the battery draining. In the beginning the beattery drained very fast, but after 2 times reloading it seems to get to normal again. The update feels very smooth and brings many new settings but also one huge problem. As you told every google App does not longer work properly, or the apps can't get the connection to the google servers. I tried everything. deinstall everthing, reinstall the apps...always the same...the problem seems to be the "google play service" app. I don't see any other chance now and will do a factory reset in the afternoon.
Please keep us informed, if you bring the Gapps back to properly work. I will do the same.
If there is a solution please let me know. I had the same problem after upgrade to AXON 2.0. Battery drain damn fast and cannot use Google apps.
lawin1207 said:
If there is a solution please let me know. I had the same problem after upgrade to AXON 2.0. Battery drain damn fast and cannot use Google apps.
Click to expand...
Click to collapse
Did you perform a factory reset?
Droggi87 said:
I can confirm every point. Except the battery draining. In the beginning the beattery drained very fast, but after 2 times reloading it seems to get to normal again. The update feels very smooth and brings many new settings but also one huge problem. As you told every google App does not longer work properly, or the apps can't get the connection to the google servers. I tried everything. deinstall everthing, reinstall the apps...always the same...the problem seems to be the "google play service" app. I don't see any other chance now and will do a factory reset in the afternoon.
Please keep us informed, if you bring the Gapps back to properly work. I will do the same.
Click to expand...
Click to collapse
...didn't work. I'm very disappointed right now. Had to switch back to my Axon 7. Hopefully it will work again with a futures google play or Firmware Update. I will wait a few weeks.
I confirm, servers are online but no updates so far. I am with the CH version.
When I flushed the Japanese docomo version(M Z-01K) ROM with microSD card in the Chinese version (6G / 128G), I could not use the mobile network, it was displayed that the model was different, and the Chinese version ROM could not be flushed.
Is there any way?
I used google translation.
ugambow said:
When I flushed the Japanese docomo version(M Z-01K) ROM with microSD card in the Chinese version (6G / 128G), I could not use the mobile network, it was displayed that the model was different, and the Chinese version ROM could not be flushed.
Is there any way?
I used google translation.
Click to expand...
Click to collapse
Dear,
which tool you used to flash it?
Regards,