My captivate will no longer vibrate. Haptic intensity is up, vibrate is turned on. I even went to the test using sgs tools. Nothing. I am running Serendipity 6.4. It's been a while since it has vibrated, but I'm just now getting around to asking the fine folks here. Thanks for any info.
Probably a hardware problem, flash to stock and see if it vibrates then.
ok so, noob question. Do I just find a stock ROM and flash it? or is there a different procedure? If it's just a matter of finding a stock OS ROM, where might i find one?
http://forum.xda-developers.com/showthread.php?t=731989
you really should've know that BEFORE you flashed away from stock.
thanks, backing up apps and flashing right meow. will i have to reinstall clockwork and reroot? Any suggestions if I dont get my vibration back? Also, any ROM suggestions? Ive been running serendipity 6.4 for a while now and have enjoyed it, but i want a change.
that will take you back to stock 2.1 like you just turned it on for the first time.
if the vibration doesnt work from there call and ***** to at&t or samsung and get a warranty replacement as that would be a hardware issue.
if you still have the update.zip with clockwork on it rooting isnt needed just have that on the root directory of the /sdcard and 'reinstall packages' twice to install a rom.
as for rom suggestions noone can really tell you as its all based on personal preference.
no vibration. oh well. I'd rather not sit on hold with at&t or samsung
Thanks to the people that helped me. I think it's probably a hardware issue and now I will take it up with AT&T . I really do hate being on hold.
I have the same issue. Did you replace the speaker/vibrator assembly? Thinking about buying one from Mobiletechvideo guy.
Related
Well heres the story. I flashed cyanogen 6.0 and all was great,fast,smooth,perfect... Then it all went downhill. The backlight cut out. After wiping,reflashing,doing everything possible as far as that it was still the same.
I soon figured out that if i lock my phone while it was closed, then slid it open and hit menu the backlight would turn on, but it will not work when its not slid open at all.
Problem #2
As i have been dealing with the first problem and i dont have alot of time to fix it because of work and all, it grew even worse. Now when i do what i was doing to get the backlight to come on, The phone will randomly freeze/backlight wont come on at all/ Screen wont even come on.
When i turn on the phone sometimes the screen wont even come on but the backlight will and it wont get anywhere."blank lit black screen no tmobile g1 logo"
This also happens when i go to recovery using home+power. I remedy that by taking out the battery and starting the phone till it works.
Could someone please help me out here i dont really have to much to spend on a new phone and it would be great if i can get this one going like it should again.
you need to wipe before reinstall
if you have armonR, you wipe everything the wipe menu and flash the rom and the flash gapp-3
ive done that many times, hasnt solved anything. i dont know whats going on..getting to the point where i might just break down and get a htc hd2 and put android on it
Try flashing the Defanged Base (which you can find on the cyanogen wiki) then flash the Rom again.
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
tank65 said:
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
Click to expand...
Click to collapse
You lucky f***! How are you liking it? I was thinking about getting one soon but i havent talked to anyone with one. Is there anything you dont like about it?
Hi, I'm currently running Perception build 9.5 on my captivate and it seems that my phone randomly loses service. I've never had that problem at home or in the city with Eclair and my family doesn't seem to have this issue either so I can only assume that the perception has to do something with it.
When I'm in this state, I try to turn on airplane mode so that I could turn it back off but I can't do that either.
What can I do to fix this phone service error? I miss calls and don't receive texts until I restart my phone!
ijoosong said:
Hi, I'm currently running Perception build 9.5 on my captivate and it seems that my phone randomly loses service. I've never had that problem at home or in the city with Eclair and my family doesn't seem to have this issue either so I can only assume that the perception has to do something with it.
When I'm in this state, I try to turn on airplane mode so that I could turn it back off but I can't do that either.
What can I do to fix this phone service error? I miss calls and don't receive texts until I restart my phone!
Click to expand...
Click to collapse
Airplane mode doesn't work? That's weird, perception is one of those ROM's that has a pretty huge userbase so problems that come out of the woodwork usually get answered pretty fast. I would try flashing back to stock and master clearing, and see if that makes a difference.
If it doesn't, I would try flashing over other modems(modem.bin), to see if you can find one that will give you service. You can do that via ODIN or a prepackaged CWM .zip flashable. Pretty sure Perception 95 comes with JL3. If reflashing/masterclear doesn't work, try some other ones!
Well actually what ends up happening is that it freezes and then as soon as I restart the phone, it restarts as airplane mode. It's pretty annoying. I will try first restoring 2.1 and then whos knows what
geokhentix said:
Airplane mode doesn't work? That's weird, perception is one of those ROM's that has a pretty huge userbase so problems that come out of the woodwork usually get answered pretty fast. I would try flashing back to stock and master clearing, and see if that makes a difference.
If it doesn't, I would try flashing over other modems(modem.bin), to see if you can find one that will give you service. You can do that via ODIN or a prepackaged CWM .zip flashable. Pretty sure Perception 95 comes with JL3. If reflashing/masterclear doesn't work, try some other ones!
Click to expand...
Click to collapse
So I tried to restore my old samsung 2.1 onto my phone but it is stuck at the "DesignGears" Logo at the very beginning. I've tried restarting using the power and volume buttons and restoring again using the same image that I used but to no avail. I've tried to press the factory restore button on clockwork but didn't work either. I can't even get it to load all the way! What can i do?
Not knowing the details of exactly how you flashed your rom, it's hard to say exactly what could be wrong. From the sounds of it, though, something got corrupted in the process.
I had something similar happen the one time I tried to upgrade without taking everything back to JF6. My suggestion is to back up what you can, start over from scratch, and reinstall 9.5.
When you start that process, drop back to JF6 with Odin, then do a Master Clear, and only then install Perception 9.5. Going that route, you shouldn't have any problems.
Ad for your failed 2.1 restore, I'm guessing that you're talking about a nandroid backup? If so, it doesn't back up the kernel or the modem. You'll have to use some other means to get those reinstalled. I'd again suggest using the Odin 1-click to drop the original rom on the phone, then performing the nandroid restore from there.
thanks so much guys!
I did that as you said and used Odin 1-click to restore my phone and have installed 9.5. Hopefully this will conclude the thread. I will let you guys know by tomorrow. I really appreciate both comments and wish you guys happy holidays!
You might be one of the unlucky few like me. Read here, http://forum.xda-developers.com/showthread.php?t=864903
bobbylx said:
You might be one of the unlucky few like me. Read here, http://forum.xda-developers.com/showthread.php?t=864903
Click to expand...
Click to collapse
Actually, yea. Nothing has changed. My phone still loses signal every hour or so probably because of the switches. I wonder if we can contact a dev about somethin like this?
ijoosong said:
Actually, yea. Nothing has changed. My phone still loses signal every hour or so probably because of the switches. I wonder if we can contact a dev about somethin like this?
Click to expand...
Click to collapse
Most of the Devs that use i9000 or Vibrant ROMs for their base are aware of the problem. At this point seems there is nothing we can do though. I keep flashing things like Perception and Phoenix thinking one day it will work, but it never does. The only stable build for signal are Captivate based, ie, stock or Cognition.
So I have the random button press issue pop up occasionally. I noticed though that it only happens with some roms. Specifically, Serendipity 6.4. It does not happen with stock 2.1, Cognition 4.3 or any of the GB 2.3.3 roms, but it affects the one rom I want to use, Serendipity 6.4. I have however found a way to get around it on my phone, and use Serendipity without the issue.
Everything I have seen regarding this calls it a hardware issue, which it most likely is, but I have been able to get around it. So perhaps there is something to be done with the software?
I have been able to get around it by flashing stock, them Cognition 4.3, then Serendipity 6.4. This actually really does fix it for me. I tried Cognition 4.5.1 and it does not work, same problem as flashing straight Serendipity.
Anyone have any ideas past "It is hardware get a new phone." I do not really need a new one seeing as I can get it functional. I try not to waste things, especially expensive hardware.
Just thought I would throw my experience out there. Perhaps something can be done about it.
My phone is batch 1009
EDIT: While this worked for me a number of times before, it does not seem to be working anymore. Probably should just get a new phone I suppose.
EDIT AGAIN: Actually scratch that. Went back to Serendipity VII and the button issue is gone, just as before. Seems I am having issues with 2.1-2.2 roms for whatever reason.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
OK so I haven't been on here or done anything to my phone in a couple months. I had andromeda 3 the whole time i haven't been flashing. I come back and immediately go back to stock and flash symply gs2 then I flash Mosaic and then I flash apex. I was just using all the roms for a short while and seeing which one was better. I disabled lagfix each time I flashed one over the other. I wasn't liking any of them too much so I wanted to back to a custom 2.2 rom. So I flash back to stock using one click. Everything looks like its going fine until odin stops. It just freezes and I believe it stopped around where it says something about "factory.rfs". Now from there I know I'm screwed. I leave it there for about 25 minutes to hope that it continues but when it doesn't I remove it. Then my phone has a red list of sentences with numbers and letters appearing. About 4 or 5 lines of them. After I try removing the battery and trying to turn the phone back on it has the same red lines of letters. Then I do it again and my phone won't even turn on. So what am I looking at here? I don't have a jig so I haven't tried that method yet. I was going to try that one click unbrick but I don't think it will work. I came back to xda and was really just rushing with everything and didn't really care for what I was doing. So was I doing everything right? or was I supposed to use something else to go back to stock from 2.3.4?
Much help appreciated!
Edit: Idk if I mentioned this but I think I may have forgotten to disable lagfix while going back to stock.
A JIG may pull you out of this but if it does not you will need JTAG. PM if it comes to that as I can fix it for you via JTAG very quickly...
Lol I actually just fixed it. Thank you for offering the help though. If a mod wants to close this or something feel free to do so.