Connect smart phones's display to raspberry pi - Raspberry Pi Accessories

I want to make a mini project, that is gps tracker for my bicycle, i want to connect my mobile's screen for visual approach. Can i connect it to raspberry. Screen and digitizer is of vivo y69. (just screen and touch only)

Dhananjay Jhinkwan said:
I want to make a mini project, that is gps tracker for my bicycle, i want to connect my mobile's screen for visual approach. Can i connect it to raspberry. Screen and digitizer is of vivo y69. (just screen and touch only)
Click to expand...
Click to collapse
try with vnc server and vnc viewer

I need to find a pinout for an older samsung screen for a pi project,any help?

Related

How to create an active Sync connection with a broken display?

Hi Guys,
I have a huge problem with my HTC Touch Pro 2, the display is broken but still working partly. But I can´t activate the Active Sync mode while connecting by USB cable.
So the problem is that i need the contacts, sms and calling history.
The only thing I can connect to, is the device as a hard disk so i have access to the SD card.
Is it some how possible to activate Active Sync without activiation through the display?
May be it could boot together with the device or something like that.
Actually I need the active sync connection for using the Mymobiler Software so that i could run PIMBackup and backup everything.
Or is it somehow possible to backup those things without using active sync.
Please help I really don´t know how to deal with this pitty situation...
tuch screen still works?
Before you broke display when you connect usb on display show popup with device connection options? May be better buy new display. I buy new display and tuch screen and pay for repair totall less than 50 usd.Display, touch screen.
The Touchscreen works only partly, well when i try to connect the device with USB, I see the screen where i can decide which type of connection I´d like to choose but its only partly and the part which is needed for connecting the phone by active sync is still in the part which is broken.
You don't need your screen for setting up a connection do you?
Are you really using active sync of windows mobile centrum. You could try that, it is available on windows vista / 7 if you connect your phone, and then search for an windows update, it should show windows mobile...
Can you get into the start menu, into settings and change the USB connection type to always default to ActiveSync?
Bumer645 said:
The Touchscreen works only partly, well when i try to connect the device with USB, I see the screen where i can decide which type of connection I´d like to choose but its only partly and the part which is needed for connecting the phone by active sync is still in the part which is broken.
Click to expand...
Click to collapse
Then you can try use hardware keyboard keys up/down and enter

[Q] Display Settings - Wireless Display - What works? [SOLVED]

