Related
When turning the phone off and then on, the camera flashes a light several times and it automatically sends previous text messages sent by me to other people again. Why is this hapenning? Can someone please post a solution?? Thanks!
this is actually a known issue
it seems to be a system bug
you can try flashing another ROM, or simply wiping the stock ROM and start from scratch
[Q] issues with SMS resending itself after reboot
I have been having a strange issue recently.
When I reboot my phone, the text messages that I have recently sent are being resent to my contacts, sometimes the messages are resent multiple times. It happens sporadically.
Anyone else have this issue?
Sent from my SGH-T989 using Tapatalk
dbiggss said:
I have been having a strange issue recently.
When I reboot my phone, the text messages that I have recently sent are being resent to my contacts, sometimes the messages are resent multiple times. It happens sporadically.
Anyone else have this issue?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I've never experienced this issue. Are you using a 3rd party SMS app? What rom is this issue happening on?
Sent from my SGH-T989 using xda premium
could be a malware
I work for tmo...change ur simcard..
Sent from my SGH-T989 using XDA Premium App
Are you using handcent? This specific issue is why I quit using handcent. If not, then I dunno, that's weird.
Sent from my SGH-T989 using xda premium
switch and use Go SMS
problem solved
hey! thanks for the reply. I tried flashing some different roms but the issue still persists. even though its not every time i restart my phone, it still happens randomly and its very annoying since people always reply back saying why are u sending me old text messages? So what do you suggest i do? I am currently on TricH's rom. how can i completely wipe the stock rom and start from scratch? please let me know! thanks.
which SMS app are you using?
the stock one that comes with TricH's rom
hmm... probably you might be better off using another ROM or a stock ROM just to see if there's any difference?
i have already tried other roms such as the beast rom but the issue still persist. even when i was on the stock rom, the issue was still there. Do you think there is a way to remove the stock sms app completely from the phone and then maybe i can download a 3rd party app?
i have been having the exact same issue. it started while i was on the stock telus rom, i then switched to the best rom and the issue was still occuring. I am now on the bombardier rom and the issue was gone for a couple of days and now when i restarted the phone, the issue occured again. so i dont know what is causing this problem. if someone knows a fix to this issue please help!
you can use TI to freeze it
Link2SD also has the Frezing option
This was happening to me. I narrowed my problem down to media scan looping, especially if you're getting it on a nandroid restore.
merged both topics, just noticed you 2 and a few other people you also have the exact bug
Had a thought... do you have any texts stored on your sim card?
nope nothing stored on my sim card.
ok so i think I may have found the solution to the issue:
i installed titanium backup pro then used it to backup and freeze the stock messaging app. I then rebooted the phone so the messaging icon disappeared from the phone. I then installed go sms pro from the market and using it as my default sms app. Tried rebooting phone after that and it has not been resending text messages so far.
*fingers crossed* hope this solves the issue for good! will update if issue persists.
Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...
Hi guys, Im the dev of Root Call Blocker, a powerful blocking solution. There have been a few reports of people experiencing issues with the data connection on the S3, which i dont have.
Could someone please let me know if this is indeed the case?
If you do find an issue please follow this procedure:
- as soon as you spot the radio without a data connection (not after a call) send logs through the "Write to us" item in Settings
- once youve sent the report, try using the Debugging tools found in settings
- if the tools do not help, please send another report - this will still help me track issues
Thanks in advance, PR after the break
****************************************************************************************************************************************
Root Call Blocker - the only truly functional call filter
Feeling paranoid? Need privacy? Discretion? Enter Root Call Blocker, the only true call firewall available on Android.
Unlike all other call blocking apps, Root Call Blocker silently blocks calls at a system level. You need not even know its working.
Supported languages: English, Español, Français, Deutsch, Italiano, Ελληνικά, Português, Magyar, Pyccĸий, Українська.
If you want to help translate, visit http://bit.ly/wCgD4j
Advantages:
- A call will never go through
- Your phone never rings
- Reject calls from anyone, including restricted numbers
- Wildcards block groups of callers
- Keep blocked calls and messages hidden
- Five reject methods, including "Don't answer"
- Per-number logging
Features:
- Multiple profiles
- Groups integration
- Exceptions
- SMS auto-replies
- Toggle widget
- Scheduling
- Logging
- In-app replies
- Persistent and event notifications
- Customizable vibrate notifications
- Export from hidden logs
- Low profile
- And much, much more
Debugging
Please follow the instructions in the app's Settings menu to send us logs of your error. Reproduce the error, then send the log.
Market link:
https://market.android.com/details?id=fahrbot.apps.rootcallblocker.beta&feature=search_result
The Trial allows you to block one ITEM. You can use Groups to block multiple contacts.
Screens:
I don't use this app, but your other one, Call Master, instead. On it I had to enable the slow radio start (something like that) when I was using anything other than a Samsung rom. I emphasize Samsung here because I don't use Call Master on a Samsung rom since it has its own call reject built in.
lordmorphous said:
I don't use this app, but your other one, Call Master, instead. On it I had to enable the slow radio start (something like that) when I was using anything other than a Samsung rom. I emphasize Samsung here because I don't use Call Master on a Samsung rom since it has its own call reject built in.
Click to expand...
Click to collapse
Indeed. But Call Master is not just for blocking calls, its for MANAGING CALLS, SMS and MMS. The people who need it understand its value and power.
RCB can be used that way too, to some extent.
I was using this app on this phone and the HTC thunderbolt I had to block my ex girlfriends calls and texts. I would still get texts occasionally and would have calls go through. I'm not trying to bash the app because I liked it over the other few that I used but their interfaces were crap and most didn't even let me have the pick up hangup feature. I stopped using it about 2 weeks ago so I don't know if there have been any updates since then. I know you said people were having trouble on the same but I was also using it with the thunderbolt and having the same issues. If there is a way I can help then by all means let me pm and let me know because I would definitely like to use this app again. I'll reinstall it and see what I can come up with.
Sent from my SAMSUNG-SGH-I747 using xda premium
vegandroid said:
I was using this app on this phone and the HTC thunderbolt I had to block my ex girlfriends calls and texts. I would still get texts occasionally and would have calls go through. I'm not trying to bash the app because I liked it over the other few that I used but their interfaces were crap and most didn't even let me have the pick up hangup feature. I stopped using it about 2 weeks ago so I don't know if there have been any updates since then. I know you said people were having trouble on the same but I was also using it with the thunderbolt and having the same issues. If there is a way I can help then by all means let me pm and let me know because I would definitely like to use this app again. I'll reinstall it and see what I can come up with.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
What is your order number? There is just no way it could let some calls through and block others because the app completely replaces the telephony service.
The issue you describe occurs on pirated copies.
Lets just check:
- you are not blocking its access to the net via a security app
- you have it set to start on boot
- you have only one profile
As i understand, this problem occurred on a different phone? And it works fine now on the s3?
Damn i need this! Sign me up
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
Damn i need this! Sign me up
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
You signed up when you joined this community
Been using RCB since my Cappy. Since then i have had it on my 9100, Note, Gnex.
Been working fine on my CM10-Jellybro SGS3 ATT.
Wish for one thing though, would like to be able to long press the number in my call log and have it added to the black list. That's one thing I miss from running stock TW. (The ability to send number to reject )
Sent from my SAMSUNG-SGH-I747 using xda premium
I have been using this app for about a month on my SIII and I have had no issues at all. I was running CM10 but just recently switched to Kyan ROM. I love this app.
Sent from my SGH-I747M using xda premium
bbgt2 said:
Been using RCB since my Cappy. Since then i have had it on my 9100, Note, Gnex.
Been working fine on my CM10-Jellybro SGS3 ATT.
Wish for one thing though, would like to be able to long press the number in my call log and have it added to the black list. That's one thing I miss from running stock TW. (The ability to send number to reject )
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Not possible im afraid. That sort of thing must be built into the framework. Other apps use a pop-up after every call, but i think thats just crap so itll never happen that way in CM or RCB.
WattB006 said:
I have been using this app for about a month on my SIII and I have had no issues at all. I was running CM10 but just recently switched to Kyan ROM. I love this app.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Interesting how on some cm10 builds it works fine, others not.
1.8.3.21
Fixed issue that lead to intermittent blocking on JB and CM10
Would love to see the block from call log feature described above!
Been using RCB for a couple of months now. It does a great job.
Thanks, however, as I've already said blocking from the call log is impossible.
Sent from my GT-P7500 using Tapatalk 2
That's too bad. No biggie, still a great app. Thanks!
camoto said:
That's too bad. No biggie, still a great app. Thanks!
Click to expand...
Click to collapse
It would require modifications to the framework of your device.
Anything to report?
Galaxy Note
This is perfect app with fast reject function when I use it with rom Rocket, but now its not work with rom ICS 4, could you place fix it. Tks,
Yeah hi. There's nothing to fix, it works perfectly on any rooted device, any android version after 2.1.
Anything to report?
Ever since December 23rd or so, when I first rooted my stock Nexus 5X, Google Messenger has been behaving strangely. Long SMS messages have seemingly random characters attached to the end of them, which do not show up on the sender's end. The most common is a "¿", but occasionally I get a delta ∆ on the end. I cannot find anyone else with this problem either here or elsewhere online. Does anyone have ideas? It's not necessarily a problem, but it is a mysterious inconvenience.
I am running the latest update of Marshmallow (stock ROM), with systemless root (SuperSU 2.61 I believe) and TWRP recovery. Nothing else out of the ordinary. This did only become a problem after rooting my phone, which may be part of the problem. Any help would be appreciated!
Edit: it should be noted that while these are valid characters, they do not appear when searched for with Messenger's built-in search function.
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Broken303 said:
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Click to expand...
Click to collapse
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
OGNatan said:
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
Click to expand...
Click to collapse
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
plwalsh88 said:
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have switched to Textra indefinitely, as this does not solve the problem, but does support many features that Messenger is lacking. If you find a way to submit a bug report, I would be interested in that information
Apologies if I am posting this in the wrong spot. I have a Pixel 2 XL(obviously) and had been on the Android beta program for some time now. The android p beta had been running really solid for me with no issues. So when they pushed it out officially last week i of course went for it. However, all of a sudden now, when *sending* texts, it gives me a notification sound (same as incoming notification). Anyone run into this? I searched the forums briefly but didnt see anyone with the issue although I couldve missed it.
Note- I'm using the Google Messages(I believe thats the official name) app, I just prefer it to Hangouts. I did check the settings, and disabled the setting for outbound notification sounds- but it persists.
Here's the kicker- it cant be isolated to just me, as my mom has the same phone -she messaged me last week and asked if she should update (I'm typically the guinea pig) and I said yep, been rock solid for me.. now she's getting the exact same behavior. So barring it being the messages app itself which i suppose is possible, I dont know.
Thoughts? Suggestions? I havent tried a different messenger app yet, suppose I could(textra maybe), I'm just partial to this one for whatever reason.
Thanks in advance!
Disregard. I guess its specific to Android Messages app. Installed another text app and the issue went no longer occurs.
I have the same issue with my Android Messages app