Anyone having problems with bluetooth on this phone? I have the Motorola H17 and it's next to useless with this phone. Sometimes it works, sometimes it doesn't. Sometimes you can hang up with the headset, sometimes you can't. etc, etc.
BTW the headsets work fine with a Vivid and an Inspire...
Thanks!
Im not having any problems with my blueant Q2
Sent from my blazing fast skyrocket
No issues here. Jaybird bt stereo headset
Actually these are quite amazing.
It is not uncommon to run into issues thou from device to device
Sent from my SAMSUNG-SGH-I727 using XDA App
Thanks for the replies!!
Are you guys using any form of voice command? What I've since found is bluetooth works fine until I initiate voice command (Cyberon) with the H17. After that (Next call) it gets all wonky. As long as I don't initiate voice command, everything is great. Maybe that's part of why it doesn't come with a voice dialing program?
Im using voice to go that came with the ogsgs2
Sent from my blazing fast skyrocket
Thanks David!
So either the Skyrocket doesn't like the H17, or I have a bad one. I'll try a blue ant Q2 and see how that goes.
I'm having bluetooth issues, it won't turn on. It just says turning on then never turns on. when it does turn on it dosen't connect to my motorola H720.
Interesting. Maybe there's an issue with some of these phones. My bluetooth turns on, but when it goes wonky it refuses to connect to any of my H17s. Coincidence that your headset is a Motorola too?
I restarted the phone and now bluetooth turns on OK and connects to my H720. I can answer calls but can't make calls with it. I had GS2 before and could bring up voice command with it.
There is no built in Voice Command with the Skyrocket. You have to add it yourself...
My Jawbone Era gives me some issues here and there but it could be the unit. Going to try my plantronics backbeats later though.
I had several issues noted in previous posts - finally got to the right section for Bluetooth settings and noted that the configured settings were not checked visible and once I enabled visible the setting needed to be changed from temp (1min if I recall) to never (for reverting back to invisible/non-discoverable). I'm using melvins stock rom - once changed this morning no more prob (though I am wondering about battery life). Fyi ymmv
Sent from my SAMSUNG-SGH-I727 using xda premium
As it turns out, it is a compatibility issue with my Motorola H17s. (NOT the newer text version, that I've never tried.) My Motorola HX1 worked fine. However, Cyberon Voice speed Dial still doesn't work well on this phone.
I'm also having the same issue. The bluetooth stops working after awhile.
You go and turn it on and it just says turning on and never does.
Also in my car it conencts for a bit then disconnects and then the bluetooth won't work intill you reboot the phone and even then it just repeats.
brand new phone.
Nakel said:
As it turns out, it is a compatibility issue with my Motorola H17s. (NOT the newer text version, that I've never tried.) My Motorola HX1 worked fine. However, Cyberon Voice speed Dial still doesn't work well on this phone.
Click to expand...
Click to collapse
Are you using stock touch wiz launcher ?
I had issues with voice2go not working properly with ADW launcher on this phone.
Totally stock. If I keep it I'll have to look at voice2go... My issue now is that the display is so dim when viewing black text on a white background. Weird, because colors are so bright and vivid. But reading an ebook it's really quite poor.
Nakel said:
Totally stock. If I keep it I'll have to look at voice2go... My issue now is that the display is so dim when viewing black text on a white background. Weird, because colors are so bright and vivid. But reading an ebook it's really quite poor.
Click to expand...
Click to collapse
Try turning off the auto brightness setting.
Thanks, but that was the first thing I did...
I had a problem with my bluetooth. When I used the toggle from the pull down, it wouldn't work. When I rebooted and turned bluetooth on and off through the settings menus, it works fine. Weird.
I had the same issue, and rebooting worked but seems like its back. When I turn it on is says turning on and never does. Anyone got a solution or should I return it for another phone?
Related
Hi, I have looked through all the forums for my issue and have yet to find a solution. In the "incall screen tweak" I have the setting activated to have the speakerphone turn on when the phone is face down I have soft reset and done many hard resets and cannot seem to get this to work. I would love to be able to have this option available. Any help would be great!
Thanks a lot,
Mikel
You need to post to that thread.
I could never get it to work either.
No tweaks in that prog worked for me.
does the rest of the features of InCall work properly? maybe you need to ignore the first sleep thing
Works fine on my AT&T Fuze with stock ROM.
it hasnt worked for me either but the rest of the features work like auto on/off screen when its by my ear and all
Make sure you calibrate your G-Sensor then try it
dalavar said:
Make sure you calibrate your G-Sensor then try it
Click to expand...
Click to collapse
has it worked for you???
Speakerphone on facedown has worked for me with TICST ever since I installed it. Did you mess with the HTC Mute when face down settings? Not sure if that would affect it.
yea, i have my fuze set to mute when face down also but thats for incoming calls so i cant really see how that would change that too?
Not sure which In Call app you are using. I have used this one on several TP's and all work as advertised.
http://forum.xda-developers.com/showthread.php?t=488991
Not sure which In Call app you are using. I have used this one on several TP's and all work as advertised.
http://forum.xda-developers.com/showthread.php?t=488991
Just got my new G2X this morning. I came from a N1.
I generally like the phone and got it to address a couple of problems I had with the N1 (handset speaker went out and I only could talk via speaker or BT, sticky buttons, and continuous switching between EDGE/3G).
I can overlook the display bleed, the fact that I HATE where the power button is located, trackball, LED notifications (boy, will I miss those) and can (I think) tolerate the lack of early android updates.
There are couple of other things that REALLY bug me, though, and was wondering if anyone else was experiencing it and if there were any solutions. (Yeah, I searched the 'net today but haven't come up with any thing elegant). I don't have these problems on the N1 so could probably tolerate it and return the G2X until more appropriate hardware was out. (Maybe sensation? Although I don't like large screens on my phone)
1. Bluetooth lag. There is a significant (sometimes 1-2 seconds) lag between the time my phone generates sounds and when my BT headset picks them up (Jawbone Icon).
2. BT/Handset simultaneous sounds. I liked the fact that when my BT headset was connected, the handset speaker would mute and all sounds would only come through the headset. This does not happen that way with the G2X - is there a way to change it?
3. So I have two places for storage and by default, most of the apps point to the internal one and can't be changed to point to the external (I was able to point the camera storage to external at least, whew!). Any known workaround?
4. Task killer can't kill certain apps. I get a message saying that 2.2 didn't allow 3rd party apps to cancel processes. Never noticed this on the N1.
5. Car Home - I'm sure a lot of people find this useful, but I don't. Is there any way to supress this from coming up? Sometimes I get it when I connect my BT headset. At other times it doesn't show up until I get a call.
I really want to like this phone, but aside from 4G, it seems like it isn't much more than a minor improvement over my N1...
I can't help you on 1-3, but...
4) Task killers on android do more harm than good.*
5) Root the phone. It's REALLY simple. Download some drivers for your PC, download the program, connect your phone, run it, boom, rooted. Download Titanium Backup, find Car Home, freeze it.
more info on rooting
I myself coming from a N1 I keep looking at the N1 wanting to reach for it and throw my SIM back in and cry holding it. Wish I could put new guts in it and make it more update.
1. the track ball my thumb keeps reaching for and its not there
2. Two storage places I dont like either
3. The bleed isn't bad on mine but Im going to wait a week and take it back and try another g2x out before my buyer's remorse period is up.
4. I'm very surprised at you coming from a N1 that you use task killers very surprised and I'm gonna keep my eye on your.
cliffy15 said:
1. Bluetooth lag. There is a significant (sometimes 1-2 seconds) lag between the time my phone generates sounds and when my BT headset picks them up (Jawbone Icon).
Click to expand...
Click to collapse
I have a BlueAnt Q2 and have no issues with Bluetooth. Phone to headset and headset to phone are almost instantaneous.
2. BT/Handset simultaneous sounds. I liked the fact that when my BT headset was connected, the handset speaker would mute and all sounds would only come through the headset. This does not happen that way with the G2X - is there a way to change it?
Click to expand...
Click to collapse
My G2 used to work that way too. The G2X and my headset work like yours. It drives me crazy but I don't think there's a fix. Oddly, in my car, it play signals through the car's speakers when I wish it wouldn't. So that seems to indicate the connected device has something to do with it.
5. Car Home - I'm sure a lot of people find this useful, but I don't. Is there any way to supress this from coming up? Sometimes I get it when I connect my BT headset. At other times it doesn't show up until I get a call.
Click to expand...
Click to collapse
You could disable it under settings with HTC phones. Settings on the G2X take you to Android settings. I kill the process when I reboot the phone.
Thanks for the info!
lance713: yeah, assuming this phone makes it past the return date, I'm going to have to root it. I was never really was into custom roms, but I think I may start soon.
lance713/wondercoolguy: btw, I don't use task killers for much ... but coverage is spotty here (Hawaii) and I kill things when they get interrupted mid-task because they wait and "search" for awhile, killing my battery. I also kill gallery and messages when they have the occasional hang.
Guess I'll have to get used to no trackball/pad. My only other consideration was the Sensation (I really don't want most of the Sense UI) and that doesn't have one, either.
Rooting and flashing with different rom, will not fixed the screen bleeding problem or charging problem, that causes the phone to reboot. Those are hardware flaws
I can help with one of your issues the LED Notifications. Check out NoLED Settings in the Android Market by a fellow XDA developer member. It works great and highly customizable.
Came from an N1 myself.
Solution: Flash CM7
You'll feel right at home!
led notification
try lg2/black notifications from the market place.
Hello guys...
I am using with satisfaction Noled app and I gave a try to the audio alert yesterday, an option I never used. It works, in fact when I receive an email or a phone call, a digital voice alerts me (about the incoming call telling the name of the caller for instance). Now I want to turn off the option but it does not work: even if I uninstall Noled, the alert is always present and it is a little bit annoying.
Do you know if there is a trick or a system option I can fix inside the phone? For sure it is a bug of the app which changed something somewhere I don't know...
thx to all
That's not Noled - that sounds like driving mode in the voice input settings. (in text to speech)
You are partially right. Noled entered in conflict with my car mode because I did not noticed that it turned on alone (don't ask me how, I never used this option). Plus they started to play each other when getting a notification of SMS out call...so everything was messed up...I uninstalled noled, reinstalled it and turned off car mode. Now it seems to work. Maybe it happened when I changed my custom ROM...many times happens something with Android when you flash even if you follow exactly the proper procedures...
Thx anyway, mate.
Sent from my GT-N7000 using Tapatalk
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
So I converted to the Global Rom. So far so great. Much better than being stuck on TMO. We get Google dialer instead of the one plus dialer which I like better but really doesn't fit with the skin OP has. Anyways when I play a voice mail and put my phone up to my face the screen goes off but the message stops playing. Am I missing a setting somewhere?
Is your face hitting some button before the screen actually turns off?
I am using the global ROM that came installed on my phone but I am on AT&T and I do not have this problem. I cannot think of any setting that would be related to this.
jaseman said:
Is your face hitting some button before the screen actually turns off?
I am using the global ROM that came installed on my phone but I am on AT&T and I do not have this problem. I cannot think of any setting that would be related to this.
Click to expand...
Click to collapse
No, I just get it close enough to hear and watch the screen. As soon as the screen goes off the sound stops. Otherwise the Rom is flawless.
Smallsmx3 said:
No, I just get it close enough to hear and watch the screen. As soon as the screen goes off the sound stops. Otherwise the Rom is flawless.
Click to expand...
Click to collapse
I have the same issue. Converted from TMO to global.
Same thing happens to me. I just play VMs via speakerphone (the button to the left of play/pause) instead.
visual voicemail doesn't work on global. I use the standalone tmo vvm app from the playstore.