[Q] android.process.acore stopped and UIDs inconsistent - Verizon Samsung Galaxy S III

I'm not sure exactly what caused all of this but i'll give some background.
* Updated from Hyperdrive RLS8 to Hyperdrive RLS9 with Zues Kernel.
* Forgot to put new ROM on SD Card after I wiped, so I plugged my SD card into a external card reader and put rom on, then re-inserted my SD card to the phone
*Installed ROM with no problems and ran all day with it.
About 12 hours in I started getting "Unfortunatly, the process android.process.acore has stopped" after I was toggling some ROM settings. I believe when I was changing the governor or doing system tweaks with System Tuner. The message appears whenever I try to do anything with my phone most the time taking back to the home screen rendering my phone unusable.
After some googling, many said if you clear data on the Contacts Storage system app it fixes the problem. Problem is my phone won't let me clear data on it and the reported size of Contacts Storage is 1.56TB (which obviously can't be right). So I tried to reinstall that system app, no luck there either.
So then I tried full wiping and re-installing the ROM (many different times with different ROMs [4.1.1 and 4.1.2] and settings each time) and every time I boot up I get: "System UIDs Inconsistent:
UIDS on the system are inconsistent, you need to wipe your data partition or your device will be unstable. With a button saying: I'm Feeling Lucky"
When you hit the button the phone just boots normal but the android.process.acore message still appears.
I have also tried wiping my external SD card and reinstalling, did not help either.
Anyone have any ideas?
Thanks in advance!

Well I had to unroot and go back to Stock. Unfortunately I'm on the road and my hotel wifi blows, so 3 times my md5 for a 1.2GB file was wrong. Which took about 4-6 hours to download each time.
Ended up flashing an OLD stock LF2 that I still had lying around. Then bringing it back up to current. What a pain in the ass!
Is it just me or is it every time I screw with custom Kernels they are nothing but headaches?
I think i'll stick to stock kernel from here on out.

You may have gotten a virus, malware, or something, the button "I'm Feeling Lucky" sounds suspicious.

It used to happen on my droid x but haven't seen it on my gs3. It's not a virus but I don't know the fix.
Sent from my SCH-I535 using xda app-developers app

Probably the cleanest solution HERE

Related

Rescanning and "losing" time?

I am on stock + rooted/3e (recently decided to go back to stock due to random data or other issues).
I have tried rewiping a few times now but the problem persists, which is:
It does the "scanning for media" several times, not just once now. Sometimes it will do it randomly while I'm using the phone.
The time keeps settings to 4 hrs ahead. I check the time zone, its right. I can fix the time by unchecking "auto" and rechecking it, but then I'll go to use my phone again later and the time is wrong again.
I rewiped and went back to stock for the 3rd time today and wiped all data, formatted the internal SD card, took out my external SD card and the issues still persist.
If I reboot my phone it also goes back to the 4 hrs ahead time. I check its still eastern time zone. I don't get it.
crawlgsx said:
I am on stock + rooted/3e (recently decided to go back to stock due to random data or other issues).
I have tried rewiping a few times now but the problem persists, which is:
It does the "scanning for media" several times, not just once now. Sometimes it will do it randomly while I'm using the phone.
The time keeps settings to 4 hrs ahead. I check the time zone, its right. I can fix the time by unchecking "auto" and rechecking it, but then I'll go to use my phone again later and the time is wrong again.
I rewiped and went back to stock for the 3rd time today and wiped all data, formatted the internal SD card, took out my external SD card and the issues still persist.
If I reboot my phone it also goes back to the 4 hrs ahead time. I check its still eastern time zone. I don't get it.
Click to expand...
Click to collapse
I don't know if this will fix it or not but have you tried wiping dalvik cache and fixing permissions? Just a guess. I haven't had this problem, I've been staying on flashed Roms..
I've wiped all data, cache and dalvik. Tried going back to UCK5 (ultimate unbrick) and right out of the gate I still have both problems.
I am going to bring the phone in to ATT today and see if they will try my sim in another phone/maybe swap. I think something is wrong with the phone.
Brought it in to the store today. They did another factory reset, tried swapping sim, bunch of random small things but no matter what the problems persisted so ATT is shipping me a new phone. Odd issue.
Got my new phone problems fixed. Was surprised to see the phone came with UCKH1 installed.
I had the same issues just before my phone gave up the ghost. Got a new one and it seems better although I still get random media scanning and it takes forever after a reboot for it to complete the scanning media thing really annoying.
Infused with Android DNA

