Database Develop

FRF91 freezes 5 times daily?

What is going on here? It either freezes when:
1) slide-to-unlocking
2) switching between programs
3) google sync icon shows up in notification bar
4) in apps
Need to pull battery all the time! What's going on?
I've had this ever since the FRF50! I'm so annoyed and want to go back to 2.1, but I do love the battery life I'm getting with FRF91.
Any help please?

Sorry, realized I posted this in the wrong forum. Can MODS transfer the thread to Q&A?

I'm getting freezes on the same situations you have posted. However not with the same frequency as you. Mine is 1-2 daily.
Sent from my Nexus One using XDA App

strange, my phone is stock and ive had none of these issues, i actually thought my battery life had worsened since 91. It seems like the green meter doesnt drain as quick but the actual percentage drains faster than ever for me, at least i think so

This should unusual and should not be happening. Wipe everything and reflash.

That's Strange... I haven't had any freezes since installing the FRF91 OTA.

galaxys said:
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
Click to expand...
Click to collapse
Yepp, same here! Never had a single freeze/lock-up since I manually updated to FRF91 from EPF21.

Hardware Issue
Seem to me you either have a defective apps or widget, a defective SD or a hardware issue like defective video ram or something like that, you could try to use a benchmark app like quadrant this may help pinpoint the exact subsystem that cause crash (video, cpu, ram) and try running stock OS with almost nothing loaded ...
This is assuming you are running from a clean install, When you have issue it's always a good idea to clean install (full wipe etc...)

Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.

Mine is stock and sometimes it freeze when I tried to unlock. I had to turn the screen off and on 1-2 times to make it work again

Following your advice and let me monitor for a day or so. If doesn't work I will wipe everything and reflash.
Thanks!
mingkee said:
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

wipe everything and flash both FRF91 and the latest gapps.

1. How many app you have and 2 are they on your SD? If you have alot of apps ittaking up your internal space causing you to freeze.
Sent from my Nexus One using XDA App

I actually installed spare parts the same day i installed stock frf91, so i am not sure who is the culprit. It didnt happen today, but froze yesterday and the day before.
turned off all the animations (transition/window) to get maximum speed out of my n1 using spare-parts maybe thats causing the craziness no?

Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.

Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.

still froze twice today....wiped + reflashed FRF91..now resetting up my phone .... hope this will stop the freezes...will report back

Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I think I found a solution.
Go to email account, settings
Auto check->off

DarkDvr said:
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
Click to expand...
Click to collapse
Thanks, It works

Captivate random shuts down

I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.

random shutting down
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.

ice3186 said:
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
Click to expand...
Click to collapse
I havent been using ATK at all. Also does SetCPU really work with the hummingbird processor? When it boots it always kicks down to 19.2 which is obviously too low. I removed it just in case. I also set it back to the default settings. I would really enjoy SetCPU to save battery if it works of course. I thought it only works on HTC devices and Motorola devices?

i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.

domin8 said:
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
Click to expand...
Click to collapse
I deleted SetCPU and I thought it might be Screebl so I disabled it. Sure as hell it just went to a black screen and shut off again. God this is beyond annoying. I dont want to have to bring back this great phone but I need the phone to work.

We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.

madjsp said:
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
Click to expand...
Click to collapse
Yes but if I am correct none of these issues will be fixed until they decide to release FroYo?
EDIT: I just tried removing the MicroSD to see if that resolved the issue. Shocker...it didnt...

spyz88 said:
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
Click to expand...
Click to collapse
This has happened to me once. Came out of a meeting, pulled it out of my pocket, and couldn't get it to wake from sleep. I have not installed SetCPU, so it's not that. Not sure what the root cause was.

What apps do you have installed would probably be the more relevant question. And what have you changed?

Mine is doing the same **** and it is driving me NUTZ!!! I thought SetCPU first so I uninstalled and rebooted. Phone is still doing it. Please someone figure this out quickly. I am going through my apps one by one and uninstalling them to try to pinpoint the problem. Subscribing to the thread.

Interesting.... I haven't heard this happen to me yet so its probably an application or process your guys all have in common.
Sent from my SAMSUNG-SGH-I897 using XDA App

