Related
Hello all,
if you are like me, you love to do things by yourself and see how it works. In this thread I'll show you how to create your Linux environment in order to create and compile your own roms - any version (1.5, 2.3, etc etc). I had soooooo many problems to make it work, so here is THE thread
BE CAREFUL : this thread is ONLY to set up the OS. The Android you will compile will not be compatible with your x10 as it needs to be "edited" for our phones. It basically shows you how to get ready
Note : parts 1 and 2 explain how to set up Ubuntu into a virtual machine in Virtualbox. If you don't virtualize Linux, if your Ubuntu is already installed, etc etc you can directly go to 3. It's just here to explain how to install Ubuntu.
This tutorial works of course for any "hard installation" of Ubuntu (I mean not in a Virtual machine) and in any virtualizing software (Virtualbox, VMWare, etc etc). I've dropped the Virtualbox tutorial because the software is free
1. Requirements
2. Set up Ubuntu 64 bit (Virtualbox)
3. Set up Android Source dependencies
4. Set up Android Source
5. Regular use
1. Requirements
A working computer, capable of virtualization (if you don't want to wipe your Windows or your MacOS X !) and with Internet connection
Few Gb on your hard drive (10Gb minimum ! Recomended : 15-30Gb)
As much RAM as possible (Minimum 1024Mb), and as powerful CPU as possible (Core2Solo, Core2Duo, ...)
A bit a time
2. Set up Ubuntu 64 bit
Download and install the latest Oracle VM Virtualbox for Windows
Download latest 64-bit Ubuntu Linux (as .iso package) - you can store the file wherever you want.
(Optional) Download the VirtualBox v4 extension, this will allow you to support improvements like USB2.0... Install : once VirtualBox will be installed, File>Preferences>Extensions>Add... If you get an error (Error 1), try to put the file in a "very simple" location (like C:\) and reinstall.
Once you've set up Virtualbox, run it. Click on "New", then follow the wizard.
Make sure you set the following :
Operating System : Linux
Version : Ubuntu (64 bit)
RAM : 512Mb (you can adjust more, but avoid use lower than 512Mb - I use 2Gb)
Create a new hard drive : set it variable size or fixed sized, but you'll need at last 15Gb to get all the files. To feel confortable, I use 30Gb (variable)
The computer is created, now run it. It will say there's no OS. Click on Devices > CD/DVD > More CD/DVD... Here is you virtual player. Click on Add, and select the Ubuntu .ISO file you downloaded. Then, choose it in the list, and click Choose. Now, you can restart the virtual machine by clicking Machine > Restart.
The computer should restart from the virtual CD, so install it to your virtual hard drive - regular install, same as if you were installing it on a physical HDD.
Once it's installed, do not forget to kick the .iso file from the virtual player for you not to start always on the CD
3. Set up Android Source dependencies
In Ubuntu, do right-click on the upper bar (where are Applications, Shortcuts...), and click Edit Menus. Then, go to System > Administration and tick Software Sources. We need to do this because Sun is highly restrictive on access to Java setup files...
Close that, then click on System > Administration > Software Sources.
Enable all sources, then on the second tab, tick the two Canonical sources (the most important ones, as these sources allow to install Java !)
Close the window and allow to refresh the sources (if you don't, next steps won't work).
Go and read the official Android Source page. That's what we're going to do.
Run a terminal, and copy/paste this : (this is a corrected setup, it should work like a charm -- please tell if it's not)
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl sun-java6-jdk zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev
After setup complete, make sure Java works, by typing
Code:
java
and
Code:
javac
This should return help on both commands. If one of these doesn't work (ie. "command not found"), your environment is not configured properly.
4. Set up Android Source
Create a dir called "bin" in your user dir.
Code:
cd ~
mkdir bin
echo $PATH
Then, type this :
Code:
curl http://android.git.kernel.org/repo >~/bin/repo
chmod a+x ~/bin/repo
Next step is to create a folder where we'll store Android sources we work on. You can place it and name it as you wish, let's call it "android" and place it on the user folder.
Code:
mkdir android
cd android
Then, run this command :
Code:
repo init -u git://android.git.kernel.org/platform/manifest.git
If it returns "command not found", restart Ubuntu !
Enter username and email, although I'm not sure it's useful for our use -custom roms-.
Now, let's get the files ! Type
Code:
repo sync
and wait... Wait... Wait... Lots of commands, of "Resolving deltas", "Receiving", etc etc. It can be very long (depends of your Internet speed), just wait...
Finally, let's register the public key and finalize setup process. Type
Code:
gpg --import
And the cursor will down a line and nothing will appear. Stuck ? Broken ? Woooops ? Not at all ! Program is waiting for you to type the key, which is sooooooo big. So, copy and paste all this :
Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
/HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
=Wi5D
-----END PGP PUBLIC KEY BLOCK-----
Once pasted, hit CTRL+D, this will make the program to register the key, and will display the key has processed.
Everything is now done, you have all the sources and you are ready to create your own roms. You can edit files simply by double-click, or use any software you want.
If you want to compile, simply run a terminal, go to your folder (remember it is cd android (MS-DOS-like command), where android is the folder you defined above) then type
Code:
make
. After a long time (depends on how much RAM you assigned to the machine, 512Mbits is slow), you will generate IMG files.
5. Regular use
If you want to get the latest source files (ie you have 2.1 files and want 2.2.1 files), simply run a terminal, go to your working folder and type
Code:
repo sync
. This should do the trick (correct me if I'm wrong)
Compiling sources takes hours to process, and you may want to kill the compile or pause it. You can then abuse of these keyboard shortcuts (common to Ubuntu OS) :
Code:
CTRL+C
will kill the process. Use it carefully, as it instantly kills it with no prompt.
Code:
RIGHT CTRL+P
is a Virtualbox command. Il will pause the whole Ubuntu (and also your process), and makes the screen ugly/gray (it just stuck the screen on Virtualbox v4.x). This is helpful when you run a Virtual machine, as you can pause the OS and make your computer to sleep/hibernate (or save an image - do NOT turn off your computer, as it will turn off the Virtual machine also !). Out of sleep, you can type again RIGHT CTRL+P to make the process to continue.
** Please note it might be risky to flash your phone with the stock rom you compiled (I mean with no modification), as this is not intended to work on X10
** Please note this install is for AOSP and NOT for Android SDK (you can install it with ease).
What's the difference ?
Android Open Source Project (AOSP) allows you to get the source code of the Android Operating System, in order to improve/change it, and create your personalized Android operating system
Android SDK allow you only to create and edit apps for Android Operating System.
Please note that compiling takes hours to process ! (3 hours or more)
** For any question, deeper info : please FIRST read official documentation. Easy to use, you'll get all info ! **
man...did you ever stop?!
THANKS FOR INFO. If you can explain how to make system images for our X10 then we can use the dual boot option to make gingerbread or froyo roms for dual boot using Zhidu chargemon file.
I am not clear on making and android system image for the x10. can we extract a system image from a running rom? that way I could make a system image of black freedom and we can all dualboot it instead of installing it.
rendeiro2005 said:
man...did you ever stop?!
Click to expand...
Click to collapse
Lol I can't stop
@SuperUserMovado : I'd love to know, unfortunately I am like you - I don't know how to do this. I'm gonna get several info there and there and try to do some stuff
Regarding Zd's Dual, please note it is not compatible with his xRecovery, which makes things a bit boring when you want to easily install a custom rom AND benefit of Dual Boot.
Dual boot by the way is an excellent idea, but it has limitations (of course), like no SD card mount and few other things because it run from SD card and not from NAND.
EDIT : here is a good start : http://source.android.com/porting/index.html
I have just started playing with this and have compiled one aosp rom from source. I think it can be extracted from a running rom but I'm not sure how yet. On the other hand it looks like the source is available on the se dev website. I'm having trouble downloading it... not sure yet if its on my end or theirs.
Here's the error if someone could help me out: (Ubuntu 64bit)
Archive: /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip
[/tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
zipinfo: cannot find zipfile directory in one of /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip or
/tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip.zip, and cannot find /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip.ZIP, period.
Check this site out as well. The whole site is really helpful. I'm in the process of compiling a captivate rom with some slight changes and i hope it works.
Edit: Btw if you get the error repo not found, type this into the command line
code:
echo 'export PATH=$PATH:$HOME/bin' >> ~/.bashrc
then close the terminal, reopen another one and it should work
@superusermovado
I'm pretty sure you use unyaffs for the system.img and split_bootimg.ph for the boot.img.
That's how to decompile an update.zip.
From there you recompile as usual. I'm not going to post the instructions because they are all over the net.
Hint: Andy rubins tweet lol
gavriel18 said:
I have just started playing with this and have compiled one aosp rom from source. I think it can be extracted from a running rom but I'm not sure how yet. On the other hand it looks like the source is available on the se dev website. I'm having trouble downloading it... not sure yet if its on my end or theirs.
Here's the error if someone could help me out: (Ubuntu 64bit)
Archive: /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip
[/tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
zipinfo: cannot find zipfile directory in one of /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip or
/tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip.zip, and cannot find /tmp/X10_X10mini_X10_minipro_X8_2.0.A.0.504.tar.gz-4.zip.ZIP, period.
Check this site out as well. The whole site is really helpful. I'm in the process of compiling a captivate rom with some slight changes and i hope it works.
Edit: Btw if you get the error repo not found, type this into the command line
code:
echo 'export PATH=$PATH:$HOME/bin' >> ~/.bashrc
then close the terminal, reopen another one and it should work
Click to expand...
Click to collapse
Thanks for info
About this package, what's the content ?? The easiest way is to download from XDA the generic global rom, it's the same -- with no bug
Perceval from Hyrule said:
Thanks for info
About this package, what's the content ?? The easiest way is to download from XDA the generic global rom, it's the same -- with no bug
Click to expand...
Click to collapse
Huh? The generic ROM is compiled. The one we are talking about here is source-code. I thought you should know since you started this topic on how to setup a build environment. Im not intirely sure what the download from from SE is but it looks like the source-code from all the changes and additions SE made to the bare system. So there's the kernel source and some other stuff that I don't know the purpose of.
Sent from my SNES using Mario Paint
LouNGeRR said:
Huh? The generic ROM is compiled. The one we are talking about here is source-code. I thought you should know since you started this topic on how to setup a build environment. Im not intirely sure what the download from from SE is but it looks like the source-code from all the changes and additions SE made to the bare system. So there's the kernel source and some other stuff that I don't know the purpose of.
Sent from my SNES using Mario Paint
Click to expand...
Click to collapse
A compiled rom is not a problem
I was asking what was the content within the rom, and as you said - i supposed too - it is the original + all SE garbage.
Very interesting to get some apps back on AOSP (some like the *Scape, i do like predictive input from SE, gains a lot of time)
To answer then, the SE kit should contain everything of what SE adds : RachaelUI, all their apps (the *Scape), modules (keyboard, apis...), etc etc and all files to link these components to the kernel. And make our phones as fast as a monster truck. Not as fast as AOSP (Formula 1 !!!!!)
Don't forget the most important part, the package contains the SE kernel.
Sent from my SNES using Mario Paint
After using, struggling more like with Ubuntu and VMware, the main issue being I couldn't figure out getting VMware tools running so copy and pasting was hit and miss, I tried the Cygwin method instead which works much better for me on Windows 7 Ultimate x64.
XperiaX10iUser said:
After using, struggling more like with Ubuntu and VMware, the main issue being I couldn't figure out getting VMware tools running so copy and pasting was hit and miss, I tried the Cygwin method instead which works much better for me on Windows 7 Ultimate x64.
Click to expand...
Click to collapse
VMWare is much more difficult to run than VirtualBox. But course you can try and compile Android from Windows
But I definitely can't tell you if the kitchen method will work for XPERIA.
Perceval from Hyrule said:
VMWare is much more difficult to run than VirtualBox. But course you can try and compile Android from Windows
Click to expand...
Click to collapse
I've put VB on too, but thought I'd try the Cygwin method, which as I've said works for me, and is better imo, at least for what I need.
Perceval from Hyrule said:
But I definitely can't tell you if the kitchen method will work for XPERIA.
Click to expand...
Click to collapse
I can, and it does.
XperiaX10iUser said:
I've put VB on too, but thought I'd try the Cygwin method, which as I've said works for me, and is better imo, at least for what I need.
I can, and it does.
Click to expand...
Click to collapse
Thanks for info then
Hey guys, did someone do the same install as me ? (Windows 7 x64 host // Ubuntu 10.10 x64 guest).
I've never been able to make USB to work, kinda weird... Because when you compile Android, you'd like to send it to your phone *warning !*
Perceval from Hyrule said:
Hey guys, did someone do the same install as me ? (Windows 7 x64 host // Ubuntu 10.10 x64 guest).
I've never been able to make USB to work, kinda weird... Because when you compile Android, you'd like to send it to your phone *warning !*
Click to expand...
Click to collapse
That's why I went the Cygwin route, much less hassle imo.
XperiaX10iUser said:
That's why I went the Cygwin route, much less hassle imo.
Click to expand...
Click to collapse
I would say it depends. Linux environment is much cooler to work with source files (no boring "NOOO Windows can't find how to open this weird non-Windows file. What to do ? 1.Delete 2.Crash Windows 3.Phone Ballmer to make a tender offer)
Is compiling long with Cyg ? From AOSP, it takes me up to 3 hours with my (well RAM-ed, well CPU-ed) Virtual Machine.
Run Ubuntu 10.10 on Nexus One
--------------------------------
Background:
In June 2010, XDA zedomax got Ubuntu 9.04 running on Nexus One, tutorial is available at this thread:
http://forum.xda-developers.com/showthread.php?t=718952
I continued studying the tutorial and worked out a way to make Ubuntu 9.04 running better, smoother and cause less error, here's my post:
http://forum.xda-developers.com/showthread.php?t=815532
Recently HTC_Linux team has released version 0.3 of their Ubuntu image, compare to the original guide provided by zedomax, the v0.3 release is based on the latest Ubuntu 10.10. So I thought about making this tutorial to guide you to run Ubuntu 10.10 on your Nexus One.
--------------------------------
What benefits will you get from running Ubuntu 10.10 on Nexus One (at least):
1. Fully functional Linux terminal, with all standard Linux command line utilities
2. Fully functional desktop browser Firefox 3.6.13
3. Ability to compile and run native Linux applications
4. Bunch of graphical Internet and utility applications as shown in the screenshots
--------------------------------
Credit:
Thanks to the great XDA-developers community.
Thanks to Zedomax for providing the original tutorial of running Ubuntu on Nexus One.
Thanks to HTC_Linux team for creating the optimised Ubuntu 10.10 image file.
--------------------------------
Now the tutorial starts.
Preparation:
1. A micro SD card at least 4GB in capacity, 8GB/16GB is recommended
2. (Optional) If you're using Froyo App2SD, move all your applications which are on SD card back to Internal Storage, or you may also uninstall all applications that are on SD card. If you fail to do so, you won't be able to enter Ubuntu. However I've discovered a way that you won't need to move or uninstall apps on SD card, will discuss later.
3. Basic Linux shell knowledge
Then:
1. Get Ubuntu 10.10 from this post (file name: hd2-ubuntu_0.3.zip): http://forum.xda-developers.com/showthread.php?t=889433
2. Download attached scripts.zip
3. On your computer, make a directory on a partition that has more than 3.5GB available space, name the directory “ubuntu” (case-sensitive!)
4. Extract three scripts (b, e, u) from scripts.zip to the directory ubuntu
5. Once you finish download hd2-ubuntu_0.3.zip, extract linux/rootfs.ext2 to the directory ubuntu
6. In your ubuntu directory, rename rootfs.ext2 into ubuntu.img (case-sensitive!)
7. Now verify that you have the following files in your computer's ubuntu directory: b, e, u, ubuntu.img
8. Copy the whole ubuntu directory onto your SD card, put the SD card back to your phone
9. Power up your Nexus One
Now we have some script work:
1. Run a terminal application from your phone (e.g. Android Terminal, Better Terminal Emulator)
2. type “cd /sdcard/ubuntu” (enter)
3. type “sh u” (enter)
4. If you see “Type 'b' to boot Ubuntu”, then you're almost there!
5. Type “b” (enter)
6. If you see “[email protected]:/#” (like shown in screenshot) Congratulations! Now you're running Ubuntu 10.10 on your Nexus One!
Whenever you want to enter Ubuntu again, simply type “b” (enter) in your Android Terminal.
To properly exit from Ubuntu, you must type “exit” from Ubuntu terminal.
If your Android terminal application gets killed by Android system (i.e. you lost Ubuntu terminal), you need to go back to Android terminal, type “e” (enter), that will properly unmount Ubuntu.
Very often that you can get “loop device busy” error when exiting from Ubuntu, in that case, type “e” (enter) multiple times (it's harmless to run “e” script multiple times, don't worry). If still you get “loop device busy” error, don't worry, ignore it then.
--------------------------------
(Optional) If you would prefer working with GUI, now let's do some extra script work:
1. Install “android-vnc-viewer” from Market (freeware)
2. Enter Ubuntu terminal
3. Make sure that you have network connection (Wi-fi recommended)
4. type “apt-get update” (enter), and wait till it finishes
5. type “apt-get install tightvncserver” (enter) and answer “y” to the question
6. After installed tightvncserver, type “cd /bin” (enter)
7. Type the following commands (all are case-sensitive!):
“cat > x” (enter)
“rm -r -f /tmp” (enter)
“mkdir /tmp” (enter)
“chmod 777 /tmp” (enter)
“export USER=root” (enter)
“export XKL_XMODMAP_DISABLE=1” (enter)
“vncserver -geometry 1024x800” (enter)
(enter)
(press and hold trackball and click D on keyboard)
“chmod 777 x” (enter)
8. The above procedure makes a script named “x”, whenever you want to start GUI, you need to type “x” (enter).
Notice that the first time (only the first time) you run “x” script you'll be prompt to enter a password for VNC connection, then you'll be asked whether to create a “view-only” password, since it is not necessary, answer “n” to the question.
9. Start “android-vnc-viewer”, create a new connection with the following settings:
Nickname: (anything you like to identify the connection)
Password: the VNC connection password that you created when ran the “x”script
Address: localhost
Port: 5901
Color format: 24-bit color (4 bpp)
Click “Connect” button, and in about a minute, you'll see your Ubuntu 10.10 desktop!
10. We still need to create one final script called “s”, now go back to your Ubuntu terminal and type:
“cd /bin” (enter)
“cat > s” (enter)
“export USER=root” (enter)
“vncserver -kill :1” (enter)
“vncserver -kill :2” (enter)
“sudo reboot” (enter)
“sudo halt” (enter)
(enter)
(press and hold trackball and click “D” on keyboard)
“chmod 777 s” (enter)
11. If you have GUI running, you * MUST * type “s” (enter) to stop VNC server before you exit from Ubuntu terminal!
In case that your Android kills your Android Terminal application and you still have VNC server running, do the following steps:
a. Start Android Terminal
b. type “b” (enter) to bring back Ubuntu terminal
c. type “s” (enter) to stop VNC server
d. type “exit” (enter) to exit from Ubuntu terminal
Fail to do so you will have problem with VNC connection next time you use it.
--------------------------------
What are not working in Ubuntu:
1. Sound
2. Some applications may not run (I guess, due to Android memory management mechanism)
--------------------------------
A little trick to access SD card from your Ubuntu:
1. Install “SwiFTP” from Market (freeware)
2. Set up FTP server using SwiFTP
3. In Ubuntu, “Places → Connect to Server” then:
Service type: FTP (with login)
Server: localhost
Port: (port number specified in SwiFTP, default is 2121)
Folder: /
User Name: (user name specified in SwiFTP)
Then press “Connect” and enter your password specified in SwiFTP. Now feel free to access your phone's file system!
--------------------------------
How to bring up Ubuntu if you have applications installed on SD card using Froyo App2SD:
1. Make sure that your Android Terminal application is installed in Internal Storage
2. Put a shortcut to Android Terminal application on your home screen
3. Make sure you have got ubuntu directory and all its contents on SD card
4. Reboot your phone (stay sharp, these following steps require perfect timing!)
5. Once you enter lock screen, Immediately unlock it.
6. Enter Android Terminal and type “b” as quick as possible, do not press Enter yet!
7. Pay close attention to your notification bar, as soon as the “SD: Checking for errors” notification disappears (the little SD icon disappears), Immediately press Enter.
8. Now you should be in Ubuntu terminal, wait 1-2 minutes before you do anything else.
9. After 1-2 minutes, you may do whatever you want.
With some applications installed on SD card, you must do the procedure above to bring up Ubuntu terminal each time you reboot your phone.
--------------------------------
That's it! Thank you for reading this tutorial. Please feel free to make any comment or ask any question!
Awesome. I'll be trying this out as soon as I get a larger SD card. It would be great if you could upload a .zip with all of the scripts, downloads, etc. already placed in one folder; that would make it a lot easier.
Thx U for this Tutorial....it was really helpful...Can u fix the adobe flash thing...i know that sound will not work but just wondering if it can be installed.
yumcax said:
Awesome. I'll be trying this out as soon as I get a larger SD card. It would be great if you could upload a .zip with all of the scripts, downloads, etc. already placed in one folder; that would make it a lot easier.
Click to expand...
Click to collapse
Actually I thought about the same but here my uploading speed is 15kb/s maximum, so I'm not sure if I'm gonna upload a 600mb file...
reubenjack said:
Thx U for this Tutorial....it was really helpful...Can u fix the adobe flash thing...i know that sound will not work but just wondering if it can be installed.
Click to expand...
Click to collapse
Adobe Flash has no support for ARM architecture.. sorry, there's no way to install Adobe Flash plugin for Firefox on Ubuntu ARM.
OMG Im abt to die. Transfering the folder to my sd card takes 20 min. I really nid to get a better memory card (higher speed). SIGH..
Works nice on my N1 running MIUI 12.24..
BTW I have a question, if I wipe my phone(data,cache).. Would I need to perform any steps then?
Keshav_CoolDude said:
Works nice on my N1 running MIUI 12.24..
BTW I have a question, if I wipe my phone(data,cache).. Would I need to perform any steps then?
Click to expand...
Click to collapse
If you re-installed a rom (i.e. /system partition gets rewritten)
You'll need to execute the following commands on Android Terminal:
cd /sdcard/ubuntu
sh u
then type "b" to enter Ubuntu terminal
Happy New Year!
Hey,
In the OP you mention that some apps will not run because of the memory management? Is there a size threshold that this is start to be seen at or is it totally random on which things run/don't?
Thanks
houzuoguo said:
If you re-installed a rom (i.e. /system partition gets rewritten)
You'll need to execute the following commands on Android Terminal:
cd /sdcard/ubuntu
sh u
then type "b" to enter Ubuntu terminal
Happy New Year!
Click to expand...
Click to collapse
Okay.. Thanks for the guide..
Happy New Year..
Chopes said:
Hey,
In the OP you mention that some apps will not run because of the memory management? Is there a size threshold that this is start to be seen at or is it totally random on which things run/don't?
Thanks
Click to expand...
Click to collapse
I'm not very familiar with Linux kernel so sorry I can't give an accurate explanation
According to my observation, many applications in the Ubuntu 10.10 can successfully start (program title appears in task bar) but immediately they turn off by themselves.
And it seems to me that all those applications share a same characteristic: they're relatively bigger than others. For example, Terminal runs, Dictionary runs, Firefox runs, but Ubuntu Software Centre won't run.
So my guess is ... Android system would not allocate too much memory for an application in Ubuntu, thus they get killed before they could start.
I'll give this a one thumb up, because I got it working, got to play around a bit... it looks really nice... but I did a reboot of my phone after shutting it down properly, and now everytime I try to launch ubuntu again, I get a bunch of errors.
I've tried just about everything.... restoring to my nand backup I did before trying this, deleting the files off the sdcard and on my system relating to this, tried to set everything back up... but I still get errors and I can't get past them, even with trying "e" in the term.
FWIW, I'm on CM 6.1.1 and I do use DTa2sd with plenty of space left on all partitions. Here's a pastebin of my errors : http://pastebin.com/adCQ62iF
tehgeekguy said:
I'll give this a one thumb up, because I got it working, got to play around a bit... it looks really nice... but I did a reboot of my phone after shutting it down properly, and now everytime I try to launch ubuntu again, I get a bunch of errors.
I've tried just about everything.... restoring to my nand backup I did before trying this, deleting the files off the sdcard and on my system relating to this, tried to set everything back up... but I still get errors and I can't get past them, even with trying "e" in the term.
FWIW, I'm on CM 6.1.1 and I do use DTa2sd with plenty of space left on all partitions. Here's a pastebin of my errors : http://pastebin.com/adCQ62iF
Click to expand...
Click to collapse
Happy New Year!
Could you please go to Settings-> Application Settings-> Manage Applications-> on SD card and confirm there is no application on SD card?
Also please make sure you execute "b" after "Checking for Errors" notification disappears.
Running this distro does that mean i can use firesheep on my n1?
Awesome! What kind of battery life are you seeing using Ubuntu? Any apps in particular you've enjoyed having on your N1?
rossonza said:
Running this distro does that mean i can use firesheep on my n1?
Click to expand...
Click to collapse
According to my study Firesheep would require WinPcap to work, WinPcap is only available for Windows so unfortunately you can't use it.
Deathwish238 said:
Awesome! What kind of battery life are you seeing using Ubuntu? Any apps in particular you've enjoyed having on your N1?
Click to expand...
Click to collapse
I notice battery drains 2-3 mAh more when Ubuntu is idle, when actually using Ubuntu I notice 30-40mAh higher current draw. So actually it's not much
hey thanx houzuoguo,
working great on my n1....!!
is there any solution for the sound to run...??
I cant seem to get any of the "cat >" letters to work, it just hangs in the terminal.
houzuoguo said:
According to my study Firesheep would require WinPcap to work, WinPcap is only available for Windows so unfortunately you can't use it.
I notice battery drains 2-3 mAh more when Ubuntu is idle, when actually using Ubuntu I notice 30-40mAh higher current draw. So actually it's not much
Click to expand...
Click to collapse
Firesheep works in Ubuntu, you just have to compile it yourself.
1) Download the required dependencies:
Code:
sudo apt-get install autoconf libtool libpcap-dev libboost-all-dev libhal-dev xulrunner-1.9.2-dev
2) Install git:
Code:
sudo apt-get install git
3) Download the Firesheep source:
Code:
git clone https://github.com/codebutler/firesheep.git
4) Change to the Firesheep directory:
Code:
cd firesheep
5) Initialize it:
Code:
git submodule update --init
6) Compile it:
Code:
./autogen.sh && make
7) You'll find the file in the build directory.
hotweiss said:
Firesheep works in Ubuntu, you just have to compile it yourself.
1) Download the required dependencies:
Code:
sudo apt-get install autoconf libtool libpcap-dev libboost-all-dev libhal-dev xulrunner-1.9.2-dev
2) Install git:
Code:
sudo apt-get install git
3) Download the Firesheep source:
Code:
git clone https://github.com/codebutler/firesheep.git
4) Change to the Firesheep directory:
Code:
cd firesheep
5) Initialize it:
Code:
git submodule update --init
6) Compile it:
Code:
./autogen.sh && make
7) You'll find the file in the build directory.
Click to expand...
Click to collapse
Not to threadjack or anything of the sort but:
Does the above method work on getting firesheep installed on a n1 running ubuntu or is this just the way to install it assuming your running on normal hardware?
Second question, what is the resulting file?
Thanks,
Which terminal application are you using, and did you type the "cat >" on screen keyboard or copy&paste?
Updates Announcement here
------------------------------------------------------------------------------
Updates
Refer to oF2pks post regarding latest UEFI on BBQLinux
------------------------------------------------------------------------------
I am very surprise that BBQLinux has almost no reviews or publicity at all & a quick google search returns only a maximum of 10 pages only...
After all it is a Linux Distro specifically made for Android Development... It is maintained by Senior Recognized Developer codeworkx mentioned by himself... :laugh:
It has everything you ever needed & you should have started development long ago & not cracking your head to setting up the Build Environment, downloading this & that dependencies packages...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Intro from wiki
BBQLinux is a user-friendly Linux distribution made for Android developers and everyone who prefers a ready-to-use system. It has everything on board to build AOSP or AOSP-based Distributions like OmniROM or CyanogenMod. The default desktop environment is MATE. It is using vanilla Arch repos, the AUR and a BBQLinux specific repo. BBQLinux can be installed by booting the Live DVD and using the graphical Installer called BBQLinux Installer.
Homepage: http://www.bbqlinux.org
Screenshots: http://bbqlinux.org/screenshots
Google+: https://plus.google.com/u/0/communities/106642342159578225975
IRC: #bbqlinux on freenode
Added on Mar 27, 2014 - Miscellaneous Tips
Terminal Shortcut Key How-to
System -> Preferences -> Keyboard Shortcuts
Vbox Shared Folder
Drag&Drop works from Win Host to BBQLinux but not the other way round. To enable Win Host to access BBQLinux folder, for this Eg: create a new folder name BBQLinux at Win Host & put a check mark at Auto-mount. At BBQLinux Terminal,
Code:
[COLOR=blue]mkdir -p ~/BBQLinux
sudo mount -t vboxsf BBQLinux ~/BBQLinux[/COLOR]
After that, both can access the folder BBQLinux. At BBQLinux, there will be a new BBQLinux folder at your [Home]
To enable Shared Folder to work after reboot, use below command at Terminal & pluma to check. Change it accordingly to your setup if you use other folder name.
Code:
[COLOR=blue]echo BBQLinux ~/BBQLinux vboxsf uid=1000,gid=1000 0 0 [B]>>[/B] /etc/fstab
pluma /etc/fstab[/COLOR]
At my fstab it is BBQLinux /home/yuweng/BBQLinux vboxsf uid=1000,gid=1000 0 0
WARNING : Take note of the double greater-than sign >> a single > will over write everything at fstab & it won't boot after that so make sure there is no typo mistake ! And remember to put a check mark at Auto-mount or it will not boot !
The new Shared Folder BBQLinux can be access from the Desktop after a reboot.
Source
Installation How-to
There are already tons of guides on the web, more or less the same so refer to the below...
Virtualbox
Dual-Boot & Boot Menu
Native Boot
USB bootable how-to tips by Master Shifu himself... :good:
Found the one & only installation walk-thru in Russian !
i guess only the Russian appreciates such a master piece... Google Translated version here...
Still couldn't boot up BBQLinux then head over here tons of infos so make sure you have gone thru all that first & if still you couldn't figured it out then ask Master Shifu codeworkx AKA Daniel Hillenbrand or try asking here . . . :good:
Added on Apr 11, 2014
Confirmed BBQLinux can successfully built cm & omni . . .
Successfully built i9500 on BBQLinux & it tooks more than 7 hours on top of the initial 7 hours for syncing cm11 FULL source...
Commands to build on my PC...
Code:
[U]First part[/U]
mkdir -p ~/cm11
cd ~/cm11
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync -f -j4
cd ~/cm11/vendor/cm
./get-prebuilts
cd ~/cm11
source build/envsetup.sh
lunch
To select [COLOR=Blue]cm_i9500-userdebug[/COLOR] by typing its listed number-> Eg: [B][COLOR=Blue]50[/COLOR][/B] -> Enter ->
Wait & it'll resume syncing but there will be some errors & it'll stop
[U]2nd Part[/U]
export USE_CCACHE=1
prebuilts/misc/linux-x86/ccache/ccache -M 25G
brunch i9500
Source
Built successfully on Omni too...
Commands to build on my PC...
Code:
[U]First part[/U]
mkdir -p ~/omni
cd ~/omni
repo init -u https://github.com/omnirom/android.git -b android-4.4
repo sync -f -j4
Then follow remaining steps here...
Miscellaneous tips
What is ccache ?
Use below command to add it to .bashrc then you don't need to type it on every build & geany to check
WARNING : Take note of the double greater-than sign >> a single > will over write everything !
Code:
echo -e "\nexport USE_CCACHE=1" >> ~/.bashrc
geany ~/.bashrc
Source
Added on Apr 22, 2014
Philz Touch CWM Advanced Edition
Updates
Refer to here for more info . . .
Added on Sept 07, 2014
How to update your BBQLinux Distro
i've bad experience with Windows Update at work so i never did try updating BBQLinux until now Thanks to Santhosh M for sharing his experience . . .
Just follow the commands & updating works like a charm !
You can find all updated packages downloaded to /var/cache/pacman/pkg so make a backup & in case of OS corruption then you can use it, no need to download all over again . . .
Added on Oct 04, 2014
Native UEFI booting BBQLinux
What is UEFI. What is the benefit ? Got mine booted to login screen in just 9 seconds & i'm not even using SSD !
Been using Vbox for quite awhile now, did install Native-Boot but only now free to look into UEFI booting for my mobo & found out all those steps are not needed for BBQLinux except modified UEFI Shell v2 binary ( scroll further down & you'll see it )
For reference only, BBQLinux now support auto UEFI installation.
Steps
Download Rufus or on Linux & create a UEFI bootable USB drive from BBQLinux iso
Boot to Bios or press F8 for Boot Menu on Asus mobo & select the BBQLinux UEFI USB drive to boot to install BBQLinux
Assign 100MB for /boot/efi, swap, root, home as per your preferences. Upon finishing, installer will tell you EFI variables are not supported, just ignore it & reboot.
Boot the BBQLinux Installer again, use caja to mount the 100Mb partition, download, extract UEFI Shell v2 to the root of this partition & rename it to shell.efi
Reboot to Bios, pull out BBQLinux Installer USB drive, boot to launch UEFI shell & follow below command.
Code:
bcfg add 0 fs0:\EFI\BBQLinux\grubx64.efi "BBQLinux"
exit
Navigate to Bios Boot section, select BBQLinux, boot to this entry and enjoy.
Accessing EFI Shell on most mobo more or less the same so hunt for it if yours is not a Asus mobo . . .
ScreenShot
View attachment 2958722
Updates
Latest bbqlinux-2014.10.03-x86_64
Complete detail Walk-Through for setting up UEFI BBQLinux with photos
They say A picture is worth a thousand words hopefully newbies will be able to DIY after going thru all these. This Walk-Through setup details my Build Box that uses Asus mobo however it should be more or less similar for most mobo available on the market.
After you have booted up the UEFI BBQLinux Installer USB drive, you'll be greeted with the above. Press N
Press Enter
This screen will ask you to enroll the BBQLinux Installer USB drive loader.efi
This error details that you need to enroll \bbqlinux\boot\x86_64\vmlinuz too
Repeat the above process, look for vmlinuz & enroll it.
After this you should be able to boot the UEFI BBQLinux Installer USB drive
Now that you have finally booted up the UEFI BBQLinux Installer USB drive, you'll be greeted with above Welcome Screen, you can either choose Install BBQLinux or Try BBQLinux
After you choose Install BBQLinux, above notification will pop-up.
Go-thru each of the simple BBQLinux Installer menu & you'll get it installed. Generic calamares installation video. Below is obsolete info for reference, BBQLinux now support auto UEFI installation.
The newly installed BBQLinux won't boot b'cos you need additional steps to setup UEFI
Reboot BBQLinux Installer again & follow command above.
Code:
sudo efibootmgr -c -l "EFI\BBQLinux\grubx64.efi" -L "BBQLinux" [COLOR=red]<- This command assume you only have one Hard Disk Drive[/COLOR]
sudo efibootmgr [COLOR=Red]<- This command will list out the boot order[/COLOR]
Your BBQLinux HDD has the UEFI label & now you shall be able to boot up UEFI BBQLinux
My BBQLinux Build Box
Misc Tips
Updates
As mentioned, UEFI BBQLinux Native-Boot on normal HDD on SATA 6 boots up & shutdown faster than Win8.1(non UEFI) on SSD SATA 6, try it yourself then you'll know !
As you've seen all other guides elsewhere, same advice, familiarize yourself with UEFI on Virtualbox first then only try it on real HDD. System -> Put a check mark at Enable EFI (special OSes only).
If you're trying it on actual HDD then better to disconnect other HDD as you wouldn't want bad things to happen in case of a single mistake.
--------------------------------------
You can skip a few more hassle if you don't use UEFI Windows. More info here, here & here
If you already have other UEFI linux distro, you can use efibootmgr to setup two different UEFI boot label. Below example details two BBQLinux installation on two different HDD. Change accordingly to you Distro.
Code:
sudo efibootmgr -c -d /dev/sd[SIZE=4][COLOR=blue]d[/COLOR][/SIZE] -p 1 -L "[COLOR=blue]BBQLinux[/COLOR]" -l "EFI\[COLOR=blue]BBQLinux[/COLOR]\grubx64.efi"
sudo efibootmgr -c -d /dev/sd[SIZE=4][COLOR=blue]c[/COLOR][/SIZE] -p 1 -L "[COLOR=Blue]BBQLinux 1[/COLOR]" -l "EFI\[COLOR=blue]BBQLinux[/COLOR]\grubx64.efi"
sudo efibootmgr
Now both the UEFI BBQLinux & BBQLinux 1 is at the Boot Menu
Added on Mar 30, 2015
Jenkins on BBQLinux
Added on Apr 13, 2015
Tried fresh bbqlinux-2015.03.22-x86_64.iso UEFI installation on my OCZ SSD & it auto-detect & auto added UEFI boot menu by itself so just let BBQLinux installer do its job instead of manual partitioning . . . Refer to attachment -> View attachment 3236670
Time taken for building from source is also cut by half when using SSD . . .
Added on May 05, 2015
BBQLinux on non-Android Development laptop
Installed UEFI BBQLinux on my non-android-developer friend's Samsung Laptop with Celeron Processor & he is super happy that it boots & shutdown super lightning fast compared to the bundle OS . . . Below are the packages that i had to remove since sudo pacman -Syu will update it as well
Code:
sudo pacman -R [URL="http://en.wikipedia.org/wiki/Android_Studio"]android-studio[/URL]
sudo pacman -R android-support
sudo pacman -R [URL="http://en.wikipedia.org/wiki/Android_software_development"]android-sdk[/URL]
sudo pacman -R monodevelop-debugger-gdb
sudo pacman -R [URL="http://en.wikipedia.org/wiki/MonoDevelop"]monodevelop[/URL]
sudo pacman -R [URL="http://en.wikipedia.org/wiki/Meld_(software)"]meld[/URL]
sudo pacman -R [URL="http://forum.xda-developers.com/showthread.php?t=755265"]heimdall[/URL]
sudo pacman -R [URL="http://en.wikipedia.org/wiki/FileZilla"]filezilla[/URL]
sudo pacman -R [URL="http://wiki.inkscape.org/wiki/index.php/Inkscape"]inkscape[/URL]
sudo pacman -R gimp-dbp
sudo pacman -R gimp-plugin-fblur
sudo pacman -R gimp-plugin-gmic
sudo pacman -R gimp-plugin-lqr
sudo pacman -R gimp-plugin-mathmap
sudo pacman -R gimp-plugin-wavelet-decompose
sudo pacman -R gimp-plugin-wavelet-denoise
sudo pacman -R gimp-refocus
sudo pacman -R [URL="http://en.wikipedia.org/wiki/GIMP"]gimp[/URL]
sudo pacman -R [URL="http://en.wikipedia.org/wiki/LibreOffice"]libreoffice[/URL]-fresh
Since he is not using it for android development & he is more familiar with openoffice, i install it for him & told him to help himself with whatever apps that he may needs . . . :good:
Code:
yaourt -S openoffice
Updates
Tried building recovery & it says not enough memory as it comes with only 2GB Ram, tried with swap file & that solved the problem ! In spite of removing quite a few apps, there are still alot of Android binary stuff in it !
Swap my Desktop PC SSD for testing purpose & expected to re-installing everything but it boots up without doing anything !
This time only allocated 256MB swap & that too builds without problems, Conclusion : You don't need 16GB RAM for building from source as advice by many other guides, just invest in a SSD & use swapfile ! BBQLinux OS on a 60GB SSD should be enough for building ROMs too, either get an external HDD for data storage or use back the existing laptop HDD as an external HDD.
Completed building recovery on Celeron laptop, it only use up 67.8% of the newly allocated 256MB swap.
Only now realize that my Desktop 16GB RAM was hardly used, wasted my money upgrading RAM, same amount of money should've got me a bigger SSD !
Updates
How to confirmed that you have really boot into UEFI OS
Code:
[COLOR="Blue"]bootctl status[/COLOR]
System:
Machine ID: be56bf48b7444091ba1c651c91e2c45f
Boot ID: 68d69ecf4cb9470b88754b968f4e6b22
Secure Boot: disabled
Setup Mode: setup
Selected Firmware Entry:
Title: UEFI OS
Partition: /dev/disk/by-partuuid/bb6adf13-4b2b-4745-9b22-ec0ef5bdf56a
File: └─[COLOR="blue"]EFI/BBQLinux/grubx64.efi[/COLOR]
Source
Added on May 23, 2015
i've created a barebone BBQLinux xfce4 with BBQLinux Media Generator for installation on my friends PCs & laptops, full credits to Master Shifu codeworkx
Removed all development stuff so now its about 800MB with installed size at just 4.2GB ! Though you'll have to install apps that you want with a simple sudo pacman -S 'name of apps'
So go ahead & install it to your old PCs/ Laptops, family & friends PCs & Laptops, let them experience the goodies of BBQLinux & they'll be amaze of how well it performs, super fast, like brand new !
Will work on any PCs/ Laptops after the year 2006.(64bit CPU either AMD or Intel)
Added on May 27, 2015
Got my old Canon MP140 scanner working as simple as Plug & Play !
Code:
sudo pacman -S xsane gocr
Source
Added on Oct 09, 2015
Got bored with mate desktop then switch to xfce4 then to cinnamon easily without reinstalling everything...
Code:
sudo [URL="https://wiki.archlinux.org/index.php/Pacman#Upgrading_packages"]pacman -Syu[/URL]
sudo pacman -S bbqlinux-desktop-xfce4
sudo pacman -[STRIKE]Rsc[/STRIKE] bbqlinux-desktop-mate
[URL="https://wiki.archlinux.org/index.php/Allow_users_to_shutdown"]systemctl reboot[/URL]
Code:
sudo pacman -S bbqlinux-desktop-cinnamon
sudo pacman -[STRIKE]Rsc[/STRIKE] bbqlinux-desktop-xfce4
systemctl reboot
Enjoy the new desktop environment & i believe the same can be apply to all the other desktop too. Updates - 13-Oct-2015 Tested & confirmed all five bbqlinux desktop works using above techniques without re-installation...
Updates => Just did a new installation for a friend's laptop & it doesn't work, use pacman -Rs & it worked, however on my BBQLinux Desktop( Month of May iso ), pacman -Rsc works...
Updates 29-Feb-2016
Need to search a certain string on the source code but its like taking forever then use... :good:
Code:
sudo pacman -S [URL="https://github.com/ggreer/the_silver_searcher"]the_silver_searcher[/URL]
The code
How Linux is Built
Were you able to get OmniRom to work for your unsupported device? If so can you detail step by step how you added your device files?
As mentioned, cm & Omni doesn't boot on MTK as most MTK vendors doesn't include kernel source...
However, i did check out with Master Shifu Dee_Troy when i hang out here & he told me there is no mkvendor.sh on Omni source & ask me to refer to one & only MTK device tree here & it did built TWRP 2.7 on 4.4 branch...
So i suggest the same that you do some research, look at various device tree example here, use the one closest siblings to your device, manually edit all those files & i'm sure it'll built or try hang out here or here... :good:
Thanks for this usefull thread my Friend
Just tested on Virtual Machine (ubuntu). Compile philz touch 6 using cm-11 source for qualcomm device works very fine .
Like you said just getting android source and device tree, and the build process could be launched!!!
Nice one. ....
Greetz
Gesendet von meinem ME173X mit Tapatalk
Thanks for this @yuweng.:good:
Awesome! Thanks for share!
There are a few tools I had to install before I could compile Kit Kat. I thought I would share because Arch is so differrent than Ubuntu or Linux Mint so it was a pain to install these. Other than that I really like this distro. Nice UI
Hmm, i never had to install anything, may be its device specific, idk . . .
But Hey, you should share the how-to here, everyone know its pain in the ass to install arch packages . . . :laugh:
Never knew this thread got featured at the XDA Portal thanks to WILL VERDUZCO & JIMMY MCGEE . . . :highfive:
Updates : Totally forgotten to mentioned Jordan Keyes doing the BBQLinux coverage at XDA TV . . .
Since this question was asked at the portal for app development, BBQLinux includes Android SDK, Android Studio, Geany & Meld.
Someone even mentioned that he has to install JDK8 then only it'll work for his app development but i can't find that link, either it was the keyword BBQLinux, Archlinux, JDK8 or something else i can't recall . . .
Yeah, I've never heard of having to use Java 8 before. But Java6 is version 1.6. This is not device specific but it's common with all ROMs. See here: https://github.com/Octo-Kat/platfor...8a96053cc2fe520fdc136594878/core/main.mk#L163
So if you want you can check some of the other main stream ROMs like AOKP, CM, etc and confirm this to be true. Also the Compression tool iz4c is a must otherwise the build errors out when it starts compiling the kernel.
yuweng said:
But Hey, you should share the how-to here, everyone know its pain in the ass to install arch packages . . . :laugh:
/QUOTE]
I've never heard about any 'pain' with Archlinux's packages in the last 3 years! And Archlinux is my main system since then.
From LG G Pad 8.3 with the original Kitkat by LG
Click to expand...
Click to collapse
speedyx2000 said:
yuweng said:
But Hey, you should share the how-to here, everyone know its pain in the ass to install arch packages . . . :laugh:
/QUOTE]
I've never heard about any 'pain' with Archlinux's packages in the last 3 years! And Archlinux is my main system since then.
From LG G Pad 8.3 with the original Kitkat by LG
Click to expand...
Click to collapse
Certain packages aren't available in aur. You can convert them but that's more advanced.
Click to expand...
Click to collapse
Updated the BBQLINUX to may 1st version
but cant get the welcome screen
The lightdm.conf in the HDD has already lightdm-gtk-greeter
But still the same error pops up
Failed to Start Light Display Manager
The correct command is sudo geany etc/lightdm/lightdm.conf (without the slash) . . .
GUI method is actually much simpler . . .
Double-click at bbqlinux's Home -> 34GB HDD(your HDD) -> password bbqlinux
Applications -> System Tools -> Mate Terminal -> sudo caja -> password bbqlinux
File System -> run -> media -> bbqlinux -> HDD UUID -> etc -> lightdm -> lightdm.conf
Change greeter-session=lightdm-bbqlinux-greeter to greeter-session=lightdm-gtk-greeter
Yeah !! GUI method worked ...Thanks to @yuweng
I've this.
Inviato dal mio Galaxy Nexus con Tapatalk 2
It seems that your problem is something to do with the DVD/ USB disk label, link mentioned at the OP too . . .
But the corrupted low memory thingy is a whole totally different problem, i think . . .
Install, Setup and Update problems...
Hay, great job on making BBQLinux!
I have been having problems with the last two iso's you have done however,
My system is a MacBook Air 2012 (i5, 8GB RAM, 60GB SSD) and I am installing BBQLinux on to a USB3 or ThunderBolt HDD. Both of the iso's tried needed some monkeying with to get them to boot on a Mac - messing about with "/boot/efi" to make it boot...
The first one - bbqlinux-2014.03.16-x86_64.iso, installs great, boots with no problems (after monkeying) has a working desktop and tools but will not update! Every time i try to update, either using packman or the GUI it errors. GUI say "Unknown Error" and pacman gives errors about "invalid or corrupted package (PGP signature)" or "error: failed to commit transaction (conflicting files) terminus-font: /etc/fonts/conf.d/75-yes-terminus.conf exists in filesystem" - have tried many fixes but can't get past those errors!
The second one - bbqlinux-2014.05.01-x86_64.iso, installs great, boots with no problem (after monkeying) but the desktop does not work - just keeps opening caja at the bottom of the screen, hundreds and thousands of them!!!
Help please, thank you
On my Vbox, upon startup before it could finished loading everything, i double-click the Home icon at Desktop then four or five of them will pop-up after that but not hundreds and thousands of them . . . :laugh:
i have experience that on the Mar version but not May . . . Hmm, did you try other VMs such as parallels or vmware that could at least narrow down the problem, idk . . .
Hmm, may be you should report it directly to Master Shifu here as his XDA profile shows that he hasn't post anything since Jan 2014 . . .
May be Master Shifu @codeworkx is not even aware of this thread is here too . . . :laugh:
Wassup?
Who t f is Master Shifu?
Sent from my Nexus 5 using XDA Free mobile app
Master Shifu is a Charakter in the movie Kung Fu Panda
Gesendet von meinem Nexus 4 mit Tapatalk
Remix OS installations on hard disks or virtual machines using the "INSTALL=1" option are using the whole ext4 partition given to them, but they need special methods for updates. An OTA update for a Remix OS installation on hard disk or a virtual machine (see "How to install Remix OS in VirtualBox (or to harddisk)") will not work showing the error message "Update failed". Obviously the OTA update works for USB flash drive installations only.
Problem Solution
An updated USB flash drive can be used to perform new (updated) installations and it can be used for updating existing hard disk or Virtualbox installations preserving the data directory (i.e. all changes the user has made before).
The tools you'll need and the single steps of operation are documented here:
1. Download Remix OS You are getting version 3.0.206 B2016101201 since October 12th, 2016.
The old version 2.0.403 (based on Android Lollipop) is not available anymore.
2. Tools (for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox)
3. Perform a Remix OS USB drive installation using Jide's current iso file
4. OTA-Update of a Remix OS USB drive installation July 15th: Update to version 2.0.403 (2016-07-12)
5. Install Remix OS (on hard disk, virtual machine, with dual boot)
6. Enable/Install Google Play Store
7. Setting screen size and density (mirrowing the output)
8. Update Remix OS (hard disk, virtual machine, dual boot)
9. Rooting Remix OS 2 / Checking and managing built in Remix OS 3 root access (hard disk, virtual machine)
10. Last Lollipop version 2.0.403 (2016-07-12)
11. First Marshmallow Versions 3.0.101, 3.0.102, 3.0.103 (2016-07-26) (2016-08-03)(2016-08-11)
12. New versions 3.0.104(2016-08-11) and 3.0.201 (2016-08-16)
13. Version 3.0.202 (2016-08-23) - 64bit version installable again
14. Version 3.0.203 (2016-08-30) - Installation directory called "RemixOS" now
15. Update from Remix OS 3.0.101 to version 3.0.x
Tools
Tools for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox
1. Which USB devices are suitable?
You'll need a fast USB device of at least 16 GB. If your computer doesn't have USB 3.0, you can use a fast USB 2.0 flash drive (e.g. Transcend Ultra Speed 16 GB) or an external SSD drive.
2. Creating a bootable USB device containing Remix OS
There are several tools for converting an iso file into a bootable USB device. It doesn't matter which one you take.
The zip archive "Remix_OS_for_PC_64_B2016030106.zip" contains a "remixos-installation-tool.exe" which you can run in Windows.
After booting the USB device and pressing the tab key you'll see this screen:
http://postimage.org/index.php?lang=german
The USB device will have 3 partitions:
- REMIX_OS (4 GB fat32)
- REMIXOSSYS (3 GB fat32, boot flag)
- REMIXOSDATA (8 GB ext4)
Unetbootin is available for Linux, Windows and Mac. It will create only one fat32 partition. The start screen is very similar (!) to the remixos-installation tool:
http://postimage.org/index.php?lang=german
If you use the Windows tool Rufus 2.8 portable or Linux system commands (see link ) you'll create a bootable fat32 partition as well and get an android-x86.org start screen:
http://postimage.org/index.php?lang=german
3. Tool for checking or creating partitions and for modifying the ext4 Remix OS file system with root privileges
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
The pmagic_2013_08_01.iso can be used for booting of a virtual machine with PartedMagic:
http://postimage.org/index.php?lang=german
4. VirtualBox Raw Hard Disk Access
VirtualBox can mount entire physical hard disks - look at http://www.serverwatch.com/server-tutorials/using-a-physical-hard-drive-with-a-virtualbox-vm.html .
This is valuable for 2 reasons:
- Only the bootable USB device with Remix OS can get an OTA update. Mounting this device to Virtualbox will be needed for an update of a Virtualbox installation (if you can't download an iso file containing the current version).
- Running a bootable USB device within a Virtualbox window will allow you to use functions of the host system for taking screenshots or for using external monitors.
Above link (by serverwatch) contains all information needed for Windows, Mac OS, and Linux.
In Linux you MUST add your user account to the vboxusers group for VirtualBox to see your USB. You MUST also add your account to the disk group as well, or you cannot add the .vmdk file to your Virtual Machine (see http://askubuntu.com/questions/693719/how-to-boot-from-a-usb-drive-in-virtualbox ; reboot is needed).
In a first step you'll have to determine the drive name of your external disk.
The Linux command is sudo fdisk -l . An example of the output listed for an USB device created by the remixos-installation-tool is:
. . . .
Disk /dev/sdc: 16.1 GB, 16055795712 bytes
. . . .
Device boot. Start End Blocks Id System
/dev/sdc1 2048 8290303 4144128 b W95 FAT32
/dev/sdc2 * 8290304 14581759 3145728 b W95 FAT32
/dev/sdc3 14581760 31358975 8388608 83 Linux
You are creating a vmdk-file for above example (i.e. drive name = /dev/sdc ) with
VBoxManage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdc
In order to run bootable USB drives in Virtualbox you have to plug in a bootable USB drive and to setup a Virtual Machine this way:
http://postimage.org/index.php?lang=german
If you have plugged in a PartedMagic USB drive you'll see it's start screen after having started the virtual machine:
http://postimage.org/index.php?lang=german
Plugging in a Remix OS USB drive and starting the Virtualbox virtual machine will show the Remix OS start screen:
http://postimage.org/index.php?lang=german
This way you can run a PenDrive installation of Remix OS within a VirtualBox window in order to create screenshots.
Remix OS Installation on an USB (flash) drive
The Remix OS iso file has to be converted into a bootable USB drive using one of the tools mentioned in Tools.
The start menu will be
http://postimage.org/index.php?lang=german
Set up Remix OS in Resident mode and wait up to 30 minutes for the screen "Select your language".
Select your keyboard layout and click "Next".
Select your Wi-Fi connection and enter your password.
Click "Start" if you see the message "Setup is complete. Your Remix OS is ready".
By clicking "Settings > Update" you can check whether there is a new OTA update. If yes perform the OTA update.
OTA Update of an USB flash drive installation
Since April 2016 you could download new versions from http://www.jide.com/remixos-for-pc only about one week after an OTA update was possible. So performing an OTA update of your Remix OS USB drive is not necessary if you can wait a few days. Since July, 15th you can download version 2.0.403 directly and go on with installing of new or updating of existing Remix OS installations.
Performing the OTA update
After clicking "Settings > Update" you might get the message "Latest version: Remix OS 2.0.403 ... Please download and install the update"
http://postimage.org/index.php?lang=german
Before starting the "Download" please click the 3 dots and select "Options"
http://postimage.org/index.php?lang=german
OTA-Upgrade after Reboot:
http://postimage.org/index.php?lang=german
You can use the updated USB device for installing of new and updating of existing Remix OS installations.
Installation of Remix OS on Hard Disk or within a Virtual Machine
Step 1: Partitioning and formatting of the (virtual) disk
The Remix OS installation tool offers cfdisk for formatting of the (virtual) disk.
How to use cfdisk has been documented in Installing Remix OS to Hard Drive or Virtual Machine without additional tools.
GParted is a better and more flexible partitioning tool which can be used after you booted your computer or your virtual machine with PartedMagic (see Tools ).
In Virtualbox that can be done by attaching the pmagic.iso as "Optical Drive" to the IDE controller (section "Storage").
http://postimage.org/index.php?lang=german
After booting with PartedMagic you can start the "Partition Editor" (GParted). You'll find a new (virtual) disk "unallocated".
After creating a MS-DOS partition table ("Device > Create Partition Table") you can create an ext4 partition for Remix OS, and a swap partition.
http://postimage.org/index.php?lang=german
The partition table has to be different if you are setting up a dual boot system - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
Step 2: Booting with Remix OS
You'll take a bootable USB device (original or OTA updated) for installing Remix OS on a hard disk.
Working with a virtual machine, you'll attach the Remix_OS.iso to it's optical drive, if it is the current version (case 1).
If you do not have an iso file of the current version, but an updated Remix-OS USB drive, take it for booting (case 2).
Case 1
http://postimage.org/index.php?lang=german
Case 2
If your Remix-OS USB drive has been updated already (see OTA-Update USB Installation ) the source of your installation has to be an USB device. You'll create a VirtualBox Raw Hard Disk Access (see Tools ):
http://postimage.org/index.php?lang=german
Step 3: Remix OS Start options "INSTALL=1 DEBUG="
Press the Tab key shortly after you see the Remix OS boot menu and change the start options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 4: Remix OS Installation
- Select a partition where to install Android-x86 (usually sda1, formatted with ext4)
If you are setting up a dual boot system, the partition may be sda2 - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
- Do not format, if you have created the partitions with PartedMagic
If you did not use additional tools (see "Installing Remix OS to Hard Drive or Virtual Machine without additional tools") formatting is needed.
- Do you want to install boot loader GRUB? - usually "Yes". If you are setting up a dual boot system: "No"
- Do you want to install EFI GRUB2? - usually "No"
- Do you want to install /system directory as read-write? - "Yes"
http://postimage.org/index.php?lang=german
Step 5: Setting up Remix OS
After the start of Android-x86 RemixOS will be initialized. Be patient - this can last up to 30 minutes (especially in virtual machines). You'll see "RemixOS" flashing a long time.
If your installation has been performed within a virtual machine you'll need "mouse integration" for the next steps.
In VirtualBox you have to click "Input > Mouse Integration". In VMWare there is a similar command (try Ctrl + G).
You need to manually start and stop the mouse integration (Virtualbox: Right Ctrl key; VMWare: Crtl + Alt), because there are no guest extensions for Remix OS yet.
After a while (the time Remix OS needs to create your new data directory) you'll see the window "Select your language".
- Please click "Select your keyboard layout" first and set up the keyboard layout of your country.
- After clicking "Next" you have to accept a "User agreeement"
- If you are not working with a virtual machine you'll be asked to select your Wi-Fi connection and to enter it's password
- Finally you'll see "Setup is complete. Your Remix OS is ready". Click "Start"
Do not forget to disconnect your installation source before rebooting Remix OS.
http://postimage.org/index.php?lang=german
If you have installed the GRUB boot loader, you can boot with PartedMagic again, start the "File Manager", open the Remix OS partition (e.g. sda1), and open directory grub. After opening of "menu.lst" you can modify "timeout=6" to "timeout=0". This way Remix OS will start without showing you a boot menu.
In case of a dual boot system your main operation system will start after the reboot.
You'll have to customize the GRUB settings - see ""How to install Remix OS alongside Ubuntu (Dual Boot)""
Enabling or Installing of the Google Play Store
Enable the Google Play Store using root terminal commands
Since version 2.0.403 you have to switch on "Enable debug terminal console" (Settings > Experimental features) in advance.
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Restart Remix OS
Clicking the Play Store icon after the restart will allow you to sign on with your Google account and install apps.
New proposal for installing the Google Play Store, coming with version 2.0.202
The new symbol "Install Apps" on the Remix OS 2.0.202 desktop is a link to a google forum "Remix OS for PC": How to download and install Google Play Store on Remix OS for PC based on downloading "GMSActivator.apk"
This approach has 2 disadvantages:
- Installation from unknown sources is required
- It is more time consuming as just typing 5 command lines into a terminal
Update for Remix OS installations
Update for Remix OS 2.0.x or 3.0.x systems which have been set up using the boot option INSTALL=1
Clicking "Settings > Update" (Remix OS 2.0.x) or at "System update" (Remix OS 3.0.x) will show that there is a new version of Remix OS.
With current version 2.0.402 you'll get the information, that there is a new version 2.0.403 (2016-07-12).
http://postimage.org/index.php?lang=german
If you start "Reboot and Install" in a Remix OS system which has been installed using the boot option INSTALL=1 ( see "How to install Remix OS in VirtualBox (or to harddisk)"), the root terminal will show an error message after rebooting the system (typing <Alt + F1> after the restart):
Start updating...
ui_print Warning: No file_contexts
script aborted: /mnt/system.img has been remounted R/W; reflash device to reenable OTA updates
wait pidpid doneError in data/media/0/autoupdater/otapackage.zip (Status 7)
Update failed
So the update has to be performed using a current updated version (downloaded from Jide - in case that exists) or an OTA-updated USB device replacing the system directory with a new one and preserving the data directory.
Step 1: Boot your system with PartedMagic (like in "Installation on Hard Disk or VM" )
Start the "File Manager", and open the Remix OS partition (e.g. sda1)
http://postimage.org/index.php?lang=german
- Delete all files and directories other than the old android directory ("android-2016-03-01" for version 2.0.102, "android-2016-04-05" for version 2.0.202, "android-2016-04-20" for version 2.0.205, "android-2016-06-30" for version 2.0.402, "android-2016-07-26" for version 3.0.101, "android-2016-08-03" for version 3.0.102, "android-2016-08-08" for version 3.0.103, "android-2016-08-11" for version 3.0.104, "android-2016-08-16" for version 3.0.201, "android-2016-08-23" for version 3.0.202)
- Rename "android-2016-08-23" into "RemixOS" for new version 3.0.203.
- Open directory "RemixOS" and delete all files and directories other than "data":
http://postimage.org/index.php?lang=german
- Close the File Manager and shut down PartedMagic.
Step 2: Booting with your Remix OS USB drive (which is the current version or which has been OTA updated before - see OTA-Update USB Installation )
For updating a VM installation (Virtualbox or VMWare) you have to distinguish 2 cases:
- there is an iso file of the current version --> attach it as optical drive
- you have an USB drive only containing the current version --> attach the prepared usb.vmdk (see Tools ) as first entry to your SATA Controller:
http://postimage.org/index.php?lang=german
After popping up of the Remix OS boot menu press the Tab key and change the boot options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 3: Remix OS installation
The installation begins with selecting the Remix OS partition. The image shows the 3 partitions of the USB device first (sda1, sda2, sda3), and the 3 Remix OS partitions (sdb1, sdb2, sdb5) below. The ext4 Remix OS partition is sdb1.
http://postimage.org/index.php?lang=german
- Do not format your Remix OS partition (sdb1) because you want to preserve your data directory
- Install a new boot loader GRUB (the old one had been deleted because it pointed to the old android directory)
If you are updating a dual boot system, don't install GRUB (but you have to update the customized GRUB of your main OS - see below)
- Do not install EFI GRUB2
- Install a new /system directory as read-write (the old /system directory has been deleted in step 2)
- Run Android-x86 after the installation has finished
- After quite a while you'll see the message "Remix . . . Finishing boot" and somewhat later your old Remix OS desktop.
- You'll find a new icon "Install Apps" (see Google Play Store ), but you don't need it, because your Google Play Store is still working.
- Shut down Remix OS and remove the USB drive or the iso file which you have used for installation
Step 4: Finishing work
The grub directory and the system directory have been created newly. So all modifications concerning boot menu (see Hard Disk or VM Installation ) or rooting (see Rooting Remix OS ) have to be done repeatedly.
In case of a dual boot system (see http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-alongside-t3352890 ) the "Grub Customizer" of the main operating system has to be opened, and the path name of the android directory has to be corrected to "android-2016-07-12" for version 2.0.403 or to "RemixOS" for version 3.0.203)
http://postimage.org/index.php?lang=german
Checking the version (with "Settings > Update") after a restart will show the new version. Your personal data and your old desktop have been preserved.
http://postimage.org/index.php?lang=german
Rooting of Remix OS 2 (Remix OS 3 is rooted by default)
Remix OS has a terminal app (version 3: Termux) and a root terminal (press <Alt + F1>). So rooting is essential only for apps which need root privileges. Remix OS 3 is rooted by default; so you can go on with step 4 (without installing anything).
Rooting of version 2 is based upon file remixroot.zip, whose contents have to be copied into the android directory of Remix OS. Running the shell script remixroot.sh with root privileges will do the rooting. The modfications of the Remix OS file system are performed using PartedMagic.
Step 1: Copy file remixroot.zip into the Download directory of Remix OS
Step 2: Boot the system with PartedMagic (see Tools ) and open the "File Manager"
- Open drive sda1 and go into path /media/sda1/android-2016-04-05/data/media/0/Download .
http://postimage.org/index.php?lang=german
- Double click remixroot.zip and extract its contents (directory su and shell script remixroot.sh) into path /media/sda1/android-2016-04-05/
Result:
http://postimage.org/index.php?lang=german
- Click "Tools > Open Terminal Here" → By entering command "sh remixroot.sh" your Remix OS will be rooted:
http://postimage.org/index.php?lang=german
- Shut down PartedMagic and start Remix OS again
Step 3: Updating App SuperSU (needed for Remix OS 2 only)
After rooting of Remix OS you'll find SuperSU in the Remix OS start menu. SuperSU's task is the administration of all root permissions (see link), and it must have the actual version.
http://postimage.org/index.php?lang=german
After starting "SuperSU" an update is needed: "The SU binary needs to be updated" → Continue → Normal → "Installation success" → Reboot
Opening "SuperSU" again shows version # 2.46.
Another update is needed now, this time after searching the app in the Google Play Store . The next start of "SuperSU" will need a SU binary update again.
After the reboot and opening "SuperSU" you'll see version # 2.65 which is ok.
Step 4: Checking whether rooting was successful
The Remix OS Terminal (version 3: Termux) can be used for a first test. The terminal prompt should change from $ to # after calling su (see link).
The user id should change, too:
http://postimage.org/index.php?lang=german
After entering "su" a window will pop up asking for "denying" or "allowing" the root access (version 3: once, always, or for 10 minutes only).
https://postimage.org/app.php
Allowing root access in Remix OS 3
http://postimage.org/index.php?lang=german
Granting root access in Remix OS 2
You'll have a few seconds only for clicking "GRANT". Otherwise you'll get the message "Permission denied".
For Remix OS 3 only:
The built in function "Settings > System > Superuser" will show you a log of granted superuser requests. Clicking "Settings" you can modify settings concerning superuser access.
https://postimage.org/app.php
or Remix OS 2 only:
SuperSU will show you which apps got root permissions. Below image shows that the first trial of giving root permission to app "Root Checker" was not successful (not granted in time - you have to be fast - see https://su.chainfire.eu/). The second trial worked.
http://postimage.org/index.php?lang=german
OTA update to version 2.0.403 (2016-07-12)
You will be informed that there is an OTA update to version 2.0.403 if you are working with version 2.0.402.
You download version 2.0.403 from http://www.jide.com/remixos-for-pc. So you don't have to OTA update your new USB flash drive.
An OTA update of the new version (see OTA Update of an USB flash drive installation) makes only sense a few days until you can download the new version.
The flash drive with version 2.0.403 can be used then for updating an installed version (created with "INSTALL=1" option - see "Install Remix OS") of Remix OS.
and the new version (2.0.205) now have ability to browse the hdd partition from file manager or another file explorer [emoji4]
Jide's announcement of new version 2.0.402
New
Keyboard mapping for certain games has been added to allow users to play games with keyboards
Supports mirrored output from DP, HDMI & VGA
Supports more Realtek/Broadcom/MediaTek WiFi cards
Pre-installed Chrome and Chrome Switcher that allows users to stay on desktop mode by default
Fix
The task bar disappearing on its own is fixed
Time inaccuracy on Windows when users switch back from Remix OS is fixed
More NVIDIA graphics cards are supported with improved stability
Thermal monitoring system is improved to avoid overheating
How to perform an update to version 2.0.402 of an installed version of Remix OS
Jide's Help Center
Hmm. having issues installing inside a ESXi host.
When booting into RemixOS I get the error message like:
"driver does not support CPU family 6 type 7"
And then it reboots. Any ideas?
Setting screen size and density
Since version 2.0.402 Remix OS supports mirrored output from DP, HDMI & VGA. So you can mirror your output to a second screen. But you have to adjust your screen size and density according to the second screen.
With <Alt F1> you can open a root terminal (see "Settings > Experimental features > Enable debug terminal console").
<Alt F7> will close the terminal.
Typing wm will show you the commands for changing the screen size and density: wm
wm size [WxH]
wm density [DENSITY]
wm overscan [LEFT,TOP,RIGHT,BOTTOM]
wm size will show e.g.
Physical size: 1440x900
Override size: 1280x1024
wm density is the DPI density and will show e.g.
Physical density: 160
Override density: 180
Example:
wm size 1024x768
wm density 140
will adjust your output to a 1024x768 screen.
Versions 3.0.101 (2016-07-26) / 3.0.103 (2016-08-08)
Using the INSTALL=1 command (see Installation Remix OS on hard disk) an installation on a Lenovo T400 or within Virtualbox was not possible (see Remix OS 3.0.101 64bit does not start correctly).
Using the 32bit version, Remix OS started correctly, repeatedly, and with good performance on an 16GB USB device (see Link). Running then 32bit version installed on a hard disk or within Virtualbox (using "INSTALL=1") was possible, too.
So it seems that version 3.0.101 64bit still has problems prohibiting an installation to hard disk or to Virtualbox. I'll keep working with version 2.0.403 64bit until the problems have been fixed.
Version 3.0.102 (2016-08-03)
Remix OS 3.0.102 64bit can be installed on a Lenovo T400. After clicking "English" the menu moves to the left side and vanishes a few seconds later. The screen remains dark. Hitting some keys I finally saw the message: "Jide setup wizard isn't responding - Do you want to close it? Wait - OK". There is no difference to the behaviour of version 3.0.101.
The 32bit version can be installed on a Lenovo T400 and runs. The main differences to version 3.0.101 are:
- Symbols for an "App store" and Games
- A symbol for checking whether there is a "System update". If "yes" an OTA update will be possible in future.
- see official thread "Remix OS for PC update 3.0.102" for more information
Version 3.0.103 (2016-08-08)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400 (see above).
The 32bit version runs. There are only minor updates - see official thread
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got those in the beginning as well. The fix that I found somewhere was to simply remove your account, add it back, and then clear data/cache of play store and play services before running play store for the first time. It worked.
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got error DF-DLA-15, too, in my first try. I repeated the installation, enabled the Google Play Store, and restarted Remix OS 3.0.101 32bit. This time I could sign on and install apps without problems.
Update from Remix OS 3.0.101 to version 3.0.10x
For Remix OS systems which have been set up using the "INSTALL=1" option, an update (preserving all data) from version 3.0.101 to version 3.0.102 is possible - see link "Update for Remix OS installations".
Version 3.0.102 has the function "System update" wich will be used for OTA updates in future.
Versions 3.0.103 and 3.0.104 could be downloaded the same day there was an OTA update available. So link "Update for Remix OS installations" is ok for an update to version 3.0.10x, too.
remixtester said:
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
Click to expand...
Click to collapse
I would strongly discourage anyone from using the 2013_08_01 version of PartedMagic. Yes, it may be the last free version, but it is also has a high risk of damaging devices. There used to be a message on the PMagic site, long since removed:
This version was released with a very destructive USB corruption bug in the Linux kernel. We removed this file from our official mirrors to minimize the damage and quickly released version 2013_08_10 to replace it. The 2013_08_01 version also included a bug in the OLD Secure Erase GUI that would allow a user to erase an ATA disk through a USB interface. In some cases it would brick the expensive USB device. The OLD GUI would also set the secure erase password to NULL by default and using the disk on a Lenovo BIOS is not possible because a password cannot be entered.
Click to expand...
Click to collapse
I have found the GParted version on SystemRescueCD (regularly maintained and readily available) will work just as well fro what I used to use PMagic for. http://www.system-rescue-cd.org/SystemRescueCd_Homepage
Versions 3.0.104 (2016-08-11) and 3.0.201 (2016-08-16)
Version 3.0.104 (2016-08-11)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. There are minor updates fixing most Google Activation issues (link).
Looking at a video e.g. using VLC does not need anymore activating the "Auto-hide taskbar" (Settings > Remix OS options) in order to have a full screen image.
Wi-Fi-Problem still existing with version 3.0.104: After starting Remix OS in most cases the Wi-Fi is not connected automatically, as long as the "Wi-Fi" pop-up window is not opened yet. After opening the Wi-Fi pop-up window Wi-Fi is connected automatically a few seconds later. It's not a big problem, just not comfortable.
Version 3.0.201 (2016-08-16)
Release Notes
Remix OS 3.0.201 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. NTFS and EXT4 (new feature!) partitions are mounted automatically. During startup Remix OS tries to mount it's own partition (dual boot with Ubuntu) and creates a message "corrupted".
Hey XDA!
For those of us that use Arch linux, compiling Android projects can be a little more challenging than on Ubuntu due to the fact the Arch is a rolling release distro. To solve this, I made a tool that allows YOU to choose whether you want to run Arch or Ubuntu in the command line without dual booting. This isn't anything new, just a simplified implementation of an existing method.
What it does:
When you open a terminal, you will be prompted with "Would you like to connect to Arch linux or Ubuntu?". You can enter A for Arch or U for Ubuntu. If you choose Arch, you will be put into your stock environment, but your bash prompt will look like
Code:
[[COLOR="red"]user[/COLOR]@[COLOR="cyan"]Arch[/COLOR] ~]:
If you choose Ubuntu, you will be entered into your Ubuntu chroot, and your bash prompt will look like
Code:
[[COLOR="red"]user[/COLOR]@[COLOR="magenta"]Ubuntu[/COLOR] ~]:
DISCLAIMER
Because Arch linux is aimed at enthusiast and experienced linux users, replies about simple or lack-of-experience issues will not be given priority. Use the following with caution.
How to setup an Ubuntu chroot:
1. Install schroot and debootstrap
2. Follow the steps given here https://bbs.archlinux.org/viewtopic.php?id=100039, or run create-chroot.sh in the OSConnect git repo.
How to install OSConnect:
1. Clone https://github.com/frap129/OSConnect
2. Run the given install.sh
3. If you use terminal mostly locally, respond "Local" to the prompt. If you mostly connect via ssh, respond "SSH" to the prompt.
4. If you connect via SSH, connect as root from now on, not your user. OSConnect will switch to your user for you.
Done! Restart to use.
XDA:DevDB Information
OSConnect, Tool/Utility for the Chef Central
Contributors
frap129
Source Code: https://github.com/frap129/OSConnect
Version Information
Status: Stable
Created 2016-05-15
Last Updated 2016-05-15
How it works:
Ubuntu chroot:
This work by downloading the Ubuntu system files to /var/chroot/ubuntu. The schroot tool then executes bash from ubuntu, and tricks the system into believing that /var/chroot/ubuntu is actually the system root directory.
OSConnect:
OSConnect is contained in its own file, .osconnectrc. This file is executed when shell is reached via your .bashrc. The .osconnectrc is a bash script that asks what operating system you would like to use, then either dumps you into normal shell, or starts the Ubuntu chroot. It also modifies the PS1 (bash prompt) to look cleaner and better distinguish between Arch and Ubuntu.
What is the difference between local and ssh?
The only difference between the local and ssh versions is whether or not youre prompted for your password (when chroot is started) because schroot must be run as root. On the local version, you are simply prompted for your password when necessary. On the ssh version, you are expected to connect as root, and therefore will not be prompted for your password.
HALP I CANT LOG IN AS ROOT
If you are having trouble connecting via SSH as root, follow https://askubuntu.com/questions/511833/cant-ssh-in-as-root
Resource wise is this lighter than running ubuntu as a docker image?
HaoZeke said:
Resource wise is this lighter than running ubuntu as a docker image?
Click to expand...
Click to collapse
I'm way to late for this to matter, but yes, its much lighter than running at as a docker image
frap129 said:
I'm way to late for this to matter, but yes, its much lighter than running at as a docker image
Click to expand...
Click to collapse
Better late than never! ? neat stuff ?