Related
Hello friends,
After some work I have finally gotten the command line interface (Dos Prompt CLI) to work on the Tmobile Rhodium with the stock ROM and Windows Mobile 6.1.
Here's what you need: Microsoft Windows Mobile Developer Power Tools available for free here:
http://www.microsoft.com/downloads/...d6-1dcc-47aa-ab28-6a2b006edfe9&displaylang=en
Within the Microsoft Windows Mobile Developer Power Tools package extract the folder called "PPC Command Shell - Command shell for the Pocket PC 2003 device." Do not worry that it says "Pocket PC 2003", we will make it work on Windows Mobile 5/6! (for background information read http://dalelane.co.uk/blog/?p=122&cpage=1#comment-102893). You will see three files: shell.exe, cmd.exe, and console.dll. Place the console.dll file in your Windows directory on your device (in our case, on the Rhodium Touch Pro 2 the Windows directory takes a long time to populate, but it will, add the console.dll to it). Then move the shell.exe and cmd.exe file to another folder on your device. After you are done with the below instructions you will be able to link directly to the cmd.exe file and run the command line terminal.
For the command line to work you would normally need to toggle the following registry key between "0" and "1" HKEY_LOCAL_MACHINE\Drivers\Console\OutputTo
By default it is set to "1" which disallows the command prompt to run, we need to set it to "0" to enable the command prompt. But, the caveat is that upon reboot it's best to have this key set to "1" otherwise your boot process is extended by about two minutes and you will get two open command prompt windows upon booting which you will need to manually close to go back to your home screen (annoying, but not a huge issue). In order to avoid all that, I have created a two simple Cab files which toggle the above registry key between "0" and "1". Before running the command prompt I run Command_Line_VISIBLE.cab (which turns the registry key to a "0" and when I'm done with the command prompt I run Command_Line_INVISIBLE.cab (which turns the registry key back to '1').
If you forget to run Command_Line_INVISIBLE.cab when done with the command prompt it's no big deal, just run it whenever you get a chance (even after a reboot, which would take two minutes longer and open the command prompt by default, which is no biggie since you can just close it once the device fully boots). Leaving the registry key set to "0" should not damage anything.
I have attached the cab files on the forum.
The goal of installing a command line interface on a Windows Mobile device is 'hackability'... you get yet much better (granular) access to your device. I have always been fond of the way Linux-based devices (Android, Iphone, Nokia N900) give you access to the command line, and always wanted something similar on Windows Mobile. Now this is possible, albeit with less options than the linux-based phones.
For example, with the command line you can now run NetCat. Netcat is known as the Swiss Army Knife of Networking. (http://en.wikipedia.org/wiki/Netcat) on your Windows Mobile phone...
You can download and install NetCat for Windows Mobile at http://prt.fernuni-hagen.de/~bischoff/wince/
I have tested a few basic NetCat commands and they seem to be working as expected, but more testing is needed.
Any feedback is appreciated
Usual disclaimer: This has worked great for me, but obviously I am not responsible if you damage your device.
Does anyone have any comments?
Please post your thoughts.
thank you
so glad i found this post, just about to try it out on my hd2...
To what end? What does this accomplish?
The goal of installing a command line interface on a Windows Mobile device is 'hackability'... you get yet much better (granular) access to your device. I have always been fond of the way Linux-based devices (Android, Iphone, Nokia N900) give you access to the command line, and always wanted something similar on Windows Mobile. Now this is possible, albeit with less options than the linux-based phones.
For example, with the command line you can now run NetCat. Netcat is known as the Swiss Army Knife of Networking. (http://en.wikipedia.org/wiki/Netcat) on your Windows Mobile phone...
You can download and install NetCat for Windows Mobile at http://prt.fernuni-hagen.de/~bischoff/wince/
I have tested a few basic NetCat commands and they seem to be working as expected, but more testing is needed.
terminal 7 said:
so glad i found this post, just about to try it out on my hd2...
Click to expand...
Click to collapse
Hi! Any update on this?
I tried this on my HD2 (WM6.5, ROM v. 1.61.468.1). The console is able to display text and run commands, but I can't type anything directly into it. The only button that seems to work is Enter.
If I type somewhere else and copy-paste into the console this works and commands execute perfectly.
What could be the trouble? Thanks in advance.
I have not tested the CLI on the HD2, but clearly your issue is caused by a lack of a physical keyboard. You may find a workaround to this (since you can copy and paste into the CLI fields), but unfortunately I cannot be of assistance since I only own the Touch Pro 2.
Good luck!
mail_e36 said:
unfortunately I cannot be of assistance since I only own the Touch Pro 2.Good luck!
Click to expand...
Click to collapse
Do you have a software keyboard in your device (my previous BlueAngel had one in addition to hardware)? If yes -- could you please check if the console works with software keyboard?
good!! Did you try pocketgcc on it?
Great news! I just tried the command line using the soft keyboard built into my Touch Pro 2 and it worked... I was able to enter commands in the command line without having to pull out or use the hardware keyboard.
Are you unable to use your software keyboard on the HD2 with the command prompt?
Pronichkin said:
Do you have a software keyboard in your device (my previous BlueAngel had one in addition to hardware)? If yes -- could you please check if the console works with software keyboard?
Click to expand...
Click to collapse
I have not tried PocketGCC, but it would be interesting to get it working on the command line.
mistm said:
good!! Did you try pocketgcc on it?
Click to expand...
Click to collapse
This is pretty awesome. I love my mini version of a PC and having this only helps...
Here is how one can use the command prompt for NetCat...
I have it working on Telus Touch Pro2 but the physical keyboard doesn't work except for backspace and enter. It could be due to Tarkims keyboard remapper. It does however work perfectly with the soft keyboards. I have a copy of Perl installed and working.
The physical keyboard should work, I'm also running Tarkims keyboard remapper and the physical keyboard works well for me. Did you use my two cab files for enabling and disabling the CLI?
Also, please tell me more about Perl on your Windows Mobile phone, is there a binary (executable) or cab file I can install for Perl?
Please advise, thanks.
mail_e36 said:
The physical keyboard should work, I'm also running Tarkims keyboard remapper and the physical keyboard works well for me. Did you use my two cab files for enabling and disabling the CLI?
Also, please tell me more about Perl on your Windows Mobile phone, is there a binary (executable) or cab file I can install for Perl?
Please advise, thanks.
Click to expand...
Click to collapse
You can find Perl here
http://perlce.sourceforge.net/
Which version of Tarkim's keyboard remapper are you using 1.3.2 or 1.4?
I just checked and I am running tarkim's keyboard controller version 1.3.2, which seems to work perfectly with the command prompt.
I am wondering what you use Perl for on Windows Mobile? I have looked at the http://perlce.sourceforge.net/ site and I am interested in installing Perl, can you give me some background on its utilization on the mobile platform?
Thanks!
Here's the response from Touch_Pete (via PM):
Actually I haven't tried much more than a few test programs. But this is a full implementation of a very powerful and flexible programing language that would allow you to go way beyond Mortscript which seems to be a popular scripting language used on Windows Mobile to do all sorts of things.
Working Perfect on my HD2 using FingerKeyboard2.1 ... I was facing same problem with original keyboard
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!
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 .
i have done some research into cracking mifare cards, and i am new to this.
i use ubuntu 14.04lts
i have purchased an acr-122u reader.
i would like to use it to try to crack a mifare classic card however information on this is either in another language or non-existent. i have archlinux on a disk if necessary, however would someone be able to explain how to run mfcuk on ubuntu 14.04lts? also does anyone know if their is a gui frontend in development for mfcuk? i believe i will need to run a dark side attack to obtain one of the keys, then use that key and a mfoc attack to find the rest of the keys. how would i install mfcuk and the necessary libnfc libraries and so forth and how would i run them? i apologize if their is already a thread for something similar to this, how ever i would like to be specific. i greatly appreciate any help that could be provided. (including links to web pages / threads related to this) thank you very much.
- csltr
anyone
anyone? anyone have anything? something to work with? ive been searching forever, only to find no information. i found a DEB of rfid-tools and nfclib and the driver to my acr122u, just cant figure out how to use it. it hangs after i put in mfcuk -C -R 0 which i believe i am supposed to do. not really sure. i just saw a forum where someone else put that command in. i tried it with a blank card and it said "recover keys 0" or something then did nothing. i hit enter and nothing happened. but i couldnt execute commands so i think, terminal thought it was doing something, especially since when i tried to x it out it said a process was running, and when i took the card off the nfc reader it gave me some codes then stopped. i tried it with a card that has keys however and it gave me some kinda error. anyone? anyone at all?
I keep getting am entry in my battery stats labeled only as random numbers. I tried googling to find out what it meant but with no success. I just factory reset and still get this problem. Usually it will drain about 5% per day. Screen attached.
I've got similar entry in battery statistics but different numbers also about 5% battery used.
I've got em too. Haven't got a clue what they are
I've no real idea if this is related but might be possible:
Linux (and probably it's cousin, Android) likely have a similar basic process interface, both use PID, PPID's and PGID's. (process ID's of one sort or another). The PID's "appear" to be just like those numbers you're displaying in your battery stats. In almost any linux or Android shell (terminal emulator for android or Adb shell), you can do a "ps" command and see if the number you're curious about is a process ID as follows:
Via adb:
Code:
adb shell;
ps | grep {the number you see}
If it shows up, check out what ps thinks the process name is. If the process name is "NULL" then supposedly linux won't show a process name over a certain number of characters (or ps won't) and will substitute the PID instead. That might be what's happening.
The PS command can accept lots of options on linux (ps -ef, ps -aux, etc) but on android, it might just output everything without options or switches, so try a plain ps command first.
Just a thought.
hachamacha said:
I've no real idea if this is related but might be possible:
Linux (and probably it's cousin, Android) likely have a similar basic process interface, both use PID, PPID's and PGID's. (process ID's of one sort or another). The PID's "appear" to be just like those numbers you're displaying in your battery stats. In almost any linux or Android shell (terminal emulator for android or Adb shell), you can do a "ps" command and see if the number you're curious about is a process ID as follows:
Via adb:
Code:
adb shell;
ps | grep {the number you see}
If it shows up, check out what ps thinks the process name is. If the process name is "NULL" then supposedly linux won't show a process name over a certain number of characters (or ps won't) and will substitute the PID instead. That might be what's happening.
The PS command can accept lots of options on linux (ps -ef, ps -aux, etc) but on android, it might just output everything without options or switches, so try a plain ps command first.
Just a thought.
Click to expand...
Click to collapse
Won't be able to try that until I get an adapter.
But thanks for the suggestion.