Wireless Display - Cast turns off automatically - Asus ZenFone Max Pro M1 Questions & Answers

Using wireless cast on a Samsung Smart TV. Have used cast with devices like OnePlus One, Mi Max, Redmi Note 5 Pro, OnePlus 3T without any issues. I have no issues connecting my M1 pro to TV, but it turns off automatically after 5-8 minutes. I noticed that it stayed on for few more minutes if I touch the display in frequent intervals, which is annoying. Playing a game would've confirmed it but multi-touch is even more irritating. Have been facing this bug since FW Ver. WW-15.2016.1805.309 and currently using WW-15.2016.1805.311.
I searched XDA threads and ZenTalk for similar threads but to no avail. So, if both Stock and Custom rom users could help me out with this - that'd be great.
Cheerio
Edit : The display or playback doesn't turn off, only cast disables/disconnects automatically. Have tried disabling WiFi Scanning, Public network notification, kept display on using Caffeine (pointless but anything worth trying must be tried out).
Edit #2 : Update dated 12-13th July did not fix it either. Cast continues to disconnect after 5-10 minute mark. Currently using WW-15.2016.1805.316

Bug is still present in the latest 316 update. I request all members to please look into the matter and confirm your findings.

I am using it with my mi tv. Faced no such issues.

Related

Lollipop issues with Android Wear

I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk

Bluetooth audio "stutter" on wake/unlock?

Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Gizmoe said:
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Gotcha, that's what I was afraid of. Will checkout the N Preview, thanks!
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Shocknoble said:
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Click to expand...
Click to collapse
I have the exact same problem with my 2015 Chevy Volt nav / stereo system. I never noticed this issue until I updated to the Android N release a few days ago. It always happens when I turn on the screen. I rooted and went back to Android M, but the issue is still there. I'm guessing that's because my phone now has the latest baseband and radios instead of the older ones that did not have this Bluetooth problem. If you guys come up with a fix let me know. I'm thinking of flashing the Android M radios to see if that's the problem since I'm now running a custom Android M based ROM anyway. I tested the phone with my wife's 2016 Mazda CX5 and it has none of this screen on stuttering garbage.
UPDATE: I went ahead rooted, installed Pure Nexus ROM (6.0.1-20160821), installed ElementalX-N6P-1.21 kernel, flashed bootloader-angler-angler-03.54.img and radio-angler-angler-03.61.img from angler-mtc20f-factory-d62de11e.tgz, and after all that the issue is still there! What a complete waste of time. What I'm guessing might be the problem is I switched to Sprint on July 2016. Before that I was on T-Mobile and I never had this screen on stuttering issue. It seems there might be some type of interference here and it's possible it is a hardware design flaw since Google has not been able to fix the issue for quite some time. As of now I've switched to my LG G5 phone which has no Bluetooth issues with my Chevy Volt. If I don't find a fix soon I'll probably sell the Nexus 6P and wait for the newer Nexus devices.
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
macmanui said:
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
Click to expand...
Click to collapse
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
I have found a somewhat reliable fix - PLEASE tell me it works for you all as well.
Hopefully we are all familiar with the problem: A Nexus 6P ( Or whatever is the issue for you) is paired with my 2015 Chevy Cruze that I use to stream audio while commuting. The audio is more or less fine until the screen turns off/I lock the phone. Once I unlock the phone or a notification wakes the screen up, the audio stutters over my car speakers until I turn the screen back off, or 6-8 seconds has passed. This doesn't happen with any other device I own when paired to my car, and my phone doesn't have the same issue when paired with any other bluetooth receiver. I am on a rooted but otherwise stock 6P running 7.0.
I do not use my car for messages, only music/podcasts and phonecalls. I went into the bluetooth settings while driving ( I do not recommend you do this while your car is in motion) and noticed the stuttering was consistent the entire time I had the menu open. This prompted me to assume it must have something to do with the phone making other bluetooth actions while connected to my car, that my car didn't like.
I clicked on the gear for settings next to my car in the bluetooth paired devices list, which pops up the menu that lets you change the name of the device, and what it is used for. My options are: 'Phone Audio', 'Media Audio', 'Contact Sharing', and 'Message Access'. I denied message access to my car the last time it prompted me, but the last two on the list were still checked. I unchecked both of them, reset my phone, and crossed my fingers.
It works. It freaking works. It's not 100% and if I flip the screen on and off over and over again it'll still get a little wonky, but I no longer cringe when I have to unlock my car in the phone.
Will the rest of you give this a shot and let me know if you have similar luck? Best wishes!
Josh
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
---------- Post added at 01:50 PM ---------- Previous post was at 01:50 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
Seems that GM vehicles are a common denominator too! I have the stuttering with my 6P int my Holden Cruze. Didn't have the issue with my old Nexus 6 and don't have the issue with the 6P when making calls over BT. I haven't listened to as great deal of music from the 6P over BT except in the car so can't really compare there.
It's interesting to read a comment that it was going to be fixed in M preview 3 but even now in Marshmallow release the issue is still there.
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Pica_Man said:
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Click to expand...
Click to collapse
Interesting. It certainly does feel like a bandwidth issue. I have a Moto360 and has tried turning that off but hadn't thought of turning phone functions off. I don't really want to do that either but will try it to confirm.
I turned off phonebook and SMS but it made no difference to me at all.
I have noticed a Terrible shutter from my device when paired to a portable BT speaker. at times the only fix is to turn the speaker off then back on. it is horrid.

Should i replace my device?

