I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
As strange as it sounds different kernels give me different results too. Some make my phone do Random Shutdowns and others are stable as can be.
I noticed that to, different rom/kernels would effect random shutdowns it seems. Then I spent 10 minutes on the phone with att (literally 10 minutes) and they sent me a new phone next day for $2 and I can run anything I want with zero shutdowns.
Sent from my SAMSUNG-SGH-I897
Then this and the fact that AT&T are replacing certain build and batch of phone with the shut down issue seems to point to bad RAMs. With different ROMs and Kernals, managing different apps and services and loading different parts of kernel and page swap of the RAM probably caused the shutdown. Sort of like the BSOD for windows when things go wrong with stuff in the memory. So it sounds like the AT&T shut down replacement are replacing a bad batch of RAMs. Just a thought.
overkillthemighty said:
I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
Click to expand...
Click to collapse
The official fix is sending it in to Samsung and having them replace the TIB board on your Captivate. Flashing various ROMs is YMMV and definitely not a real fix.
I cant bare this any more
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
pobinghun said:
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
Click to expand...
Click to collapse
Speedmod K12O kernel works wonders! No more shutdowns!
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
a2gtinut said:
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
Click to expand...
Click to collapse
it amazes me that there isn't already a class action law suit against Samsung.. I don't understand how they can keep producing all these phones with faulty hardware.. first there was the GPS not working then the Vibrants on Bell had faulty RAM.. now the Captivates are randomly shutting down and even the Nexus S has random reboots.. is it too much to ask to make a phone that actually works as expected?
My Captivate's random shut down "sleep of death" also disappeared.
There is no shut down with GB kernels (12.28 or 01.04 #47 kernel)
and there was also no automatic shutdown with Speedmod K12 kernels (500MHz)
I was on Darky's 7xx nd 8x ROMS.
I'm using Hamsters 6.3 ROM with Speedmod K12O 500MHz Warm kernel and ZMKP1 modem. There is no shutdows so far. Battery life is excellent.
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
pezx44 said:
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
Click to expand...
Click to collapse
I am wondering, would it resolve random shutdowns? Currently im using FF3.0, have random shutdowns.
Only true resolution is to get replacement from Samsung/Att
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
mpencexda said:
Only true resolution is to get replacement from Samsung/Att
Click to expand...
Click to collapse
Yep. My third phone has been shutdown free for over 2 months.
I downloaded load monitor and it hasnt shut down in 5 months, I was shutting down 20 times a day before i downloaded it.
what is monitor can you explaint me i have same shutting down 20 times a day only on miui i don't have such problem
Related
DO NOT RUN Advance Task Killer period. It does nothing but cause problems for the phone on eclair. Google recognized this and added a task managment solution built into froyo that works much better and won't cause random BS. If you think you know how to run ATK then you probably don't so read up on exactly what it does. Just remember people, when you boot up the phone, it starts most of these services because they are essential to the phone operating properly... imagine that. Don't try to be smarter than the phone. You are not going to save battery by removing processes out of memory. Period. Let them run. If you wanna save alot of battery, turn your display off automatic and run at a lower brightness level and turn your 3G radio off when not using data. Its that simple.
As for the speaker problem, remove the back and battery off the phoen and with your trigger or fore finger aggressively tap 1 time on the speaker grill and your sound should work when you boot the phone up. This action could be described as thumping the grill with your finger. I know this is a caveman way to repair a phone and is closely related to the beavis and butthead "kicking method" but it works almost every time.
Hope this thread helps. Your comments are very welcomed. Tell me what you are thinking....
Thanks for the info. I use ATK, but not in a harmful way (haven't experienced issues or random shutdowns). I have an extensive ignore list (of things that need to stay open) and security set to high, so system processes won't even show up, so it's impossible for me to kill them.
Sent from my SAMSUNG-SGH-I897 using XDA App
BTW... Just to qualify myself a bit. I am samsung certified and I am running a Captivate on the Leaked froyo, rooted, sideloaded, overclocked to 1.2ghz, verizon market fingerprint build.prop mod, LCD density mod = 210, startup sound mod, battery percentage in task bar.
well thanks for the inside scoop. so we can expect a major OTA update around christmas for the US market?
i will be removing my ATK program today. I've also been using Captivate Keep Alive, which apparently opens up a ton of applications to keep your phone active and prevent it from entering that "comatose" state i think.
Thanks for the info!
Can you recommend another easy way, besides ATK, to shut down all of the unwanted AT&T programs that load during startup?
Great info, thanks!
Hope you are right, but software issue is hard to explain my case. The first one I got had shut down 4 times within a hour(worst case, usually 2 or 3 times a day), and the replacement been used about 2 months, never had an unexpected shut down. Both of them are unroot, no side-loading, and never use ATK.
danalo1979, since you have the inside scoop, will there be any GPS improvements, or is it as good as it will ever get?
Thanks for the info on the speaker problem. I just had my phone swapped out for this problem. I wish the person I called into at AT&T would have told me about the Cave Man method.
Thanks for the interesting information.
dm
evosky said:
well thanks for the inside scoop. so we can expect a major OTA update around christmas for the US market?
i will be removing my ATK program today. I've also been using Captivate Keep Alive, which apparently opens up a ton of applications to keep your phone active and prevent it from entering that "comatose" state i think.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
JRd1st said:
Thanks for the info!
Can you recommend another easy way, besides ATK, to shut down all of the unwanted AT&T programs that load during startup?
Click to expand...
Click to collapse
Root your phone, get root explorer, go to system>app> go to desired apk file that you want to disable and rename to.bak extension and the os wont recognize the program. Its reversable just rename back to apk. Reboot phone. Don't do this on anything that is required for the phone to run.
Sent from my SAMSUNG-SGH-I897 using XDA App
So the random shutdown is only an issue for eclair roms? Kinda explains why I haven't had any shutdowns since flashing cognition.
Also, I find it kinda funny that an AT&T employee has his captivate sideloaded (no offense! Just wondering why AT&T would even want to block sideloading apk's..)
And the ETA for the OTA sounds very disappointing.... late Dec~late Feb...
Just had a shutdown, running Cognition 2.3b4. Have had other shutdowns while on Cognition.
I've been on 2.2 of some sort since it leaked. Mine has shutdown as often as 3 times in a day. from 100 to 50% battery charge. There is no ryme or reason that I can identify except: While running system panel; When you look at the graphs for the time period that a shutdown occurs I notice that the battery charge graph will suddenly drop like a rock, like 50% of what's left and then when i turn it on it initially reports the lower amount but by the time it boots it shows a "correct" representation of the battery charge. THAT is consistent for every shutdown. Sudden drop (50%ish) and it reports low on startup and jumps just the same.
Random shutdowns on Froyo but not Eclair
Well I'm on my second captivate, first one random shutdowns from day one.
I have gone months with no shutdown while running stock Eclair. The day I flashed the leaked Froyo or Cog I recieve random shuts within a few hours. I tried flashing back to stock/master clear/ battery stats all with the same results
For me with stock Eclair no random shutdowns
with Leaked Froyo or Cog I get random shutdown within a few hours
Frustrating
dhncali420 said:
For me with stock Eclair no random shutdowns
with Leaked Froyo or Cog I get random shutdown within a few hours
Click to expand...
Click to collapse
So are you able to restore to a point that does not produce shutdowns? If so, what method of restore?
jswclw said:
So are you able to restore to a point that does not produce shutdowns? If so, what method of restore?
Click to expand...
Click to collapse
Flash Stock J6 from here:
http://forum.xda-developers.com/showthread.php?t=731989
after going back to stock 2.1 no shutdowns for over 2 weeks.
Last week flashed cog 2.3B6 couldn't take being on 2.1 anymore....shutdown within a few hours, installed CPU tuner and no shutdowns for 5 days so far running cog 2.3b6
If I had one shutdown running stock 2.1 I would return it
Dear OP, first off, I believe what who you say you are and what you wrote. Thank you for being open and honest. I am bone stock ATT 1010 v.004 phone build with a 09-17-2010 battery. When phone is completely stock it does not shutdown overnight. As soon as I add an APP, I get the overnight shutdown regardless of battery condition. I see that many apps say they need access the power keep alive function of the OS. Now I am not running homebrew apps or any mods as mentioned. I tried basics like Kindle or eBay or Chase Bank. I am 7 days into my phone and need it to stay on, so I can use the alarm etc. What do you recommend I do? Just keep returning it so I stay inside my 30-day window? Jump to a WM Samsung? iPhone4?
Can you also PUSH PUSH PUSH ATT to get this corrected. Samsung and ATT did not publicly acknowledge the problem on the three times I called, but only said if I returned the phone and got a new one, I would NOT have the problem again. Why is that? What do they know?
Thanks!
StevenMP said:
What do they know?
Click to expand...
Click to collapse
No offense to OP, but both Samsung and AT&T know how to lie quite well. Especially if it serves to screw you so they get more money.
fatbas202 said:
No offense to OP, but both Samsung and AT&T know how to lie quite well. Especially if it serves to screw you so they get more money.
Click to expand...
Click to collapse
LOL.. I agree
My captivate works fine when running a non rooted stock rom, but as soon as I root it and load my apps it starts to get random shutdowns, so it's not overclocking or undervolting. I'm on darky's right now, and I am getting several shutdowns a day. I tried un installing multiple apps with root access to no avail.. Is it possible for a non root app to cause shut downs? I sent my phone in and it was sent back just fine because it was on stock eclair. I don't want to have to trade it in for an iphone but if it continues to shut down I will. Is there any way to diagnose the problem, or even fix it? I think it is an app issue.
Sent from my SAMSUNG-SGH-I897 using XDA App
Did you try a different kernel? All phones react different, I can't currently use i9000 roms. Worth a shot.
Caution swyping! Read at your own risk.
I tried Darky's and I got the same thing. I have switched to FireFly and have had no problems at all. Paragon is a good ROM as well.
I had the same problem but I would only have the majority of my shut downs within the first 10% of my battery after a full charge. After that for the most part, it would be just fine after that. I'm using cog 4.1 and have been for the last few months and I can count on 1 hand the number of times it shut off. I found that after a full charge,immediately after taking it off the charger, reboot the phone and it runs all day with no problem since I started doing that.
Sent from my SAMSUNG-SGH-I897 using XDA App
My best guess is that the officially confirmed bad ram problem is to blame. the rooted apps might be accessing bad sections of the ram and causing crashes. It makes sense that the frequency changes depending on which rom you are using since they all handle ram management differently
Sent from my SAMSUNG-SGH-I897 using XDA App
See I would think it was my kernel or rom if it didnt happen on stock eclair. It happens at any battery percentage.. I really don't know what to do. I might be able to trade it for an Iphone 3gs.. I really want to keep the phone but it seems like I might be stuck with a permanently shutting down phone.. which I can't keep.
How long have you had it? I just returned mine for a new/refurbed one a few days ago. I bought mine in Oct. I'm lucky enough to have a ATT service store near me. Went in, told them I had the shut down problem. Swapped phones and out the door. They are honoring the 1yr replacement from Samsung. Got a 1009 that has perfect GPS, for now, haha.
I got mine refurb, and sent it in to samsung, no go. Do you think an att store in a mall would honor the one year?
Sent from my SAMSUNG-SGH-I897 using XDA App
Since yours was refurbed, I think the warranty is limited by everyone to 30 days. Mine was new. One of the few perks to NOT getting a refurb.
I had same problem running seremdipity . Now i run continue and no more shut downs. I guess u should try other Rom like mentioned before
Sent from my GT-I9000 using XDA App
Give AT&T a call via 611 or their 800 number. I think the refurb policy is actually 90 days, but from my experience, if you complain hard enough and be rational and reasonable about your requests, they usually budge. I had the same shut down problem with my captivate. First thing they did was send me a new battery in case that was the problem, didn't have to return my original battery so I now have 2. Then after another call back, they told me to go to the service center and I swapped it out in under 3 minutes no problem. Just make sure to Odin to stock before returning your phone.
install setcpu app and set your min clock to 200 that helped some people with shutdown issues
I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks
yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...
Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App
My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.
Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App
Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.
My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.
Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.
I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.
Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....
I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999
Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.
For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk
Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App
Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob
ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.
Anyone else have issues with random shutoffs? I would lay the phone down and come back later seeing that the phone is off. The first few times was OK with me, but now I feel like I have to check to see if my phone is on every chance I have. It doesn't happen all the time. Sometimes I would go days without it occurring. Other times it would happen once or twice a day.
I have latest Weapon with Faux 123 kernal.
Just a problem with the phone. Lg knowd this just havent fixed it.
Sent from my LG-P999 using XDA App
So do they know what's causing it to happen? Is there anyway that we can log events so that we can get an idea of what's happening just before the shutoff?
Happens to me occasionally with CM7 stable. Mostly at night on the charger, which is annoying since my phone is my alarm, but it has happened a couple times during the day.
This was happening to me on rooted stock but I switched to weapon 2.8 a couple days ago and it's been better. It may just have needed to be wiped but who knows. I'm still using my clock radio alarm due to paranoia for a few more days lol.
chinh_tran said:
So do they know what's causing it to happen? Is there anyway that we can log events so that we can get an idea of what's happening just before the shutoff?
Click to expand...
Click to collapse
Yea they know. I belive its a hardware or driver problem. You can search this board n there is a post about lg stop tmobile from exchanging the lg due to this problem n a few others.
I had my phone shut down an reboot a few times now. Maybe 5-6 times. Had the phone since oct n been on stock rooted gb since .
gshine said:
Happens to me occasionally with CM7 stable. Mostly at night on the charger, which is annoying since my phone is my alarm, but it has happened a couple times during the day.
Click to expand...
Click to collapse
same thing happens with me sometimes. I'm on the latests MIUI by whitehawkx. seems to be a SOD issue since i have to do a battery pull for it to turn back on
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.
I will give you $20.00 a piece for them!!!!
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7
Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app
Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Android Law #1: Costum ROMs are ALWAYS 10x better than stock.
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium
qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?
ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl