Database Users

Random shutdowns?

Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App

kopykatkiller said:
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This happen to me yesterday 3 times after the phone's screen was off for more than 10 min
I uninstalled setcpu and it never happened again so far.

Ok maybe it is a setcpu setting that is defaulting wrong. Anyone with setcpu installed that is not experiencing this? If so, what are your settings?
Sent from my SGH-T959 using XDA App

i also had this happen to me w/ setcpu active, i have yet to have it happen w/o setcpu

Happened with setcpu to me to. Removed it no problem since.

Same as everyone else. W/ SetCPU it happens. W/o SetCPU it doesn't.
Just sent the dev a message to let him know of the situation. http://twitter.com/MINUS_Stl/status/18719463969

Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.

Ya know. I did actually change it to ondemand seeing as that's what I always used on my G1. Gonna reinstall and see how we do. Will definitely report back. Thanks.
UPDATE: 1 hour in on 'conservative' and all is good.

I probably have to put a warning or something for Galaxy S for ondemand. It's probably a kernel flaw for that.
For now, it looks like conservative is 100% stable, haven't had reports of crashes on it.

Yeah, I'd say conservative is it. Thanks, bro.

Yes, before the reply about the conservative setting I had messed with it and set to that. Wanted to verify before posting, but as stated that appears that is the key. Thanks guys.
Loving this phone by the way.
Sent from my SGH-T959 using XDA App

coolbho3000 said:
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Click to expand...
Click to collapse
I had SetCPU set to Conservative since I installed it. Yesterday it randomly powered off 6 times. I found this post and deleted SetCPU and am currently using Overclock widget. So far I haven't had it power off.
Has anyone else had this issue while having it set to conservative?

Yes! I changed my charger and it hasn't happened ever since.
Sent from my SGH-T959 using XDA App

i have also noticed that if i set a profile so that the cpu has a max of 400mhz while screen is off it will crash on me randomly. i have to keep it at at least 800mhz. It has just started doing this.
also does anybody know if it is dangerous to run in performance mode at a constant 1000mhz? it makes my phone super fast(obviously) but sounds dangerous making it run at maximum power constantly while the screen is on.

I've never used or installed SetCPU and my phone was shutting down by itself as well and had to do the battery pull to get it back on. I found it to be the "Power saving mode" in the display setting. Ever since I turned it off it has not shut down.

I also experienced this once when I try to install setcpu on my vibrant running bionix-v 1.2. Uninstalled it and it never happend again. =)

Just use the stock kernel.
Sent from my SGH-T959 using XDA App

this used to happen to me all the time so I got a replacement from tmobile but it continued to happen. It finally stopped when i rooted and flashed my phone

This thread is quite old, and while I do appreciate the contributions, it was long ago when this was posted and was dealing with a very early version of the over-clocked kernel. Please let this thread die, so that current ones maintain priority.
Sent from my SGH-T959 using XDA App

at least you guys are getting something. My phone shuts down 1-3 times a day. it is whether its rooted or not, customized rom or not. It just like to go to deep sleep really bad. Hopefully I can exchange it. But i just get my gps fixed, i dont know if i will get a new one with crappy gps.

Hit unlock - screen blinks one and off

So recently here I've been having an issue with my G2. After hitting the unlock button to wake the G2 up, the screen struggles to light up and sometimes it doesn't at all!
When this happens I have to hit the unlock button multiple times just to get the screen to wake itself up, is this happening to anyone else?
Thank god my 3rd G2 is on its way, I should have it tomorrow.

I'm having the same issue also. I think the issue is from setting the CPU down while the screen is off.

Could this be because we've got out G2 oc to 1.42ghz+?
Sent from my T-Mobile G2 using XDA App

My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App

EdTeach1680 said:
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well that answers that question lol
Sent from my T-Mobile G2 using XDA App

also have this problem, i usually just open the keyboard.

My stock phone did this...I was under the impression it was some issue with the unlock button. Tmo sent a new one and my replacement hasn't had any issues.
Sent from my T-Mobile G2 using XDA App

