[FIX for HD CM10.1] "android.media.process has stopped"

HiddenG

Senior Member
Nov 5, 2011
160
46
0
Manchester
Hey all!

If you constantly get the message "Unfortunately, the process android.media.process has stopped." on your Nook HD using CyanogenMod, then please read on. :)

It should be noted that this error primarily occurs on the Hybrid install of CM10 on the Nook HD, and does not occur on the Pure install; however, if the problem persists (regardless of Hybrid or Pure, or even if it's not a Nook), this solution should solve your problem. This has been updated to include the "permanent" fix, but comes at a sacrifice (described later); whereas the "temporary" solution solves the problem temporarily without affecting your tablets services.

Permanent & Temporary Fix to "Unfortunately, the process android.media.process has stopped."
This solution has been tested on the Nook HD, running CyanogenMod 10.1 (20130313, hummingbird) via the Hybrid installation.

1. Introduction/Notes
I have updated this post, as of 05/05/2013 with a permanent fix, and still "support" the temporary fix; although the latter is not worth it - as the problem reoccurs after a short period of use. However, it is still included for those who prefer it; as the permanent solution requires that your forsake the media features, such as the "Gallery" app (it will NOT work with a permanent solution). If you want to permanently solve this issue, and are willing to sacrifice the use of the Gallery app, and others (untested); then I would recommend that you proceed with the temporary solution first, then apply the permanent solution at the end (and NOT just jump to the permanent solution, as the temporary steps are crucial to your setup - except for Disabling Google Sync and Developer Mode, so you can skip those if you wish, but I wouldn't). :)

If you're reading this post, and you do NOT have a Nook; then this solution can still be used to solve your problem(s). For all we know, if you're trying this on another device, which is NOT a Nook, the temporary solution maybe permanent for you. However for the Nook HD and HDplus, it's not.

All the best with applying this fix and remember two things:
  1. It's a dead easy process, and I'm 100% confident that any person on the street who has the intellectual ability to read English will be able to perform this fix. So don't worry, it's nothing you need a master’s degree for.
  2. Ensure that you follow what I say 100% accurately; do not click any alternatives (for example, if I tell you to clear the "System Cache", and you cannot find the option, do not just clear anything with the word "Cache" - i.e. Do NOT clear the "Dalvik Cache", they are completely different). Ultimately, just make sure what I say, is what you click on-screen and nothing else. In this guide you will be booting into ClockWorkMod (CWM), and if you make any mistakes, it could cost you (i.e. lose Android on the tablet completely).

Without any further ado, let's skip over a section and get started.

2. Disable Google Sync
The process "android.media.process" is related to Google Sync (alongside being related to a lot of other processes; hence the term "media"). Therefore we will be disabling Google Sync, in order to minimise errors; you won't notice a difference in performance, and is not an important part of the system.

  1. Get your tablet at hand, and ensure the tablet's battery is charged at 20% at minimum, or above.
  2. Turn your tablet on (in CyanogenMod/Android), so that it's in a functional state (if not already).
  3. Thereafter, unlock your lock screen and go into "Settings". Scroll all the way down until you find the option "Google", besides a blue Google icon (under the "Accounts" category). Click on "Google".
  4. You will now see listed, all the accounts currently linked to the tablet. If there is only one account, click into it. If you have more than one account, click on the first listed account, and proceed to the next step.
  5. You will now be presented with all the data which is currently in sync with Google. Untick them all: So, "Browser", "Calendar", "Contacts", "Gmail" and "Sound Search for Google Play" should be all DISABLED/unticked.
  6. If at stage 4 (above), you have more than one Google account attached to the tablet, repeat step 5 until all accounts have been disabled sync.
At this point, after successfully conducting the above, you should now have Google Sync disabled on your Nook HD; thus reducing the likelihood of the error occurring. You may now exit settings on your tablet. However, we have not yet solved the issue, please read on.

3. Enabling Developer Mode
You may be able to skip this step, if you already see the selection "Developer Options" in your tablet's "Settings" (towards the bottom of the settings menu). If not, please read the following.
  1. Once again, go into "Settings" within your tablet.
  2. Scroll to the very bottom within settings, and the last presented option should be "About tablet", click onto it.
  3. Again, scroll to the very bottom of the "About tablet" screen. You should see the title, "Build number", followed by the details.
  4. At this stage, recklessly keep clicking the "Build Number". Eventually on screen you should be presented with a few messages, similar to: "Developer mode after 3 clicks". Constantly keep clicking "Build Number" until the message displayed states (similar to): "No need. You are already developer".
  5. At this point, you can now go back out of "About tablet", back into "Settings" and you should see the selection "Developer Mode".

Congratulations, you now have developer access to the tablet. For an average consumer, this is not necessary and is an extremely powerful set of options, which allows you to alter your tablet settings. We will only use this for one purpose, so please do not tamper with other settings in the developer menu.

4. Preparing to Boot into ClockWorkMod (CWM) Recovery
ClockWorkMod Recovery (CWM) is what made Android 4.2.2 on the Nook HD even possible, not only for the Nook, but for all Android-powered devices. It is extremely powerful, mis-clicks are not excusable within CWM, and with one or two clicks (at the most), you may accidentally remove the whole Android setup from the Nook; including all your data and apps. So, you must be extremely cautious after booting into CWM. As long as you follow this guide from now onwards 100%, you'll be fine. :)

  1. Again, go into "Settings" if not already. Scroll all the way down and select "Developer Options".
  2. The third option within the menu states "Advanced reboot", tick this by simply clicking it.
  3. Now, go back out of the developer menu. Go to your tablet's home screen, close all settings, and move onto the next section to boot into CWM.

5. Clearing Cache & Fixing Permissions via ClockWorkMod Recovery
Now that you're on your tablet's home screen, and you've completed all the above, you are ready to boot into CWM. Again, as warned above, you must follow this guide accurately, else you could erase the whole Android Operating System (OS). CWM should not be accessed by anyone who has no idea on what they're doing (so later, we're going to disable software-access; in order to avoid other users accessing CWM).

But for now, you're going to be booting into it. First, hold the power button on the tablet; until it provides a dialog. Click on "Reboot" (second option), and select "CWM Recovery" on the new selection. It is once again the second option. After selecting CWM, click "OK" and the tablet should boot into it momentarily.

Before you get started in CWM, you should familiarise yourself with the controls; which are basic, however do not support the touch screen (security measure).
  • Power Button: To go up one menu, for example if you go into "Advanced", to return to the original menu, you simple press the power key.
  • Volume Up/Down: These two keys are for navigation purposes, allowing you to scroll up or down the menu respectively. Use these keys to highlight your option.
  • Home/'n' Button: This is to select the current option, for example, if you're currently hovered over "Reboot system now", and press the 'n' key, your tablet would reboot.

5.1. Clearing Cache Partition
First, we're going to clear the cache on the tablet. You will not lose any data, and this process won't affect your daily usage at all (nothing will change the daily performance of your tablet within this guide).

Now that you're in CWM, and you're familiar with the controls, we can begin clearing the cache.

  1. Navigate down, so that the selector highlights "wipe cache partition". Ensure that you have highlighted this option, and not the one above (they both have similar wording). Please ensure the correct option has been highlighted.
  2. Press the Home key, the 'n' key located at the front-bottom of the tablet to select this option.
  3. You will now be presented with another selection menu, mainly consumed by the option "No" (a security feature, to avoid incorrect choices).
  4. Navigate down, until you highlight the option "Yes - Wipe Cache" and select it. Please once again ensure it states "Wipe Cache" and nothing else.

After a few seconds, the whole cache partition on the tablet will be cleared. We're now ready to fix the permissions in CWM, so let's move to the next section of this document.

5.2. Fixing Permissions
Whilst you're still in ClockWorkMod Recovery (CWM), please do the following to fix the current permission set. This is the final stage of solving the issue.

  1. The last option in ClockWorkMod is "advanced", and should be displayed on your screen. Scroll down, highlight and select this option.
  2. The last option within the advanced menu should state "fix permissions". Highlight and select this option. If you're provided with a confirmation screen, select yes, if not, ignore this sentence.
  3. This process can take up to 2-5 minutes to complete. Once complete, if you are returned to the original menu, you should see the first option as "reboot system now". If not, press (do NOT hold) the power button until you do.
  4. At this point, select "reboot system now" and safely return to your Android setup.

As soon as your tablet boots back into Android, you'll see a message, stating that your tablet applications are being upgraded. This is the simple process of reinitiating your apps, after the cache was cleared. Dependant on the amount of apps installed, this process may require a few minutes.

6. Congratulations!
You have made it to the end of this guide, and hopefully the error has stopped occurring; regardless, it should occur significantly less during use.

If the error still persists after usage, unfortunately this method was unable to provide a permanent solution, and may act as a temporary one. To temporarily solve the issue once again, when necessary, you may re-follow this guide; or for a permanent solution, please see the next section.

7. The Bold, Permanent Solution
Please consider this a last resort, as it is a "bold" move and tackles the media process head on, by disabling it. Please only continue with this step if you have completed the above, and then have tried out your device for a while. If the problem persists, then please do the following (or repeat the temporary solution).

Your media process is responsible for communicating with your media files (.mp3, .wav .jpg, .png etc.; music, photos etc.) stored on the storage space, and rendering them to you via easy access apps. For example, the media app will search your whole storage space for photos/images, and will make them viewable via the "Gallery" app. Disabling the media process will stop the Gallery app from functioning, and other apps too which have the same behaviour.

Disabling the android.media.process is simple; and in vice-versa, it is too easy to reverse. So, let's get stated. :)

To disable the "android.media.process" completely, please do the following:
  1. Firstly, go into your "Settings" menu on your tablet.
  2. The first options are "Wi-Fi" etc. under the heading "Wireless & Networks". Look for the heading "Device", and click the second-to-last option "Apps".
  3. You will then be presented with apps which are currently installed on your device, which are safely visible. We need to move into the "All" apps section; so it also displays your processes too. To do this, place your finger on the right-hand side, centre of your screen. Then swipe/move your finger towards the left-hand side of the screen. This will swipe you to the "Running" apps. Do this once more, and you will be to the "All" apps section.
  4. The apps + processes are alphabetically listed. So scroll down till your find the process titled "Media Storage", and press it.
  5. First, clear the data and cache; by simply pressing the "Clear data" button, then press the "Clear cache" button. Confirm any messages displayed (you maybe presented "android.media.process" has stopped repetitively).
  6. Once the above is complete, at the top; click the button "Disable". Towards the right-hand side of the button titled "Force stop".
  7. It will then pop-up a message, "Disable built-in app?" Just click "OK", and the process should be disabled temporarily.

Now you may return out of settings, and back to your home screen. Close all the settings; and you should now be good to go! This should have permanently solved your problem; if not restart. :D

---
All the best, any problems, please let me know. :)
 
Last edited:

ariot

Member
Sep 30, 2010
25
9
0
You are a life saver! Just bought my nook hd last thursday and immediately put CM 10.1 on it. I had about 5 hours of fun with it and then this error massage started ruining my enjoyment. I have tried clearing all manners of caches, data resets, reinstalling CM10.1, and even changed my SD card and nothing worked. Finally, I noticed that I would not get the error if only a handful on apps were added to the base rom. So I made a backup, added some more apps, and re-tested for a while and if the error reappeared, I would go back to backup. I found out that Google Currents caused the error to appear. Same for Dolphin Browser HD and Firefox browser.

So for a moment I had only a handful of apps on the mood hd. After applying your fix (super detailed instructions, thank you!),I have installed some 40 apps including the offending ones mentions above and I have not seen the error in about 30 minutes. I will keep testing and update this thread if I encounter anything of significance.

Thank you so much again!

Ariyo


Hey all!

I've recently had problems with a Nook HD (16GB) with CyanogenMod 10.1, using bokbokan's Hybrid install. Not only me, but a few friend's and cousins; but unfortunately they all turned to me for advise. Eventually, I wrote up a guide for them to follow to solve the issue (as I was not with them). Now, I have decided to release this guide to all you guys/gals, in hope for this solution to assist you (if you too have similar problems)! :)

If you constantly get the message "Unfortunately, the process android.media.process has stopped." on your Nook HD using CyanogenMod, then please read on. :)

Semi-Permanent Fix to "Unfortunately, the process android.media.process has stopped."
This solution has been tested on the Nook HD, running CyanogenMod 10.1 (20130313, hummingbird) via the Hybrid installation.

1. Introduction/Notes
This fix has been categorised as "Semi-Permanent", as the initial aim was to permanently fix the issue, and although this currently acts as a "permanent" fix, the issue can still reoccur if triggered as a result of opening specific apps which rely on the "android.process.media" (after following this guide, finding apps which trigger the process to pop-up is quite rare). Therefore this fix has been declared permanent, yet acts as a temporary fix if the issue still persists (the issue can still occur in unfortunate scenarios/occasions). If the latter is true, I will aim to look for a further solution.

Unfortunately at this time, it is unknown what precisely causes the process to fail; but it is acknowledged it is related to a Google application, thus we attempt to minimise Google apps intervention into Android.

All the best with applying this fix and remember two things:
  1. It's a dead easy process, and I'm 100% confident that any person on the street who has the intellectual ability to read English will be able to perform this fix. So don't worry, it's nothing you need a master’s degree for.
  2. Ensure that you follow what I say 100% accurately; do not click any alternatives (for example, if I tell you to clear the "System Cache", and you cannot find the option, do not just clear anything with the word "Cache" - i.e. Do NOT clear the "Dalvik Cache", they are completely different). Ultimately, just make sure what I say, is what you click on-screen and nothing else. In this guide you will be booting into ClockWorkMod (CWM), and if you make any mistakes, it could cost you (i.e. lose Android on the tablet completely).

Without any further ado, let's skip over a section and get started.

2. Disable Google Sync
The process "android.media.process" is related to Google Sync (alongside being related to a lot of other processes; hence the term "media"). Therefore we will be disabling Google Sync, in order to minimise errors; you won't notice a difference in performance, and is not an important part of the system.

  1. Get your tablet at hand, and ensure the tablet's battery is charged at 20% at minimum, or above.
  2. Turn your tablet on (in CyanogenMod/Android), so that it's in a functional state (if not already).
  3. Thereafter, unlock your lock screen and go into "Settings". Scroll all the way down until you find the option "Google", besides a blue Google icon (under the "Accounts" category). Click on "Google".
  4. You will now see listed, all the accounts currently linked to the tablet. If there is only one account, click into it. If you have more than one account, click on the first listed account, and proceed to the next step.
  5. You will now be presented with all the data which is currently in sync with Google. Untick them all: So, "Browser", "Calendar", "Contacts", "Gmail" and "Sound Search for Google Play" should be all DISABLED/unticked.
  6. If at stage 4 (above), you have more than one Google account attached to the tablet, repeat step 5 until all accounts have been disabled sync.
At this point, after successfully conducting the above, you should now have Google Sync disabled on your Nook HD; thus reducing the likelihood of the error occurring. You may now exit settings on your tablet. However, we have not yet solved the issue, please read on.

3. Enabling Developer Mode
You may be able to skip this step, if you already see the selection "Developer Options" in your tablet's "Settings" (towards the bottom of the settings menu). If not, please read the following.
  1. Once again, go into "Settings" within your tablet.
  2. Scroll to the very bottom within settings, and the last presented option should be "About tablet", click onto it.
  3. Again, scroll to the very bottom of the "About tablet" screen. You should see the title, "Build number", followed by the details.
  4. At this stage, recklessly keep clicking the "Build Number". Eventually on screen you should be presented with a few messages, similar to: "Developer mode after 3 clicks". Constantly keep clicking "Build Number" until the message displayed states (similar to): "No need. You are already developer".
  5. At this point, you can now go back out of "About tablet", back into "Settings" and you should see the selection "Developer Mode".

Congratulations, you now have developer access to the tablet. For an average consumer, this is not necessary and is an extremely powerful set of options, which allows you to alter your tablet settings. We will only use this for one purpose, so please do not tamper with other settings in the developer menu.

4. Preparing to Boot into ClockWorkMod (CWM) Recovery
ClockWorkMod Recovery (CWM) is what made Android 4.2.2 on the Nook HD even possible, not only for the Nook, but for all Android-powered devices. It is extremely powerful, mis-clicks are not excusable within CWM, and with one or two clicks (at the most), you may accidentally remove the whole Android setup from the Nook; including all your data and apps. So, you must be extremely cautious after booting into CWM. As long as you follow this guide from now onwards 100%, you'll be fine. :)

  1. Again, go into "Settings" if not already. Scroll all the way down and select "Developer Options".
  2. The third option within the menu states "Advanced reboot", tick this by simply clicking it.
  3. Now, go back out of the developer menu. Go to your tablet's home screen, close all settings, and move onto the next section to boot into CWM.

5. Clearing Cache & Fixing Permissions via ClockWorkMod Recovery
Now that you're on your tablet's home screen, and you've completed all the above, you are ready to boot into CWM. Again, as warned above, you must follow this guide accurately, else you could erase the whole Android Operating System (OS). CWM should not be accessed by anyone who has no idea on what they're doing (so later, we're going to disable software-access; in order to avoid other users accessing CWM).

But for now, you're going to be booting into it. First, hold the power button on the tablet; until it provides a dialog. Click on "Reboot" (second option), and select "CWM Recovery" on the new selection. It is once again the second option. After selecting CWM, click "OK" and the tablet should boot into it momentarily.

Before you get started in CWM, you should familiarise yourself with the controls; which are basic, however do not support the touch screen (security measure).
  • Power Button: To go up one menu, for example if you go into "Advanced", to return to the original menu, you simple press the power key.
  • Volume Up/Down: These two keys are for navigation purposes, allowing you to scroll up or down the menu respectively. Use these keys to highlight your option.
  • Home/'n' Button: This is to select the current option, for example, if you're currently hovered over "Reboot system now", and press the 'n' key, your tablet would reboot.

5.1. Clearing Cache Partition
First, we're going to clear the cache on the tablet. You will not lose any data, and this process won't affect your daily usage at all (nothing will change the daily performance of your tablet within this guide).

Now that you're in CWM, and you're familiar with the controls, we can begin clearing the cache.

  1. Navigate down, so that the selector highlights "wipe cache partition". Ensure that you have highlighted this option, and not the one above (they both have similar wording). Please ensure the correct option has been highlighted.
  2. Press the Home key, the 'n' key located at the front-bottom of the tablet to select this option.
  3. You will now be presented with another selection menu, mainly consumed by the option "No" (a security feature, to avoid incorrect choices).
  4. Navigate down, until you highlight the option "Yes - Wipe Cache" and select it. Please once again ensure it states "Wipe Cache" and nothing else.

After a few seconds, the whole cache partition on the tablet will be cleared. We're now ready to fix the permissions in CWM, so let's move to the next section of this document.

5.2. Fixing Permissions
Whilst you're still in ClockWorkMod Recovery (CWM), please do the following to fix the current permission set. This is the final stage of solving the issue.

  1. The last option in ClockWorkMod is "advanced", and should be displayed on your screen. Scroll down, highlight and select this option.
  2. The last option within the advanced menu should state "fix permissions". Highlight and select this option. If you're provided with a confirmation screen, select yes, if not, ignore this sentence.
  3. This process can take up to 2-5 minutes to complete. Once complete, if you are returned to the original menu, you should see the first option as "reboot system now". If not, press (do NOT hold) the power button until you do.
  4. At this point, select "reboot system now" and safely return to your Android setup.

As soon as your tablet boots back into Android, you'll see a message, stating that your tablet applications are being upgraded. This is the simple process of reinitiating your apps, after the cache was cleared. Dependant on the amount of apps installed, this process may require a few minutes.

6. Congratulations!
You have made it to the end of this guide, and hopefully the error has stopped occurring; regardless, it should occur significantly less during use.

If the error still persists after usage, unfortunately this method was unable to provide a permanent solution, and may act as a temporary one. To temporarily solve the issue once again, when necessary, you may re-follow this guide.

I have found that this is a permanent fix for my Nook HD, and I hope it is for you too! All the best, any problems, please let me know. :)
 
  • Like
Reactions: HiddenG

HiddenG

Senior Member
Nov 5, 2011
160
46
0
Manchester
No problem at all Ariyo! :D

I'm glad I could assist, and I extremely appreciate your response and testing; I'm definitely sure it will assist in turning this solution permanent for all users. I understand this problem is way too irritating, and frustrating too; but unfortunately, for some user's this is a temporary fix. I hope it's been going well so far for you. :)