I have a feeling it is setcpu. I just did a reboot after installing and now it is not happening. Cross my fingers!

I'm having the same issue and I never had setCPU installed. sucks..
-Teklock

Like a lot of you, I started uninstalling my apps one by one when this happened. It stopped restarting after I finally uninstalled Launcher Pro. After that, the phone stayed on the whole night last night. It's weird because it worked with Launcher Pro for a good 2 days.

I'm also experiencing this issue, ad i've only downloaded a few apps.
Has anyone exchanged their phone over this yet?

Teklock said:
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Click to expand...
Click to collapse
I reflashed to stock firmware and I'm still having an issue. I noticed that if you take the battery cover off the battery and push on it then it seems like it has a little give to it. Can anyone who is not having this problem confirm? Also, anyone who has this issue, please see if your battery has a little give to it.
It should be on the side WITHOUT the contacts. Also, if this doesn't work I'm bringing the phone back. I already had a problem with the first one and since this is my 2nd exchange AT&T wont exchange it anymore. They told me I need to go through the warranty. They are out of their minds the phone isn't even a week old. Never had these problems with HTC...
EDIT: I uninstalled ADW Launcher as a test to see if thats it.
EDIT 2: Make sure the battery door is covered tightly. I pushed mine all the way down until it clicks. Hold it down and then close the slider. I think this actually might fix the issue.

Anyone figure out why this keeps on happening? I've reflashed the stock as well and it still occurs randomly.

Strange this dosnt happen to me, and i installed setcpu(performance governor 1ghz/800mhz) but uninstalled it after seeing that it ****'s up gles 2 rendering...

I found this thread via Google search, and I just wanted to add that my phone started doing this last night, however, I have not added anything to my phone, nor is it modded in any way. It's completely stock. The only thing I have done thus far was remove all of the extra home pages and rearrange some app icons, and that was on Thursday and Friday. It does it both when it goes to sleep normally or if I hit the sleep/power button.

I narrowed mine down to SetCPU being underclocked while asleep. Bumped up the minimum clock and took off the profile I had set, phone hasn't rebooted in 4 days.

Captivate randomly powering off?

I've had the Captivate for about a week now and has powered off about 4-5 times for seemingly no reason. Each time it has happened has been when the device was idle/locked. Battery level has not been the culprit, as my charge level has been nowhere near low when it has happened. I've been missing phone calls because my phone has just shut off.
Has anyone else experienced this or do I just have a bad phone? Between this and the GPS issues I'm really starting to think about taking it back. Shame though because I love the screen!

i unroooted did a factory reset and everything im just getting a replacement so yeah

Haven't experienced that. Are you running an app killer or something?

I had the same problem. Last night and this morning it would go to sleep and I was unable to wake it up. Had to pull the battery and then it powered up. I had "setcpu" on it and I have since removed it. It hasn't shut off since. We will see if it holds up.

Citznfish said:
Haven't experienced that. Are you running an app killer or something?
Click to expand...
Click to collapse
I have Advanced Task Killer Free, but I do not have the 'Auto Kill' enabled. So it only kills apps when I run it.

Had the same issue like 5 days ago without a task killer or SetCPU. Not sure what it was, but hasn't happened since.

Try a full restore, and make sure it's not an app that is making your phone crash. If not AT&T has a 30 day return policy in store. They may want to do the restore, and have you try it for a few days. Just let them know you tried that already. If you take it back and have them check it out, if they can't fix it, they'll replace it.

I just replaced my phone due to battery issues, never had a reboot.
This morning I was listening to pandora at the gym and it just rebooted on me. Then again I never use pandora, but slacker was having issues this morning.
I will wait for it to happen again before I take action

I have pandora installed as well, but it's never happened while the player was running. I'm keeping an eye on the task killer and pandora, but so far it hasn't shut down yet.
Any gurus know if there is a shutdown/crash log anywhere to view?

My Captivate has shut off twice, ONLY when Pandora was running and it was plugged into the car charger. When I run with Pandora running, it hasn't shut off. I think it's a Pandora problem.

