Has anyone tried a Skype videocall on the Jetstream? I can't get the cameras to work. The camera light lights up for a few seconds and that's it.
confirming same issues - installed latest skype version from the market, trying to make a video call over WiFi , no luck, the call connects but without video.
THanks for confirming. HTC says to talk to Skype.
Skype isnt showing up in my market anymore when I search for it, can anyone confirm if its still there?
(edit, it was there all along lol - wasnt showing up because my maturity filter settings were set low)
Same issue but noticed that when the other user initiates the call it works.
dcd17 said:
Same issue but noticed that when the other user initiates the call it works.
Click to expand...
Click to collapse
having the same issue and haven't tried the other way around yet... will give it a shot and report back.
Related
I just downloaded skype onto my phone last night and started a video call. I was disappointed to see that I could only have a video call in landscape orientation. When I held my phone portrait orientation it would just show me as sideways to the other person.
Is everyone having this issue or did I just somehow get unlucky? I've tried a factory reset and uninstall and reinstall and that didn't change anything.
Does anyone have a fix for this?
paintballkev812 said:
I just downloaded skype onto my phone last night and started a video call. I was disappointed to see that I could only have a video call in landscape orientation. When I held my phone portrait orientation it would just show me as sideways to the other person.
Is everyone having this issue or did I just somehow get unlucky? I've tried a factory reset and uninstall and reinstall and that didn't change anything.
Does anyone have a fix for this?
Click to expand...
Click to collapse
I can't help you as I only use Google Talk - Skype is such a horrific battery drainer that I will never again install it on an Android device.
I can't stand skype myself, but trying to get the others to switch is a different story....
paintballkev812 said:
I just downloaded skype onto my phone last night and started a video call. I was disappointed to see that I could only have a video call in landscape orientation. When I held my phone portrait orientation it would just show me as sideways to the other person.
Is everyone having this issue or did I just somehow get unlucky? I've tried a factory reset and uninstall and reinstall and that didn't change anything.
Does anyone have a fix for this?
Click to expand...
Click to collapse
I was just using skype today on my phone and I was able to get it to work. I enabled the auto-rotate screen option on the phone itself and it worked.
The newest update f'd everything up. I had to revert to an earlier version via TiB.
Sent from my SAMSUNG-SGH-I777 using XDA App
paintballkev812 said:
I just downloaded skype onto my phone last night and started a video call. I was disappointed to see that I could only have a video call in landscape orientation. When I held my phone portrait orientation it would just show me as sideways to the other person.
Is everyone having this issue or did I just somehow get unlucky? I've tried a factory reset and uninstall and reinstall and that didn't change anything.
Does anyone have a fix for this?
Click to expand...
Click to collapse
although this is not a fix (I'll leave that to the skype devs), I'll suggest either using GTalk or Tango. I use Tango and my battery does not drain and it works great. I will not go back to skype until they fix the battery drain issues (if that ever does get fixed).
Entropy512 said:
I can't help you as I only use Google Talk - Skype is such a horrific battery drainer that I will never again install it on an Android device.
Click to expand...
Click to collapse
Quoted for da truf! skype killed my battery like no other
draino623, Would you provide that apk for me?
Hi guys. I have a peculiar problem in my new Galaxy S3. Whenever I make a call, the screen remains on even though I have ticked the 'Auto screen off during calls' option in call settings. Also, whenever I input any numbers while in a call, the keypad does not hide. I mean I get the 'Hide' option but it doesn't do anything and the keypad stays on the display. Can anyone tell me if this is a known issue or am I the only one facing it? Is there any workaround this? I am on stock firmware (XXLF2) and haven't even rooted my phone yet. Please help me guys!
I have exactly the same problem. I know the proximity sensor works, because I tried the proximity sensor test app. But my phone does not turn off screen when in call.
i have same problem any one help us ?
I also have this problem.. and to make it worse, I can't seem to call out occasionally. I swipe to call, but nothing happens. I can't even dial out at times.. rebooting usually solves the issue, but the problem quickly comes back.
I'm not rooted, on stock rom. Anyone know what the issue is?
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
BlueG2 said:
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
Click to expand...
Click to collapse
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Beards said:
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Click to expand...
Click to collapse
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
BlueG2 said:
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
Click to expand...
Click to collapse
'Voice' was my search pattern. It's got to be there I'll find it.
Hi guys,
Did you find a solution to this problem yet? I have the same problem, and no matter what I do, I can not make it work. The screen is always on during a call. I am using the stock rom, without root, as it is.
------------
Nevermind. I fixed it by removing FSC ID, apparently it was interfering.
i had the same problem but it was fixed after i made a phone restart.
I have the same problem...
I’m coming from an EVO 4G and I forget how I finally got it working but I was able to use Voice Search or the Bluetooth headset to make calls by name from the folks in my contacts list.
I do remember that the voice search for making calls or sending text will not use your phone contacts but only your Google contacts. That was the only real gotcha I recall. I had to export my contacts, then import them into Google contacts and then link the two contacts together. Then the voice search would finally work.
I had done this on the DNA but the Voice Search would still not work. I finally had to go into the Voice Search settings under Phone Search and remove everything but “People”. Now when I say “Call: Bob” it pops up Bobs contact info and dials him instead of doing a Google search for “Call: Bob” or whatever. By default it has 4 or 5 things checked including People but it just did not work for me. ???
This did not however affect the Bluetooth headset dialing. It still just says “I didn’t catch that.” or tries to dial voice mail or random numbers. So, it’s still acts like the contacts list is empty.
Any ideas?
The Hotword detection is also not working. “Say Google to launch voice search.”
Thanks.
Hmm… Just me then?
Just over 250 views and no one can say they do or don't have the issue?
I did speak to a few tech support folks at Verizon and HTC but they could not tell me anything. I think I'm taking the phone back in the next few days. I like the phone but a phone that can’t dial from the headset is kind of a big deal.
I am curious about this too.
nabbed said:
I am curious about this too.
Click to expand...
Click to collapse
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
syler2012 said:
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
Click to expand...
Click to collapse
I can confirm the same problem on GS3 running CM10 latest nightlies. It's a Gapps issue....We need a way to force gapps to listen to bluetooth mic....
I think it is a problem with Bluetooth, Jellybean, and Google Now/Voice. This same type of issue was reported on the Galaxy nexus once it had been updated to Jellybean.
Some GN users installed alternative dialers/voice assistants and had success over BT.
I think Android 4.1 has some issues with BT. Android 4.2 switched to a completely new stack, and that too is experiencing problems, or perhaps growing pains. The fact that Android switched bt stacks from 4.1 to 4.2 leads me to believe that Google engineers ran into some deep issues with 4.1, and decided it was better to start from scratch with 4.2 (related a whole host of BT issues, including BT 4, low power modes, AVRCP etc., and interfacing them with the microphone for google voice search/now.
I just took it back and of course the Verizon rep had never heard of any issue with JB. So I showed it to him.
Of course I still had to pay the restocking fee.
Hey guys! This is my first Android device, coming from the iOS Eco system. I am very happy with my purchase thus far! However, I'm having an unusual problem with the Hangouts audio call feature. I'm running 5.0.1 and the hangouts apps are up to date. During an audio call, I get disconnected with the person I am calling quite often, especially if I lock the screen during a call. But oddly enough it still happens if the device is awake. Is this a known glitch or is it something unique to my device? Any recommendations? I've already tried clearing the cache, but have not tried it again sense. I will also point out that calls are okay when I use the Hangouts app on the iOS devices.
Thanks for any help.
v/r,
KM
kenmillerjr said:
Hey guys! This is my first Android device, coming from the iOS Eco system. I am very happy with my purchase thus far! However, I'm having an unusual problem with the Hangouts audio call feature. I'm running 5.0.1 and the hangouts apps are up to date. During an audio call, I get disconnected with the person I am calling quite often, especially if I lock the screen during a call. But oddly enough it still happens if the device is awake. Is this a known glitch or is it something unique to my device? Any recommendations? I've already tried clearing the cache, but have not tried it again sense. I will also point out that calls are okay when I use the Hangouts app on the iOS devices.
Thanks for any help.
v/r,
KM
Click to expand...
Click to collapse
I don't get disconnected but i lose the microphone meaning the other person can't hear me, but i can hear them.
Is that what you mean by getting disconnected?
clubtech said:
I don't get disconnected but i lose the microphone meaning the other person can't hear me, but i can hear them.
Is that what you mean by getting disconnected?
Click to expand...
Click to collapse
Yes, I guess that is a better diagnosis. Have you found a way to revive the microphone once that occurs?
It happens on Skype and all voip apps as well, so not just hangouts.
Seems like an android software bug on this device.
I think plugging a headset and unplugging brings back the mic until it happens again.
Here is the same discussion o the Skype forums: http://community.skype.com/t5/Android/nexus-9-tablet-looses-microphone-during-call/td-p/3736171
Hopefully google will fix it in the next software update.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.