Related
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 have been trying for a few weeks to install kali linux on my lg g3. So far with no luck I have tried every guide on the internet but all have failed me can someone give me a detailed walkthrough on how to do so? my sd card is formatted and partitioned to fat32. I wish to install kali to the second 14 gig partition I made and named ext2. my phone is rooted with busy box installed it is the lg g3 S990 runing stock rom 5.0.1
anyone have any experience with this?
Here are some screen shots
Here are some screen shots
I don't think that you can..... They don't offical support it and there is a lot of things you have to take into effect. For example kernel, arm version, and hardware, wifi chips, touch screen drivers and a WHOLE LOT MORE!.
What would you suggest then? I'm debating getting a nexus 7 and installing nethunter on it would that be better??? I've been able to get quite close to having it work
turatt said:
What would you suggest then? I'm debating getting a nexus 7 and installing nethunter on it would that be better??? I've been able to get quite close to having it work
Click to expand...
Click to collapse
You can try that
GOOD NEWS (maybe)
I am able to get kali running through the complete linux installer app BUT it appears to be missing all pentesting tools and has no gui because vnc viewer wont connect but it does at least behave the way the app makers say it should :/
turatt said:
I am able to get kali running through the complete linux installer app BUT it appears to be missing all pentesting tools and has no gui because vnc viewer wont connect but it does at least behave the way the app makers say it should :/
Click to expand...
Click to collapse
Well, that's a start...
You can try opening a terminal and running: sudo apt-get install aircrack-ng
It says files are corrupted and cannot be read :/ ithink I will try limbo pc emulator instead will post the results
turatt said:
It says files are corrupted and cannot be read :/ ithink I will try limbo pc emulator instead will post the results
Click to expand...
Click to collapse
OK
So after many weeks of working day and night I finally have time to sit and tinker will post updates in the coming days
turatt said:
So after many weeks of working day and night I finally have time to sit and tinker will post updates in the coming days
Click to expand...
Click to collapse
Have you just looked into installing it onto like raspberry pi or a Chromebook or something? It seems pretty easy..... Plusnit might work better then the phone.
If I can't get to work ill be switching to a nexus seven with nethunter. I found a guide on how to run kali in limbo pc emulator and it appears to work to some extent but I get no gui nothing. I fear the iso file may be corrupted. Ill post screenshots next
turatt said:
If I can't get to work ill be switching to a nexus seven with nethunter. I found a guide on how to run kali in limbo pc emulator and it appears to work to some extent but I get no gui nothing. I fear the iso file may be corrupted. Ill post screenshots next
Click to expand...
Click to collapse
Just install gnome fallback or something....
Or open a terminal and try running "startx"
Here are my screenshots.
http://ikrami.net/2014/05/26/kali-linux-android/
This is the guid I have been using^
Just tried again with a new iso and limbo stopped working I will try reinstalling and wipeing cache in recovery.
turatt said:
Just tried again with a new iso and limbo stopped working I will try reinstalling and wipeing cache in recovery.
Click to expand...
Click to collapse
It could just be the arm version of our phone.... What are you trying to do with Kali?
Just run it I have a pwn box for mobile hacking so I can bluesnarf and do alot of fun things. I'm doing freelance pin testing so I thought it would be nice to be able to do those things on my phone without having to lug my laptop out
turatt said:
Just run it I have a pwn box for mobile hacking so I can bluesnarf and do alot of fun things. I'm doing freelance pin testing so I thought it would be nice to be able to do those things on my phone without having to lug my laptop out
Click to expand...
Click to collapse
OK, cool
Then I guess the nexus 7 is your best guest unless you get something like a Samsung S2 and put it in monitor mode and use aircrack-ng. Also the raspberry pi thing is pretty good if your like pretty handy you can wire up a battery, pi, and screen then just use a wireless keyboard.
S2 link: https://www.google.com/url?sa=t&sou...mgJhCRpHtESmUYXTw&sig2=IeGml16hwDKXeV9V7JXwRg
You can install kali linux on linux deploy and run with android VNC
I am running with linux deploy it on my AT&T 3g.
Im pretty sure your problem is in your configuration on preferences. Generally the SD is formatted to FAT which has maximum image file size 4095 MB. So pretty much if you want kali tools then hypothetically you could reformat your SD or external to ext4. There is also a permissions problem because of the image location. Here's how I got around it for now, I just started altering this phone 2 days ago so I'll keep you updated if you want. I moved the environment location to a folder in SD and it has consistently held up to 6000MB which is plenty for the os, necessary additions and a few fun kali tools.
Here's my mini pictorial, it's only my second post so maybe this will help.
Just do the settings like mine, Wait forever while it installs then after it finishes hit reconfigure. It takes a couple of minutes to reconfigure then you press start and wait until it's finished loading, press your home button, open VNC, make sure your port is 5900 and default password is "change me"
Open up a terminal and type "sudo su" make a password, update and make sure you have fun.
When you're finished go back to linux deploy, press stop and then use the menu button to exit the app
Announcing Sailfish for the Sony Xperia SP
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Update 15 Feb 2016
I've uploaded a new version of SailfishOS 2.0.0.10 to the Mega folder, called sailfishos-huashan-release-2.0.0.10-1.zip. This is again based off CM-12.1, the same release as stated below. This release fixes a kernel bug which lets a lot of the Sailfish system crash. This also fixes the wlan connectivity, startup-wizard which sets the themes, on-screen keyboard not popping up, and SIM unlock never asked. I've got a fix for the backlight in the works.
Update 14 Feb 2016
A very experimental CM-12.1 based SailfishOS 2.0.0.10 build is uploaded to the Mega folder linked below.
This version is based off cm-12.1-20160212-NIGHTLY-huashan.zip. I want to stress that many things in this build are broken.
Update 05 Feb 2016
This port is heavily outdated. I do not have much spare time on my hands to continue porting but I will try to post a nightly version soon.
This version was based on Sailfish 1.1.6 and CM-11.0, but the world has moved on to Sailfish 2.0 and CM-12.1, and so must this port.
There's a photo up on imgur:
http://i.imgur.com/Vg3SZ6w.jpg
Special thanks to:
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Everyone from the SailfishOS team/community, sledges and mal- in particular.
Known issues:
Half the backlight doesnt work, this is clearly visible at the top of the screen
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Settings hangs for few seconds on first start (this seems to be related to bluetooth not being set up)
What works:
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi, GPS (does take a while to get a fix though), most of the sensors (proximity, lightsensor etc)
The half of the display backlight that does work is adjusted based on lightsensor input.
Charging, bottom ledbar basic functionality, audio works, audio via 3'5 jack also works.
Installation:
Insert default warranty void message here. Your warranty is now void
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an offical Sailfish OS build, and the Xperia SP is not the Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, search for it first on bit.ly/port-bugs, if your bug is not yet there, you can add it there or post it in this thread (I'll try to keep the xda thread and bugzilla in sync).
The Sailfish OS image does not provide recovery, and since the Xperia SP does not have a recovery partition, you need a seperate bootimage with only recovery on it to flash cm/stock/sailfishos upgrade.
The Sailfish OS image is based on a specific version of Cyanogenmod 11, which you will need to flash first.
You can find all the required files in a Mega folder: http://mega.nz/#F!7YhSTDIA!Akpjs8s3qT5_nEkN04fQ-Q
You can find a bootimage with only TWRP recovery in it called recoveryboot.img
This image can be flashed with fastboot (with phone turned off, hold vol up and plug in usb), then `fastboot flash boot recoveryboot.img`. After that reboot the phone (fastboot reboot), and it will boot into recovery. If you already have recovery from cm, then you can use that as well.
First do a full wipe (make a backup first if needed, TWRP can do this , then install CM11, the specific version you need is called: cm-11-20150712-NIGHTLY-huashan.zip
There is no need to reboot cause you wont use CM11 anyway, so just proceed and flash the Sailfish OS image, which is called: sailfishos-huashan-release-1.1.6.27-UNOFFICIAL-maikel-201508201214.zip
Flashing Sailfish OS is not as fast as flashing cm11, but it shouldn't take more than 10 minutes.
Then reboot. The first boot may take some time, during which the Sony logo is not displayed (WIP).
If the boot takes more than, lets say five minutes, try a reboot. You can power off the device by holding the power button until the LED bar turns red or the display brightness goes back to full, when the leds and display turn off the device is powered off.
If this doesn't work you can remove the back cover and press the little button in the little hole for 5 seconds, the device will vibrate thrice and the phone will be forced off.
If you want to return to your previous rom or restore a backup, use the recoveryboot.img using the commands stated at the top of this document, to boot into TWRP.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Sources
In order to comply with the GPL, the kernel sources used for this port are available here:
CM-11.0 based port: https://github.com/maikelwever/android_kernel_sony_msm8x60
CM-12.1 based port: https://github.com/maikelwever/android_kernel_sony_msm8960t
edit: make links + sailfish 2.0 notice, kernel sources, 2.0 link
You rock! Very interesting project. Sailfish is an unknown world for me (and for most of us I think), I might try this ROM out sooner or later.
Why do we need to install CM11 first? Is it based on it?
Goob job bro!!!!
But I'll try this port later since it's kinda buggy
Hope you will fix those bugs.
Tomoms said:
Why do we need to install CM11 first? Is it based on it?
Click to expand...
Click to collapse
SailfishOS uses libhybris to communicate with the hardware, which in turn is talking to the Android HAL (like hwcomposer), to avoid having to write drivers for each phone, which would be pretty much impossible due to the proprietary blobs used on almost every phone.
The libhybris build included in this SailfishOS port is based on CM11, so that's why you need that.
CM12 based SailfishOS is currently experimental, when that gets more stable I will try to make a CM12 based build.
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
boylush said:
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
Click to expand...
Click to collapse
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
maikoool said:
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
Click to expand...
Click to collapse
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Tomoms said:
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Click to expand...
Click to collapse
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
maikoool said:
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
Click to expand...
Click to collapse
man i was waiting for this thing :fingers-crossed:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
will follow this thread closely...........
finally something new and different to use.
cheers
avi.singh9993 said:
will follow this thread closely...........
finally something new and different to use.
cheers
Click to expand...
Click to collapse
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
This looks really good, if it will ever be in daily driver state this will be my go to rom
sledges said:
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
Click to expand...
Click to collapse
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Why don't you post please? DIT - doing it together!
sledges said:
Why don't you post please? DIT - doing it together!
Click to expand...
Click to collapse
well i asked my friend to post it,
many people saw it but unfortunately not much of a positive feedback.
now it's onto developer and his hardwork to develop and make it atleast daily driver. then some people will be interested in trying it
Tomoms said:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
Click to expand...
Click to collapse
I agree totally that it's the dream of a geek. I've noted all your comments and will try to fix them. Thank you very much for taking the time to test!
Spasik said:
This looks really good, if it will ever be in daily driver state this will be my go to rom
Click to expand...
Click to collapse
That's what I'm aiming for too!
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Sorry, but I couldn't care less about Facebook. I'm pretty convinced that everyone that is willing to try something like this is already on XDA anyway. Hopefully the work related part will be better possible when Android app emulation or something similar finally makes it to community Sailfish builds.
PS: I've been a bit busy with other things lately, sorry for not responding that fast. I'll try to roll a build with fixes and the latest Sailfish (1.1.7.28) asap.
This has changed the mac of my device
can I ask how's the development going?
If someone could port the only rom i would like to be ported on the SP: ColourOS, it will be AMaZING
I have a few devices lying around; Optimus One-KitKat, Nexus 4-Lollipop 5.1.1, Nexus 5-N/A(waiting on digitizer) and a Zenpad 10-Lollipop 5.0.1.
I'm looking to add wifi driver(s) to the kernel of one, or all of them.. but I'm not sure where even to start.
I have Android Studio installed on Windows, I've got a Kali Boot laptop.
I can install anything on either that are required, I'm assuming the Kali would be best suited.
If you guys could get me started with something base.. like source files? I'm more than willing to attempt this mission myself...
Maybe come back here with small questions or "Ohshi- I broke it, what do I do?!"(honestly don't think that'd happen, but you never know)
Right now, all I'm looking for is what I need to install, and where I can find source files and such.
Please and thank you guys.
Edit: Currently my mission is to take a driver's .bin from linux and change it to .ko or equivalent for android so I can insert it in and have my external dongle work... any ideas?
Edit2: Turns out I can't do it that way, But now I've got the Source for both Kernels. My Tablet, and the Linux I'm running with the drivers built into it. So I have access to the drivers themselves. I'm just trying to figure out how to recompile them for Android.
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