I have no idea what this message means or what I can do to fix it. It says "The process android.process.media has stopped working unexpectedly. Please try again"
I just tried to revert it to 1.4.0 when I was at 1.4.3 I was able to fight my way to the settings and device info but under software it says unavailable or unknown. The reverting back had no problems whatsoever. i used Acclaim_update.Zip to do it and followed instructions to the letter. Is there a way to fix this by reinstalling the software differently or possibly a fix for this problem?
Also Please understand it was a hassle to even get to the settings. ive tried resetting and deregistering device. didn't work
Sounds like you need the stock firmware. Hope you get it fixed...could always tell b&n that it happened with the ota 1.4.3 update. If you get it fixed and end up on 1.4.3 again, the ext SD card root method works.
Sent from a galaxy far far away......
See if you can use one of the nandroid backups to fix
http://forum.xda-developers.com/showthread.php?p=23158867
Sent from a galaxy far far away......
Dylonishere123 said:
I have no idea what this message means or what I can do to fix it. It says "The process android.process.media has stopped working unexpectedly. Please try again"
I just tried to revert it to 1.4.0 when I was at 1.4.3 I was able to fight my way to the settings and device info but under software it says unavailable or unknown. The reverting back had no problems whatsoever. i used Acclaim_update.Zip to do it and followed instructions to the letter. Is there a way to fix this by reinstalling the software differently or possibly a fix for this problem?
Also Please understand it was a hassle to even get to the settings. ive tried resetting and deregistering device. didn't work
Click to expand...
Click to collapse
I read this 'can' be caused by a bad SD Card. The logic behind this premise is that Android ( the operating system ) reads a 'bad spot' on the memory card and being really stubborn, will not give up 'trying' to read the data at that bad spot. The fix is to re-do the card completely. Use SDFormatter 3.0
Related
I don't know what happened because I don't think I did anything I wasn't supposed to but for some reason all of a sudden my Android Keyboard gave me this message:
"The application Android Keyboard (process com.android.inputmethod.latin) has stopped unexpectedly. Please try again."
Only thing is that when I go to type something in at a place that needs the input method I can still see the soft keyboard come up in the background behind the above message. Is there something I can re/install to fix this or do I have to reformat my entire device!? What do I do!?
P.S. - I have full, permanent root access and have cleared out the "davlik-cache" folder numerous times to no avail.
Scratch this request, I just reinstalled and re-permanently rooted my A101IT & that solved it. For future reference, I'd still like to know how to fix that problem by any other means beside a full reformat?
I've just purchased transformer prime, tryed to upgrade to ICS, then it started to download the update, but I needed to turn off the unit before it finish to download.
then, later I tryed again, but now I keep getting the error message:
"the application DMClient process com.asus.dm has stopped unexpectedly please try again"
and it won't start the download.
I've tried factory reset, cold reboot, clear and stop CMClient and DMClient,
but nothing helps...
Did anyone experianced this problem ?
idanool said:
I've just purchased transformer prime, tryed to upgrade to ICS, then it started to download the update, but I needed to turn off the unit before it finish to download.
then, later I tryed again, but now I keep getting the error message:
"the application DMClient process com.asus.dm has stopped unexpectedly please try again"
and it won't start the download.
I've tried factory reset, cold reboot, clear and stop CMClient and DMClient,
but nothing helps...
Did anyone experianced this problem ?
Click to expand...
Click to collapse
No, but powering off during an update on any device is a no-no. At best nothing happens, at worst (consider this the more likely path) you corrupt your OS and will need to restore from a backup (not possible ATM) or reformat (manually reinstall your current update)
http://support.asus.com/download.as...sformer+Prime+TF201&hashedid=FqCKMQDqgvSncfFM
Again, never power off during an update (or any file reading/writing), this is a sure-fired way to corrupt system and personal files.
Thanks!
I didn't think that shutting it down while it's just downloading the file will cause any damage... I tought it will just cancel the download and the update...
anyway, I manually installed the latest 4.0.3 version from the web site (via sd card) then wipe and all is good.
Well, far as I know just downloading should have been fine, no clue what happened there.
Glad you got it worked out though!
P.s. I feel idiotic for not saying so in my first response, but of course installing from SD card fully formats the device and wipes out all information on the internal SD. Back up what you can regularly to an external SD/mSD
It didn't wipe automatically (I still had my apps and google account), but I still had "DMClient stopped working" problems after the installation, so I wiped manually and it's good now. I'm not sure about the internal SD, I didn't have anything on it.
I have had the same issue, but the error occured right out of the box... trying to fix now
Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
pzling said:
Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
Click to expand...
Click to collapse
If there was a point in time when everything was working and then one change was made, the stock dialer was removed, then things stopped working, the solution would be to revert back to the working point in time.
Curious, what guide suggested the removal of the stock dialer?
As a side note, before removing files it is always best to either make a complete backup, nandroid, or to at least backup the specific file being removed so it can be quickly and easily replaced.
The main issue here seems to be the removal of the stock dialer. On the technical side of things, the dialer is a very integrated component of Android.
In AOSP, which all ROMs to some degree are based off, the dialer apk file contains not only the dialer but also browsing of contacts and links in on the back end with a few files.
Once you restore the Dialer, I think called phone.apk or something similar, the issues should go away such as FC. If there are issues accessing the SIM card after restoring the previously removed file, off the top of my head, my best guess would be to clear out the settings stored on the data partition. A setting could have been created during the dialer removed state which might prevent the system from restoring proper SIM access.
Hope that adds a bit more detail around the standard process of removing files and making adjustments!
Cheers thanks, much appreciated.
Largely the guide of my ignorance that decided to remove the stock dialer. It's only in the last half hour or so that I've just come by a guide that specifically says to *not* remove the stock dialer. In the first instance I thought it wouldn't be such a big deal as Titanium Backup could always restore it ... in which it turned out it couldn't.
So after all's said and done, is there a way (apart from Ti Backup) to restore just the stock dialer phone.apk (say by download or other)?
Another approach I'm considering is to find a way to flash a custom / stock ROM to fix this. However as my phone is unbranded and on HBOOT 1.49.0018, I'm finding this very difficult with the standard methods posted. On the other hand, ideas are starting to run out and desperation running high!
pzling said:
Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
Click to expand...
Click to collapse
I have had this happen to me a few times, this mostly happens when you apply a mod/tweak to a rom that is not compatible. Do a wipe and re-flash the rom that you want and it should fix the problem.
Thanks so much for this, that's fixed it.
Re wiping, since you can wipe from the Recovery and installation of the rom wipes before flashing anyway, is it necessary to use a wipe img? If so, what is recommended? (As I'm on HBOOT 1.49, I seem to only be able to run CWM 4.0.1.4 Shooteru Recovery).
ROM not booting
Looks like I've dug myself into another hole again.
The 'Sim Card detection' problem was fixed with a wipe from CWM 4.0.1.4 and flashed with ShaWn3D v1.4 rom. Everything works and I was happy.
But I was keen to try out the LeeDroid rom but the WiFi error keeps recurring despite my attempts with the solutions provided at
http://forum.xda-developers.com/showthread.php?t=1248838.
I've tried:
- re-flashing LeeDroid with so many versions of bcm4329.ko I've lost count
- reflashing the kernel with the LeeDroid kernel addet
- re-flashing another rom altogether (King Cobra v1.9) to see if it makes a difference; it doesn't - WiFi persists.
So now I've decided to go back to the ShaWn3D rom but now although the flash is successful, the boot is stuck at the white HTC splash screen.
What have I done wrong?
Hi ya'll.
I have a nook that was bricked in the past, and I had to completely restore all the partitions of the nook. Now when I try to go to the nook store it says that "A problem has occurred. Please try again." It will work for about a day or two, but then it will no longer work. I've looked into restoring the serial number but I have not been able to detect the nook so far. I was wondering if anyone had any ideas about why this is happening, or what I can do to fix it? I really want to go back to using the stock as the Daily Driver, but without the store I don't think I'll be able to do that.
Hello all! I registered real quick in hopes this community could help me out with something.
So quite a while ago I rooted my Lenovo Tab 2A 10-70 tablet with KingoRoot in order to generate a logcat file. That went fine and dandy, and then I disabled some misc. apps (like Kindle for Android). I can't remember exactly what I messed with, so please bear with me.
The issue is that a couple of days ago I tried taking an image with my tablet with the default Camera app, when suddenly it started giving me some errors with generating thumbnails. Worse yet, my computer could not open these and they were seemingly corrupted. The camera started acting up as well, and claimed that "Unfortunately, Gallery has stopped working." whenever I attemted to record. I tried clearing the cache based on some recommendations through others and force stopping the app, and this seemingly worked for one recording/picture, but then would stop again. I found deleting the DCIM folder entirely from my Android's Internal Storage helped, but it'd quickly corrupt again.
Frustrated, I asked a friend for help on what to do figuring he had more knowledge in Android devices then me. He suggested I tried another camera app, but I couldn't get Google Play to download anything to the internal storage or my SD card, despite clearly having enough space.
As a last resort, I tried updating through the official "Updates" app to see if that would help me, and it claimed there was a new ROM available. I tried that, but then suddenly it failed and now my tablet seems to bricked? I can now only get the "No command." screen to show up.
I've tried using the following options while on this screen:
- reboot system now - this takes me back to this menu after it shows a Lenovo screen twice, which makes me think it's having trouble booting into Android itself.
- Apply update from ADB/sdcard - Both did nothing for fairly good reason, but I checked these options out of curiosity.
- wipe data/factory reset - Tried these the very first time I got to this screen after a failed installation. It seemingly hasn't worked for me.
- wipe cache partition - Tried this a bit later, but got similar results.
- root integrity check - Scanned a bunch of .apk files, but then later threw up some errors after that was done and said the check failed.
So, in short, I'm stuck in this menu and I'm getting kind of frustrated/scared. Is there anything that I can do to save the tablet at this point? Is there something I did wrong that might have bricked it? I'm not terribly experienced with Android, so I'd love to hear some thoughts from others! I'll gladly take anyway to restore the tablet back to a point where it can actually boot into the OS, and I understand I'd lose some data doing any sort of clean install.
Thank you!
Cornholio309 said:
Hello all! I registered real quick in hopes this community could help me out with something.
So quite a while ago I rooted my Lenovo Tab 2A 10-70 tablet with KingoRoot in order to generate a logcat file. That went fine and dandy, and then I disabled some misc. apps (like Kindle for Android). I can't remember exactly what I messed with, so please bear with me.
The issue is that a couple of days ago I tried taking an image with my tablet with the default Camera app, when suddenly it started giving me some errors with generating thumbnails. Worse yet, my computer could not open these and they were seemingly corrupted. The camera started acting up as well, and claimed that "Unfortunately, Gallery has stopped working." whenever I attemted to record. I tried clearing the cache based on some recommendations through others and force stopping the app, and this seemingly worked for one recording/picture, but then would stop again. I found deleting the DCIM folder entirely from my Android's Internal Storage helped, but it'd quickly corrupt again.
Frustrated, I asked a friend for help on what to do figuring he had more knowledge in Android devices then me. He suggested I tried another camera app, but I couldn't get Google Play to download anything to the internal storage or my SD card, despite clearly having enough space.
As a last resort, I tried updating through the official "Updates" app to see if that would help me, and it claimed there was a new ROM available. I tried that, but then suddenly it failed and now my tablet seems to bricked? I can now only get the "No command." screen to show up.
I've tried using the following options while on this screen:
- reboot system now - this takes me back to this menu after it shows a Lenovo screen twice, which makes me think it's having trouble booting into Android itself.
- Apply update from ADB/sdcard - Both did nothing for fairly good reason, but I checked these options out of curiosity.
- wipe data/factory reset - Tried these the very first time I got to this screen after a failed installation. It seemingly hasn't worked for me.
- wipe cache partition - Tried this a bit later, but got similar results.
- root integrity check - Scanned a bunch of .apk files, but then later threw up some errors after that was done and said the check failed.
So, in short, I'm stuck in this menu and I'm getting kind of frustrated/scared. Is there anything that I can do to save the tablet at this point? Is there something I did wrong that might have bricked it? I'm not terribly experienced with Android, so I'd love to hear some thoughts from others! I'll gladly take anyway to restore the tablet back to a point where it can actually boot into the OS, and I understand I'd lose some data doing any sort of clean install.
Thank you!
Click to expand...
Click to collapse
Theirs a Guide here on how to re flash your tablet back to stock
http://forum.xda-developers.com/android/general/guide-lenovo-tab-2-a10-70-root-t3279322
Quite a late reply, but thank you! That ended up working quite nicely! I upgraded my tablet from Lollipop to Kitkat too, which seems to be working a bit better app performance wise for me.