Problem with microSD Card

Hi guys,
I've been having this problem for quite some time now. I first noticed this when I shifted from one custom ROM (SAGA LBC) to another (CyanogenMod 7.1). At first, my phone kept resetting after a reboot. At first, I thought it was an incompatible ROM. For a time, wiping cache and dalvik cache via the recovery interface did the trick. But then, it just got worse and worse. I eventually reverted back to LBC, thinking that it might be Cyanogen. But, as it turns out, my phone still kept resetting. Even as mundane a task as going to the settings menu freezes up my phone, requiring me to reset, sometimes even by pulling out the battery. I tried doing the wiping of the caches again, bit it never became effective.
Then I read somewhere that Andoid seems to be uber sensitive to file corruptions and defragmentation of the microSD card, so I defragged the SD, fixed the permissions, and deleted the LOST.DIR and tmp folders. Everything went smoothly at first, but then after a couple of days, my phone kept rebooting again. To verify that it was the microSD at fault, I removed it for the mean time. Since then, my phone hasn't frozen nor rebooted.
One other thing: whenever I check the microSD via Windows (right click --> Properties --> Tools), everything seems to be in order as Windows can't detect anything wrong. Right now, I've ran chkdsk :f /f /r on the drive, but Windows says that everything is fine. I haven't reinstalled the microSD yet, as I want to run a more thorough test before I do.
Have any of you encountered this? Could you guys give me suggestions on what to do, a better tool than chkdsk, etc? I can buy another card, but I don't want to do that just yet. My microSD is 32GB, and I don't want to just throw it away or something

Android process media

I keep getting an error this has stopped. Any ideas?
Did you try clearing it's data? Manage applications -> All -> select the media process and force stop it then clear data. Hopefully with a fresh start on collecting data it will stop crashing.
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
Thanks.I tried your suggestions but the error just came back.
Is anyone else seeing this error.
Take a look here to see if it help
http://forum.xda-developers.com/showthread.php?t=1500580&
Thanks.
I am stock not rooted. took a look at the other thread but not sure if it applies to me being on stock.
tonyz3 said:
Thanks.I tried your suggestions but the error just came back.
Is anyone else seeing this error.
Click to expand...
Click to collapse
Odd. That's all it took for me to get it to behave. Force stop then clear cache and data. I restarted and used my tablet for about 4 hours last night and never had the error.
baseballfanz said:
Take a look here to see if it help
http://forum.xda-developers.com/showthread.php?t=1500580&
Click to expand...
Click to collapse
Interesting as I've been using zep's script for months and immediately added it when I first got my tablet. I didn't need to bulletproof anything just the force stop and clear data. But I did use the OOM groupings and minfrees it calculates. For those not using the script give it some consideration. It does wonders on lower end phone which are lacking memory but still makes a noticeable difference, to me at least, on current higher end devices like the Transformer or my HTC flyer.
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
thanks,
Also i just now rebooted my tf to find the micro sd card is not being read by the tf, it shows in the notifications and has all the music files etc still on it but is not recongnized by any apps.
Is this connected to the media process fail issue?
any idea how to fix.
Update:
I tried reformating the sd card putting some music and photos back on it.
Force stopping media from app list than wiped data from media, rebooted with new formated sd card but still shows sd card in the notifications and can access it from the sd card menu in notifications-seeing all the files on it, but none of the apps recongnize it- can go into any music app but does not see music on the card.
Any suggestions to try
I had this problem for 2 weeks, and then after upgrading to ICS, it persisted. So I did a reset to factory defaults, and that fixed it.
I'm sure there's a way to fix it without taking the reset sledgehammer to it, but I figured now was a good time, since I had just got ICS running, and other folks said a factory reset seemed to help fix other problems and make things faster. Plus I had tons of apps installed, many of which i didn't need, and uninstalling them would take time.
Just backup all your stuff! I ended up backing up files, and then rooting so I coudl backup apps and app data with titanium backup.

