I am a long-time Linux user, and have noticed there's some support for getting vanilla Linux onto Tegra prototyping hardware. Nvidia has some walkthroughs, there's an ARM based Arch district, which I think would be a good starting point. Does anyone have any suggestions on where I should start?
I'd like to see KDE or Meego as a GUI, with dalvik running on the side. I think it'd be a wonderfully flexible tool at that point!
Sent from my MB860 using Tapatalk
This needs to be moved to Q&A or maybe General but certainly not DEVELOPER.
It should be in development
sent from cm7 atrix 1.3ghz
the question is what exactly you want to achieve, is it only to have that linux distro on it or to have it next to android like webtop is now? as much as i saw nvidia has all the tutorials and support for ubuntu, which i dont really like so i was playing around with gentoo for it, but it is quite a nightmare to get it to run like a webtop, i think it should be way more simple getting it to run next to cm7, however gentoo takes a lot of time to compile and set up (but is faster and more space conservative than), so probably Arch is better. as for running only linux you would have to create your own kernel and ramdisk for it probably and than go on from there, since we cant change the bootloader to just load linux directly. just as a side note this should probably be in fact in the Q&A section since there is no real development made here, just discussing options.
What about running Ubuntu netbook edition? I run Ubuntu all the time, it's very stable and fast, but for this application it needs to be small and lightweight, so for that case we could go to the netbook edition. Just a thought.
I think Arch would be easiest, as it uses vanilla sources (Ubuntu heavily patches their packages) and has the most transparent configuration stuffs.
I'm rather familiar with Linux, I'm just less familiar with phone hacking and partitions.
I'd really like to see Linux running in place of android, with the dalvik machine there to be able to run android apps. Android is VERY messy.
I'm thinking the telephony end of things will be difficult, but maybe not impossible. I will be working on this, and will be pursuing it, so I think "development" is where it belongs.
Sent from my MB860 using Tapatalk
Hi killer_siller,
I know this isn't for the atrix, but it could be a good beginning for you.
http://forum.xda-developers.com/showthread.php?p=10181908
Swyped from "Mount" Olympus
nitrox1 said:
Hi killer_siller,
I know this isn't for the atrix, but it could be a good beginning for you.
http://forum.xda-developers.com/showthread.php?p=10181908
Swyped from "Mount" Olympus
Click to expand...
Click to collapse
I've played with that on a few phones, and it's not as good as the experience you get from Native Linux - ala the HD2.
Nvidia has quite a lot of resources available for their Tegra stuffs:
http://tegradeveloper.nvidia.com/category/zone/mobile-development
Here's ArchLinuxARM; they're actively developing Tegra stuffs:
http://archlinuxarm.org/
Here's a Meego dev who got meego working on Tegra2 hardware:
http://wiki.meego.com/ARM/TEGRA2
I think it's a bit dated, though
I think Meego would be the easiest route to functioning native linux on the Atrix, as it's already made for handsets, and they're already working to get android apps to run in it natively.
This may seem like a circuitous route, but you couldn't imagine how powerful this hardware could be when you peel away the android mess.
you might want to check this thread out, unfortunately the package he attached is corrupt: http://forum.xda-developers.com/showthread.php?t=1180800 u think with cm7 it should be substantially easier to get the xserver to run properly. yes meego would be best in fact but everyone is dropping support for it so ...
Hi guys. I hope this is the right place for this question. I'd rather have put it in the development forum, since I expect more devs frequent it than here, but I'm not sure it would be appropriate.
I will be writing a paper for an Operating Systems class looking at the Android OS. Specifically, I intend to compare it with Linux, giving consideration to the optimizations that were made for developing it as a mobile platform. I would like to also incorporate some analysis of the source code. This would likely include compiling a kernel from the source and probably installing some variant of it. I do not have any experience with OS/ROM development but I do have a decent amount of programming experience.
I would like to know if anyone has any favorite resources on the web, or even print, on this topic that would qualify as "academic." Unfortunately, this means forums and wikis are out. As far as I can tell, resources on this topic are scarce—or maybe I'm just not looking in the right place. I would appreciate any input I can get.
Thanks in advance!
bump
10 char
You could browse around here: http://developer.android.com/resources/index.html.
Android is Linux with Google's user space running on top of it. If you're just doing OS-level comparisons, it should be a pretty short report.
Google adds a very small number of things to the kernel, like wake-locks, but those are (allegedly) getting phased out in favor of "native" constructs.
I guess it would be more appropriate to say I'm interested in OS engineering rather than development for the OS, dealing particularly with the kernel.
Are there no major modifications done to the Linux kernel in such respects as scheduling, memory management, paging algorithms, I/O, etc. to optimize for mobile devices? I can't seem to find much that actually discusses how these are implemented in Android. For example, I am aware that there are apps that allow us to change the scheduler: are these just toggles for stock Linux code implementations?
There are a bunch of device drivers, obviously, but the only real kernel changes have to do with something called "wake-locks", which are a specialized form of locking that allow applications to prevent the phone from going to sleep. And one of the Linux kernel guys has demonstrated how an existing construct can be used to the same effect. Google has tried (with varying degrees of enthusiasm) to try and get their stuff integrated back into the kernel because anything _not_ in the kernel is a lot more work to maintain.
Right now, the kernel ARM maintainers are working on improving device management on ARM (currently, there's not much reuse, resulting in a dozen or so different drivers for some common IP blocks), which is a cause near-and-dear to Google's (well, Google's-phone-making-partner's) heart, so Google is probably going to try to avoid doing anything seriously incompatible.
Thanks for the info. I guess Android will have to sit this one out then.
What are the chances we'll see the new Ubuntu for phones os running on our hardware anytime soon?
As far as I understand it it should be just a matter of compiling for our specific soc, making a flashable rom and then flashing, right? They say it can run on android kernels so there shouldn't have to be any hardware interface work that needs to be done, right?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
If you don't mind me asking, how would this make any difference to us?
rangercaptain said:
If you don't mind me asking, how would this make any difference to us?
Click to expand...
Click to collapse
It would enable us an alternative operating system choice, allowing application developers to create processor native applications (rather than using a java virtual machine that's quite resource intensive than running apps on the bare metal) thus using less system resources, enabling faster multitasking, greater compatibility with preexisting applications, enhanced security, and the desktop mode that they are touting is quite nice as well. connect an hdmi dongle and use a bluetooth keyboard and mouse to turn the phone into a desktop computer... there are lots of uses for a bare metal operating system on a hardware platform with restrictive system resources.
there's really nothing wrong with android per se, she's a great OS, but there are a wide number of other approaches to building os's and user experiences. I would consider this pretty similar to choosing to install ubuntu on a PC, or windows on a mac for that matter. it's a matter of widening the variety of application approaches and compatibility. a matter of choice.
I really want to know if this is possible after seeing the demo of it on engadget this morning I'm convinced that this is one os I'd be willing to flash and possibly leave on over android, as amazing as Android is this just better though out in terms of where everything is and speed of access
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
It may take off, if someone is able to best the entire android community as a whole, but the odds of that are "0"...
We would be better served if google took it over, and incorporated the OS into a handful of smart phones. Beyond that prospect, a port for us would be nothing more than a pet project.
This idea is not new, and mention of it can be found in virtually ever forum on this site, and a few devs have met with success on getting a bootable Android device running Ubuntu, but it was a short lived event, as support for the OS is simply not there ATM.
I do agree that a different OS is a good idea, but as a dedicated Android user, I would not be willing to switch at this point, as a stable, functional OS is months or even years away.
Likely the OS would fall the way of RIM, and other OS platforms, albeit, ahead of it's time.....g
gregsarg said:
It may take off, if someone is able to best the entire android community as a whole, but the odds of that are "0"...
We would be better served if google took it over, and incorporated the OS into a handful of smart phones. Beyond that prospect, a port for us would be nothing more than a pet project.
This idea is not new, and mention of it can be found in virtually ever forum on this site, and a few devs have met with success on getting a bootable Android device running Ubuntu, but it was a short lived event, as support for the OS is simply not there ATM.
I do agree that a different OS is a good idea, but as a dedicated Android user, I would not be willing to switch at this point, as a stable, functional OS is months or even years away.
Likely the OS would fall the way of RIM, and other OS platforms, albeit, ahead of it's time.....g
Click to expand...
Click to collapse
While I strongly believe that everyone is entitled to their opinion, the fact of the matter is that it's already running on the quintessential android test bed for the current generation of phones (the galaxy nexus) which means that it should be very easily ported to other, similar hardware (which is most of the android devices out there right now.). if they made this completely open source (which i'm pretty sure they'd have to given that most of the components of the OS are built on open-source licenses), and allowed the already very good and very diverse linux community expand it's functionality, write good apps for it, I think it has some pretty great promise.
my personal standpoint however, is that operating systems for mobile should work exactly like they do for PC's (and macs for that matter). you should be able to install whatever, whenever, without the approval of the company that happens to make the hardware, and without the approval of the company who provides the data and telephone services for the device... it's a pocket computer, not a dumb phone designed for one thing.
I thought Android was Linux and Ubuntu was Linux. Why is one type better than the other? And to run native, wouldn't hardware manufacturers have to write a butt load of drivers? Like the fiasco of upgrading from win2000 to win7.
Ubuntu won't be released til 2014, will older phones like our note1 be supported?
Keep in mind that by 2014 the note1 would be considered old in mobile years.
rangercaptain said:
I thought Android was Linux and Ubuntu was Linux. Why is one type better than the other? And to run native, wouldn't hardware manufacturers have to write a butt load of drivers? Like the fiasco of upgrading from win2000 to win7.
Click to expand...
Click to collapse
hardware drivers always run on the bare metal anyway (usually as part of the kernel, or occasionally as a background daemon service). the point is that android applications are built on top of the java environment which is a virtual machine - it's processes are abstracted and emulated which requires much more system resources than writing in something like c++ for the underlaying hardware. the only compatibility that this would break is that binaries don't work across cpu platforms. if something is compiled for the arm9 architecture for example (what most modern smartphones use, including our note), it wouldn't run on android for x86 or another java virtual machine like bluestacks. in order to get it to run on a different hardware platform you'd either have to emulate a complete device (like the iphone and android sdk simulators), or recompile it for the platform you want to run it on (only useful if you have the source code). the latter method is how linux distributions have been doing things for years. there are virtually identical linux distributions that can run on intel, arm, powerpc, sparc, motorola 68k, etc. etc. they can all run pretty much the same applications (because of the hardware abstraction layer present in the kernel), but in order for it to work, those applications must be recompiled for the appropriate underlaying processor architecture, as the output of a c(++,#) compiler is code that is cpu architecture specific.
also, windows 2000 and windows 7 were designed for the same (or similar) underlaying hardware problems. windows 2000 to windows 7 was mostly a piece of cake. whereas the move from windows 98 to windows 2000 or windows 98 to windows xp was difficult because windows 9x and windows 2000/xp use a different variety of hardware abstraction layer and thus different drivers must be written as drivers designed for one HAL won't work with another. (same thing for major linux revisions. the HAL in the 2.4 series of kernels is different from the one in 2.6 series of kernels which means one has to rewrite device drivers in order to get some less-than-standard hardware working.
So cp....
your a smart guy...
Get it going for us.....
you've got the skills we need to pull it off....g
gregsarg said:
So cp....
your a smart guy...
Get it going for us.....
you've got the skills we need to pull it off....g
Click to expand...
Click to collapse
Actually, If i had access to the sources (that by all rights should be open thanks to the way the gpl is designed), I'd be happy to build a rom and help with the development efforts. I'm pretty decent at optimizing linux distributions for arm hardware. we should all petition canonical to release the code post haste.
I would love to see ubuntu ported over to phones. I almost fell off my chair when I heard of the idea that your phone could just connect to a monitor/keyboard/mouse to become a fully fledged desktop computer. This would literally replace almost all of my gadgets into one device. I wouldn't need a laptop, an ipod, a dvd player, or even a gaming console possibly as well.
I've been using ubuntu for a number of years and would be overjoyed to see almost all of my electronics and computing essentially made into one pocket sized device. The possibilities are so great for this kind of leap in technology and it almost seems to be the inevitable succession in personal computer technology. This could possibly be the beginning of the end for laptops, desktops, tablets, and netbooks/ultrabooks. All data would be transmitted using flash memory or transmitted OTA instead of spinning disks or other media.
If the source code is released, and I'm sure it will since Canonical has done a decent job of running Ubuntu lately, I hope someone brings it to the i717 because then I would probably sell a lot of electronic equipment
The release will never happen to allow a single, all inclusive device.
Ubuntu or not, there are too many hands in the pie, and billions of dollars on the table.
The apples, and Samsungs of the world will go at it until the day we die.
They all want the biggest piece, and will squash anyone that gets in their way.
Ubuntu would need a home run piece of code that emulates a magic carpet if they ever hope to slay the beast.
And if they did, I'm not so sure that people would embrace the one stop shop mentality for a single device anyway.
It simply stinks of yet another apple type monopoly in the making.
I support the idea, but it's the logistics that kill the deal, money driven logistics of course.....g
gregsarg said:
The release will never happen to allow a single, all inclusive device.
Ubuntu or not, there are too many hands in the pie, and billions of dollars on the table.
The apples, and Samsungs of the world will go at it until the day we die.
They all want the biggest piece, and will squash anyone that gets in their way.
Ubuntu would need a home run piece of code that emulates a magic carpet if they ever hope to slay the beast.
And if they did, I'm not so sure that people would embrace the one stop shop mentality for a single device anyway.
It simply stinks of yet another apple type monopoly in the making.
I support the idea, but it's the logistics that kill the deal, money driven logistics of course.....g
Click to expand...
Click to collapse
Too true, it's all about the money in the end, even with free stuff.
Now that you mention it, it does sound a lot like some sort of Apple type ploy to get you to buy their things... either way I hope it happens someday
Hi everyone, I didn't know exactly where to post this, but I assumed that an overall Android Platform question should be posted here. Anyways... I'm doing a research paper based around the Android OS, and I'm looking for credible, timely information to use in my paper. I've looked in multiple databases for articles that talk about what I'm looking for, but almost every article I read through talked about Androids VS. iPhones, or data encryption, and other unrelated topics.
I'm looking for articles, reviews, pretty much anything out there that will provide enough information to answer these few questions:
- How limiting is the Android OS?
- How well/poorly is the Android OS optimized for the devices that utilize them?
- What are some good/bad properties of the Android OS?
- What are some features of the Android OS?
- Is the Android OS "groundbreaking" and if so, what about it makes it so "groundbreaking?"
That's really it, anything else that I could add to the paper helps that much more!