I was having issues with my Ducky Shine 5 wiping it’s settings with ERP s4+5 set in my bios, after finally managing to hunt down someone from Ducky (they really don’t like to answer emails which is ridiculous considering the price of these!) I got a firmware update from the manufacturers which fixes the issue. Download below.
Category Archives: Uncategorized
Remote Play PC Alpha has been released! You can now purchase from the downloads section of the forums:
A full static build of ffmpeg-2.7.1 for Visual Studio can be found at the link below including the source. Libraries are in their respective folders and named *.a which can be included directly in a visual studio project.
New video on Remote Play for PC app showing audio and controls working.
Along side my modifications of the Android Remote Play app I’ve been busy working on my own implementation on PC (and other platforms in the future). It’s taken a while to get this far but I’ve successfully got video streaming working
Next I’ll be working on enabling audio and keyboard/mouse controls, I’ll be uploading more videos as the project progresses.
I couldn’t find a reliable tutorial on installing Android for the latest Pandaboard so after much trial and error here is mine, all binaries are provided so it should be extremely simple to get setup and running.
1. Pandaboard ES rev B3
2. SD card
3. Linux distro
$ sudo add-apt-repository ppa:linaro-maintainers/tools $ sudo apt-get update $ sudo apt-get install linaro-image-tools
Download boot.tar.bz2 system.tar.bz2 userdata.tar.bz2 from https://www.dropbox.com/sh/x6kgwqzfhioq8ex/AADl7dOH6SaBWSsDymNwmXMla?dl=0
Insert an SD card
Look for a line that looks like the following at the end of the log
[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
For me the device showed as mmcblk0.
Then simply run this command replacing the “sdc” with your device name.
sudo linaro-android-media-create --mmc /dev/sdc --dev panda --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2
Once completed, remove the SD card from the device writer and plug it into the board and boot.
I haven’t been able to work on RPFTool for quite a while due to lack of free time and I don’t see myself spending much time on it in the future so I’ve decided to go open source and release it to the public!
This was my first large project so to be honest its a bit of a mess, I also started adding GTA V support but didn’t get round to finishing it so for those wanting to build it themselves I suggest commenting all that code out.
Note: You’ll need a copy of devexpress to build it as the interface relies quite heavily on it.
The forums are now back online, should be a fair bit faster than before too.
working out the kinks at the moment – http://4pda.ru/forum/index.php?showtopic=346896&st=7020#entry26397221
I’ve managed to get a working grub shell on the W700 with the setup_var command (this was a feat it itself as grub doesn’t like HD4000’s, download in instructions.) so I’ve updated the instructions below, I haven’t managed to fully remove the throttling yet so I encourage people to download the list of ID’s and mess around with the settings.
Successful managed to change turbo watts, updated commands soon…
Hit another road block, it seems that although I can change the max turbo watts and the turbo time from 28 seconds up to the maximum of 128 seconds (the Intel tool shows this) the 10 watt limit still kicks in after ~30 seconds.
For those following this post I’m waiting on my tablet returning from a repair before I can continue investigating the cause of the throttle. Don’t have an official date but should hopefully be within a week or 2.
Before you we go any further I am not responsible for any damages this may cause, proceed at your own risk.
If something does go wrong and you screw up your bios chances are you should be able to recover it with the following process. Before going through with a full bios flash, if you can still access the normal bios (shutdown then Windows button + power) I’d advise trying the ‘reset defaults’ option.
- Format a usb stick to fat32
- Download the 2.07 firmware HERE
- Copy it to the root of the newly formatted USB stick
- Fully power off and unplug your W700
- attach the USB stick then hold down the Windows button + volume up + Power
- As soon as you see the screen turn on release all of the buttons, you should now be left with just a blank screen
- Your device should now be reading the usb stick and flashing the bios, leave it for a good 10 minutes.
- Power off your device, if the power button doesn’t work get a pin and use the reset button found on the bottom of the device.
- Power back on.
Removing the throttle
1. Take USB stick and format to FAT32
2. Download the archive here – DOWNLOAD
3. Extract to the root of the USB stick
4. Restart and enter BIOS setup.
5. Make sure you have following values:
UEFI mode (NOT legacy mode)
Secure Boot: Disable (you’ll need to have a bios superuser/admin password set up first)
USB stick as the first boot device
6. reboot and you should be presented with the grub shell, once here enter the setup_var commands with the format ‘setup_var [VarStore] [Value]’
7. Reboot and check for throttle. If you managed to remove the throttling leave a comment below with the commands used.
Some more info…
So for those with a bit more technical knowledge who want to know more, here’s an brief explanation of what we’re trying to do here.
So when we boot off of the usb stick using BOOTX64.efi we’re actually botting into the EFI shell, from here we’re adjusting settings stored by the bios. Whenever you change a setting in the bios normally that configuration will get stored against an ID, for a full list of ID’s pulled from the W700 bios I’ve uploaded them HERE (if there’s a lot of random symbols make sure you’re viewing it in UTF-8). Using These ID’s we can adjust any stored setting using the following command format
setup_var [VarStore] [Value]
For example if we look at the ‘ISCT Configuration’ section we can see it has a VarStore value of ‘0x32e’ with an option of 2 values ‘1’ or ‘0’. The values always need to be entered in hex so to enable this setting we would use
setup_var 0x32e 0x1
and the following to disable
setup_var 0x32e 0x0