Noticed something puzzling that started occurring out of nowhere yesterday. I'm constantly getting a pop up at the bottom of my screen reporting the current battery level of my wireless headphones (Sony WH-1000X M3) every few seconds and can't seem to get it to stop. I've owned the headphones for over a month now but this issue only started yesterday. Unpairing the headphones then pairing them again seemed to have stopped the issue from happening yesterday but it has started all over again this afternoon. This is preventing my display from going to sleep as the phone wakes every time the pop up appears (It does not wake the device if I manually lock it using the power button however).
I updated to MIUI Global 10.3 | Stable 10.3.2.0(PDGMIXM) this morning but the issue started while I was still on Global 10.2
Anybody have an idea as to what might be going on?
Related
Hi!
I already saw that there are some posts about similar problems but I'm a little bit confused because they are inconsistent.
I'm charging my Transformer over the 12V of my car and it's working correctly. I have about 13,5V when the engine is started and 0V when it is stopped. Thats good because I don't want the Transformer to be charged when the car is parked. The voltage is stable.
Now I already saw a problem about 3 times:
Two times the tablet wasn't detecting the 13,5V for charging. The battery icon got no flash and even after some time and reconnecting the cable, the transformer does not showed the flash.
One time I had the opposite problem. I stopped the car, the voltage tropped to 0V but the charging flash of the icon does not disappeared.
In all three cases a restart was the only thing which solved the problem.
Why is this charging detection so important for me?
I am using the app tasker to find out if the tab is getting charged and the car is started. If so I'm automatically changing some settings like bluetooth, wlan and screen always on...
Most of the times this works without any problem. Car gets started and tablet screen turns on automatically (cool ^^).
When the problem above appears, tasker also not detects the start of the car. Since the normal Android icons are also not working I'm expecting no problem with the tasker app.
Can somebody verify this problem which is independent from the charging adapter and the keyboard dock?
Any work arrounds?
thx
Hi XDA-Community,
you are my last Chance of Help. I recently got the Samsung DA-E550 Wireless Audi with a Docking Station and encountered a Problem. I wanted to use the Speaker for my Alarm in the Morning. The Problem is that the Station goes into Standby after 30min and cuts the Bluetooth Connection wich results in usage of the intern Speakers of my Phone instead of the DA-E550.
You know any way to keep the Station powered with a Bluetooth Signal or something else? It was the main Purpose why i got it and that it doesnt work kinda sucks....
Cheers
Exalor said:
Hi XDA-Community,
you are my last Chance of Help. I recently got the Samsung DA-E550 Wireless Audi with a Docking Station and encountered a Problem. I wanted to use the Speaker for my Alarm in the Morning. The Problem is that the Station goes into Standby after 30min and cuts the Bluetooth Connection wich results in usage of the intern Speakers of my Phone instead of the DA-E550.
You know any way to keep the Station powered with a Bluetooth Signal or something else? It was the main Purpose why i got it and that it doesnt work kinda sucks....
Cheers
Click to expand...
Click to collapse
I ordered one and it is arriving tomorrow - I am also hoping to use it as an alarm clock (My galaxy note 2's alarm isn't quite loud enough - I am a deep sleeper)
I am hoping with tasker I can auto turn off then back on bluetooth 5 min. before wake up time and that will wake up the dock.
If that works I will let you know. (when your dock is on standyby if you turn your phones bluetooth off and back on does that wake up the dock? - if so you can use taker (see link below) to auto turn your bluetooth off and back on a couple min. before your alarm goes off - this is assuming that the dock will auto connect with the speaker upon bluetooth being turned on on your phone.)
As long as when the dock goes into standby it will wake up when a device tries to connect to it via bluetooth this should work.
Tasker - https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm
Nope when it goes to sleep - it is dead to the world untill you hit the power button.
Best option is to go to sleep with a silent mp3 on loop I guess
Yea i tested a bit for myself but couldnt wake up the device but your alternative is a neat trick. Didnt thought of that.
6666 said:
Nope when it goes to sleep - it is dead to the world untill you hit the power button.
Best option is to go to sleep with a silent mp3 on loop I guess
Click to expand...
Click to collapse
I seem like to have failed the first try this night. Did you try it? Worked it?
Did it work, i am facing the same issue too, sucks cause i cant use it for its main purpose, alarm!
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.
So I have been using stock ROM or very close to for the past 6months or so and constantly have this issue despite clean wiping multiple times while moving from Lolipop to M preview to M.
At first I thought it was my specific car but now is happening with the rental I have.
I am new to Bluetooth so maybe normal but I don't think so.
When I connect to my cars Bluetooth then make a call, after the call I get a constant "bluesleep" wake lock until I turn Bluetooth off.
If I make a call during the day while driving then get out of the car when I get home, it keeps my phone awake all night unless I remember to turn blue tooth off.
Ive noticed it only happens once I make a call or use the Bluetooth for something. If I just simply connect to my car, I don't get a wake lock.
Is this how Bluetooth is supposed to work? I can't imagine so but the fact I'm basically stock and have wiped many times and different android versions makes me think maybe it's just an android thing.
it could be app related. gasbuddy has been documented to be a culprit. i can't provide link, but there is a thread on google bug tracker "Issue 87778: Bluetooth wakelock caused by Bluedroid timer keeping device awake"
Wow that worked! Thanks so much
Hi,
My S10e started to have low contrast (very poor back value) and is runny very hot in battery mode. When plugged in the phone is fine.
The behavior usually starts when the phone is waking up in battery mode. It immediately cools down when plugged into a power source. Switching the screen off and on again while plugged in is fixing the colors.
I have my S10e (G9700) now for one year. Yesterday it suddenly started the weird behavior. I haven't installed any new apps or changed any setting.
The only unusual was that it ran out of power and I was not able to charge it for a couple of hours. When I arrived home I plugged it in and charged it to 40%. I unplugged it and started the phone and I run into the trouble I described above.
Sometimes a restart helps till the screen is switching off for standby. Waking the phone up results again in the weird behavior of the colors and the phone is running hot and the battery drains in super fast.
I can't debug the behavior with adb as the phone is running fine as long it is plugged in.
Any ideas what that could be and how to fix that?
Is there a way to connect with adb in unplugged power condition?
I appreciate every help.
Cheers
The issue seems to be connected to the last System update for the S10e. After a factory reset the phone was working fine for two days. After the System update G9700ZHU2BTA2 the issue is appearing again.
And what happens if you go back to BSL7?
I installed BSL7 with odin. The same issue seems to keep happening. It seems the update G9700ZHU2BTA2 and the appearance of the issue was just a coincident.
I'll install ASJU in the next days just to check if the issue is existing in Android 9 as well.
I'm living in Singapore and Samsung support here has rejected to take care of the issue. They are not even able to send the device to Hong Kong to fix the issue. Neither is Hong Kong is accepting that I send the device to them. Only personal handover at the HK support center. Has anyone here experience how to deal with the Samsung support? I have not expected that from an global player like Samsung.
Anyone an idea?
It seems not to be connected with the power source. The issue seems to be connected with the "always on screen". When the always on screen is displaying nothing in the moment of waking up the phone this issue appears.
A workaround now for me is to turn the "always on screen" always on
A tool that is switching on the always on screen before waking up the phone would be hotfix. Any idea if it is possible with the Android SDK to hook in there?