Ok, mine just crashed three times in a row. Two of the times I was changing the wallpaper. The third time, well I dunno. I've removed the Pandora and ESPN Score Center widgets to see if that has any effect.
I'm going to load the stock ROM when I get home to see if it is truly a hardware or software issue.

I'm almost positive it has to do with setcpu.. I was setting up my friends captivate and it was doing that to several times. When i restarted and checked setcpu just on a whim, the settings were all wacked out from what i had set.. the max was all the way to the left (lowest clock speed) and the min was also set all the way to the left.. when i slid the sliders the availible min/max values suddenly changed to 1000000 for both of them..
So im thinking setcpu is not getting along with some of the captivates..

I don't have setcpu installed. I haven't even rooted my phone yet. I only have a very small number of applications installed. Here's the list:
Advanced Task Killer Free
AppBrain App Market
Barcode Scanner
Facebook
Foursquare
Goggles
Google Sky Map
Google Voice
Pandora
ScoreCenter
Shazam

Alright, I did a complete wipe, restored the factory ROM, and haven't installed any apps and it's still happening. Guess I'm taking it back. Hope they're not a pain in the ass about exchanging it.

Its not SetCPU. The reason is the battery door is loose and not clicked in properly. When you place the battery door in push on the bottom part when you close the slider.
After that, no troubles. I ran into the same problem.

Game hero of sparta made my phone wack out.. even paid the 5 for it.... darn

Try to remove Advanced Task Killer Free. Once I did it on my phone the problem went away.

spyz88 said:
Its not SetCPU. The reason is the battery door is loose and not clicked in properly. When you place the battery door in push on the bottom part when you close the slider.
After that, no troubles. I ran into the same problem.
Click to expand...
Click to collapse
As far as I can tell, the cover is on correctly. The two clips are underneath the bottom slider so I don't think this is the issue.

dirtblade said:
Try to remove Advanced Task Killer Free. Once I did it on my phone the problem went away.
Click to expand...
Click to collapse
Again, Stock ROM with no third party apps installed and it's still happening. I'm lead to believe it's a hardware issue.

zorphnog said:
As far as I can tell, the cover is on correctly. The two clips are underneath the bottom slider so I don't think this is the issue.
Click to expand...
Click to collapse
Push harder. Trust me on this one.

[Q] Quick question

When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance

Which rom are you using?
I get what I call ghost notifications of text messages kind of the same way. I'll look at the message which clears the notification bar. When I turn off my phone at night and then back on in the morning I sometimes get a notification of the message I have all ready looked at. I think this was a problem in the international 2.2 roms hence the update to 2.2.1.
Oh, I'm using Cognition 4.1.1 ..... for now.

I am using the stock one. I haven't messed with the phone at all.
Oh ok thanks, to me it only happens when i turn it off it resends txts that i previously sent. It's kind of annoying not a big deal but gets old after a while. Thanks

I never had this problem with all ROMs I flashed. Or possibly I never noticed that happening. But I have to say that sometimes I still get double notifications for messages I have received previously after rebooting. personally I don't know why. I've tried cognition, phoenix, serendipity and now on firefly.
Sent from my SAMSUNG-SGH-I897 using XDA App

droid_07 said:
When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Click to expand...
Click to collapse
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?

modest_mandroid said:
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
Click to expand...
Click to collapse
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.

droid_07 said:
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
Click to expand...
Click to collapse
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.

modest_mandroid said:
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
Click to expand...
Click to collapse
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help

droid_07 said:
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
Click to expand...
Click to collapse
I don't know the specific range, but I remember hearing that if you bought your phone before Nov 2010, you were eligible for a replacement. I could be wrong though.. I think there's a thread about it in the general section.

Event3 Event4 and Event5

