I updated my phone manually through Mini Kies.
Before the update with or without OCLF applied, the phone would never freeze. Since I've applied the update the day before yesterday, the phone has locked up three times. Basically what happens is, the screen will, well, freeze, and my button presses do absolutely nothing, I hit the back button- phone vibrates, does nothing, same with home button. To power it off I either hold the power button for 5-10 seconds, I have not yet had to pull the battery. HOWEVER. This last time it froze, I powered down the device but the phone would not turn back on. I pulled the battery from the phone and inserted it back in and after doing so my phone powered back on with no problem. It's a bit concerning though. Probably the worst thing about all of this is the fact that my phone runs great! Fast and responsive, GPS seems to be spot on. Except about once a day since the update, it freezes.
Any ideas? I have no experience with modding/flashing anything so I get really nervous with things like installing custom roms. I was thinking I could roll back the update and then re-do the update. I doubt I'd get the update OTA though, I updated my girls device OTA and she has had no problems so far.
I was even considering flashing Bionix, but again, very nervous to do so. I even had trouble just creating a nandroid backup! I couldn't get into clockwork recovery to do so.
Can anyone just baby me with this? Tell me where to start?
Thanks :/
I would suggest you flash back to stock firmware using Odin.
Go into the Development section and look at the directory sticky. There is a link in there for a thread on how to go back to stock firmware.
Once you flashed back to stock, i suggest using it on stock for a day or two to make sure the phone work correctly. Once you verified the phone working then try to update to JI6 again via Kies mini.
Other than that you can start to mess around with flashing different custom firmware and mods. It hard to brick the phone since you can always go into download mode and odin back to stock.
Be adventurous! Good luck!
would you suggest that I go back to stock before trying to flash bionix?
Wearespacepeople said:
would you suggest that I go back to stock before trying to flash bionix?
Click to expand...
Click to collapse
You should go to JFD then to JI6. Freezing isn't normal, I don't have any freezing. If it was randomly freezing there would have been a 10 page thread on it already.
I've also had it freeze twice on me. Went from rooted Stock to JI6 using Odin. /shrug
Same issue after applying JI6 OTA. I unrooted before applying the OTA, but have now reapplied OCLF with stock.
Same issue. Frozen hard twice. Browser exits randomly. Battery drains about twice as fast as before JI6.
I went from fresh Stock to JI6 via Odin. I don't know if I can wait for Froyo. I may just go back to stock again, even with the broken GPS.
I bet the OP has a bunch of apps installed.
A lot of people are blaming the update, but I'm almost sure there are many rogue apps in the marketplace, because last night I was getting freezes and after I uninstalled all the apps I don't actually need (or use very frequently) all of the freezing just stopped. The phone runs smoothly now. And removing those apps + removing the Task Manager widget from one of my screens increased my battery life by ~200%.
I installed BioNix 1.9.1 (with JI6) and I'm still getting occasional freezes, but I'm wondering if they are due to Angry Birds which I installed at the same time as my original JI6 OTA update. I'm seeing some reports (forum.androidcentral.com/motorola-droid/38906-freezes-weird-stuff-angry-birds.html) , but I have no idea if this is a valid idea.
Anyone else seeing freezes with JI6, but not angry birds?
I've also been having freezing problems, and I think they're GPS related.
The last time was last Friday. I was driving down to Washington DC using my phone for turn-by-turn navigation, and it froze about 1/3 of the way there. I had to pull the battery out to restart. When I got to my destination, I was using Maps and then the browser, and while the GPS icon was on the notification bar, telling me it was trying to find my position, my phone froze again. Again, I had to pull the battery out. Both happened within around a 1.5-2 hour period. I realized it may be due to the GPS, so I turned off GPS right away. It's now Monday afternoon and my phone hasn't frozen since.
Related
Got my official OTA update this morning and it's been nothing but problems since.
First, the phone wouldn't boot. Got the 'droid' sound effect, and phone froze on the eye. Fixed itself after a battery pull.
Now, contacts won't load, one of my email accounts won't sync, phone is not as smooth or stable, keep getting FCs (Sense FC, 'Process System is not responding') from which the phone won't recover.
Never got around to rooting, so it was stock rom -> OTA.
Anyone else? Ideas?
jaangunnar said:
Got my official OTA update this morning and it's been nothing but problems since.
First, the phone wouldn't boot. Got the 'droid' sound effect, and phone froze on the eye. Fixed itself after a battery pull.
Now, contacts won't load, one of my email accounts won't sync, phone is not as smooth or stable, keep getting FCs (Sense FC, 'Process System is not responding') from which the phone won't recover.
Never got around to rooting, so it was stock rom -> OTA.
Anyone else? Ideas?
Click to expand...
Click to collapse
Your phone wasnt frozen, it was loading. After a OTA update or new rom install, then your phone will take longer to boot and appear its stuck. You made a mistake by doing a battery pull and might of messed up something. I would only pull the battery if it was stuck for like 15 minutes+
I would take your phone to VZW and get a replacement.
I did wait for half an hour before the initial battery pull.
But you're probably right, shouldn't have pulled.
Did a factory reset and everything is smooth now. Annoying to have to get all my apps back, but so it goes.
Well, I say it did. In my patient, impatience, I rooted my Vibrant two days ago (then later that day T-Mo announced they would roll out the OTA Update).
I rooted with RyanZA's One Click from the Market and applied the lagfix (V2.1+). This morning, when I woke up, I had the OTA Update waiting for me. So I uninstalled the OneClickLagFix, uninstalled EXT2 Tools and left the phone rooted. I took the OTA Update and everything was FINE for most of the day. I did a couple of reboots, played with some things, and went about my day.
Earlier this evening I was getting some directions via Google Navigation when it took me back to the "old days". The phone froze, gave me a black screen, and hung out like a worthless welfare recipient looking for a free 40. I did a battery pull, the phone rebooted, the OS loaded, swiped in my pattern and it froze, no black screen, but froze. After about 5 minutes, and yanked the battery, rinse, repeat, same result.
After that, it would hit the Galaxy S Splash screen and then go dark. I waited as long as 25 minutes in one instance. After literally 10 attempts, I booted into the recovery console and wiped everything. The phone came back and all was well. I reinstalled apps (still had root) and went about my way.
At some point, randomly, before reinstalling the lagfix, Haptic Feedback went dead. Well, scratch that, the entire vibrate function went dead. No Vib, anywhere. So where do I go from here? I'm thinking it has to be a software glitch. Frankly, I don't want to wipe the thing again. I referenced a thread here entitled "Is your samsung vibrant not vibrating when it should??" (I'm to new to post a link here), but none of those options worked.
Has anyone else experienced this problem yet?
Do I have any other options?
Thanks for the input!
I've got same problem
Well I see a lot of people are having problems with the update... I'm not sure if I should install it when it pops up on my phone....
Sent from my SGH-T959 using XDA App
the lagfix 2.1 causes all vibration to die in the latests updates, JI5 and 6 it's a known issue use version 1+ if you want lagfix with vibration
yeah its the 2.1 lagfix. The 1.0 version work fine.
Yes, I just installed the lagfix and my vibration went away... What's the difference between version 2.1 and 1.0?
My phone is stuck in airplane mode...
It just started earlier today, about the time I had lost signal and would have gone into roaming on the way to my dads house.
In the past Ive run Epic experience with xtreme kernel, and with 2.2 I have tried the original leak, Mammon, and I was on Quantum when it started doing this. I just tried wiping and reflashing to the newest version and its still stuck.
Any ideas?
Note: I did NOT make any attempt at flashing the 2.2 modem.
So this is what I did and it worked flash the stock rom firon or noobnl posted I foget and then flash to 2.2 again it worked for me after a few times.
Sent from my SPH-D700 using XDA App
So flash the stock 2.2 that Firon had posted to get airplane off, then flash back to whatever I want? Or do you mean flash stock as in out of the box 2.1?
Ive never had to odin or whatever all that jazz is, wasnt an option on the hero obviously, and I try to keep my messing with the epic to a minimum. So it makes me a little nervous.
Well you could flash the modem.bin in odn to make it easier idk wher t find that tho search the forums.
Sent from my SPH-D700 using XDA App
Similar Problem with Epic stuck in Airplane Mode
There is a similar thread about this problem under the Sprint Forums. Myself and several others have experienced multiple instances of the Epic randomly going into Airplane Mode on its own. Sometimes it gets stuck there for several hours. It appears that this has something to do with a weak signal. For me, it happens only at my home, where I have little to no signal. I have an Air Rave, but for some reason it appears to go into Airplane Mode more often with the Air Rave on than with it off. This is very frustrating. Sprint does not acknowledge the problem. They say it must be a hardware issue, and we should just get new phones, but I'm on my fourth phone, as is another person on the Sprint forum, so it appears to us that this is really some sort of software bug, but it does not occur often enough to cause Sprint or Samsung to take notice and do something about it.
This happened to me as well the day before yesterday... I had installed ViperRom IMpact, and had car home running navigating me to LAX, and all of a sudden, my phone reboots and then was always stuck in airplane mode after that. I recovered my original rooted rom, stock 2.1 just rooted, and worked fine... Installed SyndicateRom (2.1) and still could get signal. Tried to install another 2.2 ROM, and get the same thing where it's stuck in airplane mode... So I think I'm going to stick it out with SyndicateRom for a bit...
had the same problem a couple weeks ago for several hours. spontaneously fixed. and about 20 mins ago it went into the problem again. no apparent solution.
Possible solution...
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
I have this problem pretty often when I am in a place with bad signal. Reboot the phone into clockwork recovery, in advanced options, fix permissions. This has fixed it every time. Also sometimes just rebooting it will fix it but that only seems to work randomly.
zndotcom said:
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
Click to expand...
Click to collapse
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
I've seen it happen on my phone and a friend's phone. The advice below always works.
tragiquexcomedy said:
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
Click to expand...
Click to collapse
p3dr0maz said:
I've seen it happen on my phone and a friend's phone. The advice below always works.
Click to expand...
Click to collapse
Just had the same issue pop up on my wife's phone, & wiping caches fixed it a well. Thank God for XDA & Clockwork!
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.