Any ideas about this one . . . ?

Bought an Android Motorola "Moto E" last week, and for the first few days, all was well.

But, beginning a couple days ago, "progressively(!), nothing works." Even the "Messaging" built-in application "Unfortunately, has stopped" when you attempt to see the details of a conversation. (But it worked perfectly a couple days ago.) Likewise, Geocaching crashes when you see the details of a cache (while many other buttons work just fine) ... and, after resetting the app's data, it won't even sign-up anymore.)

I am, frankly, quite baffled at such a "widely pervasive" problem. It came out of the blue (no apps installed other than Geocaching and Ingress ...), and it seems to have brought the whole damm phone to its knees.

I've never before seen an Android do this.

Try taking the battery out wait a few minutes; put the battery back in and than try firing it up.

This link has support for your device.
https://motorola-global-portal.custh...299/#/how_do_i

-::-It might have abandoned software updates like this article suggests.-::-
http://www.androidcentral.com/motoro...top-selling-it

Try a factory reset if all else fails.
http://www.android.gs/hard-reset-motorola-moto-e/

HTH-

If you just got it a few days ago, can you return it or get it fixed under warranty?

Yeah, we can take it back if need be.

Further info: upon factory reset, first of all we discovered that "most of the settings didn't reset." However, messaging started working again.

The Play Store crashed unless the Google-ID was set to the original value for the predecessor phone at this phone-number. I'm not persuaded, however, that this is actually a credible explanation for the problem. (I don't "wear a tin-foil hat" that is that big.)

Whatever it is, it's a "curiously highly-pervasive" symptom, affecting nearly every application, but (I surmise) only when those apps execute specific system calls. For example, Geocaching crashes when you ask for the "details" of a cache. Messaging crashes when you click on the digest of a message to see the whole thing. And, so on. The only place that such a malfunction could be, is "deep in the user-interface guts of the thing." But, if such a defect existed, reason says that it would never make it out into the field ... therefore, I know that I haven't put my finger on it yet.

This is the first time that I have ever seen an Android phone (or, any phone) do anything like this. I find myself looking at it and thinking, "now, isn't that mighty strange ..."

Perhaps third party software made it so that some setting didn't reset.
There might be a Safe Mode you can put the phone in. Safe Mode lets you boot up the system w/0 3rd party software.
http://www.makeuseof.com/tag/dealing...oring-backups/


I wonder if failure of software upgrades is what is creating the door for malfunction thus when the system call is generated perhaps that's why things become jammed or don't launch as they should? (Because they don't have what they need)

I really think your device lacks an update and that's why applications are crashing.
I'd take it back if it were my kettle of fish.
https://support.google.com/nexus/answer/2668665?hl=en

A update wrecked my Android tablet about 6 months ago.
Applications, the browser and all functionality came to a grinding halt.
After a factory reset all was well.
I still don't know what caused the slow grind but I was suspicious that a firmware update is what made things go haywire.

this is one of those reasons why i don't buy new hardware.
so, bring it back, get a decent, but used phone, preferably one that supports cyanogenmod or some of the even cooler android replacements, install it and don't worry about warranty.

edit:
seems you're not the only one...
http://www.gsmarena.com/motorola_mot...views-6376.php

I'm beginning to guess that a software update (of the OS) might have failed.

Get a iPhone, return the Moto, Flash the Moto,

I have a moto x and a guy at work has had 2 moto e's. They have been great. I'd assume if you can't do a reset then you need to return it. To be fair, the guy with the moto e's drops them and lets them fall in food and puddles and such and they still work.


Put it back to stock and see if it works would be a good start.