[Q] Samsung Galaxy S Captivate (AT&T) Wifi - Android Q&A, Help & Troubleshooting

I have a Samsung Galaxy S Captivate (AT&T) that I am trying to refurbish for a friend. I replaced the screen, only to find that more is wrong with it. The power button was jacked up to where it pressed itself randomly, and very frequently. I tried isopropyl alcohol - did not work. I ended up installing AOSP from this thread:
http://forum.xda-developers.com/showthread.php?t=2013285
It made the phone MUCH faster, especially since it was stuck on 2.1 and would not update. It is now on 4.2.1. I used this method to remap the volume up button to act as power and completely disable the power button:
http://forum.xda-developers.com/showthread.php?t=1696526
So now the power button situation is fixed. However, the wifi and bluetooth seem to have decided to quit on me. Wifi worked fine yesterday. The wifi failed even before I flashed the AOSP ROM. So the ROM is not the problem. The wifi switch is grayed out in settings, and it just says "Turning Wi-Fi on..." The bluetooth seems normal but doesn't actually work. It can't find any devices or be found. The bluetooth isn't terribly important. The wifi, however, is. I really need to get the wifi working. I have, of course, tried rebooting several times. Wifi hotspot doesn't work either. I don't see how the hardware can all of a sudden fail... so hopefully this can be fixed with software. If you have any suggestions as to how exactly I can fix it, that would be absolutely wonderful.
Samsung Galaxy S Captivate SGH-i897 AT&T
Android Open Source Project JOP40D (4.2.1) plus Gapps 20130301
Thanks in advance!

Related

Car bluetooth causing phone to crash

I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?

[Q] Wifi won't turn on or connect - HELP

Hello!
Okie, here is a kind of weird problem i am confronted with. About a week ago, i suddenly noticed that my phone is not updating apps and when i checked my wifi, found it turned off. Since then i have tried my best to make it connect with wifi, but of no avail. when i press the wifi toggle, it looks as if its turning on, but it stays there, a dim green line.... Never finds any network and never connects. The IP adress says "Unavailable". What have i tried:-
1. Clean install of different roms including Omega v24, Latest Neat Rom, Kitkat versions, Old 2.3.6 GBs, ICS rom and few others.
2. Clean install of Official GB, ICS and JB firmwares via Odin.
3. Changed different compatible Kernels
4. All kind of wipes including Nuke wipe
5. Opened my cell to the screen level, brushed and cleared all hardware for dust, debris etc.
Now, you can see i have exhausted almost all options here. The cell works all fine, no other anomaly, just this wifi won't turn on. I am not convinced that it could be any hardware issue because my cell didnt fall off, accidented or mishandled since i have get it. in addition during my hardware inspection, i couldn't notice any breakage, leakage etc.
I humbly request my seniors to help me finding a nice solution. Thanks.
If alternative firmware hasn't helped (stock 4.0.3 had a horrible bug with similar behaviour), then it might well be a hardware fault: http://www.stampede-design.com/blog/2012/07/samsung-galaxy-s2-wifi-issue/#.UrbGbpBFCaw
Sent from my Nexus 7 using Tapatalk
Thanx for the response. I has checked the BAT500 thing on my mainboard during self-repair but it looked just fine, no acidic leakage there.
Try to install the latest version of Odin stock ROM. Then the kernel flasha Philz and choose a ROM to your liking
Thanx for input bro, but have tried that already. No luck.
alvinasnow said:
Thanx for input bro, but have tried that already. No luck.
Click to expand...
Click to collapse
I am sorry. Then take it to help center

Samsung galaxy note 2 - 4.4.2 ROM bluetooth does not work well!

4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app

CM13 Bluetooth Stutter

My RAZR worked perfectly with CM12, but ever since I started using CM13, my Bluetooth begins to stutter or will not remember paired devices. I will need to reboot, then my paired device is not present, I need to Repair. I turned OFF Smart Lock (Trust Agent) from Google, this seems to make it worse.
When I do have BT working, it will work for a while ( < 15 min ) then it will start to stutter, and will not reconnect when I turn off BT then back on, I need to reboot.
I tried Clean Flashing numerous times, with no luck, It's definitely a coding error since I tried my phone on numerous BT devices, and it does it every time.
I turned off Smart Lock (Google Trust Agent) since this was always asking to setup every time I pair my device and I thought this was the problem but the problem remains.
My last build was 20160304-Nightly-spyder, (Yesterday's build).
I had the same problem on latest CM13 umts spyder. I was fed up and went back to stock ROM (ICS), which works perfectly not only with bluetooth, but in every other respect as well. It's a much smoother experience to CM13.
EDIT: Oh man. 4.0.4 doesn't support TLS 1.1 or 1.2.
I think I might go back to CM11/12/12.1.
EDIT2: I'm going to try MoKee ROM: http://forum.xda-developers.com/showthread.php?t=2596176
I'll get back to you and see how bluetooth is.
EDIT3: MoKee ROM killed itself (it started doing weird things from the get go, like asking me for my google account during the welcome phase after I had already logged in), and I didn't have enough time to test bluetooth with my cars headunit, which is where your symptoms occur for me, but I was able to test it on my PC's bluetooth dongle, where it showed the exact same symptoms as CM13 did. That is, I would have to reinitiate the pair every single time my phone connected, and not only that, but I would end up in a pairing loop, where as soon as I'd accept the pair, it would ask me again to accept a new pair, ad infinitum. Given this, I'm going to conclude that MoKee ROM's bluetooth is not the answer for our problem. By the way, the next time I booted MoKee ROM it reinitated the updating apps thing at startup, like I had just wiped cache (which I hadn't), and after I let it finish, it never booted properly.
The latest CM13 has an interesting commit: http://review.cyanogenmod.org/#/c/137459/
It might just solve one aspect of our problem so I'm going to test it and come back to you.
EDIT4: Nope. Same problem with headunit and dongle. FYI headunit is Pioneer MVH-X380BT (not old).
EDIT5: I'm on LiquidSmooth KitKat and I've called it a day. Bluetooth works as it should.

NFC does not activate

Hello,
I have just recently rooted my Galaxy S3 (i9300), and now I have noticed that I can't use NFC. When I click on the toggle button in the NFC settings, it just switches from "off" to "activating" like 10 times a second, but it never stays at "on".
I have tested my battery in another (un-rooted) S3 and NFC works fine with that battery, and I have also tested the battery from the other S3 in mine and NFC still did not work.
I tried googling for this issue, but I only found issues related to some custom ROM. I have no custom ROM, I use the standard Samsung ROM, and rooted it by flashing CF-Auto-Root-m0-m0xx-gti9300.zip with Odin. I have installed Xposed with a few mods, but I tried disabling them all and it still does not work.
Unfortunately I have never used NFC in the past (before rooting) so I don't know if it's a software or a hardware issue ...
Does anyone have an idea?
Leseratte10

Categories

Resources