Visual voicemail issues after converting from T-Mobile to Global - OnePlus 8T Questions & Answers

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.

Related

Bluetooth Issues?

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?

[Q] Odd classic voice dialer intermittently when using wired headset

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.

Accidentally hitting HOLD button during calls?

I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it

Screen call issue

Hi there,
I just got my Pixel 3 from BestBuy, opened it, restored some settings from an old phone and gave it a test. I'm pretty satisfied with almost everything, but it looks like the "Screen call" feature is missing. That one thing that Google was promoting a lot is not present.
Does any of you have this issue? When you go to Phone settings or when someone is calling, do you have the option for screen call there (I don't )
Thanks,
Andrei
salageanandrey said:
Hi there,
I just got my Pixel 3 from BestBuy, opened it, restored some settings from an old phone and gave it a test. I'm pretty satisfied with almost everything, but it looks like the "Screen call" feature is missing. That one thing that Google was promoting a lot is not present.
Does any of you have this issue? When you go to Phone settings or when someone is calling, do you have the option for screen call there (I don't )
Thanks,
Andrei
Click to expand...
Click to collapse
Yep, just tested it and works fine. There's a "Screen call" button on the screen that pops up for incoming calls. Works as advertised, although the transcription of what I said from the other end was garbled, so not perfect. I looked but don't see an option to turn it off.
samnada said:
Yep, just tested it and works fine. There's a "Screen call" button on the screen that pops up for incoming calls. Works as advertised, although the transcription of what I said from the other end was garbled, so not perfect. I looked but don't see an option to turn it off.
Click to expand...
Click to collapse
I've just found out that this is available only in the US. Sorry for not reading this before.
salageanandrey said:
I've just found out that this is available only in the US. Sorry for not reading this before.
Click to expand...
Click to collapse
Ah, ok, thanks for the update.
It's already saved me from a spam call. Might be one of my favorite features

Screen Lights Effects not working properly...

Hi, i am using the Chinese version of the Find X2 pro and I just can't seem to get the it to work for notifications.
It works just fine when I get calls, but it doesn't do anything when I receive messages from like WhatsApp or WeChat etc.
I have the "light effects for lock screen" option turned on but it still doesn't work Does anyone here know a fix?
Natsuhappy said:
Hi, i am using the Chinese version of the Find X2 pro and I just can't seem to get the it to work for notifications.
It works just fine when I get calls, but it doesn't do anything when I receive messages from like WhatsApp or WeChat etc.
I have the "light effects for lock screen" option turned on but it still doesn't work Does anyone here know a fix?
Click to expand...
Click to collapse
Same here. Never noticed this working on mine either now you mention it. China spec in UK also.
Doesn't work with global rom in UK either! I use True Edge from google play store, but even that is hit and miss (and it's not brilliant on the battery). Not sure why a company who doesn't include a notification LED doesn't do more for other methods of notifying.
No problems here in Holland
No chinees version
Johnti said:
No problems here in Holland
No chinees version
Click to expand...
Click to collapse
Same here. Works fine
Sent from my OPPO CPH2025 using XDA Labs
hunhool said:
Same here. Works fine
Sent from my OPPO CPH2025 using XDA Labs
Click to expand...
Click to collapse
Bizarre (seems to be the buzz word for this phone). I got mine from Netherlands, and running EU rom, but they don't work for me.
Anyone got these Lock Screen Notifications working?
I've got the settings and it works lighting up, but only once, then it just stops which sort of defeats the object ?
BlueMeany68 said:
Anyone got these Lock Screen Notifications working?
I've got the settings and it works lighting up, but only once, then it just stops which sort of defeats the object ?
Click to expand...
Click to collapse
It's only lighting up once or twice. Don't expect more. It's ok like that. If you want more then install from playstore. There a couple of apps which has similar settings for incoming messages calls, etc.
Sent from my OPPO CPH2025 using XDA Labs
Natsuhappy said:
Hi, i am using the Chinese version of the Find X2 pro and I just can't seem to get the it to work for notifications.
It works just fine when I get calls, but it doesn't do anything when I receive messages from like WhatsApp or WeChat etc.
I have the "light effects for lock screen" option turned on but it still doesn't work Does anyone here know a fix?
Click to expand...
Click to collapse
Can I ask you which update you have now , mine received update once only and may security until now
Yeah same issue here. Always On display is the only workaround I can think of.
With no LED they need a way to let you know of missed calls and text messages..
Can anyone recommend an alternative app?
Sage said:
Yeah same issue here. Always On display is the only workaround I can think of.
With no LED they need a way to let you know of missed calls and text messages..
Can anyone recommend an alternative app?
Click to expand...
Click to collapse
I've tried:
True Edge
Always on Edge
Always on AMOLED
Notify Edge
All are *huge* battery suckers
Currently using Notify Buddy by Xander Apps. Seems to be the best for battery useage and lights up a circle (which is an absolute PITA to position). I have it perpendicular to the camera punch on right of screen. Works for *most* apps but not all.
Don't agree with the comment about notification only lighting once or twice is useful. We have notification sounds for that!
Don't agree with the comment about notification only lighting once or twice is useful. We have notification sounds for that!
Click to expand...
Click to collapse
I think this is more if you are away from your phone or it's on silent. You want to be able to glance at your phone and know if there is something important pending. (like a missed call). At this point in time without Always on Display there is no way to do this.
Thanks for the app recommendation
I did try NotifyBuddy though didnt work for me.. No LED coming up.
i think always on display is the best option. at least it's a factory app designed to be run all the time.
For anyone not sure it's called "Screen off Clock" in the Oppo settings.
Sage said:
I did try NotifyBuddy though didnt work for me.. No LED coming up.
Click to expand...
Click to collapse
Took an age for me to "find" the LED on screen. Had to manually position and then use the overly-sensitive pseudo mouse to eventually find it. Move it a millimetre and it's gone again!
Similar issue on my UK purchased device, just over a month now, one update since purchase - CPH2025CPW_11_A.24 (still on June security patch!!)
Initially screen light effect for lock screen notifications worked but in the last few days has stopped lighting up for messages. Works fine for incoming calls though...

Categories

Resources