[Q] android.process.media error after CM 10.1 - Barnes & Noble Nook Tablet

First, I apologize for the inevitable incorrect use of terminology - I'm trying my best.
After hours and hours of reading up, I finally attempted to internally install CM10.1 to my Nook Tablet 8GB v 1.4.3. I appreciate all the helpful posts on this forum, and primarily used http://forum.xda-developers.com/showthread.php?t=2037368 and http://forum.xda-developers.com/showthread.php?t=2056626 to go through the steps. I hit a few snags along the way, but in the end I think I was successful.
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Android Version 4.2.2
CyanogenMod Version 10.1-20130421-NIGHTLY-acclaim
Happy to provide any more details that would be helpful. And many thanks in advance.

eyeshaveit said:
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Click to expand...
Click to collapse
This happened to me after I dirty-flashed CM 10.1 over another CM 10-based rom. Let me see if I can remember what I did to make it go away... I think it has something to do with a file or process that Android uses to index/keep track of media files on internal and external sd cards, and deleting or wiping the cache or data on that particular process fixes things. I will do some checking around and post back here if I (re)find more specific info.
EDIT: Found it, I think... Do a force stop, clear data, and clear cache on the "Media Storage" app, then reboot and see if it goes away.

Sooo... did it work?

johnseeking said:
Sooo... did it work?
Click to expand...
Click to collapse
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?

eyeshaveit said:
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?
Click to expand...
Click to collapse
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.

datallboy said:
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.
Click to expand...
Click to collapse
I tried to go back to the beginning to see what I did wrong - hoping to fix the problem but also trying to learn. I'll explain in a bit of detail...
Tried to follow the process outline here: http://forum.xda-developers.com/showthread.php?t=2037368. I was able to access root using NT16or8gbV47SDimagefile.img, but was unable to get any further as it kept saying "No files found" when trying to flash rom and gapps zipped files. After trying multiple reformats, partitions, etc, I abandoned following this process. (Of note, I did make sure that debugging and allowing installation from unknown sources were active - to no avail.)
I then followed this process: http://forum.xda-developers.com/showthread.php?t=2056626. In addition to Step 6 - "Wipe data and factory reset," I also cleared cache and dalvik cache as suggested. Everything else went very smoothly. I've now been running CM 10.1 for a few hours without any error messages. I'll report back anything that pops up over the next few days.
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
Thanks a million to all.

eyeshaveit said:
...
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
...
Click to expand...
Click to collapse
As long as you have SDcard-based CWM available for recovery purpose (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31) you don't really need to flash CWM internally. But if you'd like to flash it internally you can grab a flashable CWM zip file from Succulent's repo http://goo.im/devs/succulent/acclaim/recovery and install it using SD-cased CWM (just like you had installed the ROM/gapps zip files except there is no need for wiping cache/data & doing factory reset in this case).

Related

[Q] the process android.process.acore has stopped unexpectedly

