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:
Hi everyone,
I have been having a very annoying problem with my Galaxy Nexus during the past few days. When it enters to sleep mode (after 15 seconds without activity or when I push the power button) it wakes up itself again after 2 to 10 seconds and does not stay into sleep mode: the lock screen is displayed during 15 seconds before a new sleep mode/'wake up state' loop starts again.
It doesn't happen all the time but it does often enough to waste around 8% of battery every hour without me touching my phone.
I searched the forum for solutions and found in other threads that an application could be the source of the problem. I uninstalled every apps but the problem remained. I did a factory reset without installing any app or update after but the problem also remained. I also tried using only Wi-Fi or only 3G for data or switching to flight mode, but it didn't change anything.
Other solutions suggested on other threads, to disable GPS. It did it too, without more success.
I noticed that the problem only occurs when the phone is unplugged. It never happens during loading.
Have you any ideas that could help me to solve the problem?
Thanks a lot in advance,
Julien
Don't know if it helps but I made some screenshoot of BetterBattery Stats results.
Galaxy Nexus - The 'Waking Up' Problem
I love my Galaxy Nexus (I would like to thank Google for giving them away during the I/O 2012). Jelly Bean (the last version of Android) is simply a blast: it is smoother, snappier, sexier, you name it.
As much as I love JB, I still need to play with my devices, and what a better way to play with an Android phone than to root it. After testing a few ROMs, I ended up using Codename Android in combination with Lean Kernel. I advise you guys to have a look at it, it packages an insane number of customization and parameters that will make your phone even better!
The drawback when you hack around with your phone, is that your start feeling guilty when it starts doing random stuff, such as waking up randomly : I would put it in sleep mode (using the power button), and a few seconds (minutes if I happened to be lucky), the phone would wake up on its own, sometimes indicating it was charging when obviously no cable was plugged…
From there started the usual bug chase that many of us know: backup, factory reset, and a complete reinstallation. Unfortunately, in that particular case it would not change a thing and the problem was occuring even more often. It was becoming obvious that my problem came from the hardware…
The usb connector at the bottom of the Galaxy Nexus has a bad habit of bending downward after some time (it varies, depending of your usage). The solution is thus to take a small knife and pushing it upward so it does not touch the bottom metallic plate. Et voila! Your phone will stop waking up by itself, and your frustration will go away with it.
I guess if a lesson can be learned from that experience, it is that the obvious answer is not often the right one; you should also keep a small knife not too far from your Galaxy Nexus.
It´s work fine to me...
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.
Hi guys
I got an HTC M8s less than 2 months now and it has so many issues it's driving me insane at this stage....
It's on stock ROM unrooted with all the latest updates.
First issue that came up was not recognising the headphones after i plugged them in, that eventually went away after lots of searching and fiddling with settings etc.
Then it started going into Car mode while it was resting on the table, no input on my end no triggers set for it, hell i don't even own a car to use this function....
I disabled HTC car and that stopped.
The included micro usb cable somehow went bad, tried it on other devices, it will not charge....
Now i'm having some weird charging behaviour, it drops out of charging and resumes or sometimes it just stops charging (that doesn't happen when the phone is charging while being switched off, so i'm guessing it's not a hardware issue)
Another massive problem is that all incoming/outgoing calls go to the speaker which almost burst my ear drum first time that happened.
I have looked in every single forum out there and have tried all possible solutions, ranging from disabling google Chrome to trying every available speaker management/toggle related program on the play store but nothing seems to be working.
Some times if i plug in the headphones, make a call and then unplug them, then it works as it should for a little while. But later on it reverts to the previous mentioned behaviour.
One thing i have noticed, before it routes calls to the speaker, the screen will light up, no notifications come up and then all calls go to the speaker.
I used Wakelock to try and find out which program triggers the screen wake in order to remove it and maybe solve this issue but nothing came up.
Any input would be greatly appreciated as i am at the end of my rope with this device....
I still have my HTC DHD A9191 and i never had any issues with that phone, i'm very dissappointed with HTC :/
Thanks in advance
Yanni
Less then 2 months......return it ! Not even sure what you want to achieve here besides messing up warranty ?
I am using Spign slim armor case on m8s and after using it my power button isn't working.
and I have a Motion Launch problem when phone is on my pocket it opens camera, calls someone because of the sensor.Any fix about that?
Kyaner said:
Hi guys
I got an HTC M8s less than 2 months now and it has so many issues it's driving me insane at this stage....
It's on stock ROM unrooted with all the latest updates.
First issue that came up was not recognising the headphones after i plugged them in, that eventually went away after lots of searching and fiddling with settings etc.
Then it started going into Car mode while it was resting on the table, no input on my end no triggers set for it, hell i don't even own a car to use this function....
I disabled HTC car and that stopped.
The included micro usb cable somehow went bad, tried it on other devices, it will not charge....
Now i'm having some weird charging behaviour, it drops out of charging and resumes or sometimes it just stops charging (that doesn't happen when the phone is charging while being switched off, so i'm guessing it's not a hardware issue)
Another massive problem is that all incoming/outgoing calls go to the speaker which almost burst my ear drum first time that happened.
I have looked in every single forum out there and have tried all possible solutions, ranging from disabling google Chrome to trying every available speaker management/toggle related program on the play store but nothing seems to be working.
Some times if i plug in the headphones, make a call and then unplug them, then it works as it should for a little while. But later on it reverts to the previous mentioned behaviour.
One thing i have noticed, before it routes calls to the speaker, the screen will light up, no notifications come up and then all calls go to the speaker.
I used Wakelock to try and find out which program triggers the screen wake in order to remove it and maybe solve this issue but nothing came up.
Any input would be greatly appreciated as i am at the end of my rope with this device....
I still have my HTC DHD A9191 and i never had any issues with that phone, i'm very dissappointed with HTC :/
Thanks in advance
Yanni
Click to expand...
Click to collapse
ok man
look i have htc one m8 + one m7+one max
the one m7 had the same problem of u
i will give to you one solution for try
i try it on the one m7 and its work
but on one max not work
on m8 not test yet
try this:
1. Turn phone OFF
2. Let charge for AT LEAST 10mins even if it doesn't look like it's charging.
3. Press and hold POWER + VOL UP + VOL DOWN for AT LEAST 2mins. Anything less will not reset the charge mode.
4. After 2mins release the buttons and the phone should boot as normal
if it not charge at the first time then try it again andd u will be OK
Hi Hazem
Thanks for the input, i'll give this a go when i get back home and let you know if it works out.
Should i try this when the phone is at 4-5% ? And then let it charge all the way ?
I'm experiencing these same issues as well after rooting my M8. Hopefully someone here knows what the issue is.
Well for me all issues remain unresolved.
My guess so far for the culprit seems to be the magnetic sensor, either badly programmed or a factory defect.
Kyaner said:
Well for me all issues remain unresolved.
My guess so far for the culprit seems to be the magnetic sensor, either badly programmed or a factory defect.
Click to expand...
Click to collapse
u must charge ur phone
turn off the phone
let him charge to full about 3 hours
and try the method
it will work
i test it on 2 one m7 phones
let me know if that work
thx
Sorry Hazeem I understand that English isn't your first language, and you are trying to help but you are not making much sence....
You are basically telling me to charge my phone, then switch it off and charge it again even though it's already charged for another 3 hours....
Ok an update !
HTC Released a service pack along with an update for the car application, after installing these and a couple of reboots the charging problems stopped and the phone doesn't seem to be waking up without any reason, as it did before.
The calls getting routed to the speaker still remain but thanks to an app called Auto Speaker, I've managed to work around this issue. Before the updates this application had no effect, but now it works as it should by turning off the speaker when the proximity sensor is blocked.
I hope I am not celebrating too soon on this and I'll keep this post updated if anything else, related to these issues, happens.
Update 2
So far so good and with another unexpected benefit, I removed my phone from the charger Saturday morning around 11 and as of now Monday 7:30 it's at 27% !
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.