For Nexus 7 (2013) owners:
Lets discuss <any> working methods for using Display Settings, Wireless Display, on Android 4.3+ with Nexus 7 (2013).
1) I want to explore what happens when Wireless display is turned on - and what it takes for wireless displays to be found.
Fine if you use Google Chromecast, or any other devices as wireless displays.
2) What types of data can be pushed/streamed by "wireless display" - e.g. video, audio, VNC, RDA, files, etc?
You get the idea.
-----------
Check this post below. The Netgear PTV3000 works on new Nexus 7 (2013) out of the box.
Bob Smith42 said:
For Nexus 7 (2013) owners:
Lets discuss <any> working methods for using Display Settings, Wireless Display, on Android 4.3+ with Nexus 7 (2013).
1) I want to explore what happens when Wireless display is turned on - and what it takes for wireless displays to be found.
Fine if you use Google Chromecast, or any other devices as wireless displays.
2) What types of data can be pushed/streamed by "wireless display" - e.g. video, audio, VNC, RDA, files, etc?
You get the idea.
Click to expand...
Click to collapse
turned it on, doesnt see either of my 2 chromecast or my tv (not smart or google, just has a ethernet connected which usually allows things to be sent though very limited via dlna)
NyPlaya513 said:
turned it on, doesnt see either of my 2 chromecast or my tv (not smart or google, just has a ethernet connected which usually allows things to be sent though very limited via dlna)
Click to expand...
Click to collapse
Good info. Thanks
I *assume* the feature does *something* in Android 4.3+, and maybe *something* specifically on the Nexus 7 (2013).
Of course this assumption might be wrong, e.g. I'm not sure what Wi-Fi, three dots menu, Wi-Fi Direct accomplishes either. LOL
So please inform us if anyone has knowledge of what happens with Wireless Display turned on, or how to make it work.
I'm assuming it's for Miracast. I don't have any Miracast receivers though.
I was hoping it would work with my Apple TV but when I switch on wireless display, it finds nothing.
gksmithlcw said:
I'm assuming it's for Miracast. I don't have any Miracast receivers though.
Click to expand...
Click to collapse
You are likely correct. I just found this article with some info:
https://en.wikipedia.org/wiki/Miracast
The Wi-Fi Alliance maintains a current list of Miracast-certified devices, both source devices and display devices. The technology and certification is fairly new with the first devices being certified in September 2012. As of January 19, 2013, only just over 100 devices in total were certified.
Nvidia announced support for it in their Tegra 3 platform,[8] and Freescale Semiconductor, Texas Instruments, Qualcomm, Marvell Technology Group and other chip vendors have also announced their plans to support it.[9] Support for Miracast was added to Android in version 4.2 on October 29, 2012.
Both devices (the sender and the receiver) need to be Miracast certified for the technology to work. However, to stream music and movies to a non-certified device there will be Miracast adapters available that plug into HDMI or USB ports.[10]
On 29 October 2012, Google announced that Android version 4.2 (updated version of Jelly Bean) will support the Miracast wireless display standard, and by default will have integrated features for it.[11] As of January 8, 2013, the LG Nexus 4 and Sony's Xperia Z, ZL, T and V officially support the function,[12][13] as does HTC One and Samsung in its Galaxy S III and Galaxy Note II under the moniker AllShare Cast. The Galaxy S4 uses Samsung Link for its implementation.[14]
Microsoft also added support for Miracast in Windows 8.1, and announced this in June 2013. This functionality first became available in the Windows 8.1 Preview, and is available on hardware with supported Miracast drivers from hardware (GPU) manufacturers such as those listed above.
Click to expand...
Click to collapse
And, found this:
Nov 2012
http://phandroid.com/2012/11/19/psa-nexus-7-and-nexus-10-do-not-support-miracast-wireless-display/
PSA: Nexus 7 and Nexus 10 do not support Miracast wireless display
There’s been an ongoing discussion over on Google’s mobile support forum and after much debate, a Googler took the time to weigh in on the issue confirming:
Just wanted to confirm that Nexus 4 is currently our only Nexus device that works with Miracast wireless display on Android 4.2. There was a reference to wireless display on our Help site for Nexus 10, but we’ve since removed that reference. Our apologies for any confusion that may have caused.
Click to expand...
Click to collapse
I'm not sure but this appears to show a Google fail on Miracast (old postings):
http://productforums.google.com/forum/#!topic/mobile/DK-P8Tlnrow[1-25-false]
http://productforums.google.com/forum/#!topic/mobile/DK-P8Tlnrow
Nexus 10, Miracast and Netgear Push2TV 3000
Nexus 4 can see PTV3000, but never connects.
Click to expand...
Click to collapse
-------------------
If anyone has Miracast working on the new Nexus 7 (2013) using <any> method, whether or not including Wireless Display - please post your results here.
Bob Smith42 said:
...
If anyone has Miracast working on the new Nexus 7 (2013) using <any> method, whether or not including Wireless Display - please post your results here.
Click to expand...
Click to collapse
Here is one possible solution using Netgear PTV3000:
Published 07/04/2013 04:17 AM | Updated 07/04/2013 04:19 AM
http://kb.netgear.com/app/answers/detail/a_id/23705
How to connect Google Nexus 4 to PTV3000?
If anyone has the PTV3000 it would be great if you could test on new Nexus 7 (2013) and/or any device running Android 4.3.
The latest firmware update to the PTV3000 is now PTV3000-V2.2.16
From PTV3000_V2.2.16_FW_Release_Notes:
Supported Intel Wireless Display platforms:
Windows 7, Intel Wireless Display V3.1.29.0, Wifi driver V15.1.1
Windows 7, Intel Wireless Display V3.5.41.0, Wif driver V15.3.1
Windows 8 (systems upgraded form Windows 7), Intel Wireless Display V3.5.41.0, Wifi driver V15.3.50
Windows 8 (with Win8 preinstalled), Intel Wireless display, V3.5.41.0, Wifi driver V15.5.7
Windows 8 (with Win8 preinstalled), Intel Wireless display, V4.0.18.0, Wifi driver V15.6.1
Supported Miracast platforms:
Samsung Galaxy S3 (Android 4.1.1 or above)
Samsung Galaxy Note II
Samsung Galaxy Note 10.1
LG Optimus G (Android 4.0.4 or above)
Google Nexus 4 (Android 4.2.1)
Sony Xperia (various models with Android 4.0.4 or above)
Enhancements & Bug Fixes:
Preliminary support for WiDi Gen4 low latency mode. A new option should appear in the WiDi application for prioritizing speed over quality. The “AVSYNC” uboot variable also has new functionality, though it is still currently set to “1”. Change customer_pre_script.sh appropriately if you would like to change the default behavior.
NOTE-1: AVSYNC automatically changes from 1 to 2 when entering “low delay” mode in WiDi, and similarly from 2 to 1 when exiting “low delay” mode.
NOTE-2: Audio is currently not working in low delay mode.
AVSYNC = 0: Disabled.
AVSYNC = 1: Video FW uses Audio PTS for AV sync operation
AVSYNC = 2: Video FW uses STC, System Clock, (ignore audio and decode as fast as possible) for AV sync operation.
AVSYNC = 3: Combined mode. AVSYNC = 1 for DECODER_LATENCY > 75, AVSYNC = 2 in the rest of cases.
Nexus4 Android 4.2.2 compatibility issue – Fixed a rare connection issue related to RTSP.
Improved low power usage for EU region, by suspending to DDR. DC power usage was measured at 290mW. With a 70% efficient A/C adapter it should be around 440mW.
Fixed incorrect setting of decoder latency which was causing video to be early by a couple frames (A/V Sync issue).
Known Issues:
Audio does not work with WiDi 4.x Low Delay mode.
Samsung S3 occasionally does not connect. We are working with QCA on the issue. It appears to be a WiFi driver/firmware bug.
Nexus4 streaming issues:
Phone stops sending data abruptly while streaming high definition video. Air sniffer captures show phone stops sending video packets and goes back to scanning. As result dongle waits for at least 10 seconds for the phone to respond and goes back to ready screen if the phone does not respond.
Samsung Galaxy S3 4.1.1 phone bugs:
Connection will fail if this is done: Start Allshare cast app on phone. Lock the screen and let the phone be idle for 10 minutes. Unlock the screen. Remedy: Toggle WiFi switch on phone settings.
Connection halts after playing a video from Video Player application.
Sony Experia Tsubasa (version 7.0.A.3.185) the mirrored video does not show up until there is activity on the handset screen. Fixed in 9.0.D.1.126.
[Intel] Win8 WiDi 3.5.40.0 application hangs sometimes on reconnection, requiring a laptop re-boot..
Installation Procedure
Push and hold the WPS button on the side of the PTV3000 unit for more than 5 seconds.
PTV3000 goes into firmware update mode. Firmware update procedure shows up on TV screen (also shown below on steps 3 to 7).
Use your PC or mobile device to navigate to http://support.netgear.com/product/PTV3000 to check for and download the latest firmware.
Once you have downloaded the latest firmware zip file, please unzip it and locate the ".sbin" file that it contains.
Using the wireless network manager utility on your device, search for "Push2TV" wireless network name (SSID) and connect.
Open a web browser on your device and type http://192.168.3.1 into the URL bar of the browser.
Follow the steps on the web page to upload the firmware image and complete the installation.
Working Device (Netgear Push2TV PTV3000)
Found a working device. The Netgear Push2TV PTV3000.
Plug the PTV3000 into a mini-USB 5v for power. Connect the HDMI to a TV or monitor. The device displays waiting status.
In new Nexus 7 (2013) go to Settings, Display, Wireless Display. Turn on. Press SEARCH FOR DISPLAYS.
The Push2TV <serial #>-PTV3000 appears in the list of Available Devices. A few seconds after selecting the device the projector shows the entire Nexus 7 (2013) display on the TV or monitor screen.
Note: I took the PTV3000 out of the box and did not apply any firmware updates (yet).
I have lots more questions and things to test. My initial questions are:
1) How does it work with portrait and landscape orientation?
2) Does sound get broadcast to the TV or monitor?
3) Since it works on new Nexus 7 (2013) will it also work on 1st generation Nexus 7 (Android 4.2.1 through 4.3)?
4) How do movies look on the TV?
5) Verify this really Miracast, or is there a second mode on PTV3000?
6) What is the firmware level on PTV3000?
I don't have time to do further tests now. But, ask if you have further questions I can test.
Thanks for the suggestions and help so far... especially gksmithlcw
I tested with this over the weekend and it worked like a dream.
http://www.netgear.com/home/products/hometheater/media-players/PTV3000.aspx
I beg to differ on the PTV 3000
I find it to be useless. It projects an image in the middle of the screen. You could never really watch a movie or anything due to the black bars on the sides. It also does not pass through DTS or Dolby Digital Surround Sound. You are far better off using a media server app like BubbleUPNP to stream media. This is just a little toy. It is light years from being serviceable.
Pancake345 said:
I tested with this over the weekend and it worked like a dream.
http://www.netgear.com/home/products/hometheater/media-players/PTV3000.aspx
Click to expand...
Click to collapse
hi dudes,
i tried widi with new n7 with mk808b android tv stick. it hassame problem like the n4.
Nexus4 streaming issues:
Phone stops sending data abruptly while streaming high definition video. Air sniffer captures show phone stops sending video packets and goes back to scanning. As result dongle waits for at least 10 seconds for the phone to respond and goes back to ready screen if the phone does not respond.
but with bubbleupnp n7 works well to stream movie, pics or music. so with kitkat widi dosent work. maybe with another kernel and rom??
Bob Smith42 said:
Good info. Thanks
I *assume* the feature does *something* in Android 4.3+, and maybe *something* specifically on the Nexus 7 (2013).
Of course this assumption might be wrong, e.g. I'm not sure what Wi-Fi, three dots menu, Wi-Fi Direct accomplishes either. LOL
So please inform us if anyone has knowledge of what happens with Wireless Display turned on, or how to make it work.
Click to expand...
Click to collapse
It scans for Miracast supported device whenit's turn on. If you have a Miracast device connected to the same network, it will show up and you can display your whole screen on the reciever.
Miracast is not Apple's AirPlay and they are totally different. Although they do similar things.
It's also not DLNA. Most of the time files are being sent through DLNA, so you cant see your contacts, messages, homescreen etc. through DLNA. Miracast send your screen feed to the TV.
Miracast need a Miracast sender and reciever to work just like DLNA needs a DLNA server and reciever and AirPlay needs a server and reciever too.
My Nexus 7 (2013) has Wireless Display (I think its Miracast) since 4.3. I think it will work if you have a reciever. I tried it before with Note 2 to my friend's TV which have Miracast support.(I never try it with N7 before because I dont have a reciever). AOSP have support for Miracast as sender since 4.3 (I think)
You need a very fast network to stream smoothly.
The display will change orientation when you rotate your device.
BubbleUPNP is a using DLNA not Miracast.
Miracast still can't work properly in real life.
ALL OF THIS IS ONLY MY THOUGHTS. CORRECT ME IF I'M WRONG
Does anyone else have issues with N7 2013 filling up the screen when connected via miracast? My moto x and N5 fill the screen just fine but the N7 is cropped around the edges.
this device has been working great for me, picked mine up at Wlally-World.
http://www.actiontec.com/303.html#soft
I am also trying to figure out how the miracast feature works or supposed to work with our Nexus 7 2013 model- 5.02 lollipop.
1)My miracast enabled tv (lg model) detects the device.
2)Under cast screen tab in notification panel, tv is not detected but if you enter the more settings options then lg tv is then detected.
3)trying to connect (either from tv menu or nexus menu) results in notification that there is an invitation for connection, then authentication and when the tv shows "miracast is waiting for connection" my nexus stop detecting the lg tv for a few seconds then shows up again but no connection is established. If i insist a couple of times to connect then nexus wifi despite being connected to my home network it cannot connect to the internet.
If someone has an update from miracast feature please post.
cheers