Gtab- Stock 3358.
Previously I had Stock 3358 and rothnics enhancement pack. I installed an app from the market. As soon as I started the app the gtab screen went blank. Then the TapnTap logo as if it was rebooting then within 2 sec I was back at the home screen. If it rebooted it was a heck of a fast reboot.
then I started getting the error. Everything except stock email and settings work. But the error message pops up every few seconds. I can't go to settings and wipe. So I attempted to install stock 3358. it went fine but problem persist. Still can;t go to settings to check version or do a afactory reset.
Any and all help is appreciated.
+1
I had same problem and after debating the right courses to take, I nvflash'ed the device and started over again.
Still would like to understand that caused that error ?
This usually occurs as the result of contacts in your contact folder with blanks in the name fields. Delete any entries with blanks and you should be good to go.
PS. You will get faster resolution if you search before posting as this has been asked and answered several times in past week.
I have same problem...."The process android.process.acore has stopped unexpectedly. Please try again"
I went into my google account, deleted or put names in contacts that didnt have names, rebooted and still having problem. I tried going into the data/data file, but there was no data file to delete as indicated on other threads. There is not an easy to find thread for this problem. Please help or at least direct me.
Thanks!!!
I never had any contacts saved. Regardless I cannot even open the contacts folder to add/delete anything.
I am having problems with, email, contacts, settings. as soon as I attempt to open any of the above it gives the FC message and takes it back to home.
On the other hand I called Gtab support. As soon as I told the probelm the lady asked me if I could go to settings. Once I told her no I cannot she said you have to send the unit back for repair. She said that she helped another individual yesterday with exact same issue.
On aside note I was able to delete most of my apps using ES file explorer.
@Bekit @rothnic or other senior members is there any solution beside nvflash. I am a newbie.
thanks.
I had the same problem in February and fixed it by searching this forum and finding pieces to put together a solution. The rest of this message is what I posted back on 2/24/11. I think the important part is to repartition your SD card and clear all user data. I have had no problems since I did this fix.
Good luck.
I have had my GTablet since early December and have been running the Stock Enhancement since early January. I have had no problems except for a very occasional unexpected stop. It was never a real problem.
Yesterday I started getting the android.process.acore error literally anytime I tried to use any application. To my knowledge, I had not installed anything recently that would account for this.
The good news is that I followed multiple threads here and came up with what seemed to be a reasonable solution.
I installed Clockwork and reset the partition to 2048/0 as suggested by several posts. I also cleared everything that I could clear using their menu.
Then I installed NVFlash which I believe put me back to the plain vanilla factory OS. (I also think this wiped out Clockwork Mod but I'm not positive.)
I got the "update available" message and did the OTA update of the OS.
Then I installed the TnT Stock Enhancement update and applied the Market Fix.
Everything seems back to normal now.
I want to thank all of the forum members who posted the various instructions that allowed me to piece together this solution.
I realize that not everyone has the same issues when problems occur so there isn't one single fix that is right for everyone. I didn't really understand that until I had this problem. I feel lucky that I've had relatively no problems.
I have to admit that I'm looking carefully at the Motorola Xoom because I suspect it has a much more stable hardware/software infrastructure but I would rethink that if the Viewsonic folks would be more forthcoming about their plans to support upgrades for the GTab. I can live without 3G if I have stability.
Thanks again to all of you experts out there in xda-developers forumland.
Stuck SD card
I am having the same problem and tried to do the restore from the SD card and now the card is in the slot and I cant access the settings to eject it. to run the clockwork mod is there any way to force it to boot the clockwork mod?
For me, Clockworkmod "wipe data/factory reset" eliminated the pesky force close message about android.process.acore that several of us seem to have. NVflashing & Contacts data field corrections did not work for me. The problems seemed to come up after downloading an app from market.
Running VEGAn 1.00 beta 5.1.1 supplement, and happy!
got this last night/this morning as well. from other parts of the forum i went with the fix of using titanium backup to wipe data related to contacts (believe there were three separate items, contacts, contact synch, and something else). btw, I am running VEGAn 5.1.1.
after wiping the data, everything has appeared normal.
hope that helps.
I called CS yesterday. They help me delete most of the apps that I downloaded to see if that will fix the issue. That also helped in eliminating any personal data left behind in case I have to RMA the unit.
that makes my tablet completely stock. I don't have market any more. So can't get clockwork rom manager etc. Bigger probelm is the onscreen keyboard doesn't work either gives the error message.
I did some reading on how to NV Flash the device. Still trying to understand the process.
I have two options
1. NV flash the device and hope that everything still works.
2. I bought sears insruance. Just return the device and then be done with it.
Any help is much appreciated.
My experience level is limted to flashing stock and enhancement packs using the Power and + buttons.
You don't want to use the clockwork in Rom Manager. It doesn't work for the G Tablet.
Here are a couple other options off the top of my head...
1) cwmod for install from Micro SD card http://forum.xda-developers.com/showthread.php?t=865245
2) Try calkulin's format all http://forum.xda-developers.com/showthread.php?t=985705
flanghor said:
For me, Clockworkmod "wipe data/factory reset" eliminated the pesky force close message about android.process.acore that several of us seem to have. NVflashing & Contacts data field corrections did not work for me. The problems seemed to come up after downloading an app from market.
Running VEGAn 1.00 beta 5.1.1 supplement, and happy!
Click to expand...
Click to collapse
same thing with me. I downloaded a few apps and then I got it. Did the data wipe thing. Came back in and I am still getting the error. Not happening every 5 seconds, but still getting it.
okay, this is strange. I did the data wipe and I was still getting this error. After doing the market fix and got all my downloads available, I noticed that I am only getting this error when I hit the HOME button.
I hit the Home button and the error comes up, then the Android Market comes up. This only happens now when I hit the Home button. Error, Market comes up and I have to hit the Home button again to get home.
HELP!
only the home button
confirmed. Working on this the last 30 minutes, I am only getting this error when hitting the home button.
@ K J Rad
I downloaded caulkins format all zip. Now this may sound a silly question. Do I flash it like changing its name to update.zip and include the recovery file?
2nd question is if I am able to flash it successfully can I install the stock rom?
hipBob said:
got this last night/this morning as well. from other parts of the forum i went with the fix of using titanium backup to wipe data related to contacts (believe there were three separate items, contacts, contact synch, and something else). btw, I am running VEGAn 5.1.1.
after wiping the data, everything has appeared normal.
hope that helps.
Click to expand...
Click to collapse
Just wanted to say this single step worked for me as well.
Ok. Finally got rid of the problem.
First I attemted NVFlash. After some intial strugle setting up the drivers etc on windows got it to work. Everything worked but still had the exact same process.
B/w I noticed superuser still there. I thought NV Flash will bring it to out of box. Used Bekits image.
After some more reading took the plunge and did CWM internal. Dide wipe data. Rebooted and got it working again.
Again pardon my ignorance but do I have to manually update to 3358. And if I do it go stock would it get rid of CWM. How do i get it off the machine?
I would like to prepare for the OTA.
Please advise.
B/w it was fun going through the process.
Ok. Finally got rid of the problem.
First I attemted NVFlash. After some intial strugle setting up the drivers etc on windows got it to work. Everything worked but still had the exact same process.
B/w I noticed superuser still there. I thought NV Flash will bring it to out of box. Used Bekits image.
After some more reading took the plunge and did CWM internal. Dide wipe data. Rebooted and got it working again.
Again pardon my ignorance but do I have to manually update to 3358. And if I do it go stock would it get rid of CWM. How do i get it off the machine?
I would like to prepare for the OTA.
Please advise.
B/w it was fun going through the process.
Glad you got it working. Installing the stock 3588 update will replace the bootloader and removes CWM. That should leave you as close to real stock as you can get.
Oh, and welcome aboard ;-)
hipBob said:
got this last night/this morning as well. from other parts of the forum i went with the fix of using titanium backup to wipe data related to contacts (believe there were three separate items, contacts, contact synch, and something else). btw, I am running VEGAn 5.1.1.
after wiping the data, everything has appeared normal.
hope that helps.
Click to expand...
Click to collapse
Thank you very much, that was an incredibly painless fix. Worked on TnT-Enhanced v3.1.4b