This started happening to me when I ran that app that blinked the notification lights when you got a text/voicemail/whatever. (sorry, can't remember what it was called...) When I uninstalled it, it went back to working properly.
[edit - NoLED is the app that was causing it for me.]

Having this same problem, and its extremely frustrating. Sometimes it goes away for a few mins, but most of the time I have to keep pressing the power button till the screen stays on. For some reason, it registers almost every press of the power button as 2. As someone said in one of the above posts, it might have to do with setcpu's screen off profile, but turning that off doesn't solve it for me =(
Sent from my HTC Vision using XDA App

I have this same problem. I was wondering if it was maybe baconbits or setcpu. It never really happened before I got perma root and installed baconbits. Sometimes flipping out the keyboard doesnt even unlock the phone.

I don't know about stock. But this def happened with baconbits for me. I flashed the 2 different sense roms and whenever i applied the baconbits kernel for those roms i had the issues, once i flashed a different kernels I was fine again. So I'll have to pass on bb for now. I hope they can fix this issue because the setcpu settings were great with it.

It happened with my first stock G2. At first I just dealt with it, but then I checked out my wife's G2 (purchased together) and her's worked perfectly. I eventually decided to go though the hassle of getting a replacement from Wirelfy. The replacement's been working fine after perm root & OC.

Install ota and you won't have this problem.
[G2/HTC Vision]

Try removing the setcpu widget from your screen, it seems to have fixed it for me

This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.

xeduran said:
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
Click to expand...
Click to collapse
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?

Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
trying this too. The problem seemed to start when I overclocked the cpu. very annoying

Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
Interactive ramps up to your max speed faster and ramps down from the max slower. So you basically get a little faster performance than ondemand, but at the cost of a little more battery usage. I do not think the battery usage is very significant though.

[Q] Fascinate Won't Wake from Sleep/Screen Off

My brother and I both got Fascinates this month. Both are rooted, but only mine is upgraded to DJ05. We are both loving the phone except, both of us have a problem where the screen/phone will not wake up from sleep sometimes. It will just show a black screen, it even happened while talking on the phone today, the screen didn't wake when I got off the phone. I've done a few searches and on some other phones people suggested setting SetCP to at least one higher then the minimum when it's in screen off mode, but I just tried that and had the same issue 5 minutes later. With all the development going on, I'm hoping that someone may have found a fix for it. Does anyone else have this problem or know of a solution? I apologize if there is another thread in the fascinate forum about this, I did a few searches, but didn't see anything.
Thanks,
Ryan

You could help yourself by stating what rom version and what specific kernel you are using. And if you are using a task killer and or power managment app.
good day.

Sorry if I wasn't clear enough. We are both rooted, but my brother is otherwise running stock. No task manager, just Setcpu. I upgraded to DJ05 and installed JTs Superclean w/non voodoo and rom. But I wouldn't think that'd be the problem considering he's running stock. Maybe it's setcpu? If so is their another comparable manager for battery life that someone might suggest, I can see if that fixes it?

Setcpu offers no benefit to devices using a stock kernel only good for over clocked kernels. If the problem at hand didn't start until installing setcpu, then you have your answer. I myself do not use any power management apps so I can't speak for them.
good day.

Did you by any chance install something that adjusts the brightness of your screen?

If your running Setcpu and your having problems waking up the phone, are you running a profile for the screen off? You can't run profiles on Sammy phones, they don't like it.

No, no brightness apps.
Yes, I was running a profile for screen off and stuff. That was the whole point of Setcpu, I thought, so you could reduce it when the battery started getting low and the phone wasn't being used. Thanks for the info, I uninstalled it. I guess that's the problem. Only time will tell though. Do you know of any other reputable apps that would be similar to Setcpu?

Why not try geeks last kernel? I believe it was uv and should help battery life if that's what you're going for.

I would, but people have had some issues with them from what I hear, besides he's no longer developing them or supporting them, so sooner or later I'd be changing anyway. Maybe I'll check out juice defender.

You can keep setcpu, just don't use any profiles lol and keep it on conservative
Sent from my SCH-I500 using XDA App

Does it actually do anything for you though to help save battery life without the profiles?

Just because he isn't deving for the sf doesnt mean that his kernels are worse than the stock one...I use adryn's 12/17 test 2 and get amazing battery life..14 hrs at like 60-65% but it's voodoo and you will prob not want that.

setcpu will change the ramp up/ramp down speed...more time at max when you need it more time at min when you dont...i don't think it will help nearly as much as proper kernel

Gingerbread - high CPU utlization by "System"

On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.

Do u have any OC kernels in there or just stock GB?
Sent from my MB860 using XDA Premium App

I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.

frelnik said:
I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.
Click to expand...
Click to collapse
I had the same problem, when you delete all data from fastboot (fastboot-w), install 2.3.4 gingerbread returned and the battery lasts me about the same as the stock 2.1.1 FR. (taking into account that spends more battery 2.3.4). now I have the Orange Radio 2.3.4 with kernel faux123 0.100.00R. sorry for my English

I've run fastboot -w, and used CWM to clear data/cache both before installing ROMs and after installing ROMs, and none of that made a difference. BUT last night I installed kennethpenn's Beta 4, and for the first time, my CPU frequencies were properly scaling, and System was not taking up 40%. Since then, I've wiped data/cache and tried different kernels and different ROMs, and all of them are working. It's almost as though kennethpenn's ROM installed something that wasn't there previously and is persisting through wipes, and ROM/kernel installations. Is that even possible?

freeze your bloat.
use setcpu for system profiles.
problem solved.

For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.

Magnetox said:
freeze your bloat.
use setcpu for system profiles.
problem solved.
Click to expand...
Click to collapse
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.

stewartsoda said:
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.
Click to expand...
Click to collapse
You're right. This wasn't in 1.83. But if you freeze your bloat and use setcpu profiles, you will get 2 days of use from your phone.
Sent from my MB860 using Tapatalk

frelnik said:
On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.
Click to expand...
Click to collapse
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App

maledyris said:
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Freeze the bloat on your phone and use edgan's international kernel. I'm getting 24-30 hours on my bell atrix on 2.3.4 orange.

jaysonsantos said:
For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.
Click to expand...
Click to collapse
That's pretty much what I was getting as well. X was always second to display in terms of battery usage, and it seemed to be using the CPU constantly whenever the phone was awake. I'm not sure what to make of it, what with some people seeing it and some people not. All I know is that after I tried kennethpenn's ROM, X disappeared, and my CPU seems not to be occupied nonstop. Since then I've wiped my phone and installed the Ninja ROM and faux's stock international kernel, and my phone continues to function without X eating up the CPU. This was the exactly same setup that, prior to kennethpenn's ROM, was suffering from constant high CPU usage. No idea what changed it, but now things *seem* to be operating normally and my battery is much improved.

I solved it renaming "/etc/X11" to "/etc/X11.bkp". So... X process magically disappeared!!!

Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App

Sass86 said:
Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Open setcpu. Go to profiles. Then quit and go back in to setcpu and it should stick. Don't know why. I'm going to try a profile to keep it at 1100 like temp over 0. Who knows.
Sent from my MB860 using Tapatalk

Funny. I opened setcpu and it was back at 1300, so my solution is moot. I did just set a profile if battery is below 101% then scale to 1100 low priority (40)
Sent from my MB860 using Tapatalk

I don't know what the deal is. Set cpu tells me the clock is set to 1100. Which matches cm7 settings which also matches system panel. But watching the cpu speed in setcpu it will go to 1300. So yeah. Back to the drawing board.
Sent from my MB860 using Tapatalk

Bear with me. Not spamming. Here's my deal. Most people's governors are greyed out. Mine is not. Tasker, system monitor show it which then allows setcpu to show it. If I'm on powersave the clock will not stick to my setting of 1100. If I set it to performance. It sticks. Any one confirm or deny?
Sent from my MB860 using Tapatalk

I was seeing the same thing until I made a profile for Battery < 101 max at 1000 and a priority of 80%. Now every time I open setcpu he cpu maxes as 1000.

Indeed.. atrix with stock kernel runs all the time at high freqs..
with faux kernel, is at lowest value, so we save battery.
does it have a governor enabled by default or something?
whatever he did, its pretty good!
Imagine that with undervolt..

[FIXED] having issues.. EDIT! ram issue! Edit 2: fixed! sd card issue

im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Edit: ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?

murso74 said:
im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Click to expand...
Click to collapse
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera

Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.

poit said:
Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.
Click to expand...
Click to collapse
i never restore data from nandroid backups and i reinstall all my apps from the market...
maybe my phone is tired
modem seems to be resetting alot too

murso74 said:
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera
Click to expand...
Click to collapse
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue

murso74 said:
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue
Click to expand...
Click to collapse
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk

JohnCorleone said:
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance

murso74 said:
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance
Click to expand...
Click to collapse
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?

megabiteg said:
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?
Click to expand...
Click to collapse
i've had the phone for a year. i've been doign roms for at least 6 months.. this only started in the last month on both rfs and ext4. i don't know what i did that could have done this.. honestly i started noticing it when i odined back to EC05 a few weeks ago. then i did an rfs rom, then drockstars kernal, now srf 1.2 and tz kernal. just seems to be getting worse and worse. to be honest it may have started after i flashed back from eh22

Are you on TW4 Launcher? That can cause phone to freeze.

Overstew said:
Are you on TW4 Launcher? That can cause phone to freeze.
Click to expand...
Click to collapse
i am actually.... although this started before the tw4 launcher. i guess i'll remove it for a while and see what happens. dammit i liked the tw4 launcher too

Don't use any CPU programs like setcpu, etc.. if not try wiping your sd card. Could just be your phone too.
Sent from my SPH-D700 using Tapatalk

I had this issue for a while and it caused me to leave to the iPhone, but now after months of waiting I am trying to bring my epic back
I will post my results I am going to try flashing back to stock and see it if can stay on for a day with out crashing....I'll be back with results in a day or 2

Mine does the same thing and it shuts off sometimes at 35% battery left. Just in the past month. Im stock not rooted. One more thing somedays i get 13 hrs of life and others like 6, same usage everyday and same area so service isnt the issue.
Sent from my SPH-D700 using XDA App

I had this same issue. I was to a point of chamging phones.
I decided to watch 5 different tutorials/youtibe videos on how to odin back to stock.
In that process, 3 of the videos had different options checked. Yes, I decided to try each way, restoring apps/data from Titanium, each time.
After the first 2 attempts, and still seeing the freezes, I started to get some kind of com.google.apps process force close errors.
I was really ready to beat my phone up at this point.
So, after deciding, I've had enough, I said I would do it ONE more time. (There was still one more checkbox that another video was showing...)
Sent from my SPH-D700 using XDA Premium App

Sry, my fat fingers pressed submit.
Anyhow, Ive 0 programming experience so, all of this might kust be a lucky fluke. When I odin'd, I checked all three options. Re-Partition, Autoreboot, And F. Reset Time.
Only 1 video of the 4 I watched said to do this.
I then restored my apps and data back w/ Titanium.
I did make sure that any data from OEM apps, was not broight back, as a precaitonary on my part. It was really driving me nuts. Hope this helps....
Sent from my SPH-D700 using XDA Premium App

crap well it wasn't TW4... uninstalled it last night. today rebooted and same thing.... its so strange it only happens the most after i reboot the phone. black screen with the status bar up top. if i touch the screen the button lights will come on ... if i swipe down the status bar it will eventually come down.. but with a ton of lag
i guess i'll nandroid backup and start from scratch with odin again. bone stock no root see what happens.
EDIT: just noticed that the modem seems to reset every time it does this. didn't see that before cause it doesn't always make the no signal sound. but the bars on the status screen go dark and the little x pops up above them before the home screen redraws. so basically whatever i'm doing goes to black screen.. times out for 10 min with just the bar on top, modem resets and goes back to the home screen

ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?
man this is nuts... i've got android system info running and i'm watching the processes tab... all the programs start usign memory, then android starts killing them off until they are almost all gone then i go to black screen... i dont' know what the hell is going on
edit: tasks is showing android.process.acore twice, package com.fede.launcher. both are using 34.89 MB and have cpu at 100... however total CPU usage is only showing 7%