Half the time when I try to go to a website the Fuze just times out. Loads forever and times out.
When it doesn't time out, it's slow as molasses.
I can throw my SIM in either of my other two 3G phones, sitting in the exact same spot, and everything flows just fine.
Anyone else having this issue?
I'm about ready to take this back, after months of waiting for its release, because the data connection is so unreliable.
have you tried tweaking it and maybe flash to another rom?
or maybe you just have a lemon. Get it exchanged and see if problem persists.
baboola said:
have you tried tweaking it and maybe flash to another rom?
or maybe you just have a lemon. Get it exchanged and see if problem persists.
Click to expand...
Click to collapse
Have already returned it for a different one. Exact same issue. Actually I've posted a lot of details about this, if you look at my other posts.
Many others are having this same issue. Many others in the threads on here, like the HSDPA / 3G Fuze threads. Here's a guy on ATT forums with the exact same symptoms as me: http://forums.wireless.att.com/cng/board/message?board.id=cingular&thread.id=108522
I do not want to flash to a different ROM because I saw someone in another thread post that they tried flashing back to the stock ATT ROM and it didn't work. Haven't seen anyone post saying that it DOES work for this specific phone to the ATT ROM.
If it was just "kinda slow" I would mess with tweaks and other ROMs, but the fact that it's literally unusable makes me want to just give up and possibly re-buy the phone if and when a REAL fix for it comes along.
The frustrating thing is it seems like about half people are getting awesome speeds on this phone, and the other half are getting abysmal, unusable speeds. I've seen a lot of posts on here of people saying they're just returning the Fuze as it's useless. I'm so disappointed, I really wanted this phone bad.
I'm sorry to hear that. I'm actually on my second Fuze right now (returned the first one for some stupid reason). Both phones had around the same speed. It's not stellar, but at least it's not doing terribly worse than my friend's iphone 3g, which I use as a comparison cuz we all know they're the connection hoggers.
Have you tried calling AT&T tech support? They've been extremely helpful with some of my questions.
Lastly, why not just flash it? May people are having a bit of a problem getting stock ROM to work after flashing it back, but if you're going to exchange it, who said the stock ROM has to work flawlessly? Besides, someone will eventually find a way to fully re-flash stock ROM soon, not that I'd ever understand why anyone would want to do that aside for warranty purposes.
I would bring your phone to AT&T store, talk to the manager (chances are someone working there also has a Fuze). Tell them your problem and ask them to do a comparison. Cuz right now I can only think of two possibilities:
1) you got 2 lemons in a row
2) Stock ROM really sucks
Good luck
Thanks man. I might just try a flash and see. I have not called tech support yet even though I've been thinking about doing that for days, because it's such a hair pulling experience, i just hate going through the phone systems and then getting people who don't have a clue what your'e talking about.
I did email the manager of the store, mainly about a different issue I had with the process and the associate (who lied to my face repeatedly, but i wont go into details) and mentioned the problems i'm having with my phone and the fact that the replacement is the same way.
I also live in OC (southern cal) and have heard others are having issues w 3G in general here. However the fact remains that my other two 3G phones work perfectly for me.
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
pezx44 said:
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
Click to expand...
Click to collapse
My guess is you guys have tried to overclock and your phone really didn't like it and caused some minor damage. I have heard reports from stock 2.1, 2.2 and Cognition, most of them I have talked to have tried overclocking at some point. If you haven't, maybe just faulty hardware out of the box, if you can flash stock and it still happens, take it back and exchange it.
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
I only had overclocking on my phone once in a sre build and tested it once and found it worthless to me so i disabled it.
Anyways i have never had an issue with shut downs prior to flashing ji6. Now when i leave my phone plugged in over night, on, i wake up in the morning to find it off. This has happened every day so i cant use my phone for an alarm at the moment. Otger than that ive had a few random shut downs during the day. I do want to know what the problem/solution is for the phone shutting off during the night though.
When i flashed over to ji6 i formatted sd odined jf6 then odined ji6. I did try to do tge master clear only to have it start then say FAIL! In a red box. Someone suggested i reinstall my drivers. I do plan on trying that but am getting so sick of flashing and redoing stuff i havent got aroubd to it.
Would a master clear do anything or make a difference you think since i formatted the sd?
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
Click to expand...
Click to collapse
Agree - the extra battery drain and heat buildup in the chip is not worth it... this device works pretty good with stock and/or new FS tweaks applied.
I do hope the OP gets his device recovered with Odin etc.... hopefully just a glitch that can be remedied back to stock....
I've Odin'd it back to stock but currently am running Cognition 2.2. This has been an issue from the getgo, however (maybe I should mention that I SIM unlocked it if that makes a difference). I couldn't return it because I live out of the country and didn't even receive the thing for about 40 days (gotta love Costa Rican customs). I agree that OC seems pretty pointless on this phone and I have avoided OC roms. I only thought it was interesting that running programs doesn't seem to prevent it, but for some reason playing music does seem to prevent the shutdown perhaps meaning that accessing a certain dll or something fixes the issue (I really have no idea why it works). I just thought that info might be helpful to people who understand the OS better than I if it is a consistent problem for people and if no solutions other than "return it" have been found.
Edit: Oh and DG, great work. You'd be one of those smarter than I guys I referenced...
i've never overclocked my phone and i've mostly run it without a lagfix and no matter what ROM i've used (i've been using cognition beta 1 since it came out) i've always had random shut-downs. For a while there on the stock rom it seemed to only happen when my wifi was on but now it doesn't matter. I don't have any special automation software running (task managers, tasker, ..etc). It's the single most maddening thing about this phone.
Same here... i have had my phone since launch... i had random shut downs since launch. I have had less problems now then before and i have flashed every rom that has come out including overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
My wife's phone was never overclocked and it developed the random shut down problem about two weeks after she got it. After trying numerous things to fix the problem, some resulting in it working fine again for a few days and then starting random shut downs again, I came to the conclusion that it was definitely a defective hardware problem and had her return and exchange it. The new one is now set up exactly the same as her old one (rooted stock jf6 with the bloatware removed, side loading enabled, and market fixed) and has been running fine, with no shut downs for over two weeks.
I have been in the electronic repair business for over 25 years, and my conclusion is, the only fix is to return it and get it repaired or replaced. Nothing you can do is going to fix your defective hardware.
I had my phone for a month and it was flawless, updated to 2.2 beta and started getting random shutdowns. I replaced the phone and the new one doesn't shutdown at all on 2.2. The one I returned would shutdown at least 5-6 times per day. Again only after installing 2.2, on 2.1 it seems ok. Which could be a software issue, or just more strain on the hardware making the problem happen
Personally I think it's just bad hardware. Replace the phone.
I guess I'll have to see if there's any way of getting the hardware replaced but I don't think I'm going to be able to manage.
I just want to repeat, however, that I have tested this many many times and with numerous iterations of DG's roms as well as stock. I can guarantee a shut down soon after unplugging the phone in the morning, but I have never gotten it when I start playing music (specifically through Grooveshark - I have not tested it with the regular music player). I just think that even if it's a hardware problem, there appears to be a relationship which suggests that a software solution could prevent it (at least given my experience). I just thought it might be helpful information to people who might understand a possible relationship between the two and to see if anybody else can confirm or refute this behavior. If there is any way to trick the phone into thinking it is playing the music without actually playing it, the problem may go away for people who are experiencing it.
If anybody else can refute my observations or back them up, I would be interested to hear. Perhaps if enough people can confirm it, it may be worthwhile to investigate further. If people can refute it, I guess I'll just count myself "lucky" to have only a mildly faulty phone. Either way I'm happy with my phone. I just thought I might be able to help others out.
I actually convinced four coworkers to pick up Captivates here (our company policy is with at&t) and my boss' phone (completely stock) would randomly shut-down four or five times a day. I've been around the community since the G1 dev launch and my phone is definitely not stock but has never randomly shutdown.
I finally convinced him to return it and his new one came in today. With this many reports, it is not a user-induced problem.
+1 to everything im reading here. i tried a few software and hardware 'fixes' so to say and nothing fixed the issue for long term. sent in for a new captivate #3 yesterday. Im sorry its just got to be a hardware problem, its just to far widespread from what im seeing.
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Believe it or not, this has been working for me for a couple of days now
http://androidforums.com/captivate-...hone-shutting-off-randomly-5.html#post1572891
I called ATT and was told to call Samsung because I don't have an account. They did tell me, however, that they didn't know anything about a bad production run or anything like that or about many exchanges. Of course I take all of that with a grain of salt...
Out of curiosity, to the people that have had the shutdown issue: Did you SIM Unlock your phone? I have and I use a foreign SIM (just trying to see what is in common).
I understand that it seems to be a hardware-based issue, but there really does seem to be a correlation to software as well. If I'm told by Samsung that there was a bad production run, I'll go with it. But until then, I'm the meticulous sort and will continue testing.
I don't want to beat a dead horse though and I don't want to be one of those guys claiming some fanciful fix to something there is no fix for. I'm still doing some testing on my end. So far the music "fix" has worked for me (although I do not see it as a long term solution) and I just wanted to float it because it seems to work consistently (unfortunately you can't prove a negative). I understand, however, that others have claimed fixes that just plain don't work and so if I hear of anybody trying this and it not working for them I'll move along to focus on other possible correlations. Thanks for all the feedback so far!
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
ZoinksS2k said:
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
Click to expand...
Click to collapse
Blaming the 2.2 builds as the sole culprit is false. I have coworker who has two stock captivates. His had never had an issue, his wife is up to phone #2 and has had power issues on both.
Sent from my SAMSUNG-SGH-I897 using XDA App
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
pezx44 said:
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
Click to expand...
Click to collapse
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
bamonkey said:
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Click to expand...
Click to collapse
If you bought a new phone from AT&T, the warranty is 1 year. During this one year, you can have the warranty replacement (refurbs) as many time as you want and your warranty stays as the original (counted from the day you purchased your phone).
If you bought a refurb phone from AT&T, the warranty is 90 days.
bamonkey said:
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
Click to expand...
Click to collapse
If I lived in the states I probably would have pushed for that myself. Unfortunately getting things shipped to/from me where I live costs money plus customs delays so I'm sort of resigned to the fact that I'm stuck with this handset for now. I was hoping I could just bust into an ATT store and get it exchanged but it doesn't look like that's an option. Calling Samsung was more to just document it with them. I'm glad you have had better luck.
3rd you say though? Has it been the same issue with each?
Hey I need some advice I have a HTC One V CDMA 4.0.3 rooted none of the OTA patches through Cricket,
Last 2 months 3 or 4 times a week I dial someone's number from my phone book and it will ring like normal but all of a sudden I will start hearing a lady's voice she will say random stuff then she will pause and like usual I will ask who she is and why she is doing this to me she will start laughing and then state "I know you better than you know your self" she will then pause and wait then start talking about things that have gone on in my house that only me my wife and my children know about... I'm really upset and cricket isn't helping me and I am at the point where I am really concerned.
If anyone has any ideas please share I am at wits end and my computer is down so I can't access anything online except for on my phone.
Thanks
Sent from my HTC One V using Tapatalk 2
When did this start occuring? Was it after you downloaded a specific application? Have you ever left your phone unattended? Since you have a CDMA phone, it is extremely difficult to clone your phone compared to a GSM phone, since you do not have a SIM card in your device. If you can find the suspect app and remove it, it should take care of your problems, however, I would recommend getting a new device since it sounds like your device has already been compromised.
I would contact the authorities immediately. If you're in the US, it's probable the FBI will get involved as that would probably fall under the category of wiretapping, which holds serious federal penalties.
I've never left my phone unattended I always keep it with me even at night I'm disabled and have to be able to get to a phone at all times.
I agree I should get a new handset I was hoping to be able to ride this out until the end of the month.
I've tried contacting local authorities they didn't seem to understand or grasp the concept of what was going on.
As for the app idea I may get try that and see if it does it any more I do have a packet tracer app I might run it and see if it shows any weird activity from certain apps.
If worse comes to worse I'll contact a friend of mine who I went to school with he is a fbi agent and see what he says... I'm a old school hacker of sorts if I had stable wifi and a working pc and could VPN through my pc and run a sniffer the whole time I am sure I would be able to figure this out in a snap.
Thanks for the replies.
Sent from my HTC One V using Tapatalk 2