For the life of me I cannot figure out why this is happening. I have rerooted and re-odin'd froyo countless times and always have the same problem. After a while my texts stop sending, I will go to send a text and it shows a timestamp and says 'sent' then I'll exit messaging and won't receive a response from whoever I'm texting. I open up messaging again and I see the timestamp change to whatever the current time is and says sent, I've noticed if I put the phone down and watch that the sent timestamp changes with the time. The messages never send though, as no one receives them and also it is only with text messages because MMS works fine. Example: I'll send a text at 2:05 pm, I'll look at my phone again in 10 minutes and the text will say 'sent 2:15 pm'. This only happens after a certain amount of time has passed from a new flash, a day, a few days, even have gone a week or so before it starts happening. A data complete data/cache wipe will fix it temporarily, then I have to wipe and start over... Maybe I've been doing something wrong or have been flashing corrupted files?
I've never run into this, but since you say mms works I'd try an alternate mms.apk or try an alternate app such as handcent.
if you want to remain using a stock SMS app look at my previous posts for an alternate mms.apk and instructions on how to replace it over your existing mms.apk from your system/app directory.
if you decide to try handcent and it works whereas your stock SMS app fails, then signs point to the mms.apk.
I'll give it a try, although it seems no matter what sms app I use or no matter what rom I'm using the sms function breaks after a certain amount of time forcing me to do a complete wipe and reinstall/reflash.
so then you are saying you have tried other SMS apps like handcent?
Yes and always the sms breaks after some time :/ idk why but the only fix I have found is a clean wipe.
tapatalked from my KangBanged Fascinate
I want to revive this thread, because the EXACT same thing is happening to me!
Currently running EH03 radio, KGB_FA16 kernel, and Super Clean 3 Milestone 2 on my Fascinate.
The Problem seems to have started on March 28th, and at the time I was still running SC3 Milestone 1. It took me until yesterday to realize that none of my text messages were received by anyone I sent them to since March 28th. Same symptoms; messages appeared to have been sent, time stamp that changes, etc.
Last night I tried a few things to fix the issue:
- Disabled Voodoo and System Lagfixes via CWM
- Wiped Davlik Cache
- Flashed SuperClean 3 Milestone 2
- Updated roaming capability (*228, option 2)
- Just installed GoSMS
In GoSMS, all of the outgoing messages since March 28th have flashing green arrows next to them... What does that mean?
If someone could point me towards the android native mms.apk, I can try re-installing it.
I am running out of ideas... I am going to Odin the EC09 radio tonight and see if that fixes it. Otherwise, the only other option I can think of is to do a full wipe and start over from scratch...
Any thoughts??
Bump.... Thoughts anyone? Beuler?
Should I just bag my whole current config and just try a different ROM!?
Looking into CM7...
Related
Just noticed DCD 4.1 is up on his site. Will probably try it this weekend. Anyone try it yet?
I posted this earlier a couple people have tried it.
http://forum.ppcgeeks.com/showthread.php?p=645219#post645219
testing now 3.59-dcd
Now if only DCD would start posting again, filling us in on his work. You are missed DCD!
Wasn't he banned?
jph8tr said:
Now if only DCD would start posting again, filling us in on his work. You are missed DCD!
Click to expand...
Click to collapse
I agree DCD, and I'm sure a lot of others do too. Post here or somewhere else. If you go somewhere else, leave us some breadcrumbs so we can find you.
I gave it a try, seems to run well. About 23meg on start up. Anyone else?
same here 23 mb on start up - with app. s2u2, GPS, TomTom, call calendar, s2p,and more .....
runs smoth ...thanks DCD
Gonna try this NOW....
SDAutoRun issue?
has anyone else had a problem with UC? this rom seems awesome 27.32mb on clean boot, but UC seems to hang and isnt installing anything. anyone else?
EDIT: nevermind. 1 damn symbol missing from my code.
I'm using this rom now and I don't have any problems yet. I'll post updates if I do.
same here. loving it so far
Were the vouge dialers calc and comm manager removed? They seemed to be when I flashed...
I also had a HUGE text msg problem where it tried to (and did) resend a TON of my unsuccessful texts and from months back...this was just after I did a simple restore with Pim Backup, it never happened on any other release.
My free mem was also less than 3.3.4, and 3.3.4 has 48.25 total whereas 4.1 only has 47.45MB total.
So, I'm still rocking 3.3.4 and loving it. I'll wait till DCD officially releases it as sometimes, he just posts things up there as beta tests for friends.
so heres a new one. my phone just HARD RESET itself. i noticed my text messages didnt have contacts anymore, tried opening my contacts and it said it oculdnt be found. i opened resco explorer to restore my contacts, and it said it couldnt be found. i soft reset the phone and it loaded the calibration screen and went through UC again. ****.
Text messages that have been read show up as NOT being read. I'm using Manila 2d, so I have to scroll through them a few times and they will finally be marked at read. Pretty annoying. I had to flash back to 3.3.4.
Neurom3 did that same thing, plus battery life with Neurom3 is horrible.
I don't see any problems with text messages, I don't see why people are complaining.
a) no one is complaining. just reporting
b) the problem is, every text message must basically be selected in order to save it as read. if you get 2 txts at the same time from 1 person, and open it, the 1st txt received will stay in bold us unread, unless you scroll up with the pad, passed the second text, and let the cursor land on or go above the contact's name. so this also means that if you have a pretty old text message that you never selected, you either have to delete the chain, or scroll up through pages to find your 1 unread text.
kflipproductions said:
a) no one is complaining. just reporting
b) the problem is, every text message must basically be selected in order to save it as read. if you get 2 txts at the same time from 1 person, and open it, the 1st txt received will stay in bold us unread, unless you scroll up with the pad, passed the second text, and let the cursor land on or go above the contact's name. so this also means that if you have a pretty old text message that you never selected, you either have to delete the chain, or scroll up through pages to find your 1 unread text.
Click to expand...
Click to collapse
Hmm, I haven't that problem really, though maybe I just automatically do that. But I have BAD (black hole) reception at my house so if I try and send a text it usually says message not sent, click to try again. So it's never automatically resent texts and this time it was apparently successful sending 50 texts over hours of time - which I didn't know about.
I tried his one from Dec25th but it had the new IE app which I didn't like since I use lots of websites that work nice and fast with older pocket IE. The dialer and connection manager skins were also ugly. Haven't seen those in a long time...
After I flashed the new 4.1.0 ROM, everything seemed to be fine except the number 1 button on the dialer keypad disappeared. Has anyone experienced that? Is there a solution for the problem?
My Gmail has started acting up, and won't let me delete certain emails. I try deleting them on the NC, and the gmail app force closes!
Does anyone know how I can fix the problem?
silivrenion said:
My Gmail has started acting up, and won't let me delete certain emails. I try deleting them on the NC, and the gmail app force closes!
Does anyone know how I can fix the problem?
Click to expand...
Click to collapse
Are you trying to delete archived emails? That's when I had the problem. Had to delete from computer.
I'm trying to delete messages from the inbox. Some messages appear to sync once, but won't sync again ever, so if I try to delete, label, or archive one of these stuck emails, the app either quits or backs up. I can delete them from another device just fine, but those specific emails stay stuck and won't go away.
As a temporary fix, I'm using K9 until I can figure out how to fix it.
I'm having the same problem, rooted stock 1.1. I found that this only happens on emails that are marked as read. So if I mark the message as unread, then I can delete it just fine. This problem only occurs occasionally for me. Doesn't usually cause the app to quit for me, just fails to delete typically.
Hope this helps.
I've found Gmail to be very unstable on 1.1. I've switched to k9 and am happy with it.
I had this exact same problem on my rooted stock 1.1.
The issue did not appear until after I updated CWM from 3.0.0.5 to 3.0.1.0, including installing the kernel with ext2, 3, & 4 support. I was never able to determine with any certainty if the CWM update/kernel had caused the issue because even after restoring to a backup I had made prior to the update it didn't fix things.
I also tried uninstalling gmail and reinstalling it, but that didn't fix it either. I scoured the internet for a solution but couldn't find one. Eventually, I got so fed up that I completely restored to stock and took the opportunity to upgrade to Froyo. The problem did not carry over to Froyo, fortunately.
Nevertheless, this error shouldn't be happening on rooted stock 1.1 and it didn't for me for most of the time I used Eclair, so I'm not advising you to drop Eclair by any means. However, you might want to consider restoring to stock and starting over.
I noticed the same issue. Was not present when booted to Nookie Froyo on an SD card. I'm back to running the stock rooted OS, so I still see this GMail problem.
I'm just waiting for a good SD version of CM7 that has the market and soft keys preinstalled, preferrably that runs like it does on Nookie Froyo.
Anyone ever find a fix for this?
sent from my nook color using tapatalk pro
No, but the good news is that a stable release of CM7 (aka Gingerbread) is nearly upon us. I think pretty soon Eclair and Froyo will be obsolete as far as the Nook goes.
My solution to this was to mark as unread and then delete, the app no longer FCs if I delete that way.
However, not all emails seem to trigger this problem
Hello everyone. I recently ran into a problem, my text messages stopped sending. I am running the latest version of the community rom with the latest OTB kernel from nemesis2all. I have been running this setup since release and have had absolutely no problems. Until today.
Earlier this morning I was texting a couple people as usual. I use chompSMS as my messaging application. Sitting there writing a text when I get the "updates are available" notification from the market. I finish my text and start to update my apps. Everything seems to update just fine so then I reply to another text. It won't send. I try sending it again. No dice. Send like 5 other people a text. Nothing happens, besides "send failed" notifications. All of a sudden I get the crash vibrations and then my phone reboots, and I still can't send texts.
Any help or suggestions would be greatly appreciated. I have had this phone since September and have been flashing roms since before that. I know a pretty good amount of information but have never ran into a problem quite like this.
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
chopper the dog said:
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
Click to expand...
Click to collapse
Yes, the stock app gives me the same errors. I have tried reverting back to an older chomp and that doesn't work either. Everything else works, like calls, 3g data, gps, and I can receive texts. I just cannot send anything. It will try to send for like 5 minutes or so before I get a "send failed".
EDIT:Got it working. Didn't realize TiBu had latest version of chomp. Found an earlier version and everything works as it should. Thanks chopper.
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
It's been a week now and I still can't send any text messages.
I receive msgs but unable to respond back...
I thought it was because I finally updated to Jellybean (I've had ICS for awhile so I thought I should just stick to that) but then I downgraded last night to ICS and I still can't send messages.
well today I tried fixing it but still no luck, although I tried sending an MMS instead, I sent myself a picture and it worked! even tried it to other numbers and they received it. I also tried adding a text with the picture and it did work. but it's still not working when I just type in a text...
so anyway in short, I can't send SMS but can send MMS (and receive messages as well)
also extra: I can call people but whenever they call me it comes up as unknown number...
Does anyone of you know what might be the problem? How can I fix it? Thanks
EDIT: and btw I already checked the message centre number and it has the right number in it so I don't think the issues w/ that
I suggest using titanium backup to store user apps and data, then using mr.cook's rom wipe script to allow you to start from a blank slate, then re-install the desired firmware (whatever version)
You could work at fixing this issue individually, but (to me) it's a sign that something more fundamental went wrong, and that other issues may be soon to follow.
It isn't clear whether you upgraded to a stock jellybean, or maybe a 4.1.2 custom jellybean, or maybe a 4.2.2 custom jellybean, or a 4.3 jellybean. The latter, a 4.3 upgrade from ICS has the highest potential for weird issues if a thorough rom-wipe isn't conducted... whichever path was taken, The i777 runs all versions of jellybean well, and something like this suggests that the "upgrade" was not conducted from a clean slate, hence the suggestion for a rom-wipe and re-install.
-Cyril
can't text
Are you unable to text because a keyboard won't open? My daughter couldn't text (never figured out why - she always had a keyboard appear) so she got a replacement, and when I inherited her phone because mine has battery issues, I go through periods when I can't text because no keyboard appears. I have to into settings and play around with assigning a default keyboard before it will finally appear. Doesn't matter if I'm using the stock keyboard or one I've downloaded from a VERY reliable source - I still have to reassign and reassign and reassign to make it work. Powering off the phone doesn't do a thing.