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.
Related
I know many Samsung I780 owner is facing the resolution problem on that 320x320 display.
Some program is not work or identify the wrong resolution on it.
For example, the SlingPlayer mobile is recognized my i780 as 240x240 display and cannot support fullscreen playback with a small windows look like 160x160.
For this reason i tried Tweek2K2, but i did not support on non-Vga machine and Force High Resolution 1.65 but it didn't helpful to improve the screen layout.
Finally I try the old software “Nydiot Virtual Display 5.02” it solved all the resolution issue on my Samsung i780,
*** You should install the 96dpi respack, if you have any display problem ****
Now I can emulator to 320x240 and 240x320 resolution without dropping the system performance. (use 100% zoom, don’t scaler the screen)
**** You souhld type the "240" by your own in the combine box ****
http://www.nyditot.com/Downloads.htm
wow,... thats a good find.. im downloading now and will post my results here later!
simdao said:
I know many Samsung I780 owner is facing the resolution problem on that 320x320 display.
Some program is not work or identify the wrong resolution on it.
For example, the SlingPlayer mobile is recognized my i780 as 240x240 display and cannot support fullscreen playback with a small windows look like 160x160.
For this reason i tried Tweek2K2 (not support) and Force High Resolution 1.65 but it don’t work.
Finally I try the old software “Nydiot Virtual Display 5.02” it solved all the resolution issue on my Samsung i780,
Now I can emulator to 320x240 and 240x320 resolution without dropping the system performance. (use 100% zoom, don’t scaler the screen)
After install the virtual display, the RealVga is useless, as the Nydiot Virtual display support 320x320 of i780 golden resolution. And i can switch to any resolution without reset the phone.
I am highly recommend the i780 owner to install this software.
http://www.nyditot.com/Downloads.htm
Click to expand...
Click to collapse
Would be interested on how you managed to get 240x320 res. When I tried this software on fresh install no Real VGA nothing I only have opion for 320 or above res. There is no 240 in the drop down list in settings, Also messed up my icons in the program and settings screen.
Anyone else had any luck with this? I think I might have to stick with Real VGA unless I'm doing something wrong.
hi
i tried it extensively .. first i couldnt find the 240 res option and second .. until someone points out the ideal settings i wont be switching from realvgajust yet ! good find none the less !
zohaer21 said:
hi
i tried it extensively .. first i couldnt find the 240 res option and second .. until someone points out the ideal settings i wont be switching from realvgajust yet ! good find none the less !
Click to expand...
Click to collapse
if you type 240 on the combo box you'll get the 240. it supports 240x320 and 320x240. it's usefull in case you have some SW that do not work on default resolution.
Hi,
I want to change the screen resolution of the MHL output because it's not correctly detected maybe because my old monitor or the hdmi to dvi adapter. I wonder there is no native menu to configure the resolution and audio output device or an alternative app... My device is rooted.
So the screen settings are here:
/sys/devices/virtual/graphics/fb1
There is a thread for the evo http://forum.xda-developers.com/showthread.php?t=2090396 but on my One there is no hdmid service and no video_mode.
Available is a file named modes which probably contains all available modes and a file named mode which maybe should contain the current output mode.
modes contains in my case U:640x480p-0 and U:640x480p-94
mode contains nothing if I echo an value into its also empty after that.
The monitor supports a maximum of 1280x720.
Is there someone with deeper android development knowledge who can help in that case?
Thanks,
Patrick
Edit: Maybe I get 640x480px because of HDCP protection problems - is there any solution to get the HDCP back to work on a rooted phone or disable it? In the developer menu there is no setting for that
Hi!
I recently got my hands on an [email protected] monitor, and I would like to know if I could get some benefits of those extra 15Hz and 1440p resolution on the Shield! After all, it has HDMI 2.0 and enough horse power to run [email protected]
It's not to run apps or games at this refresh rate as it might cause some timing issues (games running faster as natively locked at 60Hz) but I'm using Shadow on it. Shadow streams the screen of a virtual PC in the cloud with low latency and resolution/refresh rates variating from between [email protected] to [email protected] That being said, the Shadow client received an image between 144FPS to 60FPS, and accordingly to Shadow's "PC" resolution. Of course you can receive 4K stream on a 1080p TV but that's not where I'm headed to.
I would like to run the Shield at 1440p, at a 75Hz refresh rate... Which is natively not doable but I wanted to know if there was a possibility to edit some files in order to add those options in the settings, or use a third party app... Anything that may help me to achieve it would be awesome!
Cheers!
EDIT: Whoops! Can someone move this to "Shield Android TV Q&A, Help & Troubleshooting"?
Make sure you have developer mode activated.
1. Enable the developer mode by going to Settings > Device preferences > About, scroll to the bottom and tap Build several times.
2. Go back to device preferences, go to the bottom.
There should now be a Developer Options.
3. Click on that.
4. Go down to HDMI and enable "Show all supported modes in custom display modes".
5. Go back to Device Preferences and click on Display & Sound > Advanced display settings > Custom display mode.
It might be there now.
If it's not, then there might be no way to get it, since its not supported
But be aware, as it say under developer options, there might be graphical and ui issues by using a custom resolution in some apps.
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