[Q] Market Apps Fail to Download

A HUGE thanks in advance for any help you can offer:
I have a Viesonic G-Tablet, and I've flashed a couple of different ROM's on it - TNT Lite 4.4 and VEGAn-TAB 7.0 RC1.
LOOOOONG story short:
Tried to install Ubuntu, no luck.
Downloaded ZPad to try it out, installed. Didn't like it, used ClocworkMod to recover to a previous TNT Lite 4.4 install. From there, reflashed to Vegan...
And that's when the problems started. Namely, Market no longer works properly. None of my downloads are successful. It gives a "Download error - Download was unsuccessful, please try again."
So, after trying again to go back to TNT Lite and having the same trouble, I NVFlashed back to stock, wiped EVERYTHING per the directions on XDA, in the order prescribed - did everything by-the-book, and still no luck on any ROM. TNT Lite, Vegan - both of them adamantly refuse to download anything from the market.
I've searched to my wits end not only in this thread, but others as well. I've reset the data, reset the cache, uninstalled the market update - you name it, I've tried it.
Could it be your internet connection? Do other devices on your network download from the internet fine?
Thanks for the question. I guess I should have been a little more specific: Yes, great connection. I can browse the web fine, even download from Amazon's appstore - but that's where it ends. The weirdest thing is that I have noticed that I can download Firefox from the Marketplace, but literally - that's it. Nothing else, and I've tried close to 40 different apps now. All fail to download.
I've tried clearing the cache, etc...
I was even desperate enough to pretty much do a system wipe and come up clean. I used ClockworkMod to format everything - even the SDcard. Made sure to set the partition size to 2048/0, the whole nine yards. Wiped all the data, cleared/formatted cache, so I'm at a loss.
*UPDATE 4/18/11 - On a whim, I decided to use ClockworkMod to reset my User Data, and signed my tablet in under another Google account I had. As I type this, I'm downloading all the apps that I was unable to download with my "usual" account. So maybe there's a bug on Google's side? How would I even go about fixing that?
I'm having this same problem. NVFLASH and reFLASH numerous times and still no luck can someone please help. Can't install anything from market at all. it download and as soon as it finish dl and start to install it will restarted itself and nothing happen. please help. THanks
Exact problem I'm having. I've tried five different roms, from Vegan to CM7, to older TnT's and Calkulin's, nothing will let me download and install from the market. I did yet another full NVFlash last night and repartitioned the tablet, still no luck after flashing CM7. It started off allowing me to download a few dozen apps then giving me the download error, but now the first app I try gives me that.
Did anyone else here come down from TwoTapsX or another 1.2 based rom? Seems to me the issue started right about the time I NVFlashed down from that.
kitsunisan said:
Exact problem I'm having. I've tried five different roms, from Vegan to CM7, to older TnT's and Calkulin's, nothing will let me download and install from the market. I did yet another full NVFlash last night and repartitioned the tablet, still no luck after flashing CM7. It started off allowing me to download a few dozen apps then giving me the download error, but now the first app I try gives me that.
Did anyone else here come down from TwoTapsX or another 1.2 based rom? Seems to me the issue started right about the time I NVFlashed down from that.
Click to expand...
Click to collapse
tvguyjohn said:
*UPDATE 4/18/11 - On a whim, I decided to use ClockworkMod to reset my User Data, and signed my tablet in under another Google account I had. As I type this, I'm downloading all the apps that I was unable to download with my "usual" account. So maybe there's a bug on Google's side? How would I even go about fixing that?
Click to expand...
Click to collapse
I just tried this myself, sure enough I can download with another Gmail account, but not my main one.
This has to be an issue with Google...I am having the same issue also.
How the hell did I quote myself up there?
Mine is downloading again, all I did was sign in as my backup account, wipe data and dalvik cache, reflash then fix permissions. When i logged in again it worked. Don't know which step actuallly fixed it.
I just deleted the data under app management and they started working again for me.
Sent from my PC36100 using XDA Premium App
I had the same. Uninstalling Flash player seem to have solved the issue for me
Me too
I seem to have the same problem however I do not get an error message at all, I just see the application in the notification bar preparing to download except instead of even downloading it basically just disappears. I had this problem ever since installing Vegan tab 5.1.1.
I had the same problem...drove me crazy...finally figured out that you can just log intp the market on my laptop and install everything from there....

