I've been running CM6.1 for about 4 weeks and hadn't had any problems until a week ago when, for 36 hours, I wasn't receiving any sms/mms messgaes. I was able to send them just fine and calls were fine also.
I wiped the phone and then everything was fine for a few days. It happened again and I wiped again. Simple reboots never helped.
Long story short...
I experimented and cleared the dalvik cache when this happened for the second time today and that fixed it. The problem returned tonight and clearing the dalvik fixed it again.
At the same time when I can't receive texts, I also don't get notifications from gmail or from WordFeud.
Any ideas what's going on? Seems to be directly related to dalvik.
This happens on CM6.1 and 6.1.1 using the most up to date gapps direct from CM site.
Thanks in advance for the input.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Related
This is probably going to get confusing, but I'll try to keep everything clear...
I installed Chiefz 2.1 Build onto my Slide. I used it for a week, customized it, and then CM6 final was released on 8/28. I backed up my phone with nandroid, and then wiped the cache and data and flashed CM6.
I used CM6 for a week. I realized after a couple of days that I was not receiving google talk messages on my phone. If I logged into GMAIL and looked at CHATS, I would see all of the messages people were sending, and I just wasn't receiving them. I cleared GMAIL, and Google Talk cache on the phone, but this still didn't fix it.
I figured I'd post and see what people thought, but I just bought a new car which has bluetooth built in for calls and A2DP to stream music from my phone. I tried doing this on CM6 and it didn't work. I looked it up, and it is because bluetooth isn't supported in CM6. So, I backed up CM6 using nandroid, and then restored the backup I had done of Chiefz 2.1 build. Bluetooth works perfectly, but I still can't receive Google Talk messages. I cleared Talk, Gmail, and Gmail storage on the phone, but they still aren't being delivered. Also, peep is not updating...it keeps saying that my phone is refreshed, and if I refresh tweets it will say updated, but the last tweet I see is the last one I saw before I backed up using nandroid the first time...coincidentally it is Cyanogen saying that CM6 is done baking in the oven.
I cleared the cache for Peep, and it still wouldn't update. So, I booted back into nandroid this morning after 2 days of not receiving Google Talk or Twitter, wiped data and cache, and restored the backup again. Same issue still exists.
Why did this happen? I used nandroid backup so I wouldn't have to wipe, load fresh roms, and then customize all over again...
Code3VW said:
This is probably going to get confusing, but I'll try to keep everything clear...
I installed Chiefz 2.1 Build onto my Slide. I used it for a week, customized it, and then CM6 final was released on 8/28. I backed up my phone with nandroid, and then wiped the cache and data and flashed CM6.
I used CM6 for a week. I realized after a couple of days that I was not receiving google talk messages on my phone. If I logged into GMAIL and looked at CHATS, I would see all of the messages people were sending, and I just wasn't receiving them. I cleared GMAIL, and Google Talk cache on the phone, but this still didn't fix it.
I figured I'd post and see what people thought, but I just bought a new car which has bluetooth built in for calls and A2DP to stream music from my phone. I tried doing this on CM6 and it didn't work. I looked it up, and it is because bluetooth isn't supported in CM6. So, I backed up CM6 using nandroid, and then restored the backup I had done of Chiefz 2.1 build. Bluetooth works perfectly, but I still can't receive Google Talk messages. I cleared Talk, Gmail, and Gmail storage on the phone, but they still aren't being delivered. Also, peep is not updating...it keeps saying that my phone is refreshed, and if I refresh tweets it will say updated, but the last tweet I see is the last one I saw before I backed up using nandroid the first time...coincidentally it is Cyanogen saying that CM6 is done baking in the oven.
I cleared the cache for Peep, and it still wouldn't update. So, I booted back into nandroid this morning after 2 days of not receiving Google Talk or Twitter, wiped data and cache, and restored the backup again. Same issue still exists.
Why did this happen? I used nandroid backup so I wouldn't have to wipe, load fresh roms, and then customize all over again...
Click to expand...
Click to collapse
First, Peep isn't working for anybody. T-Mobile is working on it.
Second, your nandroid backup appears to be working just fine.
HebrewToYou said:
First, Peep isn't working for anybody. T-Mobile is working on it.
Second, your nandroid backup appears to be working just fine.
Click to expand...
Click to collapse
Oh.
What about google talk? Is this broken for everyone too?
how is this a nandroid issue and why is this in the wrong section?
Sent from my T-Mobile myTouch 3G Slide using XDA App
stoneyjonez said:
how is this a nandroid issue and why is this in the wrong section?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You are not a moderator, so stop acting like one.
Google talk and tweet worked before the nandroid backup and restore, and both broke afterwards. Tweet appears to be a T-Mobile issue, and I'm trying to verify, at this point, that Google talk is as well. Otherwise, it is still a nandroid issue since that is the only change to my phone. Backup with nandroid, flashed a different rom, wipe, and restored with nandroid.
Voicemail notification wont go away.. running myns rls 3 wiped data cache installed rls 4 still pops up saying i have 5 voicemails but if you call it says you have none? What is going on? Is there a fix?
And i even cleared vm notifications in settings. Thanks
Sent from my PC36100 using XDA App
this is funny. there was just another post the other day about this same problem. he had just installed myns 4 and was getting the vm notice thing. i advised him to wipe system dalvik and cache. then i suggested that he completely remove vm, he wasnt going to use it at all. he said that he was going to do a full wipe of everything and then reflash the rom. he hasnt posted anything. so i just assume that it worked.
Not to sound like an ass but did you do the update for the VM? I just want to make sure all the bases are covered cause you never know.
i keep getting this error message every few days. its very frustrating. i exchanged the phone and its happening on the new phone as well. any know why this is happening?
raultsu said:
i keep getting this error message every few days. its very frustrating. i exchanged the phone and its happening on the new phone as well. any know why this is happening?
Click to expand...
Click to collapse
I'm having the same issue. My wife and I got matching Galaxy S3s on Black Friday. Mine has been flawless, but hers does this on a daily basis. Just before the 30 days, we exchanged it for a new one (that came with a later ATT release). Same problem.
I had rooted mine the day I got it, so I tried rooting hers and put Holo launcher on it (just like mine). Then I wiped cache, dalvik, and fixed permissions. I also went through her contacts and deleted quite a few older ones (but I have three times as many contacts as she does. )This seemed to work for about a week. Then contacts started crashing again every few days. Now it's every day again. Usually requires a reboot. Clearing cache on contacts and contacts storage does not help at all.
She keeps asking when she can go back to an iphone because of this issue. Any ideas?
To review: Things that DID NOT WORK:
Clear contacts cache
Clear contacts storage cache
Reduce number of Google contacts
Clear cach partition
Clear Dalvik cache
Fix Permissions
patrokov said:
I'm having the same issue. My wife and I got matching Galaxy S3s on Black Friday. Mine has been flawless, but hers does this on a daily basis. Just before the 30 days, we exchanged it for a new one (that came with a later ATT release). Same problem.
I had rooted mine the day I got it, so I tried rooting hers and put Holo launcher on it (just like mine). Then I wiped cache, dalvik, and fixed permissions. I also went through her contacts and deleted quite a few older ones (but I have three times as many contacts as she does. )This seemed to work for about a week. Then contacts started crashing again every few days. Now it's every day again. Usually requires a reboot. Clearing cache on contacts and contacts storage does not help at all.
She keeps asking when she can go back to an iphone because of this issue. Any ideas?
To review: Things that DID NOT WORK:
Clear contacts cache
Clear contacts storage cache
Reduce number of Google contacts
Clear cach partition
Clear Dalvik cache
Fix Permissions
Click to expand...
Click to collapse
Hmm... Are you sure it's not something that is attempting to sync with your contacts that is causing the crash?
patrokov said:
I'm having the same issue. My wife and I got matching Galaxy S3s on Black Friday. Mine has been flawless, but hers does this on a daily basis. Just before the 30 days, we exchanged it for a new one (that came with a later ATT release). Same problem.
I had rooted mine the day I got it, so I tried rooting hers and put Holo launcher on it (just like mine). Then I wiped cache, dalvik, and fixed permissions. I also went through her contacts and deleted quite a few older ones (but I have three times as many contacts as she does. )This seemed to work for about a week. Then contacts started crashing again every few days. Now it's every day again. Usually requires a reboot. Clearing cache on contacts and contacts storage does not help at all.
She keeps asking when she can go back to an iphone because of this issue. Any ideas?
To review: Things that DID NOT WORK:
Clear contacts cache
Clear contacts storage cache
Reduce number of Google contacts
Clear cach partition
Clear Dalvik cache
Fix Permissions
Click to expand...
Click to collapse
Bad flash.
Wipe everything, format system, and do a clean flash.
That should fix it
Sent from my SGH-I747 using xda premium
laserlight959 said:
Hmm... Are you sure it's not something that is attempting to sync with your contacts that is causing the crash?
Click to expand...
Click to collapse
Do you have ideas how to check? or what to look for?
gravedigger76 said:
Bad flash.
Wipe everything, format system, and do a clean flash.
That should fix it
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'd be inclined to agree with you except that it happened right out of the box, with two different phones.
I just had this happen out of nowhere on a clean install of CM9. I've looked around a bit and this seems to be occurring on stock, rooted, and flashed phones of all different types. I'd say it's some kind of ICS issue that hasn't been investigated enough to get a clear solution.
It's also strange that the issue was not occurring when I created my Nandroid, but even after wiping data/etc and then doing a clean reflash if I restore that Nandroid the issue starts happening.
Hi all, first post, I searched and searched and couldn't find anything, so I'm making a new post.
Ever since about a day ago, I haven't been getting sms messages. people have been saying they've been trying to text me all day, and I just sent myself a text thru email using @vmobl.com and I haven't gotten any texts. I used to get this problem with my old Optimus V on Virgin as well, and the way I would fix it is turning it off and removing the battery and all the texts would appear when I started the phone back up, but obviously the one v doesn't have a removable battery, so I can't quite do that. My notification light is going off, but the only thing I have in my notifications is voicemail, and it's never blinked for me before for that
I've tried restarting, turning it off and leaving it for 5 minutes, cycling airplane mode, and booting into cwm and erasing cache. It's a CDMA Virgin Mobile phone, running shubhamchamaria's non-sense ROM v1.1 I use ChompSMS for my main client, but I also have the AOSP messaging client installed which came with the ROM.
I'm probably going to make a nandroid and return to factory settings and see if that works, but I want to know if there's anything else I can try. Thanks!
EDIT: see final reply, I got the problem fixed by reflashing my nandroid of the factory settings, after that I flashed a new rom and texting still works. Thanks for reading everyone
hmm, i had that happen to me before but it fixed the problem after i cleared the cache. i have no idea if it will make a difference, but try Go SMS Pro...? i'm skeptical that it's the text app, though.
jetfactor said:
hmm, i had that happen to me before but it fixed the problem after i cleared the cache. i have no idea if it will make a difference, but try Go SMS Pro...? i'm skeptical that it's the text app, though.
Click to expand...
Click to collapse
Thanks for the suggestions, clearing the cache didn't work, I cleared dalvik and regular caches, but still not getting messages. I did try GoSMS, but that didn't help either, I'm gonna try restoring to factory settings and see if that helps
I restored my phone to factory settings and it started receiving texts again, I've since flashed the paranoid android rom and it's still working just fine, thanks for reading everyone!
I'm rooted with Bonestock Rom. I noticed that I can receive email (Google account) but I cannot send.The email just stays in outbox. I tried turning mobile data off and on even my WiFi.But no go. I have my company email setup with the phone and that works fine.Is anyone else experiencing the same issue?
I haven't run into this with the One, but with my GNEX when I was a flash o holic it happened quite often. I would wipe data, cache, and delvik cache as well then refresh the rom. Also sometimes it helped to download the Gmail app from the market rather than restore a back up of it.
Sent from the One and Only
I personally prefer using live mail, but clearing cache sounds like it will probably help, also just simply restarting your phone can help with a lot of stuff. My text messages were taking 15 minutes to send and receive, simple restart fixed that.