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.

[Q] infinite boot and many other problems

I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.

so no one has any idea what i'm doing wrong? or has experienced similar problems?

Try to reinstall the drivers in kies.
If that don't work do download
Them from android development site.
It should work.
Try the phone in all mode you can to get the drivers to install right.
Then you can try to fix it with kies or odin.
**DamianGTO Steam kernel. 349MB Ram. 256HZ. ext2. js3 base**

Another approach
I too cannot get odin or kies (or usb mass storage) recognized on the PC. I tried for a long time and gave up.
Are you rooted or can you access the root dir? If not can you access the external SD card or market so that you can root?
Do you have clockwork mod or similar?
I can only base my experience never using odin or a pc...
If you can get into recovery mode and start using (if you do not have it already)clockworks mod (and/or steam recovery - which I highly recommend as it can access the removable sd card which is useful to load stuff on to when things go sideways see why in my post http://forum.xda-developers.com/showthread.php?t=929020 ).
Then you can flash whatever you want from the root directory or with steam from the external SD car (root dir there) no odin or pc required (directly).
Then I'd start with stock or at least a custom rom that is based on your carriers stock and go from there.
G

wastedkila said:
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
Click to expand...
Click to collapse
Hey!
I've had the EXACT same problem as you. did you try to put your phone into DOWNLOAD MODE (Close phone, then hold volume down, then home, then power) to see if it connects to odin? Also, before you do anything, make sure you turn on odin first and then select all the files you want. After thats done, then put your phone into download mode, then connect the phone to your computer thru the USB.

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks

That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.

djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!

ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??

duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out

Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution

jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.

dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater

(Problem) S5 G900A keeps restarting

Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!

junnelle said:
Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!
Click to expand...
Click to collapse
Try flashing the experimental firmware from the rooting guide, and if that doesn't work then it is most likely a hardware issue, and I have a strong suspicion that it is.

If you have an external SD card, remove it and see if problems persist. Honestly that sounds like a firmware scrambled.