fix: insuffiencient space for apps (google market)

Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
duble08 said:
Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
Click to expand...
Click to collapse
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
k2buckley said:
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
Click to expand...
Click to collapse
no problem! this community has helped me TONS in the past, even though i haven't said anything about it (due to not being able to post in developer threads yet). I reflashed and wiped my phone about 4-5 times before realizing that the cache had to be cleaned AFTER the install and first boot of the new rom, and all the dev's kept stating it was from not wiping prior to flashing, which i did every time. Hopefully this will save some people time and headaches and i'm sure the dev's will soon find a fix to this, as they seem to work very fast at finding bugs and cleaning em up.
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Welcome to xda.
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
newkidd said:
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
Click to expand...
Click to collapse
that would make a lot of sense as well - if that's the case, maybe people should let google market crash the cache before they clear it out again? that's what i did when i got it working... it was one of those things where i just watched and wondered, "is it going to do it all this time?", and of course when it didn't, that's when i discovered re-clearing the cache again in recovery fixes it. I noticed that by clearing the application cache (settings/applications/manage programs/market/clear cache) the problem still persists, and the only way to get google apps to install again is by clearing cache in recovery, which made me think it was an installation/boot thing. but i'm still learning, like many of us here
thanks for the input!
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
this is an issue i noticed as well - i had to re-add my apps manually after it only added 24 of the 120 i had going. but hey, beggers can't be choosers, and i'm just mostly happy that i got a new rom going with everything functioning properly within 2 weeks of the phones release!
If anyone knows how to re-start the app sync succesfully without space errors, that might be good info to include in this post
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
-viperboy- said:
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
Click to expand...
Click to collapse
Recovery. Downloading another app doesn't rebuild the cache either. Now it's gotten to the point where no ROM will restore any of my apps at all, it basically thinks I've never downloaded anything. So now I've gotta try and remember the 130 or so apps I had installed.
Not complaining, just an observation. One of the caveats of rooting a new device
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
empiire said:
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
Click to expand...
Click to collapse
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
You can also go into terminal emulator and delete the Download.apk files in the cache.
You'd think Google would be a little smarter at this. All the market would need to do is download fewer apps at a time, as the files are cleared once the installation is complete.
Sent from my PG86100 using XDA App
I feel a s0be market fix coming on. Although I have not seen the issue, you could pwn the cache and symlink it out of /data and into /system. A genious linux guy, seriously, genious, made this hack back on the hero, fixed market download errors EVERY time.
See this post:http://forum.xda-developers.com/showpost.php?p=11055157&postcount=4650
If you like it, go find s0be and thank him
duble08 said:
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
Click to expand...
Click to collapse
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That won't make any difference if there is no room to actually store the downloads. Downloads from the Market go into /cache while downloading and then move to /data/app or /system/app, depending on the app. Hence why clearing cache fixes it.
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
duble08 said:
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
Click to expand...
Click to collapse
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
laie1472 said:
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
Click to expand...
Click to collapse
I tried something similar, but not exactly like you said earlier. I set my accounts to sync, but immediately went into the market while it was syncing, and cancelled everything. This would've still left the user picking each app to re-download one by one, because I believe there's no way to restart the app sync. I ended up buying titanium, and used that to put all my apps back on - its much less of a headache.

