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!
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Help please
Sent from my HTC One using Tapatalk
What happens on stock Sense firmware? If you are S-OFF, flash Dev edition RUU and test.
lettuceman44 said:
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Click to expand...
Click to collapse
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
LibertyMarine said:
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
Click to expand...
Click to collapse
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
i know how you feel
lettuceman44 said:
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
Click to expand...
Click to collapse
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
robbie09 said:
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
Click to expand...
Click to collapse
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
lettuceman44 said:
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
Click to expand...
Click to collapse
Run the full RUU if available.
What do you mean by that? I converted my phone from GPE back to stock using the AT&T ruu.
Sent from my HTC One using Tapatalk
I really need to fix this issue, it's becoming a liability
I don't know what else to do
Sent from my HTC One using Tapatalk
Bump again.
Sent from my HTC One using Tapatalk
Still looking through the internet for help, still found none.
similar issue
I'm on ViperOne 4.4.2 with similar issues. Only my router is a meter away from me, so the connection is excellent. Wifi on phone keeps disconnecting, but what is interesting, it does so like it's scheduled to do so. For an example - it'll work fine for an hour, more or less, & then it'll start to play games - disconnect, reconnect, scan for networks & show nothing, or try to connect & fail, or even get stuck at 'turning on'. Every problem that I have with my wifi can be temporarily 'fixed' with a reboot, then wifi will work fine for some time & start to disconnect again. HELP?
BTW this started after 4.4.2 update. I've downgraded back to 4.2.2, to 4.3 & now I'm back on 4.4.2, no changes. Did this update **** something up in my phone's hardware or what?
http://android-revolution-hd.blogspot.com.es/2014/02/how-to-fix-wi-fi-htc-one.html
I have a similar problem to what was initially discussed in this thread. Company wifi has multiple routers throughout the building/department - when I first connect to the system everything works great, but after moving to a different room and connecting to a different router (same network/wifi) the internet connection is lost. I stay connected to wifi, with strong signal, but don't have any data connection. In order to get internet back I have to turn the wifi off and back on - everything works fine until I walk into a different room and connect to a different router.
I'm on an HTC One Google Edition - don't remember having this problem before rooting the One from Sense to GE, but I wasn't streaming radio broadcasts of baseball games over the internet until a week ago, which was when this became a real annoyance.
As the title says, I bought a preowned C6606 and immediately flashed 4.4.2 ( I came from a Nexus4 Google Play Edition)
Got everything the way I wanted and went outside to connect and set up BT in my '13 subie stock system. Everything appeared to work fine.
Took a drive later on and BT didnt connect, turned BT on and then off again on the phone and it connected. Started Pandora and the volume was super low. I did check higher quality audio, turned up all the volumes on the phone, to no avail.
So, I accpeted this as a fluke. Parked, got out and later returned and BT wouldnt connect at all this time. Unpaired and reset up BT. Worked fine, left car, later came back and wouldnt pair again........(BTW none of the above gave me the loud volume my N4 produced, it just gave me mediocre levels)
After reading, I see others have had issues with 4.3....I was going to flash back to that, but if there is no fix...then.....
Please. Any and all ideas are greatly appreciated. I live on Pandora in the car, and cannot listen to FM radio for the life of me
Thank you.
Jasonator said:
As the title says, I bought a preowned C6606 and immediately flashed 4.4.2 ( I came from a Nexus4 Google Play Edition)
Got everything the way I wanted and went outside to connect and set up BT in my '13 subie stock system. Everything appeared to work fine.
Took a drive later on and BT didnt connect, turned BT on and then off again on the phone and it connected. Started Pandora and the volume was super low. I did check higher quality audio, turned up all the volumes on the phone, to no avail.
So, I accpeted this as a fluke. Parked, got out and later returned and BT wouldnt connect at all this time. Unpaired and reset up BT. Worked fine, left car, later came back and wouldnt pair again........(BTW none of the above gave me the loud volume my N4 produced, it just gave me mediocre levels)
After reading, I see others have had issues with 4.3....I was going to flash back to that, but if there is no fix...then.....
Please. Any and all ideas are greatly appreciated. I live on Pandora in the car, and cannot listen to FM radio for the life of me
Thank you.
Click to expand...
Click to collapse
Just for clarity sake, did you flash C6616 rom on C6606?
Correct. I flashed stock android 4.4.2 for a C6616 onto my US. T-mobile C6606...... I am not Rooted, nor is the bootloader unlocked. I flashed it 2 times using flashtool....the first time I didn't wipe my data and it was very slow/laggy....after doing it the 2nd time......perfection. Everything else works beautifully. I had 30% battery still by the end of the day. WiFi has 0 issues. I have full LTE and got 50 some odd mbps on speed test. It's just the darned bluetooth in the car. It won't consistently connect and that's a big deal to me.
Thanks.
Jasonator said:
Correct. I flashed stock android 4.4.2 for a C6616 onto my US. T-mobile C6606...... I am not Rooted, nor is the bootloader unlocked. I flashed it 2 times using flashtool....the first time I didn't wipe my data and it was very slow/laggy....after doing it the 2nd time......perfection. Everything else works beautifully. I had 30% battery still by the end of the day. WiFi has 0 issues. I have full LTE and got 50 some odd mbps on speed test. It's just the darned bluetooth in the car. It won't consistently connect and that's a big deal to me.
Thanks.
Click to expand...
Click to collapse
Try flashing your model specific firmware from here and see
That is exactly where I got it from....at the bottom of that article it reads
About the Torrents files:
Also, I would like to notify you that the download link to the torrent is not from me and is provided by Flashtool.net . I have seen the issue with C6606, when you download the file it says it is for C6616. I don’t know if it is really for C6616 or C6606, but as to my knowledge there is not much of difference. I would like to ask you readers from T-mobile from US to make a ftf file for C6606 and upload it to some website and provide the link to me in Comment box. So that it will be useful for others users also. Is there anyone who could help me?
All of that said, what would really help, and I have searched, is a Google Play Edition Firmware for 4.4.2
I dont want to root or unlock the bootloader, so I am not looking for a custom ROM, but the official one that I can flash using Flashtool. If yu can point me int he right direction for that, then I would be a very happy person!
Jasonator said:
That is exactly where I got it from....at the bottom of that article it reads
About the Torrents files:
Also, I would like to notify you that the download link to the torrent is not from me and is provided by Flashtool.net . I have seen the issue with C6606, when you download the file it says it is for C6616. I don’t know if it is really for C6616 or C6606, but as to my knowledge there is not much of difference. I would like to ask you readers from T-mobile from US to make a ftf file for C6606 and upload it to some website and provide the link to me in Comment box. So that it will be useful for others users also. Is there anyone who could help me?
All of that said, what would really help, and I have searched, is a Google Play Edition Firmware for 4.4.2
I dont want to root or unlock the bootloader, so I am not looking for a custom ROM, but the official one that I can flash using Flashtool. If yu can point me int he right direction for that, then I would be a very happy person!
Click to expand...
Click to collapse
the stock firmware for c6606 is still jellybean 4.2.2
I know this....
mymeatb18 said:
the stock firmware for c6606 is still jellybean 4.2.2
Click to expand...
Click to collapse
I am not sure I am being clear..............
I have C6606 Tmobile U.S. Variant.
I flashed Stock ROM for 4.4.2 made for a C6616 Canadian Version. Using Flashtool......
EVERYTHING works perfectly....LTE WIFI Battery etc......
EXCEPT....My bluetooth wont connect automatically in my car.
Right I did the same thing to my wifes phone, c6606 on tmobile. We don't have Bluetooth in our cars so couldn't comment on that.
If something is not working properly its inevitable since you are modifying the phone. There is nothing that u can do but deal with it. It could also be a compatibility issue as well. Some Bluetooth devices are more compatible to certain devices than others.
Sent from my GT-P3110 using Tapatalk
I went the other way around, I have a C661 and flashed a C6603, which I understand is just another variant. Everything works perfect for me. Here's the link for it; http://www.mediafire.com/download/an6lccyaa4lw96i/Stock_Rooted_Deodexed_4.4.2_XZ.zip
It is a pre-rooted if you are interested on that, and I do suffer from the google play services batter drain, I'm waiting on an update.
Jasonator said:
I am not sure I am being clear..............
I have C6606 Tmobile U.S. Variant.
I flashed Stock ROM for 4.4.2 made for a C6616 Canadian Version. Using Flashtool......
EVERYTHING works perfectly....LTE WIFI Battery etc......
EXCEPT....My bluetooth wont connect automatically in my car.
Click to expand...
Click to collapse
I had the same problem but I flashed a generic 4.4.2 C6603 from the UK. It was driving me crazy. Now I have issues where it will connect to my car but the audio won't trasnfer. It dosen't happen often. I didn't have the issue when I tried the generic 4.4.2 C6603 journalism software. Everything worked perfect then and my connections to the network for normal data and tethering are more responsive than the just released 4.3 T-Mobile software. Now that a root method has been found for KitKat I'll be going back to the jurnalism software. If you are willing to play with the software versions you might find one that works fine.
Maybe it has something to do with the audio software of the car and not the phone itself? Just a thought.