So Canonical has demonstrated a prototype version of an environment for Ubuntu, based on the Xorg X Window environment, in which Android Apps can be run. For many folks that like to experiment and play around, for instance with the installation of Android to a computer, this is pretty exciting. After the project is optimized a bit more, I guess, the source code for the emulator will be released. Anyways what I'm getting at is that the article points out that a main purpose in this is to provide users the option to run Android programs in their current Ubuntu environment instead of a full-on Android installation to their machine. Seeing as the Android OS version for computers has a long ways to go before people can really install it and have full functionality without having to do a lot of work themselves, this has my hopes high. Here is the full article so you can stop listening to me babble and see what the guys at desktoplinux had to give us:
http://www.desktoplinux.com/news/NS7172257171.html
I know this is an old article, but I figured many people had never seen this and could use the bit of info.
Related
So in this thread it tells you how to install pc operating systems like windows and linux on the Evo 3D.
http://forum.xda-developers.com/showthread.php?t=1459153
This, is freaking awesome. This one is a big breakthrough.
----
Here is the thread in the Nook Color forums for ubuntu on the device:
http://forum.xda-developers.com/showthread.php?t=1055954
----
These two threads are native installs, not using some client to access the installation, the device itself is the client as it should be.
This is not some chrooted virtual OS simulation, but the real deal installed to the device.
----
In the back of my mind i've wanted to play with ubuntu installed on the MT4GS, but not a virtual installation I want it installed and running on the device natively.
I definitely don't have the time to do this and a lot i'm trying to do around here even if I wasn't in my busy season for work.
Dropping this information so I can find it later when I do get to trying to get ubuntu (and now windows XP looks like a possibility) installed on this device.
If anyone else feels like looking into this, here's a good place to start. If anyone comes across any other projects that are the real deal and not virtual installs please post links here.
Have fun!
Blue6IX said:
So in this thread it tells you how to install pc operating systems like windows and linux on the Evo 3D.
http://forum.xda-developers.com/showthread.php?t=1459153
This, is freaking awesome. This one is a big breakthrough.
----
Here is the thread in the Nook Color forums for ubuntu on the device:
http://forum.xda-developers.com/showthread.php?t=1055954
----
These two threads are native installs, not using some client to access the installation, the device itself is the client as it should be.
This is not some chrooted virtual OS simulation, but the real deal installed to the device.
----
In the back of my mind i've wanted to play with ubuntu installed on the MT4GS, but not a virtual installation I want it installed and running on the device natively.
I definitely don't have the time to do this and a lot i'm trying to do around here even if I wasn't in my busy season for work.
Dropping this information so I can find it later when I do get to trying to get ubuntu (and now windows XP looks like a possibility) installed on this device.
If anyone else feels like looking into this, here's a good place to start. If anyone comes across any other projects that are the real deal and not virtual installs please post links here.
Have fun!
Click to expand...
Click to collapse
Regardless of what impression you may have, it is ABSOLUTELY IMPOSSIBLE to run MSWin on ARM hardware natively. The reason for this is that MSWin is x86 and ARM is... ARM. The approach used in the first link is to use BOCHS (pronounced "Box"), which is a VIRTUAL HARDWARE EMULATOR. It requires a host operating system to be functioning in the background, in this case Linux.
As for Ubuntu... well sure. No problem. Its Linux and the phone runs Linux. Not that big of a stretch to replace the Android parts with GNU.
Note that NONE of this is any kind of "great breakthrough". Bochs has been around for a VERY long time. First OPEN SOURCED in early 2000. Yeah, 12 years ago. As for Ubuntu... well I suppose that the main reason that most people aren't making a native android replacement out of ubuntu, is that not many people are all that interested in it. Cute in theory, but not practical.
What would be a more worthy project would be to upgrade android to GNU libraries and utilities. This would afford us an actually USEFUL balance between the two. Also the ability to run X *through* android without having to do stupid things like VNC. Have the proper interface ***AS AN ANDROID APPLICATION***, leaving Android to work (i.e., phone calls, etc.) while simultaneously offering the standard Linux applications.
My thought though, is that this is becoming less and less important. Firefox is on Android now, the Document foundation has announced LibreOffice for Android -- supposed to be by late 2012 to early 2013... GIMP has no place on Android... That certainly covers the basics.
Appreciate the post. I didn't have time to dig into it too deeply, so took it at face value for the impression I got. Happened to come across it in passing and didn't want to lose track of something vital to the future dev of a project like this on the doubleshot. (but definitely this doesn't belong in the dev section at this time - just clutter there.)
I was hoping people would add to it, especially the way you have, who had more of an understanding of what's going on there - I didn't realize that it was a virtual environment for the windows stuff, but it did seem to good to be true.
Even if no one responded I figured the thread would get pushed down out of the way, but still be here when I got the time to come back to it.
----
My reason for running native linux on the device itself is to be able to use the Android SDK and tools without needing a computer to do so. I have 2 of these phones and a Nook Color. The NC has USB host support, so I could plug the doubleshot into it without frying either device. (yes, i'm blending android and linux concepts here - but usb host support in android shows that it's capable of doing it)
Even from one doubleshot to the other I could use wifi adb for a lot of stuff without plugging them into each other through USB and frying the phones. So that would be a victory as well.
The lack of a hardware charging circuit in the doubleshot makes the worry of frying the phones a big deal, power transfer through USB is a big hurdle to jump in management.
Beyond that - the doubleshot is powerful enough on hardware specs to be able to compile a kernel, but that's not gonna happen through a virtual linux install because the overhead is too much. A native install might just be able to do it though. Won't know until I try, but it's worth the work to get to the point of trying, even if it doesn't work out.
The Nook Color probably won't be able to compile a kernel - it's asking too much from a device not really able to handle that.
Getting what I mentioned above to work would mean I could do all my dev work with what fits in my pocket, and let me keep working wherever I am.
I do like the idea of an app to work with this through Android itself - but I don't see how I could use the SDk and variety of user-created tools without a native linux install. Worth pursuing either way though.
If anyone has anything to add, i'd be welcome to hear it. Just understand this is not a project i'm working on or actively pursuing right now - but fully intend to down the line.
Actually blue. There is a thread somewhere that has a step by step on installing ubuntu on gingerbread. I meant to add it when I added the backtrack link. For some reason I didn't, I probably forgot, I actually think the link for it is in the backtrack thread in the sticky.
If I do find it ill let you know.
Sent from my ICS Splashed using Tapatalk
I will be honest, I'm not an Android developer - at least not yet. That said, I'm looking for an environment to performance test apps. More or less, looking for a sandbox to test apps with. For this, it doesn't really make sense to use a real device. So I'm debating between the SDK emulator and using Android x86 in a virtual machine. Each seems to have strengths and weaknesses.
I think the main advantage of the SDK emulator over Android-x86 is that it can be used to test apps for different AVDs very easily. Plus, it natively supports NDK ARM code and can be used with x86 code with version 17 (right?). The downside, is that it is painfully slow.
On the otherhand, Android-x86 has much better performance itself, but currently (maybe not for too much longer) lacks support for ARM-specific code.
Another option is BlueStacks, but I haven't looked into it much yet and am not sure how well it will suit my goals.
I was hoping to get a little survey of opinions regarding the two from developers and folks more familiar with Android than myself.
CurlySpiral said:
I will be honest, I'm not an Android developer - at least not yet. That said, I'm looking for an environment to performance test apps. More or less, looking for a sandbox to test apps with. For this, it doesn't really make sense to use a real device. So I'm debating between the SDK emulator and using Android x86 in a virtual machine. Each seems to have strengths and weaknesses.
I think the main advantage of the SDK emulator over Android-x86 is that it can be used to test apps for different AVDs very easily. Plus, it natively supports NDK ARM code and can be used with x86 code with version 17 (right?). The downside, is that it is painfully slow.
On the otherhand, Android-x86 has much better performance itself, but currently (maybe not for too much longer) lacks support for ARM-specific code.
Another option is BlueStacks, but I haven't looked into it much yet and am not sure how well it will suit my goals.
I was hoping to get a little survey of opinions regarding the two from developers and folks more familiar with Android than myself.
Click to expand...
Click to collapse
I always use the sdk emulator OK its a little on the slow side but quickly let's you test apps on a range of set ups. Plus having it integrated with eclipse makes the process even quicker
Sent from my GT-N7000 using xda premium
Here's a link to the project:
http://code.google.com/p/zgrom/
A cut&paste from the page:
ZGrom is a gaming oriented distribution for Sharp Zaurus PDA devices. It's a console based distribution built around the Gmenu2X SDL GUI. ZGrom has a wide selection of quality emulators, game engines and apps. Currently, ZGrom only supports the following Zaurus models:
•C-1000 - Akita
•C-3000 - Spitz
•C-3100 - Borzoi
•C-3200 - Terrier
ZGrom comes with GINGE. In a nutshell, GINGE enables ZGrom users to run unmodified GP2X binaries. Some of the emulators and game engines that come with ZGrom are plain, unmodified GP2X binaries that execute on Zaurus devices via the GINGE static loader.
A link to the gmenu2x page:
http://mtorromeo.github.com/gmenu2x/
A cut&paste from the page:
GMenu2X is a frontend application targeted at embedded devices, originally developed for the GP2X and successively ported to other devices.
GMenu2X provides an easy to use interface with quick access to the games and applications of the device trough links similar to those found on PC's desktops.
Its interface is fully customizable with skins.
Other features include: built-in selector for emulators, manuals and readmes integration, built-in overclocker, gamma and volume configuration, ram timings tweaker.
I started working with these but like with other projects... i'm short on time these days. The last of my efforts had a working kernel for these, only a keymap was needed to give to the zgrom developer to build a rootfs, and for someone to text and debug.
IMO the better way would be focusing on developing Android distro, because probably most people are still waiting for working Android on our beloving UNI! Anyway, your efforts are great and mainly because of you UNI developing is still alive!!! Good luck!!
l2tp said:
IMO the better way would be focusing on developing Android distro, because probably most people are still waiting for working Android on our beloving UNI! Anyway, your efforts are great and mainly because of you UNI developing is still alive!!! Good luck!!
Click to expand...
Click to collapse
Lol, I know, I’m taking a break waiting for another project to finish up:
http://forum.xda-developers.com/showthread.php?t=1948803
I’m working on shrinking android now; deleting unneeded library’s and functions to lower memory/processor requirements and running processes. This OS is better suited for people who don’t use their universal as a phone and only have 64mb of ram. I don’t have time to work on this either, the question “Who wants to port ZGrom?” wasn’t rhetorical; I really want someone to pick up where I left off porting it. And android for universals is mostly done all hardware except the cams work. Power saving, gprs, sound on both ends of the call all work… I just need to trim and speed it up….and learn some arm assembly to add in iwmmxt optimizations.
I understand that 64 MB of RAM is too little to run any recent Android version (and by recent I mean higher than 2.2), so it'd be good if there was some alternative OS to bring life to old Universals with the standard RAM - even if that new 'life' doesn't including phone abilities. I don't think the PXA 27x CPUs aren't really that optimized to run Android either (Android can be slow on ARMv6, let alone ARMv5). I'm not telling you to give up on the Android thing; just trying to make people realize notime can't focus forever on something that can't be further optimized... but if it can, then just go ahead
In that sense, I support any development efforts towards something that's not Android.
Also, the work done in porting recent Linux kernel versions can be used not only in Android but in any other Linux-powered OS porting. I may have a go at it... once I format my computer with a bigger ext4 partition (currently out of space to install any kind of cross-compiling tools or SDK) - and this can get delayed for several months.
I was playing around with my Universal (with a dead battery), running old Linux distros on it (with things like Qtopia and Opie), when I started thinking if there wasn't a more recent thing to run other than Android. Then I remembered I had promised to try to port this thing once I got my computer formatted...
Actually I have already formatted my computer and now I have a mostly free >250 GB ext4 partition. I'll only be able to start working on this in the beginning of July, however.
This seems like the perfect use for a Uni that doesn't survive when it isn't charging.
Here's an idea ARM Based Hackintosh iOS Style. Get iOS running on an ARM development board or Android phone. :highfive: You guys know that would be bad($). Because creating drivers can be a problem since there are many ARM Platforms lets choose one device then branch out. If anyone is up to the task I'll help found what I can.
Toxic_Dragon said:
Here's an idea ARM Based Hackintosh iOS Style. Get iOS running on an ARM development board or Android phone. :highfive: You guys know that would be bad($). Because creating drivers can be a problem since there are many ARM Platforms lets choose one device then branch out. If anyone is up to the task I'll help found what I can.
Click to expand...
Click to collapse
Sounds cool, not to hip on the mac side of things; but I've seen some things. I've two cence to throw in:
Check out qemu or limbo for android. Their all about tight prossessor emulation. This may enable you to emulate the hardware that normaly runs iOS.
Check out java. I've seen some fantastic and fast development in translating programs, sometimes on the fly, in such a way that they become hardware independent.
I'm up for seeing about a port to linux that can be dule-booted for development as that may lend to branching for Android easyer. As far as a device to choose I'd sugest something older but not so old as the g1, though that would be fancy, because cost will be lower, documentation more prevolent, and paralel minded progects may already have a levereg point that you can start from.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Or
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
I like this phone. Feels good in my hand. Did the job fine with Froyo. When the GB update never came, rooted it and began a new hobby (obsession?). Now running a 4.4.4 Omnirom. Works mostly quite well. Doubtful if there will ever be Lollipop.
I do not need a quad-core screamer. This is a mobile phone and information device. I am not playing Grand Theft Auto on it, and if I spend time viewing my favorite flicks, there will be no battery left when I need to phone home. Wife will not be happy (unless here battery is also dead for similar reasons so will never know).
However, more and more apps will not run. Armv6 is definitely on the outs, even though some providers still sell such phones. Running old Maps version, Google Now does work, sideloaded, with an online-voicesearch-wrapper. Not bad, in all.
But maybe time to get a newer device. Or maybe another OS ...
Android was designed to be a Java-based Linux. Apps written would simply install and run on any hardware. No need to compile for that Atom or other chip. Simply played. The way it was supposed to be. (Gnu Linux depends on Gnu C and C++ compilers, and every distro needs to maintain app package variants for various HW architectures. Android was to be the alternative with one app store ...)
and then, devs started incorporating pre-compiled JNI (Java Native Interface) components. These are compiled (using the Gnu compilers?) for specific architectures. Read Armv7. Lets out our devices, Intels, etc. It is too much trouble to maintain multi-architecture apps this way. Armv6 is obviously obsolete, so goes by the wayside entirely. Most apps are not opensource even if I were to compile them myself.
This destroys the whole idea of Android and Google is the worst offender. How long till that shiny ridiculously priced flagship ends up like our device? How long to only 64 bit is supported (definitely need 64-bit on a ... phone!)? How long till Armv8, 9, .... Maybe time to forget about Android all together. Google is the prime offender.
Problem is that Windows and Ubuntu both need compiled Apps (though QML and HTML5 should be portable). Both do look good. Put in the Dalvik VM, just like Java gets installed on any distro, and made in the shade, can keep the more reasonable apps. Gnu tools should be available for Ubuntu.
Do not know whether this is the place for this tirade, but ... what say you?