I'll be doing my best to provide a permanent solution to those who are current in this situation. :)

Thank you again for your response. :)
 

ariot

Member
Sep 30, 2010
25
9
0
You are a life saver! Just bought my nook hd last thursday and immediately put CM 10.1 on it. I had about 5 hours of fun with it and then this error massage started ruining my enjoyment. I have tried clearing all manners of caches, data resets, reinstalling CM10.1, and even changed my SD card and nothing worked. Finally, I noticed that I would not get the error if only a handful on apps were added to the base rom. So I made a backup, added some more apps, and re-tested for a while and if the error reappeared, I would go back to backup. I found out that Google Currents caused the error to appear. Same for Dolphin Browser HD and Firefox browser.

So for a moment I had only a handful of apps on the mood hd. After applying your fix (super detailed instructions, thank you!),I have installed some 40 apps including the offending ones mentions above and I have not seen the error in about 30 minutes. I will keep testing and update this thread if I encounter anything of significance.

Thank you so much again!

Ariyo
Just to give an update. I am still getting this error, but the rate is like 10% of the rate before applying this fix. I am going to re-do my SD card from scratch and re-install CM, then apply this fix and will report back. Thank you
 

ariot

Member
Sep 30, 2010
25
9
0
Just to give an update. I am still getting this error, but the rate is like 10% of the rate before applying this fix. I am going to re-do my SD card from scratch and re-install CM, then apply this fix and will report back. Thank you
I was finally able to get rid of this error when I re-created my SD card from scratch using files from here:

