I'm wondering if this is because of my device (HTC Titan) or because of WM6... all I know is that I never had this happen before!
Basically, I'll pull out my phone sometimes and find that its turned on by itself, and has been sitting with the dim idle backlight on.
I noticed it can be caused by several things but the 2 main ones I've seen is:
1) when the phone switches to/from roaming, it wakes up
2) when using A2DP controls (AVRCP), it wakes up.
I've been using workarounds to keep the backlight off for now (set the phone to roam only, or carrier-only, so it won't be switching in/out of roam, and use core player or just remember to toggle the screen off everytime I use a media AVRCP control), but there has got to be a better way to keep the darned screen off until I press power!
Anyone have any suggestions? This is really an unexpected annoyance as it eats up my battery quickly not knowing its on...
I had a similar issue with whenever I received an email and didnt shut off the device manually. What I eventually ended up doing was setting the device to automagically lock when it was powered off, and this seemed to solve the issue. I'm not sure however if this will fix it in your case because locking it may interfere with AVRCP controls working.
I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.
So I had this same problem when I first got my Z1 Compact, but it went away after a while (I'm not entirely sure how). This creates a problem if I have my phone in my pocket, as it will skip tracks, fast forward and rewind, and waste battery. Is there a way to prevent the screen from waking when the device connects to a Bluetooth device?
EDIT: Found a solution! At least for me, hope it helps others as well. My bluetooth microphone no longer works, so I went into the Bluetooth settings for the stereo and unchecked the box to use the BT for phone audio, and only left media audio checked. This seems to have fixed this issue as well, as my screen no longer turns on automatically when it's connected! I re-checked the box and it turned on like before, so it seems like that's what's causing it to wake.
festizzio said:
So I had this same problem when I first got my Z1 Compact, but it went away after a while (I'm not entirely sure how). This creates a problem if I have my phone in my pocket, as it will skip tracks, fast forward and rewind, and waste battery. Is there a way to prevent the screen from waking when the device connects to a Bluetooth device?
Click to expand...
Click to collapse
Have a look at the Smart Connect app, maybe it has an event there that triggers when the bluetooth connects.
Thank you for the suggestion. Unfortunately, there were no such events under any of the Smart Connect options, and I can't even find an option to turn the screen on/off when a device is connected or disconnected.
I've tried setting the screen timeout to 15 seconds (the lowest possible), and I noticed that once the screen turns on after connecting, it never times out or turns off on its own. It was sitting on my car's dash, and I listened to a few songs without it shutting off. I even checked the timeout settings afterwards, and it was still set to 15 seconds.
Any idea what else could be causing this? Maybe Throw? I know I was able to uninstall that on my Z1C using Titanium Backup, but obviously I can't on this one since it's the T-Mobile Z3.
EDIT: So this apparently only happens when connecting to my car stereo. I just tested it with my Bluetooth headphones and the screen stayed asleep the entire time I was connecting and playing music.
I still have no idea what could be causing this, but I'm starting to think it has something to do with my stereo and not my phone. Is there any app or way I can test it? So far, here's what I've tried. Again, on T-Mobile Z3 so no chance of rooting at the moment. Screen still turns on whenever my phone auto-connects to my car stereo's Bluetooth.
1. Disabled Throw using adb shell.
2. Disabled MirrorLink using adb shell.
3. Disabled Smart Connect using adb shell.
4. Auto-connected to Bluetooth headphones and screen stays off as it should.
5. Tried with multiple apps (Shuttle+, Walkman, PowerAmp, even with all music apps uninstalled/disabled).
6. Old phone's screen (Z1 Compact) still stays off when connecting to the car stereo. It's rooted with an unlocked bootloader, maybe something in the Z3's DRM keys is telling it to wake up?
So that's where I'm at right now, not sure where I can go from here. I suppose I'll have to learn to live with it for the time being.
festizzio said:
So I had this same problem when I first got my Z1 Compact, but it went away after a while (I'm not entirely sure how). This creates a problem if I have my phone in my pocket, as it will skip tracks, fast forward and rewind, and waste battery. Is there a way to prevent the screen from waking when the device connects to a Bluetooth device?
Click to expand...
Click to collapse
Do you have :Smart backlight control in "Display Settings" on? In my case that was the problem! So when the screen wakes up and i'm on the move, this setting prevents the device from auto lock.
Same issue around here mate. I got a pioneer car stereo and I set the smart connect to play music as son it connects. Every time it connects the screen turns on and I got the connection message on status bar.
Smart backlight control was off, but I tried turning it on just in case. Screen still turns on. I don't even have Smart Connect enabled right now, and I don't get any connection message when it connects. I'm thinking it has something to do with Pioneer specifically, since mine's a Pioneer as well. It also doesn't turn on when it connects to my bluetooth headphones/headset, which should be the same type of connection.
I'll try messing with some settings on my stereo, see if that does anything.
I'll try on my friends Sony stereo later and see if the issue happens.
When I connect the lg g watch the screen remains off.
Sent from my D6643 using XDA Free mobile app
I tested on my friends Sony stereo and the issue is there. The screen lits.
Sent from my D6643 using XDA Free mobile app
I have the same isue with my zenec car radio This sucks because I can't keep my phone in my pocket while I'm driving.
It would be interesting to know if this is a general android isue or if it's only a isue from sony smartphones with stock rom. Just to narrow down possible causes...
I also have this issue with my Kenwood deck. I also noticed my volume resets to half too, which is even more annoying than the screen turning on. I have no smart connect events or anything turned on. Odd thing about the volume, it doesn't do it all the time. It just seems to randomly.
NumRocket said:
I have the same isue with my zenec car radio This sucks because I can't keep my phone in my pocket while I'm driving.
It would be interesting to know if this is a general android isue or if it's only a isue from sony smartphones with stock rom. Just to narrow down possible causes...
Click to expand...
Click to collapse
It may be a security "feature", so that no-one/nothing can connect to your device without you seeing the screen light up.
poldie said:
It may be a security "feature", so that no-one/nothing can connect to your device without you seeing the screen light up.
Click to expand...
Click to collapse
I don't think so, because the phone is most of the time in the pocket so it wouldn't make sense to lighten up the screen to inform the user about a "BT event".
But hmm, maybe I'm able to solve it with tasker
BT connect on event -> turn screen off
NumRocket said:
I don't think so, because the phone is most of the time in the pocket so it wouldn't make sense to lighten up the screen to inform the user about a "BT event".
But hmm, maybe I'm able to solve it with tasker
BT connect on event -> turn screen off
Click to expand...
Click to collapse
Lighting up, by itself, would be harmless, even if your phone is usually in your pocket.
I was going to suggest tasker, but I never got anywhere with it (at least, the things I wanted to do, which don't appear to be too extravagent, apparently require either a rooted phone or additional non-free plug-ins).
poldie said:
Lighting up, by itself, would be harmless, even if your phone is usually in your pocket.
I was going to suggest tasker, but I never got anywhere with it (at least, the things I wanted to do, which don't appear to be too extravagent, apparently require either a rooted phone or additional non-free plug-ins).
Click to expand...
Click to collapse
As other member have already described, the screen keps turned on for a long period of time when a BT device connects. So it's battery waste and it's likely that I execute unwanted actions like calling someone
But thank you anyway... I'll try it with tasker and will share my solution here if I find one..
I have a Pioneer car stereo, but I haven't noticed my screen turning on. I'll test this when I get off work.
I did notice though that sometimes the BT volume goes to 50% as mentioned earlier.
My screen does not turn on when it connects to My pioneer car stereo.
Sent from my D6616 using XDA Free mobile app
My screen turns on when it connects to my Sony stereo in my Ford fiesta [emoji20]
Sent from my iPad using Tapatalk
I have Z2 and Uconnect stereo in my car and my screen turns on when connects to stereo.
Bumping the topic.. exact same problem. Screen lights up every time I connect via BT to my car Kenwood stereo. Very very irritating. Battery drains out without even my knowing it. Seems like a serious bug.
When I get into my car and my bluetooth headunit connects with my Z3, the screen decides to turn on... for no reason whatsoever. I've disabled apps, tried setting up tasker to turn the screen on after a few seconds... yet nothing seems to work.
Why is this happening? I never had this with my Z2, it really sucks when my phone is in my pocket and I just want to drive, instead I get random actions, and even at one point pocket dialed people.
I hate to reply with anything but a solution, but this is an ongoing issue for me as well. It doesn't seem like it's solvable without a custom kernel. After I rooted my Z1C and installed SlimKat, it stopped happening. Since I got my Z3 I haven't been able to figure it out at all. The closest I got was to install a custom lock screen and have Tasker check for BT Connected and [custom lockscreen] started then wait 1 ms and turn the screen off. That used a ton of battery. I guess it's a solution if you find a way to stop the battery drain. Went from 5+ SoT to less than 3 in a day.
Bumping the topic.. exact same problem. Very very irritating. Battery drains out without even my knowing it. Seems like a serious bug.
I'm not sure I've actually identified the problem so let me start at the beginning.
I have a new Gear S3 Classic. It randomly will beep and vibrate for no apparent reason. If I look at the watch the only difference I can detect is a watch icon in the 12 o'clock position on the face. If you swipe on it, it will display the word 'standalone.'
The problem is that it should not be in standalone mode since this always seems to happen when the watch is in close proximity to my phone. What's worse is that it doesn't just happen once but 2 or three times in close succession before it finally gives up.
I think I can defeat the notifications by putting the watch in do not disturb mode but that has other obvious disadvantages.
So is my watch defective? Do I need to pursue a warranty claim? Am I doing something wrong, do I need to reconfigure my watch somehow? I have no idea how to proceed from here. Any help is appreciated.
I think the vibrations are BT disconnection alerts. This can be disabled in settings CONNECTIONS -> ALERTS.
In terms of addressing the underlying problem of why the watch and phone aren't able to maintain a solid BT. Have you tried pairing to a different phone, to rule out a problem on that end?
afblangley said:
I think the vibrations are BT disconnection alerts. This can be disabled in settings CONNECTIONS -> ALERTS.
In terms of addressing the underlying problem of why the watch and phone aren't able to maintain a solid BT. Have you tried pairing to a different phone, to rule out a problem on that end?
Click to expand...
Click to collapse
Thanks for the tip. I set it to turn of the alerts. That will be very helpful since it could be seriously distracting at times not mention annoying for other people with me.
My guess is that it's an issue with my phone - Alcatel Idol 4. It probably doesn't send out an "I'm here" signal or whatever the technical term is, often enough for the S3 to realize that it's in range. The last time this happened, I swiped the icon and looked at the watch face and within about 10 seconds it reported that it was connected again.
As long as I don't have to listen to the watch and phone work out their marital differences though and they can manage to stay connected when I need them to be, I'm not going to worry about the watch going standalone periodically.
Thanks again.