Having issues seeing GLASS in Fastboot [closed] - google-glass

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I can see my GLASS id in adb and adb reboot-bootloader seems to work. I can not see my device id in fastboot however and fastboot oem unlock hangs on "waiting for device". Pressing the camera button does reboot the device.
Has anyone else had / seen this issue and what have you done to remedy?
I am currently on XE7 with debugging on. I have side-loaded apk's before with no issue via adb. I would like to know of any possible solutions to be able to see my GLASS in fastboot.
My Solution-
I had issues on Win 8 so I swapped over to my OS X install, unplugged all usb peripherals and then ran "./adb reboot bootloader", saw my GLASS in "./fastboot devices" and then ran "./fastboot oem unlock" twice to initiate.
I did not try unplugging all peripherals in win 8. That may help for those that have the same issue on Win 8.

You can use a hardware technique to get your Glass into fastboot. Make sure your device has some charge (15% or more should be sufficient) and follow these steps.
Power down your device by holding the power button for 15 seconds.
Press and hold the camera button. Keep holding it until step 5.
Briefly press the power button.
Wait until the LED solidly illuminates.
Release the camera button.
Now your device should be visible to fastboot. Plug it into a USB port and use fastboot to list devices:
$ fastboot devices
If your device is listed, you can now run other fastboot commands.

This issue on OS X, https://code.google.com/p/google-glass-api/issues/detail?id=243 is still not addressed (please star the issue while there), it still exists post XE8 regardless of how you start fastboot which as noted, times out and will reboot after inactivity of just a few seconds. Part of the problem is that the USB vendorId switches between Google and TI when switching between adb and fastboot (bootloader) modes.
The solution for Windows:
In android-sdk\extras\google\usb_driver\android_winusb.inf
Add to both the [Google.NTamd64] and [Google.NTx86] sections 2 additional lines:
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_9002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9002&REV_0100
Then from ControlPanel->System->Device Manager confirm the VID and PID values with the yellow warning tagged device or “unknown device” - if not the same, edit to match these values.

Related

Change screen resolution without monitor programmatically under Linux? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm writing a GUI program which will be executed along the OS (CentOS 6.6) boots.
The resolution configuration is programmed in the init part of the GUI program, my solution right now is get the resolution sets of the monitor using xrandr and parse the result and set it to one of the candidates, you can choose one of them in the Preferences part of the GUI program later. But xrandr won't work if no monitor is plugged in, right?
If I got no monitor plugged into the box, that means I have no idea what the resolution sets one monitor can provide (at least not from xrandr), so now what I want is, if I turn on the computer, and the GUI program will be executed, after plugging a monitor later, I can see the GUI program already loaded in the monitor.
I mean I want the resolution fixed (1152x864 75.0Hz, for example) in the GUI program init part using some commands or APIs if no monitor plugged?
Does anyone know anything about the available commands or APIs?
I didn't try this with/without a monitor, but it should be possible to "prime" outputs without a display connected with xrandr.
xrandr --newmode "1024x768_2" 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync
to define a new, fixed mode since we can't use EDID with no monitor connected(make sure the name is unique). Also make sure you define a mode any thinkable monitor will be capable displaying (which pretty much limits you to small resolution VESA compatible modes, otherwise you risk damaging old fixed frequency monitors).
xrandr --addmode <output device> 1024x768_2
to assign this mode to a graphics card output
xrandr --output <output device> 1024x768_2
to enable this output.
set this the primary display
xrandr --primary <output device>

