just updated to Dorimanx 3.0.0 cLK and everything was working fine, but then my sms messages stopped sending. I was able to send them fine and then poof... every time I send one now it just sits there forever saying "sending...". I can receive them fine, but sending doesn't work at all. I know my APN settings are correct because it was working with these settings for months up until recently ( and I double checked to see if they got changed somehow, they didn't.) I have experienced this a few times before after running on a ROM for a few months and I usually task29, re-install, and then it's fixed but I literally just task29'd and re-installed everything (restored data) last night when I updated to 3.0.0 so this is a totally fresh install.
I tried doing a logcat while sending... absolutely no log output from sms whatsoever. HELP?!?! tried clearing cache and dalvik-cache and rebooting. tried fix_permissions. tried re-installing 3.0.0 on top of my previous install. Nothing seems to fix this "infinite sms sending" bug for me.
Is there a particular cache or data directory that I can clear out to possibly fix this because I really don't want to be wiping my data on my phone and restoring all the time just to make my sms let me send for a little while.
nobody has seen this before?
I have a similar problem running Typhoon CM7 3.7.5, but only with MMS. It will attempt to send for hours with full data connection, but never does. Will not download them either.
brunality said:
I have a similar problem running Typhoon CM7 3.7.5, but only with MMS. It will attempt to send for hours with full data connection, but never does. Will not download them either.
Click to expand...
Click to collapse
When sms was working for me I could send mms messages no problem. I think this must be some sort of bug in the mms.apk from cm7 because it's happened several times for me and every time the only way to remedy it is a full system wipe (which I literally just did less than 24 hours before the sms issue happened to me the last time.)
I find that if a txt fails to send, it will never send, regardless of the retry timer, and I must resend it as a fwd.
Related
Hello,
I have strange behavior every time my Hero connects to internet (via Wi-Fi and also 3G) -> I'm getting "com.htc.provider" crash... After this exception everything seems to be working (Exchange mail push, weather updates, google talk) but this happens every time the phone connects to the network (for example to check the mail).
I'm running Modaco's latest ROM.
Anyone had this problem? Found a solution?
Thanks,
Darky
I had that problem when I first applied the 2.0 Modaco ROM. I had done a factory reset to wipe it.
I tried a second time, using the recovery image to wipe the data and then applied the ROM again. That seemed to have fixed the issue.
Hope that helps.
Thanks.. So you think this is a matter of wiping the info before? Will it also erase custom applications, locale settings?
The wipe removes all data related to applications and set up so you lose everything you may have customized. Some things have changed under the new ROM so some of the data formats aren't compatible anyway (unless you want to hack your data files). The "com.htc.provider" issue seemed to have been related but I couldn't be sure. I just noted that doing the recovery ROM wipe and a re-install of the new ROM cleared the error - which was a very annoying error when connecting via WiFi (or disconnecting).
YMMV.
Thanks... Did "wipe" and upgraded to latest Modaco ROM - now it is perfect
I did a wipe from the rescue menu and re-installed this morning but I'm still getting the com.htc.provider error! I'm reluctant to try again immediately as I had a lot of set up done before the error re-surfaced. Has anyone any suggestions? Should I wipe the sd card too?
There's a suggestion on androidforums.com that it might be something to do with twitter (see here) but my friend has a Hero (with RUU ROM) and he's not getting the error!
http://forum.xda-developers.com/showthread.php?t=563684
enlightener said:
http://forum.xda-developers.com/showthread.php?t=563684
Click to expand...
Click to collapse
Thanks enlightener! Guess I'll just live without the twitter widget for the time being!
I am running Cyanogenmod 5.0.8 on a T-Mobile Mytouch3G (I tried upgrading twice to CM 6.0.0 but due to issues (lots of Force Quits due to running out of memory - I did not try swapping), went back to Android 2.1).
After running into the issue where creating a new folder would generate a Force Quit (ACore) message, I followed the advice here of running su -> fix_permissions which did solve that issue. However, it created the issue where the Phone Lock (i.e. slide to unlock) no longer appears. It also reset several passwords but that is manageable and also reset my Android Market list so it thinks my downloads were not installed, which was also manageable.
I have tried other lock programs (Lock 2.0, myLock) from Android Market but they don't always work.
I'd greatly appreciate suggestions on how to fix this problem.
Thank you
You can try reflashing CM without a wipe.
Sent from my HTC Magic using XDA App
I tried that but ended up having lots of issues with my phone so I restored my Nandroid backup. I may try flashing it again sometime in the near future.
I encountered further problems with my phone last week, especially with no missed call messages or flashing LEDs being displayed when I missed several calls one evening.
After using multiple backup utilities (just in case) to backup all of my call logs, SMS, MMS, Applications and Data, I dropped into Nandroid last night and did a full user data wipe along with the Cache and Battery Status. (It was a good thing I had used multiple utilities as the first program I tried couldn't find my backup after the install).
I then updated to CyanogenMod 6.0.0 and Gapps-tiny 09302010 and downloaded fresh copies of my applications (moving them to the SD Card where possible) and restored my backups. After completing that, I was pleased to note that the phone lock was restored along with the missed call LED and title bar notifications.
Running nightlies on Sprint GS4. Been happening on multiple nightlies going back for some time. Currently running 6/18 Nightly
Voicemail crashes every time I try to open it with the 'Blame Split Screen' message. Cleared data and forced stopped. When I started again I got the 9016 text saying vm successfully provisioned, but it still crashes. Sometimes it says up long enough for me to see the message about verifying your account
Calls are going to VM and I get the //ANDROID text when a VM is left.
Doesn't seem to matter whether WiFi or hotspot are off/on.
tryanDLS said:
Running nightlies on Sprint GS4. Been happening on multiple nightlies going back for some time. Currently running 6/18 Nightly
Voicemail crashes every time I try to open it with the 'Blame Split Screen' message. Cleared data and forced stopped. When I started again I got the 9016 text saying vm successfully provisioned, but it still crashes. Sometimes it says up long enough for me to see the message about verifying your account
Calls are going to VM and I get the //ANDROID text when a VM is left.
Doesn't seem to matter whether WiFi or hotspot are off/on.
Click to expand...
Click to collapse
Have you wiped cache and dalvik cache? If that doesn't work try a factory reset. But remember to bakup things if you need.
Hit thanks if i helped :good:
vinc10 said:
Have you wiped cache and dalvik cache? If that doesn't work try a factory reset. But remember to bakup things if you need.
Hit thanks if i helped :good:
Click to expand...
Click to collapse
Always wipe cache & dalvik when flashing nitelies - doesn't fix the problem.
This weekend I went all the way and factory reset and flashed new nightly and 4.4 Gapps - still broken
tryanDLS said:
Always wipe cache & dalvik when flashing nitelies - doesn't fix the problem.
This weekend I went all the way and factory reset and flashed new nightly and 4.4 Gapps - still broken
Click to expand...
Click to collapse
Try different gapps
Sent from my Nexus 4 using Tapatalk
Recently I get this error when I refresh email stock app.
A. Wasn't happening before
B. Can't see any reason why it started happen
C. Doesn't happen while connected with wifi. Only mobile data.
D. All other apps perform normally. Only the email app stucks
E. I updated to latest version of 4.4.2 kitkat but no fix
F. I am rooted.
Any clues what the heck is going on???
awarexda said:
Recently I get this error when I refresh email stock app.
A. Wasn't happening before
B. Can't see any reason why it started happen
C. Doesn't happen while connected with wifi. Only mobile data.
D. All other apps perform normally. Only the email app stucks
E. I updated to latest version of 4.4.2 kitkat but no fix
F. I am rooted.
Any clues what the heck is going on???
Click to expand...
Click to collapse
By any chance do you have a proxy set on your APN's? Jot it down and erase it, including the port number.
If you have normal internet working - then it must be a problem APN-wise.
You can isolate it down to the hosts file, but if you use apps like Adfree or ad blocking software, then it really eliminates it down to your APN settings. For ad blocking software to work, proxy and port number must be removed. Try placing a proxy back if it's gone.
Thanks for the answer.
I have no clue what to do reading and rereading your post...
It's too technical
Update
This happens only when i press the refresh button on the widget. And only on mobile data.
Solved by wipe data.
However this wiped all sdcard contents
Really bad.
The wipe data also fixed a problem I had with delivery reports not working.
Although enabled both on stock app and gosms.
But but but...
...after some days the delivery reports again stopped working.
So please I have read one million posts about this delivery report issue.
Can you help and suggest any fixes?
Thanks
I also have the problem with the SMS delivery report.
Still don't know how to fix?
No luck no fix yet.
What device you have?
Android version?
I have gosms and mightytext apps that may be messing
Do you have any of those apps?
Only by diagnosis we may reach something
My device is N9005, stock 4.3.
I don't have GoSMS nor mightytext app, but I have installed HushSMS and also the its Xposed module.
I'm not sure if it may cause the 'SMS delivery report' problem. Tried to uninstall HushSMS and its Xposed module but the problem still persist.
I think factory reset may help (as I don't have the problem when I first bought the phone), but I don't want to factory reset
Factory reset will not help
For me it fixed it for a couple of days only
Nobody jumps into this thread
Which means that from millions of note 3 devices we are just a few with this issue ?
Most people don't have the sms delivery report enabled.
(the majority of western-world mobile users doesn't use sms altogether anymore.)
Check with your service provider, there may be a network related issue.
And does the problem also persist if after a reset you don't install any apps, particularly sms ones?
Sent from my SM-N9005 using Tapatalk 2
It worked after factory reset until I enabled mightytext app.
The app was restored with titanium backup but not set up yet.
After I set it up and used it then no delivery reports anymore
Coincidence? who knows
Of course I uninstalled mightytext but the delivery reports still were not working
I recently switched from AOSPA after not being particularly impressed and went back to oxygen. However, after attempting to send a message I was unable to send one and noticed that I also am unable to receive. Phone calls and cellular data seems to work perfectly. I have flashed the proper firmware and reflashed the OS several times, but for no avail. I've also tried to clear cache l, but still no luck. I haven't been able to test the SIM card on another phone yet, but as the problem started as I switched OS I doubt that the problem lies there.
Some weird things I've noticed:
- Both Facebook and Google Messenger refuse to even attempt at sending a message, whereas textra pretends nothing is wrong
- In gsam battery monitor the phone line is greyed out
- Right after boot a message saying there is no service appears, but disappears fairly quickly.
Thanks in advance!
And this is after clean flash? Also without trying to restore any data using Titanium backup or other?
Clean flash, but I did use titanium backup. Guess that could be the cause. Seems like I'll have to do another clean flash anyway.