Related
We've updated a bit....
Download Link: [Here]
We now have a complimentary app on the app store for this A4D App.
What is A4D?
The goal of A4D is for us to move beyond just N1 make it an all in one flashing/upgrading/android utility. We just added a ROM library with MD5s. We are not going to be hosting the actual ROMs by themselves so if you report a dead link, they will be taken down (after a number of reports). You can also add your own ROMs as well into the library.
The ROM library will be supported by both Android and Desktop App. We are rewriting the Desktop apps so that we can do all 3 platforms in one, Linux, Windows, and Mac. You'll love the layout of the app. That's all we can say for now.
Oh one more thing. The android app won the best android app award at the Mobile in the Middle Hack-a-thon over the weekend in Chicago (on 3/6/2010).
I would like you guys to try out the app and tell us feedbacks. Also feel free to add your own ROMs to the Database and tell us how we can make the DB better. There a number of features we are trying to add as well. But with our full time jobs... things are going a little slower than we wanted. Sorry.
Requirements to run the app on Android: Amon_RA's recovery. That's what we tested it with.
Reserved
Reserved for Future Updates / Changelog
Can't wait to see if this is fool proof.
Add md5 check. Make it in this way: user have to enter/copy-past md5 hashsum from forum/site. Program calculates md5 of image and says image is good or bad. Also you can disable flashing with out this check. ;-)
good idea. Will do that. That will help with flashing screwed up downloads.
Hi
Thank you for sharing the application.
Does it flash the radio too? I mean CyanogenMod has two files a radio ROM and a CyanogenMod ROM. Does it flash both of them to the phone?
Thanks.
Radio flash is in there we took it out. May do so in the next release but radio flashing is dangerous (can brick phones) so...
Hey Lwin,
Nice concept man, this is gonna prove very handy for many peeps.
You've come up trumps again
So, this is a desktop application?
Does it flash ROM's from your desktop or copy them over and just run the commands on the phone for you?
I ask, as I'm having some problems flashing now, based round a slightly faulty Micro SD card. Does it store backups on the phone or on your desktop PC?
This program is written so you don't have to do command line commands. Everything else remains the same. If you are doing a Nand backup, it goes where it used to go.
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
nice app for those that aren't familiar with cmd or jus pure...lazy lol
maybe the screens should be bigger as quite hard to see clearly whats available.
Pure Genius...
seraph1024 said:
Here is the GUI tool for unlocking, updating, restoring, flashing of the N1 (and in theory should work on all HTC androids).
Try it out and see if it is useful. The tool is made to help for people with very basic skills since the tool at this stage is a wrapper for the shell commands at this point.
Again, as usual, we take no responsibility for loss of sleep, loss of phone or screw ups on our side (due to app) or on your side (due to lack of ability to follow instructions).
I wish to make it more simple. We welcome feed backs.
Seraph1024 - ShadowPyro
Download Link: [Here]
Click to expand...
Click to collapse
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
shadowpyro said:
This program is written so you don't have to do command line commands. Everything else remains the same.
Click to expand...
Click to collapse
But I don't use command line now. I didn't realise anyone did. Do you not just boot into RA Recovery and flash from there?
shadowpyro said:
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
Click to expand...
Click to collapse
Thanks, I didn't ask for advice.
GodDriven said:
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
Click to expand...
Click to collapse
There will be a mac port sometime this week. I can most likely port to linux too but if you know linux and if you have to use wrapper, you have an issue
install issues
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Sounds like the app uses .NET framework 3.5.
So goto microsoft website an get 3.5 .Net Framework.
pwvandeursen said:
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Click to expand...
Click to collapse
You do need .Net 3.5. It should have asked you, if not installed that as a prerequisite.
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
pwvandeursen said:
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
Click to expand...
Click to collapse
Can you send us a screenshot.
Do not unzip into C:\android-sdk-windows. App will install SDK or search for the SDK there.
Unzip on your desktop or temp and install from there.
just to be clear, I unzipped adroid sdk and placed in the mentioned location. the android4dummies is extracted on the desktop and executed from there..
so should I remove the SDK and retry?
Ive managed to run Ubuntu Netbook Remix on the A101 in SDE.
By run i mean i see GDM, because the driver for the touchscreen seems not to be working.
What ive did was, i took an image from here: http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/10.10/release/ and copied everything from the data partition to a new .img file. Also ive copied the modules from the angstrom rootfs.img.
Then just copied over my rootfs.img over the angstrom one and booted.
There seems to be lots of issues, mainly, i guess, because the init script in the initrd should do something, the one from angstrom doesnt.
Also the kernel-log says it cant read the /proc/ filesystem.
I uploaded my rootfs img to rapidshare for you to try for yourselfes, maybe someone can pick up from here and build a really working kernel+initramfs.
http://rapidshare.com/users/KVLF41
I know it's not working out of the box but it's still pretty cool! IBy netbook remix you mean the new Unity UI correct>
Yes, but as i could not login,i havent seen if the windowmanager works correctly.
gomork said:
Ive managed to run Ubuntu Netbook Remix on the A101 in SDE.
By run i mean i see GDM, because the driver for the touchscreen seems not to be working.
Click to expand...
Click to collapse
Kudos! - You could just try to plug in a usb mouse/keyboard into the usb port - it's usb host (mouse and keyboard work in android)
I'd love to see some more action with this. A mouse+keyboard should at elast get you access to the desktop and thus, terminal. From there, enabling the touch screen should be within arms reach.
To experiment for myself, could you write together a fool proof (noob proof) guide to get to where you're at?
casimir007 said:
Kudos! - You could just try to plug in a usb mouse/keyboard into the usb port - it's usb host (mouse and keyboard work in android)
Click to expand...
Click to collapse
i tried that, but it did not work. But that might be because the only Device i have here to test is some wireless usb mouse, which might need some other drivers.
Im currently working on an image with the xserver-xorg-input-evtouch driver built-in. I hope that gets the touchscreen working in X11.
To get started:
Get some Ubuntu.
Install rootstock using: sudo apt-get install rootstock.
Run rootstock:
sudo rootstock --fqdn archos-ubuntu --login ubuntu --password ubuntu --keepimage --imagesize 2G --seed ubuntu-netbook
That one generates an .img file you can copy over your existing rootfs.img.
hi,
I'm very interested to get ubuntu working on archos 101
I've tried your instructions to build an image but it stops after:
...
Setting up software-center (3.0.4) ...
No protocol specified
/usr/lib/pymodules/python2.6/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
WARNING:root:Failed to setup dbus (ignoring)
Setting up xul-ext-ubufox (0.9~rc2-0ubuntu5) ...
Setting up ubufox (0.9~rc2-0ubuntu5) ...
Processing triggers for python-central ...
Setting up xserver-xorg-core (2:1.9.0-0ubuntu7) ...
Setting up gamin (0.1.10-1ubuntu3) ...
Setting up firefox-branding (3.6.10+build1+nobinonly-0ubuntu3) ...
Setting up mono-2.0-gac (2.6.7-3ubuntu1) ...
Setting up mono-gac (2.6.7-3ubuntu1) ...
* Installing 3 assemblies from libappindicator0.1-cil into Mono
i had to ctrl+c, because i tas going no where for about an hour.
I guess it needs display ? ..but i don't know how to solve this
Maybe you could try with an imagesize of 3G or another release like karmic.
i did, my first try was with 2Gb, but didn't finish because it went out of space
then I've tried with 3Gb and stoped as i wrote
I had that problem too once.. Just trying again might work rootstock seems to be a bit buggy.
A little update: usb-mice work, when the modules are copied in /lib/modules in the image, but only when no computer is connected on the mini-usb port, that was the problem in the first place.
Wlan driver extracted from stock archos android can be loaded too, but i didnt manage to get the firmware to load yet.
Ps: a happy new year to all of you.
Sent from my U20i using XDA App
I've tried this image http://forum.xda-developers.com/showpost.php?p=10190468&postcount=38
boots really fast to desktop (10 seconds), but touchscreen don't work, also tried with mouse but nothing
please delete post
could be nice if we run Ubuntu on Gen8
Maybe the image from this thread:
http://forum.xda-developers.com/showthread.php?p=10486278
will get us a little further?
gomork said:
Im currently working on an image with the xserver-xorg-input-evtouch driver built-in. I hope that gets the touchscreen working in X11.
Click to expand...
Click to collapse
Any luck with this?
Would offer to help, but am pretty much a n00b dev at this point >.<
Good God, how awesome it'd be to have a USEABLE distro of linux on the 101 or 70. I love using linux (i have linux mint installed on all 3 computers in my home) and it'd be excellent if i could install an embedded version on my tablet, but alas, i'm a plumber not a programmer! So if someone could post a few links or tutorials to get us started ( as i'm sure there are plenty of gen 8 owners who feel the same as me ) it'd be much appreciated.
Q. Does the 101 it have the same hardware components as the 5 it? The reason i ask is that i think there is a working version of ubuntu nbr for this device and im pretty sure it has the same processor as the gen 8 tablets ( cortex arm a8 ).
Q. Would an amature linux geek like me have any hope of porting it over to our device?
Q. Would it work natively or would we need to modify it?
If anyone else has an interest in having ubuntu on their tablet please post as we have to get this bumped up the list of to do's. BTW, thanks to all you guys in advance and best of luck.
shameless bump for a worthwhile cause!
EDIT:
also, if they can port it to the nook color...
http://forum.xda-developers.com/showthread.php?p=10306407
and, here is a link to a german site where the dev managed to use ubuntu nbr on an a70it using the vpn method:
http://www.android-hilfe.de/archos-70-forum/59607-ubuntu-auf-dem-a70it-es-laeuft.html
pfarrelliv said:
shameless bump for a worthwhile cause!
and, here is a link to a german site where the dev managed to use ubuntu nbr on an a70it using the vpn method:
http://www.android-hilfe.de/archos-70-forum/59607-ubuntu-auf-dem-a70it-es-laeuft.html
Click to expand...
Click to collapse
that's only running via vnc - that means no drivers for display and touchscreen and unfortunately won't get us much further
yes it's just a chroot so you can imagine as a ubuntu running with the android kernel. you could try mux the drivers from the angström to the ubuntu kernel and compile the kernel for arm processors this could work, at least integrating ev-touch will help a lot. search for google for ubuntu4arm and you will find some howto.
the reason why i'm outta this is i have not much time at the moment and without a usable on-screen-keyboard (and at the moment there is none) ubuntu is worthless for me on the tablet.
Why o why have there been so few posts on this subject? Are we the only one's interested or is it just too much work to get another version of linux on the gen 8 devices? Really not trying to be rude to any of the developers on xda because i think you guys are awesome, really, but could someone please tell us if this is a worthwhile cause or a pure waste of time and effort.
I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
roninisc said:
I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
Click to expand...
Click to collapse
anyone anyone, Beuller...
Hey, saw this was unanswered and figured I could help. First off, you will not be able to compile or install headers in the Ubuntu Touch system, as /lib/modules/<kernel version> is a bind-mount into the read-only LXC system image, one way to work around this issue on device is to mount the LXC container's system image read-write somewhere, move out the lib/modules directory to someplace else, umount, reboot and then link your moved lib/modules back into /lib/modules. You will need to do this compilation outside of your Nexus 10 in a cross-compilation environment or in an armhf chroot (imho, a chroot running the ARM build of Ubuntu works very well for this).
Once you have that, you can install the kernel package for your device (which I believe are labeled linux-headers-manta and linux-image-manta respectively) and build the driver you seek. However the kernel already comes with backports 4.4.2 in it's tree, so you may be able to apt-get source linux-image-manta and build the driver and/or the kernel itself if you wish. (I believe building the kernel builds the firmware needed for the drivers as well, but I have no way of knowing as I haven't actually rebuilt any drivers with firmware yet in my foray into linux-image-flo's source.)
One piece of advice: Make sure to join together the config.*.ubuntu files under the debian.flo and debian.master folders to get the working .config for your device. The defconfig from arch/arm/configs doesn't have all the needed options for uTouch and won't boot it.
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
roninisc said:
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
Click to expand...
Click to collapse
Sadly at this time, it definitely seems to be. The normal linux way of building drivers doesn't work on here because the modules directory (/lib/modules/3.4.0-5-flo) is read-only, also due to this kernel headers cannot be installed, this can be worked around, but it is definitely not something that the casual user can do easily. I hope this will change so I could start compiling modules and NOT need to rebuild the entire kernel for it.
Glad I could be of help and I love answering questions, I am currently using Ubuntu Touch as my main OS on my Nexus 7 as I'm trying to make it into my own portable workstation. So I'm constantly digging into the system and learning what I can, and I love to share.
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
- Backlight Control (added 25/5/2018)
I'm getting very near to have the touch and the keyboard working though
P.s. In attach you find the outputs from 3DMark - IceStorm Extreme (default settings), would be much appreciated if someone with the real Win version shared its score
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Broomfundel said:
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Click to expand...
Click to collapse
I have added the link to the guide! If yo have any issues let me know but keep in mind that currently no input devices (touchscreen or keyboard) work!
Thanks for posting this. I am really so impressed. Will be trashing my X90F tomorrow. Just got to dig out a powered USB hub. Ill report back, and lets see what happens.
(Hopefully not a brick)
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Broomfundel said:
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Click to expand...
Click to collapse
Hello Broomfundel,
I never got that error, but it seems to be a problem of the ASL Compiler build not of your file.
I am using Mac so I have another build, if you want to post the file I can compile it for you .
Otherwise you can try an older release or to build the tool from source maybe?
Poz1 said:
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
I'm getting very near to have the touch and the keyboard working though
Click to expand...
Click to collapse
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
THE MAXIMUM POWER said:
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
Click to expand...
Click to collapse
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Broomfundel said:
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Click to expand...
Click to collapse
With the -ta option I get both the .hex and the .aml file but you can try -tc if it doesn't work. Maybe due to the different build
P.s. (for other people that may incur in this) If you don't get the output files check that you have as last line of the terminal
"Compilation complete. 0 Errors"
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Poz1 said:
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
Click to expand...
Click to collapse
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Poz1 said:
Hello guys!
Click to expand...
Click to collapse
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
As Poz1 is obviously busy at the moment. Can anyone else get the DSTDWin.aml file for me to try and decode?
Thanks
Sorry guys I've been busy with university
Broomfundel said:
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
Click to expand...
Click to collapse
There you go I'm also updating the files DSTDWin of my blog with one with some fixes Well they depend on the settings you use in your Bios (that's why Windows may not boot after install, it changes some parameters (the wait time of the bios and the default boot partition)). When you use the builtin one is the bios that "updates" it for you but for now we need to do it by hand If we are going to end with everything working we can release a patched "Win" bios and everything will be simpler
Riskypedia said:
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Click to expand...
Click to collapse
I know There something in the DSDT (the file that tells the os which and where your pc components are) that has to be fixed to make Windows see these parts correctly
THE MAXIMUM POWER said:
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Click to expand...
Click to collapse
Didn't try Will do as soon as I have some free time :fingers-crossed:
Kinyapiplele said:
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Click to expand...
Click to collapse
Yep, but the problem is in the DSDT Thanks fot the input anyway
Poz1 said:
Sorry guys I've been busy with university
Click to expand...
Click to collapse
Don't worry, we all have real lives as well. I'm in the UK and we have a bank holiday on Monday. So this weekend, Ill get stuck in again.
Thanks for all your doing on this. You have already got further than anyone else who tried.
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Poz1 said:
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Click to expand...
Click to collapse
Just another Question, you as a Advance user, do you believe that we (yoga book Windows owners) can boot Android yb STOCK ROM ( i mean not the Android x86 based distros)?
Yes, but I think you would have to do the "reverse" DSDT injection (from win to android) as the official ROM has drivers for that components.
This means that, if you're lucky you would end up with our same problems (keyboard, pen and touch). If we don't fix that before
The problem with Android is that it is meant to be flashed on rom instead of being installed and this makes things more difficult.
It should be possible to flash the rom on an USB key, add grub and use it for DSDT injection like we do and see what happens.
Another problem is that the provided kernelflinger seems to have most of the security options enabled so 99% it will refuse to boot anyway.
Since it is opensource it should be possible to fix this anyway.
So yes, but it a loooong journey
Hi,
Firstly, installing desktop OS's of whatever sort on the Android version (YB1-X90F), insofar as anyone has managed it, is a completely different process and none of what follows is likely to be relevant.
Secondly, it should go without saying that any use of the linked ISO or the information in this post is entirely at your own risk.
There are several threads on xda and elsewhere dealing with attempts to install Linux on the Windows version of the Yoga Book (YB1-X91F). They're pretty consistent in terms of results, both with each other and my own attempts. I have tried the latest and previous LTS or main releases Debian, Ubuntu (all flavours), Mint and Fedora.
Between mine and others' attempts, most distros have the following working, using a Live ISO flashed to USB:
- Boot to desktop and successful install to eMMC
- Display
- Graphics pad responds to touches, but not aligned with screen rotation and probably in need of other calibration.
- USB, including ethernet-to-USB adapter
Some distros/versions additionally have:
- Touchscreen (only newer kernels, I think 4.13 onwards but definitely 4.15 onwards)
- Sound via HDMI
- Not sure about Bluetooth - possibly
The following didn't work with any distos/versions:
- A lot of the ACPI subsystem, meaning that some ICs (e.g. SD Card) don't receive power.
- Wifi
- SD Card
- Sound via headphones or speakers
- Halo Keyboard
- Touchscreen multitouch
- Battery gauge
- OS control of battery charger IC, though the IC sits in autonomous mode so the device still charges
- Display brightness adjustment (always set to max)
- Display auto-rotate
The Mint ISO linked at the end of this post has WiFi, the SD Card, two-finger right click and brightness adjustment working in addition to the OOTB functionality. I've made a lot of progress on the sound - the driver and codec load but it needs some configuration. I have read elsewhere that configuring this incorrectly can blow your speakers which is why I haven't tackled it yet.
The Halo keyboard doesn't work yet, so the Yoga Book can't be used in laptop mode for now. The only real barrier to using it in tablet mode is the lack of a functioning battery gauge. More on this below.
Instructions:
You will need a USB flash drive of at least 2GB, a USB keyboard and mouse and therefore a USB hub as well as a way of attaching it to the micro-usb port. I use an OTG adapter which came with a Samsung phone.
The touchscreen does not work when the Live ISO boots but it does work after installation.
Once Linux is installed on the eMMC, the firmware will boot to GRUB by default rather than Windows. To boot into Windows you have to enter the firmware menu. This should be easy to fix/reconfigure but I haven't got round to it yet. I need to get the volume and power keys working in GRUB first.
- Download the ISO from the link below and flash to USB. I use Etcher on MacOS which flashes in a dd-like manner (other tools make their own changes to the target drive to make it bootable - this isn't needed or desirable).
- Turn off hibernate, fast boot and secure boot in Windows. There are easily found guides on how to do this. It ought to be possible to retain secure boot but I have found doing so a real headache on other systems so didn't try in this case.
- Turn off any secure boot settings in the device firmware (access the menu by powering on with the volume up button pressed down).
- Using the firmware menu, boot from the flashed USB drive. When the desktop boots, use GParted to shrink the Windows partition, leaving at least 11GB (Mint says it needs 10.7GB). I've been messing around with Linux for months now on the YB and have found 11 enough.
- Run the desktop installer. At the partitioning menu, choose 'Something else'.
- Create a new Ext4 partition using all of the free space created previously and map it to '/'.
- Ignore any warnings about a swap partition. If you get stuck on a dialog about forcing a UEFI install, open a terminal and run 'killall ubiquity' then run the installer again with the network connection turned off. If the install doesn't work, you may have to risk the default 'Install Mint alongside Windows....' option. I have never had a problem with this, but I don't quite trust it, or indeed the installer in general.
- If you fail at the point of GRUB install, go back and start again with networking disabled.
- Just reboot as normal.
Changes from Stock ISO (probably not exhaustive)
- New ISO using 18.3 Cinnamon as a base using Cubic
- Updated, inc dist-upgrade as of 6 Sept 18
- Missing Broadcom firmware (for WiFi) added.
- Additions to /etc/skel/.config to put Mint into HiDPI mode
- Florence on screen keyboard added and loads on start
- Touchegg, which enables two-finger right click added and loads on start.
- LightDM settings changed to enable Florence and HiDPI
- Most importantly, a custom kernel (4.18.5) which is responsible for most of the above-OOTB functionality. Some of this is just about enabling the correct Atom ACPI ICs, other bits relate to load order (to get past the lack of brightness control).
Help!
- I really need some help with the battery gauge IC. For now, dmesg is the best bet but I'll follow up with another post with more detail.
- There are other things which need doing, e.g. the keyboard and finishing off the sound but these are relatively straightforward by comparison. The gauge/charger setup is the last low level thing not working.
Custom ISO:
This is my first post. I can't post links! Remove the spaces and ..... :
drive.google.com/ .... open? .... id=1-5vtnKAVpERmzTFIR3TGXe1DgvoFvehc
Help Needed - Battery Gauge/Charger
The issue
The following can be seen by running 'dmesg' after boot using the ISO in my first post, which uses a 4.18 kernel customised for the hardware in the Yoga Book.
The kernel attempts to load the driver for the TI bq24190 battery charger IC. I'm not yet able to post links so search for 'bq24190_charger.c' in the Linux kernel Github repo. The driver throws an error on boot when it hits this code at line 1640. It's expecting a 6 and it gets a 4, the value of BQ24190_REG_VPRS_PN_24190.
bq24190_charger.c
Code:
if (v != BQ24190_REG_VPRS_PN_24190 &&
v != BQ24190_REG_VPRS_PN_24192I) {
dev_err(bdi->dev, "Error unknown model: 0x%02x\n", v);
return -ENODEV;
}
If I remove this check altogether and re-compile the module then the driver proceeds to load but reports zeroes for all status values. It's not clear whether it is, in fact, the right chip and isn't talking to the rest of the hardware or it's simply the wrong driver.
However, at least removing this check allows the Whiskey Cove ACPI IC driver to get a bit further along. Search for 'intel_cht_int33fe.c' in the kernel source. Comments in this file (line 124) confirm that this IC is expected to be paired with a bq24190.
By adding in dmesg warnings and re-compiling the int33fe module I could see that when an unmodified bq24190 driver is used, i.e. the check above takes place and is failed, the int33fe driver fails its own check at line 138:
intel_cht_int33fe.c
Code:
regulator = regulator_get_optional(dev, "cht_wc_usb_typec_vbus");
if (IS_ERR(regulator)) {
ret = PTR_ERR(regulator);
return (ret == -ENODEV) ? -EPROBE_DEFER : ret;
}
regulator_put(regulator);
When I remove the check, it fails at the next check starting at line 145:
Code:
/* The FUSB302 uses the irq at index 1 and is the only irq user */
fusb302_irq = acpi_dev_gpio_irq_get(ACPI_COMPANION(dev), 1);
if (fusb302_irq < 0) {
if (fusb302_irq != -EPROBE_DEFER)
dev_err(dev, "Error getting FUSB302 irq\n");
return fusb302_irq;
}
I have tried various combinations of including the FUSB driver and dependencies as modules/built in but the result is the same. I also tried moving the FUSB check to after the code which tries to link up with the max17047 battery gauge IC, but this fails also.
Some owners of the Android version of the Yoga Book have posted files/screenshots on Telegram which indicate that a different charger, the bq25892 is used. As far as I know i2c devices are simply identified by the fact that they occupy a certain address on the bus. You can see in the datasheet for the bq24190 (sorry, no links!) on page 3 that it uses i2c address 6BH. The datasheet for the bq25890/2 shows on page 5 that the bq25892 also uses 6BH.
I don't know enough about i2c to know whether this is the issue, or how to point Linux to a different driver in the way that you might using a VIDID for a USB or PCI device? It would be really helpful if anybody could definitively confirm which chip we are dealing with.
Some final ACPI errors crop up towards the end of the dmesg output (I've cleared all the others) and I suspect that sorting this will clear them, as well as making the Yoga Book with Mint usable in Tablet mode.
Other things which need fixing:
- There are sound errors in the dmesg output but it also shows that the drivers and codec are loading properly. I can see all the devices which should be visible in amixer from the command line. Because getting the config wrong can blow speakers I've resisted tackling this until I've done further research but if anyone has a solution please let me know.
- Halo Keyboard. This needs either a kernel module to be written or a software layer which runs at least under X. I don't expect this to be hugely difficult - Linux can see the Halo as a wacom graphics pad and take input, albeit not deal with it properly yet. There's also a mystery, generic HID device which by process of elimination must be the button/backlight. However, the generic HID driver loads so it shouldn't be too hard to work out how to talk to it.
- I re-built the ISO using Cubic. When I have tried to make ISOs which use my custom kernel to boot the ISO itself, they don't work. I get garbled graphics and the boot stalls. This is why the touchscreen doesn't work when you live boot (which uses 4.10) but does when you install (because it uses 4.18). This ought not to be insurmountable but I haven't cracked it yet. I've tried doing it manually and using the Debian live-boot commands for both Debian/Ubuntu. Still no luck.
- Until I can get a custom ISO to boot from a custom kernel it won't be possible to install on the SD Card. Otherwise, there's no reason this shouldn't be possible.
- It should be possible to install to another USB device now, but I haven't tried yet. Make sure to use the disable MMC script on the desktop if you don't want to install Grub EFI on the eMMC. Ubuntu and derivatives ignore whatever you choose for this and just use the fist EFI partition they find. Amazingly this bug has been there since 2014!
- It ought to be possible to map the hardware buttons (volume, power) to specific keys in Grub, possibly using a locale. This would allow selections to be made without a keyboard.
android install
This might be related as I was just installing windows on Android version and now reverted back (https://forum.xda-developers.com/showpost.php?p=77556606&postcount=44), couple of observations that might help you: On android reinstall back it required to activate halo keyboard to get it working again, there was a phone code entered into the search bar to get it activated which triggered something called easyimage app. In android stock image you can actually find easyimage.zip which I guess is this "fake android update" to install the halo keyboard. Inside the zip are *.so libraries and some files related to halo keyboard and ink pen so you could try to play with those to get it working under classic Linux.
DNX mode allows to boot EFI via a USB cable &*fastboot (I guess windows version have also this as I activated it somewhere in BIOS?) so this can be also alternative version of booting an OS. IMHO Grub can also chainload iso image directly (I did it in past on normal PC, it was a couple of years ago so I can't find the guide to do it now) so in theory you can just place the Linux ISO image as a normal iso file on disk and tell GRUB to chainload that directly. Since it's possible to revert the Windows installation back to Android it might even be possible to dualboot. Android bootloader is also EFI based (kernelflinger) so you could also play with that. TWRP recovery image have full touch support for screen so that might be also a help when digging for configuration or extracting it from the sources.
intense.feel said:
...you can actually find easyimage.zip which I guess is this "fake android update" to install the halo keyboard. Inside the zip are *.so libraries and some files related to halo keyboard and ink pen so you could try to play with those to get it working under classic Linux.
Click to expand...
Click to collapse
This is really helpful, thank you. I'll have a look at what's there.
Still no progress with the battery gauge...
intense.feel said:
This might be related as I was just installing windows on Android version and now reverted back (https://forum.xda-developers.com/showpost.php?p=77556606&postcount=44), couple of observations that might help you: On android reinstall back it required to activate halo keyboard to get it working again, there was a phone code entered into the search bar to get it activated which triggered something called easyimage app. In android stock image you can actually find easyimage.zip which I guess is this "fake android update" to install the halo keyboard. Inside the zip are *.so libraries and some files related to halo keyboard and ink pen so you could try to play with those to get it working under classic Linux.
DNX mode allows to boot EFI via a USB cable &*fastboot (I guess windows version have also this as I activated it somewhere in BIOS?) so this can be also alternative version of booting an OS. IMHO Grub can also chainload iso image directly (I did it in past on normal PC, it was a couple of years ago so I can't find the guide to do it now) so in theory you can just place the Linux ISO image as a normal iso file on disk and tell GRUB to chainload that directly. Since it's possible to revert the Windows installation back to Android it might even be possible to dualboot. Android bootloader is also EFI based (kernelflinger) so you could also play with that. TWRP recovery image have full touch support for screen so that might be also a help when digging for configuration or extracting it from the sources.
Click to expand...
Click to collapse
I'm currently doing on that without the Hardware. my plan is to find the small / light weight linux kernel and port the driver of the HALO. I call this Project HALO port (not on github cuz I just gathering everything until I ready). right now I'm learning to compile the kernel because I never do that (3 years on linux xD). I hope soon I can figure out the protocol it did uses for the HALO (My guess is I2C/SMBus).
Update : I found someone on github just build custom Debian ISO to deploy on USB flash drive and be able to use HALO keyboard (A.K.A Yeti, based on Goodix gt9xx chip). This is his work on github
Woah this is amazing progress! I haven't been on the forums for a while; been working mostly on messing with Windows to make it more efficient and responsive lol.
jimnarey said:
The issue
The following can be seen by running 'dmesg' after boot using the ISO in my first post, which uses a 4.18 kernel customised for the hardware in the Yoga Book.
The kernel attempts to load the driver for the TI bq24190 battery charger IC. I'm not yet able to post links so search for 'bq24190_charger.c' in the Linux kernel Github repo. The driver throws an error on boot when it hits this code at line 1640. It's expecting a 6 and it gets a 4, the value of BQ24190_REG_VPRS_PN_24190.
bq24190_charger.c
Code:
if (v != BQ24190_REG_VPRS_PN_24190 &&
v != BQ24190_REG_VPRS_PN_24192I) {
dev_err(bdi->dev, "Error unknown model: 0x%02x\n", v);
return -ENODEV;
}
If I remove this check altogether and re-compile the module then the driver proceeds to load but reports zeroes for all status values. It's not clear whether it is, in fact, the right chip and isn't talking to the rest of the hardware or it's simply the wrong driver.
However, at least removing this check allows the Whiskey Cove ACPI IC driver to get a bit further along. Search for 'intel_cht_int33fe.c' in the kernel source. Comments in this file (line 124) confirm that this IC is expected to be paired with a bq24190.
By adding in dmesg warnings and re-compiling the int33fe module I could see that when an unmodified bq24190 driver is used, i.e. the check above takes place and is failed, the int33fe driver fails its own check at line 138:
intel_cht_int33fe.c
Code:
regulator = regulator_get_optional(dev, "cht_wc_usb_typec_vbus");
if (IS_ERR(regulator)) {
ret = PTR_ERR(regulator);
return (ret == -ENODEV) ? -EPROBE_DEFER : ret;
}
regulator_put(regulator);
When I remove the check, it fails at the next check starting at line 145:
Code:
/* The FUSB302 uses the irq at index 1 and is the only irq user */
fusb302_irq = acpi_dev_gpio_irq_get(ACPI_COMPANION(dev), 1);
if (fusb302_irq < 0) {
if (fusb302_irq != -EPROBE_DEFER)
dev_err(dev, "Error getting FUSB302 irq\n");
return fusb302_irq;
}
I have tried various combinations of including the FUSB driver and dependencies as modules/built in but the result is the same. I also tried moving the FUSB check to after the code which tries to link up with the max17047 battery gauge IC, but this fails also.
Some owners of the Android version of the Yoga Book have posted files/screenshots on Telegram which indicate that a different charger, the bq25892 is used. As far as I know i2c devices are simply identified by the fact that they occupy a certain address on the bus. You can see in the datasheet for the bq24190 (sorry, no links!) on page 3 that it uses i2c address 6BH. The datasheet for the bq25890/2 shows on page 5 that the bq25892 also uses 6BH.
I don't know enough about i2c to know whether this is the issue, or how to point Linux to a different driver in the way that you might using a VIDID for a USB or PCI device? It would be really helpful if anybody could definitively confirm which chip we are dealing with.
Some final ACPI errors crop up towards the end of the dmesg output (I've cleared all the others) and I suspect that sorting this will clear them, as well as making the Yoga Book with Mint usable in Tablet mode.
Other things which need fixing:
- There are sound errors in the dmesg output but it also shows that the drivers and codec are loading properly. I can see all the devices which should be visible in amixer from the command line. Because getting the config wrong can blow speakers I've resisted tackling this until I've done further research but if anyone has a solution please let me know.
- Halo Keyboard. This needs either a kernel module to be written or a software layer which runs at least under X. I don't expect this to be hugely difficult - Linux can see the Halo as a wacom graphics pad and take input, albeit not deal with it properly yet. There's also a mystery, generic HID device which by process of elimination must be the button/backlight. However, the generic HID driver loads so it shouldn't be too hard to work out how to talk to it.
- I re-built the ISO using Cubic. When I have tried to make ISOs which use my custom kernel to boot the ISO itself, they don't work. I get garbled graphics and the boot stalls. This is why the touchscreen doesn't work when you live boot (which uses 4.10) but does when you install (because it uses 4.18). This ought not to be insurmountable but I haven't cracked it yet. I've tried doing it manually and using the Debian live-boot commands for both Debian/Ubuntu. Still no luck.
- Until I can get a custom ISO to boot from a custom kernel it won't be possible to install on the SD Card. Otherwise, there's no reason this shouldn't be possible.
- It should be possible to install to another USB device now, but I haven't tried yet. Make sure to use the disable MMC script on the desktop if you don't want to install Grub EFI on the eMMC. Ubuntu and derivatives ignore whatever you choose for this and just use the fist EFI partition they find. Amazingly this bug has been there since 2014!
- It ought to be possible to map the hardware buttons (volume, power) to specific keys in Grub, possibly using a locale. This would allow selections to be made without a keyboard.
Click to expand...
Click to collapse
Not sure if you've seen, but this issue on the above GitHub project that has managed to get the battery gauge working says they're using the BQ27542.
https://github.com/jekhor/yogabook-linux-kernel/commit/f0b7662fa10f012410170c241a9fa91295f54dc1
Hi, I am the author of the repository mentioned above, https://github.com/jekhor/yogabook-linux. My linux porting efforts were focused at kernel, getting battery charger driver and halo keyboard working basically. So, this kernel supports the battery gauge, battery charger (with fast charging mode, yes!). For halo keyboard patch for the goodix touchscreen (touchpad really) kernel was needed, see the https://github.com/jekhor/yogabook-linux-kernel/commit/bd3a5953126fd87e4218550c5a31baafcdc60a38 commit. There is userspace keyboard driver in the Chromium OS which converts touchpad events into keypresses. Forked version suitable for build at GNU\Linux system is here: https://github.com/jekhor/chromiumos_touch_keyboard .
Some patches were accepted to the mainline Linux already:
0e116237aa42 extcon-intel-cht-wc: Make charger detection co-existing with OTG host mode (v5.1)
ff6cdfd71495 ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book (v5.1)
236c765d6abc mfd: intel_soc_pmic_chtwc: Register LED child device (v5.2)
a72a1be0de71 extcon: intel-cht-wc: Enable external charger (v5.2)
Feel free to ask me about this work and to create github issues. This is my spare time project, so I will glad to see other developers connected.
nice project dude was trying it today and touchscreen works good so far,
but i cant get the halo keyboard to work, if i try to use it my mouse only moving from left to right and right to left.
if i can help you with creating some logs or something else, just write me i'm not rly good on linux, but i want to use it on this low power device
edit: and yes i tried to reload the kernel modules (if modprobe is the correct command) but no change
i dont know if the problem is maybe that i have a germany keyboard layout, changing in the menu works for my hw keyboard but on the halo no difference still only mouse movement
blgblade said:
nice project dude was trying it today and touchscreen works good so far,
but i cant get the halo keyboard to work, if i try to use it my mouse only moving from left to right and right to left.
if i can help you with creating some logs or something else, just write me i'm not rly good on linux, but i want to use it on this low power device
edit: and yes i tried to reload the kernel modules (if modprobe is the correct command) but no change
i dont know if the problem is maybe that i have a germany keyboard layout, changing in the menu works for my hw keyboard but on the halo no difference still only mouse movement
Click to expand...
Click to collapse
Hmmm... You are second people who reports such problem with this image. What YB version you have? I have YB1-X91L only.
Could you please post an output of the command 'sudo cat /sys/class/dmi/id/*' (use external keyboard for this)?
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
Arghhh... I have lost one part of goodix touchscreen driver patch and keyboard will works only at YB1-X91L model (not X91F). Wil be fixed.
jekhor said:
Hmmm... You are second people who reports such problem with this image. What YB version you have? I have YB1-X91L only.
Could you please post an output of the command 'sudo cat /sys/class/dmi/id/*' (use external keyboard for this)?
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
Arghhh... I have lost one part of goodix touchscreen driver patch and keyboard will works only at YB1-X91L model (not X91F). Wil be fixed.
Click to expand...
Click to collapse
yep i have a YB1-X91F
ok nice, than i will wait for the next release
i found out 2 things that did not work (or not correctly or i'm to stupid xD)
- sound (but i allready see the post in issues )
- the gui and if i tried video it looks like there is no graphic driver installed (dont know how to specify this, but if i just move a window it looks like software rendering, ok my english should be better to explain this but i hope you know what i mean ^^)
if i found something more i will give you feedback
but for now, its rly nice work
thank you so much for this project
here the output from the command above
Code:
08/26/2016
LENOVO
04WT18WW
NO Asset Tag
INVALID
HA0QPQ1T
LENOVO
Not Defined
NO Asset Tag
HA0QPQ1T
11
LENOVO
X91F
dmi:bvnLENOVO:bvr04WT18WW:bd08/26/2016:svnLENOVO:pnLenovoYB1-X91F:pvrX91F:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct11:cvrX91F:
cat: /sys/class/dmi/id/power: Is a directory
(TBD)
Lenovo YB1-X91F
HA0QPQ1T
LENOVO_BI_04_PCG_FM_YB1_X91F
41564e49-494c-0044-0000-000000000000
X91F
cat: /sys/class/dmi/id/subsystem: Is a directory
LENOVO
MODALIAS=dmi:bvnLENOVO:bvr04WT18WW:bd08/26/2016:svnLENOVO:pnLenovoYB1-X91F:pvrX91F:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct11:cvrX91F:
blgblade said:
yep i have a YB1-X91F
ok nice, than i will wait for the next release
i found out 2 things that did not work (or not correctly or i'm to stupid xD)
- sound (but i allready see the post in issues )
- the gui and if i tried video it looks like there is no graphic driver installed (dont know how to specify this, but if i just move a window it looks like software rendering, ok my english should be better to explain this but i hope you know what i mean ^^)
if i found something more i will give you feedback
but for now, its rly nice work
thank you so much for this project
[/CODE]
Click to expand...
Click to collapse
I have uploaded fixed iso (halo keyboard should work): https://github.com/jekhor/yogabook-linux/releases/tag/livecd-test3.1
Yes, no sound, no force-feedback for keypresses.
Don't know about video driver and acceleration, need to check.
jekhor said:
I have uploaded fixed iso (halo keyboard should work): https://github.com/jekhor/yogabook-linux/releases/tag/livecd-test3.1
....
Click to expand...
Click to collapse
yes, the keyboard is now working, nice thank you
i will follow your progress and try to help if i can ^^
hey all, because @jekhor is using a diffrent keyboard layout (not only mapping are diffrent) i created a modified layout.csv
(on this page --> https://forums.lenovo.com/t5/Yoga-Book-Windows/Yoga-book-Window-keyboard-layout-wrong/td-p/3705108 <-- you will see the layout diffrences)
layout.csv as attachmant (as txt because csv is not allowed ^^)
changes:
- Enter key diffrent size
- # moved to the other position
- added the > < | key (dont know the name )
- LeftShift key diffrent size
edit: i created a patch for the filesystem.squashfs file, just unpack the patcher in the /live/ folder on your stick and run it or run it ffrom any location you want and choose the live folder from the app, than you can use the keyboardlayout on the livesystem (sorry, the patcher is windows only)
Thanks for all the hard work
Hey all, just came across this thread recently - really appreciate all the hard work here. I've been trying to install Ubuntu on my Windows powered YogaBook since the beginning, and am amazed at how far your efforts have come. Looking forward to the completed product later on! Can't stand Win10 as it tends to bloat and slowdown. Hopefully Linux runs better on this thing.
Thxxx man
Love the level of involvement in this adforable and light device with great potential in linux
Hope u guys dont lose patience in the development.
Once the wifi, keyboard and touch screen is aredy, i think i will fully change my android yogabook into linux.......
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Love the level of involvement in this adforable and light device with great potential in linux
Hope u guys dont lose patience in the development.
Once the wifi, keyboard and touch screen is aredy, i think i will fully change my android yogabook into linux.......
Thanks for the effort
Thanks again, all for the effort.
Has there been any progress made so far?
It has been more than 2 full years, one in this forum has been able to achieve in only a few weeks of coding what MOST of us have tried to achieve in years. He has uploaded his ISO of Debian with many things working, however some things are left to be desired : Resume keyboard (tried with script - failed), fix for keyboard keys layout, and the resolution (worked with XRANDR script : working). However, he does not seem either interested in going further or does not have the device to compile against, either way without him we could be stuck with WinBlows on this machine. Until we get him BACK on board, we are stuck in the water... @jekhor ?
Jeff said:
It has been more than 2 full years, one in this forum has been able to achieve in only a few weeks of coding what MOST of us have tried to achieve in years. He has uploaded his ISO of Debian with many things working, however some things are left to be desired : Resume keyboard (tried with script - failed), fix for keyboard keys layout, and the resolution (worked with XRANDR script : working). However, he does not seem either interested in going further or does not have the device to compile against, either way without him we could be stuck with WinBlows on this machine. Until we get him BACK on board, we are stuck in the water... @jekhor ?
Click to expand...
Click to collapse
RN, I use the systemd to fix keyboard resume and very soon I will working on sound driver totally ported from android kernel. Plus I can get the haptic feedback to (partially) works only random left or right motor via using udev rule. Extra, the recent kernel added support for the front facing camera (ov2740).