Does anyone else have problems with the Email app force closing on Kratos overcome rom? Here is what is happening. I will open the email app (not gmail app, its works just fine) and it will load messages but as soon as I try and look at them it freezes for a few seconds then force closes. Weird thing is, after I reopen the app I can view that message that I tried to look at before. It just has to force close first for some reason.
I did a clean install of kratos, wiped data,cache, and dalvik cache. Not sure what to do next?
Any ideas?
Okay so i figured out my own problem. I was using titanium backup to freeze apps and i ended up freezing a few system apps i apparently wasnt supposed to freeze. Weird thing is that i froze the exact same apps on my Samsung captivate and its email app works fine??? Oh well it works now so im happy.
Sent from my GT-P1000 using XDA App
Within the last few weeks, the YouTube app has just NOT been working, continuously giving me the "YouTube has stopped working" error.
I have found that uninstalling and reinstalling the YouTube app allows it to work properly until it decides to stop working again.
Even clearing the cache and data does nothing.
It's anyone else having this problem?
Sent from my KF-HD7
quirky software
evildread said:
Within the last few weeks, the YouTube app has just NOT been working, continuously giving me the "YouTube has stopped working" error.
I have found that uninstalling and reinstalling the YouTube app allows it to work properly until it decides to stop working again.
Even clearing the cache and data does nothing.
It's anyone else having this problem?
Sent from my KF-HD7
Click to expand...
Click to collapse
Hello,
I too am having this problem. I also notice the same thing with the browsers (Dolphin & Silk) in general. There must be something that is still updating even though Droidwall is running. I still haven't been able to get any firefox version running.
Regards,
Jim
So i dint really notice this but flow free and fruit ninja started force closing when i wanted to play them, they worked fine in the past but i havent played with them for quite some time
its isnt like the regular force close which is instant, i could go into fruit ninja, then new game then it only force close, flow free force close when im in the menu instead
i could just do a factory reset but i tried clearing the data/cache and reinstalling the app but still force closing, my other apps work fine
just wondering, could this be caused by i flashed a newer AOKP over a older AOKP from maclaw
I have a Nook HD 8gb and I installed 10.1.3 RC2 but I had issues with the Amazon app losing it's login details and Chrome closing when I was browsing. I have now installed 10.2 nightly (919,920,921) and everything is running great, no reboots and all apps work apart from browsers. I have tried several browsers from the app store - dolphin, opera, firefox, boat etc and they all force close when loading up web pages, this usually occurs in the first minute. Chrome works for a bit longer but as soon as I open a page with lots of images it just closes without any errors. I am now trying Chrome beta which seems to be the best and I can browse ok but even this closes eventually. I find it odd that only browsers are effected. I have no other apps crash and I have watched movies, listened to music and played games for several hours without any problems. Can anyone offer any advice on how to fix this problem? as I really do not want to go back to the stock rom.
Reklaw said:
I have a Nook HD 8gb and I installed 10.1.3 RC2 but I had issues with the Amazon app losing it's login details and Chrome closing when I was browsing. I have now installed 10.2 nightly (919,920,921) and everything is running great, no reboots and all apps work apart from browsers. I have tried several browsers from the app store - dolphin, opera, firefox, boat etc and they all force close when loading up web pages, this usually occurs in the first minute. Chrome works for a bit longer but as soon as I open a page with lots of images it just closes without any errors. I am now trying Chrome beta which seems to be the best and I can browse ok but even this closes eventually. I find it odd that only browsers are effected. I have no other apps crash and I have watched movies, listened to music and played games for several hours without any problems. Can anyone offer any advice on how to fix this problem? as I really do not want to go back to the stock rom.
Click to expand...
Click to collapse
Go to recovery. Wipe Cache, Wipe Dalvik Cache, reinstall CM zip, Wipe Cache, Wipe Dalvik Cache. No idea why that works or even if the first two steps are necessary but it worked for me and I am now superstitious about doing it in that order. Just a suggestion, I am not a tech.
dsore1218 said:
Go to recovery. Wipe Cache, Wipe Dalvik Cache, reinstall CM zip, Wipe Cache, Wipe Dalvik Cache. No idea why that works or even if the first two steps are necessary but it worked for me and I am now superstitious about doing it in that order. Just a suggestion, I am not a tech.
Click to expand...
Click to collapse
You are right, the first two steps are not necessary. But reinstalling CM and wiping dalvik-cache (once) can be very helpful sometimes.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks for the replies.
I have tried as you suggested but I am still experiencing browser crashes. I have now restored the stock rom and all of the browsers are now working so I don't know what to try next, it's all very odd.
Has any other Nook HD owner experienced this?
I have also tried a androidfornook sdcard and the browsers also crash using this method as well. I'm currently using the stock rom with Nova Launcher and I've not had any problems but obviously I would have preferred a CM rom. :crying:
I've now tried 10.1.3 stable and I still have the same problem. If anyone with a nook hd and CM installed would like to test this for me, then please install dolphin and then go to to overclockers.co.uk and then click on 'contacts' in the top right corner. The dolphin browser will then close. This occurs with most browsers.
I have also tried the 10.1.3 stable release on my wife's nook hd and it it behaving the same as mine so it looks like it is a possible issue with the cm rom. I'm now using the stock rom and nova launcher and it is actually quite good.
Same problem with stock and CM.
It may be related to JavaScript. I turned it off and crashing stopped. Not a solution but may help to browse problematic sites.
This is the first time I've seen weird behaviour on Chrome and it started after installing Android 11. When I open Chrome it just closes right away. I need to open it about 10-20 times for it to finally stay open. I tried installing Chrome beta and it works better although sometimes it gives the same issue.
I tried clearing all the data in Chrome but didn't help. Wondering if anyone had this issue or has suggestions to fix.
dortok said:
This is the first time I've seen weird behaviour on Chrome and it started after installing Android 11. When I open Chrome it just closes right away. I need to open it about 10-20 times for it to finally stay open. I tried installing Chrome beta and it works better although sometimes it gives the same issue. I tried clearing all the data in Chrome but didn't help. Wondering if anyone had this issue or has suggestions to fix.
Click to expand...
Click to collapse
Since chrome beta is a stand alone app and can be run beside chrome, it seems you have some kind of hard configuration error or corruption. I'm guessing you have already uninstalled/reinstalled the app. If you are unlocked I would try a dirty flash using the full image (not OTA). Next I would backup everything and wipe the phone, installing 11 fresh. Sometimes stuff happens and you just have to reinstall. Not a bad idea going from 10-11. In addition to chrome beta, I use Firefox beta because it supports extensions (eg. uBlock). If the thought of wiping your phone is too much work for this single issue, it may be time to try another browser. Best of luck and let us know how you get it resolved.
Turns out it was app list mode on edxposed that was causing the issue. After disabling it, it works normally again!