I was curious if any of the dev gurus had a nice Linux setup that they could make a Android Development distro from?
I keep running into repo issues when trying to set up my system. This led me to go.....'why isn't there a precompiled dev distro??'
If there is....please point me towards it, as I have been searching, but if it exist it's in a deep dark part of the internet I'm yet to discover.
Thanks
(ps. I wanted to make a clockwork recovery for an unsupported device.)
I keep running into repo issues when trying to set up my system.
Click to expand...
Click to collapse
I think the best Idea is to set up an Ubuntu based system at the moment.
With fedora based distros (fuduntu) I allways get some issues as well.
Some month ago I ran into a site that provided some Ubuntu based virtual box images with the Android SDK installed, but as it changes alot lately I don't think it's up to date, and I can't find it anymore anyway.
Maybe the guides aren't accurate anymore??
The distro I tried was the newest Ubuntu, but with everything I attempted to install I would get permission issues and sometimes the links to repo's weren't live any longer..
Perhaps what I should ask is 'Where can I find an accurate, reliable guide to setting up my linux distro for dev use?'
eh, I'm not completely dumb to Linux, but I require a bit of assistance :/
Ya, Ubuntu is kinda mandatory considering the way the kernel in AoS forked from it. Ubuntu is a common one, should be able to do what you need off the USB bootable even.
Really depends on your hardware setup. I've been playing around with a portable Puppy lately - something I can use at work and on my ancient semi-sandbox laptop. If you like I can put a vanilla package together for you.
There is a distro from 2010 made by a beginning builder specifically for linux/android developers. I haven't used it but it may be worth a go: http://www.simply-android.com/discu...oid-developers-have-their-own-linux-distro/p1
I have searched a number of ways for a definitive set of steps to install Linux applications, fix apt-get dependencies, and create icons for those newly installed applications in Webtop on my Atrix 4G. I have installed Debian Linux and Xterm on my Webtop, and have successfully used the VI commands to unhook the new 4.0.1 version of Firefox, but my success ends here.
What I have found in my searching is piecemeal, version specific, or so highly specialized that a Linux noob like me has no chance of pulling together a successful install. I would like to install Gimp, OpenOffice, and maybe even a desktop application (like Gnome), and am having an appreciable amount of difficulty closing the circle.
I would be happy to buy a cup of coffee for someone who can put together a sequential list of steps (preferably with the actual Linux commands) that can be adapted to accomplish this. Thank you!
Sent from my Atrix 4G running Homebase 5.2 with Fauxs enhanced stock Kernel
I'm definately no Linux Guru, but This is what I did to install openoffice on my webtop. (assuming you followed the steps to fix the repo listed in the Webtop2SD post)
sudo apt-get install openoffice.org
and that was it....now running it nearly every day with no problems, good luck.
I installed Synaptic. It's a package manager. Just select the package you want to install and it does it.
http://forum.xda-developers.com/showthread.php?t=1279724&highlight=synaptic
If the Synaptic install errors, it should suggest what to run to fix it.
use backports
Use pdmenu (the penguin) to open a shell, bash will do nicely and type "apt-get install synaptic" as suggested by robrj. Then do a search for backports and libreoffice. That should help you get started. Remember, this is just Debian squeeze and the Debian support groups have the answers you need until you jump back into android or webtop mods.
So, I actually own an Atrix 2, but I figured I'd post this here as webtop/linux development is much more active. I've gotten my device set up with a custom linux installation, but it seems the OS could run much faster were it not hampered by the phone running its own OS at the same time. Would it be possible to, say, modify the android boot scripts to launch webtop instead if it detects a dock? Just have the phone with a blank screen fully powering the /osh environment on the lapdock. Once undocked, you'd have to manually reboot so the system could actually boot up android again.
It seems like there's no reason why this shouldn't be possible. Just a simple boot script that uses the phone's ability to detect whether or not it is docked; if it is, boot into webtop, if not, run android. Once, my phone had a forced reboot while I was in webtop mode. However, instead of webtop going down with the phone, I opened the mobile view and actually watched the phone's boot animation and boot process, with webtop still running. Maybe there could be a script that runs android until webtop is fully "hooked", then shuts down android and continues running webtop?
Secondary question, is it possible to upgrade the linux install itself with the sudo dist-upgrade command?
I think it is actually quite possible to do this. The reason I say that is because I have seen the Android component of the phone reboot whilst being docked into the Lapdock. The whole Android environment is then reloaded once again meaning that Ubuntu is running as the host OS.
The challenge is if you can get it to boot directly into the Ubuntu shell primarily as opposed to going directly into Dalvik.
bchliu said:
I think it is actually quite possible to do this. The reason I say that is because I have seen the Android component of the phone reboot whilst being docked into the Lapdock. The whole Android environment is then reloaded once again meaning that Ubuntu is running as the host OS.
The challenge is if you can get it to boot directly into the Ubuntu shell primarily as opposed to going directly into Dalvik.
Click to expand...
Click to collapse
That's exactly what happened to me! Te webtop environment stayed booted, but just ran the boot script again. All you'd have to do would be to edit the android boot script to check if RM_IS_DOCKED, right? Or does the webtop rely on certain android components to run?
Secondary question, if I were to go the route of letting it load android, then webtop, then unload android, how would I send a command to android to shut down without *actually* shutting down?
Sent from my ATRIX 2 using Tapatalk 2
I dont know enough about the technical details of the boot scripts to do this. But just as a observation, it does look plausible from the Dalvik rebooting separate to the Jaunty instance I have running.
I would like to know how to do this as well
Sorry guys, this is technically not possible.
At boot, the Linux kernel starts first. It is a custom kernel with Android patches - that implies, as far as I know, some extra security (only users with uid of 3000something have IP access) and something that breaks udev. The latter thing messing up init scripts of most modern Linux distros.
Then the Dalvik VM is started - which is the one that sucks the RAM.
Then the mountosh command is started, which takes care of mounting the webtop partition.
Then ubuntu.sh is started, which takes care of initializing the webtop environment.
The "docked" event launches a script in /etc/init.d (don't remember the name, probably stg like StartWebtop.sh) which starts the Moto's customized Xorg and some other software for the trackpad.
I think that what you have seen rebooting is probably the Dalvik VM - not sure why, I've seen it too at times.
IMHO webtop is slow because the Linux apps in Ubuntu are memory-hungry and not optimized for ARM.
I think Moto was hoping that HTML5 apps would take off sooner - so to make webtop useful just with the bundled firefox - but that never happened.
In the meanwhile, android tablet apps are getting more and more mature, and they are optimized for lower memory and less CPU than Ubuntu apps (eg Quickoffice vs Libreoffice, maildroid vs thunderbird). Hence Moto killing the webtop the way we know it and replacing it with TabletUI ICS.
Sent from my MB860 using xda premium
Interesting thread. I have always been amazed by the Atrix with webtop (only had it for a few days, until I hard bricked it ).
Actually, from what I was able to see, it was not Android as host OS, then running Ubuntu. It was 1 kernel (the Linux kernel for Android, as we always have on an Android phone), and on top of that kernel, two different OSes: "Android" and "Webtop (ubuntu based)". It was especially visible when running ps from one or the other, you could see there was actually no distinction, no isolation between both. From Android you could see all the webtop processes, and from webtop the android processes as well. It was amazing!
(confirmed in https://books.google.nl/books?id=E9...btop a second OS on same linux kernel&f=false, Figure 6.8)
Technically it 's the once and only time I have seen this happen actually. Never before, and never since.
So, yes, it was very possible to "soft reboot" any of the two OSes and keep the other one running, as long as the kernel was kept running (not rebooting the phone). That would mean restarting the Android zigote or Ubuntu/Webtop init (or whatever was doing that function).
Built android last night, AOSP off the latest branch (default path or w/e, kinda new to this) on a clean install of ubuntu 12.04 lts in VMware workstation.
Everything seemed to go fine, although it was tricky to get libgl1-mesa-dri:i386 to install. Had to go several dependancies back manually and check into what was getting installed, probably should have paid more attention because it seems to have uninstalled some critical packages including xorg and ubuntu-desktop.
Rebooted the VM this morning and still can't get in trying to undo what it broke.
Why is that package needed ( libgl1-mesa-dri:i386 )?
Why does it require breaking your desktop setup?
I really hope I don't have to redo the whole config (fetching the source etc) I was really hoping to get to making source edits tonight!
EDIT:
I was able to text boot, manually reinstall xorg and ubuntu desktop, and startx although I didn't get unity back. Doing "startx" then hitting control-alt-t gave me a terminal and I'm right back to building!
Wierdly "emulator" didn't work. Unrelated but does it have to be same boot as when you built or something?
Any help is appreciated!
Hi guys,
I got the following problem and haven't got enough experience to solve it myself:
I used the app linux deploy to install a debian wheezy distro on my HTC Sensation. The problem is now, that the appache2 server, for example, doesn't start or does get shut down immediately after startup. I guess that it's some problem with the user rights ("chroot"? totally don't know ..).
As I'm not much of an linux expert I don't know what I could do. The EXACT same installation steps brought me a working apache server on my Samsung Galaxy Tab 2 10.1. So it has something to do with the HTC Sensation. I've tried several Custom ROMs (and some different kernels allready). I tried different distros as well.
What could be the problem? What could I try next? THANKS! :cyclops:
//edit: Just tried my linux.img at a Nexus 5. Worked right out of the box. I'm using the copied linux.img now, so it's the exact same image and can't be an installation problem. Works on other devices but not on the HTC Sensation.