Related
Well i've been doing a bunch of stuff to my phone to get things humming along, but the one thing that hasn't worked at all is Bluetooth Voice Command Dialer.
I've tried the native bluetooth voice command dialer, and the following apps below:
Vlingo Virtual Assistant
Choice Dialer
Bow Tie
The bluetooth handsfree that i am using is the Samsung WEP200 and I own 3 of them and all 3 of them don't work.
When i mean don't work, i hit the command button and it would prompt with the "Bluetooth Voice Dialler" prompt and I try to speak but nothing is happening. The audio routes to the bluetooth, but i suspect the mic isn't.
Bluetooth calls and call last caller works, but that is it as it is basic bluetooth capabilities.
So at the moment I am stumped and wondering if anyone out there got it to work and what your handsfree is.
I have noticed the same problem. Is your phone a Rogers Captivate using Kies to update or it's an ATT Captivate using Odin to flash rom?
I have i897 AT&T and Odin flash and I notice this issue. When I was on the Rogers ROM 2.1, my bluetooth wouldn't pair. Now on 2.2, I can pair and call using BT, but voice dialler doesn't seem to have the mic on...
I tried bluetooth mic tester app and it didn't record anything via bluetooth.
I'm using the Rogers Froyo over Kies. It took me forever to install it since i had to repair my nv_data.bin.
This problem plagued me from Cognition 2.3b8 as well. To date I haven't had a Froyo install that worked with Bluetooth Voice Command Dialer.
If anyone out there that had the bluetooth voice command dialer to work on their captivate I'm all ears. I am thinking maybe it is because my Samsung WEP-200 is too old?
BTW, I'm using Jawbone Prime.
I also tried other apps vlingo and all those none seem to be able to capture mic from BT when voice dialing. I can have voice conversations using my BT, but no voice dial.
Well I think it might be a general issue with Froyo and Samsung Captivate in general, regardless of Froyo custom builds. If someone else has it working on a specific ROM i am all ears.
Later tomorrow I will contact Samsung Support and ask them about this, because this is really stupid.
Just wonderful. Well, I hope that's not your true official Froyo. If so, Samsung is just killing me. I've been running I9000 Froyo ROMs because the first nor second Cappy Froyo leaks don't have this functionality. This is the one function I want Froyo for more than anything else. I hate to say this, but my iPhone 3GS worked perfectly (you know what that means: I could voice dial over Bluetooth, but the call wouldn't stay connected!!). I just hope this is not an indication that Froyo for Cappy - if it ever is released - will not have this functionality. It just keeps getting better with these guys.
Any updates from Samsung?
well i called samsung social hub support. Their official answer it isn't even a feature of the phone. Also they are aware that the bluetooth voice command dialer is broken on the phone and isn't supported.
I've requested they have it as a potential feature in the future as it is bylaw in some provinces and states that people use bluetooth voice command dialer.
Well this only puts one more nail in for samsung...
Also this could be related because of their stupid bluetooth stack, but there isn't much more I can find on this.
I hope this information is helpful to those looking around.
I've had it successful on two or three different ROMS. But I can't remember which for sure.
I think it worked on one of the Perception ROMS; It doesn't come on Assonance ROMS.
Something that I have done on ROMS that don't come with the Voice Dialer, I use Blue Tooth LAunche. I'm using it now on Assonance 5.2 You can configure it for what you want it to connect to.
It may take a bit of experimentation on how to configure it. When you go into the list of apps to configure, it lists all the various activities of the apps, and you need to select the right one. For example, to bring up Google Voice Search, I have it using com.google.androd.voicesearch.recognitionactivity.
Google Voice Dial
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
I just downloaded the voice dialer.
I actually have it at home, but not sure if same version. I tried to install it on one of the ROMS (I think Assonance) and was unsuccessful. I probably tried using Root Explorer. I don't think I tried just dropping it in the Apps folder. But not sure.
I'm installing Cognition 3 as I write this. We'll see how things go on that.
baxster said:
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
Click to expand...
Click to collapse
I'd try this but it wont let me install over system apps lol. Anyone know how to do it? BT dialing doesn't work on my rogers 2.2 either.
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
kintaro said:
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
Click to expand...
Click to collapse
I am hopping that when the AT&T update happens we may be able to get the files we need to get the Rogers version working...
I also tried with the VoiceDialer.apk provided in this thread and no luck. Also tried the 09SEP-VoiceDialer.apk and no luck.
I do agree that there is some system libraries that need to be updated, since there are claims that 09SEP-VoiceDialer.apk worked with others.
Since we can have conversations with our bluetooth, it's not an hardware issue. It's something with software.
Same issue here with rogers captivate.. I deleted the dialer to see what happens, and the button on my headset now did nothing, but if i held it in, it would call the last number dialed. I flashed it back to factory and got my app back, and the button brought up the bluetooth dialer again, but it doesnt work. And now pressing and holding calls voice mail again.
I wish they had a settings section to assign the button presses to applications without 3rd party apps.
I hate how rogers and samsung are washing their hands of the issue. they wont take the phone back. Its illegal here to use my phone while driving. I got the phone on the 11th. I am still waiting for the accessories I bought to arrive, everything from a desk dock to car dock, spare battery.. all OEM.
If they don't get this right, I wont be buying more products from them.
I have more faith in you guys finding a solution than them.
Same problem and I think NONE of the Bluetooth mic works on Voice Command on Froyo roms for my Captive. I've tried the AT&T leaked Rom and also the Cognition 3.04, NONE of them support Bluetooth voice dialing but no problem for normal phone conversation. Now that is EXTREMELY ANNOYING!
iPhone 5 for sure! No more Android suckers!
Just wanted to pipe in that I'm in the same boat and pretty mad at sumsung/rogers for not including bluetooth voice dialing! Is this 2011 or what?
I just bought some very expensive bluetooth headsets for my motorcycle and now find out that my brand new "state of the art" phone can't voice dial with them?
Hopefully someone figures this out. I'm counting on someone being way smarter than I am with this stuff
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Miami_Son said:
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Click to expand...
Click to collapse
In all fairness, this is a samsung issue. Not Android.
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 recently took the plunge and updated to Cloudyfa's CloudyG3 2.0+ Rom and it is super awesome. There is a HUGE General Discussion thread here:
http://forum.xda-developers.com/showthread.php?p=56644031
Here is the main Rom thread:
http://forum.xda-developers.com/showthread.php?t=2783192
It is for all variants but it is a port of the GSM G3 rom. So some things aren't 100% on our VS980 roms. Just to be certain, everything is working for me but it takes a few tweaks, hence the point of this thread.
Here are the main issues off the top of my head:
Cellular doesn't work out of the box
You have to manually change it to LTE/CDMA. It took a few times to get this to work. I also use an app from the Play Store called "TellInfo" which lets you select "LTE/CDMA/EvDo/GSM/WCDMA" (which seems to work best for me). You also have to go into Settings > Tethering & Networks > Mobile Networks and select "Data Enabled" and "Data Roaming". The Network mode that seems to work best is "Global" mode.
I would advise that you check with your data plans to make sure you aren't being charged a crazy amount of money to roam on other networks. At this point (I travel), I haven't racked up any additional charges.
MMS doesn't work with the stock Messaging App
This requires downloading Textra or Hangouts for SMS/MMS handling. I like Textra.
Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options
Other random facts
The keyboard no longer has arrow keys in the nav bar when typing. I've read the G3 rom keyboard is supposed to let you swipe the spacebar for left/right movement... but it doesn't work nor do I see any options.
WiFi File Sharing is gone from the G2. The G3 took this feature out, which is really really sad. A good alternative is "Samba Filesharing". Same thing except can't be launched from the Notification Shade
Otherwise, the rom is beautiful and pretty. The Xposed G3 Tweaksbox has tons of options for some really neat features. Everything else works the same/better then stock G2 software. I don't know if I could go back to the stock G2 rom after using this for a few weeks. Outside of the small issues listed above (SMS/MMS being the only semi-big one) it works and looks so good that it is a keeper.
Any additional tips and tricks to making the CloudyG3 rom work better on our VS980 Verizon LG G2s, please share!
For a Lollipop Theme using G3 Tweaksbox:
Theme: http://forum.xda-developers.com/devdb/project/?id=5684#downloads
Notification Icons: http://forum.xda-developers.com/showthread.php?t=2717736
@player911
Although I appreciate the time you spent working this up for people, its in the wrong section.
This really should be in the Verizon specific General section (maybe q&a?)
Just to add on a bit. Any time I flash one of his ports, I just change the build prop.
I use ROM toolbox pro, light would work, but the app you really need (that's built into it) is root explorer.
I change the tele device to 10, country to US (make sure its caps) and carrier to vzw, and I never have an issue with LTE sticking or anything of the sort.
Obviously you would change the country if you don't live in the US.
I haven't done any of these changes and if seems fine...
Sent from my VS980 4G using Tapatalk
Thats weird I've been running this rom on my vs980 for a few weeks now. Everything worked perfect for me without having to mess with any settings at all. Also messaging worked without a hitch. Only thing i noticed while driving was the signal would say roaming sometimes. A reboot would correct this issue. Think it has something to do with the 3g to 4g hand off.
Jeff Zaugg said:
Thats weird I've been running this rom on my vs980 for a few weeks now. Everything worked perfect for me without having to mess with any settings at all. Also messaging worked without a hitch. Only thing i noticed while driving was the signal would say roaming sometimes. A reboot would correct this issue. Think it has something to do with the 3g to 4g hand off.
Click to expand...
Click to collapse
If it is roaming that means you're in a 3g area
I tried this for awhile on more than one occasion and every time, my sms would eventually take hours or days to receive. It was maddening. Did not matter what app I used, fixed apn settings, tried everything. It would work for a day or two then messaging totally fell apart.
Sent from my VS980 4G using Tapatalk
Lawlrus said:
If it is roaming that means you're in a 3g area
Click to expand...
Click to collapse
Are you actually roaming though? Or does it just say so?
mulhiny said:
Are you actually roaming though? Or does it just say so?
Click to expand...
Click to collapse
Its cosmetic.
The reason it does it, is because the ROMs he builds are based off of international builds. So they don't cater to vs/ls980 as they use cdma
Edit: Same reason why the stock messengers won't send mms
---------- Post added at 07:14 PM ---------- Previous post was at 07:05 PM ----------
Also, I just flashed the new cloudyg3 2.1, (I think?) and it looks like all the normal changes I make to the build prop are already done.
Country and tele device number.
I am having MTP issue. It refuses to go into MTP mode.
Does anyone know how to fix this?
I put build.prop fix in and it did not make any difference.
Otherwise, it appear to be pretty good. But battery drain seem a bit higher than stock.
Lawlrus said:
Its cosmetic.
Click to expand...
Click to collapse
Great to hear..I'll note that the G3 tweaksbox has an option to kill the roaming icon and then you can use the Verizon icons..perfect.
Since flashing this last night I've had no troubles. GPS, LTE, MTP, everything is working...
"Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options"
anyone solve this? Same problem for me with any custom rom.
Does anyone know how to get the automatic login working for the my verizon mobile app? I tried inatalling the verizon login from the play store and that didnt work, so I tried restoring a backup of the app from stock and that didnt work. I converted both to system apps and that didnt work either! ? Anyone please help its important that i get this working.
mrdunn said:
"Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options"
anyone solve this? Same problem for me with any custom rom.
Click to expand...
Click to collapse
I gave up on VVM a while ago. Had to call Verizon and have them deactivate it. Now I just get a regular notification when I have a VM.
The only good alternative to actual VVM I've found is Google voice.
How does CloudyG3 perform compared to an AOSP rom on our G2? I'm running AICP right now and love the stock feel, but have some issues like GPS. Is the G3 UI that much better than AOSP?
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Lawlrus said:
@player911
Although I appreciate the time you spent working this up for people, its in the wrong section.
This really should be in the Verizon specific General section (maybe q&a?)
Click to expand...
Click to collapse
Well my intention was to put it in the VS980 General Section. Im not sure if it got moved or where it currently is, as I am on mobile.
I am running 2.0 and heard 2.1 has the phone force close that prevents usage. It appears some people experience this while others dont. Could depend on previous rom.
Im in no rush to update. I'll check out the build prop changes. I have root explorer. Although I thought that this was the purpose of the aroma installer.
I have selected the Verizon icon set in G3 Tweaksbox but still see the occasional Roaming icon. Not a big deal. Still works fine.
arctic84 said:
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Click to expand...
Click to collapse
I had the same exact issue so I was forced to downgrade to 2.0, and the dev didn't really seem to know how to fix it, although 2.0 is truly great on the VS980. Would be great to be able to run 2.1, although I was able to get it to work as soon as I changed it from global mode to any other mode that started to crash.
arctic84 said:
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Click to expand...
Click to collapse
2.1 worked fine for me no issue for two days. You either didn't clean flash, or did something wrong.
Sent from my Vs980 running Validus 4.4.4
Lawlrus said:
2.1 worked fine for me no issue for two days. You either didn't clean flash, or did something wrong.
Sent from my Vs980 running Validus 4.4.4
Click to expand...
Click to collapse
KK baseband - check
full wipe - check
2.1 rom - check
What am i doing wrong?
arctic84 said:
KK baseband - check
full wipe - check
2.1 rom - check
What am i doing wrong?
Click to expand...
Click to collapse
You tell me. It works fine.
You restoring system apps and or data?
Using xposed modules?
Flashing a different kernel?
Removing system apps?
Flashing any mods such as status bar with the ROM?
You check md5?
Using twrp 2.8.1?
Sent from my Vs980 running Validus 4.4.4
Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.
Nurmi_CEO said:
Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.
Click to expand...
Click to collapse
Okay, I just thought I had this problem... here the same, after the latest update to 5.1.1.
I'm try with 2 bluetooth headsets (Plantronics - Jabra) and a full factory reset but no notifications for text messages (sms, chat, whatsapp ect ect ect)
Italian Sony Xperia Z3C (Vodafone) Android 5.1.1 - 23.4.A.1.200
I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!
Nurmi_CEO said:
I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!
Click to expand...
Click to collapse
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232
qmaxmobile said:
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232
Click to expand...
Click to collapse
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.
Nurmi_CEO said:
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.
Click to expand...
Click to collapse
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't
qmaxmobile said:
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't
Click to expand...
Click to collapse
Well I decided to flash a 4.4.4 ROM because the battery life is supposedly better (althought my 5.1.1 had great battery life, almost 7 hr SOT). However same thing, no notification through bluetooth.
qmaxmobile, what rom were you running on 5.0.2 to have notifications play through through bluetooth? I only found one 5.0.2 rom and I couldn't get it to boot, and seems like others in the thread had the same problem.
I really need bluetooth notifications. Seems like a simple app would do the trick, but haven't found much except a thread on a forum saying Xperia phones don't support it.
So I posted on the Sony Xperia forum, and a sony rep confirmed that Sony firmware does not support this feature (why????). I tried high and low to find an app in the play store to get it to work, but no dice.
Supposedly the rep also said that if you get a Sony bluetooth headset you can get the sony app to control that feature. I'm not so sure....
If anyone can confirm a sony bluetooth headset will in fact work with stock xperia firmware, please post!
The only option I was able to think of was to unlock the bootloader and flash a custom rom. I just did that and it worked. My DRM keys are backed up in case I decide to relock. So now I'm running Ressurrection Remix rom. It's a shame, as I didn't mind the Sony interface.
Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!
Nurmi_CEO said:
Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!
Click to expand...
Click to collapse
Well, I don't know about you, but notifications go out when using Bluetooth for me on the latest Sony stock room.
You may try the apps SoundAbout, or Mono Bluetooth Router, though.
That's so weird. No idea how it works for you. I found a few threads on other forums complaining about the same thing. I even posted on the Sony forum and support said I need a Sony app and a Sony headset because this "feature" isn't supported.
I did monkey with SoundAbout, no luck. There are so many options, and I didn't see a specific one for this feature.
Phone will connect but when making a call it acts as if it hung up, doesn't ring, but then eventually connects to the call. Also, it seems that it freezes. Didn't have this issue on 5.1.1
I have a few questions and thoughts about this.
1. I assume it is an issue with Honda's iMid. I've had issues with bluetooth and my phones since I got the civic.
2. If I buy an aftermarket headunit the problem should go away, right?
3. Is it possible for me to take the bluetooth files from 5.1.1 and put them into 6.0, and will this fix the issue?
4. Has anyone else had this issue. It's possible that a factory reset could fix it, but I'm doubting it.
Thanks.
Tried using 5.1.1 files and it breaks bluetooth. Any other ideas?
Seems that HD calling/4G Enhanced is what is causing this. There is a delay in the phone connecting to activate HD. When I deactivate HD it rings through my car speakers like normal. Turn it back on and there is a delay in the call. I doubt there is a fix, but I'm curious if this is happening to anyone with aftermarket headunits in their cars.
theycallmerayj said:
Seems that HD calling/4G Enhanced is what is causing this. There is a delay in the phone connecting to activate HD. When I deactivate HD it rings through my car speakers like normal. Turn it back on and there is a delay in the call. I doubt there is a fix, but I'm curious if this is happening to anyone with aftermarket headunits in their cars.
Click to expand...
Click to collapse
I don't have a car with a head unit, and I'm still on 5.1.1, but I have noticed long delays with HD Voice and WiFi calling on, and have had complaints about long delays for my phone to start ringing when people call me. I have turned off HD Voice for now to see if it helps me, and good luck to you!
Never ran into this on LP and yet have to on MM.
I use a Kinovo BTC450 kit in my GTI.
I have the exact same problem on my Mazda after updating to 6.0 (worked fine on the 3 previews). How do you disable HD calling?
shadowxm said:
I have the exact same problem on my Mazda after updating to 6.0 (worked fine on the 3 previews). How do you disable HD calling?
Click to expand...
Click to collapse
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
theycallmerayj said:
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
Click to expand...
Click to collapse
My BT is not working in my Pioneer head unit with 6.0. I don't have enhanced 4G LTE in my settings, so it may be an issue with the kernel
byrdcfmma said:
My BT is not working in my Pioneer head unit with 6.0. I don't have enhanced 4G LTE in my settings, so it may be an issue with the kernel
Click to expand...
Click to collapse
Are you having the same issue I'm having or just straight up doesn't work? I'm using the stock rooted kernel that I got from xda. I'm going to try hellscore to see if maybe that makes a difference.
theycallmerayj said:
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
Click to expand...
Click to collapse
Thanks but I don't see that option on Cellular Network Settings, so I guess the issue must be something else, or maybe I just can't turn that off
theycallmerayj said:
Are you having the same issue I'm having or just straight up doesn't work? I'm using the stock rooted kernel that I got from xda. I'm going to try hellscore to see if maybe that makes a difference.
Click to expand...
Click to collapse
It connects, but no sound. Not the same issue as you exactly. I also don't have the option of turning off the HD calling ii nn settings.
shadowxm said:
Thanks but I don't see that option on Cellular Network Settings, so I guess the issue must be something else, or maybe I just can't turn that off
Click to expand...
Click to collapse
http://www.droid-life.com/2015/03/1...e-and-data-now-works-on-nexus-6-with-verizon/
Read down through it. You may have to turn it on in the deeper phone settings.
"In order to enable the setting on your phone, head into the dialer and type in *#*#4636#*#*. When you hit that last *, your phone will jump into the hidden settings menu. Choose “Phone info” and then scroll down until you see an option for “TURN ON VOLTE PROVISIONED FLAG.” Tap that and then reboot your phone (I had to reboot twice for some reason to get it to work). "
theycallmerayj said:
Phone will connect but when making a call it acts as if it hung up, doesn't ring, but then eventually connects to the call. Also, it seems that it freezes. Didn't have this issue on 5.1.1
I have a few questions and thoughts about this.
1. I assume it is an issue with Honda's iMid. I've had issues with bluetooth and my phones since I got the civic.
2. If I buy an aftermarket headunit the problem should go away, right?
3. Is it possible for me to take the bluetooth files from 5.1.1 and put them into 6.0, and will this fix the issue?
4. Has anyone else had this issue. It's possible that a factory reset could fix it, but I'm doubting it.
Thanks.
Click to expand...
Click to collapse
This is the exact same issue I am having with 6.0 on my Acura. I did not have the issue on 5.1.1. The issue on 5.1.1 was constant connect/disconnect if WiFi was active.
artiemon said:
This is the exact same issue I am having with 6.0 on my Acura. I did not have the issue on 5.1.1. The issue on 5.1.1 was constant connect/disconnect if WiFi was active.
Click to expand...
Click to collapse
Out of curiosity, does your Acura have the imid? Apparently Honda doesn't update the old models to play nice with Android. I think the 2015+ has adjustments to make it work correctly.
theycallmerayj said:
Out of curiosity, does your Acura have the imid? Apparently Honda doesn't update the old models to play nice with Android. I think the 2015+ has adjustments to make it work correctly.
Click to expand...
Click to collapse
I am not familiar with imid. My Acura is a 2015 & I am using the factory phone interface.
artiemon said:
I am not familiar with imid. My Acura is a 2015 & I am using the factory phone interface.
Click to expand...
Click to collapse
Oh okay, its the software/interface for the audio of civics. I've had issues with it before with certain Android phones. I want to get a touch screen head unit, but not going to rush into it if it won't fix the issue anyway.
byrdcfmma said:
It connects, but no sound. Not the same issue as you exactly. I also don't have the option of turning off the HD calling ii nn settings.
Click to expand...
Click to collapse
Same here. It connects, but no sound, no option to "turn off HD". Phone is nexus 5, originally bought from google, on tmobile
network. Car is 2014 Honda CRV, factory unit. Never had any problem with this phone or any other phone with this car.
Very annoying.
Glad I found this thread. Since clean flashing from 5.1.1 to 6.0, I've had the same issues with my 2013 Cadillac ATS: when I make a call, the call goes through but there is no sound through Bluetooth. It seems like the person on the other end cannot hear me and I cannot hear them. Same problem receiving calls with Bluetooth connected. I have to manually change the output from Bluetooth to headset/speaker and then the call resumes fine...so there's definitely no problem with the call connecting.
I did notice that one issue has been FIXED: when I control my Bluetooth audio (play, pause, ff, rw), my screen no longer turns on. This was very annoying but certainly not as bad as the new bug!
On a side note, a week or two ago I began having significant battery drain from "Bluetooth Share" even when no devices were connected. I can no longer leave Bluetooth on all day like I used to. I made a post about it here:
http://forum.xda-developers.com/nexus-6/help/bluetooth-share-draining-battery-wipe-t3224863