Hi there - I guess this might be a question for @electrikjesus but the IPTS Surface Pro stable build (11.10) doesn't appear to have the Android-x86 options in Settings. This means a number of ARM games don't run. I can install the stable 11.9 build on a Surface Pro (2017) and the Android-x86 options are there, can be enabled and games run. However, using the firmware as per the documentation to enable touch on a Surface Pro does not work on the non-IPTS 11.9 build (presumably by design).
Is there a way to get the Android-x86 options on the IPTS stable Surface build please? Everything else is working just great (I know there are issues with cameras, mics, sleep, etc.)
I also tried the 12.6 build but couldn't get touch working, tried the old 11.6 (11.4?) Surface builds but no Play Store, etc, etc. The 11.10 works great IF I could enable the Native bridge. I have the 11.9 installed on a Dell XPS 13 and everything works super, including touch.
Thanks in advance,
Shaky
Related
XDA Thread
I've tested and it works for the most part. Though it seems a little sluggish. And it Arm not Arm64 so if you want gapps choose ARM 7.0. As the thread says Video and audio recording doesn't work (though I believe the mic works).
And yes I know it's for Android One Second gen devices but as the Swift is a clone of the GM 4G it works. And I've tested that it works.
Just thought I'd share the thread
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'm running the official LOS16 now and I've tried to enable ARCore. Everything seems to work, I can go to the Playground feature in GCam and place stickers, but the viewfinder is kinda sluggish and doesn't recognize any surfaces, so stickers just jump around not attached to anything (though sometimes looks like it works, just sometimes and without dots for surfaces).
On the last preview build I was of LOS16 ARCore was perfect and I don't think I changed much, so no idea what could work, that's what I'm using:
Arnova's Advanced 1.4 https://f.celsoazevedo.com/file/gcamera/GCam_6.1.021_Advanced_V1.4.032219.1950.apk
ARCore_enabler1.4 https://f.celsoazevedo.com/file/gcamera/ar/ARCore_enabler1.4.zip
ARCore from the Play Store
Playground_No_Pack_V2.0build-2.2.190204106 https://f.celsoazevedo.com/file/gcamera/ar/Playground_No_Pack_V2.0build-2.2.190204106.apk
And if you want to test for yourself here's the TUT: https://www.celsoazevedo.com/files/android/google-camera/ar/ - https://www.celsoazevedo.com/files/android/google-camera/ar/ Option 1.
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
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