Guest achromic Posted April 2, 2011 Report Posted April 2, 2011 Hi all! This problem has only just started this morning, and was wondering if anyone else has been having the same. When I go to sites like modaco, I immediately get an FC with the following: The application Browser (process.com.android.browser) has stopped unexpectedly. Please try again. Would digging out an apk from the rom I downloaded work if I pushed it using adb? Or, is there a better way??? I'm running r8 if thats any help
Guest trevor432990 Posted April 3, 2011 Report Posted April 3, 2011 Hi all! This problem has only just started this morning, and was wondering if anyone else has been having the same. When I go to sites like modaco, I immediately get an FC with the following: The application Browser (process.com.android.browser) has stopped unexpectedly. Please try again. Would digging out an apk from the rom I downloaded work if I pushed it using adb? Or, is there a better way??? I'm running r8 if thats any help If you Google "application Browser (process.com.android.browser) has stopped unexpectedly" there are quite a few examples of this incident occurring and some suggested fixes. If you have installed a new application recently it is suggested you uninstall that app, reboot and see if the problem goes away failing that it might be that your browser data file has been corrupted and there are some ADB instructions on how to fix that here just remember to insert 'adb-windows' at the start of each ADB command line rather than just 'adb'. Let us know how you get on? :D
Guest El Nino9 Posted April 30, 2011 Report Posted April 30, 2011 If you Google "application Browser (process.com.android.browser) has stopped unexpectedly" there are quite a few examples of this incident occurring and some suggested fixes. If you have installed a new application recently it is suggested you uninstall that app, reboot and see if the problem goes away failing that it might be that your browser data file has been corrupted and there are some ADB instructions on how to fix that here just remember to insert 'adb-windows' at the start of each ADB command line rather than just 'adb'. Let us know how you get on? :mellow: would be easier probably going into application data and wiping the data for the browser app. usually fixes FC for me
Guest Zebrahead Posted April 30, 2011 Report Posted April 30, 2011 would be easier probably going into application data and wiping the data for the browser app. usually fixes FC for me +1, it's most likely some browser data has become corrupt and thus the browser doesn't like opening it. If this fails, I'd just repush browser.apk. If it still doesn't work, then it's sounds like it's conflicting with some non-browser related data, which makes it a bit more difficult to solve. Zeb
Guest warriorscot Posted May 1, 2011 Report Posted May 1, 2011 Clearing data and pushing a new browser apk are both excellent ideas. If you get really stuck in the interim try using another browser the NI stock one is a good stock alternative or Opera is a very nice alternative browser for the vega as its tablet optimised(unlike the stock one) and well polished. If push comes to shove make a nandroid or titanium backup and reflash the R8 on a clean system which should sort the problem.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now