• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stock email not working

J

jhnelo

Well-Known Member
since updating to ICS stock email app won't work. When opening up it will say unfortunately email has stopped. Even downloaded another email app and same happened with that. Any suggestions
 
Are you using hotmail? Lots of people are having hotmail problems right now. If not just try clearing data via settings>applications>manage applications. You will need to input your email account details again though.
 
nicka3200 said:
Are you using hotmail? Lots of people are having hotmail problems right now. If not just try clearing data via settings>applications>manage applications. You will need to input your email account details again though.
Click to expand...
No the stock email app. I have cleared data many of times and re done my details still crashes tho?
 
OP, I believe nicka3200 was asking if your email provider was Hot mail, not the app you were using. Second, if it hasn't worked at all since the update, I suspect that your best bet would be to do a hard reset which wipes all your data off of the device, so you get a fresh start with the new OS.
 
I belive your right. Yes my provider is Hotmail. At times when I have cleared the data it would work for a week or so then crash. But you still think I should Do a hard reset?
 
I get
 

Attachments

  • Unfortunately.jpg
    Unfortunately.jpg
    19.6 KB · Views: 132
jhnelo said:
At times when I have cleared the data it would work for a week or so then crash. But you still think I should Do a hard reset?
Click to expand...

Well, at least that answers my question in that its worked some of the time. Was this the case at all before the upgrade?

And to answer your question on the reset, at this point I'm not sure. If it worked completely before, and stopped with the upgrade, I think that would be a clear case. You can't say that you'll never rule it out, but I'm not so sure now that it'll be a guaranteed fix at this point. Did. It behave like this much, before the upgrade?
 
RyanB said:
Can't say that I've heard of that. Does it behave that way after you reboot the device?
Click to expand...

Yes, it also happens following reboots.

It's probably caused by an app that worked fine under ICS on my RAZR MAXX but doesn't play well under JB on my Note II.

The "Unfortunately .... " is no big deal, just a minor inconvenience. I'm sure that I'll eventually track down the cause.
 
Does it always happen on the same apps? If so, alerting the dev wouldn't be a bad idea.
 
Here is a screenshot of what ssFlicker does to K-9 Mail.
 

Attachments

  • Unfortunately.jpg
    Unfortunately.jpg
    19.6 KB · Views: 137
Out of curiosity, how did you determine it to be the launcher?
 
RyanB said:
Out of curiosity, how did you determine it to be the launcher?
Click to expand...

I had a strong suspicion that ssFlicker was the cause of the problems so I Force Stopped ssFlicker in Settings and all the problems immediately went away.

I restarted ssFlicker and the problems immediately came back.
 
It looks like ssFlicker was also doing the "Unfortunately .... " dirty deed on the stock Internet browser, Chrome, the PlanMaker spreadsheet, Business Calendar, Google Play Store, OverSkreen, and the X-Ray Testicles Scanner.
 
That's a lot of apps for it to be messing with. Have you bothered to alert the dev?
 
RyanB said:
.... Have you bothered to alert the dev?
Click to expand...

No. I just got this far into the problem a few hours ago.

*And* although ssFlicker is doing the actual damage, ssFlicker is not the root cause of the problem. **Widgetsoid** is interfering with ssFlicker and causing ssFlicker to misbehave.

WHO KNOWS how many other apps might be involved!! :p

In the past I have always run Widgetsoid under ssFlicker as a launcher within a launcher and it has always worked great. But things aren't so great under JellyBean. I'll get this straightened out eventually.
 
People on Android Forums tend to resist looking at diagnostic data but in this case the main Android system log *might* show what the problem is. I would suggest using the "aLogcat" app with the preferences set to:
- Level - "Verbose"
- Format - "Time"
and
- Buffer - "Main"


- Start aLogcat
- Note the time on the phone
- Initiate an "Unfortunately email has stopped" event
- save the aLogcat log to a file or "share" it to a text editor and save.

- Repeat with the buffer set to "Events"

Then have somebody analyze the log files around the times that were noted.


Are there any volunteers for reviewing the logs? I don't want to be in the business of analyzing logs but I volunteer to review *2* logs :)


Here is a sample of W/ Warnings in the system log on my phone during an "Unfortunately ...". PID 24347 is the Android OS:

Code: 
--------- beginning of /dev/log/main
12-24 19:06:18.100 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:06:18.100 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:06:18.100 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:06:18.100 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:07:03.040 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:07:03.040 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:07:03.040 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.

12-24 19:07:03.045 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.
 
Well, the logs tend to be over people's heads (mine included). If you don't a get any explanations in a day or two, I'd try posting it in the root sub-forum for your device, or maybe over at XDA.
 
RyanB said:
.... If you don't a get any explanations in a day or two, I'd try posting it in the root sub-forum for your device, or maybe over at XDA.
Click to expand...

I'm kinda too busy to work on this right now, what with all the holiday activities plus I moved to a new house last Friday and still have over a hundred movers boxes to unpack :rolleyes:
 
jhnelo said:
since updating to ICS stock email app won't work. When opening up it will say unfortunately email has stopped. Even downloaded another email app and same happened with that. Any suggestions
Click to expand...

So can you post some system logs? :)
 
jhnelo please post copies of your system log.


Dieben said:
....It's probably caused by an app that worked fine under ICS on my RAZR MAXX but doesn't play well under JB on my Note II...
Click to expand...


I will probably have to change the configuration of my ssFlicker until the developer updates ssFlicker for JellyBean.

Here is one of the warning messages that was written to the main Android system log on my phone during an "Unfortunately .... ":


Code: 
12-24 19:07:03.040 W/InputEventReceiver(24347): Attempted to finish an input event but the input event receiver has already been disposed.


Which translates to:

https://groups.google.com/forum/m/#!msg/pdfnet-sdk/zYL1wqTeNtU/5iP0Ou8GSPsJ

".... JB is handling events differently from older versions of Android, thus breaking our logic of selecting the annotation from the quick menu. In this specific case, an ACTION_CANCEL is being delivered before we actually dismiss the quick menu. The documentation says that:

Views should always be prepared to handle ACTION_CANCEL and should tolerate anomalous situations such as receiving a new ACTION_DOWN without first having received an ACTION_UP for the prior gesture.

To fix that you need to treat the ACTION_CANCEL in the tools library (or whenever you are treating the events). In the onTouchEvent method of MenuView class (QuickMenu.java), add:

case MotionEvent.ACTION_CANCEL:
* * break; .... "
 
You must log in or register to reply here.
Back
Top Bottom