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
Related
I'm on 1.1 pre-rooted ROM and my gmail was working OK but somehow today it stops syncing and if i manually refresh inbox it just closes. I tried clear data but no luck. Does anyone know how to fix?
Many thanks!
Sent from my LogicPD Zoom2 using Tapatalk
Ditto, Jiang. My gmail started acting flaky last night. Crashes anytime i hit refresh inbox; randomly closes whatever message i happen to be viewing or composing; and reverts to previous viewers message when refresh does happen to work.
Afraid to wipe data with titanium for fear of even bigger probe
Any takers?
Same here. Subscribed.
Sent from my PC36100 using XDA App
I have had this issue since I upgraded. I have tried clearing data, uninstalling and reinstalling, even restored a nandroid of 1.0.1 and then reflashing 1.1.0. Nothing has helped so far. Hopefully somebody else comes up with a solution...I don’t really like L8 which is what I have switched to at this point.
I have the same problem. Started when I upgraded.
Same issue. New NC with 1.0.1, used autonooter. Gmail worked fine. Then flashed pre-rooted 1.1. Gmail flaked out.
Same problem here. Gmail just started flaking yesterday afternoon after working fine for a week.
On 1.1 rooted with unofficial AN3.0.
I tried wiping data for all gapps in tibu, also tried adding same account again... all other gapps working fine.
Getting FC's when hitting Archive, and Gmail wont sync at all.
Same here, since the 1.1 r2 update, FC on open, even after data wipe.
Had the same problem with Reader, and "un install / re install" fixed it, but I'm not sure it can be done without any consequences with the gmail apps (wouldn't the google account be wiped as well causing problems?)
I use K-9 mail for now, but I'd like to get gmail running again...
Has anyone found a fix for this? My Gmail is totally hosed up and useless at this point... which just plain sucks!
I've tried reflashing all of the 1.1 gapps using CWM, then wiping data for both the Gmail app and gmail storage app, and then finall deleting the apk and replacing it via adb... but, nothing works! FC's whenever I try to archive or refresh, and shows inbox from two weeks ago... Uhgg!
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...
hi all I am posting this as an "official" question in this section because it's a known issue and it's not been resolved. this issue was briefly (and by that I mean "very few replies") discussed in this thread: http://forum.xda-developers.com/showthread.php?t=1055407
I am wondering if anyone has come up with a solution or some more hints.
to sum things up:
- in a threaded sms conversation, upon sending AND receiving a message the small contact pictures (both yours and your interlocutors') flash one time (like if they were reloading: you can briefly see the grey android default "no picture" icon meanwhile). this didnt happen on elder builds, and when it happens the phone lags.
- it can happen from time to time that after this strange reloading the pictures won't load anymore and immediately after this, the app will loose sync with contact names too: you'll end with phone numbers anymore like if you had an empty phonebook.
I have found the culprit to be not the messaging app but the contacts app. when this happen, i "just" need to go back to home and tap the contacts app. sometimes it just displays a black screen, sometimes i get a FC message about com.android.process.acore. after pressing the FC button the app will restart and both contacts and messaging will return working normally (although still with the weird reloading thingy).
as far as things go it seems that
- hard resetting / wiping data does not help
- removing and re-adding the google account sync does not help
- it happens on 354 too
- not all users (very few, it seems) are affected by this
- there is no weird backup & restore voodoo procedure implied in the affected streaks
the small amount of users affected by this issue leads me to think we are, in some way, doing something wrong. any help would be greatly appreciated really. thanks in advance folks.
crashDebug said:
hi all I am posting this as an "official" question in this section because it's a known issue and it's not been resolved. this issue was briefly (and by that I mean "very few replies") discussed in this thread: http://forum.xda-developers.com/showthread.php?t=1055407
I am wondering if anyone has come up with a solution or some more hints.
to sum things up:
- in a threaded sms conversation, upon sending AND receiving a message the small contact pictures (both yours and your interlocutors') flash one time (like if they were reloading: you can briefly see the grey android default "no picture" icon meanwhile). this didnt happen on elder builds, and when it happens the phone lags.
- it can happen from time to time that after this strange reloading the pictures won't load anymore and immediately after this, the app will loose sync with contact names too: you'll end with phone numbers anymore like if you had an empty phonebook.
I have found the culprit to be not the messaging app but the contacts app. when this happen, i "just" need to go back to home and tap the contacts app. sometimes it just displays a black screen, sometimes i get a FC message about com.android.process.acore. after pressing the FC button the app will restart and both contacts and messaging will return working normally (although still with the weird reloading thingy).
as far as things go it seems that
- hard resetting / wiping data does not help
- removing and re-adding the google account sync does not help
- it happens on 354 too
- not all users (very few, it seems) are affected by this
- there is no weird backup & restore voodoo procedure implied in the affected streaks
the small amount of users affected by this issue leads me to think we are, in some way, doing something wrong. any help would be greatly appreciated really. thanks in advance folks.
Click to expand...
Click to collapse
I've the same prob. i was thinking it maybe from my rom (simple streak 1.2) but looks like its not.
yeah it seems to be an issue related to android 2.2.2 (I didn't have this problem on stock 318 rom). I have done some more tries yesterday but I didn't come up with a solution. I even tried to desync google account, remove all contacts etc, and create a new test contact with random picture, well as soon as I insert the picture the problem reappears.
I forgot to mention it in the op but go sms pro seems unaffected.
Contacts app in StreakDroid 1.9.1 does this as well.
I'm going to try and roll back contacts.apk, contactsprovider.apk and mms.apk from stock 318. I have checked the filesizes and they actually are slightly different.
well tbh I am 99.9% confident I will end up having to reflash my phone but oh well..
i'll report back!
EDIT: so here's the news. replacing apps didnt work. ROM 360 is still affected by the issue.
back to the drawing board...
Ok guys I finally got around to rooting and freezing some apps last night on my X2. However, now I'm having texting problems. They seem to go out fine but they rarely come in. Also, I sometimes get a FC error saying the application Text Messaging ( process com.motorola.conversations has stopped unexpectedly.
Also, when texts do come in about 75% of the time I get two of the same text. This may be a chompsms thing since it was doing this before I rooted.
The list I used can found by googling "X2 freeze app list" and it's on androidcentral. (i can't post links, sorry)
Can you guys help sort this out? Thanks!
I've looked at the list and its sound. None of those apps should have caused the issue you are experiencing. You mentioned a 3rd party messaging app? Do you still have the stock messaging app?
Sent from my DROID X2 using xda premium
Yes I sure do. I haven't removed anything, I've only frozen apps. I went halfway through the list and just froze a few at a time but stillgot the random FC's. I'm not sure what to do now..
I would unfreeze everything and see if you still get fcs. If you do it might be your third party app. If not then freeze just Verizon apps and freeze the rest one at a time, that way you can discover the problem by process of elimination. I personally think the third party app is causing the problem but hey I could be wrong.
Sent from my DROID X2 using xda premium
If I don't freeze anything then I don't get any fc's or problems to speak of. But that kind of defeats the purpose of buying Titanium Pro and the phone is much quicker when I had a bunch of the bloat frozen. I'll spend some more time freezing apps slowly but the problem is that the fc's don't happen happen every time even with the same list of frozen apps so that makes narrowing it down very difficult. If you have any great ideas in the meantime let me know, thanks!
Sure thing I will keep it in mind
Sent from my DROID X2 using xda premium
My frozen list without FCs in any stock apps:
Amazon MP3
Amazon Kindle
All other preloaded apps (NFS Shift, Let's Golf, etc.)
android-syncservice-app (related to Backup Assistant)
BackupAssistanceClient.apk
blur_flickr.apk
blur_lastfm.apk
blur_linkedin.apk
blur_myspace.apk
blur_orkut.apk
blur_photobucket.apk
blur_skyrock.apk
blur_twitter.apk
BookmarksWidget.apk
BooksPhone.apk (Google Books)
BuaContactAdapter.apk (Backup Assistant Contact page)
Cardock2.apk (do not freeze if you use a car dock)
DeviceStatistics.apk (polls various systems and stores statistical data)
Dock.apk*
DockService.apk*
* These apps are also required for HDMI mirroring; keep ro.hdmi.mirror.enable=false in the build.prop as it is enabled via hotplugging
HelpCenter.apk
IMPresence.apk
MessagesWidget.apk
MyVerizon.apk
PerformanceManager.apk (this will cause persistent FCs until battery pull; on restart, the system will remove data related to this app)
Preloaded.apk (preloaded contacts)
Protips.apk
QuickContactWidget.apk
Quickoffice.apk
QuickSMS.apk
RichLocation.apk
Skype_mobile_live.apk (use Market version instead)
Slackerradio.apk
SpellingCheckService.apk (I'm a good speller and hate this crap)
SuggestionsProvider.apk
SuggestionsRuleCheckerCore.apk
SuggestionsServiceScheduler.apk
-- Freezing these will alleviate a lot of the lag experienced with the stock ROM; adding build.prop optimizations will complement this
ToggleWidgets.apk
Vcast.apk
VcastMusic.apk
VcastVideo.apk
vnav_DROIDX2... (VZ Navigator)
Vsuiteapp.apk
VVM.apk
VZWIM.apk
VZWInstaller.apk
WeatherWidget.apk
You can freeze the datacollection APKs, but just know that you won't have any battery statistics and some data push features won't work either. If you freeze datacollection without freezing the 3 Suggestions APKs, you'll get a force close on the RuleChecker at startup.
I kept the social stuff mainly because the stock ROM doesn't integrate the Facebook app like stock Android, so in order to have your Facebook contacts sync'd with your phone contacts, you need the blur_facebook.apk authenticator, and to keep the status updates intact when receiving a phone call from a contact with Facebook data, you need some of the social apps (mainly friendfeed.apk). I disable the social messaging notifications from the Messaging app in the launcher, as the official Facebook app provides notifications, and I don't need two.
If you don't care about that stuff, just remember that the stock ROM expects many of the authenticators to be there, mainly Facebook since stock Android also links with Facebook. You may get force closes when trying to open or edit a contact, or when text messaging contacts.
Here are the APKs that will cause FCs in the contacts area (opening or editing a contact):
blur_activesync.apk
blur_email.apk
blur_facebook.apk
blur_yahoo.apk
I kept blur_picasa and blur_youtube as I wanted these sync'd in my gallery.
blur_xxx are authenticators (used in the Accounts page)
Blurxxx are actual programs
Sorry about the length, but some things need to be explained so everyone can understand these things.
Thanks for the very long and detailed post Jason. I'm also trying to get my extended battery calibrated but the Battery Calibrator app doesn't seem to be working.
I will definitely get to work on that app list but with just those few that I had listed I wasn't able to get into my contacts without a fc. I don't see how everyone else is doing all these things so easily but I'm struggling. Is it possible to have a bad root or something?
I didn't read all of Jason's post, so forgive me if I repeat something, but I use Chomp and have run into something like this, but only if I freeze the default messaging application. If I freeze it, I can send text from Chomp, but not receive them. Unfrozen, I can send and receive fine. As much as I'd enjoy freezing the default app, I've just disabled the notifications from it and hidden it from view. I know I was able to freeze it without issue when I first got the phone (back on FroYo), but, since updating to GB, it causes issues.
I've seen problems when my mother sends me a text where it doubles the text, we are both in VZW and the text itself is doubled on her end, so could it be VZW?
shoota13 said:
Ok guys I finally got around to rooting and freezing some apps last night on my X2. However, now I'm having texting problems. They seem to go out fine but they rarely come in. Also, I sometimes get a FC error saying the application Text Messaging ( process com.motorola.conversations has stopped unexpectedly.
Also, when texts do come in about 75% of the time I get two of the same text. This may be a chompsms thing since it was doing this before I rooted.
The list I used can found by googling "X2 freeze app list" and it's on androidcentral. (i can't post links, sorry)
Can you guys help sort this out? Thanks!
Click to expand...
Click to collapse
Forgive me if mentioned or answered I didn't read...just saw this while at work
did u happen to freeze email engine or authentication?
That will mess up texts
I can't remember now for sure but I think I froze Corporate Sync Authenticator. Would that affect texts? I need to get some more time to play around with this but it's so darn frustrating, I thought this would be pretty straight forward. I also still can't get my extended battery calibrated. I get the blinking red-light after about four hours off the charger
shoota13 said:
I can't remember now for sure but I think I froze Corporate Email. Would that affect texts? I need to get some more time to play around with this but it's so darn frustrating, I thought this would be pretty straight forward. I also still can't get my extended battery calibrated. I get the blinking red-light after about four hours off the charger
Click to expand...
Click to collapse
Our phone will NEVER read an extended battery correctly
no matter how many times u "calibrate" it.
You gonna want to use a battery widget and keep an eye on the voltage left.
I believe around 3700 is pretty much dead and u should recharge.
Corporate email may have had something to do with that text issue.
It sounds more likely that it is the third.party message app giving u issues.
I know when I used go sms and I froze stock message app I entered the APN and SMSC #'s or something like that manually ((I forget exactly what I entered...but I had found what needed to be entered by digging around in root explorer somewhere)) for it to pull messages and send correctly....
good luck...
If I have time later ill browse around and see if I can locate what I did before...
ashclepdia said:
Our phone will NEVER read an extended battery correctly
no matter how many times u "calibrate" it.
You gonna want to use a battery widget and keep an eye on the voltage left.
I believe around 3700 is pretty much dead and u should recharge.
Corporate email may have had something to do with that text issue.
It sounds more likely that it is the third.party message app giving u issues.
I know when I used go sms and I froze stock message app I entered the APN and SMSC #'s or something like that manually ((I forget exactly what I entered...but I had found what needed to be entered by digging around in root explorer somewhere)) for it to pull messages and send correctly....
good luck...
If I have time later ill browse around and see if I can locate what I did before...
Click to expand...
Click to collapse
In IRC I saw that someone was watching theirs and they said 3200 is dead....
sent from my cyanocrack
motcher41 said:
In IRC I saw that someone was watching theirs and they said 3200 is dead....
sent from my cyanocrack
Click to expand...
Click to collapse
Yeah I have had mine go lower than 3700
I meant that when it starts to go under 3700 it seems to drop faster also
so its a good idea to charge up when u get under 3700 since its a BAD idea to let a Li-on battery drain completely....they work better and last longer if u start charging when it gets to around 15%...
Thanks for clarification motcher
Thanks for the input guys. Unfortunately I just can't seem to freeze anything without getting force closes. So I guess my root was all for not :/ boo.
Is there a specific battery widget that you would recommend? Or will any do?
When i first got my X2 I had a problem with sending double texts and not being able to open a thread once it had 100+ mesages in it. I would have to delete the thread for it to be corrected. I rooted the phone and tried freezing and unfreezing a bunch of apps and it still gave me problems. Both when i was stock with very few apps and rooted. But when i flashed minimal x it seemed to quit. Ive been running Eclipse and now CM7 and havent had anymore issues. Btw the problem with the text wasnt just one phone. This is my second X2 and both had it till I put a rom on it. Im sure there was something simple I missed but I still dont know what.
pacman377 said:
When i first got my X2 I had a problem with sending double texts and not being able to open a thread once it had 100+ mesages in it. I would have to delete the thread for it to be corrected. I rooted the phone and tried freezing and unfreezing a bunch of apps and it still gave me problems. Both when i was stock with very few apps and rooted. But when i flashed minimal x it seemed to quit. Ive been running Eclipse and now CM7 and havent had anymore issues. Btw the problem with the text wasnt just one phone. This is my second X2 and both had it till I put a rom on it. Im sure there was something simple I missed but I still dont know what.
Click to expand...
Click to collapse
I might have to give CM7 a try. This is just complete BS. I rooted in order to freeze and apps and calibrate my battery, neither of which I can do. So now I have a stock phone with a pointless root :/
shoota13 said:
I might have to give CM7 a try. This is just complete BS. I rooted in order to freeze and apps and calibrate my battery, neither of which I can do. So now I have a stock phone with a pointless root :/
Click to expand...
Click to collapse
ummmm
not pointless
just gotta figure out which apps are interdependent
as with most phonesI believe
also
eclipse!!! best part of being rooted.....and it's about to become even BETTER
(a little Birdie told me hahaha)
there is just enough to keep us rooted x2 users busy...
take a stroll thru booked's sticky in development section to see what's available
Yeah I saw a lot of people raving about Eclipse. I was going to install that but for some reason while I was reading up on how do it I got scared off. Convince me it's easy
How long until the new rom comes out? Is it ICS?
I upgraded my NT from CM7 to CM10 & overall, I'm very happy with it. My only problem at the moment is that my email app crashes when I open it. I can get yahoo & gmail, but when I open the stock app it crashes right away. I figure that if I uninstall/re-install it might fix it, but I have no idea of exactly to un-install & where to get it to re-install it.
Right after I installed CM10, Talk kept crashing but that has stopped. Not sure if that points to anything, but figured it should be mentioned.
Any ideas? Thanks!
Answering my own question in case it happens to someone else. It looks like I got it working. I deleted all the data, not just the cache. That meant I had to set the account up again, but it appears to have worked. Mail no longer crashes. Must have been something in the settings when it tried to check mail.