[Q] Bootloop only when starting up with SD card

Hello everyone, this is my first post here even though I have referenced the xda forums for some time now. I've spent a bunch of time trying to fix this problem on my own but now I feel that I have exhausted all of my options and I could use some help from anyone who has heard of or encountered this problem before.
The problem:
My Samsung Infuse will boot up completely and perform the SD card scanning but the SD applications won't show up on my phone (they only exist as SD card icons), which leads me to believe that it's not mounting properly because of some process or application that interferes during the scanning process. The phone will continue to run for a few minutes, slowing down exponentially as time goes on until it completely freezes and reboots to my boot animation which starts this whole process over and over again. However, the phone will boot fine and run normally if I remove the SD card. Occasionally, it will randomly boot normally with the SD card if I let it bootloop for a long period of time.
What I've already tried:
This problem started happening when my phone was completely stock so I researched it and tried:
- getting a new SD card (which actually seemed to work for awhile which led me to believe the original was bad)
- downloading a new launcher, switching to it and clearing the TW launcher data (this works occasionally when I can actually make it through this process without being interrupted by a reboot)
- performing a factory reset and manually loading all my data back to avoid restoring any potentially problematic settings
- recently rooting my phone and running UCLB3 firmware with Entropy's Daily Driver kernel with CWM to see if it was just a bug with the factory software
Since it's been rooted it seems to have gotten worse though. When everything was stock it would only do this occasionally but now this problem will occur every time. However, I was thinking that it might just be that the sd cards have to be reformatted every so often for some reason (I will try this out soon to see what happens). But if anyone else can help with this issue it would be greatly appreciated. It seems like this is a fairly common issue with Samsungs so I'm hoping that someone has figured out exactly what the problem is that would be causing this to happen.

Android Media Process killing my S3 even when I don't have an SD card or media

I've been having this problem on my Galaxy s3 for several months now where "Android Media Process" is killing my battery. I am dead out of ideas because I have tried everything I could think of.
First, I swapped the SD card incase the SD card was corrupt, Didnt wokr
Then I removed the SD card all together, Still didn't work
Then I deleted the rest of the Media on the phones internal memory, didnt work
Then I did a hard reset and reinstalled all my apps from the Play store, incase one of the apps were currupt, didnt work
I don't know what else try try.
I am running CM10. Usually this media scanner causes a problem when I reboot my phone to a point where it gets really hot and "Watchdog" alerts me when the Android Media Process is using up too much of the cpu, however when I press "kill process" it doesn't solve the issue, so then I have to go into GSam battery monitor and find the Android Media Process and click on Manage. It then opens up the the process called "Downloads" and once I force stop that, the problem is solved until I reboot my phone. Here are some screen shots of the process I go through to Kill the process:
http://imgur.com/a/ge8lq
http://db.tt/ggdT334Y
Any tips on what I should try? I don't have much else on my phone. One folder which I somewhat suspect is the folder which stores my Nandroid Backups because it is a huge folder with thousands of files, however I placed one of those .nomedia files on that folder.
Thanks
A few ideas.
You could try installing Mctweaker... Although this is an advanced user process, tweaking the settings may be your answer. Even messing with the CPU settings could solve your issue, just don't mess with the voltage and don't overclock your phone too much. Setting the governor to Performance is generally a good rule of thumb.
Second, you could try installing a different Kernel. The one you are running may be less stable than another or look for an update to the current one your running.
Finally, you could try installing a different ROM. There may be a compatibility issue with your devices hardware and the software your running.
P.S. If all else fails, try try again. Wipe your data, wipe your dalvick and reinstall the OS.
:good::good:

Categories

Resources