Related
For those who have used their warrantee to get a refurbished phone, is it working better than the new one you had? OR are you still experiencing problems? If so, what kind of problems are you experiencing (random shutdowns, reboots, no 3 button recovery, etc)? Chime in!
I have been using a "refurbished " phone now for over 20 days and dont have any issues.. The only problem I was having was with the batteries overheating and that was solved when att kindly sent me a new battery free of charge.
I also dont think the phone is really refurbished.. How can they refurbish something so quickly??
I have a warranty swap also. There is just no way this thing was a refurb I completely agree. No marks on any part of it and screen is perfect covered in original plastic. Refurbs will take a few more months to show up I think. My warranty swap doesn't freeze on me anymore but gps can't really lock still..
three button works fine btw
thanks for the replies guys. this eases my mind. my phone has randomly shut off on me. i dont want to risk setting an alarm for work/school and not being able to wake up because the phone turned off.
anyone else w/ refurbished phones?
Should have mine Tuesday, Wednesday at the latest. My current one shuts down every time I power it on and let it idle for a few minutes. I didn't even bother turning the phone on today but like 3 times. My first Captivate was perfectly fine, but somehow it got a scratch on the screen, so I decided to swap it for a new one. Now this one has the shut downs non stop all day.
88EVGAFTW said:
Should have mine Tuesday, Wednesday at the latest. My current one shuts down every time I power it on and let it idle for a few minutes. I didn't even bother turning the phone on today but like 3 times. My first Captivate was perfectly fine, but somehow it got a scratch on the screen, so I decided to swap it for a new one. Now this one has the shut downs non stop all day.
Click to expand...
Click to collapse
please chime back in and let us know how the new phone is. let me know if it looks brand new
bump......
Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem
I understand that there are a couple of topics opened for this but I wanted to have a new one with the title showing that a solution has been found as I want to help other who are experiencing the problem.
I'm not sure if this would resolve the issue for you but it did for me so please don't blame me if it didn't work for you, I say this because the solution requires an install of a paid app.
So I've had my transformer for 2 weeks and the SOD has been happening since day 1, it would happen every time I left my transformer asleep for more than 2-10 minutes (WIFI on or off). I've tried everything but could not resolve the issue. The only time the SOD didn't happen is when I had it plugged into the charger.
Solution: WidgetLocker, it's an SOD killer
All I did was install it and left everything as is, I also made sure that the stock lock screen is disabled.
I dont think it's widget locker that fixed the problem its disabling the stock lock screen. I had the sleep issue the first few days I had the xformer but after disblong the lock screen it went away.
Sent from my Transformer TF101 using XDA Premium App
I had SOD issues when I had Juice Defender installed. I knew it was causing the problem because it started happening right after it was installed. Haven't had one SOD occurrence since I removed it.
I had te stock lock screen disabled for days but the problem never went away until I installed widgetlocker.
I don't want to be a Debbie Downer, but I think you'll find the SOD will reappear when you least expect it. Mine didn't do it for well over a week after I fiddled with all the suggestions offered on this forum, and now it's just as random as ever. I hope 3.1 fixes this, but it sounds a lot like a Transformer issue rather than a HC issue, since you don't hear the Xoom or Iconia owners complaining about the same thing.
Anyone else tried this?
Thanks
the SoD is probably caused by the big frequency/voltage jump when you wake the system up. This is probably what's freezing the system. Someone with a rooted transformer that's having the issues should get the netformer kernel and sit minimum frequency to something higher (400~600 MHz) and see if they still get the problem.
FYI: We had the same problem with the HTC hero when some hero's would lock up when asleep when you set the minimum frequency too low which meant they made a big frequency jump when the screen got turned on.
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
L0$t$0ul said:
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
Click to expand...
Click to collapse
I don't think we've had the screen waking up issue.
It's been over 24 hours and not a single SOD since installing WL. I used to get it SOD every time I left my ASUS unused for few minutes.
If I use dock I never have that problem only without dock.
Glad to hear the wake issue isn't happening here. It's really annoying. Just had my acer not wake up again though. Happens at least once a day.
seshmaru said:
I don't think we've had the screen waking up issue.
Click to expand...
Click to collapse
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
steftymo said:
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
Click to expand...
Click to collapse
3.1 update fixed this for me and no Widgetlocker is needed.
Hi everyone.. I searched a bit but couldn't come up with any more answers so I'm wondering if I missed something.
I've had my TF since like May, and for as long as I've had it, I've had this issue.
No matter what kernel or Rom or anything, my TF always randomly reboots ONLY when my screen is shut off and the wireless is left on. It doesn't reboot if I'm using it, and the only way to make it not happen is to turn on airplane mode when I'm done with it.
Its not a big deal, but it is annoying, especially if I leave it in the living room and forget airplane mode. Then whoever is in there gets to watch my TV constantly and randomly reboot every few minutes.
Its just more annoying than anything. Id love to just keep wifi active so it automatically connects when I turn the screen on.
Other than this, my TF has been flawless for like 6 months
Thanks if anyone has any information!
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
avlon said:
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
Click to expand...
Click to collapse
Wow, ill have to give this a try. I've never used the pattern lockscreen.
random reboots
I get this after about an hour of use. If I sitch it off via the button then when I press it again it reboots. If I just let th TF switch itself off (after 5 mins) it switches on normally when I press the start button.
I also had similar problems with my wife's TF, it rebooted randomly just about anytime (not just with screen off), apps crashing randomly. When I returned it to the store where I bought it, they immediately replaced it with a new one that doesn't suffer any of those problems.
If you have such problems, I'd recommend taking it back to the store for repair, because that is definitely not the expected behavior.
unfortunately the lock screen thing didn't work
Can't really take the thing back, I've had it for months.... fortunately this is the only issue I have... I can live with it. Its purely an annoyance that doesn't affect me when using it...
I installed a stable version of cyanogenmod 9 on my phone and the system was working perfectly, but I spent some time without using it because it didn't have any signal(I think its aerial is broken). After some time I decided to try to fix it, so I turned it on. It booted normally, but shortly it turned off by itself. Then I tried to turned it on again successfully, but again it turned off. I thought it was the battery so I plugged the phone, but it wasn't showing any sign of being charged. So I tried to charge the battery out of the phone and I checked its voltage, but when I put it back in the phone, it didn't work. The only thing I see, when I try to turn it on is a dim red light in the trackpad.
Any ideas of what happened? Is this reversible?
Thanks in advance.
I'm no expert, but it unfortunately sounds bricked to me.
Similar thing happened on my 1st MT4GS after like a week of owning it. We were on vacation and I was playing fruit ninja, slashing happily away as the phone was plugged in for bedtime. All of a sudden it turns off. I'm like WTF, it was charging! But it apparently wasn't, and similar symptoms to you. No other lights/charge/indication of anything working. Just the dim red light in the track pad I could get to go on and off. Since it was just over a month old after I got back from vacation, I wound up having to ship to HTC rather than walk out with a new one from t-mobile, but they sent me a replacement I've been using since.
So sorry I don't have better news, but it sounds like what happened to me, and it was dead and had to be replaced.
Hi,
This has happened to me two or three times but thankfully I have a few other devices so I needn't worry much.
When this happens I take out sim, SD and battery for a week or so. Upon reinserting battery all was good each time.
If you have a spare try it, I can't say for sure if we are on the same boat but its worth a shot before throwing it away.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Edit
Here is a link that I and a few other discussed our issues, none the same but all similar.
http://forum.xda-developers.com/showthread.php?t=2257451
Also there are plenty of other threads I seen on this as well, search around a bit and hopefully you'll find an answer
Best of luck!
So there's some threads I just shouldn't read ...
After coming across this today my phone has started turning off by itself (doing routine things, like pressing the "Read" button on an SMS). There's gotta be a weird coincidence there (I had an underclock issue where the screen wouldn't come on a couple months ago while earlier that day I was reading the post on how to replace a bad LCD panel - so I get to overreact like that).
I think my issue is more about battery as I have been tracking it the past several hours (three shutdowns in a row at 60% battery, and then one ten minutes ago at 20%) but it continues to work itself out (with some weird stuff like notification panel crashing on me on one of the last reboots).
I have what I presume is a cheap 1900mAh battery (EZOPower) that is starting to show it's wrinkles. I have dropped the max processor speed a notch according to a recommendation in this post:
http://forum.xda-developers.com/showthread.php?t=2753720
...hopefully that was the issue. I nandroid'd my device just in case something goes wrong. If it continues, I'll swap batteries and see.
I'm hesitant to shell out for a couple Ankers because I currently have my eye on the LG Optimus F3Q (although getting one would be three months away, I gotta have priorities).