Related
I am wondering if anyone knows of any way or if someone is working on a way to get ICS or JB to boot on a home-built PC? My PC is AMD 64, 8G RAM, etc. I have seen some instructions online, but they failed to mention that you must have a certain laptop or tablet. I would like to be able to tri-boot Android and run it whenever I feel like (probably use it the most). Thank you for any input.
Massive overkill. Why not simply run VMware and stick Android in a virtual machine?
android-x86
There is a project called "android-x86" - this might help you.
I tried android-x86. That is where I found out after several failures that you can only use a handful of specific Lenovo devices to boot into Android. Apparently there is a way to use Android 1.6, but who wants that.
As far as the overkill thing. Well I did build it as a workhorse PC. And I could run VM. But I would rather boot into it. I think it would be great for average tasks.
How difficult would it be to make it work for myself from AOSP?
Kernel build, hardware support etc. That's why I just run a VM for mime when I want to play. Also means I can access all my synched days such as SMS messages easily on my PC.
Sent from the darkest corner of my mind.
There is a particular web site I was not able to connect to from my android devices but connected just fine from my windows PCs/laptops.
After some playing around with wireshark and Shark for Root, I saaw the server never answered the SYN from the android clients. Comparing the SYN packets between the windows 7 and android stacks, the only differences were in the options, and I was able to determine that either the server, or more likely a router/firewall in the path is choking on the TCP Timestamps option (option #8)
I if I temporarily disable the timestamps option echo 0 > /proc/sys/net/ipv4/tcp_timestamps, the android device connects just fine.
Once I identified the problem I found at least one thread showing that some servers still don't handle this 20 year old RFC properly (see http://serverfault.com/questions/23...-a-syn-ack-packet-in-response-to-a-syn-packet, I didn't have to muck with windows scaling in my case).
writing to /proc/sys is only a temporary solution though. it gets cleared when the device reboots.
Under linux, I would modify /etc/sysctl.conf to make the change permanent, but it doesn't look like android uses the sysctl.conf system (at least it's not present on any of my devices, custom ROMs or stock)
what's the proper way to disable the Timestamps option permanently?
I run SmoothROM on my nexus 7 and it has support for init.d, so at least one workaround was to create a /data/lcoal/userinit.sh that writes 0 to /proc/sys/net/ipv4/tcp_timestamps at every boot.
ParanoidAndoird on my Galaxy Nexus seems to also support init.d (edit: yup it does)
My main phone, a Nexus 4, is running 4.2.2 stock (albeit rooted) and doesn't seem to support init.d....
looks like installing busybox will install sysctl, so it might be an avenue to explore, although it's getting too late for me to try today.
I also saw mention somewhere of the later versions of busybox implementing init.d?
install-recovery.sh appears to be run at each boot, so I can add my tweak to that file on my rooted Nexus 4, or I could implemnt the full init.d solution described in this thread, although it's overkill for me: http://forum.xda-developers.com/showthread.php?t=1933849
Bottom line is maybe it's klugy, maybe it's the only way, but I got the tmestamps option disabled on all my android devices and can now connect flawlessly.
Stuff that doesn't work: 3G/LTE, accelerometer, GPS, camera, and maybe some other stuff that I'm not remembering
Stuff that does work: GPU (full OpenGL 4.5 and Vulkan), sound, USB device and host, WiFi, Bluetooth, touchscreen (including stylus), SD/USB install
Downloads:
Linux4Tegra R24.1 beta (mirror) (updated on February 18th 2016)
Linux4Tegra R23.1 (mirror) (updated on November 21st 2015)
Linux4Tegra R21.4 (mirror) (updated on July 21st 2015)
Linux4Tegra R21.3 (mirror) (updated on March 9th 2015)
Installation instructions:
Install MultiROM (+ TWRP + touch support + patched kernel)
Download Linux4Tegra and install it through TWRP (Advanced -> MultiROM -> Add ROM)
Tips/notes:
To enable the on-screen keyboard during setup or login, press the blue icon in the corner and select on-screen keyboard from the menu that appears.
To enable the on-screen keyboard on desktop, run Onboard.
If your touch input becomes misaligned, install and run xinput-calibrator.
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Gnurou said:
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Click to expand...
Click to collapse
I've tried L4T 21.2, 19.3 and Lollipop. All of them need a small kernel patch (which might break HDMI, I have no idea) for the graphics to work, but apart from that they should all work fine for the most part.
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Edit: this actually isn't needed, I was just using the wrong cmdline
Getting Started
THESE INSTRUCTIONS ARE OUTDATED. CONSIDER USING THE PREBUILT INSTALLER FROM THE MAIN POST INSTEAD!
You need a computer with Linux installed and some free space (I don't have the exact numbers, but 5GB would probably be enough). On the tablet, you need 2-3GB of free space (on the internal memory), an unlocked bootloader , root and you need Busybox installed too.
On the computer, you'll need to compile your kernel first (this guide includes the compiler, and there's a prebuilt boot.img in the attachments if you want to skip this part). I recommend using https://github.com/Bogdacutu/STLinux-Kernel, with st8_linux_defconfig.
The initramfs is pretty simple, it just mounts the relevant system partitions and loads Linux from them: https://github.com/Bogdacutu/STLinux-Initramfs. You'll need to edit KERNEL_PATH in build.sh and make the kernel beforehand, then running build.sh will result in a boot.img which you can boot with fastboot:
Code:
fastboot boot new_boot.img -c "console=tty1 fbcon=map:10 fbcon=rotate:2 fbfix"
For the rootfs, Linux4Tegra is the easiest place to start from. All the Tegra K1 versions should work fine. For example, with R21.2: (the sudo is necessary there)
Code:
$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra124_Linux_R21.2.0_armhf.tbz2
$ tar xfvj Tegra124_Linux_R21.2.0_armhf.tbz2
$ cd Linux_for_Tegra
/Linux_for_Tegra$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar xfvj ../Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra/rootfs$ cd ..
/Linux_for_Tegra$ sudo ./apply_binaries.sh
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar cfvj ../rootfs.tar.bz2 .
The resulting rootfs.tar.bz2 you'll need to somehow get on the device. For the next part, I'll assume it's in /sdcard/rootfs.tar.bz2. You'll need to do this on the device (through ADB or through Terminal Emulator)
Code:
$ su
# cd data
/data# mkdir linux
/data# cd linux
/data/linux# tar xfvj ../media/0/rootfs.tar.bz2
Enabling Bluetooth with brcm_patchram_plus:
Code:
$ sudo brcm_patchram_plus -d --patchram /system/etc/firmware/bcm43241.hcd --baudrate 3000000 --enable_lpm --enable_hci --use_baudrate_for_download --no2bytes --tosleep 1000 /dev/ttyTHS2
Prebuilt boot images:
new_boot(80).img - working WiFi and sound
new_boot(90).img - added pointer emulation to touchscreen driver
new_boot(94).img - fixed Bluetooth stability
new_boot(114).img - fixed HDMI, added support for non-LTE partition table, my tegra driver patch is now optional (without it fbcon doesn't work properly, enable by adding fbfix to cmdline)
new_boot(123).img (newest at the moment) - fbfix isn't needed anymore, added support for tmpfs ACLs, enabled XZ compression (because after reaching a certain size, the kernel wouldn't find the initramfs anymore), enabled KVM
Bogdacutu said:
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Click to expand...
Click to collapse
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
_TB_TB_ said:
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
Click to expand...
Click to collapse
It will always return -ENOENT except for the first time the function gets called (which is enough for the screen to get initialized).
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
joshtheitguy said:
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
Click to expand...
Click to collapse
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Bogdacutu said:
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Click to expand...
Click to collapse
Thanks, that was the command I couldn't remember. Let me do a backup of it first then I will try again to see if the outcome is any different, I'll let you know how it goes once I have a chance.
Great i need a dual boot Android/Linux
Bogdacutu said:
What works:
Audio
WiFi
Click to expand...
Click to collapse
Bogdacutu said:
Got it working thanks to /u/GenuineAster, will post a full guide in a day or two.
Click to expand...
Click to collapse
Bogdacutu said:
Photos:
https://s3.amazonaws.com/pushbullet...OAfew/Screenshot from 2014-12-28 12:51:51.png
Click to expand...
Click to collapse
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
etienne51 said:
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
Click to expand...
Click to collapse
I just updated the boot.img from post #4, WiFi and sound work now, Bluetooth works if you load firmware but it's pretty unstable at the moment.
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
etienne51 said:
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
Click to expand...
Click to collapse
Not really, you can try messing with the governors and max frequency, iirc there's a script in the driver package that automatically sets the CPU frequency lower on boot.
Update: I got the touchscreen to work with the Android drivers! I will upload the changes to my kernel repo soon (as soon as I figure out which of all the changes I did are actually required).
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
No idea if HDMI works, I don't have a cable (my patch might break it though, in which case we'll probably need to change it). And it works on LTE tablets, but mobile data doesn't work (at least for now).
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
I just ordered a Mini HDMI to HDMI cable, it will arrive in less than a week. As soon as I get it, I'll tell you guys how it works!
/u/GenuineAster confirmed that HDMI isn't working. I'm going to get an Ethernet adapter for netconsole soon, so that I can find out why it doesn't work with my patch to the tegra driver (which I'm sure is the reason HDMI isn't working). I'm also working on a way to get libGL.so to work in an i386 chroot (so that we can try to play desktop games that aren't compiled for ARM yet).
I'm impressed that this actually works so well. Makes what I have on my Shield Portable look pitiful. No sound, no video acceleration, etc. Now the question is, what changes have to be made to a mainline kernel to get similar results? Well, minus the video acceleration that's likely hard-coded to a specific kernel version. Bogdacutu, do you have a patch of your changes? Your github repo isn't a forked copy of the kernel, so it's hard to see the initial changes. I'd like to get a copy of Fedora running. Also looking forward to your touchscreen fix. My usb-otg cable is flakey to the point it causes Ubuntu to reboot if I bump it too much...
Question to the larger community: Anyone know how to get the wireless controller to work with this? I poked at wpa_cli and a couple of the p2p_ commands, but so far haven't picked up anything from the controller when it's searching.
Edit: Seems the otg charging thing doesn't work either. Makes long-term use impracticle when an input device has to be plugged in. Any of the kernel hackers know the bits that changed in nvidia's lollipop kernel to allow this?
For those of you missing Windows 8.1, congratulations, you just found the solution.
Download
OneDrive http://1drv.ms/1SGHo5e
MEGA https://mega.nz/#F!ks8gjaZT!oQx3xt9ET0nXe8JbKDvtsA
Features
1.Windows is fully updated as of February 2016.
2.Surface February update included (solves most speaker popping issue)
3.Based on Surface Pro 3 image. Full stock-like Surface branding (desktop background, out-of-box experience).
4.Windows activates with the embedded product key. Fully legit. I cannot guarantee if yours couldn’t activate though.
5.Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again.) | Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store | Trial Office removed | Speech data removed.
6.Languages included: English, French, Spanish. Since it is Windows 8 Pro, you can download any other language later.
7.Fully working refresh and reset functionality.
8.WinRE from vanilla Windows, touchscreen driver included.
9.Pagefile takes less space: 400 MB. It can grow to up to 8 GB, a reboot brings it back to 400 MB.
10.Various Windows tweaks | File Indexing paused on battery | Verbose messages, you get more information in boots and shutdowns | No startup programs delay | non-certified DLNA devices are supported | Custom resolution script added (open C: drive, its there. Just double click.) | "Get Windows 10" system tray icon disabled.
11.Some drivers from S3, SP3, SP4, and other OEM devices (kudos to them for releasing their Skylake devices with Windows 8.1 drivers).
12.Latest Intel iGPU driver (version 4380 Beta).
NOT working
1.Windows Hello. As expected, Windows 8.1 does not support Windows Hello.
2.The buttons are mapped differently | Power --> Volume Down | Volume Up --> Power | Volume Down --> Start
3.Surface app | You cant adjust pen sensitivity | You can't configure the pen top button action through the app. You can still customize it manually with AHK.
FAQ
Q: Camera app crashes / BSOD
A: You need to disable the IR camera. You can do that either via the BIOS or Device Manager.
Q: The pen button doesn't work after the first setup
A: You may need to re-pair the pen. Go to PC Settings > Bluetooth and remove the Surface Pen. Create a new pairing by pressing the pen top button for 7 seconds, it will show up on the Surface, and just pair it.
Q: How did you get the embedded Windows 10 product key to work with Windows 8.1?
A: Actually I have no idea. It just worked.
Q: Are the "not working" issues going to be fixed?
A: For the buttons, its up to Microsoft to release a Windows 8.1 compatible driver, and we have no other source as Microsoft has modified Intel's driver. If you know how to remap the buttons (either via editing the driver, Registry, or AHK), please share it with us and I will include it in the next version. For the Surface app, I believe it is simply because the Windows 8 version of Surface app was not updated for the Surface Pro 4 (and will never be), so don’t expect that one.
Q: Why did you go with the beta driver for the graphics?
A: The latest release version, 4352 and 4364, are practically unusable. I experienced blank screen in video playback and some random BSOD. No choice really.
Q: When Intel has released the new driver, do I need to wait for the next version of the ROM?
A: No, you can just download and install it yourself without waiting for me to upload an updated ROM. The new version should pop up here, download the ZIP version for Windows 8.1, and install it using the "Have Disk…" method. Step-by-step guide http://www.windowscentral.com/how-install-intel-beta-graphics-drivers-surface
Q: How do I remap the pen buttons manually?
A: Go browse /r/Surface in Reddit, they have comprehensive guides on how to use AHK with the Surface Pen.
Q: Do I need to wait for your next ROM to get Windows updated?
A: No, you can just update normally via Windows Update
Q: You idiotic luddites should just upgrade to Windows 10 rather than shoehorning Windows 8 to the cutting-edge device that clearly does not deserve the old, ****ty Windows 8. Also, I am a Windows 10 fanboy.
A: Before you get angry and all that, I actually *do* want to upgrade to Windows 10. I mean, how cool is that to login with your face? However, it is hampered by quite a lot ergonomic usability issues, bugs, and the general quirkiness of Tablet Mode. As of today, Tablet Mode is nowhere near final. Not even the Task View has proper animation in Tablet Mode, it already tells how half-assed the Tablet Mode is.
How to install
BACKUP BACKUP BACKUP!!! This will format the entire disk. No data will be preserved! Its also advised to remove the microSD card during the process.
0. Get a keyboard and USB hub if you don’t have the Type Cover.
1. Download and extract the package
2. Set up the ISO image on a CD or USB stick. If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part.txt
6. Enter apply D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.
Signed up on xda just to express my gratitude for this great tutorial and release. Everything worked a charm with full touchscreen support and I am so glad to finally have Windows 8.1 on my Surface Pro 4! No more forced windows updates sucking up my bandwidth, more free space on my hard disk, and the only gaming app that I use for my ps2 games (PCSX2), finally runs at 60fps (can you imagine on windows 10 the emulator would drop between 40-50 fps)!!! Thanks again for making my day!
ptrkhh, did you by any chance figure out how to configure the power and volume buttons???
For now I'm using volume up button to turn the tablet on and off and the power button to turn the volume down.
Fan-damn-tastic!!!
Like the other person above, I made an account just to express my EXTREME gratitude for the amazing work that was done.
I just got myself a surface book for dirt cheap, fantastic device, horrible OS. I'm not one to shy away from randomly screwing with things, so on my research for windows 8 installs for the Book, I found this absolute GEM of a post.
Downloaded the image, and threw it on my Surface Book and here's what happened:
a) installed flawlessly
b) activated instantly
c) everything that works on the Pro, works on the book. The keyboard and mouse work too!!!
d) The BIG one... the DETACH...... IT WORKS!!! Hold the detach button like normal, and, granted it seems to take a second or so longer than it did on Win10, but it releases JUST fine.
e) the dual batteries. I didn't test it for long, but Win8 seems to drain the base battery and leave the tablet battery alone.
f) the power /vol buttons do the same thing as the pro4, but i really don't care. Actually, the Book doesn't have a windows button on the tablet, so the vol down button doing that is actually a HUGE plus for me. Screw the volume controls!
g) i have not figured out the nvidia drivers yet, but i also haven't tried too hard yet. So that's a negative so far.
h) Front camera does weird infared things. It will be disabled.
I would imagine even if i get the dual gpu to work, if i start a program with the nvidia, and disconnect the screen, it will probably go all fubar and need a hard restart. The latch seems to run independently from the rest, and without software watching it, it WILL do what you tell it to, period. (my assumption, haven't tried it yet)
Battery life has not been tested much yet.
Device manager shows 2 unknown devices. I'm assuming one is the GFX card, the other one, probably the detatch button. If that's not it i have no idea. Really don't care though.
Updates pick up on new driver versions just fine. (again, so far)
I have the i5 version w/dual gfx. I have no idea what will and won't happen with the i7, the i7 with nvidia, or the newest performance base with the better nvidia gfx. I doubt much will be different, but much as I did, proceed at your own risk!
I hope this was useful, and if it was, let everyone know it works!!!!
If anyone wants, I can post an update after I finish setting it up, and had some real-life usage of it. If not, my feelings will not be hurt!
Awesome!
Works almost perfect on my Surface Pro 4.
But somehow it cannot auto rotate and the touch keyboard is not popping up (even in metro apps).
Does anybody know how to fix that?
Edit: you have to reboot and remove the keyboard before windows boots to get it working.
The OneDrive link is dead, can you get a new link? Mega isn't working for me
Would this work on a surface 3?
Surface pro 4 BSOD
Hi, I have the i5 version surface pro 4 and when i use the image above or a fresh copy of windows 8.1 pro it finishes installing then blue screens with internal power error. Any ideas as to get past this.
Cheers
I have the same problem.
When it finishes installing, I get a blue screen saying there is a problem with the BCD. I tried booting with a Windows 10 ISO to use the startup repair tool to fix it, but it says it can't. I've tried it 3 or 4 times; it did work once, but I wanted to try a different Windows, so I wiped it. Now I can't get it to work again. I did all the diskpart stuff, and the apply, all seemed to work until final boot = bsod. The apply.cmd is supposed to do the configuring, I think. Anybody else had this problem?
Surface Pro 4 factory restore
Hi" have you tried going to the Microsoft site and downloading the factory image. Just take the ISO and make into USB bootable. It will install everything and recreate all partions. Hope this helps.
Does anyone know If this will work on Surface pro 6????
I ran into an issue with my Surface pro 6 that gives me the BSOD every time I connect my type cover!!! I tried everything! I ran all the diagnostics and went through almost every safe steps and was able to fix the corrupted files. I even did all the driver diagnostics!!! It is very frustrating because I even did a factory reset and I'm still having the same issue... I'm hoping to be able to safely downgrade to Windows 8.1 to see if it fixes the issue, then upgrading to Windows 10 again. That's the last thing I can think of.
Does it work on SP4 2017???
I have the same problem.
When I tried to install this ROM on my Surface pro 4 2017, it gives me the BSOD.
Commands do not work, it says right no the first: "The system cannot find the path specified"
i also have the same problem on my surface pro 6
How to install a version of 8.1 on SP4-SP6
If you get that INTERNAL_POWER_ERROR, you most likely have a Kaby Lake processer which only supports Windows 10. The only version of 8.1 that works on a Kaby Lake Surface Pro 4+ is Windows Server 2012 R2.
asking for drivers
ptrkhh said:
For those of you missing Windows 8.1, congratulations, you just found the solution.
Features
1.Windows is fully updated as of February 2016.
2.Surface February update included (solves most speaker popping issue)
3.Based on Surface Pro 3 image. Full stock-like Surface branding (desktop background, out-of-box experience).
4.Windows activates with the embedded product key. Fully legit. I cannot guarantee if yours couldn’t activate though.
5.Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again.) | Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store | Trial Office removed | Speech data removed.
6.Languages included: English, French, Spanish. Since it is Windows 8 Pro, you can download any other language later.
7.Fully working refresh and reset functionality.
8.WinRE from vanilla Windows, touchscreen driver included.
9.Pagefile takes less space: 400 MB. It can grow to up to 8 GB, a reboot brings it back to 400 MB.
10.Various Windows tweaks | File Indexing paused on battery | Verbose messages, you get more information in boots and shutdowns | No startup programs delay | non-certified DLNA devices are supported | Custom resolution script added (open C: drive, its there. Just double click.) | "Get Windows 10" system tray icon disabled.
11.Some drivers from S3, SP3, SP4, and other OEM devices (kudos to them for releasing their Skylake devices with Windows 8.1 drivers).
12.Latest Intel iGPU driver (version 4380 Beta).
NOT working
1.Windows Hello. As expected, Windows 8.1 does not support Windows Hello.
2.The buttons are mapped differently | Power --> Volume Down | Volume Up --> Power | Volume Down --> Start
3.Surface app | You cant adjust pen sensitivity | You can't configure the pen top button action through the app. You can still customize it manually with AHK.
FAQ
Q: Camera app crashes / BSOD
A: You need to disable the IR camera. You can do that either via the BIOS or Device Manager.
Q: The pen button doesn't work after the first setup
A: You may need to re-pair the pen. Go to PC Settings > Bluetooth and remove the Surface Pen. Create a new pairing by pressing the pen top button for 7 seconds, it will show up on the Surface, and just pair it.
Q: How did you get the embedded Windows 10 product key to work with Windows 8.1?
A: Actually I have no idea. It just worked.
Q: Are the "not working" issues going to be fixed?
A: For the buttons, its up to Microsoft to release a Windows 8.1 compatible driver, and we have no other source as Microsoft has modified Intel's driver. If you know how to remap the buttons (either via editing the driver, Registry, or AHK), please share it with us and I will include it in the next version. For the Surface app, I believe it is simply because the Windows 8 version of Surface app was not updated for the Surface Pro 4 (and will never be), so don’t expect that one.
Q: Why did you go with the beta driver for the graphics?
A: The latest release version, 4352 and 4364, are practically unusable. I experienced blank screen in video playback and some random BSOD. No choice really.
Q: When Intel has released the new driver, do I need to wait for the next version of the ROM?
A: No, you can just download and install it yourself without waiting for me to upload an updated ROM. The new version should pop up here, download the ZIP version for Windows 8.1, and install it using the "Have Disk…" method. Step-by-step guide
Q: How do I remap the pen buttons manually?
A: Go browse /r/Surface in Reddit, they have comprehensive guides on how to use AHK with the Surface Pen.
Q: Do I need to wait for your next ROM to get Windows updated?
A: No, you can just update normally via Windows Update
Q: You idiotic luddites should just upgrade to Windows 10 rather than shoehorning Windows 8 to the cutting-edge device that clearly does not deserve the old, ****ty Windows 8. Also, I am a Windows 10 fanboy.
A: Before you get angry and all that, I actually *do* want to upgrade to Windows 10. I mean, how cool is that to login with your face? However, it is hampered by quite a lot ergonomic usability issues, bugs, and the general quirkiness of Tablet Mode. As of today, Tablet Mode is nowhere near final. Not even the Task View has proper animation in Tablet Mode, it already tells how half-assed the Tablet Mode is.
How to install
BACKUP BACKUP BACKUP!!! This will format the entire disk. No data will be preserved! Its also advised to remove the microSD card during the process.
0. Get a keyboard and USB hub if you don’t have the Type Cover.
1. Download and extract the package
2. Set up the ISO image on a CD or USB stick. If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part.txt
6. Enter apply D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.
Click to expand...
Click to collapse
Dear ptrkhh,
Thank you very much. Without your excellent work, people can still not use SP4 installing Windows 8.1 or even Server 2012(based on Windows 8.1 framwork and also working with Windows 8.1drivers). Because there are many versions of both Windows 8.1 or even Server 2012, I was tring to collect the drivers that SP4 can work.It is hard to find touchscreen driver from vanilla Windows, and there so many drivers to test from S3,SP3,OEM. Could you please share the Surface Pro 4 drivers for Windows 8.1 separately, or give us a guide to lead to download each drivers. Hope you have a nice day
repo006 said:
Dear ptrkhh,
Thank you very much. Without your excellent work, people can still not use SP4 installing Windows 8.1 or even Server 2012(based on Windows 8.1 framwork and also working with Windows 8.1drivers). Because there are many versions of both Windows 8.1 or even Server 2012, I was tring to collect the drivers that SP4 can work.It is hard to find touchscreen driver from vanilla Windows, and there so many drivers to test from S3,SP3,OEM. Could you please share the Surface Pro 4 drivers for Windows 8.1 separately, or give us a guide to lead to download each drivers. Hope you have a nice day
Click to expand...
Click to collapse
Hi, thank you, it means a lot to me. Unfortunately I no longer have the device nor copies of the driver. Quite surprisingly many drivers are actually available online, you may want to consider using the software called "Snappy Driver Installer" (SDI), it is able to find drivers suitable for your device. The ones I formulated myself are under the folder "bastard drivers.rar", which is not many if I remember correctly.
For the touchscreen functionality in particular, it needs the graphics driver. Once you have the graphics driver installed, touchscreen should work instantly.
How much free ram is there after a fresh install?
I have ram shortage issues in Win10 with my 4GB Pro4. I'm not a fan of Win10 either but I sure wish I could just disable crap and free up the ram instead of downgrading.
Does the front webcam and mic work ok? I use mine frequently. Thanks!
Disclaimer: I got this device from the Manufacturer to test Linux on it. The below findings are my own and express my own opinion.
Specs and short review:
Intel Atom x5-Z8350 CPU (4x1,92 GHz)
Intel Integrated GPU
1920x1200 10.1" IPS Screen
4GB RAM
64GB Internal Storage
1 x USB C
1 x USB Micro B
1 x Mini HDMI
Bluetooth 4.2
2.4GHz WiFi
Rotation Sensor
Front and Back Camera
Mico SD Card slot up to 400GB (Website claims 64GB but I sucessfully tested it with an 128GB Card that uses the SDXC Standard)
Headphone Jack
Stereo Speakers
Keyboard Dock Support
Touchpen support
The Chuwi Hi10 Air is a compact 10.1" Tablet running a Windows 10. It has a sturdy Aluminium Body and the overall build quality is astonishing.
The speakers are surprisingly good for a tablet in that price segment. Paired with Bluetooth, a headphone jack and the 1920x1200 WUXGA display it's perfect for all kind of Media Playback. The battery is powerful enough to easily survive a few Movies. The optional detachable keyboard is a welcome addition for when you need to write some text.
The keyboard is nice to type on, but I had cases where it would send keys out of nowhere. I can't guarantee that's not caused by the few drops of water I accidentally spilled on the connection to the tablet at some point. I'm not a big fan of the trackpad, mainly because it's way to small to be usable for me but that might be because I am used to the trackpad on my 15" MacBook Pro.
The Touchpen is very accurate thanks to the digitizer, however the touchscreen does not send different signals for Pen and Finger to the System. That means trying to take notes while resting your hand on the screen doesn't really work.
Sadly, the full Windows 10 install user experience is really impacted by the entry level Intel Atom Z8350. It's just not powerful enough to accomplish any advanced tasks.
However, Chuwi sent me the device to bring linux to it, so that's what I did. This allows us to use lighter Window Managers and therefore more resources for actual tasks, resulting in a better performance.
Install Linux
First of all you need to install Linux on the tablet. That means you will erase your internal Windows installation, so make sure to either do a backup of it, or at least make yourself familiar with how to reinstall Windows in case it's needed.
Please note that you can NOT install Linux on an SDCard because the BIOS can not boot from the SDCard.
Backup
You can find the Hi10 Air Windows drivers here:
https://forum.chuwi.com/forum.php?mod=viewthread&tid=6861
And a guide here (applies for the Hi10 Air too):
https://forum.chuwi.com/forum.php?mod=viewthread&tid=15&page=7#pid29091
https://forum.chuwi.com/thread-15-1-1.html
Install
Next up, it's time to choose your Linux distro.
I recommend anything that is based on Arch Linux and that uses either LightDM or lxdm, because that is what my guide will be using to setup certain features. Of cause you're free to choosewhatever you want.
That means you could for example use Antergos, an ArchLinux based distro that includes Desktop managers (for Antergos I recommend XFCE), or go the hard way and install ArchLinux from scratch and use lxdm with LXQt. LXQt proved to me to be the best lightweight and yet High-DPI friendly Desktop Environment, so that's what I used.
I trust you will be able to find the guides on how to install either with a quick Google search, so I will not go much further into detail here.
To get into the boot menu, you need to press F7.
After your installation is done most things are already working.
Fixing Remaining Issues
Out of the box, there are a few issues and things that do not work because they are missing drivers or similar.
Automatic Rotation
We're getting started with the most important which is rotation.
As you'll need to enter a couple commands to get automatic rotation working, start off with manually rotating the screen by opening a terminal and run the command
Code:
xrandr -o left
Note: xrandr is part of xorg-xrandr, and you will need that package for autoration to work.
There are a couple solution on how to rotate the screen out there, however I decided to go for the one with least overhead that looked the cleanest to me.
First of all, compile the 2in1screen binary. The sourcecode can be found on my GitHub. Download, compile it and push it to /usr/local/bin.
Note: Make sure to install xorg-xrandr and xorg-xinput for this tool to work.
Code:
wget https://raw.githubusercontent.com/Myself5/Chuwi_Hi10_Air_Linux/master/2in1screen.c
gcc -O2 -o 2in1screen 2in1screen.c
sudo mv 2in1screen /usr/local/bin/
sudo chmod +x /usr/local/bin/2in1screen
Now configure the Desktop Manager to start it after login.
LXDE: add
Code:
/usr/local/bin/2in1screen &
to
Code:
/etc/lxdm/PostLogin
LightDM: Place the screenrotate.sh in /etc/lightdm/screenrotate.sh and set
Code:
display-setup-script
in
Code:
/etc/lightdm/lightdm.conf
to
Code:
display-setup-script /etc/lightdm/screenrotate.sh
screenrotate.sh
Code:
#!/bin/bash
pkill -9 2in1screen
/usr/bin/2in1screen &
Reboot and make sure everything works as desired.
Touchscreen
The Hi10 Airs Silead touchscreen requires drivers that are not bundled with a Linux install. You can download them here: https://github.com/onitake/gsl-firmware/tree/master/firmware/linux
See the Readme on how to install them.
These drivers get loaded by the Linux kernel. I submitted a commit to add support for the Hi10 Air to the Linux Kernel and it has been approved. The commit is merged in the 5.1 (and newer) Kernel. That means you need to update your kernel for a proper touch support.
If you previously used my Kernel you can go back to the official kernel by running:
Code:
sudo pacman -R linux-chewbacca linux-chewbacca-headers
sudo pacman -Syu linux linux-headers
sudo grub-mkconfig -o /boot/grub/grub.cfg
Now reboot and enjoy your touchscreen.
Audio
If your Audio isn't working, make sure to update the alsa-lib to Version 1.1.7 or above. On Arch that package is in the stable repos so a
Code:
sudo pacman -Syu
will be enough.
Bluetooth
Install blueman and follow the firmware instructions mentioned here:
https://github.com/lwfinger/rtl8723bs_bt/issues/28#issuecomment-432806835
Which means you need to clone https://github.com/lwfinger/rtl8723bs_bt
and run
Code:
sudo cp rtlbt_fw /usr/lib/firmware/rtl_bt/rtl8723bs_fw.bin
sudo cp rtlbt_config /usr/lib/firmware/rtl_bt/rtl8723bs_config.bin
cd /usr/lib/firmware/rtl_bt
sudo ln -s rtl8723bs_config.bin rtl8723bs_config-OBDA8723.bin
General UI
Now, you probably already noticed, everything is a bit small to use your Fingers.
As a browser I recommend Google Chrome as that has a great touchscreen UI already.
For File browsing and reading I suggest using nautilus and evince because of their touch friendlyness.
System DPI
For the whole system, there is a few things you can improve:
First of all, increase the general DPI.
You can do so by adding
Code:
Xft.dpi: 150
to
Code:
~/.Xresources
. If the file doesn't exist, create it.
LXQt Tweaks
Next up a few additional tweaks for LXQt:
First of all increase the Panel bar
Rightclick on the Panel and Press "Configure Panel". Then set the Size to 50px and the Icon Size to 30px.
Next up, Go to the Menu -> Preferences -> LXQt settings -> Appearance -> Font and set the DPI to 96
and finally go to Menu -> Preferences -> LXQt settings -> OpenBox Settings -> Font and increase the individual fonts to get a window title bar to drag/drop as well as hit the navigation with the finger. I set mine to Cantarell 16 and Cantarell 14.
Install OnBoard
Another Handy feature I found myself in need of was an onscreen keyboard. For that I installed OnBoard, and found a very neat feature here: https://bugs.launchpad.net/onboard/+bug/1232107
You can map a button to open/close the keyboard.
I set mine to Super L, which equals the left Windows button and the touch button on the tablet itself.
In the LXQt Settings Menu you can configure Shortcut Keys.
Create or edit the existing shortcut and either map the following DBus Call.
DBus Call:
Service:
Code:
org.onboard.Onboard
Path:
Code:
/org/onboard/Onboard/Keyboard
Interface:
Code:
org.onboard.Onboard.Keyboard
Method:
Code:
ToggleVisible
If your Desktop environment doesn't support DBus calls, use the following command:
Code:
dbus-send --type=method_call --dest=org.onboard.Onboard /org/onboard/Onboard/Keyboard org.onboard.Onboard.Keyboard.ToggleVisible
I got a Chinese manufactured pad-like device which is supported by the Linux mainline kernel and works pretty well except for the ****ty wifi chipset from Broadcom. That device has z8300 Soc and runs pretty well. I really like the On-The-Go device design as it is easy to carry around. Thanks for sharing!
Does this do a total partition wipe? Can you install to the Android partition and keep windows?
Droid_Nut said:
Does this do a total partition wipe? Can you install to the Android partition and keep windows?
Click to expand...
Click to collapse
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.
I would love to get one of these units for review
Myself5 said:
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.
Click to expand...
Click to collapse
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
Droid_Nut said:
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
Click to expand...
Click to collapse
That sounds like a good plan. Clonezilla backup is what I went for too.
silv3rfox said:
@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
Click to expand...
Click to collapse
Battery life is great, i'd say better than Windows. Can't give you any numbers though because I didn't really pay attention to it yet.
Android-x86 is technically possible and with the Linux drivers even easier but I havn't looked into that yet.
Hey guys happy to see there is interest in this tablet. I do got the dualboot version too.
To install Android i found this:
jonathansblog. co.uk/ factory- restore- android- on- chuwi- hi10
After i personally Installed remix OS
konstakang.com /devices /chuwi_vi10plus /RemixOS/
When I installed Ubuntu, just Ubuntu Started, Android stuck, i found a solution here:
github.com /floe /tuxblet
I Just cant figure out this one:
Unfortunately, this still causes the Android install to hang on boot after Linux has been installed. I was assuming, for a very long time, that this is also an EFI-related problem. However, after multiple factory resets (see https://forum.chuwi.com/thread-2341-1-1.html and https://01.org/node/2463 for instructions), I finally found out that the problem is related to the very eager Ubuntu automounter, which grabs any ext4 filesystem it can find and mounts it read-write.
Of course, this shouldn't be a problem in theory, but this also happens for the Android system/data/etc. partitions, and whatever Ubuntu does to the ext4 FS when it's mounted, causes Android to croak. This means that even just booting a Ubuntu Live System from USB one single time will likely render the Android installation unbootable.
I've finally managed to fix this by setting the respective UUIDs to noauto in /etc/fstab as follows:
# do _not_ automount the Android partitions
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 /none ext4 ro,noauto 0 0
If you look closely, you will notice that entries 2-4 are not actually proper UUIDs, they have an additional digit from 1-3 at the very end. The reason for this is that all the Android partitions (system, cache, data, config) have the same UUID and show up with the extra digit when the automounter grabs them. I'm not sure if this UUID duplication might actually be the root cause...
Unfortunately he does not explain how to no auto mount this partitions without a live CD and / or it is going to work even if Ubuntu installed is.
Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
nikmag said:
Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
Click to expand...
Click to collapse
5.1 includes the touchscreen fix on it's own so you don't need to use the kernel I provided anymore.
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
nikmag said:
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
Click to expand...
Click to collapse
So it does work with my 5.09 kernel though, right? Otherwise you'd have forgotten to install the touch drivers (see the OP on how to do that).
Bluetooth works flawless for me on Arch. Maybe Mint has some other packages that don't fully work with the chip yet?
As for Grub: there's nothing we can do about that. As it currently stands grub has no support for touchscreens or screen rotation. You could try different UEFIs (rEFInd comes to mind here) but other than that it's not possible. I thought about possibly mapping the volume buttons to up/down for selection, but that would still leave us without an enter key.
Although, now that I think about it again: it might be possible to register the windows touchkey as "enter". I guess I'll take a look into that
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
nikmag said:
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
Click to expand...
Click to collapse
According to a quick Google search custom keymapping for grub seems to be harder than expected. rEFInd seems to have touch support for some tablets though. I might look into that instead.
The "active Pen" on Windows is useless because it's not "active". It does get prefered over your hand, but the Hi10 Air doesn't have proper pen support. So the 256 pressure level touchpen they sell you is effectively as good as your finger. There is no pressure sensitivity support. On Linux this get's even worse because the pen is apparently using a different kind of calibration, so if you use it it's horribly offset. I was looking to use it for Notes during lectures, which is impossible to do. Even on Windows it's just not working. I've been in contact with my contact at Chuwi (who also sent me the device) and he just kept on talking around the topic. He never officially claimed the Pen would be supported but also never denied it. All he did was keep on sending me different touch drivers to "make the pen work" (although the definition of the term "work" can mean everything here).
TL;DR: Not pleased AT ALL.
P.S: I just updated the OP. the 5.1 kernel is released and works flawless on my Hi10 Air.
Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc
heenry20 said:
Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc
Click to expand...
Click to collapse
So which tablet do you have? A normal Hi10 Air?
Myself5 said:
So which tablet do you have? A normal Hi10 Air?
Click to expand...
Click to collapse
Yes, running kde neon.
M5 you are right, the finger is much better than 'active' pen! I bought also nebo app for recognition but the pen is totally invisible. Probably you checked drivers from you know https://forum.chuwi.com/thread-6861-1-1.html. It will be a big help if you manage to do something with rEFInd . Thanks