First, I didn't know if this should go in development or general since most of the people who are going to be on Ubuntu will be devs, but hopefully this will be useful for everyone.
Honeycomb changed a lot of things. Most of the changes are awesome (as we know) but some of them have made certain things frustrating. Honeycomb marked the move from USB Mass Storage to MTP (media transfer protocol). Although for Windows users it actually works pretty well, for Linux users it doesn't...at least at first.
If anyone has hooked up their Xoom to a Ubuntu box then they know at first nothing happens. There is no selection on the tab to "mount" USB Mass Storage because it is not supported (which I thought Honeycomb was supposed to support both so this may change) It's like the computer doesn't even recognize anything is plugged in.
So this was very frustrating but I have put together a solution. Previously I was using a GUI interface called gMTP to connect to the Xoom and transfer files. This was an ok solution and it worked but I would still rather just use it in Nautilus like every other drive I use. Ok so starting here I will just post the commands and then explain after so no code gets lost.
Start with installing a needed program for all of this to work
Code:
sudo apt-get install mtpfs
Next we will create the device rules, so Ubuntu recognizes it as a USB device.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
NOTE: Some of you may have already added the Vendor ID. If you don't this file will start off blank and then you need to add this next line. If it does not come up blank, then make sure you have a line with Vendor ID 22b8 and 18d1 (for bootloader which uses a different VendorId) and you are all set.
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
You might need to start a new terminal for this change to take effect for adb and bootloader access.
make the mount point and take ownership:
Code:
sudo mkdir /media/xoom
sudo chown user:user /media/xoom
NOTE: "user" in the above code is literally your user name for your box.
ANOTHER NOTE: if you stopped here you could mount by typing mtpfs /media/xoom -o allow_other and unmount by typing fusermount -u /media/xoom...but that's no fun
add the mount point to your fstab:
Code:
sudo gedit /etc/fstab
In the first unused line available you might want to type a comment like:
Code:
# mount point for moto xoom
then add this line after it:
Code:
mtpfs /media/xoom fuse user,noauto,allow_other 0 0
Next modify fuse.conf to allow_other:
Code:
sudo gedit /etc/fuse.conf
uncomment the last line which should read:
Code:
#user_allow_other
uncomment this line by removing the '#' symbol.
add your user to the fuse group:
Code:
sudo gedit /etc/group
a long file will open, press CTRL+F to bring up the find dialog and type
Code:
fuse
close the dialog and fuse should be selected and visible.
At the end of that line with no space add your user name.
Save that file. Close it.
Lastly reboot your computer.
Now when your computer restarts, if you look at your "Places" menu you will see a Drive marked with 'xoom'
Plug in your xoom, and click on xoom in Places.
Nautilus should open with all your files that you have on your device. It will also place a mounted drive icon on your desktop. If you would like to unmount, right click on that icon and click unmount.
As you can see this was a pain for me, but hopefully this solution will work for everybody. I know the instructions are really long but follow it and you will feel old school mounting your storage in your file browser.
NOTE: THIS WAS TESTED ON UBUNTU 10.10 ONLY, IF THIS WORKS FOR ANYONE ELSE PLEASE POST YOUR FINDINGS.
Also, I am fairly new to Linux actually, so if there is an easier way to mount the storage in nautilus let me know. This works for me and I just want to help out so please no flames.
Couple things I have also noticed with MTP, when you have the internal storage "mounted" you still actually have access to the files on the device. Plus the file transfer is a lot faster. Usually I had been getting about 4 Mb/s and now I get about 15. Of course this speed difference from what I am used to might be the internal storage vs. SDCard transfer rate diffs.
Last thing, is this might need to modified when the sdcard access comes since there is only one mount point specified.
not trying the artificial bump.
I guess no comments on 228 views means this is working?
Can someone chime'in if this worked for them so I can know'if it works'as is or needs to be tweaked.
Thanks
I got mount up and running last night. Works like a champ. Great work. I was tired of pushing and FTP.
Thanks for the reply. Glad it worked for you too. One thing I need to add tonight to it is the fact that the xoom uses a different vendor'id when it's in the bootloader. The one vendor id if used alone will not recognize the xoom to use fastboot but ill update it when I get home.
FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.
kcrudup said:
FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.
Click to expand...
Click to collapse
So, I'm on 10.04 and not getting segfaults, but after pugging in (xoom is in usb debug mode) and click on xoom in places, ubuntu gives me the error "could not open location file:///media/xoom. Error stating file '/media/xoom': Permission denied"
Would love to get a copy of your recompiled 10.04 mtpfs package as a deb file...
I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb
roberj13 said:
I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb
Click to expand...
Click to collapse
Unfortunately, that's not gonna work for me. I'm 32-bit.
Ill keep looking, for some reason the 64-bit was the only one there.
roberj13 said:
Ill keep looking, for some reason the 64-bit was the only one there.
Click to expand...
Click to collapse
Thanks! If i could ge this to work, it would totally be awesome!
--Q
Most excellent guide!! Thanks you for taking the time to figure this out. I'm on 10.10 so I have nothing else to add.
Works flawless on Ubuntu 10.10 running on an older Mac Pro
Thank you for posting the easy to follow guide.
This is semi-working for me in that I can successfully mount and browse the device, but there are a few problems. One, it locks up Nautilus for 30-60 seconds (grayed out and unresponsive) though it does come back. Two, file transfer speeds are very poor.
I'm trying to load two movies totaling 1 GB right now and the copy dialog says 2hrs 56 min to transfer w/ a speed of 99.7 kb / sec. This is unreliable, however, as the copy dialog is frozen on those metrics.
Build is AMD64, distro is 10.10 upgraded from 10.4.
I appreciate the effort to document this, in spite of my issues. Let me know if anyone has suggestions for a fix and I'll try them.
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I find it odd that Android dosn't play nicely with *nix.. considering they are cousins in the OS family. That it works sooo well with Windows instead offensive IMO
sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I've seen the same thing. Usually an unmount then mount will clear it up.
this did not work for me. i'm getting no application is registered as handling this file
i told nautilus to open it and its saying /media/xoom is not a folder
Using this guide I'm able to mount fine, but I'm seeing a couple issues:
I have my music organized like this:
Artist
-----Artist - Album
----------Music files
When I copy over the top 'Artist' directory to the Xoom's Music folder it works, but, all of the music files have been directly placed in the Xoom's Music folder and the Artist and Artist - Album folders are empty, seems pretty weird?
EDIT: It looks like the Xoom (or MTP?) forces all music files into the root of the Music directory. Even if I try copying the artist folder to the root of the device the mp3 files end up in the Music folder.
EDIT take 2: Nevermind...the Android docs say nested directories are supported for music, and Windows preserves the directory structures fine.
I'm totally unable to copy over movies. I've transcoded a file into mp4 and it seems to copy over but, once the copy is finished the file doesn't show up on the Xoom.
EDIT bonanza: Looks like I'm also able to copy over movies fine through windows...so I guess all my problems are Linux related.
I keep gettting a "Transport endpoint is not connected" error when I try this. I am using 10.04 64-bit. Does anyone know how to resolve this?
Related
Let me say upfront that yes I did read all of unrevoked replies in the dev section.
They mention that the 8/1 leak (ROM I'm currently running) may also have the same USB issues as SkyRaider.
When I plug my phone into my mac, I get a device error message and the option to ignore or (I think cancel). Anyway, if I click ignore, I can see both the SD card and internal storage just fine. I can also see my SD card from my phone and I know adb is working because I recently went into recovery, /mount systen, to remove the old flash.apk for the hulu hack.
So on the surface it appears like my phone is fine except for this error message. I'm curious if any other mac users receive the same error message (never got it before the 8/1 leak). With s-off coming as early as tonight, I don't want a USB brick. Thanks for any help.
Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.
HeyItsLou said:
Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.
Click to expand...
Click to collapse
Hey thanks a lot for the info. I'll run adb shell when I get home and see if this solves the problem. Good to know it wasn't just me.
let me know if that fixes the issue for you
Worked perfect. Thanks!
Glad I could help
i had the same problem, but with a pc. whenever i plug in my phone into my pc, nothing comes up, i hav to go to my computer to open it up. and also i have an extra cd drive that says verizon mobile. do u know if the "rm /system/etc/CDROM.ISO" command works with a PC too?
Hi,
Here is the fourth version. Its not upgradeable, so delete the old /sdcard/ubuntu before, except you know what you are doing and are able to fix upcoming problems by upgrading.
[Hints]
To remove the stupid overlay scrollbars, goto ubuntu shell and type
Code:
apt-get remove overlay-scrollbar liboverlay-scrollbar*
in the next version setupgnome will automatically do that, all which setup gnome befor, do that to get the normal scrollbars.
in gnome goto system -> preferences -> appearance. there to the fonts tab, and there to details. use a resolution of 120 dpi, so you it is a bit more touch friendly
[Requirements]
Archive from http://www.bisme.net/files/xda/ubuntu/ubuntu_b6.tar.gz
Optionall an VNC client like android-vnc
[step by step]
Install the kernel (without you'll not have full functionality, but it'll work)
Extract the ubuntu archive to /sdcard/ubuntu (in adb shell goto sdcard and type: "tar xzf ubuntu_b6.tar.gz")
cd to this dir and type
Code:
su
then
Code:
sh ubuntu install
you will be asked a few questions, if you have no plan just press always enter. after reboot open a terminal and type
Code:
su
then
Code:
ubuntu start
optional if you want gnome via vnc
Code:
ubuntu setupvnc
and
Code:
ubuntu setupgnome
this still takes long, you are installing here almost the complete ubuntu via internet. that are a few hundred megabytes of downloading and over one gigabyte of extracting and installing. leave with exit and on android shell type (first time it asks for a passwod)
Code:
ubuntu startvnc
then connect to it via: localhost:5901 using a vnc client and the password you set.
[what you got]
you start the ubuntu subsystem with ubuntu start (still chroot)
with ubuntu setupvnc you install vnc service
with ubuntu setupssh you install ssh service
with ubuntu setupgnome you install gnome
with ubuntu setupkde you install kde (if you do so, you need to modify inside ubuntu /usr/bin/vnc)
with ubuntu shell you open an bash session
with ubuntu screen you open an persistent bash session
with ubuntu startvnc you start the vnc service
with startssh inside ubuntu shell you the start the ssh service
with ubuntu stopvnc you stop the vnc service
with stopssh inside ubuntu shell you the stop the ssh service
with ubuntu stop you stop (is rebooting)
with ubuntu uninstall you uninstall the script from system(directory /sdcard/ubuntu stays)
in ubuntu you can access:
android's /dev bound to ubuntu's /dev (fdisk /dev/block/mmcblk0 is working fine(sdcard). don't touch /dev/block/mmcblk1 or you'll kill your android system, maybe your whole xoom )
android's /system bound to ubuntu's /android/system
android's /data bound to ubuntu's /android/data
android's /mnt/sdcard bound to ubuntu's /adnroid/sdcard
[working]
With android-vnc Gnome (bluetooth keyboard and mouse)
Firefox 4
Chromium Browser
LibreOffice
Gnome Terminal
SSH Daemon
"D" key needs to remove the gnome keyboardshortcut uses "D" (just open vnc, goto a textfield and type d then you know what I mean )
and a lot more
[not working]
Ubuntu Software Center (use Synaptic instead, find it in the system menu)
[the tecnical side]
Ubuntu Natty Narwhal (11.04) from http://elinux.org/BeagleBoardUbuntu
dd for creating an image (no size limit anymore)
image formatted with ext2
adb push /sdcard/ubuntu/img/ubuntu.img (android shell has gunzip)
chroot env
tightvnc, gnome-session
different kernel features which i'll list here later
[changelog]
Beta 6
small changes in the scripts to ensure compatibility with other roms and devices
you can choose now between UBuntu 11.04, 11.10 and 12.04 Beta2
[next]
providing preinstalled images for gnome, kde and xfce
app instead script
[ideas]
weirdx
wayland
Have Fun
Ralph
GhostOfTheNet said:
Hi folks,
Actually I'm poking around with the common "How to get ubuntu onto xoom", but with an own img file i created based on the maverick arm minimal archive. Now I'm installing unity, but in weekend I'll try to make the installation, configuration, ... more userfriendly. maybe I'll build a small app doing thinks like starting, stopping, starting a terminal with the chroot and so on. I've no plan at this moment what I'll do exact. But you can say me what you would like to have, so I know if there is a need for something. I think with the next ubuntu using something based on opengl as replacement for x and the promised touch support, it might be relly interesting to have in a chroot env and maybe write something like a wrapper for androids opengl es api. in this context maybe also a port of the android sdk to linux arm would be very interesting.
Regards
Ralph
Click to expand...
Click to collapse
I just posted in the general forum about this lol. I would love maverick meerkat on the xoom. I'm sure the software center wouldnt work, but if you could somehow incorporate compiz fuzion, along with all of the standard apps, that would be the sh*t. Good luck man!
Got it to run on gtab but not sure how to do it on xoom.
Sent from my Xoom using XDA Premium App
i have it already running, but I'm not getting the f*** unity running, because it needs opengl... a bit bad with tightvncserver
so i decided to jump over and try directly this out:
http://rcn-ee.net/deb/rootfs/natty/ubuntu-natty-alpha3-r0-minimal-armel.tar.xz
the omap4 is an arm cortex a9 processor, so it should be binary compatible.
wish me luck, if it will work you will have today a howto, otherwise i'll go back to 10.10 and search for another useful desktop.
edit: apt is working fine with maverick
regards
Ok, so far so good. Ubuntu 11.04 is basically running, all is working fine, but the repository is buggy, so apt is not letting me install unity.
Besause today i'll not google for a missing lib, let see further tomorow. Hopefully the repositories are fixed then.
I'm uploading now a file called ubuntu.zip
To install it do the steps i'll write now in the first post. (the setup is not tested, so you may still need your knowledge)
Regards
Sent from my Xoom using XDA App
Hey Ghost -- thanks for your great work on this!
One thing I was wondering -- would it be possible to break out your instructions on how to do this from scratch? I'm interesting in putting together my own version (probably a minmal Ubuntu 10.04 install), and would really appreciate the source "steps".
From what I've read, it looks like it's a matter of grabbing the right kernel (I thought I saw a recent one on the tegra development site), bootstrapping the right debian-based arm-compatible distro, and copying that over to the device with the right script to get it setup. I'd just love it if I could piggyback on your fine work
GhostOfTheNet said:
It's alpha, so nothing for you if you have no plan whats going on here.
Archive: http://www.bisme.net/ubuntu.zip
Needed:
Rooted xoom with busybox installed
Steps:
1.) Extract the zip to /sdcard/ubuntu
2.) Open a terminal su, cd to this dir and type
./setupubuntu (sh*** i forgot to change the file, all cp commands are not working for some reason, needs to be
cat filename > /system/bin/filename
3.) ... ehm fin
(always su before)
If you replaced the cp, you can directly type for example bootubuntu, if not you need to be in dir /sdcard/ubuntu and say ./bootubuntu
After ubuntu booted(real only mounted) you can start a bash shell with shellubuntu. Unmount it with shutubuntu(in most cases will fail, then you need to reboot before you can say bootubuntu again)
Ehm, yes... i love my xoom :-D most of the time i worked on that... my pc i almost didn't need. Small tipp, it is worth its 4 dollar, better android terminal. Without bash this would be the hell.
Regards
Ralph
Click to expand...
Click to collapse
Man you are the best. I really really want to get this up and running but i cant get through setup. idk how to install... this is not my area of expertise lol. help?!
edit: i guess for clarification, after i type in the cat command it tells me write: no space left on device
Is the touch screen working
Sent from my Evo 4G using Tapatalk Pro
Ok, first of all, this is not a rom. Thats not needed in this case, because with linux more installations can share the same kernel. Android has a linux kernel, ubuntu has one. Google for chroot
This is not an attemp to replace android, just to enhance it a bit
In this state it's just something like a technical preview. Give me a few days. For now only advanced linux users wich understands whats happening there can do something with it.
Concerning a minimal ubuntu, this is now a minimal installation.
Regards
Sent from my Xoom using XDA App
After unity 2d is not really working at this moment, I'm actually preparing a version with icewm and lxde. Post will come in a few hours.
Regards
Sent from my Xoom using XDA App
What about Enlightenment?
http://www.linuxuk.org/2010/02/the-new-ui-for-arm-based-ubuntu-devices/
i'm installing it. lets see.
the reason why it's still not posted, i have a problem with the xstartup file of tightvnc. for some reason it is not running the commands for the ui, so there is just an empty xserver in vnc until i start icewm lxde manually. i think it would be the same with efl, and i had until today to less time to check out whats wrong.
edit: netbook-launcher-efl + metacity + maximus is looking fine
Is there any way to not use VNC? Can you dual boot or otherwise get into X ?
or possibly something like freenx client on android maybe??? in hopes that it's faster than vnc. if we can't boot into ubuntu.
edit - scratch that, i read you need X to use freenx... kinda defeats the point there.
i thought there was something else though that fowards all the window data over like lightning fast.
I found until now two possibilities but both needs much work. First taking the wayland xserver client and port it to android, or port weirdx to android.
Sent from my Xoom using XDA App
Hmm... so back to the dual boot question... What about something like this guy did?
http://androidforums.com/samsung-i7500/81090-debian-dualboot.html
https://code.google.com/p/linux-on-android/wiki/BasicSteps
Would that also work on the XOOM?
Me personally, I'm not interested in another Linux Distri as main System
1. I would miss the android functionallity and feel, because of that I would never boot Ubuntu.
2. Only android has the needed touch support for a tablet. Maybe this changes i future ubuntu releases.
Because of that my primary target is a more seamless integration of a ubuntu subsystem in android, so we can use many beloved functions without much work. So there is the best of both worlds in the same time avaliable.
Sent from my Xoom using XDA App
Makes sense. My motivation for research and all this is that I want to do (light) web development and server administration on the tablet as well. Of course, buying that bluetooth keyboard makes it all feasible and I'm not looking to do heavy amounts of work on it, but I want to ditch my netbook. For starters, the tablet lasts longer in terms of battery life and the form factor is better.
Other than that, to me, tablets serve merely as an entertainment purpose (unless maybe you're using it to bill people or for a sales pitch/meeting) and I can't justify the cost. A $600 travel Scrabble is retarded. So I think tablets need something like Ubuntu running on them in order for them to be a more productive device that is a justifiable expense.
Right now the biggest thing that I'm thinking about is gedit and git. If I can get those two... Then I think I'd be pretty much set. I think there's actually two or three text editors for Android as is and I might be able to use those provided I could get git for Android.
The graphical user interface isn't the most important thing so I can even live w/o the VNC. Having a local webserver would be rad, but not a high priority since I can use git to update a server on the net.
If you have any ideas, and I know it's getting somewhat off topic, but your research is really the crux of my situation...I'd appreciate it. Thanks.
--edit ok, so i found www.cloud9ide.com which will cover me I guess. but still I want more power under the hood. I really appreciate your work efforts! Thanks.
updated useful for people which knows whats going on
deleted. got it. Thanks! this is awesome. great work!
Hi all!
I just bought a Galaxy Nexus, and I've already a problem: how to connect it to my linux computer?
You know that ics use MTP protocol to interface with computers. Maybe it's good for windows users, but with ubuntu I can't let the phone be recognized by the pc. I tried this guide http://www.reddit.com/r/Android/comments/ne6ud/mount_your_new_galaxy_nexus_from_the_unity/ but it doesn't work, when i click "mount galaxy nexus" it shows an error message ("the socked is not connected").
Can you help me, please?
Use airdroid or something similar. It will save you many hours of pain
Sent from my Galaxy Nexus using Tapatalk
Evostance said:
Use airdroid or something similar. It will save you many hours of pain
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You're right if you need to transfer just some files. But I've to transfer all my music (about 4/5 GB) and my photos and videos (about 1 GB). Using something like airdroid, I will die before it ends
try installing mtpfs
i keep meaning to try it on fedora
bleets said:
try installing mtpfs
i keep meaning to try it on fedora
Click to expand...
Click to collapse
I've already installed it, but it doesn't work. Almost, on ubuntu.
When I try to mount the phone it shows an error message.
Another question is: why, if i connect the phone using PTP protocol it works, the pc recognize the phone, but it seems to have just 700 MB of free memory? (realy there are more than 12 gb)
Metallaro said:
Hi all!
I just bought a Galaxy Nexus, and I've already a problem: how to connect it to my linux computer?
You know that ics use MTP protocol to interface with computers. Maybe it's good for windows users, but with ubuntu I can't let the phone be recognized by the pc. I tried this guide http://www.reddit.com/r/Android/comments/ne6ud/mount_your_new_galaxy_nexus_from_the_unity/ but it doesn't work, when i click "mount galaxy nexus" it shows an error message ("the socked is not connected").
Can you help me, please?
Click to expand...
Click to collapse
I ended up installing Windows 7 in virtual box. In the end it was easier to do that then to continue wasting time getting Ubuntu 11.04 to play the MTP game
Just installed mtpfs from source and it works fine...doesnt look like it will auto mount when you plug it in though.
this might help
bleets said:
Just installed mtpfs from source and it works fine...doesnt look like it will auto mount when you plug it in though.
this might help
Click to expand...
Click to collapse
I used this guide some month ago when I had a motorola xoom. Now if I try to mount my phone, it shows an icon named "xoom", but if I try to open it it shows this error message
(the message was in italian, i tryed to translate it in english but it's difficult)
Code:
[B]Impossible to show «/home/marco/Galaxy Nexus».[/B]
Error: Error in executing the file stat "/home/marco/Galaxy Nexus": the destination socket is not connected. Please chose another viewer (??) and try again
Edit: no, wait. I used another guide to connect the xoom to the computer, but I can't find it again. Anyway, if i try to follow the guide you linked, when I write
mtpfs mountpoint
the console shows this error message
fuse: bad mount point `mountpoint': No such file or directory
mtpfs mountpoint = mtpfs /whereyouwanttomount to
for instance i do
Code:
mtpfs Mounts/nexus
so you have to make the folder where you want to mount to
for instance in your shell, in your home folder
Code:
mkdir nexus
(by the way, it's best to avoid folder names that include spaces)
then to mount to that folder you'd do
Code:
mtpfs nexus
or if you're currently cd'd in a different folder
Code:
mtpfs /home/marco/nexus
simples
the guy in that post even did an example to show you a bit furthery down :|
I found gMTP works quite well, though I just recently switched from Gentoo to Arch and unfortunately gMTP isn't as stable as it was in Gentoo.
Grr...I don't have enough posts yet to post links but if you do a google search for:
omgubuntu galaxy mtp
The first link in the list is the guide I used and it works great.
http://www.omgubuntu.co.uk/2011/12/...eam-sandwich-phone-to-ubuntu-for-file-access/
this is what i used, because i like to do stuff myself. there is also a script if you like automated stuff. good luck
If anyone knows how to get it working on 10.04 let me know ;-)
Sent from my Galaxy Nexus using Tapatalk
I followed the instructions on the websites. It connects using MTP but only allows music playlists. Change the USB setting on the phone to Camera (PTP) and Ubuntu recognises the file system on the internal sd card.
I will try this
Sent from my Galaxy Nexus using Tapatalk 2
Welcome to jimmyco2008's Layman's Guide to the Galaxy (Nexus) - Open WebOS Edition!
------------------------------------------------------------------------------------------------------------------------------------
EDIT: I wonder if I can spare you guys all the building and just upload the 1/2 GB WebOS image and Fastboot file... I'm going to try that out, upload them to Google Drive tonight/now, I'll add the link by tomorrow and you guys can try to just download the files instead of building everything, at least for those who just want to try this out. If you're serious about working with this Open WebOS, I recommend going through all the steps to get all the files building gets you, and so you can update your build files as webos-ports.org updates them.
But here's a link to the folder containing the WebOS developer image file (I didn't build the regular image, not sure of the difference) and the fastboot file needed to boot the thing. Get these files, and you can skip to the giant, bolded "LIKE A BOSS" heading somewhere in the middle of the guide below. Keep in mind you still need to meet prerequisites, save the decent resources, if it runs Ubuntu, and ADB/the Android SDK are/is set up, you're clear for takeoff.
Also note that the .ext2 image of WebOS has a different name, relax, it's the same thing!
Download! .. And feel free to mirror, though I doubt demand nor lack of reliability for Google Drive warrants one.
------------------------------------------------------------------------------------------------------------------------------------
Know this before diving in:
- You NEED Linux.. Not OS X, not Windows, some Linux distro... For the Laymen, you'll want Ubuntu 11.10 or above (can't go wrong with the latest 12.10)
- Get 64-bit, no questions asked.
- Building/compiling the WebOS image in Linux/Ubuntu takes A LOT of resources, generally you can build with any old computer, but it'll take a long time.
- I'm saying if you're running Ubuntu full-boot (not in a Virtual Machine), have at least 3GB of RAM and a 60GB hard drive... any decently-modern processor should do, but the slower and older, the longer it will take to build... You're more than welcome to try this with whatever computer you have, just give it plenty of time to do its thing.
- If you're doing this in a Virtual Machine, like with Parallels or VirtualBox, give the Ubuntu Virtual Machine (VM) as much of your computer's resources as possible. For example, I have a 2012 Macbook Pro (240GB SSD, Ivy bridge Intel Core i5 @ 2.5Ghz, 8GB DDR3 RAM @ 1600 Mhz), I gave the Parallels Ubuntu VM 4GB of RAM, 60GB of hard drive space (I'm at 51 GB used and all I did was the minimum to get WebOS on the GalNex) and all of my cores (4) at 100% cap. It took... well, a few hours to build.
- This boots on both the GSM and CDMA Galaxy Nexuses, so toro, toroplus and maguro are all supported, well except for anything related to the radio.. As with anything Galaxy Nexus-related, GSM gets radio stuff working first.
- This procedure boots WebOS tethered, so you can unplug the Galaxy Nexus once WebOS (Luna) is booted, but rebooting gets you back to Android, and you have to do the fastboot boot image thing again to boot into WebOS. So this doesn't touch your Android (or Ubuntu Mobile I guess) setup.
- Ignore the dollar signs ($) and pounds (#) preceding commands, it's just for organization!
- I am not responsible for anything that happens to your phone or any of your property as a result of using this guide... Standard disclaimer.
---------------------------------------------------------------------------------------------------------------
Alright the Layman's Guide to the Galaxy Nexus! (isn't that punny lol)
Preflight Checklist
- Ubuntu 12.10 (probably good with 11.10 or 12.04 as well) 64-bit.
- Java Runtime 6 or 7 (available for download @ Ubuntu Software Center, or if you're a boss with Linux, you can do the Terminal install, you know what you're doing lol)
- Android SDK
- Android Tools installed via the Android SDK Manager (run from Terminal or double click "Android" script, located in sdk/platform-tools (or some other folder in sdk)
- You can access your Galaxy Nexus via ADB on Ubuntu (getting the host to share the Galaxy Nexus with the Ubuntu VM can be a ***** sometimes, make sure ADB finds your Galaxy Nexus via "./adb devices" .
- At least... eh 1-2 GB free on your Galaxy Nexus sdcard0 storage (who out there actually has to check this lol)
- Your Galaxy Nexus' Bootloader is unlocked... At first I didn't think I had to add this, but for the sake of being thorough...
- If # ./adb commands aren't working, like ./adb devices or ./adb reboot-bootloader, and it gives you some error in Terminal, you need to update 'cha libs. Open a fresh Terminal window and enter:
# sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
Go through all that, tell it yes however many times, and when it finishes, ADB commands should work.
---------------------------------------------------
The Main Event
This is actually kind of boring, you have to literally copy and paste like 10 commands into Terminal for the Prerequisites webos-ports.org dictates.
Enter all this into Terminal one at a time as it processes and finishes each line (by giving you the block cursor back), and remember to answer "y"/yes to all questions!
1$ sudo apt-get install build-essential
2$ sudo apt-get install gawk && sudo apt-get install diffstat && sudo apt-get install chrpath
3$ mkdir webos-ports-env && cd webos-ports-env
4$ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh * Ugh, damn, XDA forums sets this as a URL and shortens it, if you copy and paste directly into Terminal, it won't work...just right click and Copy Link URL or whatever, and paste that separately from "wget".. Do the same for the link below.
6$ sudo sh prerequisites.sh (this takes a while, ~10-20 minutes depending on your internet/hardware)
6$ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
7$ make setup-webos-ports
Now you can probably build, I know the official guide says differently, but I've done this MANY times, just hear me out!
1$ cd /webos-ports-env/webos-ports
2$ . setup-env
Now the text preceeding whatever you type should be blue and green (how magical!), if it's not.. Well post below and I'll help you out.
So actually building this, commands vary depending on if you want the developer image or the regular image... In fact a bunch of WebOS not working for me (like apps) may be because I opted to build the developer image... Honestly, I'm not sure what the difference between the two is, it's open source, you should be able to develop on either... If I were you I'd go for the non-developer image, but here's both commands, choose ONE:
*Also, on the webos-ports.org website, they offer advice about speeding up the build by editing the number of threads value in a config file, default value is 4 cores and 4 threads, I changed mine to 8 threads, I dunno, really shouldn't matter unless you're rocking an i7 Extreme Edition or a Bulldozer, you know something with more than 4 processor cores (physical and virtual). If you have less than 4 cores, like you have a Phenom II X2 or an Intel Core 2 Duo, maybe even an older i3, you should be fine with the default 4/4 settings.* If you're into changing the settings, the file you edit (with TextEditor or whatever) is located at webos-ports/conf/local.conf . Lookin' for BB_NUMBER_THREADS and the line above it, both should = 4 by default.
Regular Image (make sure you're in the build environment > Magic green & blue text!)
$ MACHINE=tuna bb webos-image
Developer Image (again, make sure the magic blue and green text is there)
$ MACHINE=tuna bb webos-dev-image
Now the magic happens, if all goes well, within a couple of minutes (or sooner) you'll see "preparing runqueue"... If you look at System Monitor, you'll see it's downloading (at 100 - 400 kbps, even if you have a 50mbps down internet connection) the build stuffs, which takes 1- 3 hours (don't be afraid to use Netflix haha).
It'll actually go between downloading at a rather slow rate and running tasks (over a thousand of 'em)... All in all, give it, again depending on your hardware and internet, like the night (5 - 12 hours), perhaps even more... It'll finish when it finishes. If you get errors at the end, well that's normal, ignore it, you may not even get errors for the regular image, again I've just used the developer image.
-----------------------------------------------------------
Booting Open WebOS *LIKE A BOSS*
Make your life easier and have a file manager window open to webos-ports-env/webos-ports/tmp-eglibc/deploy/images/tuna. Let's call this directory "Foxtrot" for the sake of simplicity.
Okay this is the part where the official guide at webos-ports.org just... ugh... It says to enter this command from your Android SDK /platform-tools folder:
adb push webos-dev-image-tuna.ext2 /storage/sdcard0/linux/rootfs.ext2
Actually it should be (type this in, don't copy and paste):
./adb push *click and drag the webos-dev-image-tuna.ext2 file to Terminal* /storage/sdcard0/linux/rootfs/.ext2
NOTE: Yes, you can click and drag that .ext2 file and Terminal automatically figures out the path, remember that this file is located in webos-ports-env/webos-ports/tmp-eglibc/deploy/images/tuna . Let's call that directory "Foxtrot" for easy reference.
If all goes well, you see the cursor is gone, it's doing its thing- pushing the WebOS image to Galaxy Nexus sdcard0 in a folder called "linux" (as shown above), if you wish to delete this later. Pushing this file took my Macbook about 6 minutes, allow up to 15 minutes for those slower computers out there.
Now reboot your GalNex to the bootloader (you know how to do that)
./adb reboot-bootloader ...or just power off and hold vol up + vol down + power.
Okay here's where the official guide will really **** you up... The file isn't called what the guide states it's called, at least for me...
Type (don't copy and paste this one either):
sudo fastboot boot *click and drag whatever file is closest to "zImage-tuna.fastboot" in our "Foxtrot" directory. Mine had a bunch of numbers, it was like zImage 8246237860837462387462038756012831982 .fastboot. Make sure the file you drag to Terminal ends in ".fastboot", there's one that ends in ".bin".
So: sudo fastboot boot *that file dragged over*
Now it should do its thing, may see a black screen on the Galaxy Nexus for a minute or two. Eventually you'll see a clock where it would be in WebOS (top-middle) and "First Boot" (something like that, I forget) at the upper-left corner.
Now we have to send a couple of simple commands to this WebOS thing from Ubuntu to get Luna (the UI itself) to boot.
You'll see that there is an Ethernet connection in Ubuntu, mine was Wired Connection 2.... Click on the network icon on the top bar in Ubuntu, click "Edit Connections", click on Wired Connection 2, add an Address. Address is 192.168.7.1, Netmask is 255.255.255.0 (actually you can probably get away with entering the default value), Gateway is 192.168.7.2 . Save that bad boy.
Now in a fresh Terminal window, enter, one at a time of course (remember to omit the dollar signs, just good syntax):
$ ssh [email protected]
$ stop LunaSysMgr
$ touch /var/luna/preferences/ran-first-use
$ start LunaSysMgr
Congratulations! Give it a few seconds, you should be in Open WebOS! Woo!
Feel free to contact me if you need help, I made an error in the guide, or you want to help make this a realistic alternative to Android!
Remember, to get back to Android, just pull the battery and reboot normally!
Credit goes to the webos-ports team at webos-ports.org for making this happen!
---------------------------------------------------------------------------------------------------------------
Details about the port!
Hardware acceleration appears to be at least partially working, that's probably about it, calling (and possibly SMS) works on GSM versions of the GalNex. For those of us with CDMA (myself included), this port should work, however about all it will do is boot for now. So it's just for fun atm. Furthermore, it's uncertain as to whether the Verizon or Sprint GalNexes will ever get a fully-working port because they're CDMA. That would be a shame, but we'll just have to see, won't we?
EDIT (after I actually got it booting): Not a whole lot to do with it, I'm hoping someone can work with me to make this port better, or at least get the radio portion going, no one will use this if it can't send and receive calls/SMS... I (with my Verizon toro) was unable to get any apps to actually open, but the UI is EXTREMELY smooth, I mean holy damn, and the on-screen nav light/bar from past WebOS devices is slick and really cool! WiFi turns on and eventually picks up networks, but I was unable to actually connect (though it may work for unsecured networks, never prompted me for a password so..). Bluetooth does not work (again, at least for the toro), and I had difficulty with the orientation, like sometimes it would go landscape but I couldn't get it back to portrait...
...As for the poll, it's pretty pointless, if a mod happens by, please remove it! No need to worry about bricking (for obvious reasons), and the lack of radio support is no excuse, just battery pull and reboot to get back to Android.... No reason to wait till someone else does it, I just did it!...So go for it!
-----------------------------------------------
Re-Booting Open WebOS after doing it once before!
Now reboot your GalNex to the bootloader (you know how to do that)
./adb reboot-bootloader ...or just power off and hold vol up + vol down + power.
Okay here's where the official guide will really **** you up... The file isn't called what the guide states it's called, at least for me...
Type (don't copy and paste this one either):
sudo fastboot boot *click and drag whatever file is closest to "zImage-tuna.fastboot" in our "Foxtrot" directory. Mine had a bunch of numbers, it was like zImage 8246237860837462387462038756012831982 .fastboot. Make sure the file you drag to Terminal ends in ".fastboot", there's one that ends in ".bin".
So: sudo fastboot boot *that file dragged over*
Now it should do its thing, may see a black screen on the Galaxy Nexus for a minute or two. Eventually you'll see a clock where it would be in WebOS (top-middle) and "First Boot" (something like that, I forget) at the upper-left corner.
Now we have to send a couple of simple commands to this WebOS thing from Ubuntu to get Luna (the UI itself) to boot.
You'll see that there is an Ethernet connection in Ubuntu, mine was Wired Connection 2.... Click on the network icon on the top bar in Ubuntu, click "Edit Connections", click on Wired Connection 2, add an Address. Address is 192.168.7.1, Netmask is 255.255.255.0 (actually you can probably get away with entering the default value), Gateway is 192.168.7.2 . Save that bad boy.
Now in a fresh Terminal window, enter, one at a time of course (remember to omit the dollar signs, just good syntax):
$ stop LunaSysMgr
$ touch /var/luna/preferences/ran-first-use
$ start LunaSysMgr
Congratulations! Give it a few seconds, you should be in Open WebOS! Woo!
Got it booting just now lol, and the instructions at webos-ports could be... better, clearer, so if anyone wants to try this out, it doesn't affect their Android installation and you can just reboot into Android easily enough.
If you encounter issues, post here, I should be able to help you out!
jimmyco2008 said:
Got it booting just now lol, and the instructions at webos-ports could be... better, clearer, so if anyone wants to try this out, it doesn't affect their Android installation and you can just reboot into Android easily enough.
If you encounter issues, post here, I should be able to help you out!
Click to expand...
Click to collapse
Would you mind writing a simplified version?
Their instructions are Daunting!
Sure, here's a really layman version, I'll add to it over the next day or so:
Okay so what we're doing is using Linux (specifically Ubuntu if you're following this guide to a tee) to build the WebOS image for the Galaxy Nexus which webos-ports.org put out. Then we're using ADB and Fastboot to push the image to a certain directory within sdcard0 (the emulated SD Card on the Galaxy Nexus), then we're using Fastboot to deploy, not flash (over the Android boot.img), to the Galaxy Nexus to tether-boot WebOS. It actually boots a really basic version, not sure what it's called exactly... From there we connect via ssh (like telnet) to the Galaxy Nexus with IP to send the final commands to initiate Luna (the WebOS UI).
EDIT: Actually I'll edit the OP with the instructions...
Why would anyone want web os? Ugh awful..
Sent from my Galaxy Nexus using xda app-developers app
Why would anyone want iOS? Ugh awful..
Does anyone have a video of this working on a Galaxy Nexus?
Yeah.... I'm not making a video, but there's a couple on YouTube.
Sent from my Galaxy Nexus using xda app-developers app
Really cool. Im a ubuntu beginner and hope i can pass the installation ^^ thank you for this guide. Have a gsm (maguro) gnex -> calling/sms/3g is working?!
Raphi86 said:
Really cool. Im a ubuntu beginner and hope i can pass the installation ^^ thank you for this guide. Have a gsm (maguro) gnex -> calling/sms/3g is working?!
Click to expand...
Click to collapse
3g isnt working , call and sms is .
Beat me to it lol... Yeah I may have to pick up a GSM Nexus, no one ever supports CDMA :/
Unless some kind sir out there in the community is ambitious enough to port the radios, not sure how involved that is...
Why is there no easier way to install it? Cant they compile a "ready to flash" rom for maguro/toro etc?
(Sorry for my bad english)
Not really, this isn't Android... But it may work if I just upload the two files needed to start WebOS, instead of having everyone compile it for 6 hours or whatever. I'm looking into that.
Sounds good Makes it a lot easier. Thanks
Alright check the OP for the download link, it's about 550 MB or so.
Okay.... after 3 Hours its running.
It feels very good on gnex, but there is a lot of work to do.
On my Maguro wlan works. Bluetooth isnt.
The gesture bar is very very cool and works like a charm.
The os (+Launcher) itself is very smooth. Apps in fullscreen are laggy.
The virtual keyboard and some apps look like cutted up
Cant open phone, but i think its because i have a simlock on my card. cant find a sms button?!
Is the ext2 image build with the lastest source/uploads? the keyboard, especially the scaling, looks better in this version -> http://youtu.be/XelmomAq91o?t=1m19s
Thanks a lot for your guide... it helped me a lot!!! :good:
Two things:
-
Rename "webos-dev-image-tuna-20130226032314.rootfs.ext2" File to "rootfs.ext2"
-
ssh [email protected]
stop LunaSysMgr
touch /var/luna/preferences/ran-first-use
start LunaSysMgr
Glad to hear it, what about the two things, could you elaborate?
The files linked were what I got when I built them a couple days ago, the difference in the video is probably from it being the normal image whereas I built and uploaded the dev image...Damn, there is a difference I guess, well who wants the Dev image over the one that looks and works better (supposedly)?
I deleted my Ubuntu VM for housekeeping, considered moving it, but in any case I won't be able to build for a little bit, anyone care to upload the normal 500 MB image? I can take it and upload to my cloud so you're not losing space.
Sent from my Galaxy Nexus using xda app-developers app
EDIT: Oh I gotcha, fixed. Thanks!
Just thought I'd remind people that this exists... And does anyone out there have any interest in this, either as a user or a developer?
jimmyco2008 said:
Just thought I'd remind people that this exists... And does anyone out there have any interest in this, either as a user or a developer?
Click to expand...
Click to collapse
webOS ? i wont mind .
...onto this device? It's the perfect size for an ARM laptop and Arch Linux is a great Linux distro too. I'm helping some devs port/get running natively Arch Linux ARM on the semi-ancient/underrated HP TouchPad from 2011. If it could run natively on this tablet, then I'd highly consider getting it to play with it on it.
I'm looking to do this also, I just rooted my pixel and tried "Linux Deploy" but it failed at "mounting /dev/loop0", looks like the stock kernel doesn't support mounting loop devices so this will be impossible until we get a new kernel.
edit: /dev/loop0 exists so I don't know why mounting fails...
Sent from my Pixel C using Tapatalk
So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.
it's interesting that your ubuntu is arm64 and not armhf. i can't understand how that would work. i have a nvidia tx1 which runs armhf ubuntu 14.04 so i would have guessed that the pixel would be the same. i guess i need to read into linuxdeploy a bit and see what that is about.
It's ARM64 because the Tegra X1 is a 64 bit processor ARMHF will work too. All it does it create a chroot easily, a little difficult to look deep into it because a large amount of it is done using a binary he created.
brando56894 said:
So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.
Click to expand...
Click to collapse
How is everything working out so far? I'm tempted to pop the screen off mine when it shows up to flip a switch for some chrome os fun (if I can figure out a way to do it gracefully) but might also just roll with ubuntu. Really interested in hearing how your experience has been... Thanks for sharing.
Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk
brando56894 said:
Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I've only seen one paywalled teardown so far in some brief searching to give any hints / clues. After seeing cheep5k8's posts my interest has peaked and I am digging your posts as well. I need to run through the chromium os git and doc stuffs first before I fire up my heat gun and spudgers though...
Hi !
Me too i'm interessed on a linux instalation for my "ryu"
...Pretty interessed on ubuntu touch : the Pixel C seems to be the perfect item for the distro to combine tablet and pc in one.
Sadly i'm not a developper, but i hope somebody will think like me ^^
will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?
I have been working on this, please see http://forum.xda-developers.com/pix...ux-pixel-c-running-ubuntu-xenial-lxc-t3410655 if you want to run ubuntu xenial on pixel C
kxra said:
will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?
Click to expand...
Click to collapse
I was just using whatever distros were provided by Linux Deploy, half of them don't work anyway, for example Arch. I was only successful with Ubuntu IIRC.
Sent from my Nexus 6 using Tapatalk
For those who are interested :
https://www.youtube.com/watch?v=4B8unHrbZK4
Weston and XWayland are running quite well on Pixel C (without acceleration until now)
I will try to publish something quite soon (there are still stabilities issues)