Related
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
Is anyone successfully using MTP on Ubuntu Linux 11.10 with the Galaxy Nexus? It totally sucks that Google has dumped USB Mass Storage support in Android 3.0+
Anyway… I connect beast to my PC. Next:
Code:
[FONT="Courier New"]10:33:01 [email protected]:~$ mtp-detect
libmtp version: 1.1.0
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1 (04e8:6860) @ bus 1, dev 23
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
10:35:05 [email protected]:~$
11:58:08 [email protected]:~$ sudo mtp-detect
libmtp version: 1.1.0
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1 (04e8:6860) @ bus 1, dev 27
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
12:00:11 [email protected]:~$ [/FONT]
Well… Not so good.
Well, what to do? I've read about having to setup udev rules, but that's a solution for a problem yet to come, isn't it?
Thanks,
Alexander
Yeah, I am using it. I am a big time Linux noob but even I have got it to work using these instructions:
http://www.reddit.com/r/Android/comments/ne6ud/mount_your_new_galaxy_nexus_from_the_unity/
You need to be in root on your Ubuntu machine when you do this.
Let us know how you get on.
No go
samizad,
thanks, but that doesn't work for me. Basically, that package simply calls "mtpfs", which makes use of libmtp. And libmtp doesn't work for me.
Here's what I did:
Code:
13:39:39 [email protected]:~/Downloads/++Unsortiert++/g/mount_gnex$ mtpfs -d ~/Desktop/GNex/
FUSE library version: 2.8.4
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.16
flags=0x0000007b
max_readahead=0x00020000
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
And that's it… (Same result when I try "sudo mtpfs …", ie. when I run the command with root privs.)
In another term window, I tried listing the ~/Desktop/GNex/ directory, and it simply hangs (ie. it doesn't return to the prompt):
Code:
13:40:01 [email protected]:/data/Downloads/++Unsortiert++/g/mount_gnex$ ls -la ~/Desktop/GNex/
Like I said, I am a noob so I can't help further. Just one thing though - in the screen dump you give above, it refers to Samsung GT-P7510/Galaxy Tab 10.1. What's that about?
samizad said:
Like I said, I am a noob so I can't help further. Just one thing though - in the screen dump you give above, it refers to Samsung GT-P7510/Galaxy Tab 10.1. What's that about?
Click to expand...
Click to collapse
I also noticed that it says "Samsung GT-P7510/Galaxy Tab 10.1". No idea why it does that… I guess that there's some sort of database in the background, which "translates" something like (VID=04e8 and PID=6860) to readable names.
EDIT: To clarify: I only have 1 MTP device connected. I don't have a GTab.
I'm not currently at home so I really can not give you my system settings (ubuntu 11.10). Anyway, the mtp connection sucks big time and has lots of intreruptions. I'm using "samba filesharing" (free 9n market) on the gnx and I'm mapping the storage on my linux machine. I'm doing the same withbmy galaxy tab.
ADB mount?
ro_explorer said:
I'm not currently at home so I really can not give you my system settings (ubuntu 11.10). Anyway, the mtp connection sucks big time and has lots of intreruptions. I'm using "samba filesharing" (free 9n market) on the gnx and I'm mapping the storage on my linux machine. I'm doing the same withbmy galaxy tab.
Click to expand...
Click to collapse
Network based solutions (like samba, ftp, ssh or whatever servers) don't work for me, because where I'm at most of the time (ie. at work…), there we cannot access the mobile phones over WLAN from our PCs. Mobile devices and workstations are in different networks (which is good).
BTW: In the rare chance, that this MTP sh*t would work - would I even be able to access any random file which is stored on the "sdcard" (ie. underneath /mnt/sdcard)? If not - is it somehow possible to mount the device using ADB? With "adb push" and "adb pull" (and any other adb subcommand), there's full access to the (almost?) complete filesystem.
There is an alternative way of transferring files. You can use a flash drive and the usb host capabilities of the Galaxy Nexus. I'll give you my settings as soon as get home, this mean tomorrow afternoon.
ro_explorer said:
There is an alternative way of transferring files. You can use a flash drive and the usb host capabilities of the Galaxy Nexus. I'll give you my settings as soon as get home, this mean tomorrow afternoon.
Click to expand...
Click to collapse
Is that maybe using the "[root] StickMount" app?
---
DISCLAIMER: THIS IS A REALLY GOOD WAY TO EFF UP YOUR KINDLE IF YOU DON'T KNOW WHAT YOU ARE DOING!!!
IF YOU DON'T KNOW WHAT ADB, PARTED, OR WHAT LINUX IS, YOU MIGHT WANT TO JUST CLICK THE BACK BUTTON!
---
Most that know Android, knows that it's just fancy UI and API on top of Linux, but it's still not quite Linux... But what if you want to run real Linux on your tablet?
Well, it's actually not that hard to do, but certainly not for n00bs...
Need to know: Linux, fastboot, adb, parted, etc.
You will also need the mkbootimg program, fastboot, working ADB, etc.
And a USB OTG adapter and working USB keyboard.
(this is assuming you already have modded your kindle with the usual FFF+TWRP 2.1+CM9)
The first step is to do a little repartitioning, so boot the Kindle into recovery, and run an 'adb shell'.
Then run 'parted'.
The idea here is to basically maintain the stock layout, while making room for linux...
Which can be done a few ways, the easy way would to just delete 'media', then recreate it much smaller (I did 1GB).
Then make one more new partition, using the remaining flash memory (should be a little over 4GB).
Making sure to reassign the name 'media' to partition 12, you can also name the new linux partition 'linux' or whatever, if you like.
After that, quit parted, and create the new FS on the new linux partition (mke2fs -Text4 /dev/block/mmcblk0p13, but you should know that already ).
Then reboot the tablet, get back into Android, it may or may not complain about the 'SDCARD' needing to be formatted, which should be done anyway, since it changed in size.
Do another 'adb shell', mount the new linux partition to a useful place, you can just mount over '/mnt' if you like, it won't hurt anything. Exit out of the shell.
Download this pre-built Debian rootfs I found:
http://rcn-ee.net/deb/rootfs/wheezy/
Unpack that file on your host machine, then use 'adb push' to copy the armel-rootfs tar to the Kindle's '/mnt'.
'adb shell' back into the kindle, and change to '/mnt' and untar the armel rootfs tar file... Maybe go to the bathroom, get a drink, get some fresh air or something, it'll take a little time to do it's thing.
After that's done, download my rc.local and 'adb push' that to '/mnt/etc' and make sure to ungzip it, and chmod is 0777 (or is it 0766, either should work lol).
http://www.mediafire.com/?gx46xxb4813n5ob
Then you can delete the rootfs tar file if you like, get out of '/mnt', and unmount it.
Linux is now installed, easy eh?
Now, download my kernel (acutally it's Hashcode's kernel, but with needed changes):
http://www.mediafire.com/?2lqex9j5bgws0b1 (Updated 6/11/2012)
Using mkbootimg:
'mkbootimg --kernel zImage --ramdisk /dev/zero --cmdline "root=179:XX" --base 0x80000000 -o boot.img'
Where XX is the partition that you put linux on (if following this exactly, should be 13), you should now be able to use /dev/mmcblk0pXX as well, if that doesn't work just use 179:XX.
Then using fastboot, boot the kernel package:
'fastboot boot boot.img'
While it says 'waiting for device...", reboot the Kindle and wait for it to download and boot the package.
Then wait for the linux login!
Plug in your favorite USB keyboard, a USB 1.1 one works best I've found.
The root password for that rootfs package is just 'root'.
-------------
Now, the fun part: Internet access, the hard way.
I'm still working out getting the WIFI modules working, so you'll have to use it tethered via USB... Which means no keyboard, but you can still log in by SSH.
In my kernel, instead of being an 'android' USB devices, it's a multifunction USB gadget with ethernet, serial port, and mass storage.
Mass storage works, but a little buggy sometimes.
Serial port seems broken for some reason.
Ethernet is what we're after.
Now the rc.local I made, in addition to enabling the video overlay (so there's a framebuffer console on the LCD), it also sets up the ethernet USB gadget.
I set the IP address to 192.168.5.1, which really should be out of the common IP range that most people use, but if it conflicts, then you can edit rc.local before you push it over above.
On your Linux host, with the Kindle plugged in, bring up the USB ethernet interface:
'ifconfig usb0 192.168.5.2 netmask 255.255.255.0'
After that, maybe try pinging the kindle (192.168.5.1), to make sure everything is working... If it is, you should have no problems connecting with SSH and logging in.
Once you can connect/login by SSH, you'll need to add your host machine as the default gateway ('route add default gw 192.168.5.2'), then edit '/etc/resolve.conf' and add a DNS server (add your ISP's DNS, or use 4.2.2.1).
After that, you should have internet access on the kindle side via SSH, and should be able to download/install your favorite Debian packages.
Oh, did I mention that you'll need a IP forwarding/NAT service running on your linux host too? I'll have to refer to linux manuals on how to do that, but if you can do all this, you should have no problems doing that.
I should also say that this CAN technically be done in windows as well, since all the needed programs are available in WIN32 bins, but you won't be able to get tethered network access working, because Microsoft doesn't support CDC ethernet devices.
Have fun!
OH! And X works fairly well with the omap3 video driver, just so long as you DON'T touch the screen, the touch screen driver currently crashes X on input.
So fair warning, make sure you know how to navigate X with just a keyboard, unless you have a OTG working hub and can use a keyboard and mouse, or have a wireless keyboard/mouse combo of some kind.
Update 6/11/2012:
Uploaded new kernel (link above), touch screen is now working, though no multitouch.
I have a boot loader with multiple boot options, http://www.mediafire.com/?l6aaqgsdkiksfw0
To use it, make a partition named "linuxboot", and flash your linux's boot.img created with the above instructions.
Still working on wifi.
Update 6/11/2012:
Ok, WIFI is working... Not sure why it wasn't before.
Here are the modules: http://www.mediafire.com/?139hold2a2l9vbl
Don't forget to run depmod.
You'll also have to copy the firmware from android system partition in /etc/firmware and copy it to Linux /lib/firmware
In case no one believes me, here's a console dump (typing blind of course, this was an early attempt with no LCD):
Code:
d.
.
Starting periodic command scheduler: crond.
FATAL: Could not load /lib/modules/3.0.21+/modules.dep: No such file or directory
Debian GNU/Linux 5.0 carrier tty1
carrier login: usb 1-1: new low speed USB device number 2 using musb-hdrc
usb 1-1: device v0b38 p0010 is not supported
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.0/input/input4
generic-usb 0003:0B38:0010.0001: input: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-musb-hdrc-1/input0
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.1/input/input5
generic-usb 0003:0B38:0010.0002: input: USB HID v1.10 Device [HID 0b38:0010] on usb-musb-hdrc-1/input1
root
Password:
Last login: Sun May 27 21:55:28 UTC 2012 on tty1
Linux carrier 3.0.21+ #40 SMP PREEMPT Sun May 27 16:59:27 CDT 2012 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
carrier:~# echo skdjfhnsdkjfshdsummit_bat_notifier_call val=41
summit_smb347 4-0006: summit_fsm_stateTransform:state : suspend(0) -> suspend(0) ; event : EVENT_BATTERY_NTC_NORMAL
kfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb0
carrier:~# echo skdjfhnsdkjfshdkfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb1
-bash: echo: write error: No such device
carrier:~# omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
cat /dev/vcs1 > /dumpp.txt
I was trying to get something to come up on the framebuffer, to no avail of course.
The backlight comes on, and it seems like it want to work, but there's nothing.
Are you talking about a true Debian dual-boot on our tablet? That could be really awesome .
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
Actually, yes.
It's mostly a matter of having a proper framebuffer console and telling the kernel to use a root instead of using the initrd to setup android.
If we could get a scripted bootloader, one that would give a customizable boot menu, you could easily boot whatever you wanted.
And what about it : http://thomaspolasek.blogspot.fr/2012/04/arch-linux-lxde-w-xorg-mouse-keyboard_16.html?m=1 ?
Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.
seishuku said:
Well, I already got most of that working, chroot environment is easy.
I got the full Linux init going, no android at all... just no display.
Click to expand...
Click to collapse
Display might be tricky, as we are currently using the very latest graphics modules from TI. I'm not sure if you can use those in our current build.
That being said you could send a cat /proc/msg to a file during boot and that might contain your error.
Sent from my Amazon Kindle Fire using Tapatalk 2
Well I already have a working fbcon in android, but it seems the display just isn't being enabled in Linux.
I've tried "echo 1 > /sys/devices/omapdss/display0/enabled" to force it on, but nothing.
The back light is already on though...
I thought EXT2 was for really old linux distros.
Sent from my Kindle Fire using XDA
Not really, its just more compatible.
I could have made pretty much anything...
I read somewhere that SSDs should use EXT4.
i am really anxios to see this even though is only cmd line.
will the steps to get this going available even for SSH commands?
I really should hack together a wifi script to get some kind of network connection, would make working on it a little (lot) easier.
The idea here though is to basically have a full linux, to operate exactly like it would on a PC.
With a working framebuffer console, an X.org config can be made and X should work just fine with the touch screen too.
The end result, with just keyboard, should be a full blown linux system.
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk
Hashcode said:
The real question is how long it would take to compile android for.. itself.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
pbailey212 said:
They can start reproducing them selves, isn't this how terminator started?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.
I'm at a bit of a loss here... if I disable surfaceflinger, so I keep my android fb console, then if I disable the display and reenable it, I lose the console.
Also, in my initrd, I can remove everything except ueventd and still keep the console... so something ueventd (init) is doing to enable the console.
In Linux I can play with enabling/disabling the display, but nothing seems to provoke Linux to give me an actual console.
Sblood86 said:
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.
Click to expand...
Click to collapse
On the vm670 legend has it, people have compliled whole roms in 30 minutes, with an optimus v, and Leslie Ann's build server
sent from my Nokia 5110
Aha! Got it!
http://www.youtube.com/watch?v=PXhnVP3lWLU
For whatever reason sysfs wasn't taking my commands.
Now I can work out some bugs and get X working.
I also switched the USB gadget from android to an Ethernet CDC, so I can SSH via USB while I get wifi working.
Edit-
Sorry about the super blurry video, my phone's camera is having "issues".
Ok, I've switched to the official Debian armel wheezy distro (basically just formatting my linux partition and untaring the distro), seems to have fixed a lot of problems... One being aptitude not working correctly (seen in the video).
I need to enable some kind of ip forwarding on my local linux install, so I can get a temp internet connection on the kindle via USB gadget ethernet cdc (ssh and http already works).
Hi all,
I've been tinkering around trying to get mtpfs to work properly and get mtp services working in Ubuntu for my Xperia ZL (Bell C6506 4.2.2 android)
Here's where I'm at so far:
Linux can recognize the device and automatically mounts it now.
Rhythmbox can detect it, but I haven't tested sync features, but I did notice it couldn't automatically detect my music libraries. It obviously doesn't autodetect their locations and is possibly only looking for them in a certain place.
I'm also worried if I try to sync with rhythmbox, that it will erase data on the SD or worse, the internal.
Don't give me credit for any of this, I pulled all my info from various sources online, mostly from webupd8.
My steps:
Create a directory that we can mount the device to. Open up a terminal and type:
Code:
sudo mkdir /media/xperiazl
I never had to use chmod, but if you wanna make sure permissions are right, do a quick google search on how to set permissions with chmod. I think it's more important if you have multiple users on the one computer, but I'm the only user on my PC.
Next, install go-mtpfs through the ppa provided by webupd8
go-mtpfs is a Ddebian package that manages the filesystem used by the mtp protocols. It should work on any Debian distro, but I only work in Ubuntu 13.04 so I haven't tested anything else.
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
But go-mtpfs isn't enough on it's own, because it doesn't autmoatically detect the Xperia ZL (it is supposed to detect nexus devices, etc. automatically though)
Next you need to edit a script file in the udev folders, to tell linux how to recognize the phone; or theoretically any other MTP devices.
If you want to know about udev and the files you're editing, go to /etc/udev/rules.d/ and look for the readme document inside.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
I use the code below to set the parameters for recognizing the Xperia ZL, specifically while it's in MTP, with USB debugging enabled.
With debugging disabled you have a different product ID (labelled "ID_VENDOR_ID" in the code below). You could just duplicate the code and have two entries then, one for usb debugging on, one for when it's off.
FOR NON C6506 / Xperia ZL device users:
When looking at the below code, notice the idVendor tag and the idProduct tag in the first unhashed line of code. These numbers are specific for the Xperia ZL (possibly specific to the C6506, I never looked into it). If you're setting up auto-mount for another device, use the following function in the terminal:
lsusb
lsusb gives you a readout of all the usb devices attached to your computer (that linux can detect). The readout looks kind of like this:
Bus 002 Device 055: ID 0fce:5189 Sony Ericsson Mobile Communications AB
That's the readout at this time for my Xperia ZL. The 0fce is meant to be handled by idVendor or ID_VENDOR. The 5189 is meant to be handled by idProduct or ID_VENDOR_ID. Again, remember that your idProduct or ID_VENDOR_ID is different when usb debugging is off / on.
Ok, we're almost there! C6506 users, just copy the code below and replace YOUR_USERNAME with... well, your username.
All other users must replace the product ID and Vendor ID with their own device's values.
Code:
# Sony XperiaZL idProduct="0189" for usb debug off, and idProduct="5189" for usb debug on
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", ATTR{idProduct}=="5189", MODE="0777" #MTP media, USB debug on
# Xperia ZL MTP mode under JB 4.2+ : automatic mount & unmount whel plugged (usb debug on & off)
SUBSYSTEM=="usb", ENV{ID_VENDOR}=="0fce", ENV{ID_VENDOR_ID}=="5189", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_USERNAME /usr/bin/go-mtpfs -allow-other=true /media/xperia"
You will often run into errors and other random problems if you try to mount with the screen off (or at lockscreen). If you're gonna do lots of file transfers, I suggest jumping into your phone's developer options and turning on "stay awake" so the screen stays on while it's charging. That'll prevent loss of permissions in the middle of a file sync.
If there are any linux experts, could you help point out any faults in my code? I'm pretty sure its all good actually and that all the rough edges are linux issues with mtp, since it's not supported as well as it could be.
Anyways, thanks for reading, I know I'm not the best at teaching this but hopefully this helps someone else out who's been struggling with linux and MTP protocol.
EasyAI said:
Hi all,
I've been tinkering around trying to get mtpfs to work properly and get mtp services working in Ubuntu for my Xperia ZL (Bell C6506 4.2.2 android)
Here's where I'm at so far:
Linux can recognize the device and automatically mounts it now.
Rhythmbox can detect it, but I haven't tested sync features, but I did notice it couldn't automatically detect my music libraries. It obviously doesn't autodetect their locations and is possibly only looking for them in a certain place.
I'm also worried if I try to sync with rhythmbox, that it will erase data on the SD or worse, the internal.
Don't give me credit for any of this, I pulled all my info from various sources online, mostly from webupd8.
My steps:
Create a directory that we can mount the device to. Open up a terminal and type:
Code:
sudo mkdir /media/xperiazl
I never had to use chmod, but if you wanna make sure permissions are right, do a quick google search on how to set permissions with chmod. I think it's more important if you have multiple users on the one computer, but I'm the only user on my PC.
Next, install go-mtpfs through the ppa provided by webupd8
go-mtpfs is a Ddebian package that manages the filesystem used by the mtp protocols. It should work on any Debian distro, but I only work in Ubuntu 13.04 so I haven't tested anything else.
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
But go-mtpfs isn't enough on it's own, because it doesn't autmoatically detect the Xperia ZL (it is supposed to detect nexus devices, etc. automatically though)
Next you need to edit a script file in the udev folders, to tell linux how to recognize the phone; or theoretically any other MTP devices.
If you want to know about udev and the files you're editing, go to /etc/udev/rules.d/ and look for the readme document inside.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
I use the code below to set the parameters for recognizing the Xperia ZL, specifically while it's in MTP, with USB debugging enabled.
With debugging disabled you have a different product ID (labelled "ID_VENDOR_ID" in the code below). You could just duplicate the code and have two entries then, one for usb debugging on, one for when it's off.
FOR NON C6506 / Xperia ZL device users:
When looking at the below code, notice the idVendor tag and the idProduct tag in the first unhashed line of code. These numbers are specific for the Xperia ZL (possibly specific to the C6506, I never looked into it). If you're setting up auto-mount for another device, use the following function in the terminal:
lsusb
lsusb gives you a readout of all the usb devices attached to your computer (that linux can detect). The readout looks kind of like this:
Bus 002 Device 055: ID 0fce:5189 Sony Ericsson Mobile Communications AB
That's the readout at this time for my Xperia ZL. The 0fce is meant to be handled by idVendor or ID_VENDOR. The 5189 is meant to be handled by idProduct or ID_VENDOR_ID. Again, remember that your idProduct or ID_VENDOR_ID is different when usb debugging is off / on.
Ok, we're almost there! C6506 users, just copy the code below and replace YOUR_USERNAME with... well, your username.
All other users must replace the product ID and Vendor ID with their own device's values.
Code:
# Sony XperiaZL idProduct="0189" for usb debug off, and idProduct="5189" for usb debug on
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", ATTR{idProduct}=="5189", MODE="0777" #MTP media, USB debug on
# Xperia ZL MTP mode under JB 4.2+ : automatic mount & unmount whel plugged (usb debug on & off)
SUBSYSTEM=="usb", ENV{ID_VENDOR}=="0fce", ENV{ID_VENDOR_ID}=="5189", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_USERNAME /usr/bin/go-mtpfs -allow-other=true /media/xperia"
You will often run into errors and other random problems if you try to mount with the screen off (or at lockscreen). If you're gonna do lots of file transfers, I suggest jumping into your phone's developer options and turning on "stay awake" so the screen stays on while it's charging. That'll prevent loss of permissions in the middle of a file sync.
If there are any linux experts, could you help point out any faults in my code? I'm pretty sure its all good actually and that all the rough edges are linux issues with mtp, since it's not supported as well as it could be.
Anyways, thanks for reading, I know I'm not the best at teaching this but hopefully this helps someone else out who's been struggling with linux and MTP protocol.
Click to expand...
Click to collapse
Hey i did everything as you said, but still cannot mount my ZL C 6502...is there anything else that i could do?
okey im needing little help now, i just installed 64bit ubuntu to start practicing how to compile roms etc.....but now when i have zip on my computer finally, my nexus dont want to show itself anywhere on my pc. i followed these guidelines without succes "# sudo gedit /etc/udev/rules.d/99-android.rules" and added "SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your-login" # MTP mode with USB debug on" but obviously changed login and ATTR. also with ADB devices command my nexus is there, but should there read nexus instead of random numbers and letters?
E: got it working by following this -> http://bernaerts.dyndns.org/linux/74-ubuntu/268-ubuntu-automount-any-mtp-device