http://forum.xda-developers.com/showthread.php?t=2063968

and instructions from here:

post 48 by Diogenes5 on this page http://forum.xda-developers.com/showthread.php?t=2097731&page=5

It appears I may have not had the latest CWM. It's been 4 days of heavy use and I have not had the issue again. Before, it happened like 10 minutes after startup and every 2 minutes thereafter. It was very frustrating. Hope this helps the apparently few people with this issue.

Ariot
 
  • Like
Reactions: HiddenG

HiddenG

Senior Member
Nov 5, 2011
160
46
0
Manchester
I was finally able to get rid of this error when I re-created my SD card from scratch using files from here:

http://forum.xda-developers.com/showthread.php?t=2063968

and instructions from here:

post 48 by Diogenes5 on this page http://forum.xda-developers.com/showthread.php?t=2097731&page=5

It appears I may have not had the latest CWM. It's been 4 days of heavy use and I have not had the issue again. Before, it happened like 10 minutes after startup and every 2 minutes thereafter. It was very frustrating. Hope this helps the apparently few people with this issue.

Ariot
That seems amazing! Great find! Thank you for your post, I'm sure it'll help a lot of members! :)

However, please may I ask? You're currently not using a Hybrid install on your HD, correct? The ClockWorkMod/SD Image provided on the first link of your post is for the Pure Install (link after you stated "SD card from scratch using files from here"), not Hybrid (as stated on bokbokan's post: "CWM bootable image for pure SD install", source). So, the CWM from bokbokan's post is not for the Hybrid install, but for the Pure Install (installed completely on SD).

