Related
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
TomSilverSpring said:
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
Click to expand...
Click to collapse
Are you using an experimental ROM or stock rooted?
Jedi Mind Trick XI (although the problem has been growing worse and has happened across the last several JMT versions). I will give a stock rooted ICS a try.
I just tried a stock rom and the problem persisted.
I have the same problem
I have scoured the net looking for an answer, any answer, to this problem. It seems that a few people are having the same issue. But before it is ever answered, some dip$#!t always jumps in and says "I have the same problem, my phone won't connect to my car." Then the conversation goes off into other people that can't connect their bluetooth to their car or their headset- or their cat... That is not the same problem!!!
I cannot turn my bluetooth on unless I soft reset the phone. Even after I've gotten the bluetooth working, if I restart my phone the bluetooth turns off and when you try to turn it on, it says "Turning on Bluetooth..." It cycles for about a minute and a half and then goes back to "To see devices, turn on Bluetooth."
I bought this phone on Amazon for what appeared (at the time) to be a reasonable price. Since then, I believe that I have read at least one of the seller's post about bluetooth not coming on (no proof, just an educated guess). The seller probably got rid of the phone because noone could or would give an answer to this problem. Heck, it's possible that every post that I've read so far is by someone who owned this phone at one point or another. :silly:
I am sending this post to XDA because even the adminstrators on android forums say that you guys are the smartest and most responsive forum available. (Okay, they didn't say smartest- it was implied). Please help me resolve this issue.
I rooted this phone the moment that I pulled it out of the box. In other words, I don't know if the bluetooth issue is caused by the root, or if the previous owner didn't root the phone and also couldn't get the bluetooth to work. I believe that, because the phone is rooted, I should be able to remove and reinstall the app that bluetooth is based upon.
I am not a techie, the only reason I know anything about root is because I was complaining to someone about my old phone and how all of the bloatware that seems to constantly run eventually kills my battery. He told me about rooting, and it was easy enough - the rest is history. In other words, if you ask me for more information- I promise that I can give it to you. Yet, have patience with me if I ask you a question that you believe that any person that has rooted their phone should know.
I really hope that you guys can help me without bricking my phone. I truly appreciate any suggestions or thoughts on this matter.
jzxpw6;34880517I cannot turn my bluetooth on unless I soft reset the phone. [/QUOTE said:
I may have figured out what is going on, although I can't understand why it is (maybe someone more versed with processes can help me figure this out).
Using Titanium Backup, I first froze the two bluetooth items (Bluetooth Share and Bluetooth Test). Of course, that didn't remove anything, but I wanted to make sure that I could. Then I wanted to see how Bluetooth Share would react without Bluetooth Test. I unfroze Bluetooth Share.
I was then able to turn on and off Bluetooth fine. I restarted the phone and Bluetooth came in just like it did on my old phone. I guess I want to know:
1) Is the Bluetooth Test the cause of my problem?
2) Why is it there?
3) If I uninstalled it, would I experience a major hiccup?
There is still the possibility that this was simply a fluke, and very soon I will go back to the old bluetooth soft reset problem.
There is, however, one distinct difference between this phone and the last and may be the "drop out" that everyone else seems to be having. I have a Chevy Malibu with bluetooth in the stereo. On my old phone, when I started the car and got going, the word "Bluetooth" would appear on the digital display for about 10 seconds, which means that the vehicle detected and connected the bluetooth pairing. Yesterday, as I was driving in the car, every 5 minutes or so, "Bluetooth" would appear on the digital display.
This leads me to the conclusion that Bluetooth is dropping out and being picked up continuously by my vehicle. Does anyone have any thoughts on this? I'm okay with that as long as when I am talking to someone for more than 5 minutes I don't have to keep calling them back. I simply want to know what you guys think about this issue.
Click to expand...
Click to collapse
I am beginning to think that the problems I have had are related to the condition of the battery contacts.I have several third party batteries with contacts that are somewhat damaged from the pins on an external charger that came with them. I seem to experience a variety of problems when I try to use them.my original factory battery seems to work most of the time. I have several new Samsung batteries on order and will post again if they seem to solve the problem.
Sent from my SGH-T989 using Tapatalk 2
i had the same problem and it started with JMT so I switched roms countless times and the problem kept coming back. It would work for a little bit but when i turned it off it would not turn back on. I decided to go back to stock to see if the problem was still there and it was gone. Since then I have rerooted and once again flashing diff. rom every other day and bluetooth works just fine.
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
enveous said:
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
aaronchili said:
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Click to expand...
Click to collapse
Hey thanks! I switched to JMT JB4 and it's not happening (much) now, I'll try to flash it and see if it fixes something :good:
I grabbed my brother's S II X because he was tired of it (phone having some issues that I didnt get so far, but he's not the most responsible phone user out there). Screen is cracked (not a huge crack, touch works 100%), bezel in poor condition, but otherwise works great.
Except for the Wi-Fi, which most of the time I cannot get working for some reason. It just stays off, or if I go in the Wifi menu and turn it on there, it shows "Turning On...", then stays there. Sometimes it starts working for absolutely no reason, sometimes it works from a cold boot, sometimes it works after enabling data/4G and messing with other stuff. I can't replicate the fixes. And it will also "disable" itself automatically for no reason after a while (could be minutes, could be hours).
A quick search made me realize this was a recurring issue with a few phones, not only the T989, but the fixes are missing.
It was doing this on stock 4.0.3, now I flashed AOKP's latest nightly (2013-02-22) and the issue is still there. I havent touched the kernel at all, other than dumping AOKP in there (if it includes a custom kernel then I guess I did, but otherwise I havent flashed anything else other than AOKP).
Anybody knows what is going on, or a tip to figure it out? Its rather annoying not being able to use Wi-Fi, especially since I was hoping I could change carriers to drop my plan prices by half by losing unused data.
I have a Canadian/Telus T989D, using the TLLE4 radio. I will try the TLLG2 (Koodo) radio and see if the issue is still there, but Id like to have a few ideas to try out since Im not really used to the inner workings of an Android phone.
Up, I really need tips on how to try and fix the issue. The phone is barely usable, the USB won't connect to the computer 19/20 times, Wi-Fi doesn't really work, and BT doesn't even turn on. I needed to remove the SD card from my old phone to put in this one and manually transfer pictures I took for job, to put them in the computer...
I flashed TLLG2 radio (Koodo) and Wi-Fi worked immediately after, but again stopped working shortly after. EDIT: BT doesn't seem to work on TLLG2, now that Im back on TLLE4 it works, but WiFi still doesn't work
I've searched and searched... Tried and tried with no success. wifi bluetooth hotspot and mhl will not enable. I bought a used s4 m919 and everything was fine. Updated to 4.4.4 and started having all these problems. flashed back to 4.4.2 and everything started working again... 30 mins later started having the same issues. took phone apart and 'cleaned' antennas... reconnected all ribbon connectors... cf rooted and deleted wpa_supplicant. factory reset, wipe cache, removed battery, entered safe mode... don't know what else to try. tried to rollback to 4.3 but odin authen failed. anyone ever find a solution for this? is this hardware or software issues?
I have tried a lot of "fixes" for this problem... none worked
I have tried all the "fixes" you have listed and none worked for me either. I also noticed that when the WiFi and Bluetooth quit working the IR functionality also stops working. I will have to try the MHL functions to see if that is affected on my device as well.
What I found out... is mine is related to a hardware issue and is defiantly related to CPU/device temperature, and not firmware/software issues.
you can monitor the device's temperature and a lot of other good information about your phone by downloading the Phone INFO*Samsung* app from vndnguyen in the google play store.
This may sound odd, but here is something to try:
Turn the phone off, and stick it in the refrigerator for about 10 minutes, just long enough to get your phones internal temperature down to about 18 degrees C. then remove the phone from the fridge, turn it on and check to see if the WiFI, Bluetooth, etc. works. If they are working, keep tabs on the devices temperature to see when the functionality quits working, you may be experiencing the same problem that I am having with my phone.
Regardless of ROM, or baseband, modem, or non-hlos file used, this method has worked for me every time. It is only temporary, once the device warms up past 28 degrees C... the WiFi, Bluetooth and IR functionality all stop working. But it did help me answer the question to what was truly the cause of the phone's problem. And yes... 28 degrees C is right about room temperature, way too low for a protection circuit activation to be shutting down device capabilities to protect itself.
I can repair the phone myself, I'm just not convinced that $90 USD for a used SGH-M919 motherboard is a good deal when I can get a complete used SGH-M919 phone for $150 USD.
Hello,
I have spent many hours attempting to solve the ongoing problem of the wifi button not responding but remaining gray when touched. Here is a quick chronology of symptoms and attempted fixes. I love everything else about the phone, especially the size, but am close to throwing my hands into the air. If anyone has any suggestions as to a Rom that may finally fix this, please let me know!
Wifi worked fine on phone for about 6 months, then became unreliable, not connecting after being out of range and coming back into range of wifi stations. I was usually able to force it to come on by a reset, pulling battery, turning off mobile data and calling *#0011# and turning wifi power saver off and on several times.
After this would no longer work, I rooted phone with CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 , was able to use wifi for a day or two, then nothing would force it on.
Tried multiple custom roms, including CM11 kitkat and CM12 Lollipop, same results, I would originally get wifi to fire up and connect, but after a day or two max, nothing.
Have flashed stock kernel for modem, nothing.
Took back of phone off, unplugged and plugged in blue antenna wire, nothing.
Recently flashed M919UVUFNH7_STOCK_ROOTED_DEODEX_KNOXLESS along with NH7_modem.tar.md5, wifi worked a little while, and as usual, wont respond to any resets, battery pulls, etc.
Thanks for any help you may be able to afford.
ive been having the same issue or a month or so now... cant seem to find a sulution anywhere. I too tried multiple roms, even the new 6.0 . I cant imigine its the wifi antennae because it works fine when it wants to... gettin frustrated with it.
MorrisonMike said:
Hello,
I have spent many hours attempting to solve the ongoing problem of the wifi button not responding but remaining gray when touched. Here is a quick chronology of symptoms and attempted fixes. I love everything else about the phone, especially the size, but am close to throwing my hands into the air. If anyone has any suggestions as to a Rom that may finally fix this, please let me know!
Wifi worked fine on phone for about 6 months, then became unreliable, not connecting after being out of range and coming back into range of wifi stations. I was usually able to force it to come on by a reset, pulling battery, turning off mobile data and calling *#0011# and turning wifi power saver off and on several times.
After this would no longer work, I rooted phone with CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 , was able to use wifi for a day or two, then nothing would force it on.
Tried multiple custom roms, including CM11 kitkat and CM12 Lollipop, same results, I would originally get wifi to fire up and connect, but after a day or two max, nothing.
Have flashed stock kernel for modem, nothing.
Took back of phone off, unplugged and plugged in blue antenna wire, nothing.
Recently flashed M919UVUFNH7_STOCK_ROOTED_DEODEX_KNOXLESS along with NH7_modem.tar.md5, wifi worked a little while, and as usual, wont respond to any resets, battery pulls, etc.
Thanks for any help you may be able to afford.
Click to expand...
Click to collapse
Need more info....did you try to just Odin the official firmware yet?
MorrisonMike said:
Hello,
I have spent many hours attempting to solve the ongoing problem of the wifi button not responding but remaining gray when touched. Here is a quick chronology of symptoms and attempted fixes. I love everything else about the phone, especially the size, but am close to throwing my hands into the air. If anyone has any suggestions as to a Rom that may finally fix this, please let me know!
Wifi worked fine on phone for about 6 months, then became unreliable, not connecting after being out of range and coming back into range of wifi stations. I was usually able to force it to come on by a reset, pulling battery, turning off mobile data and calling *#0011# and turning wifi power saver off and on several times.
After this would no longer work, I rooted phone with CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 , was able to use wifi for a day or two, then nothing would force it on.
Tried multiple custom roms, including CM11 kitkat and CM12 Lollipop, same results, I would originally get wifi to fire up and connect, but after a day or two max, nothing.
Have flashed stock kernel for modem, nothing.
Took back of phone off, unplugged and plugged in blue antenna wire, nothing.
Recently flashed M919UVUFNH7_STOCK_ROOTED_DEODEX_KNOXLESS along with NH7_modem.tar.md5, wifi worked a little while, and as usual, wont respond to any resets, battery pulls, etc.
Thanks for any help you may be able to afford.
Click to expand...
Click to collapse
I agree, flashing stock firmware is one of the first things that should be done in this case
Blasito777 said:
ive been having the same issue or a month or so now... cant seem to find a sulution anywhere. I too tried multiple roms, even the new 6.0 . I cant imigine its the wifi antennae because it works fine when it wants to... gettin frustrated with it.
Click to expand...
Click to collapse
Sent from my SM-G920T using Tapatalk
MorrisonMike said:
Hello,
I have spent many hours attempting to solve the ongoing problem of the wifi button not responding but remaining gray when touched. Here is a quick chronology of symptoms and attempted fixes. I love everything else about the phone, especially the size, but am close to throwing my hands into the air. If anyone has any suggestions as to a Rom that may finally fix this, please let me know!
Wifi worked fine on phone for about 6 months, then became unreliable, not connecting after being out of range and coming back into range of wifi stations. I was usually able to force it to come on by a reset, pulling battery, turning off mobile data and calling *#0011# and turning wifi power saver off and on several times.
After this would no longer work, I rooted phone with CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 , was able to use wifi for a day or two, then nothing would force it on.
Tried multiple custom roms, including CM11 kitkat and CM12 Lollipop, same results, I would originally get wifi to fire up and connect, but after a day or two max, nothing.
Have flashed stock kernel for modem, nothing.
Took back of phone off, unplugged and plugged in blue antenna wire, nothing.
Recently flashed M919UVUFNH7_STOCK_ROOTED_DEODEX_KNOXLESS along with NH7_modem.tar.md5, wifi worked a little while, and as usual, wont respond to any resets, battery pulls, etc.
Thanks for any help you may be able to afford.
Click to expand...
Click to collapse
I have a suggestion. Use the following link to get latest T Mobile firmware for the phone.
http://forum.xda-developers.com/showthread.php?t=
Sometimes it takes flashing the firmware twice for the full install of the radio to take properly.
To begin, remove the back of the phone, because your going to remove the battery after the first flash.
Boot into download mode by holding the volume down and power.
Assuming you know how to use Odin, before starting the first flash, unchecked the auto reboot option.
After Odin has reached the point of RESET, unplug the cable, remove the battery... Replace the battery, reboot into Download mode and
repeat the process, leaving auto reboot checked this time.
You are now completely stock. Your data will be basically left untouched.
Good luck.
Sent from my SM-T320 using XDA Premium HD app
Have you tried cleaning the hardware contacts on the antenna? I remember this same scenario on my old HTC Desire... the antenna contacts were dirty IIRC and they needed cleaning.
Wow, so I am not the only one still facing this issue! I flashed this rom http://forum.xda-developers.com/showthread.php?t=2539361 a few times and I eventually noticed the wifi issue as well.
Baseband: M919UVUF0H3
Kernel version: 3.4.0-2437203 [email protected] #1
Build number: KTU84P.M919UVUF0H3
Here's what I attempted:
1. Did a full wipe on the phone and installed full firmware 4.4.4 http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835
2. Flashed stock kernel from the same link above
3. Installed SuperSU, flashed TWRP
4. Installed and ran TriangleAway to clear KNOX counter
Same issue as OP--at first wifi would work but the connection would not stick and I was unable to activate the wifi button anymore. I tried uninstalling KNOX but I get an error "Failed to create KNOX mode." When I reboot into TWRP, I get the message "E: failed to mount /efs (invalid argument)."
I discovered that my EFS folder is empty. I don't have a backup. Could this be related to the wifi issue? Am I screwed?
Finally got the wifi working. Took the white shell that covers the board off and cleaned the contact on the shell with a q-tip and isopropyl, but it looked kinda scuzzy so I scratched it a bit to expose bare metal again. Then I went to the board side and pulled up on the tiny piece of metal that springs to make contact, enough to bend it to a steeper angle for better contact. Wifi and BT working steady for over an hour now. Thought id share.
http://blog.brokenlcds.com/samsung-galaxy-s4-bluetooth-and-wi-fi-problem/
Heres a link with pics of the locations of the antennas
Edit:
though the wifi worked briefly after this, it stopped working shortly afterwards... back to square one...
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.