1. I am facing a, haptic feedback issue, auto brightness issue, and now another touch issue.
2. Was using youtube in landscape, and minimised the video, and then post that it did not register any touch. tapped on the video, youtube menus, nothing worked.
pressed home, reloaded the app, it worked again.
3. Was using Microsoft remote desktop app, the device rebooted itself. Opened the app again, again the device rebooted itself.
Should i go for a replacement?, am i using a faulty unit!
Seems more of a software issue. 1 is a known bug and 2 happens at times. 3 might have happened due to kernel panic. MS apps are not always well coded and up-to-date
Sent from my MI 5 using Tapatalk
So none of this is a major issue, and would resolve through an update?
I have 10 days to return the device, its only been 4. Was thinking to return it coz of all these issues.
Sent from my ONEPLUS A5000 using Tapatalk

Screen sharing issue

I am having an issue with screen sharing. It has always worked before today. Right now, when i screen share I get a black screen on both of my smart tvs. If i am playing a video I can still hear the sound. Also, if i share to my tv through youtube it works fine. If i share to my tv through the stock gallery app it also displays a picture. If i share to my tv using the stock video app it also displays fine. The issue only occurs when I use the screen sharing app itself to mirror the phone to the tv.
I have tried restarting the phone, pulling the battery, restarting the tvs, pulling the power wire for tvs from wall and restarting tv that way and I also tried restarting my router. I cannot figure this out and was wondering if anyone else has run into this issue and maybe has a fix. Thanks in advance.
Also, my phone is completely stock.
Did you install a security update from Verizon recently? I have an Lg v20 and am having a similar problem.
Sorry, hadn't had anyone reply to the thread so figured it was a lost cause. Im on at&t and yes I do remember getting a security update prior to this occuring. Still havent found a solution.
There seems to be a problem with the latest update for the 990DS as well .
Edit: Yes mine have the same issue after the update
Its odd that there hasnt been more people with this same issue. Im inclined to say its an issue with the last security update because theres 3 of us with similar situations. Just wish there was more info anywhere on the web about it. Either the 3 of us are experiencing an isolated issue or nobody uses screen share.
Just got another security update now. Tried the screen share and sure enough it is working once again.
Fingers crossed
I hope I receive a similar update.
I happen to have two v20’s and one will screen share at full screen and one screen shares at 4x3 with black bars in the sides. Is there a way to fix this nd screen share so it uses the full screen?
LG v20
When screen mirroring apps to my Samsung TV everything all good until I stream netflix, hbomax, espn & tnt. I get no picture/video, only audio and subtitles. Any solution?
I don't recall doing an update and this LG v20 is on T-Mobile network.

[Help] Wear Os disconnect problem.

Hey, guys.
I've trouble with my smartwatch "Ticwatch E2" and think it's occur because wear os problem.
My watch is disconnect from bluetooth or even wifi randomly.
I've tried restart ,reset watch or reinstall latest wear os on my phone (Galasy S9) but problem still occur.
I've noticed this problem occur when I've enter game or open many apps on my phone. (I suggest it's battery saving feature on android oreo) Could it be the reason? If so, How could I shut it down even its drain my battery? (I've checked my app list and it has already shown "exemp")
Anyway, I've searched for any solution but have not found permanent solution yet.
Could anyone can help me for this problem?
Thank you for every comments
You're not alone, I have tried everything, I even flashed Lineage OS 16 on my Mi 5s Plus, this is supposed to fix that issue but no change I have a Moto 360 Gen. 2.
Help!
Hy, I have redmi note 7, it is not pairing with my smart watch (ticwatch e2), my watch is pairing with other cellphones like ( iPhone and Motorola) but not with xiaomi redmi phones I tried to pair it with redmi note 4 as well, kindly look into this
markus_mark said:
Hey, guys.
I've trouble with my smartwatch "Ticwatch E2" and think it's occur because wear os problem.
My watch is disconnect from bluetooth or even wifi randomly.
I've tried restart ,reset watch or reinstall latest wear os on my phone (Galasy S9) but problem still occur.
I've noticed this problem occur when I've enter game or open many apps on my phone. (I suggest it's battery saving feature on android oreo) Could it be the reason? If so, How could I shut it down even its drain my battery? (I've checked my app list and it has already shown "exemp")
Anyway, I've searched for any solution but have not found permanent solution yet.
Could anyone can help me for this problem?
Thank you for every comments
Click to expand...
Click to collapse
Samsung is getting worse after pie update. The aggresive battery saver kill almost everything. Follow the instruction on dontkillmyapp for S9. Hopes thi helps
Cloos said:
You're not alone, I have tried everything, I even flashed Lineage OS 16 on my Mi 5s Plus, this is supposed to fix that issue but no change I have a Moto 360 Gen. 2.
Click to expand...
Click to collapse
Does your disconnection also happen when opening some app? If yes, can you try to repeat if that is reproduceable consistently?
waliwasti said:
Hy, I have redmi note 7, it is not pairing with my smart watch (ticwatch e2), my watch is pairing with other cellphones like ( iPhone and Motorola) but not with xiaomi redmi phones I tried to pair it with redmi note 4 as well, kindly look into this
Click to expand...
Click to collapse
What is the ROM at Redmi Note 7 or 4? If you are using custom ROM, there might some extra restriction preventing it from pairing. Example is LineageOS privacy guard, if this is enabled for the wear os app, you can't pair it properly. You have to exclude it. I use RR pie, which has LOS privacy guard too, have no problem with pairing, since I exclude it.

Categories

Resources