Database Develop

[Q] Foce close error all installed apps not showing 2nd time...

Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.

i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run

Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.

I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.

nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later

I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.

read this
http://forum.xda-developers.com/showthread.php?t=793404

Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...

I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?

Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.

"Check for update not available" error

Here's a new one, at least for me...when I hit my system update check button in about phone, my Bionic is spitting out
"check for update is not available
at this time.
Try again later,"
Has anyone else ever seen this message? It looks like its happening on 4G or wifi, haven't forced 3g and tried yet.
Usually I expect the "Your phone is up to date" message, but this one's new to me.
I'm bone stock, btw...no rooting yet.

I got that a few times yesterday and then tried again 10min later and it ran the check successfully but didn't find an update. When I ran the check for updates this morning it found the update and downloaded/installed successfully.

Well, that's encouraging I suppose...every time I think I really like this phone, something like this pops up...ugh, I want bionic speed and HP, but with my OG droid and droid X's "it just works" reliability.

I think the only reason you're seeing this error is because the servers are under a very heavy load pushing out the updates. I never saw this error before yesterday. But I'm with you on the frustration factor. I'm on my 4th Bionic now, if I continue to get the black screen of death, random reboots, or data connection issues, I'm going to do whatever I can to get a different phone. I've never had to return a phone to Vz before this model, nor I have ever spent so much on a phone. I certainly don't feel like I'm getting what I paid for. How this phone made it thru user testing with these issues blows my mind.

I had been getting that message ever since I replaced my SIM a couple months ago. I figured it wouldnt interfere with me getting any OTA's, but last night I decided to do a factory reset to see if that cleared it up. Low and behold i hit system updates and it said my system was up to date. An hour or so later I did it again and I got the update!

Good to know. I read a thread somewhere, I think it pertained to battery issues, and someone suggested that when you first take the phone out of the box the first thing you should do is a factory reset b/c it helps with overall performance. I don't know if there's any truth to that but that's what I've done on all of my replacement Bionics and I do perceive there to be some improvement. I don't know if it was necessary but I ran the reset after receiving the OTA today too just to rule that out if I have issues going forward - that's the first thing tech support makes you do when you have problems from my experience anyway.

I've been getting that message a lot too when checking for the update. I got the update today and it installed fine. Still have the data drops though. VERY frustrating.
One think I HAVE noticed with this update is that the battery stats are completely reversed. It used to be the display was down in the 3-5% region, as well as the Android OS. Now, those 2 are at the top, and my phone has just been laying on my desk most of the day.

