Database Develop

Phone becoming unresponsive after FRF83 OTA

I received my OTA to FRF83... and now my phone seems to be freezing up every so often while doing basic tasks... even waking up the phone sometimes freezes at the unlock screen. Anyone else getting this? My phone is UNROOTED and official. FRF72 ran fine... not sure whats going on but its REAL annoying.
I even tried factory resetting and still getting the same issues.
Any ideas? Can I manually go back to FRF72 somehow?

Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory

stuff said:
Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory
Click to expand...
Click to collapse
I just tried "clear user data"... thats about all I get with stock recovery. I don't think its an app considering I deleted everything and it still continued to freeze.
Can I delete Dalvik from ADB even unrooted?

I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.

Big_O said:
I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.
Click to expand...
Click to collapse
Like I said... I factory data reset so there where NO APPS. and the phone still comes to a screaching hault after a few minutes of jumping in and out of apps. It freezes to the point I have to remove the battery. Becomes completely unresponsive to touch.
As a side note, ive been using android since the first G1 on pre-order... I know how it works and how you need to use a task killer to keep stuff running smoothly... This however is extremely odd as it completely freezes.
again, only started after my OTA update to FRF83.
thanks for the input. I guess i'll have to send back my N1 for the forth time to HTC... getting pretty sick of this. That Iphone 4 or Galaxy S looks better everyday.

You don't need a task killer manager since 2.1. Froyo is even better at handling memory.
Sent from my Nexus One using XDA App

i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?

rensky said:
i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?
Click to expand...
Click to collapse
I'm glad I'm not the only one. Mines also an unlocked phone. Wonder if that has anything to do with it.
Ugh we need frf90 to come along and fix this!

The Same here
It happened to me right now, My phone hanged and I forced reset it, it happened one time when I was on FRF72 and one time now on FRF83. it was after a phone call and I couldn't unlock the phone, touch screen didn't work but it did work for power button menu so it should be a software problem, I thought it should be something incompatible between launcher pro and FRF 72 and FRF83 but it seems it is not the case.

I have the same problem. Went from ere27-frf50-frf83. I thought it was launcherpro so I uninstalled it.
Still getting freezes on unlock...and switching between Apps. Sometimes need battery pull sometimes just some time for the phone to catch up.
I had previously switched from frf50 back to ere27 because I couldn't stand the constant need to pull battery because phone freezes.
issues i have with frf83 is not as serious as frf50 so I think I will still stick with it for a few days and see what happens.
Just really need the official ota.
Sent from my Nexus One using XDA App

I just upgraded to the 2.2 (FRF83) yesterday, already had to pull the battery twice in one morning because it just froze up..
What the fu*k did they do! The 2.2 prerelease was fine hadn't had any crashes at all in the month I used it.
Edit; make that 3 times.. WTF!
Now, I'm extremely tempted to just root the phone but I was sticking with official builds for stability, I really didn't think it would get worse..

Yup having the same problem... Had to pull the battery twice today due to freezing and the same thing yesterday... It just started happening to me. Got 83 when it first came out, and its now starting to freeze. Idk what the deal is..
I still have no idea what these updates do.. What's different? I'm talking about the frf50, 72, and 83.. Froyo by it self seemed fine, what's new??
Sent from my Nexus One using XDA App

[Q] No system sounds, even after flash.

Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?

lisurgec said:
Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?
Click to expand...
Click to collapse
Mabey an odin one click, then keys update to froyo might work ??? !! I'M NOT TELLING YOU TO DO THAT, I'm just suggesting that might work. If it came with froyo then you might get a bootloop so I would suggest getting a jig if try this way
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

jig
in all cases the jig is your lifeline lol. I SUGGEST having a jig handy when any new roms are installed. There are alot of good roms out there having no phone for a couple days changes the perspective and for you to make a jig is under 10$ .... Did I mention lovin the new Serendipity 7, good clean rom.

[Q] Stock Dialer Gone Bad, Used Odin and Kies, Still bad! Help!

Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign

^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.

I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.

A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.

how to fix turning off issue for samsung i9000 ?

I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed

I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.

what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.

Try to flash a custom kernel and see if it the problem is still there

can you tell me or give information what's is 'flash custom kernel' ?

I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.

Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.

Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4

Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...

Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.

Anyone???
Maybe theres another forum that this problem should be posted at??

I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.

hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...

Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).

Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.

hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you

madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.

try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html

Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know

my turning off issue went back and it's getting every time more annoying, I don't know what to do...

Will Flashing Back to Stock Solve My Problem?

I just recently flashed a ROM for the first time. I went with CM7 as I was looking for something close to gingerbread to improve my phone's performance. I like the way the phone is running, there is a lot less lag, but it didn't solve a problem I encountered a few days before flashing.
On the advice of a friend, I installed an app called Llama, which is a free, dumbed down Taskr wannabe. I installed it, played with it a while and decided I didn't like it, so I uninstalled it. However, since installing it, my phone no longer vibrates when it gets an alert (text, google talk, etc.). I was hoping flashing would solve this, but it hasn't.
My question is, would flashing back to stock (via Odin, or something similar) possibly solve this issue? Or, is there any type of data that the stupid Llama app left behind that I could manually delete to get my vibration notifications to work again? Thanks in advance for any advice.

Dude llama's awesome, I use it for everything. Most likely it just changed a few of your volume settings. You just need to set them back to the way you like. No flashing necessary
Sent from my ICS i897 Captivate

It was okay, just wasn't for me. I've reset all my settings and whatnot, especially considering I flashed CM7 after uninstalling Llama, but still nothing. It won't vibrate for any alerts or when I plug it in like it used to.