Hey guys,
I was using Galaxy tab 7 since 6 months, yesterday i upgraded it to Galaxy Tab 7 Plus (P6200 with Honeycomb 3.2).
Basically i use my tab to make sip (voip) calls for example through Fring, Nimbuzz etc. it was working perfect in older version. But in newer one, when i try to make any call, it immediately disconnects.
There is also a genuine SIP setting in the tab, but same problem.
I have also installed SIP Driod, SAME PROBLEM.
Please let me know is there any special setting?
I have re-installed all above application, have done factory reset, rebooting many time. but
No one knows solution for my problem????
PLEASE HELPPPPP
Still waiting ...................
Dear Friends,
I am new to this forum . I have just bought S3 International version, two weeks back as a first android phone . Its with Jelly bean 4.1.2.
I am facing the notification problems in wifi . Notification works fine in mobile network but not always in home WIFI. The problem starts only if I change twice in between wifi to mobile ( wifi -mobile -wifi ). I am using notification for Facebook messenger and Gtalk. I did factory reset ,hard reset and also tried in friend's WIFI but nothing works to that problem. Only one thing I see, it works if I reboot the phone, then the notifications start to work again in the same WIFI and I use to get all the old notification also.. During this phase( notification stop phase) I see that Gtalk goes offline even though I can chat and Facebook messenger remain online. I am not using any apps other than skyple/facebook/voip that may have an impact to this problem.
Pleas let me know if you are facing this issue or if you know any solution towards the problem.
Thanks for reply in advance.
Malay
Hey all,
I've been searching for a while now and decided I should just post my question finally. I have the Galaxy SIII, rooted, running CM10 stable. For the last 3 months or so, my stock SMS app, Messaging, has been randomly force closing and crashing. The only way to fix it is by rebooting the phone. I've tried re-flashing the mod 5 times, and even wiped data and done 2 factory resets. Still no luck.
And more recently my stock "phone" app has been doing it too. It crashes when I open up the dial pad and drops calls randomly and I have to restart my phone for it to work again.
Both of these will happen randomly. Sometimes I can go 4 hours without having to restart my phone, other times I have to restart my phone every 20 minutes. It's really starting to bug me.
Is there an app that's known to cause these crashes? Or is there a possibility that the mod file is corrupt? Thoughts? Questions? Any help is appreciated!!
Stock but you say you flashed the mod .
CM 10 Discussion post is the place to ask .
Do you actually have an I9300 as per this forum ??
jje
I already used my gear s for months successfully with my note 4. Always worked OK, also remote connection through WiFi or 3g went without hiccups. Yesterday I bought an edge+, I reset my gear to defaults and installed and ran gear manager. Pairing was OK. All seemed good, only the moment Bluetooth connection is lost the gear switches to WiFi and almost immediately says it cannot set up remote connection. Also on 3g is not working. I ticked the remote connection checkbox in gear manager settings but doesn't work. Already three times reset the gear and setup again, completely removed all gear manager components, no luck so far. Working seamless on Bluetooth, not through remote connection.
Any body with s6 edge+ experience the same?
I have the same issue with my S6 edge+.
I also used the gear S with note 4 without remote connection issues.
I passed by Galaxy S6 Edge to Galaxy S6 Edge+ and I do not work more calls and notifications remotely with Gear S .
Before when I walk away from the range of the bluetooth with the Galaxy S6 Edge could perfectly to have call forwarding and notifications, now with Galaxy S6 Edge+ I get the message that you can not make the call diversion etc etc. connect to Bluetooth.
You have done the same experience?
You know the reasons and solutions?
Thanks for the reply
( * Please forgive Google Translate for the bad translation)
ddborello said:
I passed by Galaxy S6 Edge to Galaxy S6 Edge+ and I do not work more calls and notifications remotely with Gear S .
Before when I walk away from the range of the bluetooth with the Galaxy S6 Edge could perfectly to have call forwarding and notifications, now with Galaxy S6 Edge+ I get the message that you can not make the call diversion etc etc. connect to Bluetooth.
You have done the same experience?
You know the reasons and solutions?
Thanks for the reply
( * Please forgive Google Translate for the bad translation)
Click to expand...
Click to collapse
I have the same issues. I reported them to Samsung. I suggest everybody does the same. So maybe Samsung wakes up and fixes this problem. I suspect it has something to do with gear manager. I noticed that the preinstalled version on the s6 edge plus is older then the one you find in the Samsung store. But I cannot update to this version....
Not dependent on the software version. My S6 Edge+ version is the same that is on the Galaxy Apps (v.2.2.15070942)
ddborello said:
Not dependent on the software version. My S6 Edge+ version is the same that is on the Galaxy Apps (v.2.2.15070942)
Click to expand...
Click to collapse
You're right. Same version here. I was wrong because in my galaxy store the date next to the version number seems to be today's date. When I looked yesterday it was 9 Sept. That way it looked like it's was released today.
+1, same here
I also updated my S6 edge to the plus version. Everything worked fine with S6 edge but now I can't connect remotely (wifi or 3G). BT connection is OK.
I have reported this to Samsung and they promised to be in touch. Nothing yet thought...
6sto said:
I also updated my S6 edge to the plus version. Everything worked fine with S6 edge but now I can't connect remotely (wifi or 3G). BT connection is OK.
I have reported this to Samsung and they promised to be in touch. Nothing yet thought...
Click to expand...
Click to collapse
I thought i read somewhere that there was an update for gear manager. Can you check the samsung store to see if there actually is? Maybe it fixes the remote connection problem. I cant check for myself because i had to send my edge+ for repairs (i'm the guy who's back cover shattered)
Let me know please.... And if not succesful keep reporting to samsung... I'll do the same
Sent from my SGP512 using XDA Premium HD app
For me no update available..
Build date is 14.9 but its the same version number (2.2.15070942)
It still doesn't work
Last V.2.2.15070942 ..... remote transfer does not work!
We must insist to request a final settlement with the Service Samsung People.
Same here...note 4 worked perfectly. I swiched 2 days ago to S6 Edge plus and only Bluetooth connection works. Remote conection fails. Tried 3 resets/ uninstals but still nothing
Just reconnected to note 4 and remote connection works flawlessly... Back to the edge and the same problem... Come on Samsung!!!!!
Sent from my iPad using Tapatalk
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
ingenious247 said:
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
Click to expand...
Click to collapse
You have edge+ ? Cant try myself for the moment, maybe somebody can confirm? Tnx for the tip...
Sent from my SGP512 using XDA Premium HD app
Yes Edge+
Sent from my SM-G928T using Tapatalk
I use Multi Sim on the gear S so i tried it with the Multi Sim option. Doesn't work for me.
Anyone succeed with this method? I tried it a few times but with no luck.
ingenious247 said:
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
Click to expand...
Click to collapse
Hi there,
Having the same issues as everyone else here. I am connected to a Note 5 , with the gear manager pre installed. everything works fine except for the remote connection, I just get an error message "failed to enable remote connection" .
I was going to try this fix you suggested, however on my version of gear manager I do not even have the option of auto call forwarding, so I cant try your fix.
I have also tried connecting to a friends S5 and the remote connection worked fine.... this is very disappointing from Samsung to have this major function not working properly for so long.
I hope they provide an update / fix soon.
Regards
Brian
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
glenner05 said:
I have the same issues. I reported them to Samsung. I suggest everybody does the same. So maybe Samsung wakes up and fixes this problem. I suspect it has something to do with gear manager. I noticed that the preinstalled version on the s6 edge plus is older then the one you find in the Samsung store. But I cannot update to this version....
Click to expand...
Click to collapse
Can you provide a link to the where to report to Samsung please and Thanks
So the problem is with the note 5 as well....it must be the version of gear manager cause its a different version than my note 4 which it works perfectly on for the past 9 months. I love my gears s. So i hope Samsung fix this problem!!!!
Sent from my iPad using Tapatalk
cydiamante said:
So the problem is with the note 5 as well....it must be the version of gear manager cause its a different version than my note 4 which it works perfectly on for the past 9 months. I love my gears s. So i hope Samsung fix this problem!!!!
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I just spent some time with a "Samsung Expert" in online chat discussing the issue , they said this has not yet been reported to them, so I hope everyone who is posting here will start reporting it to Samsung.
They have now arranged to call me on Wednesday and remotely take control of my phone to see if they can find or resolve the issue , so I will wait and see what they come up with, in the mean time I hope everyone will start contacting Samsung.
I will post back again after my call with them on Wednesday.
Regards
Hi guys, I'm only starting this thread because I searched over 50 pages and tried different methods already.
After my Xperia Z3C decided to have major issues on the screen, I decided to go back to my SIII while I try to fix the Z3.
My S3 is still running perfectly under cm-11, the only problem is that I can't connect any calls, if I try to make a call both phones rings normally, but when the person answers the phone (or the other way around) the connection goes mute, no sound at all. After I hang up the call the SIII loses the networks for a couple of seconds and then it comes back up.
Viber and Skype works, messaging works, 3G Mobile Data connection works with no problem, and the phone only loses signal when I place or receive the calls.
I upgraded from cm-11-20150901-SNAPSHOT to cm-11-20160115-SNAPSHOT, installed a new modem, checked APN configuration and IMEI, the only thing left to do is to Odin flash back to stock android, and actually I don't want to do that, I love cm since the day I installed.
One thing to notice is that the SIII worked for quite some time with cm-11 without presenting this problem.
What else can I do? Thank you very much in advance.
Can no one help me?