I have a stock captivate running 2.2. Every time I reboot my phone it vibrates like something is force closing but no dialog pops up. Is this normal? If not how can I determine what is force closing. It takes about 5 min to become usable after being turned on.
The only other problem I have is the crappy GPS and it is kinda laggy.
Is it factory stock 2.2 or for you install stock 2.2
If so possibly something when wrong on the install, try it again
Stock is most likely going to have crappy GPS and lag so that's sadly normal
Sent from my SGH-I897 using XDA App
Can't say what app is FC on you but of I were you I would backup my apps with titanium backup and would flash the stock or custom rom again then restore.Usually by then problem gets resolved 99% Just be sure when in tibu restore apps only never restore with data and also don't restore sytem apps only user apps.
Rom: Continuum 4.1
Kernel: Onix #7
Modem: jk4
Theme: Crysis Revolution
Try a factory reset first.
reboot or after/while shutdown process? mines vibrates everytime I shutdown after the S galaxy logo,I think to confirm that the device is totally shutdown and vibrates in the end of shutdown process
Sent from my SAMSUNG-SGH-I897 using XDA App
I had the same problem and booting up took over 20+ minutes of it just vibrating every so often indicating FCs. I think I gave up and factory reset mine after it wasn't ready to use after waiting for an hour. It fixed it for me.
I think my problem was when I upgraded from Stock 2.1 to 2.2, something bad happened but I can't remember accurately what it was. I think some how my phone was in download mode when my microusb wasn't connected or something. I just remember the phone showing do not disconnect but I had cable in one had and phone in the other lol.
Related
hey,
So I have a Bell Samsung Galaxy S Vibrant, it is rooted, runs 2.2 & Speedmod kernel.
It has been running fine on the speedmod kernel for several days now, until today. Out of no where, when I was using the phone Launcher Pro started CONSTANTLY force closing, basically leaving my phone in a useless force closing cycle.
AND, on top of that there are other apps that are force closing about every 10 seconds or so. they are: Market, Clock, and Samsung Apps.
Any idea whats happening here?
Thanks a lot!
~Dylan
did you install any recent apps that cause problems? it might be one of them.
You may need to ODIN back to stock.. well thats how we go back to stock on Galaxy S VIBRANT.
should be the same.
I haven't installed any apps that have caused problems that I know of...
I was just listening to music for an hour or so in the car, then when I unlocked my phone I was met with countless force close messages.
Yes, I was thinking that might be the route I have to go, but I was hoping there would be some way to uninstall those problem causing applications (namely Launcher Pro) somehow. I don't know how I would go about uninstalling it though, as my phone is basically rendered useless due to the constant force closing.
But thanks a lot for the input!
DS1495 said:
I haven't installed any apps that have caused problems that I know of...
I was just listening to music for an hour or so in the car, then when I unlocked my phone I was met with countless force close messages.
Yes, I was thinking that might be the route I have to go, but I was hoping there would be some way to uninstall those problem causing applications (namely Launcher Pro) somehow. I don't know how I would go about uninstalling it though, as my phone is basically rendered useless due to the constant force closing.
But thanks a lot for the input!
Click to expand...
Click to collapse
i don't think theres a difference between our phones, mines Tmobile Vibrant, but theres a built-in feature in stock, and most custom roms called SAFE MODE.
most people don't know about this.
This mode helps you do exactly what your facing, uninstall apps that act up.
In Safe Mode, it disables any startups and all that shiz.
Try going in like this.
shut down phone.
press power and wait till it get on vibrant screen, then start holding the MENU KEY the whole way until it starts.
the way to know if thsi worked is.. on the bottom left hand corner, it'll say SAFE MODE with a box aroundi t.
if this doesn't work, ODIN is the best way.
If you haven't turned it off recently, try a reboot. Yeah, standard boring advice, but I had constant-force-close issues a few months ago and a reboot fixed it.
So I somehow managed to get into the task manager by long pressing the home button, then from their I was able to uninstall Launcher Pro. So the CONSTANT force closing has stopped.
BUT, I still have plenty of other apps that are force closing very consistently. For example, everytime I go into the messaging application it force closes, so I can't send or receive texts. Along with that, Facebook, 'Clock', Samsung Apps, & Market are force closing.
When I go into the market it says **Connection Error (or something like that) and then sometimes force closes....so this problem renders the market useless as well.
Oh, and when I go into safe mode, I still get the constant force closing... but thanks for that info! I had no idea you could even go into safe mode with this phone.
Honestly, at the point flashing stock firmware back into ODIN is looking like my best option, but I reallllllly don't want to lose all of my installed apps, and text messages, and whatnot.
Anybody have any other ideas?
btw, thanks a lot for the input so far!
So I did a backup of all my data using the speedmod recovery menu (volume up, home, power)
If I reflash the PDA in ODIN, will I still have the speedmod kernel, thus allowing me to recover my backup of installed apps, texts, etc.?
Or will re-flashing wipe the backup and get rid of the speedmod kernel..?
DS1495 said:
So I did a backup of all my data using the speedmod recovery menu (volume up, home, power)
If I reflash the PDA in ODIN, will I still have the speedmod kernel, thus allowing me to recover my backup of installed apps, texts, etc.?
Or will re-flashing wipe the backup and get rid of the speedmod kernel..?
Click to expand...
Click to collapse
Idk what the speed mod thing is.. But yes. It will be erased.
If u want to save backups of apps..
Get titanium back up doesn't matter if u get pro or free.
Just restart on everything dude.. Like a clean fresh install.
Its something that u installed or flashed that's causing these problems.
Sounds like your phone's internal SD is dying. Our Bell Vibrant has a nasty habit of the internal SDs dying, and I've heard that force closing all the time is one of the signs that the SD is going. There's a thread in development about this. I suggest you start backing everything up
Alright, I started from scratch and now everything is working great! thanks for your help guys!
plus, now I'm even running Darky's v7.5 Gingerbread Edition, this ROM is soooo epic. haha
DS1495 said:
Alright, I started from scratch and now everything is working great! thanks for your help guys!
plus, now I'm even running Darky's v7.5 Gingerbread Edition, this ROM is soooo epic. haha
Click to expand...
Click to collapse
No problem.
just glad your phone works great.
DS1495 said:
hey,
So I have a Bell Samsung Galaxy S Vibrant, it is rooted, runs 2.2 & Speedmod kernel.
It has been running fine on the speedmod kernel for several days now, until today. Out of no where, when I was using the phone Launcher Pro started CONSTANTLY force closing, basically leaving my phone in a useless force closing cycle.
AND, on top of that there are other apps that are force closing about every 10 seconds or so. they are: Market, Clock, and Samsung Apps.
Any idea whats happening here?
Thanks a lot!
~Dylan
Click to expand...
Click to collapse
Try To Install **Rom Manager**
& There's A Option Called
**Fix Permissions**
This Recently Fixed All My FC's,
Also I Believe The App,
**Spare Parts** Also Has A Fix Permissions Option!!
*Note*
I Have A "HTC Hero", But It Still Should Work For You!!
Hope This Helps!!
Sent from my HERO200 using XDA App
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
so my go launcher ex suddenly froze up, and the phone randomly restarted itself. then i just left it and went to go watch xmen 3
i come back almost 2 and a half hours later, and the phone's still on the boot screen, and then i take out battery and restart and i come back to 7% battery life. (was at over 50%)
weird.
not the first time go launcher's frozen up on me.
other times, it says (usually) my keyboard (swype) is not responding so i force close and then soon after it says go launcher not responding so i force close. and then my phone goes back in time and launchers some of the apps i previously used. (ie: it would start up asphalt 6 which i was playing earlier in the day, and after i exit, it would start another app that i used).
or other times, it just restarts itself when i exit out of an app.
(i exit out of asphalt6 and go launcher freezes then restarts)
im not rooted/modded/anything, on stock 2.3.6 nexus s i9020a patiently waiting for ics :/
Yes, it seems to happen a lot. Sometimes on my G2 and a lot on my vibrant.
Sent from my HTC Vision using xda premium
I've used Go Launcher long time and never happened to me! I have Galaxy mini 2 with stock rom. Seems to be a prblem for some devices. Sorry for bad english!
change to a new launcher...Did you try clearing data/cache of that app?
Sent from my HTC Bliss/Rhyme
So I've had a few similar problems with recent ROMS i have flashed.
I'd been using CM9 and CM10 for a while, but got tired of lag and bugs. I thought I'd go back to GB for a while and reflash after some bugs had been worked out.
From CM10 odin'd back to GB stock with CWM and root, then installed AEON purely by reputation. That lasted for about a week. The phone had all kinds of issues with the battery. The battery level would often be all over the place (i know this sometimes happens after a reboot.) After a full charge the phone would stay on for about 4-12 hours, and simply turn off. Prior to shutting off the battery would read at 50%+.
Every time the phone shut off like this I could charge it all day and it would not restart. The only way it would start is if i pulled the battery, plugged in the carger and reinserted the battery. Once I did that an empty battery would show up on the screen. However it was not the normal green one with gradients that would show up, but simply a white box showing no charge. If i held down the power button eventually the normal battery charging screen would show up and it would reboot.
I'm assuming the phone was misreading the battery level for some reason. I tried clearing battery stats. No change.
So I thought 'time for a new rom'
I'm not certain if I went back to stock before this.
So from there I went back to CM9 and then to CM10. The battery issues remained, and two new issues arose.
My reception in the notification bar would turn to an empty triangle. It was not a misreport. I could not make calls or access the internet.
Also whenever i went in to airplane mode it would be grayed out in the power menu. It was impossible to turn off airplane mode without restarting.
I'm not on the most recent verison of liquid smooth. The issues remain, but I don't think it's the ROM as others don't seem to be having these issues.
Does anyone know any reason for this?
My understanding of flashing is that it's essentially a list of folders and files that replaces or adds to existing ones on the phone. Does it actually erase anything? Obviously it leaves our simcards and picture files. It also seems to leave app folders.
And just to be clear I wiped user data, cache, fixed permissions, etc. IMEI is still there, so i don't think that's the service issue. I did not restore any apps with titanium backup for similar. Everything was installed from the play store.
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
magnetboard said:
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I flashed back to GB so I don't think that was necessary. I've not had the other bootloader issues with garbled display, etc.
I seem to have really strange issues with this phone.
I've tried both C-Rom and Cyanogen and both of them have these same issues.
When I first turn on the phone, it will run, but everything will stutter around at about 1-2 fps for about 2 minutes. I can confirm that this happens even with no 3rd party apps installed.
Secondly, half the time when I go to grab the phone and just check notifications and so on, I'll unlock it and try to press something and it'll be frozen. I have to wait about 2 minutes before I can do anything else on it. The only thing I can do in this time is lock the screen, but not unlock it. I can tell it frozen at a low level because I have a system setting in C-Rom to play a sound when the battery dis/reconnected and that doesn't play while it's in this state. Has anyone else been experiencing this? I've already completely wiped the phone completely once using the return to stock guide and these issues have not been resolved.
Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...
fckland said:
Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...
Click to expand...
Click to collapse
Are you still having these issues or did you find a fix for them? I have the Boost Mobile one, but are you suggesting that I could/should put the GPE ROM on here?
Isn't this a memory usage ( ram ) problem that's been mentioned?
Sent from my XT1032 using xda app-developers app
The first part (FPS issue) happens to me, whe the phone boots, the FPS go down, bad, but the phone works ok, if i put the stopwatch app (CM11) time runs normally but the screen refreshes every half second or more.
Now, the second problem, about the phone freezing whan it wakes up, never happened to me, but i have to recognize that i had a few (2 or 3) reboots just when i waked up the phone and one time it just freezed with the screen off.