Could someone please tell me what Event3, 4 and 5 are? Those are keeping my phone from going to deepsleep. Everything was fine until january when I took a train, during the ride the battery got hot, I ahd the phone charged overnight to make sure I had a good battery all day long. Well the battery drained like crazy that day and before I got home the battery was down to 0 in less than 12 hours. From that day on, the battery was never the same. I usually don't go online or do much, just using it to make a phone call, sms and mms. Not a gmaer or big internet user. The phone is rooted, I used to get 3-4 days out of it, before a recharge was necessary, now I'm down to half a day, 12 hours. I even disconnected the phone (yes took it apart). No change. Those 3 events and then mid_pmu are on the top of the list from wakelock detector.
Please help!?

I don't know about those events. But maybe a cache clean or even a reflash could work?

Hazou said:
I don't know about those events. But maybe a cache clean or even a reflash could work?
Click to expand...
Click to collapse
No cache cleaning does not help. And I want to stay away from reflashing.

volkerc said:
No cache cleaning does not help. And I want to stay away from reflashing.
Click to expand...
Click to collapse
I would just backup everything and reflash. But if i don't want to try that i don't know. Maybe look up on the internet what those things do. Or even have a look at the kernel source and see if u can find those events.

Hazou said:
I would just backup everything and reflash. But if i don't want to try that i don't know. Maybe look up on the internet what those things do. Or even have a look at the kernel source and see if u can find those events.
Click to expand...
Click to collapse
well, that's the problem, can't find anything on the web, except one post where one thought it's wifi related. apparently google new trick is that even with wifi turned off they search for wifi to track down your location when gps and wifi is turned off! disabled receivers, used system tuner, better battery stats, wakelock detector, whatever one can think of, still, whatever i do, event 3, 4 and 5 come back to the top of the list. i used to get 3 to 4 days on one charge, now using the phone has become a joke and a drag.

volkerc said:
well, that's the problem, can't find anything on the web, except one post where one thought it's wifi related. apparently google new trick is that even with wifi turned off they search for wifi to track down your location when gps and wifi is turned off! disabled receivers, used system tuner, better battery stats, wakelock detector, whatever one can think of, still, whatever i do, event 3, 4 and 5 come back to the top of the list. i used to get 3 to 4 days on one charge, now using the phone has become a joke and a drag.
Click to expand...
Click to collapse
The event*'s are input events. u can find them under /dev/input/event*. When u execute the command getevent from terminal u get the input devices corresponding to the number. The XXX is the PID of the proces. By using ps in terminal u can get the pid of all processes and then determine the process that causes the battery wake on what input. So from there on u can investigate further. Find out what inputs are used the most en which process is using that input. Maybe u can shut down some and see what happens

I'm lost, with getevent i get a looong list.
event 3 msic_power_btn
event 4 gpio-keys
event 5 medfield_audio intel(R) Mid Audio Jack
what are the numbers(?) afters dev/input/event6::
dev/input/event6: 0003 0036 00001f2

I think I found something that doesn't belong on the phone.
Found a file/folder that keeps coming back even after deleted titled "logger" inside that folder is another folder titled "hmon" (host monitor???) spyware? the logs show all of my files, and activities. what the!

volkerc said:
I think I found something that doesn't belong on the phone.
Found a file/folder that keeps coming back even after deleted titled "logger" inside that folder is another folder titled "hmon" (host monitor???) spyware? the logs show all of my files, and activities. what the!
Click to expand...
Click to collapse
hmon can also stand for 'hardware monitor' and that is an essential part of the android system.
About the numbers: 0003 0036 00001f2. The first or second number should be the PID (proces id) that's calling the event. If u can find out what proces is using what event u maybe can disable something. Within terminal u can use the command 'ps' to get all processes with there pid shown. Compare the and find the proces that is causing all those problems.

Ok, i found that wakelock event3, 4, and 5 all have a number 358 behind them in wakelock detector. that number was found in the text files of the logger! !! 358 keeps checking for battery level in insane amounts! the text files are full of battery level and those numbers. i have 3 xt890's all are rooted the same way, have the same apps. all of them have a file logger, but only one phone goes crazy with that hmon file and continously saving text files in the folder logger. the file can be found after a restart in the internal memory and also on the external sd card. on the external sd card, lost.dir and logger folders pop up. if i delete the logger, it will come back after a while doing it's thing. so somehow the battery drain, the wakelocks are related to root, the logger and the constant "logging" of events....