Related
If you want to install Debian, just follow this step:
1. Download this : megaupload.com/?d=EV1SOKWJ
In the debian folder you should change the installer.sh and bootdeb files by this one
Download them:
installer.sh : mediafire.com/file/6j99zi0g1lu4oxq/ashu11x_installer.rar
Bootdeb : mediafire.com/file/osshm94mo1qhd65/ashu11x_bootdeb.rar
2. After that, copy the debian folder unzipped to the root of your sd-card
3. Than open Terminal and type:
Code:
su
cd /sdcard/debian
sh installer.sh
bootdeb
cd /scripts/onetime.sh
sh onetime.sh
That's it!
Credits:
ashu11x
An other way to install it
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
Download Linux Installer here:
uk.androlib.com/android.application.com-galoula-linuxinstall-tFjz.aspx
Install it
Press "Menu" button and choose "Setup".
The configuration apper, the defaults settings work without touch anithing : Debian Leny into a 500M loop file named "Linux.loop" in th sdcard. for lunch this Linux, the script name is "linuxboot".
Detailled functions :
- Install into LOOP file
Check to box if you want use an loop file, a loop file, is a virtual disk, same as image of hard drive. The loop file can be in any directory. I recomand to put this loop file into sdcard with an extension ".loop".
- Server
Name or IP of download server. If this option is empty, the default server is used. To install ubuntu, leave emtpy.
- Distribution type
Type of distibutions, actualy, Debian or Ubuntu.
- Distribution version
Version in type distribution. Warning ! Please check your version with a real type ! Debian can be Lenny or Squeeze, but no Dapper or Jaunty ! This two end, is Ubuntu version !
- Script to lunch Linux
The command to lunch Linux. you can choose own command to lunch. It permit to install Lenny into file Lenny.loop with script name bootLenny and install. after that install debian squeez or Ubuntu Jaunty into a partition of your SD card, and use an JauntyBoot to lunch jaunty. You have two Linux distributions on the same phone !
- Install into (loop)
Enter full path for the filename used as loop. I recommend to /sdcard/myfile.loop
- File size
The size of file allowed for loop. The size is alocated directly, no possible to change or have an dynamic size !
Click to expand...
Click to collapse
The full site with pictures
android.galoula.com/en/LinuxInstall/
where is the /scripts/onetime.sh
http://forum.xda-developers.com/showthread.php?t=1129803
http://forum.xda-developers.com/showthread.php?t=996746
http://forum.xda-developers.com/showthread.php?t=954807
ccownu said:
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
The full site with pictures
android.galoula.com/en/LinuxInstall/
Click to expand...
Click to collapse
on My P500 that one sucks, it worked on 2 gb not on 8 gb, but as told its an rc
Or just do this: ← How to Build CHROOT ARM Ubuntu Images for Android! (UBUNTU ONLY) SHALL WORK ON DEBIAN I THINK!
How to Install Busybox on your Android! →
How to Install Ubuntu on Android!
Posted on February 1, 2011 by admin
For those of you who want to install Ubuntu on your Android smartphone or tablet device, here’s our universal guide on how to do it. (This guide is based off my original guide at NexusOneHacks.net)
*Note – This guide should work on most “rooted” Android smartphones/tablets with no further modification.
We will be running Ubuntu “chrooted” under Android OS, which just means that we will be running a “virtual” Ubuntu OS that runs on top of the Android OS. Your Android OS will work fully (e.g. your phone will keep working normally) while the Ubuntu runs on top of it.
First of all, you should have your Android device “rooted” because you need root access to run Ubuntu off your Android.
Second, your Android OS must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it.
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
How do you know this? Just try installing Ubuntu and if it doesn’t boot, your Android device needs a kernel with loop device support. Otherwise you are fine.
How to Install Ubuntu on Android! (Windows)
First, download the following Ubuntu.zip file (from a preferred mirror), unzip and copy over the whole ubuntu directory to the SD card of your Android smartphone/tablet device:
Download ubuntu.zip http://downloadandroidroms.com/files/get/Nhi9EJWSw7/ubuntu.zip
(Turn USB storage ON then copy over the Ubuntu folder to the root directory of your SD card.)
(What it looks like after copied over to the SD Card)
1) Again, make sure you have your Android smartphone/tablet “rooted”!
2) You must have Android SDK installed or have access to adb.exe.
3) Make sure your Android phone/tablet is in debugging mode. Go to Settings->Applications->Development and make sure USB Debugging is checked ON.
4) Connect your Android device to your computer via USB cable and set the USB mode to “Just Charge”.
5) Your Android device should be recognized as “ADB Device” under Device Manager. If not, install appropriate drivers.
For all HTC Android smartphones/tablets (such as G2 Phone, Nexus One), you can download Windows drivers here:
HTC Windows 64-bit driver download – Click Here to Download Driver
HTC Windows 32-bit driver download – Click Here to Download Driver
6) Open up a command prompt by typing “cmd” under Start->Search programs and files.
7) Browse to your SDK directory where you installed the Android SDK:
8) Then go into platform-tools directory:
9) Type “adb devices” to double-check your Android device is recognized.
In this example, I used an HTC G2 Phone, which shows up at “HT09SR204261″. This is fine. However, if you get an empty device, that means you didn’t install the drivers for your phone/tablet correctly. (Go back to #5)
10) Type “adb shell” to enter the Android shell.
Then type “su” to enter super user mode, then type “cd /sdcard” and “cd ubuntu” to enter the ubuntu directory in your SD card of your Android device.
11) Next, type “sh ubuntu.sh” to run the script which will basically get your Ubuntu image ready to run on your Android smartphone/tablet.
If you get error messages, don’t worry and keep going.
12) Type “bootubuntu” to enter Ubuntu. (Next time you enter Ubuntu, you just need to type “bootubuntu” from your /sdcard/ubuntu directory, no need to run ubuntu.sh again.
If you got “[email protected]” at this point, congratulations! This means your Android OS comes with loop device support and Ubuntu is now running “chrooted” on top of your Android OS!!!
However, if you failed at this point, your Android OS probably doesn’t support loop devices, try installing another ROM or compiling your own kernel with loop device support.
How to Install Programs on your Ubuntu!
Once you’ve got Ubuntu running on your Android device, it’s time to install some Ubuntu packages(or programs).
Type “apt-get update” to update, this is the first thing you will need to do before installing any new programs.
How to Install OpenSSH-server on your Android Ubuntu!
Type “apt-get install openssh-server” to install OpenSSH-server. What is OpenSSH-server? If you want to connect to your Android Ubuntu via an IP address (and SSH into it), you will want to do this.
How to Install TightVNCServer on your Android Ubuntu!
If you want to access the GUI of your Android Ubuntu, you can install TightVNCServer, which allows you to access the Android Ubuntu via Android VNC app on your Android smartphone/tablet or even access it remotely from your desktop computer.
Type “apt-get install tightvncserver” to install.
How to Fix Language Issues
Above is after I connected to my Android Ubuntu via SSH2. Well, for some reason my default language switched to German. To fix that, just type “export LANG=en_US.UTF-8″:
How to Install LXDE!(optional)
Next, we will install LXDE (Lightweight X11 Desktop Environment). Although we can use Ubuntu’s default GNOME (and trust me I love that), LXDE takes up less memory so our GUI access will be faster.
If you like GNOME, you can skip this step though.
Type “apt-get install lxde”
Next, let’s setup xstartup file so that when TightVNCServer is started, the LXDE runs instead of GNOME:
Type “cat > /root/.vnc/xstartup”
Then type:
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then hit Ctrl+D twice and enter to save the file.
How to Start TightVNCServer!
Next, let’s start the TightVNCServer and connect to it from our Android phone and my Windows 7 desktop:
Type “export USER=root” and “vncserver -geometry 1024×800″.
Here, you can change the resolution settings 1024×800 to the resolution of your liking.
Now your TightVNCServer is ready to accept any incoming connections from your phone or computer. Just point to the correct IP address and use port number 5901 to connect.
On your Android smartphone, just download the free app “Android-VNC-Viewer” and set the IP address to “127.0.0.1″ and port number 5901 to connect.
And you should be able to get into your Ubuntu like this:
You can also use desktop software like TightVNC Viewer and connect to your phone.
Do “ifconfig” to find out what your IP address is in your Android Ubuntu.
In this example, mine was connected to “192.168.1.131″.
Then connect to “192.168.1.131:5901″ on your TightVNC Viewer:
Here’s LXDE running on my desktop off my G2 Phone’s Ubuntu:
Troubleshooting
Ubuntu not running?
Try typing “cp” under Android shell and if you get an error message, it means you need to install Busybox. Install Busybox and try again.
Final Thoughts
As said in the video, there will be a lot of improvements in the speed of Android devices in the near future. This year, there will be a slew of dual-core 1Ghz processor-equipped Android devices being introduced. Which just means our Android Ubuntu will run faster and faster.
Hi,
I always had problem with mtp and GB on linux. With the ICS update I couldn't even find my device listed by nautilus. I'm a little bit tired of using Airdroid, wich seems to be slower now and I never liked to download the pictures from it as a zip file.
for those who like to MTP transfer from xperia NXT series on Mint or Ubuntu:
add this repository Olci PPA launchpad.net/~olci/+archive/ppa1
it contains the new libmtp library, the new mtpfs and gmtp
with this command: sudo add-apt-repository ppalci/ppa1
then update & upgrade if already installed
or
update and install libmtp libmtpfs gmtp
from terminal launch gmtp
wait for a little bit (it takes a while)
once in gmtp go to preferences and set your directories for upload download
and there you go
finally can control and backup everything in your sd to your linux system
there is a smile on the command
sudo add-apt-repository ppalci/ppa1
how can I remove it?
Damn that's my ppa if anyone got questions or issues on that ppa
I can help
Sent from my haida
Thank you so much for the ppa and your job, a friend sms that to me today as we were searching for mtp on mint. I tried it worked and i wanted to share it.
Sent from my ST25a using xda app-developers app
Or you could use Airdroid for file transfers. It's what I use on my Linux laptop.
uao said:
there is a smile on the command
how can I remove it?
Click to expand...
Click to collapse
Code:
sudo add-apt-repository ppa:olci/ppa1
damn can't fix
Sent from my haida
@ The Alpha Gamer
As I wrote I already use airdroid and I'm tired of it. Still it's out topics.
This thread is about xperias, MTP and linux which are working thanks to that ppa
Sent from my ST25a using xda app-developers app
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Thanks. Very useful! :good:
for me and the HTC One X it wont work.....
-Happy Feet- said:
for me and the HTC One X it wont work.....
Click to expand...
Click to collapse
Did work previously?
maybe restart the adbd on the phone.
Can you test in Recovery, Cwm has an extra button for restarting.
Maybe Stock too.
Illidan Pornrage said:
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Click to expand...
Click to collapse
Fraid it didn't work. End up with various errors and randomly appearing devices. Plus, the original error reappears eventually. Please help!
If you give me some Info around the issue, like what you intended to do and if it worked previously, I could help you.
FIX adb offline problem
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window
------------------------------------
After that you every thing will be OK
this solved my problem
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
ciano865 said:
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
Click to expand...
Click to collapse
as far as I know adb doesn't work in bootloader mode.
MadMan29729 said:
as far as I know adb doesn't work in bootloader mode.
Click to expand...
Click to collapse
How can I push file to phone it doesn't boot ?
I think thats intentional, bootloader mode is the mode corresponding to fastboot for directly flashing, deleting, formatting, stuff like that in the most basic environment. Try recovery or normal boot for adb, which is for debugging, shell access, backup, filetransfer and so on.
(More info for more specifics)
Thanks, my mistake not using recovery
from Nexus 4 with Tapatalk
took me a bit to get into the thing myself after > 4.2 update
i'm on ubuntu
i had to use the terminal command
Code:
android update sdk --no-ui
a couple of times to get the thing actually updated. using just
Code:
android update sdk
wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.
then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),
it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and
Code:
sudo rm adb
then navigate over the folder whereeveryouputyoursdk/platform-tools/ and
Code:
sudo cp adb /usr/bin
that should be the new version of adb into /usr/bin. remember, do all that after running the
Code:
android update sdk --no-ui
a few times
peace
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
ah great i thought there was an issue with my adb and you wrote the solution
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
Thanx man you saved me !!!
Sent from my Micromax A57 using xda app-developers app
Thanks
I still had this problem on OSx and Ubuntu in cli.
what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)
killall adb
then turn off USB debugging on device.
start new adb (doesn't work nothing to connect to)
then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"
test adb devices and should show 'device' instead of 'offline'
or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.
yay!
svs57 said:
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
Click to expand...
Click to collapse
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.
Hello!
I wanted to know if it has the same effect updating Ubuntu Touch via Terminal or is it better to flash the daily build without wiping to keep updated?
Updating Ubuntu via Terminal: sudo apt-get update && sudo apt-get upgrade
via computer: phablet-flash -l
In my opinion it does the same but I'm not 100% sure.
Apt-get just updates the packages. For some updates it requires a full image upgrade. Which Canonical will implement to be done within Ubuntu Touch by the end of august.
Sent from my LG-LS970 using xda app-developers app
blmvxer said:
Apt-get just updates the packages. For some updates it requires a full image upgrade. Which Canonical will implement to be done within Ubuntu Touch by the end of august.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've figured out, you can add a repo to update the whole system (except some system packages like the kernel) as well.
I've written this down in my tutorial thread.
Hello community!
For those who are interested in installing a linux system (debian) on a NON-ROOTED Android device:
I managed to install GnuRoot referring to this tutorial:
https://www.xda-developers.com/guid...a-gnulinux-environment-on-any-android-device/
At first i had graphical errors when starting LXDE (like missing icons) due to missing libraries during the installation process.
I show you the steps for installing it, referring to above tutorial, but i added some new terminal commands, because there were libraries and dependencies missing when installing LXDE.
1) First install GnuRoot and XSDL server from playstore.
2) Let GnuRoot start and doing its installation. Then type in following terminal commands:
apt-get update
apt-get upgrade
dpkg-reconfigure tzdata <----- if you wanna change your locales
apt-get install libffi6 <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
apt-get install execstack <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
execstack -c /usr/lib/i386-linux-gnu/libffi.so.6 <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
apt-get install lxde-core <------- alternatively apt-get install lxde (for full LXDE with its apps)
3) start XSDL and make your configs (resolution etc.), let it run in the background
4) now type in GnuRoot following terminal commands:
export DISPLAY=:0 PULSE_SERVER=tcp:127.0.0.1:4712
startlxde &
5) switch back to XSDL and then wait until the GUI (aka LXDE) starts
It still shows some bugs like "No Session for PID # xxxx" whenever i log in. So i hope that i can get help to install it better (correctly) from the community.
Alternatively:
In the last few days i managed to let GnuRoot Debian run LXDE and connect to it via VNC viewer by running a VNC server locally. So if you dont want to use XDSL, but VNC instead, you can follow these instructions:
Download "GnuRoot Debian" and "VNC Viewer - Remote Desktop" in playstore.
Start GnuRoot, let it do its things and then type in the these shell commands:
For installing LXDE:
apt-get update
apt-get install apt-utils
apt-get install dialog
apt-get install sudo
sudo apt-get install libffi6
sudo apt-get install execstack
sudo execstack -c /usr/lib/i386-linux-gnu/libffi.so.6
sudo apt-get upgrade
sudo apt-get install lxde-core
For installing VNC-Server:
sudo apt-get install tightvncserver
su - root
tightvncserver :1 (<---- just start the VNC-Server in order to create the xstartup-file)
sudo apt-get install nano
nano ~/.vnc/xstartup
an editor will show up and add this line at the bottom of the xstartup-file
/usr/bin/lxsession -s LXDE &
save the file and continue with these commands:
vncserver -kill :1 (<--- kill the server)
tightvncserver :1 -geometry 1280x720 -depth 24 (<--- start it again with this resolution, you can choose any resolution you want)
Now open VNC-Viewer and create a new item in order to connect to the VNC-Server
type in this adress: localhost:1
There you go... you are connected to the VNC-Server running by GnuRoot Debian. Have fun... I installed LibreOffice and Gimp as desktop solution. Working great with the Halo keyboard and with a bluetooth mouse
Does the keyboard work?
boofman said:
Does the keyboard work?
Click to expand...
Click to collapse
Yes. Halo Keyboard works, as well as the touchpad. It simulates a "right click" of a mouse by touching the pad with two fingers. But i can't recommend using the touchpad. I use a Bluetooth mouse, and it works well with GnuRoot. You can work just like with a normal Linux environment.
Furthermore I got Libreoffice, GIMP, Firefox ESR and Evince (pdf-Reader) working. Unfortunately i didnt get Chromium (32-bit) working.
ok what about the wacom pad i.e. the create pad itself? does it work in linux?
Okay, so it works similar to a Virtualbox, but is more lightweight as it uses the Linux system that's running behind android in principle, right? Well, it makes the Android YB much more better than the Windows variant if that's the case, as it makes it a lot easier to use a real desktop environment inside of Android without having to reboot..
I'm weighing the pros and cons of going through all these trouble though, as the only reason I would want to have a linux desktop running would be more about using Office apps more than anything, and now with MS Office for Android, that would shorten the gap. I love Linux and have a Mint dual boot on my other machine, but the advantages in using the YB ultraportable Android with MS Office should suffice..
@bisharat:
I tried the wacom pad within linux using gimp. but it recognizes the pen only as normal mouse input. sometimes it lags, so drawing (on a professional base) doesn't work that well. and: in linux the pressure used with the pen (i.e. the intensity of the drawn line) isn't recognized as well.
@boofman:
The reason why i installed a linux system on the yoga book was: i tried every reasonable office solution in the app store or other sources, but i haven't found one that can work offline and which can work nearly as good as LibreOffice. As i have to read a lot of Magazines / Journals and as i have to write a lot of papers and making presentations, the installed linux system sufficed as Office solution.
And i plug in an external monitor (if needed) through the mini-hdmi, so i can have a light-weight mini office computer upon my android system for work. I think this is a good alternative, as I still don't see any possibilities to dual boot this device (aka Android and Win10).
-- message deleted --
ok so if possible can u post a video on how to install it and how to uninstall it (in case anything goes wrong)?
bisharat said:
ok so if possible can u post a video on how to install it and how to uninstall it (in case anything goes wrong)?
Click to expand...
Click to collapse
i just wrote a small tutorial in the first post. its similar to this tutorial:
https://www.xda-developers.com/guid...a-gnulinux-environment-on-any-android-device/
but i added some new commands.
uninstalling is very easy. just uninstall it through the application manager of the yoga book and delete the "GnuRoot" folder in your sdcard.
Tiggi2017 said:
@bisharat:
I tried the wacom pad within linux using gimp. but it recognizes the pen only as normal mouse input. sometimes it lags, so drawing (on a professional base) doesn't work that well. and: in linux the pressure used with the pen (i.e. the intensity of the drawn line) isn't recognized as well.
@boofman:
The reason why i installed a linux system on the yoga book was: i tried every reasonable office solution in the app store or other sources, but i haven't found one that can work offline and which can work nearly as good as LibreOffice. As i have to read a lot of Magazines / Journals and as i have to write a lot of papers and making presentations, the installed linux system sufficed as Office solution.
And i plug in an external monitor (if needed) through the mini-hdmi, so i can have a light-weight mini office computer upon my android system for work. I think this is a good alternative, as I still don't see any possibilities to dual boot this device (aka Android and Win10).
Click to expand...
Click to collapse
Thanks for the feedback.
Yeah, I can see where you are coming from, and as a matter of fact, I use my YB Android pretty much the same as you do: hook it up to a monitor and sometimes use it on a projector for presentations.
The issue I have with LibreOffice is that there are times the formatting gets messed up when opened in MS Office (where majority of my officemates use) unless saved in a PDF Format which you can't edit.
For now, MS Office for Android works though a bit lacking in features as compared to the Win10 version, but gets the job done in a pinch.
Dual-boot is one thing we can look into, but for now though, your solution is worth a try and should be a better option.
boofman said:
Thanks for the feedback.
Yeah, I can see where you are coming from, and as a matter of fact, I use my YB Android pretty much the same as you do: hook it up to a monitor and sometimes use it on a projector for presentations.
The issue I have with LibreOffice is that there are times the formatting gets messed up when opened in MS Office (where majority of my officemates use) unless saved in a PDF Format which you can't edit.
For now, MS Office for Android works though a bit lacking in features as compared to the Win10 version, but gets the job done in a pinch.
Dual-boot is one thing we can look into, but for now though, your solution is worth a try and should be a better option.
Click to expand...
Click to collapse
yeah, thanks. the thing with ms office is that you have to have an account the the features arent that superb. but you are right, most people use ms office and the format is messed up when continuing working with LibreOffice. thats why i only write documents and make presentations with LibreOffice. when publishing i always convert to pdf.
alternatively i also tried crossover with.... well... not so good results. its lagging and therefore disturbing the workflow. furthermore i just got Libreoffice working with crossover (more or less working...), gimp or other free graphic apps dont work.
having Linux on an Android system is a good way to have an Office computer in one's pocket. i also look forward to a possibility to dual boot the device.
deleted
Tiggi2017 said:
Hello community!
For those who are interested in installing a linux system (debian) without root:
I managed to install GnuRoot referring to this tutorial:
https://www.xda-developers.com/guid...a-gnulinux-environment-on-any-android-device/
At first i had graphical errors when starting LXDE (like missing icons) due to missing libraries during the installation process.
I show you the steps for installing it, referring to above tutorial, but i added some new terminal commands, because there were libraries and dependencies missing when installing LXDE.
1) First install GnuRoot and XSDL server from playstore.
2) Let GnuRoot start and doing its installation. Then type in following terminal commands:
apt-get update
apt-get upgrade
dpkg-reconfigure tzdata <----- if you wanna change your locales
apt-get install libffi6 <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
apt-get install execstack <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
execstack -c /usr/lib/i386-linux-gnu/libffi.so.6 <------ this is one of the missing libraries, otherwise LXDE will have errors during its installation
apt-get install lxde-core <------- alternatively apt-get install lxde (for full LXDE with its apps)
3) start XSDL and make your configs (resolution etc.), let it run in the background
4) now type in GnuRoot following terminal commands:
export DISPLAY=:0 PULSE_SERVER=tcp:127.0.0.1:4712
startlxde &
5) switch back to XSDL and then wait until the GUI (aka LXDE) starts
It still shows some bugs like "No Session for PID # xxxx" whenever i log in. So i hope that i can get help to install it better (correctly) from the community.
Click to expand...
Click to collapse
Edit: I see that it's via an Android device. Never mind
Was this done on the Android version or the Windows 10 version of the Yoga Book? Because this may be the breakthrough of getting Android on the Windows 10 version, and then enabling me to do research with a custom ROM.
Yoga Android: "It still shows some bugs like "No Session for PID # xxxx" whenever i log in. without the possibility to close the message windows." smae as the starter herein. anyone else? how to solve that?
s01q said:
Yoga Android: "It still shows some bugs like "No Session for PID # xxxx" whenever i log in. without the possibility to close the message windows." smae as the starter herein. anyone else? how to solve that?
Click to expand...
Click to collapse
For me, i can close that error message. But it is still annoying and i cannot get rid of that.
@nan0s7
Unfortunately it is for the android device only. Still waiting for a possibility to dual boot the device. I hope for a breakthrough soon....:fingers-crossed:
Tiggi2017 said:
For me, i can close that error message. But it is still annoying and i cannot get rid of that.
Click to expand...
Click to collapse
stupid me. Can close it
Tiggi2017 said:
@nan0s7
Unfortunately it is for the android device only. Still waiting for a possibility to dual boot the device. I hope for a breakthrough soon....:fingers-crossed:
Click to expand...
Click to collapse
Hope so... this device has so much potential =D
nan0s7 said:
Hope so... this device has so much potential =D
Click to expand...
Click to collapse
but then dual boot with linux or HaikuOS
s01q said:
but then dual boot with linux or HaikuOS
Click to expand...
Click to collapse
I'm aiming for Android first ;P