beanstalk 4.4 kitkat installation issues

so i installed cwm touch on my device,
factory reset
clear cache
clead dalv cache
format system
install beatstalk and get this error
E: can't copy meta-inf/com/google/android/update-binary
installation aborted
can anyone help me
i've tried from both my internal and external sd card
What version is CWM? You need 6.0.4.3.
Also, try re-downloading the rom and gapps.
Error I717 vs i717
I have installed CWM touch 6, wiped (2x) then goto install and get the error that "This rom is for I717, and your device is i717" I have formatted the sd card and downloaded 2 different versions of the 4.4 and both give the same error. Also when I try to install others roms I get an error about "Bad" file. Any suggestions?
Only bug I see is YouTube does not work. I uninstalled and reinstalled updates and also tried force stopping the app.
It will play the first video I choose but then it won't play anything else.
Otherwise, Great Rom!
ddochi11 said:
What version is CWM? You need 6.0.4.3.
Also, try re-downloading the rom and gapps.
Click to expand...
Click to collapse
cwm touch 6.0.4.3 and standard cwm 6.0.4.3
i've downloaded cm11 and installed beanstalk 4.4 downloaded rom and multiple version of the rom and all the same thing
Maybe try formatting the sd card
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Installed this ROM and GAPPS from the dev thread for t0lte device.
First issue: AOSP keyboard force close. Looked up solution - install Google KB via APK. Ok, managed to do that, then set it to default. The AOSP FC message still appears, although not as frequently as before, and at least Google KB works.
Next issue: No data, no phone network.
Next issue: Went to set up APN, entered information, Menu > Save, APN did not save.
Not sure what the problem(s) is/are. Wanted to try this ROM but maybe I'll wait a while to see if anyone else runs into the same issues and if so, if they get fixed.
Permissions?
Well apparently the APN issues are caused by any 4.4 ROM if it is installed using TWRP.
So I have tried a couple of 4.4 ROMS using CWM and yes, my issues with APN didn't crop up. However, if I used another ROM that wasn't 4.4 (Paranoid) and then restored a backup of a 4.4 ROM, the APN again disappeared and was not modifiable. Anyway it's not the fault of any particular ROM, it appears.
As for the other issues, I have not gone back to Beanstalk since I posted my other message. Mostly because I don't really want to have to start from scratch every time I want to switch to a KitKat ROM (unless coming from another KitKat ROM, I presume - although I haven't ruled out that any recovery from backup wipes out APN).
Hopefully between the ROM developers and the custom recovery makers, this gets resolved and I can get back to feeding my ROM addiction.

Nook Tablet, 16 GB, AOSP Android 7.0

