After the 4.1.2 update talkatone stopped working right. It locks up the whole tablet. And groove ip wont work at all. Did another factory reset but still screwed up. anyone else having these problems?
ok well ive uninstalled, reinstalled google voice and talkatone 4 or 5 times. ive done 3 to 4 factory resets, ive restored my note with cwm to 4.1.1 and all works great. redownload the 4.1.2 and all goes bad again. you can use talkatone 1 or 2 times then it locks up the tablet and sets it on vibrate to boot. same with groove ip now. has anyone made several calls from talkatone or groove and it workes right?
Did u ever get groove ip to work on 4.1.2?
I've posted in the longer voip thread in the general section, too. Csipsimple works on JB 4.1.2. I had been using Sipdroid but it was a source of system crashes on JB so I deleted it. Download the additional free Csipsimple codecs as well. I have no issues with audio on incoming or outgoing calls and it's actually using less battery power than Sipdroid, which wasn't really a power hog. I have my Google voice setup with pbxes and there are no issues with registration.
malimal said:
Did u ever get groove ip to work on 4.1.2?
Click to expand...
Click to collapse
Nope. It is a feature I miss a lot
talkatone / grooveip
conan1600 said:
Nope. It is a feature I miss a lot
Click to expand...
Click to collapse
I can get GrooveIP working, but Talkatone completely locks up my tablet. Can't even shut it down. It finally reboots after I lean on the power key for a couple of minutes (NK). It's annoying enough that I'm uninstalling it, and it's going NOWHERE near my phone.
But GrooVeIP worked fine for a while, including this afternoon. Not behaving tonight, but I think it's Hangouts, blocking calls to other GV clients. Tried signing out completely, but it's still wonky. Rings, and appears to answer, but on the outgoing end there's just constant ringing and then voicemail. I'll take it up again tomorrow, perhaps, because I like having the wifi phone.
And this is why I bought the N8000 with phone calls enabled....:laugh:
I've been running GooveIP on JB 4.1.2 without any problems on my GT-N8013. Even with the update to Hangouts.
Now I am running GloryROM for GT-N8000 / GT-N8013: http://forum.xda-developers.com/showthread.php?t=2273892 using the instructions to install on GT-N8013. This leaves the phone & messaging functions in place, and that could have some effect on why it works just fine. I do use the built in phone to do the calls as well.
If you are using a N8013 rom without the phone functions, I wonder if that could be the cause of it not working on JB 4.1.2. Since something might have been removed with the phone functionality that causes the problems. But can't say without a lot more testing and looking into everything.
Wow, Niscandia, thanks! I'll take a look at this. Like I noted above, GrVIP used to work just fine, even after JB. Seemed to go off the rails with Hangouts, but I'm no longer convinced of an association. I've learned to get along without GrooVe now, so I hadn't pursued this much lately. But I'd like to fix it, so I can help trouble shoot for other folks, so I'll take a look at this. BTW, I'm using an GT-N8013.
Niscandia said:
I've been running GooveIP on JB 4.1.2 without any problems on my GT-N8013. Even with the update to Hangouts.
Now I am running GloryROM for GT-N8000 / GT-N8013: http://forum.xda-developers.com/showthread.php?t=2273892 using the instructions to install on GT-N8013. This leaves the phone & messaging functions in place, and that could have some effect on why it works just fine. I do use the built in phone to do the calls as well.
If you are using a N8013 rom without the phone functions, I wonder if that could be the cause of it not working on JB 4.1.2. Since something might have been removed with the phone functionality that causes the problems. But can't say without a lot more testing and looking into everything.
Click to expand...
Click to collapse
Related
I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.
kingston73 said:
I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.
Click to expand...
Click to collapse
It is none of the above. Wifi calling on Tmo US with an ICS ROM is a known issue and will not be resolved until a developer gets an actual Tmobile US RUU to play with.
Between that and the inability to use the MyAccount app on an ICS is the whole reason I'm still on AHRD 3.6.
It is well known and documented that WiFi calling will work for a short time then cut out...and the fix by a dev is waiting on the above mentioned RUU.
I know that I've read posts that people claim to have been using wifi calling on ICS without any issues. I know its a known issue and I know the root of the problem is ICS itself, but why do some people say they use it without a problem?
My guess is people try to talk on the phone like me...as little as possible.
if someone is able to carry on a lengthy conversation without issues, I'm in the same boat as you...I'd like to know too.
Sorry...I didn't know you were aware of the apparent issues...
I have Wifi Calling partially working on my T-Mobile/HTC G2 running Andromadus Alpha13 (CyanogenMod 9 based).
I haven't figured out all the specific build.props entries that it needs to work, except I know that some update.zips with a minimal set don't work. I have one that pretty much replaces the build.props with one that spoofs TMO build data as well as other stuff and that this build.prop file works.
In addition to needing the .so files that are provided in all the update.zips I've found, and the Wifi Calling APK, I've read that GanOptimizer.apk is needed too and added that to mine.
I've found I can unreliably make outgoing calls. The first boot it did not work, the second boot I was able to make a call every other attempt or so. The audio quality seemed good too.
I can receive every single incoming call but they won't route audio wise and will drop. Then the app gets into a bad state and can't make outgoing calls either. Rebooting fixes that.
I haven't finished figuring out the bugs. The bottom line is it seems that CM9 *does* support Wifi Calling and it can work with some libraries and APKs added, however there are bugs that need to be figured out and fixed.
So from what it sounds like if I switch to Revolutinoary HD, then I won't get wi-fi calling, but since I'm running CM7, I get wi-fi calling but in exchange my HD camera doesn't work. We really just have to wait for updates now don't we?
Hey I actually just got HD Revolution installed, made a call on wi-fi for 15 minutes or so and it worked just fine.
Im running ARHD ICS and wifi calling works perfectly for me.
Sent from my HTC Sensation 4G using XDA App
That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.
kingston73 said:
That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.
Click to expand...
Click to collapse
+1. Same boat.
Well there's not much to tell really. I just updated my firmware as I was running CM7 to ICS and installed AR HD ICS 6.5.1. Other than that I guess I run NOVA launcher and that's really it
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Borrow the ole ball and chain's phone and see if it acts the same way.
Tried it. It works fine in my car, she has an S4. My phone also does the same in her car...
Sent from my HTC6525LVW using Tapatalk
Sounds like u need to swap it out for a replacement. Never had an issue unless using custom kernals.
deeznuts said:
Sounds like u need to swap it out for a replacement.
Click to expand...
Click to collapse
^ ^ What he said^ ^
Weird...
My M8 should be here today and I have a 2010 Mazdaspeed3. I hope this isn't an issue with all of them. Although, my MS3 has a long history of it's bluetooth not getting along with HTC phones.
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So far, no. It took me like 20 minutes to get the phone to pair but once that was done it hasn't disconnected at all. I have music constantly streaming through Bluetooth to the car and I've taken a couple calls with no issue.
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
jdebutts said:
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
Click to expand...
Click to collapse
Have you tried clearing data and cache in settings?
the Red Viper ROM
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
Sounds like the common theme may be root for whatever reason. I assume when you first had the phone and it worked that you were not rooted? Possible issue?
Sent from my SM-N900V using Tapatalk
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
you need to let HTC backup app take care of backing up your texts etc...what if you dropped the phone in the toilet tonight or got pushed into a pool?
this app is free...will backup your stuff daily or on demand and will restore email accounts/texts/desktop/apps/blinkfeed settings etc.
http://www.androidfilehost.com/?fid=23329332407589902
install that, backup to the cloud (uses Google drive) and then continue troubleshooting without fear of losing stuff.
Sent from my SM-T320 using Tapatalk
Hey guys. Ia anyone having any issues with background data? I don't get push Notifications When im not on WiFi. Even when I'm on WiFi, my screen needs to be on to retrieve them. I've tried toggling the background data setting on and off. Music seems to work fine though, streaming. Tried prl and profile updates and even hard reset. I also installed the software update. anyone else having the same issue? Ia there a setting I'm missing?
Tyia
I have something similar, it seems to update but only when it wants to. Specifically with some apps data works only when on WiFi. For Example Google Play Music takes forever (I mean 10 minutes to load one song) to load songs on Sprints Network, but it is immediate on WiFi. Same thing with Facebook App, it will take 15-20 minutes to load data when in Sprint Network. As soon as I connect to WiFi it works immediately. Other apps work great, others don't.
Had the same issue. Sprint told me to do the ##72786# trick. Seems to work so far.
skinneejay said:
Had the same issue. Sprint told me to do the ##72786# trick. Seems to work so far.
Click to expand...
Click to collapse
Grrrr i don't get it. I tried that, still a no go. Google play music, google wallet and hangouts don't work period on lte. But voice search and the google app works just fine. No push Notifications on anything except on gmail for some reason. So frustrating, i don't get email notifications for work which is bad. I blame sprint's software team because my sprint note 4 and the s6 on verizon and att have no such issues.
I also posted a thread describing the same issues. All i know is sprint bette be working thier asses off on this because this is ridiculous i miss my gvoice txt for work because of this. If a customer cant txt me than i lose money. And im blaming sprint right now
Not to mention that the workaround is to use wifi. To use wifi!! Did they forget that there is also a major bug with wifi draining the phone like crazy as well. Pretty messed up
I've got the issue back again. I'm going to best buy to return. My wife's white phone is working perfect. Do you guys have the black version?
White, im outside of my 14 days. I have the white.
It works! Out of nowhere today , all of the issues are gone !
Guys please contact your carrier and samsung this is a bug affecting a lot of phones. I'm on the 4th and it is still an issue. The first 2 were black 64gig models and the last 2 are gold 64gig models.
http://forum.xda-developers.com/gal...s-stop-screen-off-t3071248/page4#post60888131
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here