Without the Hybrid CWM, and following Diogenes5's guide should still provide you a Pure Install; not a Hybrid one.

Of course, this is no major problem. If anything, it's amazing! I'm glad you stumbled across it. So it seems as if the problem only occurs on Hybrid installs, where the Pure Install is perfectly unaffected by the issue. Thank you for your response, and research efforts! It's greatly appreciate by the community, and myself. Thank you again!

I'm not too sure if I can change my current set up from Hybrid to Pure, as I'd prefer to keep my current set-up as is (it's actually my mother's). Therefore I'm still looking for a solution for a Hybrid setup. I believe I may have something; but may require sacrificing certain features. I'm still testing it out, and once ready, I'll update my initial post.

Again, I appreciate your response. I appreciate it all! :)
 

konelyn

New member
Jul 19, 2014
1
0
0
install s4 music player

i ve installed s4 music player apk on my device-s3 gt-i9300 4.2.2.- CM(mod) 10.1.2,. But music player has stoped whenever I click it. Pls let me know how to fix it. Cos i d to install s4 stock music player on my device. Thanks!
 

Brian2489

New member
Sep 16, 2014
4
0
0
Hi,

I just updated my Nook HD to CM 11-20140916-SNAPSHOT-M10-Hummingbird and am now getting the "Unfortunately, the process android.process.media has stopped" error.