ESXi 5.5 crashing under load [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a whitebox dual CPU home server running ESXi 5.5.
I have loaded the server up with a bunch of VM's for learning Microsoft SCCM. I noticed that as soon as one of the guests gets under load, the host will crash with the attached photo (apologies for the quality). Could this be due to a dying CPU? I have noticed that one of the CPU's runs quite a bit hotter than the other.
Usually with CPU overheating the machine would shut down first, however if the temperature inside the case is too hot, something else might be getting affected (e..g memory or video display circuitry).
If you want to diagnose overheating, I can suggest placing a vacuum cleaner hose over the air vent, this will draw much more air than your regular fans. If the system stays up under load with the vacuum cleaner attached, it will be an overheating problem.
Not a programming issue, so I'll close this off and note the resolution I found incase anyone else has the same issue.
Looks like this was a known issue under ESXi 5.X that has to do with the E1000 and E1000e virtual network adapter as per the lines:
#BlueScreen: #PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing#vmkernel#nover+0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx#vmkernel#nover+0x18a
0xnnnnnnnn:[0xnnnnnnnn]IOChain_Resume#vmkernel#nover+0x247
0xnnnnnnnn:[0xnnnnnnnn]PortOutput#vmkernel#nover+0xe3
0xnnnnnnnn:[0xnnnnnnnn]EtherswitchForwardLeafPortsQuick##+0xd6
0xnnnnnnnn:[0xnnnnnnnn]EtherswitchPortDispatch##+0x13bb
0xnnnnnnnn:[0xnnnnnnnn]Port_InputResume#vmkernel#nover+0x146
0xnnnnnnnn:[0xnnnnnnnn]Port_Input_Committed#vmkernel#nover+0x29
0xnnnnnnnn:[0xnnnnnnnn]E1000DevAsyncTx#vmkernel#nover+0x190
0xnnnnnnnn:[0xnnnnnnnn]NetWorldletPerVMCB#vmkernel#nover+0xae
0xnnnnnnnn:[0xnnnnnnnn]WorldletProcessQueue#vmkernel#nover+0x486
Simply remove any adapters using E1000/e and replace with VMXNET3.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059053

Unable to run virtualmachine - vbox amd-v [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I just received my new Thinkpad E545 and would love to set up a new virtual machine for development. After creating the appliance and adding the #! iso for installation, I tried to start up the machine and I get the following error:
Failed to open a session for the virtual machine CrunchBang.
AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
I did some searching and found this thread (https://askubuntu.com/questions/118006/amd-v-is-not-enable-in-virtualbox-in-amd-apu) and followed the advice about enabling virtualization in my bios, but I still get the same results from virtualbox, even after re-installing. After enabling virtualization in the bios, the acceleration tab in vbox is still not available (greyed-out and un-clickable).
Screenshot: http://i.imgur.com/ev3Ty53.png
Relevant laptop specs:
Processor AMD A10-5750M Accelerated Processor (2.5GHz to 3.5GHz, 4MB Cache, 1600MHz) with Radeon HD 8650G Graphics
Operating System Windows 8 64
Operating System Language Windows 8 64 English
Display 15.6W HD AntiGlare, Midnight Black
Graphics AMD Radeon HD 8570M 2GB Discrete Graphics
Memory 16GB PC3-12800 DDR3L SDRAM 1600MHz SODIMM
Keyboard Keyboard with Number Pad - US English
Camera 720p HD Camera
Hard Drive 320GB Hard Disk Drive, 5400rpm
Optical Device DVD Recordable 8x Max Dual Layer
Sorry, that I am so late, but at least someone else will be able to use my advice.
In the latest version of BIOS for this model (have the same one) they mixed up the setting: ENABLING amd-v DISABLES it.
Or this could be some bug of VirtualBox as stated above, however this worked for me.
I've just discovered that having hyper-V installed seems to prevent certain virtualisation features (such as 64 bit) being available to virtualbox. Switching hyper-V off (via add/remove windows features) fixed this for me.
Judging by a sudden spike in forum posts and Stack Overflow questions about this precise error code (VERR_SVM_DISABLED) starting right about when 4.3 came out, I'm willing to bet that this is a legitimate bug in 4.3.
I've triple-checked my BIOS settings and AMD-V is enabled...but I'm still seeing this error in 4.3.10. I never had this problem on 4.2.18.
And this bug report might be good additional reading: https://www.virtualbox.org/ticket/12049
You can simply change the Virtal machine from 64-bit to 32-bit

Hardware Fastboot Boot Method in XE11 not working? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I got stuck on my Glass unit with Launchy crashing (sideloaded the wrong version -_-) in XE11 every time I try to launch an application, including the built-in settings. The problem is for some reason I don't have ADB access anymore and because of Launchy, now can't even reenable Debug mode.
So I am now trying to boot into fastboot mode using the hardware method reference here: Having issues seeing GLASS in Fastboot
But when I keep the camera button pressed and press the power button briefly, the LED is solid for a few seconds and then goes on to blink at very low frequency. No matter how long I seem to keep the camera button pressed, the LED never goes solid.
I've also tried to plug in the unit to my computer and look for it show up in the System Information (the Apple Device Manager equivalent).
Does anyone know if the fastboot hardware method changed in XE11? Or what am I doing wrong?
Thanks in advance,
Charles.
The slow blink you're seeing is Glass in fastboot. Once in fastboot you can verify that it's connected by doing a device list:
$ fastboot devices
If you see output, you'll be able to run other fastboot commands.

Detect other iPhones in a range [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I'm looking to create a mobile app on IOS devices before I started I just needed to check up on one thing. How can I detect other IOS mobile devices within local rage e.g same room, same train, etc..
I want to be able to do it while the phone is locked, so bluetooth wouldn't be a great example as most people have it turned off.
Thanks!
The application has to send its location to the server.
Then the server knows where every devices that shared its location are.
Then your application can ask "who is around?" to your server... and your server calculates (let's suppose within a radius of 2 miles) who is around... and sends back to you.
It doesn't have anything to do with bluetooth. It's done via regular internet.
For other users of your app who want to be discovered you could use Bluetooth LE and the new iBeacon support added in iOS 7. Each user would have to launch your app and give it permission to start "advertising" their presence. However, the range of Bluetooth LE is like 10-20 meters (I forget the exact figure) and that will go down in "RF hostile" environments.
If everybody's connected to the same WiFi network you could use Bonjour.
Another option, as suggested by Wagner, above, is to have the devices send their locations to a central server.