A few months ago I purchased the Flytouch 3. Here are my stats:
DISCO10; Version 2.2-20110529; Kernel 2.6.32.9 z/d@dtlinuxserver #29 Build #FRF85B
I flashed with Tims 5a and all things were wonderful! So fast and solved the problems. Used tablet yesterday as follows: watched YouTubes; Tweeted & added to my NetFlix Queue - all was good. Powered off.
This morning I turned tablet on and immediately got the following message:
The process android.process.acore has stopped unexpectedly. Please try again. and the button "Force close." which when pushed does nothing - the message just appears immediately again. At the time the battery was more than half charged. I powered off and tried again - same thing. Hooked up to charge battery mode and same thing.
I've read a few posts about similar issues and everyone says to flash with Tim's firmware - which I already did and it was running terrific.
So, is the only answer to reset to factory and then reload Tim's firmware and then download apps again? If so, is this going to be an on-going problem?
Has anyone had this happen often? Thanks for any feedback.
DISCO10; Version 2.2-20110529; Kernel 2.6.32.9 z/d@dtlinuxserver #29 Build #FRF85B
I flashed with Tims 5a and all things were wonderful! So fast and solved the problems. Used tablet yesterday as follows: watched YouTubes; Tweeted & added to my NetFlix Queue - all was good. Powered off.
This morning I turned tablet on and immediately got the following message:
The process android.process.acore has stopped unexpectedly. Please try again. and the button "Force close." which when pushed does nothing - the message just appears immediately again. At the time the battery was more than half charged. I powered off and tried again - same thing. Hooked up to charge battery mode and same thing.
I've read a few posts about similar issues and everyone says to flash with Tim's firmware - which I already did and it was running terrific.
So, is the only answer to reset to factory and then reload Tim's firmware and then download apps again? If so, is this going to be an on-going problem?
Has anyone had this happen often? Thanks for any feedback.