I ran through the instructions in this thread but was unable to complete the last step as the version of CWM on my Nook does not have the fix permissions option within the advanced menu.

The gmail app crashes with this error every time I launch it, but other apps, including other google apps such as drive, will launch.

Is anyone else getting this error after the update?

Hopefully this is something a future build will fix but if anyone knows of something I can do to fix this please let me know :)

Can I roll back to a previous build of CM11 if it continues to be a problem?

Thanks

Brian
 

julian67

Senior Member
Nov 8, 2013
136
63
48
Brighton
Hi,

I just updated my Nook HD to CM 11-20140916-SNAPSHOT-M10-Hummingbird and am now getting the "Unfortunately, the process android.process.media has stopped" error.

I ran through the instructions in this thread but was unable to complete the last step as the version of CWM on my Nook does not have the fix permissions option within the advanced menu.

The gmail app crashes with this error every time I launch it, but other apps, including other google apps such as drive, will launch.

Is anyone else getting this error after the update?

Hopefully this is something a future build will fix but if anyone knows of something I can do to fix this please let me know :)

Can I roll back to a previous build of CM11 if it continues to be a problem?

Thanks

Brian
Yes, I ran into this on upgrading my Nook HD from nightly to M10. I then tried a clean install of M10 with same result. I reverted to the nightly of September 13th as this had worked fine. I didn't try 14th or 15th nightlies as there is nothing in the changelogs that matters on a Nook. Anyway the nightly is great, just download it onto your sd card and install from recovery. The snapshot M10 unfortunately seems to be a complete lemon.
 

Brian2489

New member
Sep 16, 2014
4
0
0
Hi julian67,

Thanks for your reply.

I rolled back to the 13th Nightly and everything is back in action.

I didn't bother doing a clean install and haven't encountered any errors yet :)
 

csiman

New member
Sep 19, 2014
1
0
0
Cool, thanks for the heads up.
Just turned my nook on and automatically a CM updater kicked in, updated and rebooted my Nook HD+ and now I get this error all the time

please tell me I dont have to reinstall everything from scratch to get it working again?

I just want to back out this bug ridden update

Any help appreciated

Thanks
 

julian67

Senior Member
Nov 8, 2013
136
63
48
Brighton
Just turned my nook on and automatically a CM updater kicked in, updated and rebooted my Nook HD+ and now I get this error all the time

please tell me I dont have to reinstall everything from scratch to get it working again?

I just want to back out this bug ridden update

Any help appreciated

Thanks
Download a nightly, for example the nightly of 17 September is fine, onto your external microSD card. Boot into recovery, install the nightly zip, reboot. Your Nook HD will be working again. Once you're sure all is back to normal I suggest you again boot into recovery and then make a backup.