Profile cover photo
Profile photo
Thibaud Lopez Schneider
Thibaud's posts

Post has attachment

Post has attachment

Post has attachment

Post has attachment
I am having difficulties connecting my Lenovo Phab 2 Pro with ADB to my Windows 7 Pro. I bought the phone new; I updated Android to the latest version 6.0.1; it has software version Lenovo PB2-690Y_161214; I enabled Developer mode and USB debugging; I rebooted the phone; and I am using the USB cable from the box. After some automatic detection and installation of the drivers, the Device Manager says "This device cannot start. (Code 10)"; I tried several combinations of delete the drivers and un-plug/re-plug the cable; I even updated the driver with the USB driver of the Android SDK. I was hoping to develop for Tango with Unity, but Unity and the command adb devices do not find the device. Are there any special steps to install the driver? Here are some screenshots of what I have. Any help is appreciated. Thank you.
8 Photos - View album

Post has attachment
I finally made a video on how to install Ubuntu 16.04 LTS on Chromebook Pixel 2013: beginner's level, wipe it all, install with full disk encryption, and test all drivers. (This is not crouton.)

I hope it helps whomever wants to make the jump but was afraid to.

Post has attachment

Post has attachment
The dreadful moment happened: I seem to have accidentally wiped my Chromebook Pixel Developer mode at boot while I was cleaning the keyboard with a cloth.

I have a Chromebook Pixel 2013 in developer mode with Ubuntu 16.04 that I just installed a couple of weeks ago, with full disk encryption. I've always been very careful at boot to never press the combination of wipe keys, I've always been very careful.

A couple of hours ago, I suspended Ubuntu and cleaned the screen and the keyboard with a cloth.

I must have accidentally pressed the combination of wipe keys: power button, space bar, and ENTER. I don't remember. Because now when I turn on the laptop it only shows "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card".

Before, it would show the developer mode boot screen, and I would press CTRL+L for legacy boot, and it would go into SeaBIOS and the full disk decryption.

Now neither CTRL+D (disk boot) CTRL+L (legacy boot) nor CTRL+U (USB boot) do anything. The TAB key shows "recovery_reason: No bootable disk found. dev_boot_usb: 0. dev_boot_legacy: 0. dev_boot_signed_only: 0" And at some point CTRL+D showed some screen to "Turn OS verification OFF"; I can't reproduce that one.

Did I really press the combinations of keys and wiped it all? Is there another possibility?

I had backed up my data so I'm good there. I just don't want to have to re-install everything again, and mostly I don't want to accidentally wipe it again.
2 Photos - View album

I am running the latest Ubuntu Desktop 16.04 LTS Live USB on my Chromebook Pixel 2013 in preparation to install it.

The display, wifi, keyboard, touchscreen, audio, and video work correctly out of the box. Even the F-keys are mapped, and even closing the lid makes it go to sleep; those were an issue before.

However, the touchpad does not work, no mouse; so meanwhile I am using the touchscreen. What are the latest instructions to setup the touchpad? I have been looking all over the Internet, but I only find bundled instructions for multiple drivers which now work correctly, and for an old kernel.

I also found some people providing corrections for the Home/End/PageUp/PageDown keys, and corrections for the edges/palm of the touchpad. I will try those afterwards.

Anything else I should think of?

Thank you.

Update #45 Jul 23 2015 "[Rick:] 30 years ago the Amiga was launched. This weekend, the anniversary is being celebrated in castAR’s hometown at the Computer History Museum. Coincidentally, Jeri and I also started Technical Illusions 30 months ago. We were asked to participate in the event by showing castAR, so Jeri and myself will be spending our weekend showing something unique on the glasses."

Update #44 Jul 17 2015 "A Tale of Two Volumes - When setting up our Kickstarter campaign, we had two distinct groups of glasses. The first set of glasses were made available earlier in the process, but at a higher price and low volume. The second set of glasses was to be delivered later at a cheaper price. We wanted to detail some of the choices and factors that separates the two sets of glasses out, what we’ve learned by creating the early dev glasses, and some of the improvements to processes, procedures, production, and parts going through."
Wait while more posts are being loaded