I'm still running 10B on my VZW G4 and I can no longer retrieve voicemails. Already tried deleting/reinstalling the app, clearing the app's cache, wiping cache in recovery, all that good stuff.
Is anyone else having this issue w/ 10B & Verizon's VM app? If you have 10B but use google voice for VMs or a different app, is that working properly for you? If so, which VM app is playing nicely with 10B?
I'd just hate to update away from 10B solely to get VM back and bork myself by going from v0 to v1 (but let's not talk about that since there are already 100 other threads on that matter!)
Okay to close thread - issue resolved
Related
For everyone that has been clearing the Google Services Framework to try to get the OTA, does it have any negative consequences? (Besides having to re-associate your device with google.com/play)
I have been hearing a lot of people say it will mess up a lot of applications that use C2DM for notifications? Is there any truth to this? Can a dev just clear this up? Do notifications for apps continue to function fine after clearing the framework?
Thanks
I'm a total noob to flashing ROMs etc. and used Wugfresh's root kit to flash my yakjuxw to yakju. Then I had to 1) force stop the Google Services Framework, 2) clear data, and 3) check for updates all of twice before I got the JRO03C OTA ...
Now I'm noticing that GMail, Google+, Facebook, etc wont show me notifications in the notifications shade. The notifications come through on my older Nexus S (which I use as wifi only) just fine, but wont show up on the galaxy nexus
I was searching for a solution to the problem on Q&A thread and found this post, thought I'd confirm your suspicions. To me this is worth getting JB this soon, and I'm sure there's a solution anyway...
try clear cache, data and re-install the app.
Reset app preferences! Any fixes for these issues?? Have cleared cache partition,. got 2 new sim cards to no avail. Randomly mine n my husbands phones go straight to vm without ringing or showing missed calls!! Same for my son in another state. Cust svc is no help. Have cleared app preferences multi times. Anyone else with these issues?! Any help appreciated.
I had that on mine when I was running 4.3, but only with wifi calling. first random incoming calls, then all incoming calls would go straight into voice mail and then I couldn't even call out on wifi. Temporary solution was to change preferences to cellular calling from wifi calling. Then I updated to 4.4.2 (nf4) and its fixed now and it works fine with wifi calling and all. I suspected t-mo made some changes in their server software and either accidently or on purpose never tested properly with older firmware, introducing some bug, but feel free to call it wrong guess. The reason I suspected problem was on their side, was that I have not updated or changed my phone at all, since before problem started and installed probably only 1 new program, which later I deleted it as first suspect, but deleting it didn't fix the problem at all.
Did you ever install google voice? I was having similar problems because I had installed google voice, then removed it, thinking everything would be fine. It turns out you need to change something on your Google account also. There was a previous thread about google voice.
No google voice in my case. The program I installed I think it's called Wechat for text, voice and video calls over internet. I deleted it after my family came back from overseas vacation since no longer needed, but that didn't fix wifi calling until firmware update. Could have been some settings got messed up and weren't restored until update.
smaisonville said:
Did you ever install google voice? I was having similar problems because I had installed google voice, then removed it, thinking everything would be fine. It turns out you need to change something on your Google account also. There was a previous thread about google voice.
Click to expand...
Click to collapse
thanks
I reflashed firmware from SamMobile. Appears to be working better. Difficult to tell 100% yet. Appears the app prefernce requests are no longer an issue.
I don't know when it it started, but my contacts just won't open, and even my dialer is difficult to open unless it is on the actual dial pad when closed last (if it's on logs, favorites, or contacts it also force closes whenever I try opening it). I was using Ready Contacts for a while, but I don't like it so I went back to my TouchWiz contacts and dialer to find they are all jacked up. I've tried clearing cache, manually force closing it, and clearing data, but nothing works.
Anyone know what would cause contacts to refuse to open? I'm on 4.4.2 NF9 rooted but otherwise stock.
Thanks.
I have exactly the same issue, any help would be appreciated
Sent from my SM-N900T using XDA Free mobile app
I just upgraded on the weekend. I did not have problems with contacts but had problems with Google services using to much battery.
I had to factory reset. You don't lose root, you will have to download it again.
Using Titanium back and restore data was problematic with apps like 3C Tool box that alter performance or permissions on your phone. I cleared my data for 3C and some force closes went away.
I was getting reboots when scrolling through some apps. Reinstalling 3C and resetting the data got rid of problems.
It is new firmware and sometimes it is better to reinstall apps than restoring them from backup.
I don't know if any of this will help. Just some thoughts from my experience.
MadJoe said:
I don't know when it it started, but my contacts just won't open, and even my dialer is difficult to open unless it is on the actual dial pad when closed last (if it's on logs, favorites, or contacts it also force closes whenever I try opening it). I was using Ready Contacts for a while, but I don't like it so I went back to my TouchWiz contacts and dialer to find they are all jacked up. I've tried clearing cache, manually force closing it, and clearing data, but nothing works.
Anyone know what would cause contacts to refuse to open? I'm on 4.4.2 NF9 rooted but otherwise stock.
Thanks.
Click to expand...
Click to collapse
Using xposed? First thought was the mod for showing a call icon in contacts list... if you are in a VoLTE area (and have it on) it FCs due to pointing to a non-existant image. Not sure it's the issue but figured I'd share.
dwitherell said:
Using xposed? First thought was the mod for showing a call icon in contacts list... if you are in a VoLTE area (and have it on) it FCs due to pointing to a non-existant image. Not sure it's the issue but figured I'd share.
Click to expand...
Click to collapse
That's probably exactly it, since it's intermittent, and seems to have started around the time I installed Wacom. I've disabled it and will see if the problem goes away. Thanks!
Hey has anyone ran into any issues with Third Party apps causing the phone to lock up once the camera is accessed? It seems to be happening with both Hangouts and the Skype app. I have Reset my phone as well as cleared the data and cache. I am running a rooted Sprint G4. Thanks for any help.
I just got the 1/5/17 beta version of the Google app today (via the play store beta channel). Will work one time for a voice command, then a second voice command will be heard by the app, immediately followed by a hang, then short delay, then force close message. Clearing app data will allow another single successful voice command, followed by the and hear then hang behavior.
Anyone else seeing this behavior?
I have uninstalled updates to run the stock included version (which is behaving fine) to work around the problem for now.
Here's the offending build:
My Google app did similar when I had the recent security update. Try clearing the cache from the app and see if it helps after a reboot. Mine only fixed itself when the app update to a regular (non-beta version).
Someone else said to remove and re-add your google account, although I didn't end up needing to do that.
emailrob said:
My Google app did similar when I had the recent security update. Try clearing the cache from the app and see if it helps after a reboot. Mine only fixed itself when the app update to a regular (non-beta version).
Someone else said to remove and re-add your google account, although I didn't end up needing to do that.
Click to expand...
Click to collapse
Clearing cache didn't help me. Clearing all app data (including cache) reset it so it worked once.
I have a fully functional solution just uninstalling app updates - was just curious if I was the only one having the issue (would point to something in my configuration causing the issue) or if everyone was (indicating a problem with the app)
dandrumheller said:
Clearing cache didn't help me. Clearing all app data (including cache) reset it so it worked once.
I have a fully functional solution just uninstalling app updates - was just curious if I was the only one having the issue (would point to something in my configuration causing the issue) or if everyone was (indicating a problem with the app)
Click to expand...
Click to collapse
Hard to tell. Mine was definitely related to the recent security update - it stopped working right after that.
emailrob said:
Hard to tell. Mine was definitely related to the recent security update - it stopped working right after that.
Click to expand...
Click to collapse
Gotcha. Google beta app updated to 1/9 version yesterday, haven't had a chance to test it yet.
Edit: newest beta (1/9) appears to have resolved the crash issue I was having, and it can also now speak inbound text content in hangouts (that hadn't worked for me for a while).