i stopped getting inbound texts yesterday afternoon about this time
im rooted but i have been for days and backed up but tryin to see if anyone has any ideas before i rom reboot
Are you using SwiftKey? I was having the same problem, so I started doing some trials with getting rid of apps to see if there was one that was causing it.
So far I believe SwiftKey was the big issue, since I haven't had the problem since I stopped using it, and the problem came up only about 12 hours after doing a fresh flash and only having installed that app. I wasn't even rooted...
If you're not using it though, I'm not entirely sure...
i just rom flashed it to 2 days ago so its all better
just odd lol
thanks for the help though
Related
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
neonflash said:
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
Click to expand...
Click to collapse
The most likely issue is the fact that it is running a dual boot and your SD card is messing up. I never advise dual booting as things like this can happen. I would reflash a stock rom. Then go from there. Also might find more help in the captivate section.
Thread closed
Sent from my SGH-I777 using Tapatalk 2
Starting today, my phone has been giving me notifications about a sign in error to my Google account. It's happened about 5 times so far, all just today. My phone is completely stock. Is anyone else experiencing this issue? Are Google servers having some issues?
I think Google was having problems this morning. Maybe they still are.
Sent from my ADR6300 using xda app-developers app
Okay thank you
Same here. I just flashed the latest Cyanogen mod nightly so I thought it was the ROM.
Sent from my SCH-I535 using xda app-developers app
Been getting that error like crazy today. I'm guessing it's cleared up though? Haven't seen it in a minute..
Just started getting it a few hours ago, completely stock.
I wonder if they're just making system wide changes in waves, you guys are getting the errors much later than me, I haven't gotten one in hours now
I am getting as well yesterday and today with 2 different ROMs so I believe its a Google issue
Confirming as well, just got one to be exact
I've been getting the log in error periodically for over a day now
It's been happening to me since last night, and I'm on a completely different phone. In searching for a solution that DIDN'T involve starting from scratch by reflashing a ROM (literally hours of work to retweak and restore everything, titanium backup and all) I found another thread regarding this issue on a totally different phone forum of xda.
I myself am running Now for ICS on my One S running Viper Rom. From this thread, with no details given I can only assume most of you are using Verizon galaxy S 3s?
But anyways. In the other thread it seemed the consensus that the issues were related to Google now. Some users reported some success from logging out of their Google plus then logging back in again. That resolution has provided me no dice so far.
Most users reporting the issue said that their google now was even not working at all. Have any of you tried google now while encountering these issues? Does it work or does it seem to be malfunctioning? Mine (along with the rest of my google apps) all seem to be working fine still. =L
Is anyone on here using a phone other than the Verizon GS3? what roms are involved? Anyone encountering this issue NOT have google now installed to their phone?
Hoping to narrow the details down in the interest of gaining a little more knowledge about this specific occurrence.
This happened to me a couple months ago, and I was running GNow for ICS back then too. Can't remember but I'm fairly certain the issue worked itself out. But its obnoxious ass all hell. Been getting the notification once every 5 minutes whenever I dismiss it, and its been prevalent since last night! It's starting to severely irritate me lol.
Sent from my HTC One S using xda premium
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
FIXED!!! (for me at least)
boojay said:
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
Click to expand...
Click to collapse
Tell me about it. Im seriously starting to lose my sanity over this.
A couple users said to disable Google Account manager (via settings > apps) as a temporary solution, but for me doing so disabled all of my g apps entirely so that's definitely not a good work around.
I spotted a thread in the amaze forum involving a speedrom issue (http://forum.xda-developers.com/showthread.php?t=1968141) and he seemed to think it was related to his Rom. Seemed that doing what he did resolved it, but given the prevalence of this issue accross as many devices as it has and as many roms as it has, I'm inclined to think that the issue coincidentally resolved itself while he was busy flashing lol
Regardless... I'm so desperate to stop being pestered by this issue that imma bout to wipe cache and dalvik cache and see I'd that doesn't fix the issue for me as well. I'll report back when I know one way or the other.
Edit - cache and dalvik cache wiped. Crossing my fingers. Only time will tell... Or not. Got the error whilst I was writing this paragraph lol. No dice
Edit 2 - interesting. I've had the sports card running for a couple days now. It kinda updated but didnt seem to be working 100%. Whether its related or not, im not sure but simultaneous to this behavior I noticed that the search function didn't work. Didn't open chrome up at all so I'd simply have to type my search into chrome directly. I just disabled the sports card and my search function is working again all of a sudden. Haven't gotten the error yet, if this pans out that might have been the source of my problem. Keeping my fingers crossed.
Edit 3 FIXED!!!!! (for me at least). It's now been an hour and 35 minutes since I disabled the sports card. My now search has been working for the first time in days since the instant I disabled it and the error free hour and 35 minutes is by far the longest span of time I've achieved in the last 24 hours (was getting the error within 5-10 minutes of each time I dismissed it previously). Anyone else encountering this issue have the Sports card enabled? Try it, see if it solves the issue for you as well and share with the class =)
Edit 4 - I guess it was a passing moment nonetheless. Got more errors.in the last 15 minutes after about 2 and 1/2 hours of not seeing it at all. Damn this is effing ridiculous
Sent from my HTC One S using xda premium
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
boojay said:
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
I just went into the phone settings then account. Removed my gmail account then resign in and I have got the error all night
Sent from my SCH-I535 using xda premium
AndroidAutobot said:
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
boojay said:
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yep. It's been gone all day for me. At least it was persistently annoying enough this time around to actually remember that it.resolved.itself.I'd.there's ever a next time this comes up. Knocking on wood that It won't ever again of course =)
Sent from my HTC One S using xda premium
Hey guys!
It's been a while since i visited these boards. Sadly I'm faced with a problem that may make me go back to some stock 2.3.3 ROM.
I've got the CM10 on my P500, used it for months, was quite happy with it (tho didn't really play around much with it).
Well, untill around 2 weeks ago when my phone stopped playing ringtones, making me miss calls when i was sitting right next to it. Quite annoying, tried changing all known setting that could cause this. It did vibrate on vibrate-only mode, except for that no results.
Finally today I got fed up with things, restored default settings and behold, now the phone doesn't even display incoming calls. Though they do show up later in missed calls. All of this is crazy :silly:
So, my questions are. Did anybody else get this problem? Any new version of the ROM or patch to fix this? Should I just find myself some old sure-proof ROM, cause I don't even play around with all the new 4.1.2 toys?
Anyways, I'm awaiting your replies. Thanks a bunch in advance.
Cheers fellas!
Hi! Until yesterday i was using Bytecode's ParanoidDroid 3.15 (nice JB 4.2 rom, thanks Bytecode!!!). Couple of days ago i had a ringtone problem also: the phone begin to ring, but only for a second, and then stopped (i keep my ringtones on my sdcard). I don't know the solution because i switched roms - for that bug and speaker bug - searching for a stable one. Now i'm testing 4.0.4 ICSPlus, and hope to be the "right" one.
Same prob.
scholarTD said:
Hey guys!
It's been a while since i visited these boards. Sadly I'm faced with a problem that may make me go back to some stock 2.3.3 ROM.
I've got the CM10 on my P500, used it for months, was quite happy with it (tho didn't really play around much with it).
Well, untill around 2 weeks ago when my phone stopped playing ringtones, making me miss calls when i was sitting right next to it. Quite annoying, tried changing all known setting that could cause this. It did vibrate on vibrate-only mode, except for that no results.
Finally today I got fed up with things, restored default settings and behold, now the phone doesn't even display incoming calls. Though they do show up later in missed calls. All of this is crazy :silly:
So, my questions are. Did anybody else get this problem? Any new version of the ROM or patch to fix this? Should I just find myself some old sure-proof ROM, cause I don't even play around with all the new 4.1.2 toys?
Anyways, I'm awaiting your replies. Thanks a bunch in advance.
Cheers fellas!
Click to expand...
Click to collapse
Hi there. Actually i have this problem too. I flashed Rashed's cm10 about two days ago and when somebody calls me it doesn't ring. I thought that the problem was my phone, but now if there are more people with that problem I don't know what to think anymore..
me and my girlfriend both own nexus 5's. today i got a force close message while using instagram, then later my gf said the same thing was happening to hers. afterwards it started doing it much more frequently. it doesnt seem to be doing it as much now, but it was pretty darn annoying. i was just wondering if anyone else has had the same issue lately? im on xposed + franco kernel, but my lady is all stock. i was wondering if maybe the new camera update could be causing it but im just grabbing at straws.
Crashed just a moment ago after I posted an image. Can't say that happens often. I'm on stock 4.4.2
yeah..it is crashing here and then
satanisneat said:
me and my girlfriend both own nexus 5's. today i got a force close message while using instagram, then later my gf said the same thing was happening to hers. afterwards it started doing it much more frequently. it doesnt seem to be doing it as much now, but it was pretty darn annoying. i was just wondering if anyone else has had the same issue lately? im on xposed + franco kernel, but my lady is all stock. i was wondering if maybe the new camera update could be causing it but im just grabbing at straws.
Click to expand...
Click to collapse
Couple of people in Slimkat's thread posted they're having issues with it, possible it is the new camera app yes. I tested mine and it's all good (so far at least)
Mine crashes a few seconds after opening it
i actually uninstalled the new camera app and it reverted to the version prior to the update. and it would still crash without the newest camera apk.