Develop Bugs

Guide to compiling (covers cm7)

This guide is geared to people that are new to ubuntu but would like to start playing with the internals of their android device and maybe even make themselves a rom,
disclaimer: if you break your equipment well that just plain sucks
If you are new to linux or wanna learn more about ubuntu, here is a link to the ubuntu 10.10 wiki and is full of great info
http://ubuntuguide.org/wiki/Ubuntu:Maverick
So you got yourself a nice copy of Ubuntu 9.10/10.04/10.10 and you have every intention of building a rom for yourself or maybe you just wanna learn the inside workings of android, well there are a few extra steps for getting it set up in 9.10/10.04. Gonna try to make this an easy transition since most of you are coming from a windows based machine. Make sure that you have at least a 30 gb partition set up to follow along with this guide, more is better but I know some don't have the hard drive space to spare.
So let's get our hands dirty
First we need to set up java and get a few programs, but first we need to open up our software settings, this is achieved by going up to our MENU BAR, going to SYSTEM and then then ADMINISTRATION. We will then go into SOFTWARE SOURCES. On 9.10/10.04, the repository for java 5 was removed so we need to add 9.04's repository. So let's go to our second tab marked “other software” and click ADD. A small box will open up asking us to add a apt line. So we have two software lines to add individually.
(on 10.10 software sources is inside update manager, clicking settings gets you into it)
{
"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"
}
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
then
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
Now, make sure that both are checked to be used in software sources and close the window. It should ask to update your sources, allow it to (insert screenshot)
Some people have problems with internal wireless cards so this might be a fix for you which was an issue for me and thankfully Garok89 had the answer. This fix works on Broadcom based cards only (including Dell wireless cards).
For the wireless card (plug in via ethernet of course)
Open up a terminal and type
sudo apt-get install bcmwl-kernel-source bcmwl-modaliases
Reboot and then enable via System>Administration>Hardware Drivers
and see if it now says that you have proprietary drivers now
gingerbread is 64 bit only
http://groups.google.com/group/android-building/browse_thread/thread/852d63ab6124c87e?pli=1
Let's open up a pretty little terminal and let's get some debs (debs are Linux distribution specific packages like we have apks in android). After entering this command it will ask you to input the "[sudo] Password for xxxxx", this is the password you use to logon. (When you type your password you will not see anything, this is for security purposes)
sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind
NOTE: If we want to build with a x64-bit system we must also do the following
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl sun-java5-jdk zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev sun-java6-jdk gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind pngcrush wput
It is quite a lot but it will download quickly depending on your internet connection, but almost all are needed, and yes, I did put in both java 5 and 6 because for some reason it helps having both installed side by side.
(don't forget to run update manager again and get your system up to date)
well while we are here we midas well set up our tool for downloading the source
REPO
Repo is a tool that makes it easier to work with Git in the context of Android. It is a almost the same as Git and we will go into the differences at a later time
we are gonna make sure that we are in our right directory so
cd ~
~ means home/user dir, so in my case it would be /home/sykopompos/ but using ~ allows us to simplify our use.
Mkdir bin
export PATH=${PATH}:~/bin
by typing echo $PATH we can see the all of what is in our path
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
to get the repo script
then we give it executable permissions so we can run it as a program
chmod a+x ~/bin/repo
Now we have repo set up we can move on to other things. Let's get going with setting up the android sdk. Let's go to the sdk's page in our web browser
http://developer.android.com/sdk/index.html
and select the newest linux version and download. When it is finished downloading open it up and extract it to your home/user folder and rename it to androidsdk for guide following ease purposes
next let's set up eclipse
open up eclipse, it will be in your menu bar under programming. just let it save to the workspaces folder that it defaults to and open up the help tab up on the top bar and go down to install new software
and add this line into the open text bar and type this
http://dl-ssl.google.com/android/eclipse/
now click add and in the box down below you will see it says developer tools. Click on the little check box and hit next. You should see android development tools hit next and follow the prompts and wait for it to download and install. You will have to agree to the terms to download, You will get a warning about unsigned content, just say yes. Once it is done click to restart Eclipse then go up to the window tab and go down to preferences, in the new window that pops up, go to android and add in where your android sdk is. Just hit ok and not apply or it will complain.
close out of that window than go down to in the window tab again and go into android sdk and avd manager. Go down to available packages and click on the little check box again. Download all available packages (you can prob get away without downloading anything pre 1.5/cupcake. Let that download and exit out
testsigning
go up to places on your desktop menu bar and go into your home folder. Press Ctrl and h together on your keyboard to show hidden folders. Anything marked with a . in front of it is hidden, we are looking for a folder name .gnome2, go into it and look for nautilus-scripts. Once inside this folder, right click on a empty space and select create document and then empty file and name it sign. Open up that empty document and copy and paste this script from dumbfaq on xda
#!/bin/bash
# Update the Loc var to where YOU stored the testsign.jar file !
SUCCESS=
Loc=~/androidsdk/tools/
for arg
do
TMP=$(ls $arg | sed 's/\(.*\)\..*/\1/')
EXT=${arg##*.}
java -classpath "$Loc"testsign.jar testsign "$arg" "$arg"-signed 2> /tmp/signTmp
SUCCESS=$?
if [ $SUCCESS -eq 1 ]
then
zenity --info --title "Sign APK" --text "signing FAILED! \n`cat /tmp/signTmp`"
exit 1
fi
mv $TMP.$EXT-signed $TMP-signed.$EXT
done
zenity --info --title "Sign APK" --text "signing completed!"
save and exit out and right click on our new script and select properties. select thru the tabs and look for a check box that says allow executing as a program. click on it and now we have a pretty little script that we can just right click on a update.zip file and sign with our test keys for flashing. but first we need to download the testsign java file and add it to our androidsdk/tools folder http://rapidshare.com/files/257189327/testsign.jar do not extract this just add it to the tools folder.
Last but not least, we need to set up adb
Open up a terminal (you might still have the previous one open, you can use that just make sure you are at ~/) and type
gedit .bashrc
paste this in the top
#AndroidDev PATH
export PATH=${PATH}:~/androidsdk/tools
export PATH=${PATH}:~/androidsdk/platform-tools
save and exit
we will check what our phone's vendor id is, this is helpfull to see if our phone is on the list, with all the growing numbers of new manufacturs producing android it is hard know every vendor's id so type
lsusb
while your phone is connected to see our vendor id and you will see something like this, if you have a device not listed please send me the vendor id at [email protected] so i can update in for others
Bus 002 Device 004: ID 0bb4:0c91 High Tech Computer Corp. (example is G2)
In this case the Vendor Id is “18d1″ and the Product ID is “4e12″. Please keep in mind that the Vendor ID for HTC changed from “0bb4″ to “18d1″. The older HTC phones like the G1 have a Vendor ID of “0bb4″.
in most cases as seen below we only need the vendor id and with a new device you can just c+p the line and replace the vendor id
so now we can make our rules file for connecting for adb so
sudo gedit /etc/udev/rules.d/51-android.rules
paste
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
save and exit
reboot your computer to have the new changes take effect otherwise adb will not be in your $PATH
let's check to make sure our device is seen by adb by typing
adb devices
it should give you info back that you are connected if you are not or it doesn't read the vendor id than it might be a little bit more complicated, note adb will not read if you have usb mass storage mounted, also need usb debugging on in settings/apllications/development on your phone
Now we have a complete android development environment, aren't you proud of yourself. You are well on your way to making your own custom rom
it is a wise idea to have a backup of a system dump for stock apps and to get a feel for the way android is set up and also to pull any needed files from that are easily viewed on your computer at least as refefence connect your phone in adb in the terminal type
cd ~/
mkdir stock
cd stock
adb pull /system/ ~/stock/
this will make a system dump of your systems folder of your device, a wise idea would be to make a zipped versions of it and put it someplace secure

Compiling cyanogenmod 7 source
Now we work on actually pulling sources and compiling source code. Since Cyanogenmod 7 is the most popular we will work with this (as of writing 1/15/11, cm7 source does not have a Rc1 yet so non official builds after the bacon script has the KANG attached to them)
So let’s pull cm7, open a terminal and type these commands
(you can name your source folder whatever you like but for guide purposes it will be cm7)
(make sure you are at ~)
mkdir cm7
cd cm7
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
It will ask you to enter your name and email (this is completely optional and you can just press enter to skip)
Press y and enter to confirm that your identity is correct, press y again to enable user color
You will now see repo initialized in our in our cm7 folder
Now we can use repo sync (this acts as a git clone to copy the source to our local branch)
In the terminal type
repo sync
This will take a while to download depending on your internet connection since it is pulling in over 2gb of source code (don’t use tethering during this as it will eat up your data for the month)
(you can use -j`grep 'processor' /proc/cpuinfo | wc -l` to run at full cpu speed. -j# (# means twice the amount of cores in your computer) means jobs. I will compare this to workers, your cpu could be a dual core, quad core and/or have hyperthreading (hyperthreading means a quad core will be seen as having 8 cores, I7 are considered this) well each one of your cores is a worker so one worker would be -j2 meaning the worker will handle 2 jobs. If you tell your workers to do more jobs then they won’t be happy being overloaded just like how any worker would be and will actually be slower. Now -j`grep 'processor' /proc/cpuinfo | wc -l` means read your computer’s info and run at optimal speed, now why choose between the 2 well you might not wanna run at max speed and just wanna use only half your power so you use your computer for other things during)
When we are done syncing we can get back to work
I am gonna use vision as an example but you can change it to suit the device you are working on
connect your phone you are gonna work for adb and open a terminal or use current previous terminal
(note, the proprietary vendors have been modified to work for gingerbread so make sure you have either the most up to date cm7src build or when rc1/stable comes out on your phone to get the proper files)
(this assumes you are using a previous and are in cm7)
cd device
cd htc/vision
bash extract-files.sh
cd ~/cm7
cd vendor/cyanogen/
bash get-rommanager
cd ~/cm7
We now have pull the proprietary files for our phone so we can inject them into our build along with rom manager since it is required and will fail the build if you don’t
(if you look in your cm7 source you will now see inside vendor a folder called htc (our manufactor, if you are working on a samsung or motorola you will see that) and inside it you will see your device)
We are actually now ready to build so in our terminal
source build/envsetup.sh
lunch cyanogen_vision-eng
make clean
make bacon -j`grep 'processor' /proc/cpuinfo | wc -l`
Now our build is compiling
(the lunch command pulls target specific info so there is no need for a buildspec.mk to be made as lunch does this for us)
(always make clean between builds to remove old compiled files and make sure you have a fully working build with each update, it takes a bit longer but it is worth it)
(make bacon is a script that runs make otapackage and the squisher script which uses pngcrush to cut down the size and also removes unneeded things added by doing a -eng build, it also resigns it)
When your build is complete you should have a update-cm-7.0.0-RC0-vision-KANG-signed.zip in your cm7/out/target/product folder, this is your new build.
Congratulations on your first build from cm7 source
Now for a new build you would repo sync again, make clean and make bacon again

Kernel compiling
We are gonna be pulling the cyanogenmod htc msm 7x30 kernel source, this covers ace, vision and glacier
so let’s open up a terminal and clone the kernel source so we can work with it
cd ~/
mkdir kernel
cd kernel
git clone git://github.com/CyanogenMod/htc-kernel-msm7x30.git
cd htc-kernel-msm7x30
We now have our source pulled and now need to set up our cross-compilier so we can make our kernel
export CROSS_COMPILE=~/cm7/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
export ARCH=arm
Now have our cross compilier toolchain set up and will need to now tell it what to build, I find that make menuconfig is just plain ugly and rough to work with so
make xconfig
This will load a nice menu UI for us to work with, we are not gonna get into modifying the kernel but just a default config so go up to file and click load and select arch, then arm, then configs.
select cyanogen_vision_defconfig and click open, this will load the default cyanogen kernel config and is what you will find in a cm7 build (or glacier or ace depending what you are building for)
You can just click the x button in the corner to close it and collect save changes
Now we can compile our kernel, we can us the -j command like before to speed it up
make -j`grep 'processor' /proc/cpuinfo | wc -l`
Once the kernel compiles we have to grab our zimage and our wifi module (the couple lines up will show you the modules made and the location)
The zimage is our kernel and it can it can be found at /kernel/htc-kernel-msm7x30/arch/arm/boot/ and our wifi module name as bcm4329.ko (modules have a .ko extension) is found at /kernel/htc-kernel-msm7x30/drivers/net/wireless/bcm4329/
These are the only things we need to worry about. Now you can adb push the wifi module onto your phone and fastboot the zimage or we can have it built into our build by going to cm7/device/htc/vision/ and replacing the kernel with our zimage (will need to rename zimage to kernel) and putting our wifi module in modules and overwriting the one currently there (Make a backup of the stock kernel and wifi modules to replace your’s just in case)
Now you have your own kernel and you can compile it into your build

reserved jhjlkk,mlkjnl;klm

reserved for future use
you guys can post now

Instead of make bacon -j`grep 'processor' /proc/cpuinfo | wc -l`, you can type mka bacon. mka uses schedtool (may have to install the package) as well as auto doing the correct number of jobs.
And after you do a ". build/envsetup.sh", you can just type reposync, rather than repo sync do do a faster sync of the repos because it will do a -j10. (repo supports multiple simultaneous jobs (ie -j#)

Wow a lot to learn. Now I have to kick the dust off my Linux and see what version it is and how much of a partition I made. Now I have something to do along with being a flash junkie.
I want to really Thank You for this guide. I really commend those that try to help others. Some people might not be able to do this no matter how easy you make it. But some including myself will find this information very useful.
A big thanks.

Thank you for sharing this with the Community.

Holy mother of matrimony, with corpses

You say 2.3 is 64-Bit only. Is that referring to the OS on the computer?

bubonik said:
You say 2.3 is 64-Bit only. Is that referring to the OS on the computer?
Click to expand...
Click to collapse
The os needs to be 64 bit, that is according to google's android blog
Sent from my HTC Vision using XDA App

gridlock32404 said:
The os needs to be 64 bit, that is according to google's android blog
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hmm Not sure what ubuntu 10.04 is? 32 or 64 bit? Also can I make a extra partition for this as the original one for ubuntu is only 15 mb? And do I make it ext4 or Fat32?

bobsbbq said:
Hmm Not sure what ubuntu 10.04 is? 32 or 64 bit? Also can I make a extra partition for this as the original one for ubuntu is only 15 mb? And do I make it ext4 or Fat32?
Click to expand...
Click to collapse
You can make it a new partition but you will have to change all the commands to the new partition so it might be more hassle than it is worth. Make it ext 4 for speed cause it is a native linux file system
Sent from my HTC Vision using XDA App

Updated the op with a link regarding gingerbread needing a 64bit os host

I'm gonna learn how to make bacon! Thanks for this thread.

Wish you had this up last month when I was pulling my hair out trying to figure this crap out. Thanks for it!

Is ffc working? ;p

The link in the first posst to ubuntu pocket guide is not working . It gets you to 4shared,but when trying to download it i just get that link is broken

I've built a rom for my incredible. I haven't flashed it as I went to work, and by the time I came back it was out of date lol. I ran it in a 32 bit VM, so I don't know what's up with needing 64 bit, as it's not what I used and got a good build I believe.

[APP] Ubuntu Install Guide - Archos Gen8/9 Testers wanted

I have working on a project in the form of an app, which guides you through the installation of Ubuntu within android via chroot. It includes a ubuntu 10.10 image I have been working on which includes lots of program to allow users to develop program/scripts etc within Ubuntu on there phone/tablet.
However I have I have yet to get much testing on this device and would like more feedback from users!
Please post your device/kernel/rom along with what did and didn't work, so I can draw up what I need to change in the next release of the app/ubuntu build.
Website
http://zpwebsites.com/android-app/ubuntu-install-guide/devices/
Video
http://www.youtube.com/watch?v=UCqzs8yQTM8
App Download
Free App
Paid App
Boot Script
ubuntu.sh(V5)
Full Image
This image is 1.5GB to download, once extracted 3.5GB, and include alot of programs like openoffice, thunderbird, firefox and over programs for 'developing' - Also allows you to switch between the LXDE and Gnome desktops, and you can define screen size on boot!
ubuntuV5-image.zip
Lightweight Image - This is yet to be included in an app, will be included in the next release (aka 2.0 ), so get it now before anyone else!
This image is just under 500MB to download, once extracted 2.5GB, and include only programs needed (LXDE desktop, web browser, + other basic programs) also allows you to define screen size on boot
ubuntuV5-sm-image.zip
I also want to build up a small group of testers who I can email with new images and scripts, these will include all future distros that I do. If you are interested in joining this test group please PM me or send a email to [email protected]
The only requirement is that your willing to test and send feedback along with screen shoots etc where required, it would also be good if your willing to try different roms and kernels for your device!
Sig Banner
Show your love of ubuntu on android with my sig banner:
{
"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"
}
image url is "http://dl.dropbox.com/u/11206993/ubuntuuser.png"
Other Guides
Like this guide? want to try something different? then check out my other guides for different distro's
Backtrack - This is a distro that is based around security testing, it also includes the Gnome desktop environment and a range of other programs.
Updates
29/01/12
*New V5 small image, featuring fixed Java, even more lightweight (now around 1.2GB free) and user can set screen size on boot
*PAID New Build guide which shows you how to build your own Ubuntu images
*Brand new UI To make the whole thing more useable
*PAID new 'one click boot' feature to allow quick booting from either the widget or inside the app
*PAID new widget to activate the one click boot
*PAID app install guide changed in light of 'one click boot'
*Fixed keyboard mapping of random letters in Gnome
18/01/12
*Large ubuntu image now allows user to set screen size on boot!
*Large Ubuntu image now lets you select between LXDE and Gnome desktops
*Large Ubuntu image has been recompiled to fix the likes of Java (note some of the above changes will be included in the small image in the future)
*FAQ section updated with more answers to questions I have been getting
*Install guide updated in light of the new large image
06/01/12
*PAID app file downloads now use new fast FTP server and support direct downloading (click the button to download a image and it starts to download right away)
*New boot script which has fixed problems with it not booting on alot of devices, and fixed problem which some people getting a grey screen when loading UI
*Boot script now downloaded in zip file to fix problems with downloading script
*Both apps fixed to support low resolutions
*Both apps cleaned up
28/12/11
*PAID app now supports 960x540 'qHD' resolution
*ALL Ubuntu lightweight images cleaned up even more saved another 300MB of space
*ALL Ubuntu images updated with all new updates
*ALL Ubuntu images now in .zip format to fix problems with some peoples devices failing to extract the .rar files
*Boot script updated, once booted now terminal acts like a command line interface for Ubuntu, and some boot problems now fixed
*Image and boot script now downloadable separately to allow easier updating
19/12/11
New 'lighter' ubuntu image options for all resolutions already supported
15/12/11
New ubuntu images with all updates up to 15/11/11
FREE app ubuntu image resized to fit 800x480 resolution
PAID app ubuntu images now includes 4 images for 800x480, 854x480, 1024x600 and 1280x800 resolutions
See how deep the rabbit-hole goes...
http://linuxonandroid.blogspot.com/

I want to be in
Hi zacthespack I was reading about your project, and I would like to help you, I am new to linux world, I was reading some about this OS, I am willingto learn about it, so I would like to try this, but I would like you to give me some advice and directions to learn and help you, I am very interested in learn about linux (and maybe in learn some other stuffs for android) I have some limited free time the hork and my family takes most of them, but I can use my free time to work on this...
Hope to be able to be in your project
P.S. By the way I would like to learn about backtracking, hope you can help me with this

Ubuntu Installer Paid 2.0 Cooked and ready to be tasted
Well tasted by my beta testers anyway...but yes 2.0 for the Paid app is ready! so long as there are no more bugs the new update will be loaded to the market tomorrow.
Note that once the new update is on-line the sale will end, so if you have not already grap your paid copy for 20%!!
The change log for the new version is:
*New V5 small image, featuring fixed Java, even more lightweight (now around 1.2GB free) and user can set screen size on boot
*PAID New Build guide which shows you how to build your own Ubuntu images
*Brand new UI To make the whole thing more useable
*PAID new 'one click boot' feature to allow quick booting from either the widget or inside the app
*PAID new widget to activate the one click boot
*PAID app install guide changed in light of 'one click boot'
*Fixed keyboard mapping of random letters in Gnome
The free version should then be updated by the end of next week and will include the new UI and the new V5 small image and Gnome mapping fix.
Backtrack will then be updated shortly after that to include pretty much everything in the change log above (apart from the small image, there is still no small image for backtrack)

rplc790222 said:
Hi zacthespack I was reading about your project, and I would like to help you, I am new to linux world, I was reading some about this OS, I am willingto learn about it, so I would like to try this, but I would like you to give me some advice and directions to learn and help you, I am very interested in learn about linux (and maybe in learn some other stuffs for android) I have some limited free time the hork and my family takes most of them, but I can use my free time to work on this...
Hope to be able to be in your project
P.S. By the way I would like to learn about backtracking, hope you can help me with this
Click to expand...
Click to collapse
I shall PM you

The wait is over, last minute bugs have been stamped out and the new update is live, should be coming to a device near you soon!
If you have bought the paid version check for updates!

Thanks for the good work!
I use it to run some wxPerl applications (standalone, e.g, no session, no window manager, just a fullscreen touchscreen application) on my Android Tablet.
I made some changes to the ubuntu.sh and init.sh scripts, to make them more flexible and robust. PM me if you're interested.

Hello,Zacthespack:
Why I follow your recommend process to install ubuntuV5.img in my Archos 101
but still could not open your ubuntu from UrukDroid-1.6.1 and 1.6.2
which already create "ubuntu" boot file in /AlternativeOS directory ?
Please help to answer beneath questions to make ubuntu V5 working
with UrukDroid-1.6.1 and 1.6.2 :
(1)whether I have to install the "ubuntuV5.img" in external SD Card
or internal SD Card respect the UrukDroid-1.6.1's shell script?
( refer to : http://code.google.com/p/urukdroid/wiki/RM_AlternativeOS )
(2) Do I need to locate "ubuntuV5.img" in a "Ubuntu" folder ?
(3) Do I still need to changes the ubuntu.sh and init.sh scripts if
UrukDroid-1.6.1 already has "ubuntu"boot script ??
Thanks and I like to further test your ubuntu V5 after your answering!!
(Sorry, Because I am not familiar with Linux program so need more detail
guideline for ubuntu v5 installation)

jackson0829 said:
Hello,Zacthespack:
Why I follow your recommend process to install ubuntuV5.img in my Archos 101
but still could not open your ubuntu from UrukDroid-1.6.1 and 1.6.2
which already create "unbutu" boot file in /AlternativeOS directory ?
Please help to answer beneath questions to make ubuntu V5 working
with UrukDroid-1.6.1 and 1.6.2 :
(1)whether I have to install the "ubuntuV5.img" in external SD Card
or internal SD Card respect the UrukDroid-1.6.1's shell script?
( refer to : http://code.google.com/p/urukdroid/wiki/RM_AlternativeOS )
(2) Do I need to locate "ubuntuV5.img" in a "Ubuntu" folder ?
(3) Do I still need to changes the ubuntu.sh and init.sh scripts if
UrukDroid-1.6.1 already has "ubuntu"boot script ??
Thanks and I like to further test your ubuntu V5 after your answering!!
Click to expand...
Click to collapse
My method is different to what you have said, it is not running ubuntu natively but within android.
If you follow the install guide in the app it will tell you all you need to know.
but basiclly you need to create a folder on the internal memory called ubuntu (e.i sdcard/ubuntu) and place both my boot script and image in there.
Then if you have the paid app use the one click boot to boot ubuntu, or if using the free app enter the commands into the terminal app as described in the app.
The ubuntu boot script urukdroid has already is for booting ubuntu natively, so this can be completely forgotten about.

zacthespack said:
My method is different to what you have said, it is not running ubuntu natively but within android.
If you follow the install guide in the app it will tell you all you need to know.
but basiclly you need to create a folder on the internal memory called ubuntu (e.i sdcard/ubuntu) and place both my boot script and image in there.
Then if you have the paid app use the one click boot to boot ubuntu, or if using the free app enter the commands into the terminal app as described in the app.
The ubuntu boot script urukdroid has already is for booting ubuntu natively, so this can be completely forgotten about.
Click to expand...
Click to collapse
Hello,Zacthespack:
Thanks for your detail illustration my questions!
I try to follow your "ubuntu installer guide" but still got" VNC connection failed " message due to incorrect key-in data to "androidVNC",can you help to show me how to key in beneath
data in "androidVNC":
Connection: ubuntu:lacalhost:5900
Nickname: ubuntu
password: ?????? (Does ubuntu.img have password ?)
Address: localhost (Do I need to change to 192.168.x.xx ?)
Port: 5900
Username: ???? (what kind username I have to key-in?)
Thanks and looking forward your answers

jackson0829 said:
Hello,Zacthespack:
Thanks for your detail illustration my questions!
I try to follow your "ubuntu installer guide" but still got" VNC connection failed " message due to incorrect key-in data to "androidVNC",can you help to show me how to key in beneath
data in "androidVNC":
Connection: ubuntu:lacalhost:5900
Nickname: ubuntu
password: ?????? (Does ubuntu.img have password ?)
Address: localhost (Do I need to change to 192.168.x.xx ?)
Port: 5900
Username: ???? (what kind username I have to key-in?)
Thanks and looking forward your answers
Click to expand...
Click to collapse
password: ubuntu
address: localhost
port: 5900
and you do not need a username

Thanks for the good work!

Hey, I purchased the premium app and followed the guide to create my own .img, but I removed the old one before extracting the init.sh script of yours, and was hoping you could post a link to it or send it to my email (which I can pm you or email you directly). I tried downloading the img again, 5x infact, but each time the archive was corrupted. Maybe there is something wrong with my connections or something, but that script is all I need anyway.

Valde_Edius said:
Hey, I purchased the premium app and followed the guide to create my own .img, but I removed the old one before extracting the init.sh script of yours, and was hoping you could post a link to it or send it to my email (which I can pm you or email you directly). I tried downloading the img again, 5x infact, but each time the archive was corrupted. Maybe there is something wrong with my connections or something, but that script is all I need anyway.
Click to expand...
Click to collapse
sure just drop me a pm I shall give you the script

problem with file attributes
moved to G S2 Section

Hi
I want to install ubuntu on media-player with android, i'm only intrested in full ubuntu version. But I'm noob and I have got troubles.
MT7002 (similar to ATV2918, MAQ R7, Dayfly GTV574, Unuiga GT U574R, Kimdecent K830, Dealextreme GV-2):
ARM Cortex A8, 1,2 GHz 512k L2 (rk2918)
Android 2.3
512MB DDR2 RAM
2 GB NAND Flash
Android destinaton is 4 GB SD card and this is problem. I have got rooted android 2.3.1 firmware, and I have changed destination of installation applications to SD card, but it still won't download ubuntu from site (to small memory), when I'm using your android application.

[Mod] for (Archidroid Rom) {Pocket Ubuntu 14.10/13.10/13.04} (2014/7/4 Updated)

Archidroid is a excellent&wonderful rom for SGS3,
provides flexible,fast,fancy android environment.
With its built in Pocket Debian,you can use"adflash" to upgrade your Archidroid everyday via OTA from git source, USE "adlinux" to boot into Debian. a lot of useful functions....etc
**This built in chroot brings you more stability than mounting a downloaded img from "complete linux installer"**
But in the rom Devoloping concept, the size of pocket debian is limited to 50MB(in case of being included in a rom) &it is not going to support Pocket Ubuutu
Update log:
2014/07/04 added Ubuntu 14.10 Utopic
*14.04LTS is the first build that promised to long term support on arm architecture*(which brings more stability on everything)
*ubuntu now replace "Upstart" with "Systemd" in 14.10, we can avoid a lot of "upstart error" in chroot with 14.10
*screenshot of the update with 14.10 Mate-Desktop Environment(Now it has arm for 14.10){with Archidroid 2.5.0 stable)
{
"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"
}
Why Pocket Ubuntu?
If you want to install more,more,more,but you found a lot of Repositories are not avaliable for Debian testing(Binary-armhf)(cinnamon,chromium?orphaned?..etc),only for ubuntu
Or....you want to get something from ubuntu-backport,ubuntu mutiverse........or ....Maybe you just prefer ubuntu more than debian?
###we know that simply adding ubuntu repositories to debian causes problems,due to the difference of libraries between two distro###we need a pocket ubuntu:angel:
------------------------------------------------------------------------
so I made my own Pocket Ubuntu by myself, and included a little more ingridients I prefer to replace the built in debian....
The acceptable size for me is 60~100MB,
Features
*All the necessary function in Pocket Debian works(exmple...adflash,vnc,ssh...etc)
*Ubuntu Repository main restricted universe mutiverse
*Ubuntu Utopic 14.10(new added) /Saucy 13.10 /Rariing 13.04 with security updates
*size of current release is 86MB
*you can set your own vnc password at first boot
*Nothing....I just like ubuntu more than debian....AND I PREFER THE CONVIENT "ADLINUX" COMMAND IN Archihdroid
Known Issues
Upstart function dont work! you see [start: Unable to connect to Upstart:.....]
THIS IS NOT A BUG,THIS IS CHROOT'S PROBLEM, Upstart will ever not work in chroot....
there are some ways to hide the error message via command:
Code:
dpkg-divert --local --rename --add /sbin/initctl
ln -s /bin/true /sbin/initctl
but this does not fix the problem but hide the error(I didn't hide the error in this Pocket Ubuntu)
HOW TO USE IT?
simply open a filemanager(need root access),rename the downloaded tar.gz file(ubuntu13.10-archi****.tar.gz) to "debian.tar.gz" and replace
/system/archidroid/system/debian.tar.gz
*note:if you have booted up Pocket debian before you have to run "adlinux clean" again after replacing the original tar.gz
Download:
All versions of pocket ubuntu are all in the same download link:
File names& build versions & last updated date
ubuntu14.10archi-20140704.tar.gz | Ubuntu 14.10 Utopic (2014/07/04)
ubuntu13.10archi-20140223.tar.gz | Ubuntu 13.10 Saucy (2014/02/23)
ubuntu13.04archi-20140223.tar.gz | Ubuntu 13.04 Raring (2014/02/23)
https://www.dropbox.com/sh/by61jvmtxqcptm2/rP6rFFAP1e
BUT OF COURSE:THANKS FOR JUSTARCHI FOR CREATING THIS WONDERFUL ROM!:good::good::good:

download now..
evilhawk00 said:
Archidroid is a excellent&wonderful rom for SGS3,
provides flexible,fast,fancy android environment.
With its built in Pocket Debian,you can use"adflash" to upgrade your Archidroid everyday via OTA from git source, USE "adlinux" to boot into Debian. a lot of useful functions....etc
**This built in chroot brings you more stability than mounting a downloaded img from "complete linux installer"**
But in the rom Devoloping concept, the size of pocket debian is limited to 50MB(in case of being included in a rom) &it is not going to support Pocket Ubuutu
Why Pocket Ubuntu?
If you want to install more,more,more,but you found a lot of Repositories are not avaliable for Debian testing(Binary-armhf)(cinnamon,chromium?orphaned?..etc),only for ubuntu
Or....you want to get something from ubuntu-backport,ubuntu mutiverse........or ....Maybe you just prefer ubuntu more than debian?
###we know that simply adding ubuntu repositories to debian causes problems,due to the difference of libraries between two distro###we need a pocket ubuntu:angel:
------------------------------------------------------------------------
so I made my own Pocket Ubuntu by myself, and included a little more ingridients I prefer to replace the built in debian....
The acceptable size for me is 60~100MB,
*All the necessary function in Pocket Debian works(exmple...adflash,vnc,ssh...etc)
*Ubuntu Repository main restricted universe mutiverse
*Ubuntu Saucy 13.10 /Rariing 13.04 with security updates
*size of current release is 86MB
*Nothing....I nust like ubuntu more than debian....AND I PREFER THE CONVIENT "ADLINUX" COMMAND IN Archihdroid
Known Issues
Upstart function dont work! you see [start: Unable to connect to Upstart:.....]
THIS IS NOT A BUG,THIS IS CHROOT'S PROBLEM, Upstart will ever not work in chroot....
there are some ways to hide the error message via command:
Code:
dpkg-divert --local --rename --add /sbin/initctl
ln -s /bin/true /sbin/initctl
but this does not fix the problem but hide the error(I didn't hide the error in this Pocket Ubuntu)
View attachment 2594296View attachment 2594295
HOW TO USE IT?
simply open a filemanager(need root access),rename the downloaded tar.gz file(ubuntu13.10-archi****.tar.gz) to "debian.tar.gz" and replace
/system/archidroid/system/debian.tar.gz
*note:if you have booted up Pocket debian before you have to run "adlinux clean" again after replacing the original tar.gz
Download:
https://www.dropbox.com/sh/by61jvmtxqcptm2/rP6rFFAP1e
BUT OF COURSE:THANKS FOR JUSTARCHI FOR CREATING THIS WONDERFUL ROM!:good::good::good:
Click to expand...
Click to collapse
give u feed back soon

Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:

install Gui
QUOTE=Niko99ITA;51947564]Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:[/QUOTE]
Originally Posted by*JustArchi*
1. 127.0.0.1:5901 password archidroid.
Remember that before starting VNC you probably want to install some GUI as well, so adlinux default -> debian -> apt-get update -> apt-get install xfce4 (for example)
2. If u successfully installed xfce4 u better run this in terminal:
exec ck-launch-session startxfce4
and for ur sake do a reboot ur phone... and run again adlinux-default or ur choice - vnc and connect again**u then will have a fully working gui*

Didn't notice this thread, nice job .

Niko99ITA said:
Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:
Click to expand...
Click to collapse
Just fellow my steps simply
Hello! To launch the GUI , First you need to install newest desktop environment, I suggest XFCE4 or Mate-Desktop(with 14.04)
when you first boot into Ubuntu, you might set a vnc password
after chroot ,terminal type:
apt-get update
apt-get install mate-desktop-environment or apt-get install xfce4
now you need to restart the vncserver, terminal type:
tightvncserver -kill :1
exit
now chroot back again,terminal type:
adlinux
default
vnc
debian
And now the GUI should already launched in the background.
(*if you finished installing these desktop environments, but tightvncserver can't launch it correctly, you have to edit /root/.vnc/xstartup ,edit the correct command to make it works*)
Second,use any vnc viewer app to connect to 127.0.0.1:5901 with your own password set at first boot
I suggest using Pocketclound Pro as vnc viewer App

evilhawk00 said:
Just fellow my steps simply
Hello! To launch the GUI , First you need to install newest desktop environment, I suggest XFCE4 or Mate-Desktop(with 14.04)
when you first boot into Ubuntu, you might set a vnc password
after chroot ,terminal type:
apt-get update
apt-get install mate-desktop-environment or apt-get install xfce4
now you need to restart the vncserver, terminal type:
tightvncserver -kill :1
exit
now chroot back again,terminal type:
adlinux
default
vnc
debian
And now the GUI should already launched in the background.
(*if you finished installing these desktop environments, but tightvncserver can't launch it correctly, you have to edit /root/.vnc/xstartup ,edit the correct command to make it works*)
Second,use any vnc viewer app to connect to 127.0.0.1:5901 with your own password set at first boot
I suggest using Pocketclound Pro as vnc viewer App
Click to expand...
Click to collapse
Ehi Thanks bro
it workeed
finally developing as well as my pc does with an useful interface :victory:
you have all my respect! Good job :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
AMUK0110 said:
QUOTE=Niko99ITA;51947564]Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:
Click to expand...
Click to collapse
Originally Posted by*JustArchi*
1. 127.0.0.1:5901 password archidroid.
Remember that before starting VNC you probably want to install some GUI as well, so adlinux default -> debian -> apt-get update -> apt-get install xfce4 (for example)
2. If u successfully installed xfce4 u better run this in terminal:
exec ck-launch-session startxfce4
and for ur sake do a reboot ur phone... and run again adlinux-default or ur choice - vnc and connect again**u then will have a fully working gui*[/QUOTE]
Ah,and you also
thanks you two,i appreciate that

Can anyone guide me step by step starting from scratch? (clean install?)
I can't boot it, get lots of errors.
_________________________________________
Edit:
I reinstalled archidroid, at the last step. I have installed mate desktop. Gui doesn't loads up, please help!

eatsleep said:
Can anyone guide me step by step starting from scratch? (clean install?)
I can't boot it, get lots of errors.
_________________________________________
Edit:
I reinstalled archidroid, at the last step. I have installed mate desktop. Gui doesn't loads up, please help!
Click to expand...
Click to collapse
Hello , first of all, make sure u use the newest 14.10 utopic build
After the installation of mate desktop u only need to try the las two steps to fix any error could happen
YOU SHOULD GOOGLE ABOUT HOW TO EDIT XSTARTUP FILE
if you connect via vnc viewer client and found that the gui does not load, this only means the tightvncserver did not execute mate desktop by default
So, you need to edit tightvncserver's settings. This is what you can do, please edit the file /root/.vnc/xstartup and find something like this:
"exec /etc/X11/xinit/xinitrc" this is the default setting....please add # in front of this line
so it becomes "#exec /etc/X11/xinit/xinitrc"
(u can use vim comand "vim /root/.vnc/xstartup" in terminal to edit the file in terminal...)
After disabling the default setting, u now need to add mate desktop as default
please add the line below into /root/.vnc/xstartup
/usr/bin/mate-session&
and this edit means it will excute this binary file"/usr/bin/mate-session&" before starting vnc server....
now save the file and restart
it should work!
DONE!
Cheers

[GUIDE] Installing Archlinux on Asus t100ta and probably other baytrail tablets

I have spent the past month or so dealing with installing Archlinux (my favorite distro) on my t100ta. I have just about everything working (wifi, suspend, audio, touchscreen, battery stats, and I haven't tested Bluetooth but it is apparently supported)
I have posted it on my site HERE but am sharing it here as well.
I might try to make an Archlinux ISO similar in fashion to the Ubuntu Magic Stick that would streamline this process a little bit but finding time to do that around midterms is kinda rough.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Information about archlinux​Arch Linux is a Linux distro that is based on a Keep It Simple Stupid philosophy (KISS). It comes packaged as bare as you can imagine to still be able to provide basic functionality in order to build a system in which you have control over what is installed. It is the distro that I keep finding myself using because I love to keep everything simple and as small as I can. I will walk you through the basic installation steps that I used in order to get Arch installed on my Asus t100.
A note of warning, if you have no understanding of Linux in general, you might want to look here. This is a good solution for Linux on the machine that does not require too much in terms of knowledge.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installing the System​
First some background info. The t100 is a 32bit tablet that comes with a full version of Windows 8.1. It runs Windows pretty good as it contains the atom-based baytrail cpu. The battery is decent and overall use of this machine is a streamlined and remarkable experience.
As you may know, the machine ships with UEFI instead of BIOS. Generally this is not a problem with Linux however, most ISOs you find for a distro that are UEFI compatible are 64bit (x86_64). The 32bit (x86) ISOs are usually not UEFI enabled because it is not the norm to see or use UEFI on 32 bit machines.
In order to skip the building of a custom ArchLinux ISO, I decided to use the Ubuntu Magic-Stick from the guys at Asus T100 Ubuntu. All I needed was to boot into a live session, I could do the rest by the command line. You can alternatively choose to make an ArchLinux ISO but be sure to package it with grub-efi-i386. The tablet will not boot otherwise.
Once you get all the secure boot and bitlocker disabled on windows, you should be able to boot the USB just like any other Linux ISO. You will be greeted with Ubuntu’s familiar Unity desktop and some default applications that might be needed like gparted. You can find info on disabling bitlocker and secure boot here
What I did, since I didn’t have the need for Windows anymore, I erased the entire storage device and decided to install Arch singularly. If you want to do something else, that is okay. 10gb should be good enough to install arch and have plenty of space left over for testing. Here are the steps I did from this point.
I used curl to download the arch-bootstrap image:
Code:
$ curl -O http://mirrors.kernel.org/archlinux/iso/2015.09.01/archlinux-bootstrap-2015.09.01-i686.tar.gz
this will get you a basic setup environment so that you can do the rest from a chroot
Mount the partition you want to install Arch onto somewhere and extract the tar archive.
Code:
$ sudo su
# mount /dev/mmcblk0p4 /mnt/ ##of course, change the 0p4 to the partition you chose
# cd /mnt/
# tar -zxf <path/to/tar>.tar.gz
# mv root.i686/* .
# rm -r root.i686/
Now that we got the everything extracted and moved around to a logical place, we need to edit a few files before we chroot into the installation because the chroot environment does not have a text editor installed.
Code:
# nano etc/pacman.d/mirrorlist
We will need to uncomment a mirror closest to you in order to download packages and install the system.
Its time to chroot and start installing your ArchLinux
Code:
# bin/arch-chroot .
You will notice the bash prompt change, this means you are now in arch
The next few commands will setup the pacman keys so that you can download and isntall packages
Code:
# pacman-key --init
# pacman-key --populate archlinux
Note: This step would not work with me even though the Archwiki advised to install haveged and try several times. I’m impatient so I exited the chroot and edited the etc/pacman.conf again to set the signature to “Never”. You can fix it once Arch is installed and booted.
Click to expand...
Click to collapse
Now we can actually install the base packages and anything else you want.
Code:
# pacman -Syyu #Sync and update packages
# pacman -S base base-devel nano
Everything else is basic for an archlinux install, install the packages, configure the system and install bootloader. You can find all of those directions here.
Installing the bootloader is going to be a little different than usual. You will need to do it basically the same as the archwiki describes (including setting up ESP) however, for the actual command, use:
Code:
# grub-install --target=i386-efi --efi-directory=$esp --bootloader-id=grub --recheck
# grub-mkconfig -o /boot/grub/grub.cfg
Once this is installed, you should be able to reboot to Archlinux
Note: The first time I did this, I was greeted with a kernel panic and it fail to boot. I had to chroot back into the archlinux installation and rebuild the initfs with ‘# mkinitcpio -p linux’ and regenerate the grub.cfg with ‘# grub-mkconfig -o /boot/grub/grub.cfg’ I did not have to do it the second time I installed it so I don’t know if was just a fluke or a necessary step.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Getting Wifi, Battery, and Sound to Work​
Apparently there is a kernel that was compiled by Luka Karinja that has support for Wifi, Battery, and Sound working. It does have battery and backlight working but I had no luck with wifi or sound. You can grab the kernel and test for your liking here: http://bazdara.com/arch (you could put this in your pacman.conf so that you can receive updates upon release)
Wifi: The guys at T100 Ubuntu did some amazing work and got wifi nearly perfect in my experiences. I’ve seen some reports of signal drop which need a reboot to fix but I haven’t had any issues with it.
Download the files from here
Code:
$ wget http://ftp2.halpanet.org/source/_dev/linux-firmware.git/brcm/brcmfmac43241b4-sdio.bin
$ wget https://raw.github.com/jfwells/linux-asus-t100ta/master/nvram/lib/firmware/brcm/brcmfmac43241b4-sdio.txt
Move the files into the proper directory
Code:
$ sudo cp brcmfmac43241b4-sdio.bin /lib/firmware/brcm/
$ sudo cp brcmfmac43241b4-sdio.txt /lib/firmware/brcm/
Open the .txt and remove all the characters before ‘#’ in the very fist line.
Code:
$ sudo nano /lib/firmware/brcm/brcmfmac43241b4-sdio.txt
Rebuild the initfs
Code:
$ sudo mkinitcpio -p linux
Rebuild grub config
Code:
$ sudo grub-mkconfig -o /boot/grub/grub.cfg
Sound: One of the guys at Asus T100 Ubuntu, Kirill Belyaev, posted a sound fix that works exceptional for me. You can find the post here
Download the firmware and the t100_B.state from the “new ####” folder here
Extract the archive into the /lib/firmware/intel/ directory
Code:
$ sudo tar zxf linux-firmware-master-intel.tar.gz -C /lib/firmware/intel
Move the .state into the /var/lib/alsa dir as asound.state
Code:
$ sudo cp t100_B.state /var/lib/alsa/asound.state
Reload the alsa configuration
Code:
$ sudo alsactl --file /var/lib/alsa/asound.state restore
Reboot and enjoy WiFi and sound working. It should be noted that even though everything should be good at this point, you may have to change some of the configuration for status information.
The battery information is found at: /sys/class/power_supply/BATC
The backlight (if using t100 kernel from bazdara) is at: /sys/class/backlight/intel_backlight
The volume is not the usual MASTER. Is is the ‘Speaker’ control.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Final Thoughts and Information​
While this installation is not perfect by any means, It is perfectly usable. There is a chance for a random freeze of the kernel however, since I have started to use the T100 kernel, I’ve not had any. So many thanks to the person that compiled it.
I use awesomeWM on this install because I use mine as a laptop for school. I would recommend XFCE for anyone that wants a more robust desktop environment because it is light enough to work great on this tablet. It also detects the audio, battery, and backlight automatically. The choice is yours just be sure to configure it correctly.
Join #t100-linux on freenode for any questions or if you need help installing. If Im active I will walk you through it.
I would like to say thanks to a few communities and people for helping me get Archlinux on this machine in a mostly stable state.
The Asus T100 Ubuntu community for the LiveUSB and configuration files: Google+ Page
Linux North for information about all the test he had ran. Also information for disabling bitlocker and secureboot. LinuxNorth Page
Archlinux Forum thread with a few tips and tricks like the T100 kernel. Thread
User LambdaComplex in #archlinux and #manjaro on freenode for support and ideas.

Hello again! So you did make a thread about this.. I'm going to try this!
Thanks
edit: Is there any different about the guide between here and on ur website?

hello again, I realize that you use all the ssd for arch? will it be possible to use the drive on keyboard for arch? I'm on unencrypting process right now. free space on ssd is only 10gb now
so on yours, you can use arch with tablet mode? (screen detached)

dokie80 said:
hello again, I realize that you use all the ssd for arch? will it be possible to use the drive on keyboard for arch? I'm on unencrypting process right now. free space on ssd is only 10gb now
so on yours, you can use arch with tablet mode? (screen detached)
Click to expand...
Click to collapse
Sorry apparently I didn't have notifications enabled on this. There shouldn't be a problem using the keyboard drive for this. Just define the partition correctly.
Also, this guide is the same on my site. I am just trying to share with people like me who like other distros more than Ubuntu

@dodgejcr ur guide is to install 32-bit of, right?
i686 means 32bit?
Can I use magic stick to install arch 64 bit?
I'm stuck on entering Choot,
Code:
chroot: failed to run command '/bin/sh' : Exec format error
Research says that that error normally happen when using different type of architecture
Sent from my Nexus 5 using Tapatalk

@dodgejcr Your guide is mentioned on xda development article and Google plus. Congrats
Sent from my Nexus 5 using Tapatalk

dokie80 said:
@dodgejcr ur guide is to install 32-bit of, right?
i686 means 32bit?
Can I use magic stick to install arch 64 bit?
I'm stuck on entering Choot,
Code:
chroot: failed to run command '/bin/sh' : Exec format error
Research says that that error normally happen when using different type of architecture
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah this is 32bit. Are you sure you are doing the chroot process correctly? you are wanting to call the /bin/arch-chroot binary from your mount point (/mnt).
For example, to chroot from / on ubuntu you will want to use:
Code:
# /mnt/bin/arch-chroot /mnt/
To chroot into the arch partition.
If you need help, You can usually find me in #manjaro on freenode
dokie80 said:
@dodgejcr Your guide is mentioned on xda development article and Google plus. Congrats
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Interesting, got links for this?

@dodgejcr quite sure, but i will try again later when I have the time.
link to g+ : https://plus.google.com/+xda/posts/NvPzTa3GYhy
link to xda - http://www.xda-developers.com/xda-external-link/install-archlinux-on-asus-t100ta-tablet/

Thanks for the post dodge! I'll have to try this as I've been frustrated that only Ubuntu is available for the T100. Also, didn't think I'd ever see your username again, after abandoning the Moment

HA! that was a looonnnnnggggg time ago. Good to see other people here from way back in the day.

dokie80 said:
@dodgejcr quite sure, but i will try again later when I have the time.
link to g+ : https://plus.google.com/+xda/posts/NvPzTa3GYhy
link to xda - http://www.xda-developers.com/xda-external-link/install-archlinux-on-asus-t100ta-tablet/
Click to expand...
Click to collapse
Very interesting, thanks for letting me know this info is being spread. I just did it for my own benefit and a few people said to share it.
Well, if you cant get it next time hop on to that irc channel, hopefully you can catch me in-between school and family time. Ill be glad to walk you through it

Appreciate it. But tell me, do u mind if I just post it here, or you prefer to be contacted via irc? It's probably better to post here for others reference. Unless you actually prefer to be contacted via irc
Sent from my Nexus 5 using Tapatalk

{
"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"
}
Still got the error. I probably just install 32bit version
Sent from my Nexus 5 using Tapatalk

dokie80 said:
View attachment 3519137
Still got the error. I probably just install 32bit version
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That is my fault, I didn't realize you were attempting to install 64bit archlinux from your previous post (I dont always read properly ) I would just stick with 32bit as there is no actual benefit of running 64bit on this machine.
It is possible to get it to work through emulation of a 64bit host system but the amount of work necessary does not outweigh the benefits. Do a quick google search about chrooting across archetecture for some more info.
Also, I dont mind if you post here at all. I just have alot of thing going on so I can't promise you that I will be super attenative to this thread all the time.

Have you had any issues with the T100 specific kernel? I was able to used sound and wifi with the standard kernel from testing, but when I tried the T100 dev kernel the tablet doesn't even boot. Really would like that backlight

4512jth said:
Have you had any issues with the T100 specific kernel? I was able to used sound and wifi with the standard kernel from testing, but when I tried the T100 dev kernel the tablet doesn't even boot. Really would like that backlight
Click to expand...
Click to collapse
Funny you should ask, I literally just tried the latest and it didnt boot either. I went back to using 4.3rc3 which was the most stable for me.
I havent tried the bazdara stable kernel but I can tell you 4.2 t100 and 4.1 t100 worked for me during all my testing

Note: This step would not work with me even though the Archwiki advised to install haveged and try several times. I’m impatient so I exited the chroot and edited the etc/pacman.conf again to set the signature to “Never”. You can fix it once Arch is installed and booted.
Click to expand...
Click to collapse
which step did you mean about this?

That was the pacman keyring, it can be disabled to install and re-enabled once you get it booted.

Hiya Dodge! haha. I'm about to attempt this on my Atom Tablet (the Quantum Suppliers Quantum View). I'll post here if I have any issues.

Shiggity said:
Hiya Dodge! haha. I'm about to attempt this on my Atom Tablet (the Quantum Suppliers Quantum View). I'll post here if I have any issues.
Click to expand...
Click to collapse
Most definitely. Id like a to know how many baytrails can run archlinux.
I wouldnt recommend the t100 kernel for you. Its made with patches for the t100 specifically but the default i686 kernel should get you booted. The rest can be figured out upon configuration. Good luck

[Guide] Build Your Own [UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

In the spirit of open-source, if there's one ROM that deserves to be "home-brewed" in addition to AOSP and Lineage, it's LineageOS4Microg. This guide will explain how to do so using Docker. LineageOS and Microg are explained below followed by the guide.
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Known issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Building Requirements
1. A fast PC or VPS account such as Google Compute Engine. Minimum PC recommended requirements are Intel i5 or equivalent, 4 cores 8 threads minimum (more cores and better CPU recommended), 16GB ram, SSD and 300GB free drive space minimum, fast internet connection (you will download over 30GB of sources).
2. Ubuntu 18.04 is supported here. If you use Windows or another version of Linux, let others know of your tweaks and workarounds.
3. Patience and time. Downloading sources, setting up and building a rom will take hours if not days (depending on your PC hardware and internet speed).
Environment Setup & Build​1. Install Docker on Ubuntu (run each command once in terminal)
Code:
sudo apt-get update
sudo apt install docker.io
sudo systemctl start docker
sudo systemctl enable docker
2. Test that docker is running (run command in terminal)
Code:
docker run hello-world
You should see something like this, "docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world ca4f61b1923c: Pull complete Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. ..."
3. Pull lineageos4microg docker onto your pc (run command in terminal)
Code:
docker pull lineageos4microg/docker-lineage-cicd
4. After pull is complete, create the following directories in your home/YOURUSERNAME directory
lineageos4microg
lineageos4microg/src
lineageos4microg/ccache
lineageos4microg/local_manifests
lineageos4microg/keys
lineageos4microg/logs
lineageos4microg/zips
So it might look something like this: home/JoeAndroid/lineageos4microg
5. Copy the 4 attached xml files (bottom of this post) to your local_manifests folder
These are: ocean.xml, include_proprietary.xml, proprietary.xml, and custom_packages.xml
6. In terminal, cd into the lineage4microg folder, and copy and paste the following commands all at once after changing YOURUSERNAME to your username in ubuntu. For an explanation of options, see the link at bottom of post. This code will download sources, sync your repos with newest updates and start your build. This step could take hours. It is downloading sources, syncing repos and building your rom!
Code:
sudo docker run \
-e "BRANCH_NAME=lineage-16.0" \
-e "DEVICE_LIST=ocean" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension " \
-e "INCLUDE_PROPRIETARY=false" \
-v "/home/YOURUSERNAME/lineageos4microg/lineage:/srv/src" \
-v "/home/YOURUSERNAME/lineageos4microg/zips:/srv/zips" \
-v "/home/YOURUSERNAME/lineageos4microg/logs:/srv/logs" \
-v "/home/YOURUSERNAME/lineageos4microg/cache:/srv/ccache" \
-v "/home/YOURUSERNAME/lineageos4microg/keys:/srv/keys" \
-v "/home/YOURUSERNAME/lineageos4microg/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
7. Your build should be in the zips folder when complete! Flash in twrp/ofox.
8. If your build fails, check the log in lineageos4microg/logs/ocean folder. If you receive the following error, "Can not locate config makefile for product "lineage_ocean"" you will need to copy the 4 xmls from lineageos4microg/local_manifests to lineageos4microg/manifests.​
References and links:
https://phoenixnap.com/kb/how-to-install-docker-on-ubuntu-18-04
https://github.com/lineageos4microg/docker-lineage-cicd
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Thanks to Dark98, Electimon, Barry and many others for initial help and repos when building this rom.

Reserved #1

Reserved #2

Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?

skalnas said:
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
Click to expand...
Click to collapse
Can you take a picture of the screenshot including how you typed in the commands? Need a bit more info

I just pasted the code changing username screenshot attached

skalnas said:
I just pasted the code changing username screenshot attached
Click to expand...
Click to collapse
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?

Bernie_nix said:
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Click to expand...
Click to collapse
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.

skalnas said:
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
Click to expand...
Click to collapse
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script

Bernie_nix said:
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Click to expand...
Click to collapse
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again

skalnas said:
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
Click to expand...
Click to collapse
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.

Bernie_nix said:
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Click to expand...
Click to collapse
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks

skalnas said:
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
Click to expand...
Click to collapse
Awww... Well I had that happen before. Even if you have an old platter hdd (not ssd) as long as it's got the GBs of space it will take a little longer to build but for these purposes will do just fine. I use both SSD and hdds to build.

Got my dual boot set up. First tried Ubuntu but it kept locking up, went with Linux mint. Got a 250 GB partition, going to give it another go tommorow.

View attachment 4980819well, after switching from VM to dual boot, I gave it another go, and i got a msg in linux mint that i ran out of space about 3 1/2 hrs into build. I had set up 250gb partition as you suggested. I did 30gb root, 220 GB home,4 GB swap.
Can you take a look at the logs, i'm not clear looking at logs how much of build completed.
There was the zip file about 604 mb in the zips folder, which I could open(along with an sha and md5 files, which i dont know anything about.) I'm thinking possibly the build completed despite the warning in linux about running of free space.
I shrank the /root partition in gparted to 20gb and tried to extend the extra 10gb to home, but i couldn't.
Is it possible to specify 25gb ccache in the docker script somehow so that instead of the 50 it seems to allocate, maybe that will solve the space issue?
Thanks again, looks like progress.

Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?

skalnas said:
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
Click to expand...
Click to collapse
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
boot.img already exists, no need to overwrite...
dtbo.img already exists, no need to overwrite...
system.img already exists, no need to overwrite...
vendor.img already exists, no need to overwrite...
Total of 704512 4096-byte output blocks in 23 input chunks.
Total of 147456 4096-byte output blocks in 13 input chunks.
done.
Click to expand...
Click to collapse
Where is "Missing "vendor/lineage", aborting." appearing?

Bernie_nix said:
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
Where is "Missing "vendor/lineage", aborting." appearing?
Click to expand...
Click to collapse
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.

skalnas said:
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
Click to expand...
Click to collapse
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?

Bernie_nix said:
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Click to expand...
Click to collapse
The zip was 604mb, i did successfully flash it, thanks again for your help and guide building my first rom!
so the xml file should be edited to:
<project name="bernie-nix/android_device_motorola_sdm632-common-1" path="device/motorola/sdm632-common" remote="github"/>
?
btw, i don't see your repos on github anymore.