Hello people,
I have a very weird issue with the phone on my Galaxy Tab...
There's one particular number (one of my other ones) that causes the phone to throw an FC on my Tab on incoming or outgoing calls (to and from that number only!!)
I've tried 3 different ROMs and I've tried making and receiving calls to and from other numbers on the three different operators here and that particular number is the ONLY one that causes the phone to crash! I've also tried landlines and they work fine.
Now I clearly don't need to call myself so this issue isn't exactly killing me but I'm very curious as to why this is happening.
Any thoughts?
Sent from my Galaxy Tab using XDA Premium App
you mentioned that stock rom works with this number. Is this still true? Or does it fc with stock rom? Anything special about this number. Restricted or anything?
Just clarifying to see if its operator fault or tab's fault.
Nothing special about the number at all.
I haven't tried it with Stock ROM since I discovered it was a problem with this specific number. I have tried it with Overcome 1.4.4 and Overcome 1.5 Beta (which have different bases so can be considered as different ROMs in a way)
Sent from my Galaxy Tab using XDA Premium App
Hey all, need some help. I am a work from home employee. All of my meetings are via conference calls. Once I dial into the main dial in it asks for the conference pin number. When I enter it its almost as if my phone isn't sending the tones. It just keeps asking over and over. I have the same issue with my bank and voicemail. I can make the initial call but after that its a no go on being able to enter anything after the fact. Could this be ROM or Radio related? I'm currently on the current EVO radio and latest MIUI. Also had the same issue with CM7 latest.. any help / advice would be great.
Sent from my PC36100 using XDA Premium App
Change your audible touch tones to long or off.
Hi everyone,
I'm N8013 owner, recently upgraded to 4.1.2 N8013BMA3 .
After the upgrade, Mobile VOIP not working anymore. It cause the tablet to hang then not working at all , till I press power button for 8 seconds.
It was working flawlessly with N8010 LK9, N8013 LK8 .
Sent from my GT-I9100 using Tapatalk 2
mohammedsarhan said:
Hi everyone,
I'm N8013 owner, recently upgraded to 4.1.2 N8013BMA3 .
After the upgrade, Mobile VOIP not working anymore. It cause the tablet to hang then not working at all , till I press power button for 8 seconds.
It was working flawlessly with N8010 LK9, N8013 LK8 .
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I use sipdroid and have not had any issues since upgrading to JB. If you look at customer comments on playstore, some are reporting problems when running JB.
Thanks.
But does Sipdroid support Lowrate voip accounts?
Sent from my GT-I9100 using Tapatalk 2
mohammedsarhan said:
Thanks.
But does Sipdroid support Lowrate voip accounts?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I'm not familiar with this particular VOIP service so I can't say. They do provide sip settings here http://www.lowratevoip.com/sip . You could try setting up sipdroid with those settings. You could also contact their customer service since their app is known to have issues with JB, maybe they can help you. Good luck.
MagicJack works great on my GT-N8013 with JB 4.1.2
Sent from my GT-N7000 using Tapatalk 2
I use Grooveip and it works ok..
Thanks, but none of these are LOW RATE VOIP agents. They are useful for calling USA & CANADA
Im living in Italy
Sent from my GT-N8013 using Tapatalk 2
mohammedsarhan said:
Thanks, but none of these are LOW RATE VOIP agents. They are useful for calling USA & CANADA
Im living in Italy
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
I looked in one of the voip foruns that I read for info. Apparently, you can configure ATAs to use this service as well as other software, but you'll pay a higher rate. Their lower rate only applies to their app. I'd suggest that you try to contact their support staff. Issues with Jellybean have been reported on their Playstore page so maybe they can provide a solution. Here's the thread discussing their rates. http://forum.voxilla.com/threads/lowratevoip.14831/
Both grove ip and talkatone lock mine up. You have to use them twice in a row for it to happen
I had it installed on my SII running 4.1.2, and no issues at all.
However, I un installed mobile VOIP.
But today I got one hang up of the tablet.
Really I'm in love with this Firmware , and don't want to downgrade to LK8
Sent from my GT-I9100 using Tapatalk 2
Using the MagicJack app and it works *better* on 4.1.2 than it did on 4.0.4 or 4.1.1
Also having problems with GrooVe IP on 4.1.2:
When I placed a call: When the call connects, no one can hear me and I can't hear them. When I exit the app, the tablet can freeze and I have to reboot. When it didn't freeze, my microphone was screwed up and I had to reboot.
When someone called me: it didn't realize the phone was ringing.
I'm using a google voice number.
---------- Post added at 02:15 PM ---------- Previous post was at 01:16 PM ----------
I just tried an app called Spare Phone. Same problems as with Groove IP.
I then installed the free Magic Jack app. I was able to make phone calls, but since it doesn't go through google voice, I couldn't receive them on my phone number.
Maybe it's a google voice problem?
Ooma HD and AT&T Call International both work...
Vincent9756 said:
Also having problems with GrooVe IP on 4.1.2:
When I placed a call: When the call connects, no one can hear me and I can't hear them. When I exit the app, the tablet can freeze and I have to reboot. When it didn't freeze, my microphone was screwed up and I had to reboot.
When someone called me: it didn't realize the phone was ringing.
I'm using a google voice number.
---------- Post added at 02:15 PM ---------- Previous post was at 01:16 PM ----------
I just tried an app called Spare Phone. Same problems as with Groove IP.
I then installed the free Magic Jack app. I was able to make phone calls, but since it doesn't go through google voice, I couldn't receive them on my phone number.
Maybe it's a google voice problem?
Click to expand...
Click to collapse
I guess you need a MagicJack account/number to receive calls.
Sent from my GT-N7000 using Tapatalk 2
Vincent9756 said:
Also having problems with GrooVe IP on 4.1.2:
When I placed a call: When the call connects, no one can hear me and I can't hear them. When I exit the app, the tablet can freeze and I have to reboot. When it didn't freeze, my microphone was screwed up and I had to reboot.
When someone called me: it didn't realize the phone was ringing.
I'm using a google voice number.
---------- Post added at 02:15 PM ---------- Previous post was at 01:16 PM ----------
I just tried an app called Spare Phone. Same problems as with Groove IP.
I then installed the free Magic Jack app. I was able to make phone calls, but since it doesn't go through google voice, I couldn't receive them on my phone number.
Maybe it's a google voice problem?
Click to expand...
Click to collapse
It could be voice. It worked beautifully on 4.1.1 ... makes me sad in the pants. I love tapatalk. Ill try to uninstall and reinstall google voice with all new data and see if that helps
Update: well, no dice even with a new attached phone number and all new data with a fresh install. Even as we speak my heart is broken
I wrote to the Groove IP guys about the problem. This was my response:
"We don't have a Note 10.1, but we have tested with android 4.1.2. It sounds like something on the device isn't following the published android sdk. That's generally an issue in the rom, but sometimes we can work around those. It's possible the audio driver changed and maybe some different settings are required in the app. The best ones to start with would be Keep Screen Alive, Synchronize Voice, changing the mic buffer size, changing the mic source, or enabling WiFi tablet. I'd try those settings independently. Another thing to make sure would be the android advanced wifi settings. Make sure wifi optimization is off. And set wifi to stay connected always."
This is my first tablet and I know very little about Android. Does anyone think it's a ROM problem or could you suggest something for me to change?
All my other apps work fine. Until I run Groove IP, both my mic and speakers work fine; tablet does not hang or freeze. Before I upgraded I was on the samsung standard ROM using all default options/settings. My tablet worked great right out of the box. I just upgraded OTA when I was notified by samsung. With my first Groove IP problem, I uninstalled the app, rebooted the tablet and re-installed the app. No change. Still doesn't work.
TheWerewolf said:
Using the MagicJack app and it works *better* on 4.1.2 than it did on 4.0.4 or 4.1.1
Click to expand...
Click to collapse
I love that app but it's running the same for me. Still need to FC it and its battery sucking capabilities remain the same. Hoping for an update!
Regards,
Vincent9756 said:
I wrote to the Groove IP guys about the problem. This was my response:
"We don't have a Note 10.1, but we have tested with android 4.1.2. It sounds like something on the device isn't following the published android sdk.
Click to expand...
Click to collapse
The SGS3 and N2 are running the same SoC as the Note 10.1. I'd imagine Samsung reuses s/w components so that their common to more than one device. There are ten times more TW-equipped devices in the wild than AOSP. If Groove IP’s idea of testing is to throw it on AOSP and call it good they need to rethink their testing procedures. And you'd think if Samsung was using some drastically altered Wi-Fi stack that all VoIP apps would be affected, not just those we mentioned. So either there's something unique about the apps that don't work or the vendors of apps that do work are more diligent in their programming and testing to make sure their compatible with popular devices.
BarryH_GEG said:
The SGS3 and N2 are running the same SoC as the Note 10.1. I'd imagine Samsung reuses s/w components so that their common to more than one device. There are ten times more TW-equipped devices in the wild than AOSP. If Groove IP’s idea of testing is to throw it on AOSP and call it good they need to rethink their testing procedures. And you'd think if Samsung was using some drastically altered Wi-Fi stack that all VoIP apps would be affected, not just those we mentioned. So either there's something unique about the apps that don't work or the vendors of apps that do work are more diligent in their programming and testing to make sure their compatible with popular devices.
Click to expand...
Click to collapse
Yeah! Magic Jack worked fine for making calls. It didn't screw up my microphone, the audio was also fine and my tablet didn't freeze. I just couldn't receive calls because it doesn't work with a Google Voice phone number.
After I use Groove IP, the system standard voice input method (dictation) doesn't work. When I tap the mic, a voice says "I didn't get that" without even giving me a chance to say anything.
Here's my latest response from the Groove IP guys:
"We are quite interested in trying to resolve the issue. If it's something we can work around we will do that. As I mentioned currently we don't have a Note 10.1 but we are looking at buying one. Until then if none of the suggestions worked I can give you a version with logging. Unfortunately to get the logs you'll need a PC with the android sdk. Logcat isn't available from the device itself any longer with jelly bean."
I can't help with the log thing. I'm old now. and I decided not to get another PC because the Note does everything I need. I posted this here in case anyone with an android SDK (or doesn't mind install one) is interested in helping them. Regardless, sounds like they'll be getting a Note and hopefully the app will get fixed in a few months.
Anyway, if you're having problems, you may want to let them know. The app may get fixed faster if more people send them an e-mail. You can send a message with your problems to [email protected].
Hey guys,
Bizzare problem here.
I've been using call forwarding on my iPhone pretty much forever. Never had an issue.
I would forward to two different numbers depending on my location. - Work or Home -
The issue when I try to forward with my nexus 4 is that for the last few months, doesn't matter which number I would forward to, it would forward all calls to work. And recently it switched to forwarding all calls to home.
I tried using the call forwarding option in the settings and I've also tried forwarding using the input method being *21*phonenumber#.
Now, I still have my iPhone 5 and if I drop my sim card in there and proceed to call forward everything is always flawless.
I tried rebooting and this is my second nexus to do this. It didnt bother me before because I could forward calls to work at least, now they all go to home which isn't as important.
thanks for reading
If this help anyone one day. Resolved in 4.3
Sent from my Nexus 7 using XDA Premium 4 mobile app
Has anyone discovered a way to unlock the calling feature on the SG Tab 4 line of products yet?
Sent from my SM-T337T using Tapatalk
jhlarson1 said:
Has anyone discovered a way to unlock the calling feature on the SG Tab 4 line of products yet?
Sent from my SM-T337T using Tapatalk
Click to expand...
Click to collapse
Mine works for some reason already. The phone app and the text app are already there. Only works as a speaker phone or using a bt headset though.
Who are you with? T-Mobile here and I only have txting. Even try ed Activity Launcher to find dialer app, but no go.
Sent from my SM-T337T using Tapatalk
I did find speed dialer under contacts in Activity Launcher. I can apply a contact to speed dial number, but when I atempt to use said number. Message shows up... "Voice calls not supported." Beh... was worth a try.
Sent from my SM-T337T using Tapatalk
Decided to dive into Activity Launcher again. I found 'Voice Call Barring' under Device. Opened it up and come to find if i only new the passwords i can activate incoming and out going calls on the T337T. Now to figure out the passwords or find them online.
Sent from my SM-T337T using Tapatalk
-- Edit --
Tryed 0000 worked sort of... options turned on and off, but message popped up saying 'Network or simcard error.'.
jhlarson1 said:
Decided to dive into Activity Launcher again. I found 'Voice Call Barring' under Device. Opened it up and come to find if i only new the passwords i can activate incoming and out going calls on the T337T. Now to figure out the passwords or find them online.
Sent from my SM-T337T using Tapatalk
-- Edit --
Tryed 0000 worked sort of... options turned on and off, but message popped up saying 'Network or simcard error.'.
Click to expand...
Click to collapse
Sounds like you found the magic answer, however, your SIM card may only be provisioned for data only. Take the SIM out of your phone and try it.
Im going to try swapping my wife's sim with mine. If that doesn't work I think i'm going to just leave this one alone for the time being.
Sent from my SM-T337T using XDA Free mobile app
jhlarson1 said:
Im going to try swapping my wife's sim with mine. If that doesn't work I think i'm going to just leave this one alone for the time being.
Sent from my SM-T337T using XDA Free mobile app
Click to expand...
Click to collapse
did you figure this out-thread hung up with this when you seemed so close to resolution (either it worked or did not) thanks
i have tried a bunch of passwords and nothing, called tmobile and Samsung and they offer no solution at all, i am deployed and really need to be able to use the tab as a phone
joseluisgonzalez17 said:
i have tried a bunch of passwords and nothing, called tmobile and Samsung and they offer no solution at all, i am deployed and really need to be able to use the tab as a phone
Click to expand...
Click to collapse
in looking at the user manuals it appears the T337T does not have an additional microphone (for speaking into as in a phone call) unlike the T335 which does. This indicates to me that the T337t could not be used as a phone even if someone managed to get the phone app, modem etc all to work together (unless microphone arrangements were changed and even at that would not be worth the trouble-unlikely it would work well-as the folks using CM/AOSP on such tablet phone devices-no solution for echo issue due to speaker/microphone config)