Miracast with PTV3000

Has anyone had their device hooked using Miracast and a PTV3000? I just updated the firmware on the PTV, and I still can not connect. It shows the adapter in the Wireless Display Settings, but seems to "time out" while it is "connecting". Any tips or suggestions?
Firmware update
JuJu142 said:
Has anyone had their device hooked using Miracast and a PTV3000? I just updated the firmware on the PTV, and I still can not connect. It shows the adapter in the Wireless Display Settings, but seems to "time out" while it is "connecting". Any tips or suggestions?
Click to expand...
Click to collapse
Gah just needed to update the firmware and it worked first time. SOLVED.
JuJu142 said:
Gah just needed to update the firmware and it worked first time. SOLVED.
Click to expand...
Click to collapse
I just got a new PTV3000 from BestBuy and it worked out of the box. But, I'm unsure what is my firmware version out of the box.
This works great.
How to check firmware
Bob Smith42 said:
I just got a new PTV3000 from BestBuy and it worked out of the box. But, I'm unsure what is my firmware version out of the box.
This works great.
Click to expand...
Click to collapse
Put your PTV into "Firmware mode" by holding down the button on the side for "At least 5 seconds". You will see it switching to firmware mode on the TV. Once it is in this mode, look at your available wireless signals and you will see one for the PTV3000. Once connected to it with your laptop/tablet/phone, go to 192.168.3.1 in your web browser. In the upper right hand corner it tells you what Firmware version you are using. The latest seems to be 2.2.16.
http://support.netgear.com/product/PTV3000
I cant connect my PTV3000 if FW 2.4.3 is used there, but works with old 2.2.9.
Anybody knows if latest FW beta is available somewhere?
BTW, the same situation with Nvidia Shield - dont work with latest 2.4.3, works w/2.2.9.
Howz gaming with Miracast adapters?
Has anyone tried Gaming with these Push2Tv thingies? I just bought a RocketFish Miracast from Best Buy. While the overall streaming is decent, it's definitely not meant for gaming. I see a lag. I would like to know if anyone has any good experiences in terms of gaming performance with these devices? I tried playing Asphalt 8 and NOVA 3.
Cheers.
drunkaard said:
I cant connect my PTV3000 if FW 2.4.3 is used there, but works with old 2.2.9.
Anybody knows if latest FW beta is available somewhere?
BTW, the same situation with Nvidia Shield - dont work with latest 2.4.3, works w/2.2.9.
Click to expand...
Click to collapse
I just read the release notes from 2.4.3. Wow, they made a bunch of changes.
Netgear likely has an active developer on the PTV3000, so its best to report this problem to Netgear.
I am not familiar with their support. I did a Newegg review once and their product came with a reviewers note. Something about contacting support with any issues. I suspect their support is top notch.
Good luck.
Firmware 2.4.19 released today
Firmware 2.4.19 released today:
http://www.downloads.netgear.com/files/GDC/PTV3000/PTV3000_V2.4.19.zip
Here's the included change log. Good luck
Supported Intel Wireless Display platforms:
Windows 7, Intel Wireless Display V3.1.29.0, Wifi driver V15.1.1
Windows 7, Intel Wireless Display V3.5.41.0, Wif driver V15.3.1
Windows 8 (systems upgraded form Windows 7), Intel Wireless Display V3.5.41.0, Wifi driver V15.3.50
Windows 8 (with Win8 preinstalled), Intel Wireless display, V3.5.41.0, Wifi driver V15.5.7
Windows 8 (with Win8 preinstalled), Intel Wireless display, V4.0.18.0, Wifi driver V15.6.1
Supported Miracast platforms:
Samsung Galaxy S3 (Android 4.1.1 or above)
Samsung Galaxy S4
Samsung Galaxy Note II
Samsung Galaxy Note 10.1
LG Optimus G (Android 4.0.4 or above)
Google Nexus 4 (Android 4.2.1)
Sony Xperia (various models with Android 4.0.4 or above)
Enhancements & Bug Fixes:
Fixed EU power-save mode that device does not wake up after entering power-save mode.
Updated the RTSP User Agent to ME29 so new Samsung phones will project at 1080p.
Blurry text when projecting for Sony Mobile phones.
AP mode does not turn on properly when in FW update mode.
Prevent pushbutton from initiating p2p pairing if coming out of low power mode. It just wakes up now.
[MS Windows Blue] UI gets stuck if PC left idle for too long – Only added watchdog to reboot the system if key any key applications die unexpectedly.
[MS Windows Blue] PTV3000 is not responsive which leads to be disconnect.
[Widi Gen4] Blank/black screen with mouse only.
[Widi Gen3] Black screen during HDMI hot plug after WiDi connection is established.
(Heavy WiFi Traffic) Lenovo x220, WiDi 3.0.13, 4.0.17 and v2.4.1(r14548) cannot connect.
Added Miracast failed cases (not tested yet):
6.1.2(P-SnUT operating as a Group Owner accepts a WFD Session with a Reference Source)
6.1.3(P-SnUT starts a WFD Session with a Source that is operating as an Autonomous GO)."
Keep the credential(s) even after changing any of the settings on web UI.
[#481 r14862 & V2.4.14] PTV locks up when disconnecting Windows.blue session from laptop.
NON-HDCP FW shows black screen when WiDi mirroring starts. This FW is for engineering verificaiton purposes only.
Enable Miracast certificaiton, test case 6.1.17a.
[Microsoft Windows.blue] Dongle is dead after prolonged use.
Integrate QCA 3.2.1.127
SF 1157749: ar9374 Block Ack flood during Nexus 4 4.2.2 streaming
SF 1176921: ar9374 Inconsistency between probe response (20Mhz) and capability beaconed (20Mhz & 40Mhz)
SF 1190765: ar9374 fails to send invitation response.
MSFT IOT fixes (no single channel scan).
Other P2P mobile phone IOT fixes.B29".
[#234, #335, #435, #436 Excessive frame repeats and skips, Excessive latency, and A/V sync.] Tested at Intel KPI lab and passed all Playback Quality, Latency, and A/V Sync tests for Speed and Quality modes.
[Widi gen4] Connection drop within 4 hours. Deauth sent from NB. WiDi log and sniffer trace sent to Intel.
[HTC new one] TV displays "WiFi connection closed" screen instead of mirroring. Changes for this have been in r14767.
[Sony Xperia Z] Sony Odin 10.3.A.0.423 crashes supplicant on reconnect.
Set L2SD off as default for all future releases.
Fixed issue of Connecting icon animation stays on screen after WiDi connection.
Fixed issue of PTV3000 outputs low resolution to Sharp LC-19DV24U.
Fixed HMDI hot plug issue.
Fixed no HDMI signal if no HDMI cable is plugged in upon power up.
[Windows.blue] "Display correct error connect/disconnect messaging on PTV.
To access additional debug capabilities, the following actions need to be taken:
For connection issues, add extra handling to rtspfailedgui.sh and disconnectedgui.sh
For HDCP, add the uboot variable DISPLAY_HDCP_STATUS=1. The scripts displayHdcpStatus.sh, connectinggui.sh and rtspfailedgui.sh
also are modified.
For displaying packet drops, add the uboot variable DISPLAY_PKTDROP_SEQERRROR=1. The script displayPktDropSeqErrStatus.sh
displays the UI."
[Widi gen3] After entering wrong PIN, TV screen shows new PIN but WiDi app still displays "connecting" message.
[Widi gen4] Failing to connect with BCM4352 (2 cases)… Note: Discovery issue is still open. Now tracked by #448.
[AV quality] Excessive frame repeats and skips (possibly, needs KPI testing). Improved datapath such that it takes about 55ms less time to decode large WiDi I-frames in Quality mode.
Blank or Black Screen.
Cleaned up pushbutton disconnect so that it works properly for Legacy Widi laptop connections, as well as cleanly sends an RTSP TEARDOWN for Miracast devices.
All settings are kept with FW update (except the device profile).
All settings are erased when doing reset-to-factory default.
Incorporate final string translations.
New UI animation images without line below text.
When pushing reset button in Settings mode, successfully reset to factory default settings.
Connection time is too long.
No Audio when switched to Low Delay Mode.
No Video while 1366x768 streaming (Calpella Laptop).
Fixed issue with incorrect UserAgent parsing for Samsung Galaxy S3. This enables all movie mode features properly for that phone.
HDCP Authenication drops after connection.
Black screen during HDMI hot plug after WiDi connection is established.
Ensured UI goes to EDID resolution upon disconnect.
Fixed issue with incorrect aspect ratio correction being applied after connection.
UI animation enabled by default and without the respective user setting in web UI.
The "Browse" button in web UI customized for all languages.
Do not reset language to factory default language after user updates FW.
Firmware Update Procedure:
Step 1: Press and hold the button on the side of the Push2TV adapter for 7 seconds, to put your device into firmware update mode.
Step 2: Use your PC or mobile device and navigate to http://support.netgear.com/product/ptv3000/ to download the newest firmware.
Step 3: Once you have downloaded the latest firmware zip file, please unzip it, and locate the ".sbin" file that it contains.
Step 4: Using the wireless network manager utility on your device, search for Push2TV wireless network name (SSID) and connect.
Step 5: Open a web browser on your device, and type http://192.168.3.1 into the URL bar of the browser.
Step 6: Follow the steps on the web page to upload the firmware ".sbin" file and complete the update.
Black Bars and No Surround Sound
I am having very little success using the PTV3000 with my Nexus 7 2013, Denon AVR-4311 receiver, and Panasonic Viera ST30 TV. I am able to connect to device and share the screen. However, it does not pass thru 5.1 surround sound to my receiver, and there are black bars on the top and bottom and on the sides of the screen, making it impossible to watch movies.
I have searched but found anything about that option in firmware settings, which has values 0,1,2,..15 or something, what for is that?
Cannot perform Step 5 open 192.168.3.1
When I try to open 192.168.3.1 I get a page cannot be displayed. I tried to ping that IP from a workstation on my network and that is unsuccessful too. I am still able to mirror my Kindle HDX on the current firmware.
dabgeek said:
When I try to open 192.168.3.1 I get a page cannot be displayed. I tried to ping that IP from a workstation on my network and that is unsuccessful too. I am still able to mirror my Kindle HDX on the current firmware.
Click to expand...
Click to collapse
Did you press the button first and then wirelessly connect to the device?

HP Elite X3 Help Needed

I have been conducting a review of the new HP X3 for my job, and there are two major "problems/things" are driving me nuts. I am a 28 year application developer, I have built my own Windows CE environments since PocketPC 2003 and my daily driver is a unlocked 950XL, so I am not some noob. But at this point this device has me stumped on Microsoft or HP motives with this device.
Just an overview, the device comes with a nice continuum dock with two USB ports and a USB C port, so basically three in total. It also has a display port as well, which to most people will require a DVI converter. As a developer remote desktop was my first stop. This option does work, but you quickly find out the that you don't like the mouse speed or the pointer size isn't exactly what you want as far as the overall RDP session. OK, so you go to settings and guess what. One option, mouse button left or right...Really HP and/or Microsoft????? At least give me some sort of mouse speed control. I was able to write a complete UWP application using Blend and Visual Studio through remote desktop, but if it had not been for the testing of the device I would have ended up pulling out my laptop and had the app done in 1/4 the time. So please expose some mouse settings, I have been through the Image Design Control tool for the provisioning and their WAP files from the ffu images but can not find the settings that I could configure to change this. My 950XL on the same HP dock with the same mouse and keyboard works 1000% times better, so it is something they have in a setting, hopefully not in a build.
Next I try and get the great dock that comes with the device to sync with a desktop. I have not tried this with the HD-500, so maybe this isn't fair. But as far as I can tell you can not have your device sync to a workstation when it is docked. I tried connecting the USB-C to a normal USB port on the desktop (both USB3 and USB2) and the device gets the dialog on the device saying USB error. So I try a straight through normal USB male to male cable, same error. Very annoying thing at first, but for a developer it gets worse.
So you end up taking the device off the dock and connect it using a UBS-C to a USB3 cable directly to the desktop. Finally the device is seen by the OS and Visual Studio. Things are looking up, workstation makes the ding, you can browse the files, visual studio shows the device and you think everything is ready. You go back to visual studio and set the break points in the code and press debug. The device turned off when you first sit it down but at first you don't even think about it. So you pick the device up get the screen running so visual studio starts trying to connect for the debugging session. Your humming along and visual studio debugger hits a null exception error and breaks. You sit down the phone and turn to visual studio to check out which object only to find out the phone turned off and the error along with the debug session had been cut off. I really don't understand whether is the light sensor or accelerator that HP has set here but it has to be a setting. My 950XL does not exhibit this behavior. I can see exposing a setting such as this as an option, but I cannot find the setting controlling this behavior if it is an option or something HP is enforcing for some unknown reason.
So if anyone can point me in the direction to the following options and/or settings it would be helpful.
1. Where are the mouse pointer speed settings for USB connect mouse including when using Continuum. (Registry settings or visual don't care)
2. On the HP X3 does anyone know how to turn off the setting to turn off when sat down. Trying to figure out if this is the black out of light or when it is acceleration setting.
Hi to prevent the phone to turn off you must turn off the double tap feature.
acuatico69 said:
Hi to prevent the phone to turn off you must turn off the double tap feature.
Click to expand...
Click to collapse
I think there was also a new FW update to aid in the screen timeout while docked.
geekempire said:
I have been conducting a review of the new HP X3 for my job, and there are two major "problems/things" are driving me nuts. I am a 28 year application developer, I have built my own Windows CE environments since PocketPC 2003 and my daily driver is a unlocked 950XL, so I am not some noob. But at this point this device has me stumped on Microsoft or HP motives with this device.
Just an overview, the device comes with a nice continuum dock with two USB ports and a USB C port, so basically three in total. It also has a display port as well, which to most people will require a DVI converter. As a developer remote desktop was my first stop. This option does work, but you quickly find out the that you don't like the mouse speed or the pointer size isn't exactly what you want as far as the overall RDP session. OK, so you go to settings and guess what. One option, mouse button left or right...Really HP and/or Microsoft????? At least give me some sort of mouse speed control. I was able to write a complete UWP application using Blend and Visual Studio through remote desktop, but if it had not been for the testing of the device I would have ended up pulling out my laptop and had the app done in 1/4 the time. So please expose some mouse settings, I have been through the Image Design Control tool for the provisioning and their WAP files from the ffu images but can not find the settings that I could configure to change this. My 950XL on the same HP dock with the same mouse and keyboard works 1000% times better, so it is something they have in a setting, hopefully not in a build.
Next I try and get the great dock that comes with the device to sync with a desktop. I have not tried this with the HD-500, so maybe this isn't fair. But as far as I can tell you can not have your device sync to a workstation when it is docked. I tried connecting the USB-C to a normal USB port on the desktop (both USB3 and USB2) and the device gets the dialog on the device saying USB error. So I try a straight through normal USB male to male cable, same error. Very annoying thing at first, but for a developer it gets worse.
So you end up taking the device off the dock and connect it using a UBS-C to a USB3 cable directly to the desktop. Finally the device is seen by the OS and Visual Studio. Things are looking up, workstation makes the ding, you can browse the files, visual studio shows the device and you think everything is ready. You go back to visual studio and set the break points in the code and press debug. The device turned off when you first sit it down but at first you don't even think about it. So you pick the device up get the screen running so visual studio starts trying to connect for the debugging session. Your humming along and visual studio debugger hits a null exception error and breaks. You sit down the phone and turn to visual studio to check out which object only to find out the phone turned off and the error along with the debug session had been cut off. I really don't understand whether is the light sensor or accelerator that HP has set here but it has to be a setting. My 950XL does not exhibit this behavior. I can see exposing a setting such as this as an option, but I cannot find the setting controlling this behavior if it is an option or something HP is enforcing for some unknown reason.
So if anyone can point me in the direction to the following options and/or settings it would be helpful.
1. Where are the mouse pointer speed settings for USB connect mouse including when using Continuum. (Registry settings or visual don't care)
2. On the HP X3 does anyone know how to turn off the setting to turn off when sat down. Trying to figure out if this is the black out of light or when it is acceleration setting.
Click to expand...
Click to collapse
hello
try using Bluetooth mouse
I'm using the following setup:
hp pro display p2012 over Display port to HDMI cable with DVI to HDMI adapter
Bluetooth mouse and keyboard
they work perfectly

How to use my moto z2 force as a pc screen?

Recently I see Asus is producing UX580 which has a touch screen as mouse pad. This is exactly what I want my android phone to do, but don't know how.
As I have used miracast a lot between my PCs, I know for sure this is already technically possible. It should be like this: use Android phone as miracast receiver, pc connects to the phone to use it as an extra screen, pc receives the touch moves as operating commands.
All we need is just a software to activate the phone as a miracast receiver if I am not wrong?

Categories

Resources