Followed all the steps in the detailed "[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet". During the process I was unable to install the suggested open_gapps-arm64-7.0. Tried several times, so right now I ended up with a mean and lean android system with 3 icons on the home screen. .
I'm a beginner doing this. So I attempted to copy superuser apk and the play store apk via usb connection to no avail. Don't even know where they ended up. I'm able to do a google search but it does not retain any bookmarks I'll be making, the reason being explained as I'll need an updated bookmark apk. (Which one??) and how do I install that?
Anyone out ther who can guide me in the right direction? Much appreciated. I do understand a little of the jargon being used in the forums here.
leenaud said:
Followed all the steps in the detailed "[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet". During the process I was unable to install the suggested open_gapps-arm64-7.0. Tried several times, so right now I ended up with a mean and lean android system with 3 icons on the home screen. .
I'm a beginner doing this. So I attempted to copy superuser apk and the play store apk via usb connection to no avail. Don't even know where they ended up. I'm able to do a google search but it does not retain any bookmarks I'll be making, the reason being explained as I'll need an updated bookmark apk. (Which one??) and how do I install that?
Anyone out ther who can guide me in the right direction? Much appreciated. I do understand a little of the jargon being used in the forums here.
Click to expand...
Click to collapse
I'm sorry to tell you that those are the wrong GApps for the hardware. I will update the original instructions. What you need are the arm GApps, not the arm64 (remember, this is OLD hardware). The filename of the zip I used is open_gapps-arm-7.0-pico-20170310.zip
At this point, having done some fooling with the system, it's best to start the entire process over. That will give you the most stable result. You cannot install the PlayStore and have it function without GApps, so just forget that part. The superuser file I mentioned is a must, once you get the PlayStore working.
The Bookmark provider apk is already on the device. Re-read the second post in the instructions. You just have to tap to install it, for some unknown reason.
Thank so much for your quick response. You were absolutely correct that I was installing the wrong gapps, so I started over again with the 7.0 stock (error message), the nano (same thing) and finally the pico and that one worked. By that time I hit the sack. I found that out shortly after I posted the message. I kept reading and reading the instructions and completely overlooked the GAPPS choices I had. Even a very cryptic error message popped up that said something about "incompatible" and "arm". Duhh. So what I'm going to do is wipe it clean again (3rd time) and reinstall everything so I can do it in my sleep.
Regards
leenaud said:
Thank so much for your quick response. You were absolutely correct that I was installing the wrong gapps, so I started over again with the 7.0 stock (error message), the nano (same thing) and finally the pico and that one worked. By that time I hit the sack. I found that out shortly after I posted the message. I kept reading and reading the instructions and completely overlooked the GAPPS choices I had. Even a very cryptic error message popped up that said something about "incompatible" and "arm". Duhh. So what I'm going to do is wipe it clean again (3rd time) and reinstall everything so I can do it in my sleep.
Regards
Click to expand...
Click to collapse
If you reformatted data as f2s, you might need to change it back to ext4 before you can do a successful wipe. Just a thought.
nmyshkin said:
If you reformatted data as f2s, you might need to change it back to ext4 before you can do a successful wipe. Just a thought.
Click to expand...
Click to collapse
I'm lost. All I did during the previous wipes, went into Advanced Wipes and cleaned out everything. Did.n't format. So are you saying I format first (ext4) and then do a complete wipe? The last time I booted it seemed to be very unstable. Looked like an invisible finger was touching the screen. Jumped all over the place.
leenaud said:
I'm lost. All I did during the previous wipes, went into Advanced Wipes and cleaned out everything. Did.n't format. So are you saying I format first (ext4) and then do a complete wipe? The last time I booted it seemed to be very unstable. Looked like an invisible finger was touching the screen. Jumped all over the place.
Click to expand...
Click to collapse
OK, I read your instructions again and think I know how to go about it. If all goe well during the installation ad it still seems unstable when booting I might ask for help again.
Thank you
leenaud said:
OK, I read your instructions again and think I know how to go about it. If all goe well during the installation ad it still seems unstable when booting I might ask for help again.
Thank you
Click to expand...
Click to collapse
Me again. Everyting installed without a problem. Was able to get a couple apk from google plastore. Having said that, I also installed ES filemanager thinking it would give me root access. (no go.) No option under the developers option either. So gave up on that. Also I noticed that depending what apk I loade, the response time was rather slow. Also for no reason at all it came randomy up with "shutting down" messages. And it seems to execute some stored touch screens as it was going all over the place. At this point I'm going to be looking for something else. Again thank you for your help
leenaud said:
Me again. Everyting installed without a problem. Was able to get a couple apk from google plastore. Having said that, I also installed ES filemanager thinking it would give me root access. (no go.) No option under the developers option either. So gave up on that. Also I noticed that depending what apk I loade, the response time was rather slow. Also for no reason at all it came randomy up with "shutting down" messages. And it seems to execute some stored touch screens as it was going all over the place. At this point I'm going to be looking for something else. Again thank you for your help
Click to expand...
Click to collapse
Sorry it didn't work out for you. It continues to perform very well for me. Seems like each piece of hardware has its own quirks.
Is this for the Nook 2016 or 2018 hardware versions, or does it work with both?
Goggles2114 said:
Is this for the Nook 2016 or 2018 hardware versions, or does it work with both?
Click to expand...
Click to collapse
Are you talking about the firmware upgrades for the original Nook Tablet or thinking about the various newer devices called by the same name?
This is for the OLD Nook Tablet BNTV250.

Categories

Resources