Installed VMWare Remote Console 10.0.4 (latest as of writing this) on MacOS Mojave 10.14.3. installation went well, but running the app, nothing is shown on the Mac. seen some unanswered similar questions on VMWare forum here and added my question here. Have anyone seen the same issue and have a solution?
I may have sound something - when i go to a vSphere VM, i have two options: 'Launch Web Console' or 'Launch Remote Console' - if i click the latter, i get the application to open with the UI displaying as it should. so, unlike VMWare Horizon, Player and others, here it seems you need to connect to the VM first via browser, to open the desktop client. weird choice from VMware in my mind, but still some solution. See image below
Related
My GEE2 is currently running on version OPM1.190831.007, and I can't find a way to get a more recent version running. I've tried the flashing tool and manual flashing, but both methods came with their own issues. I'll give them below:
Flashing tool: I get either a 'device already in use' connection error or the device is offline. This besides the more common message that the flashing tool has some problems on windows sometimes, and that I should try refreshing the webpage.
Manual flashing: once I have given the adb reboot-bootloader command, the fastboot devices command won't recognize the device (listed as ???????? instead of the device name/number) or it will be offline. As a result, the commands that should be given afterwards according to the Readme file don't work.
I have the adb debugger from the Android Studio SDK platform-tools folder, so I updated the driver software of the GEE2 with the use of that folder initially. Afterwards I tried installing other adb software as well but that didn't help either.
I have also tried a couple of the simpler solutions, as unplugging and plugging, refreshing the site, using another computer, using another internet browser, deinstallation of the driver software, a factory reset of the GEE2, installing less recent firmware instead of the latest. None of these things changed the outcome.
Any suggestions would be highly appreciated!
Firstly, check if you have enabled developer options on EE2.
I had a hard time flashing it on Windows due to driver issues. My Android studio or ADB had no problem deploying apps to EE2, but the fastboot never worked. I ended up flashing it on a Mac using brew installed adb.
I had similar issues with Windows, the driver, and fastboot not working using the flash tool. I was told by support to use a USB 2.0 port. I used a Mac with USB 2.0 to flash it and it was successful.
There's a flaw with the instructions on google glass firmware update - for Windows only, there's a USB driver you need that is glass-specific which isn't mentioned anywhere on the page. I can't even find the page where I found that out right now and I know what I'm looking for. Which isn't very helpful.
The best I can give you is a link to this installer tool might sort out your problem judging this reddit post.
If that doesn't work, use a mac or linux.
I have red mi note 4 devices after update device with miui version 9 attempt to enable installation via application via USB, it doesn't work and shows "This device is temporarily restricted". The solution I found didn't work.
Without that feature, I can't develop an application.
Model redmi note 4
miui version: 9.0.5.0
I faced the same issue. I was not able to enable Install Via USB option, however, I found a solution that actually worked.
Here are the steps to enable it.
Install PlexVPN app on your mobile phone
Open PlexVPN then set VPN to China (e.g China-Shanghai) and connect
Go to Developer Options and enable Install Via USB option
Enjoy :)
For me, the only solution that worked is to toggle on OEM unlocking
Only then I could enable Install via USB and other options that previously restricted
yes the solution is VPN you need chinese serevr for proxy , should is buy vpn or i can do it for free , follow the links below
i faced the problem before so here is answer
Each time I launch WAMP on my Win7x64, I see some graphical bugs in windows ui, such as grayed menu on right-click window (anywhere), menus in app (Notepad++ for example) and so on.
The only way to restaure my initial configuration is to stop server and reboot pc... It's not really important but i can't find out why this issue is still there, even after having reinstall several versions..
Search and researches led to nowhere... am I the only one, THE CHOSEN ONE?
THX !
By the way my current wamp conf is : Apache 2.4.9, php 5.5.12, MySQl 5.6.17..
I installed VM ware recently now whenever i try to power on VMware it shows the below message:
"Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, adjust the additional memory settings to allow more virtual machine memory to be swapped.
If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines."
I am not able to change the memory setting .It just shows an option to resume the virtual machine, All other options are disabled. I have by mistake increased the VM ware memory in run time .Could any one help?
For anyone who encountered this problem recently, please visit this link:
http://blogs.vmware.com/workstation/2014/10/workstation-10-issue-recent-microsoft-windows-8-1-update.html
Go to Control Panel -> Programs -> Programs and Features,then uninstall the Windows 8.1 Update KB2995388 may help
--* Edit *--
The Optional Update for Windows 8.1 for x64-based Systems (KB2995388) published on 10/13/2014 may causes issues when running VMware Workstation on a Windows 8.1 host with it installed.
And a message saying "not enough physical memory" will be reported.
Because the VMware team hasn't fix the issue, you can follow steps below to uninstall the update to boot your virtual machine:
1.Go to Control Panel -> Programs -> Programs and Features, then select View installed updates at the top left corner.
2.Scroll down the list and locate Update for Microsoft Windows (KB2995388), select it and click on the Uninstall button.
3.Follow the steps to finish the uninstallation.
In the comment list, someone also reported a fix from VMware communities:
Open the config.ini file located at C:\ProgramData\VMware\VMware Workstation.
Add this line:
vmmon.disableHostParameters = "TRUE"
Save & reboot your PC
It sounds like your VM machine is in a suspended state. What you need to do is follow the steps outlined here in this help ticket. Do these steps while vmware is not running. And once you do this, start vmware again and then you should be able to edit your memory settings.
Run it in Administrator mode in Windows 8.1. Probably a Windows Update... Deleting the suspended state didn't work for me.
Before proceeding with any alternative solutions/workarounds, please always double ensure you have updated to the latest version of VMWare Player.
My machine was running VMWare Player, Version 6.0.*, and this issue was occurring (my local machine's Operating System is Windows 8.1). The relevant error(s) were resolved after updating to the latest build currently available, VMWare Player, Version 7.0 (Please note: I did not have to remove/uninstall any Windows Updates/Features)
Just spent a few hours trying to get my VMware to boot. Power flickered off enough to shut down the computer while the VMware was in suspension and recieved this message.
Make sure the update isn't installed. Make sure to follow the accepted answer. What made it work for me was:
Right click on your development name tab
Click on "Manage" and then "Clean up disk"
It worked for me. I'm not sure why it worked, but it was able to fix my issue. Didn't need to restart.
Follow these steps:
Close the VMware.
Select VMware icon.
Run VMware as Administrator.
I've created a small Glass app and am trying to help someone else side load the .apk file directly on on their Glass as part of internal testing. I had them install the Eclipse + ADT Bundle, run the SDK Manager, etc (i.e. the basic instructions from here). They verified that the Google USB driver does show up in the SDK Manager.
With the device plugged in, running "adb wait-for-device" hangs. So it doesn't appear device communication is working. The device also does not show up in DDMS in Eclipse.
They verified that USB debugging is enabled on the Glass itself under settings.
I also tried having them follow the instructions here but this also did not help. They are able to see the Glass removable storage device in windows.
Any suggestions on what else to try? I do recall that with my Glass device at one point I put it on and it asked me if I wanted to allow debugging from the computer where it was plugged in. I'm not sure if this could be a roadblock here or not but I'm also not sure how to get to that prompt.
Once you get the correct values into android_winusb.inf it works fine, see
Google Glass ADB devices doesn't find. OMAP4430 driver not installed (can't find it!)
Here's an example on a Win7 box:
(edited to include screen capture)
The easiest workaround is to find a Mac, Chromebook or Linux computer. Windows with ADB and Glass is nothing but pain.