Hi,
I've been trying to get the desktop mode to work on android 12 OriginOS but all I'm getting is a blank screen with navigation buttons (either while if I pick light theme, or black if I pick dark theme)
When the phone is locked, then the clock appears on the external monitor
I tried 3 different adapters / cables but getting same results
Only app so far where it works 100% is VLC: The video will properly play on the external monitor, in full screen (no tearing visible or any artifacts)
Has this been fixed on android 13?
Did someone manage to get the desktop mode to work?
cam someone with android 13 try this in the developer options -> 'Force desktop mode'?
Does it display anything?
Thanks
I've tested it on OnePlus 9 Pro running Android 13 on a Huion Kamva 13 tablet and I could see the desktop screen on it. However pen was not working at all.
Hoping that Android 13 improves on it, anyone being successful or seen improvements over Android 12 version?
How did you get apps on the external monitor? I was unable to move an app from phone's screen to external screen, any options?
Washo4evr said:
cam someone with android 13 try this in the developer options -> 'Force desktop mode'?
Does it display anything?
Thanks
Click to expand...
Click to collapse
is it working now?
havent heard back from anyone running android 13...
finally updated to android 13 (x80 pro, snapdragon W10 variant) and can report that desktop mode is NOT working
only mirroring of whats on screen works
very disappointing from Vivo
Related
Hi guys! I got a tab pro 8.4 (mondrianwifi) last week and I can't seem to get the cast screen function in chromecast to work and I wondered if anyone had experienced and maybe found a solution. Whenever I choose to cast screen it connects but my screen on both the chromecast and tablet freeze, no error message or anything. I can still here system sounds on occasion though! The only way out of this is a reboot.
Now I have read through the forum posts and I realise there was a problem casting content within apps itself but this was apparently fixed in the NI1 update, which I'm currently using. Nothing I can see in the forum refers to the native ability to cast screen or relates to problems when using this firmware.
I have seen videos of this functionality being used on the mondrianwifi but it may have been CM or some other ROM being used, so maybe it's a TouchWizz thing.
Any help or suggestions would be greatly appreciated! :good:
I have the same problem . The mirroring freeze my tablet when using stock unrooted rom.
Right now I'm using a custom rom based on stock and rooted and my tab 8.4 (mondfianwifi) can't find a chromecast to screen mirroring.
Later I will try a few custom roms based on aosp and I will see what happens. Then I will tell you the results
Bruno_Tec said:
I have the same problem . The mirroring freeze my tablet when using stock unrooted rom.
Right now I'm using a custom rom based on stock and rooted and my tab 8.4 (mondfianwifi) can't find a chromecast to screen mirroring.
Later I will try a few custom roms based on aosp and I will see what happens. Then I will tell you the results
Click to expand...
Click to collapse
Thanks Bruno, I've actually just flashed Euphoria ROM and I'll see how that goes and let you know. Battery doesn't seem as good as stock so that's a bit annoying :/ also the notification drawer seems tiny. I guess it's still a work in progress.
Andy4Shurr said:
Thanks Bruno, I've actually just flashed Euphoria ROM and I'll see how that goes and let you know. Battery doesn't seem as good as stock so that's a bit annoying :/ also the notification drawer seems tiny. I guess it's still a work in progress.
Click to expand...
Click to collapse
Tell me your experience with screen mirroring so I don't have to try it myself. Try it using the default screen mirroring in notification drawer and later using chromecast 's own screen mirroring option
---------- Post added at 11:15 PM ---------- Previous post was at 10:54 PM ----------
Hey . I have just made screen mirroring work without it freezes the tab pro 8.4
In using a custom rom called revolution 1.1 based on stock TouchWiz 4.4 .
When I wanted to screen mirror the tablet didn't find the chromecast .
What I did was to use YouTube own chromecast option (the one that shows videos but don't mirror the screen) , then it appeared 2 option to connect with chromecast :
1) "device with cast option"
2) "name of my wifi web"
I frequently use option 2 because that's the only option available (when using cast or screen mirroring ) but I choose the 1st one (by the way, I only have 1 chromecast and that's the only device with cast options)
After I choose option 1 my TV took 10 seconds and it shows the video but it didn't appear on my tab pro 8.4 that a cast was been made.
Then I choose to click the cast option of YouTube again and this time it only appear option 2 (like always ) and then it conects at that same second to my tab and chromecast .
After that I decided to try screen mirroring again and it appears to me the 2nd option (meaning that my tab found my chromecast. That didn't happen before when I try to mirror my tab) I chose to mirror and bum! Screen mirroring working perfect!! It didn't freeze (when using stock unrooted rom it freezed right away, in 10 seconds ) . This time I went 5 minutes and all is working perfectly. !
Try yourself and tell me your experience . Good luck!
Bruno_Tec said:
Tell me your experience with screen mirroring so I don't have to try it myself. Try it using the default screen mirroring in notification drawer and later using chromecast 's own screen mirroring option
---------- Post added at 11:15 PM ---------- Previous post was at 10:54 PM ----------
Hey . I have just made screen mirroring work without it freezes the tab pro 8.4
In using a custom rom called revolution 1.1 based on stock TouchWiz 4.4 .
When I wanted to screen mirror the tablet didn't find the chromecast .
What I did was to use YouTube own chromecast option (the one that shows videos but don't mirror the screen) , then it appeared 2 option to connect with chromecast :
1) "device with cast option"
2) "name of my wifi web"
I frequently use option 2 because that's the only option available (when using cast or screen mirroring ) but I choose the 1st one (by the way, I only have 1 chromecast and that's the only device with cast options)
After I choose option 1 my TV took 10 seconds and it shows the video but it didn't appear on my tab pro 8.4 that a cast was been made.
Then I choose to click the cast option of YouTube again and this time it only appear option 2 (like always ) and then it conects at that same second to my tab and chromecast .
After that I decided to try screen mirroring again and it appears to me the 2nd option (meaning that my tab found my chromecast. That didn't happen before when I try to mirror my tab) I chose to mirror and bum! Screen mirroring working perfect!! It didn't freeze (when using stock unrooted rom it freezed right away, in 10 seconds ) . This time I went 5 minutes and all is working perfectly. !
Try yourself and tell me your experience . Good luck!
Click to expand...
Click to collapse
So screen mirroring using the chromecast app works in euphoria rom but it crashes if you rotate, if you keep it in a fixed rotation it's fine. Using the cast screen option from the notification drawer doesn't show the available Chromecast at all.
I also changed the governor settings to power save and that makes the battery performance a bit better. I'll keep playing around with those options.
I have just found the same as you but on stock TouchWiz rom with 4.4 kitkat. If you rotate the screen it freezes and also it freeze if you start screen mirroring while horizontal but If you use the tablet all time in vertical it's fine.
What about the color while screen mirroring in a aosp rom ?
Are they inverse or negative?
If you start the screen mirroring while the tab pro is horizontal and don't rotate . Does it freeze?
In my case , using TouchWiz 4.4 it freezes no matter if I rotate to horizontal or if I start the mirroring in horizontal
Bruno_Tec said:
I have just found the same as you but on stock TouchWiz rom with 4.4 kitkat. If you rotate the screen it freezes and also it freeze if you start screen mirroring while horizontal but If you use the tablet all time in vertical it's fine.
What about the color while screen mirroring in a aosp rom ?
Are they inverse or negative?
If you start the screen mirroring while the tab pro is horizontal and don't rotate . Does it freeze?
In my case , using TouchWiz 4.4 it freezes no matter if I rotate to horizontal or if I start the mirroring in horizontal
Click to expand...
Click to collapse
The colour is normal on this ROM and if you start in landscape it's fine as long as you don't rotate. Even if you do, it just disconnects you.
I'm still undecided about sticking with this ROM or to go back to touchwizz. Battery is better on stock but I like the aosp lollipop feel so I'm not sure... Battery is really important to me though so I'll probably go back to stock or a modified stock rom. Hopefully aosp lollipop ROMs will improve when touchwizz gets a lollipop update!
Hopefully you are right. Sometimes in horizontal it doesn't freeze even if you rotate the screen but I'm not sure if those freezes were because of the first time of using mirroring r just at random
If I try any other ROMs I'll let you know mate!
I received a Nexdock which is basically a display and a bluetooth keybord. The idea is that with Nexdock you can turn your Pine64 computer into a laptop.
More info on NexDock on indiegogo.com
I'm running RemixOS 2.0 on my Pine64 2GB but I can't change the output resolution of the Pine64 to 1366x768.
1366x718 is the native resolution of the Nexdock.
Nexdock works together with Pine64, but all text is hard to read because of the wrong display setting.
When ordering a Nexdock Nexdock claimed compatibility with Pine64...
Any solution or Remix OS update to fix this issue?
I'm on the same boat as you.
Running debian the display is using the right resolution but obviously there's no GPU acceleration and no bluetooth working.
Bluetooth will get a fix in the future probably but I have little hope for GPU on debian. That means no usable Kodi-
At this stage of development Android (and RemixOS) seems to be the better solution for the Pine64.
On PC you can change the vesa mode at boot but I don't know how to do it on Pine.
Ok. I don't have an available SD to burn again RemixOS but could you try this?
in settings> experimental features >enable debug terminal console
press Alt+F1 this will opens the console
type wm size 1366x768 hit enter
press Alt+F7 to exit
Debug window
Unfortunately, that option seems to have been removed for the Pine build. I tried alt+f1 to see if maybe it was enabled by default, but no luck.
I've got a problem with my Honor 8 Pro (EMUI 5.1, Android 7.0).
Whenever I play a video fullscreen on YouTube, I notice the brightness of the screen increasing. After I leave the fullscreen mode the brightness doesn't change unless I close the app.
Black colors look washed out thanks to this and watching dark videos is problematic. Anyone else with the same issue?
I which fw version you are?I dont have that problem.Try update phone to latest B188.
Allek84 said:
I which fw version you are?I dont have that problem.Try update phone to latest B188.
Click to expand...
Click to collapse
I have all updates installed
Did you try to repair software via Hisuite or reset to factory settings including erasing all files from memory?Really strange problem.
I have this same issue on Emui8 .. Besides Amazon prime video
Every single app turns the contrast weirdly high and the black colors are not black anymore.. Awkwardly enough I have to constantly keep a finger on the screen to view a video normally in MXplayer.
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
BuzLightSabre said:
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
Click to expand...
Click to collapse
Usually features can vanish in an android version upgrade, but not in a regular update.
https://wiki.lineageos.org/bugreport-howto.html
kurtn said:
Usually features can vanish in an android version upgrade, but not in a regular update.
https://wiki.lineageos.org/bugreport-howto.html
Click to expand...
Click to collapse
Yes. I would have thought that this was so but Miracast was working until I updated a 20200801 nightly build. That's why I think that it might be a default setting.
I also noticed this:
https://forum.xda-developers.com/showpost.php?p=64121701&postcount=10
Maybe that will solve the problem?
BuzLightSabre said:
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
Click to expand...
Click to collapse
Google creates Android Compatibility Definition Documents, in which it is written:
Code:
5.8. Secure Media
If device implementations support secure video output and are capable of supporting secure surfaces, they:
[C-1-1] MUST declare support for Display.FLAG_SECURE.
If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:
[C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.
If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:
[C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.
That's the theory. In practice, everything depends on programmers.
For example.
In the custom ROM with Android 9 for Oneplus One Miracast (connection to Microsoft Wireless Display Adapter) works only in 3 ROMs with 33 that I tested.
In the custom ROM with Android 10 for Oneplus One Miracast (connection to Microsoft Wireless Display Adapter) does not work in any ROM with 25 that I tested.
.
.
Miracast starting working again after build 20200829. There was d"ummy HIDL lib" removed that shouldn't have been removed and now it's back again. https://review.lineageos.org/284011
BuzLightSabre said:
Miracast starting working again after build 20200829.(...)
Click to expand...
Click to collapse
To which model of device do you cast the screen in Android 17.1 using Miracast (WiFi Display)?
.
I have a Panasonic Personal Video Recorder (PVR) model number DMR-BWT955. Under its Function menu there's an option to "Miracast". I select that option and it starts searching for devices. I select the "Screen Cast" option from the drag down menu on my Pocophone and select the "DMR-BWT955" device to connect to. They both do their bits and then I see my Pocophone screen showing up on my TV screen, which is connected to the PVR. My 5.1 surround sound system is also connected to the PVR and so I can not only see what's on my Pocophone but also hear what's it's playing through the 5.1 sound system.
Is that the sort of information that your after?
BuzLightSabre said:
Miracast starting working again after build 20200829. There was d"ummy HIDL lib" removed that shouldn't have been removed and now it's back again. https://review.lineageos.org/284011
Click to expand...
Click to collapse
Hi
Still doesn't work on lineageos 17.1.
I try to connect my tv to honor 5x to miracast screen but see no tv.
I add persist.debug.wfd.enable=1 on build.prop to enble wireless display. Nd see 'Anycast' device
But when I try to connect, lineageos reboot ( hot reboot without vibration neither pin prompt)
I am using 11 mars 2021 build witch is newer than 28 ugust 2020
Build lineageos-kiwi-userdebug 10qq3a 200805.002 d5580ebdfc
Official lineageos.
Worked perfectly on lineageos 14.1, 15, 16
Cheers
I am not able to enable the Android12 Desktop UI on my Vivo X80 Pro.
The Phone was pluged in to a USB C Hub with HDMI Port. but it just mirrors me the Phone Display.
I've already enabled this Feature in the Developer Options (Force Desktop Mode).
But it does not work.
I am more and more annoyed about the software.
I was wondering the same thing
but at least, having video output is a good start
Can anyone confirm if desktop mode is working on funtouch OS?
Can anyone confirm if desktop mode is working on funtouch OS 13 for vivo x90 pro?
it is not working on the X80 pro
you could check the x90 dedicated threads and see, but I expect it to not work as well