I am sure I saw somebody else mention this but can't find the thread.
Every now and then (once every few days) I notice that Bluetooth has turned itself off. I can't see any reason for it doing so and I do not believe it is due to power management so has anybody else spotted this?
I am wondering if there is an undocumented key press combination or something that is getting pressed by accident but I can't work it out.
I have same problem. Anybody can help me???
I can reconnect bluetooth only to re-boot S740.
i'm having problems with bleutooth.
When i set bleutooth on, i have always go to settings and then to choose for: bleutooth seeing for other device's.
is there any other way ??
Related
After an upgrade to dcd latest ROM 2.2.6 and Radio I have found that when my phone sleeps or I turn it off it doesn’t always turn back on I need to soft reset it. I am even tried an earlier Rom version 2.2.1 and still the problem.
This is a Telecom New Zealand phone and as for normal practice they don't give out their Rom's so I can't just flash back
With some playing I think I have tracked it down to only causing this issue when my data push is enabled ie, don't sync up to an exchange server and the phone works fine.
I am aware from other posts there are others out there with the same issue, can you check if this is the same with your phone. Turn off all your data connections and delete your exchange server and see if you phone then behaves.
I know people are saying it could be the Bootloader but if the above is the cause then I don't think it is in the loader and maybe dcd can help us track it.
I have tracked this problem down to when activesync does a Microsoft Direct puch while the phone is in standby. To connect to our work's mail server we need to also create a VPN connection (not using SSL) as long as I put in a wrong name or password causing activesync never to be able to sync then the power button turns the phone on everytime. If I also connect and sync (while phone is on) then dissconnet my VPN and and change password then the phone still works fine.
Does anyone has any idea where I should be looking, as I would like to have my Direct push email working.
Sorry to jack your thread, but I have a very similar problem. Sometimes when my phone goes on standby when I'm on the phone and my conversation is finished. I cant power back on my phone either. The green light still flashes, but the power button does nothing! Anyone have that same problem?
I've also had this problem. When I press the power button the phone would enter standby mode and when I pressed it again it wouldn't wake up. The only way around it I found for my phone is to install S2U2 and set it so it activates when the backlight turns off. That seems to catch it before it whatever happens to not let the phone wake up happens. So now when I press the power button, the screen cuts off and S2U2 opens. Hope this helps.
I have similar problems. Maybe I'll try using S2U2 ...
Same problems, doesn't seem to wake up if it goes to sleep while VPN is running... any fix?
I had the same issue when I flashed my ROM with the USB connection. It could be the bootloader. because I then used the SD card bootloader and re-loaded my ROM from the SD card and it resolved the issue.
I would recommend reinstalling from the SD card using the no2chem.
Since two days I got the problem, that I can not activate Bluetooth anymore. On the settings "Wireless & network setting" I press the Bluetooth activation (Turn on Bluethooth). The status changes to "Turning on ... " for about 10 seconds, but doesn't turn on. Before was working fine, I do not remember to have something deleted.
It seems to me, as if Bluetooth is switched off (or disabled) by some application.
Would like to isolate the problem. Any ideas how I can find out.
- Log file
- command line
- etc
1.ATRIX-in-PT said:
Since two days I got the problem, that I can not activate Bluetooth anymore. On the settings "Wireless & network setting" I press the Bluetooth activation (Turn on Bluethooth). The status changes to "Turning on ... " for about 10 seconds, but doesn't turn on. Before was working fine, I do not remember to have something deleted.
It seems to me, as if Bluetooth is switched off (or disabled) by some application.
Would like to isolate the problem. Any ideas how I can find out.
- Log file
- command line
- etc
Click to expand...
Click to collapse
Do you have anything frozen through titanium backup? Have you installed any apps that use Bluetooth? I had an issue with car home locking my Bluetooth up when I undocked it. Telling Car home to turnoff Bluetooth once disconnected fixed mine. If all else fails and you cant figure it out, I would try flashing back to 1.57 and then OTA update it back to 1.83. Last resort of course so you don't have to set your phone back up, titanium backup can make this process easier.
If nothing works then may be a hardware issue. Best of luck.
Just wait before you get into it, another person may have better advice!
Dirtburgler said:
Do you have anything frozen through titanium backup? Have you installed any apps that use Bluetooth? I had an issue with car home locking my Bluetooth up when I undocked it. Telling Car home to turnoff Bluetooth once disconnected fixed mine. If all else fails and you cant figure it out, I would try flashing back to 1.57 and then OTA update it back to 1.83. Last resort of course so you don't have to set your phone back up, titanium backup can make this process easier.
If nothing works then may be a hardware issue. Best of luck.
Just wait before you get into it, another person may have better advice!
Click to expand...
Click to collapse
Hi. I installed a Bluetooth Transfer app. This was the reason, why I found out that Bluetooth wasn't working anymore. But I know for sure that Bluethooth was running fine, just a few days ago.
I really would like to find the reason, quite sure there is a software reason, and defenitly do not want to flash back.
I've done a quick search of this forum and [ALARMINGLY] can't find a solution (or any references) to a continualy cycling reboot on my daughter's day-old Sony Tablet S.
What's happening is, the system boots, I see the unlock screen for a few seonds and then it reboots again!! No time to do anything.
The power button (in combination with either of the volume buttons) doesn't do anything when the boot animation is being displayed. And the reset button (in the tiny hole) simply turns the tablet off, but the cycling reboots start again when powered back on.
Just so you know, I have owned and used the Morotola Xoom since August 2011, so do have some experience with Android Honeycomb, but nothing like this. Oh, and I have not attempted to root either machine.
Here's what I believe is the cause: I was copying a file off a network share (using a third party file manager), but it was VERY slow. The transfer mustn't've finished when I turned the tablet off (completely) for the night.
Therefore, I assume it is trying to resume the transfer, but there is a problem (possibly the WiFi connection is slow to connect). Nevertheless, I would have thought Andorid was more robust than to simply reboot... an error message would be a bit more "professional" and much more welcome than a cycling reboot that does not allow me to do a F%^&$#G thing about it!!
PLEASE HELP or point me to a forum that may be able to.
Thanks in advance.
Wow. That tablet is toast. Something must have been corrupted when you turned it off.
My girlfriend had an HTC Sensation 4G that had similar problems the day she bought it. HTC and our cell provider gave us the run around denying responsibility. We rooted it and flashed a new ROM which completely fixed it though. In your case for the Tablet S this solution is impossible as the tablet hasn't been rooted yet.
Return it to the store asap and tell them it's not working properly!
Have you tried the reset button on the side underneath the volume button. Just stick a pin in thhere and hopefully voila.
Let us know if that works.
Sent from my Sony Tablet S using Tapatalk
Cycling reboot - FIXED!
mightyfo said:
Have you tried the reset button on the side underneath the volume button. Just stick a pin in thhere and hopefully voila.
Click to expand...
Click to collapse
motoscoddie said:
And the reset button (in the tiny hole) simply turns the tablet off, but the cycling reboots start again when powered back on.
Click to expand...
Click to collapse
Yeah, mightyfo, I did. Thanks for your reply, though.
Anyway, I have attempted a few more "fixes". Among them was to delete the partial/currupted files from the SD card, without result. Then, for some reason, I turned off my WiFi access point, and, bugger me, the tablet booted! I turned the WiFi back on to be certain it was responsible for the problem and, yes, the reboot cycling started again.
Obviously, I turned off the WAP again, booted the tablet and killed the saved connection. Once I turned the WAP back on, I re-established the connection and the tablet has behaved ever since!
Just so you know, I did have the latest System update (v3.2.x) when all this was going on...
Makes me wonder if it is an Andorid issue, or something Sony have done while tinkering with Andorid. I just hope my findings can help someone else in the future.
Sounds like you need to do a system reboot.
Comprehensive explanation of the problem
Please take a look at the following very thorough explanation of the underlying cause of the reboot problem:
[Can't post links] Search for "android stops renewing lease" in Google and select the Princeton link (should be top of list).
My fix was to turn off the WiFi AP (to stop the reboots), delete ("forget") the connection and then set a static IP outside my DHCP range.
Hope this helps someone else...
When i got this device i thought how stupid this was and hoped after flashing a custom rom maybe it would eliminate this stupid feature of this device. It seems HTC thinks it's a good idea to turn the screen ON after ending a phone call, WTF?
At work i use my bluetooth headset all day with my phone in my pocket. I will take my phone out, dial the number i want to speak to, press power to turn screen off, put device in pocket and have my conversation. I end the phone conversation with my bluetooth headset and guess what? The dang phone's screen turns on while it is in my pocket. I guess the light sensor has zero effect here! So now since this happens and my device has a timeout of 2min i set before screen turns off my phone accidentally "butt dials" people and without me knowing i'm now calling people randomly while i'm working!
Another case. I have my phone in my car's cupholder, i use bluetooth to make a call with my car, it initiates the call to my phone and again it turns the screen ON to make the call. WHY? I never pressed power on my device to turn the screen on to make a call. So again i press the power button to turn screen off while in call. I hang up the call when i'm done via the bluetooth in my car and again the device turns the screen back ON once i disconnect the call via bluetooth.
I just don't understand the logic behind this? Is this some HTC thing or all android? Coming from iPhone 4 never had this issue so was a first for me with this device. Just don't see the reason or logic for this?
Anyway to prevent this or stop this from happening? I mean isn't that the point of bluetooth to not need to touch your device thus no need for the screen to be turned on????
+1
It seems that this is not a HTC thing because I have the same behavior on my Samsung device. Same problem as well with pocket dialing during/after a call. Really annoying. I had the same thing on my old HTC Nexus One running Froyo, so this is not a new bug. Back then I tried a lot of different apps, and none helped. I even flashed CyanogenMod on it and it didn't change anything.
I really hope someone has run across a fix whether it's an app, a patch or a whole new ROM, because pulling my phone out of my pocket to turn the screen back off TWICE for every call I make or receive is getting to be a pain.
I can't believe this behavior is voluntary on the part of the designers. If it is, please someone explain why.
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
ethanon said:
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
Click to expand...
Click to collapse
Just downloaded but no idea how to use this thing. Not very saavy with this type of stuff. How can I use tasker to turn the screen off when ending a call ONLY while connected to a Bluetooth headset? This is my biggie since it's in my pocket.
Got it to work
Ok, I downloaded Tasker and I'm impressed.
Here's how I got this to work:
1: Create new profile using STATE, then go to NET, then hit BLUETOOTH CONNECTED. Here you can specify if you want only a specific device or any Bluetooth.
2: Set new task: SET plsLock to ON
3: Set exit task: SET plsLock to OFF
4: Create new profile using EVENT, then go to PHONE, and hit PHONE OFFHOOK.
5: Set new task as: SCREEN, SYSTEM LOCK
6: Hit IF, and specify if plsLock is ON
7: Create new profile using EVENT, then go to PHONE, and hit PHONE IDLE.
8: Set new task as: SCREEN, SYSTEM LOCK
9: Hit IF, and specify if plsLock is ON.
You're done.
Since I had the same problem with the wired headset, I also created a profile with HARDWARE, HEADSET that sets the variable plsLock to ON and exit task sets it back to OFF. You can name the variable anything you want and it will still work.
If anyone has a better/simpler way of programming this, please share. I just started using this program and am still trying to wrap my head around the way this is structured.
As this stands, it works... But it's still a patch on something that should be an option in Android.
Let me know what you think.
Ok thank you I'll give it a try. Yeah could never understand why my device thinks it's a good idea to turn screen back on after ending a call via Bluetooth or not? I receive call, I then press power button to turn screen off bit continue my call, the caller hangs up, boom my screen turns on displaying the phone dialer until my time out settings turn screen off. Dumbest feature I swear. Hello phone I pressed power offbutton to turn screen off, get the hint and keep screen off until I press power button and want it back on again. No sense...
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
ethanon said:
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
Click to expand...
Click to collapse
No unfortunately not. I would greatly appreciate that! I would think it's a simple task but honestly I'm very handicapped when it's comes to stuff like this.
Basically a string for tasker that would simply just do this:
When my device is connected to a Bluetooth device whether it be my car kit, headset, stereo headset, etc. and a phone call ends where by me pressing the End Call on screen button, by ending call with car kit, headset, etc, doesn't matter but will make the screen turn off. That's it.
When connected via Bluetooth, a phone call ends, screen turns off.
Now here's a kicker and not sure if this part would be harder. I'm connected via Bluetooth headset or device, I have screen on to manually make a phone call, then while on the call I press the power button to turn screen off while on call and put device in my pocket. Now when the call eventually ends I would want the screen to stay off.
I will read into the link you provided and mess with it somewhere. Thank you for your time and help.
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
ethanon said:
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
Click to expand...
Click to collapse
Correct BUT only when connected to a Bluetooth device. My gripe is on a Bluetooth call, place a call manually then talk on headset, car kit, etc. I press power button to turn screen off then put phone back in pocket, when call ends the phone turns screen back on for some reason. Never understood this?
Hi guys,
I know that someone with some deep knowledge can help with this problem.
I discovered that when I start a call with plugged in headset, and then I switch off the screen, the mic gets lost completely.
The same doesn't happen to the the mic if the headset is not in at all.
However if I start the call without a headset, but if I plug it afterwards and continue the call, then even switching off the screen does not stop the mic.
This behavior started for sometimes now and I am not sure what caused it. I cannot remember or find any relevant setting that may be the cause of this faulty behavior.
My phone (LG G3) is rooted, I use Xposed with some modules and additional tools, so it is possible that somehow I disabled or changed something unintentionally.
Can someone help with an useful advice?
Thank you very much in advance for the reasonable advises and hints!
I think I found the bug myself.
I switched off "Ok, Google" detection and it looks the issue is solved:
Settings-> Google-> Search & Now-> Voice->"Ok Google" detection-> Turn all settings off.