I am not rooted. I've been getting that message since I got the phone in October. It only happens when I am on 3G. I haven't checked it on 4G (don't live near one) and it says "...up to date" when I am on WiFi.
Sent from my DROID BIONIC using xda premium

I am getting frustrated... I have been getting the same error for three days now. I am rooted, but am on 5.5.886 and everything still the same. My partner is still original stock, and he's getting the same errors as well. Perhaps this is a regional thing? Anyone in the DC area get the update rolled out to them?
Additionally, can I just flash the update file that is posted here on the forums to upgrade manually? Or should I just wait?

Works!
I was getting the same "check for updates not available at this time" message, however I rebooted (used Quickboot, battery pull is not necessary). After the reboot went back to "Check for upgrade" and it worked; BUT just like the previous upgrade the process checks your file system and if you removed/altered any bloatware then it will fail and reboot. After the first time, I decided instead to create a folder "bloatware" in the system direction and move all bloatware apps to that folder. So this time around all I had to do was move all the bloatware back to the "app" folder in one shot. Very easy and straight forward (I also wrote down the bloatware apk filenames so I didn't forget that I moved over last time). Tried the update again, installed just fine, and phone is up and running.
AND....root is INTACT!
Btw...I had no idea there was a new update available until my friend who just got a new Bionic said he's having problems rooting on software v5.9.902

process acore has stopped hell

I know there is a lot of information on this, however my problem appears to be a bit more chronic all of a sudden. If anyone has any idea what this is (especially if it is a possible hardware issue), I would really appreciate it.
This started the past weekend and has been driving me crazy ever since. After uninstalling facebook on Saturday, I got the pop up. Rather than messing with trying to fix it, I went and reflashed the rom. While restoring all my apps, the error popped up again. Convinced there as something up on the phone or the sdcard file system, I restored back to stock 4.4.2 with odin. I rooted, went through the same restore process and after one of my reboots, it came back. Finally I searched and did "restore app defaults" in the application manager. That worked for a while, but came back a few times, until finally that method wouldn't fix it anymore.
Last night I reflashed with odin again. This time I didn't root. Everything was fine all day until I decided to uninstall twitter and the acore message is back. Doing an app reset did fix it again, however I am afraid at this point to reboot the phone or do anything else.
I had this problem maybe once about 3 months ago, now I can't get ride of it no matter what I do. I should also point out that I did not do a TiBu restore or anything, I installed all my apps through the play store.
Thanks in advance guys

Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message

majortaylor said:
Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message
Click to expand...
Click to collapse
I did that, however it usually didn't work. I had to reset all application defaults and the issue usually went away. During one of my reflashes, even that didn't work anymore.
Seems like the issues started when either I turned off one of the bloatware apps, or deleted something. Sometimes the acore would start right away, other's after I rebooted the phone.
This last time, I got the phone setup, I got 2 acore's early on (Clearing app defaults worked both times). I didn't do anything else to the phone for a few days. Last night I finally rooted, installed safestrap and my other root apps and so far everything seems stable. I will just do a twrp backup before removing anything in the event things go bad again.
What still bothers me is don't know what caused this all of a sudden. I've been flashing roms for years and never once had this sort of problem. I will all set to consider this a hardware issue, until it finally settled down.

[Q] Note 3 crashes/reboots about once a day

For the last few weeks, my AT&T Note 3 has started randomly rebooting. It can happen when I'm viewing email, when the phone is in my pocket, or even in the middle of the night when it is just sitting recharging. The rebooting is roughly once per day: somedays more than once, other times it can go over 24 hours. The problem seems to have started after I updated to 5.0. I have tried a factory reset, but the problem came back. I called AT&T support and they said that they've had a lot of problems with Samsung devices after the 5..0 roll out, with random rebooting, or the Bluetooth failing, or the WiFi failing. They said that they need to replace the Note 3, but because it is over a year old I must pay $100 for the replacement through Asurion (I have been paying the insurance fee).
Searching on line has not provided much on this problem. Does the AT&T comment make sense? If I need to replace the phone, shouldn't it be for free because the problem was caused by AT&T?
I'd appreciate any comments.
Note that I realize it could be related to an App I use being incompatible with 5.0, but I need to use my phone for work pretty much constantly, so troubleshooting which one (if any) is not practical.

Mine started doing the same thing about a week ago. Till then it was not having any problems with the 5.0 version.
They need to figure out the problem and push out a update. Otherwise it is like they don't care about us, unless we go out every year and buy a new phone !

Problem solved?
After trying a reset and cleaning checking the battery contacts didn't work, I looked for other patterns. It seemed to me that one of the most common times it rebooted was when I checked my email with the K9 email client - something that is always running in the background, and could have caused it to reboot when on charge overnight.
I uninstalled K9 and that didn't help - the phone rebooted after about 9 hours. However, since that reboot it has now gone nearly 48 hours without rebooting. Maybe I was right about K9 and uninstalling it wasn't enough - I should have also manually rebooted the phone.
The phone has been rebooting at random times, sometimes as short as about 5 hours apart and sometimes more than a day apart. It could be that right now I'm at one extreme and it will reboot randomly today. But if it makes it through tomorrow morning without rebooting then K9 was probably the problem.

It has now been over 72 hours since the last reboot, which does suggest that the original problem was the K9 email client, crashing and forcing a reboot on the phone after the Android 5 update.

Problem NOT resolved!
A few minutes ago, roughly 76 hours after the last random reboot, when I thought that the problem was resolved, I heard the reboot tone coming from my phone that was sitting on the table.
So, while removing K9 reduced the frequency of the reboot, it did not solve the underlying problem.

Use Titanium Backup and backup all user apps and data. Factory reset and reflash stock if you want to take the extra step. Use standard Google and Samsung apps for a while. Do not restore accounts or system data automatically. Removing and reconnecting accounts and clear data for an app in app manager are always good quick troubleshooting options. Restore apps as you need them, if you really need them. Favor stability over extraneous features.
.......................................................
Galaxy Note 3 - AT&T (sm-n900a)

Since I removed K9 and rebooted the phone, it has only rebooted randomly once in 5 days: this was at 72 hours, and now it has been up for 65 hours since then. Trying what you suggest would take weeks, given the current frequency of random rebooting. Plus, my phone is used for work constantly - I couldn't get by with just the Samsung and Google apps built into the basic phone image.
For the moment, I will just live with the phone as-is and hope that Samsung issues a new version of 5 soon.

Now at nearly four days since the last crash/reboot, or only one in seven days. At that frequency, it is certainly not worth the effort of trying to track down the secondary cause (it could take months), now that I know that K9 was the main problem.

It has been a while since I started this discussion, with no conclusion. The phone still randomly reboots - only once all of last week, but then it woke me up on a reboot at 4:30 am this morning, and rebooted again while I was checking Facebook at 7 am.

I'm having a rebooting issue as well with my Note 3. It started about a week ago and will do it many times during the day. I have tried wiping the cache partition, doing a factory reset and the other day I downgraded the software from 5.0 to 4.4.2 and rooted it and froze the over the air update from AT&T but still have random rebooting. I have had the reboot issue with and without the SD card installed so I know that is not the issue either. I was thinking it was a software issue so that is why I did all of the stuff listed but now I'm wondering if it could be hardware. I guess I'm just at a loss of what to try know and was hoping someone on here had any suggestions.

I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.

jeffp25 said:
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
Click to expand...
Click to collapse
It happens both when charging and when sitting unplugged. I even tried swapping the battery for a new one and the contacts and also clean

Well, it was an idea. I did the same thing, buying a new OEM battery and hoping it would help. It didn't. But then again, mine often reboots at night (it woke me up at 4 am this morning), so I knew it was unlikely to be a battery issue in my case.

Yeah thanks for the idea but it seems like I'm running out of things to try

I feel the same. The only thing left would be to wipe out the phone and try it with nothing but stock, non-upgrades, apps. But I use the phone for work, and it can go more than a week between reboots (or less than a day), so that isn't practical.

I might just end up mailing my phone into Samsung to be repaired but now that I have it rooted is there any special steps that need to be done to unroot it? I was just going to do a factory reset and let AT&T android 5.0 do it's update if that will kill the root. I'm not worried about warranty since it is no long under warranty.

Maybe use logcat and letting it run and wait for a reboot to happen so you can see what is going on. However the logs could get big and it might not capture what happens right before it reboots.

Galaxy SIII stuck in upload loop after software update

Hi all
I am not technical and am not really sure what to even call this issue, but have done numerous searches on this and other forums over a few weeks and am not able to find anything like it. I'm sure there must be, but because there is nothing onscreen to help identify the issue I don't know what to search for next.
I few weeks ago I got a message to upgrade the O/S. I didn't do it at work, as my reception there is pretty lousy. When I did do it I had good reception. When it had finished, it then wanted to install. I left it until the next day, when I was home again with a strong signal. It commenced installation but when it got to 91% it rebooted and started over again. This has been happening ever since and the only way to stop it is to remove the battery. I've tried leaving the battery out for several hours, draining it, and all the different kinds of reboots but nothing helps. I was able to get it into download mode, but then it got stuck in there. I was able to get it back to the other screen and don't know what to do now.
The only thing on the screen is a standing android guy with a blue polyhedron rotating in his belly, and an upload percentage. It always restarts at 91%.
I don't want to mess anything up, because this is a borrowed phone - after my previous two Nexus 4s chucked it in. I ended up having to send the first N4 back to Google and lost everything on the phone, but the other one has a lot of data I really want to keep, so I won't do that again.
Is anyone able to help me with this issue?
Altotude