Related
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
Just a bit of info to pick everyone's brain:
Every time I would open the contacts and try to add a new contact, com.motorola.contacts would f/c.
I kept playing around with it, and when I tried to edit display options it would f/c. I ended up freezing about 10 different apps in Titanium Backup before I found the culprit: Contacts Sync, and now it works perfectly. WEIRD.
btw, I have made a full nandroid backup of my original system, and my phone has 0 bloatware removed. So idk if it's an issue with the stock rom, or me rooting, or what. but there you go. Any input is appreciated
I've got the same issue. I was wondering if I uninstalled a wrong file.
Having the same issue. I thought I tried unfreezing that and rebooted but still would not work. Will try again
Contacts sync is not frozen and I still cannot add contacts. Any other ideas appreciated.
I fixed the issue finally. When you are in Titanium Backup, first make a backup of the contacts sync apk, then convert it to a user app. fixed all my weird contacts issues and it actually still syncs my contacts.
I probably overlooked something when freezing apps, screwed something up. Can't wait for our fxz files!!!!!!!!!!!!!
Thank you for the info. TB won't stop processing it but it started working again.
rockingout92 said:
I fixed the issue finally. When you are in Titanium Backup, first make a backup of the contacts sync apk, then convert it to a user app. fixed all my weird contacts issues and it actually still syncs my contacts.
I probably overlooked something when freezing apps, screwed something up. Can't wait for our fxz files!!!!!!!!!!!!!
Click to expand...
Click to collapse
rock:
I had the same issue along with atquick IIRC. Restored all frozen apps/system with TiBu Pro; plus restored to original backup that was made when first rooted w/ Zedomax using modded Bionic Bootstrap. Nothing would correct FCs. Local VZW was told by Tech Support to replace phone!
http://forum.xda-developers.com/showpost.php?p=20562332&postcount=7
Glad to hear you got your razr working again! Have to think the Bionic Bootstrap/recovery missed something during the backup; but that's just a guess.
FWIW...........
Hey all, sorry if this has been asked, but I have done searches and tried looking thru the forum and cant find an answer... So today after I got sick of my Droid X2 not working properly on stock for months now, I finally went ahead and tried rooting and installing CM7 and this time around (well on my second or third try tonight) I got it installed and working!! Well, working for the most part. So far I am super impressed and enjoying the rom! The one major issue is I cant seem to sync my contacts from Google. I have always been able to in the past on stock and what not, but not on CM7. I get like 3 contacts that were saved to my phone, but everything else is gone. Ive added my gmail account that they were associated with and synched and still no contacts. If anyone could help me out, it would be greatly appreciated!
*Also, just checked my calendar and its working fine... all my info has updated there, but still not my contacts...
This also happened on a friend of mine's x2 when I flashed cm7 for him. Not sure why?
I suspect it had something to do with google not sync the contacts properly before I flashed though, and nothing to do with the rom.
I felt so bad that he had lost all his contacts. I swore then to never flash rom's for anyone else, and I haven't. I just direct them to xda. If I can learn it, then they can too.
O catches my friends 30 to root and rom... did u correctly flash the Google apps thing for aosp roms? Try again with the flashing of Google apps.... but it's just a few numbers...
cyanogen
Edit: I charge my friends....
I had the same exact thing happen to me...
Thanks for all the help... I ended up just staying up for a few hours and re-adding it from Verizons backup assistant. I did a search for the CM7 rom in general (not just for the DX) and some others had the problem and used Verizon to get their contacts back. The sad thing though was there is a file you are able to download from Verizon and put it on your sd card to load your contacts... but I tried and tried and couldnt get it to work. I tried putting the file on the SD, then on the internal and nothing... So I just went thru one by one and added them in myself... heh.
Now my next issue is that my wifi drops out frequently. I have not had the chance to look it up, but was wondering if any of you have had this problem. I am hoping the file was not outdated, as the stuff I put on the phone I got back in January and February. Not sure if there have been updates since then, but I thought I would ask. If anyone has a fix I would greatly appreciate it! Thanks again everyone!
kalojado said:
Thanks for all the help... I ended up just staying up for a few hours and re-adding it from Verizons backup assistant. I did a search for the CM7 rom in general (not just for the DX) and some others had the problem and used Verizon to get their contacts back. The sad thing though was there is a file you are able to download from Verizon and put it on your sd card to load your contacts... but I tried and tried and couldnt get it to work. I tried putting the file on the SD, then on the internal and nothing... So I just went thru one by one and added them in myself... heh.
Now my next issue is that my wifi drops out frequently. I have not had the chance to look it up, but was wondering if any of you have had this problem. I am hoping the file was not outdated, as the stuff I put on the phone I got back in January and February. Not sure if there have been updates since then, but I thought I would ask. If anyone has a fix I would greatly appreciate it! Thanks again everyone!
Click to expand...
Click to collapse
Look it up. Its out there.
cyanogen
Umm. Here u go wifi fix... http://forum.xda-developers.com/showthread.php?p=23029794
cyanogen
king..kranium said:
Look it up. Its out there.
cyanogen
Click to expand...
Click to collapse
I am... been looking thru the forums for the past hour. Sure I will figure it out...
The best way (in my experience) to keep contacts while going from ROM to ROM is to use the import/export feature in the contacts list.
Contacts -> menu button
Select import/export, then export to SD card.
This sends a vCard file to your SD card which you can keep there or backup to an external HDD or computer HDD.
To restore, follow the same instructions and select import from SD card. Select the file and watch all of your contacts come back
Verizon's backup assistant is crap IMO. It's too slow and confusing to navigate efficiently.
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...
I rooted my Note 2 about a year ago, but had left it stock until yesterday. I had wanted to be able to adjust my APN settings and that seemed like as good as time as any to try a rom. I had TB backups that I have been running since I rooted my phone, and made a Nandroid backup in TWRP and then flashed CM11. Had a few hiccups along the way, but eventually got it working. I read the warning about not using TB to restore all system data, but people seemed to ahve success using it in a more limited way to restore just select data, so I tried using it just for contacts...but that didn't restore my contacts and caused other immediate issues. Did some more reading and saw that TB is apparently not good at backing up contacts, just everything else. Standard reply was to use Google to sync contacts, but I don't do that anymore after having problems with it years ago when I first tried an Android phone.
So the other solution I came across for people who hadn't ever synced with Google was to use the Nandroid backup you made before flashing to go back to stock. Get your contacts there and then sync them with Google, export them, or use another app to back them up, and then flash back. So I tried this, but when I restored my Nandroid backup in recovery it restored a factory reset device. I was able to download TB and use it to restore most of my data, so I'm now about 80% of where I was before I flashed...but still no contacts (well actually it restored 1 of my contacts, plus the VZ default contacts). So am I screwed, or is there any other thing to try to get my contacts back?
Screwed.
Use Google, dude. Google has made major leaps in the past few years.
I flash a lot and use tibu a lot. Never ever been able to successfully restore contacts unless from an exported file or from a tibu restore.
You could use that file you exported and import it to Google, maybe?
Thanks. Figured that was the case. Google screwed up my contacts in the same way a couple of years apart the first two times I tried an Android phone. I got a ton of duplicated contacts, a bunch of unrelated contacts were merged, and phone numbers were forgotten. The only way I got everything resorted was by taking my old dumb phone into a Verizon store and after about an hour of playing around they were able to figure out how to get the contacts onto my smart phone. Which is what I guess I will end up doing again. I'll lose the last couple of years worth of new contacts and contact changes, but at least I won't be starting from scratch. Once I do that it looks like I need to make sure to export the contacts and save them as a vcf somewhere off my phone. Maybe even print them out. Oh well, valuable lesson and all that.