So, I've worked a little bit with sztupy's creation from here:
http://forum.xda-developers.com/showthread.php?t=817387
and I decided to tweak/improve it a bit.
Included:
-ssh
-samba to access files on Debian from the Windows host
-Eclipse IDE to work nice with the linux Kernel
Check the screenshot to get an ideea on how it looks on Eclipse IDE.
Please take note that all the fuss is to get a nice looking with nice features IDE working on windows (but should not be a problem for someone on linux to follow my tutorial).
This is not intended to compile the kernel right from the Eclipse IDE, be it installed on Windows or Linux.
However, with some nicely crafted ssh commands you can tunnel some "make" command over ssh and trigger the compiler on the guest os.
The best stuff of this is that on Windows you get nice software like Beyond & Compare to compare/diff/join source code from different repos/kernels.
Also, something nice on Eclipse is that you can see the defines grayed out if those are not declared, also you can jump easily from a variable to its definition/declaration, etc.
ssh, samba, alter configuration for virtualbox
First thing first, the connection to the VM box over ssh (putty) can easily be achieved following the steps described here:
http://forum.xda-developers.com/showpost.php?p=8868634&postcount=54
###########################################################
Let's continue with setting up some sort of file sharing between host and guest.
Note: to make things easy, login as root.
Now, we can ssh nicely into guest OS, so what about sharing?
Well, we can share files over "Shared folders" feature, but this sucks cause we can't see symlinks in Windows.
So, the best choice would be to install Samba.
Note: People might get better speeds if instead of Samba would try NFS, but tbh, I wasn't able to get a damn working NFS client on Windows.
So, for now, Samba FTW!
Code:
apt-get install samba smbfs
You need to configure the samba share to be able to see it inside the Windows host machine.
edit /etc/samba/smb.conf in your favorite editor and add the following lines:
inside [global] section you should have something like:
Code:
[global]
workgroup = kernelcompiler
security = user
browseable = yes
guest ok = yes
guest only = no
encrypt password = yes
then add a new section, called [kernel-compiler]:
Code:
[kernel-compiler]
#in order to make the files touched on windows not executables add map archive = no
map archive = no
path=/home/kernel
read only = no
writable = yes
browseable = yes
public = no
valid users = kernel
restart the samba daemon:
Code:
/etc/init.d/samba restart
###########################################################
Great, now shut down the Guest (I think the previous restart was not necesary).
On Virtual Box window, all VMs stoped, select File > Preferences.
On the network tab, add a new Host Only network (you can reuse the existing one if you wish and you understand what are you doing).
Alter settings, the IP should be something like: 192.168.134.1 and mask: 255.255.255.0
Disable DHCP server.
Ok. Ok.
The new network interface should be installed.
Right click on the Debian machine, Settings > Network.
On the tab Adapter 2, check Enable Network Adapter, Host Only Adapter, select (the Name field) the network card that we created above and click ok.
The first interface (Adapter 1) NAT is for internet access of the guest os.
The second interface (Adapter 2) Host Only is for communication between guest os and host os. You need that to be able to access Samba. If I think a little that could be used to access also the ssh port...
###########################################################
If we have something left to do is to configure the network settings inside the guest os.
Start virtual box.
Note: Inside /etc/udev/rules.d/ there is a file like: 70-persistent-net.rules Just delete this file if you run into problems while configuring the network interfaces inside guest os.
To enable the second interface (Host Only) do something like:
Code:
ifconfig eth1 192.168.134.1 netmask 255.255.255.0 up
Also, do your stuff (I assume you kinda know how to config the linux box) inside the file:
/etc/network/interfaces
Reboot.
###########################################################
Now you should be able to map the /home/kernel folder in Windows to something like Z: drive.
Ask for help if you don't understand/run into troubles.
Eclipse IDE on Windows
Install Eclipse CDT. Google for it. Chose your Windows/Linux version and install it.
Inside Eclipse installation folder there is a file, eclipse.ini.
Edit it and change the last line (regarding memory) to something like -Xmx768m.
Reason: You need some memory, the linux kernel is kinda big, in order to get comfortable we need to change the default settings.
Note: To run Eclipse, you need Java SDK. Google for it, find it, install it if you don't have Java SDK.
0.###########################################################
Start Eclipse.
New project.
Select a C project. Give it a name. Example: sgs_kernel.
Project type: Makefile project -> Empty Project
Toolchain: --Other Toolchain --
(check screenshot 1)
Note: You can change the location of the folder, you can work with the default one, just don't create the project in the same folder where you have the linux kernel sourcecode.
1.###########################################################
Next
Advanced Settings
In the Properties window that was opened, go on the C/C++ General branch, expand it, Indexer.
Check Enable project specific settings
Uncheck Enable Indexer. I repeat, you have to uncheck in order to disable the indexer.
Apply
Ok
(check screenshot 2)
2.###########################################################
In the Project Explorer select your project (sgs_kernel), right click, New > Folder
Click on Advanced then Link to alternate location (Linked Folder)
Browse and select the root of the kernel of your choice. (you have a kernel folder already, right? If not, check sztupy post regarding git commands to retrieve your own kernel source code)
Finish
(check screenshot 3)
Reason: By linking to alternate location you keep the mess out, the project settings stays on your windows machine, the kernel files remains on the linux machine.
3.###########################################################
Get a cofee. Adding all the files to the project over Samba should take some time.
###########################################################
When it is done, expand the source code tree, inside arch folder select everything except arm folder and right click Resource configuration and then Exclude from Build....
In the new window, check Default, then OK.
The same should be done in the arm folder, so, expand the arm folder and there select all folders starting with "mach-", except mach-s5pv210 which is the platform for our Galaxy S, and we dont want that one to be excluded.
Again right click Resource configuration and then Exclude from Build....
(check screenshot 4)
4.###########################################################
Right click on the project (sgs_kernel) and expand C/C++ General > Paths and Symbols.
On the Symbol tab click on Add... button, check Add to all languages and add the symbol with the name: __KERNEL__ and Value: 1.
(check screenshot 5)
5. ###########################################################
Now the hard part.
To push Eclipse to the limits, we have to add the defines from the include/linux/autoconf.h.
There are several ways to do that, I'm still looking for better ways to do that, but for now the ideea is to use a script that parse the file autoconf.h and extract the defines and push those inside our project.
The script I'm talking about is a python script (yeah, that sucks, something else to install on our kitchen.
Code:
sudo apt-get install python
Note: The python script is attached in this post.
Copy the script autoconf-to-eclipse.py somewhere, example: /home/kernel
Also copy/create a new sh script that will call the python script above, using a syntax like:
Code:
#!/bin/sh
python autoconf-to-eclipse.py /home/kernel/voodoo/linux_gt-i9000/Kernel/include/linux/autoconf.h /home/kernel/voodoo/linux_gt-i9000.eclipse/
The first parameter is the path to the autoconf.h file, the second is the path where you should copy your eclipse project file (that would be the .cproject file).
So you have to copy over the .cproject file from the Windows host project folder C:\Users\XXXXXXX\workspace\sgs_kernel to the linux box to a folder like: /home/kernel/voodoo/linux_gt-i9000.eclipse/
You have samba, right?
Then on the linux guest, run the sh script, that will run the python script.
If everything is ok, then the .cproject file should be much bigger (the defines were imported).
Note: you have to do this step each time you alter the configuration, like running "make menuconfig".
Copy the file back on windows to the project folder and inside eclipse, right click on project folder and hit Refresh.
Wait...
To check everything is ok, right click, Properties, expand C/C++ Projects > Paths and Symbols, Symbols tabs... and there you should have all defines.
(check screenshot 6)
6. ###########################################################
Switch to the Includes Tab in the same branch C/C++ Projects > Paths and Symbols.
Add include folder. Check Add to all languages.
Add arch/arm/mach-s5pv210 folder. Check Add to all languages.
(check screenshot 7)
Apply.
Ok.
END. ###########################################################
Finally.
Right click > Properties > branch C/C++ Projects > Indexer.
Check Enable Indexer.
Ok.
Get a RedBull, it should take a while.
###########################################################
Start coding!
Ask for help if you don't understand/run into troubles.
Credits: Inspiration from here -> http://www.nazgee.eu/en/book/forcing-eclipse-to-work-with-linux-kernel-indexing-kernel-source
awsome work man . thanks to you and sztupy !
This thread is kicked to the front page
Sent from my GT-I9000 using XDA App
ragin said:
This thread is kicked to the front page
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Kicked again.
Thanks! This pretty much still works for the Gingerbread source except that the autoconf.h is now in include/generated/autoconf.h.
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.
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
{
"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"
}
Clean | Stable | Flexible | Optimized | Excellent
-> ArchiDroid 2.X <-
A Port of JustArchis Rom to our S1
Changelog
ArchiDroid 2.5.2
- Added additional r_submix audio module, idea thanks to @nelsonw # This should help with chromecast
- Updated PA GAPPS to 25 July
- Updated Nova Launcher to 3.0.2
- Updated Google Keyboard
- Updated XPrivacy to 2.2.2
- Updated Onandroid to 9.51
- Updated cm and ArchDroid sources (31.07.14)
Download
All Files Mediafire
Stable: ArchiDroid 2.4.5 Mediafire
Experimental: ArchiDroid 2.5.2 Dev-Host, Mirror: Mediafire
Remember that you don't need anything else to flash. Google Apps are included already.
Known Issues
All known and unknown Cyanogen Rom bugs (if any)
INSTALLATION INSTRUCTIONS
- Download the latest build of ArchiDroid ROM
1.- Wipe data / factory reset (mandatory if you coming from STOCK OR 4.2.X version or any other ROM)
2.- Install the Main ROM via Aroma installer, make your choices and lean back.
3.- Reboot
Attention: first boot will last a couple of minutes, at least almost 5 minutes or a few more. So after flashing take a rest and drink a coffee or a beer !
And after rom has booted up, led it settle a bit, till all apps and settings are initialised!
UPDATE INSTRUCTIONS
- Download the latest build of ArchiDroid ROM
- Take a nandroid backup
- Flash ROM using recovery and aroma installer
- Reboot
- Enjoy!
Known Bugs
-tethering is not working proper fixed in v2.5.0
In Aroma Installer you can select for example:
- 3 different Kernels: Stock, Neo and Mackay
- different Launchers
- different Keyboards
- different Bootanimations
- many additional apps
- to add nav bar
- to select: ro.config.low_ram=true or ro.config.low_ram=false (transparent statusbar)
and many other things
Follow ArchiDroid On XDA!
Write A Review!
Rate This Thread!
Buy JustArchi a Beer!
Like ArchiDroid On Facebook!
Hit Thanks!
XDA:DevDB Information
[ROM] [4.4.4. - KTU84P] [OmniROM] [Linaro 4.7] [Experimental] [Flexible] [Excellent] [01/08/14] ArchiDroid V2.5.2 | Power In Your Hands, a ROM for the Samsung Galaxy S1 I9000
This Rom is an official kanging of i9300 thread by @JustArchi lead developer and author of ArchiDroid ®. So all credits and thanks goes to JustArchi!!
Contributors
rodman01
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenROM / ArchiDroid / SelfKANG
Version Information
Status: Experimental 4.4.4 v
Created 2014-04-23
Last Updated 2014-08-01
[SIZE="+3"]ArchiDroid's FAQ / Q&A Section for i9300[/SIZE][SIZE="+1"]There is a special thread in the SIII section with and for FAQs. If you are interested in, I am sure there are good infos about the rom, for everybody and also related to our S1.[/SIZE]
[SIZE="+1"]Features / Why ArchiDroid?[/SIZE]
First of all, ArchiDroid includes everything available in it's base. The whole point of ArchiDroid is to improve the base, without needing of making any trade-offs, so by flashing ArchiDroid, you're getting everything offered by the base itself. There's nothing to lose, everything to gain.
You can read detailed information about every ArchiDroid component here. It's a massive wall of text, so I'm only going to list the core features without describing them.
These were written from scratch, they're completely unique and you won't find exactly the same implementation in any other ROM.
ArchiDroid-Unique features:
- ArchiDroid's AROMA Installer
- ArchiDroid's Pocket Debian
- ArchiDroid's Flasher
- ArchiDroid's RunOnce
- ArchiDroid's Init
- ArchiDroid's Backend Control
- ArchiDroid's HArdware Volatile Entropy Gathering and Expansion Daemon (Haveged)
- ArchiDroid's Fast Random Number Generator (Frandom)
- ArchiDroid's Adblock (dnsmasq/dnrd, dnsproxy2, pixelserv)
- ArchiDroid's Forced Update
Apart from that, here, on the credits page, you can find all third-party projects, which have been implemented into ArchiDroid. In addition to that, it's up to YOU to decide if you want to install something, or not.
ArchiDroid focuses on flexibility and user choice.
If you're looking for fastest ROM, choose ArchiDroid.
If you're looking for most battery-saving ROM, choose ArchiDroid
If you're looking for cutting-edge functions, choose ArchiDroid
If you're looking for the most flexible rom ever created, definitely choose ArchiDroid
ArchiDroid adjusts to your needs. You can make it whatever you want. With bunch of presets, modes and questions, you can make your ArchiDroid behave. Check yourself why ArchiDroid is The TOP 1 ROM for Galaxy S3http://forum.xda-developers.com/galaxy-s3#romList, according to number of followers, rates, reviews and downloads count. Check the Reviews, take a look at Video Reviews, do whatever you want to, ArchiDroid is proven to be one of the best ROMs for Galaxy S3, ever created.
Try ArchiDroid once, and you'll never look back. I can assure you.
Disclaimer
Developer's Kitchen
Unless stated otherwise, all ArchiDroid components are licensed under the Apache License:
Code:
Copyright 2014 [email protected]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Especially:
ArchiDroid is one of the most complex ROMs ever created. When you start digging in my work, you can very easily get lost. And I'm not talking about base itself, but about everything next to it. You can use every part of my work, as long as:
1. You include proper credit where you should. This usually includes proper comment in a script/file and in the credits of the project, including license (if needed)
2. You let me know about this fact. Through PM on xda or e-mail
I'm always happy to help, especially with the problems I faced in the past. However I also want to be respected, considering that most of the ArchiDroid parts were written from scratch.
ArchiDroid 2.X vs. ArchiDroid 1.X
The long battle between choosing over ArchiDroid 2.X and 1.X is still recent. There's no one real and true answer to this. It's up to YOU to decide who wins this battle, because obviously every user is different. I'm only going to give you some tips and briefly describe differences.
Despite the name, ArchiDroid 2.X and 1.X are totally different ROMs. It all started with ArchiDroid 1.X, a ROM based on Sammy's stock firmware, with all needed goodies and features baked in. Then eventually I managed to implement everything what I ever wanted to implement, therefore making ArchiDroid 1.X more or less complete. Then I started with ArchiDroid 2.X project, built from scratch from AOSP sources, with all source codes available.
The point is, ArchiDroid 1.X is more or less complete, there's no "real" development going on, as I obviously don't have samsung sources to begin fun with. On the other hand, ArchiDroid 2.X will never be finished, there's always something to improve, something to add, something to fix... This is ongoing process, which will reach the end when I finally break my SGS3 or change the phone to another one .
If you're new user or you don't know how AOSP works on our SGS3s then I highly suggest to flash ArchiDroid 1.X firstly. ArchiDroid 2.X is targeted at advanced users, who don't mind some "core" features being broken. It will NEVER be as stable as ArchiDroid 1.X is, so if stability is the number 1 for you, choose 1.X.
ArchiDroid comparision
From 1-10, based on my own point of view
Stability
2.X - 5
1.X - 8
Compatibility
2.X - 4
1.X - 9
Battery
2.X - 6
1.X - 9
Performance
2.X - 9
1.X - 6
Features
2.X - 9
1.X - 4
Android Updates
2.X - 9
1.X - 6
-----------
Overall
2.X - 42
1.X - 42
This is ArchiDroid comparision in a nutshell. If you ask me, I think that ArchiDroid 1.X is far better choice for daily driver, but if you're advanced user and you know how to deal with possible broken functions then you can have great time using ArchiDroid 2.X as well.
Remember that only ArchiDroid 1.X supports Samsungs-specific features, such as Smart Stay, Screen mirroring, Allshare or whatever. This also includes closed-source proprietary drivers, such as many bluetooth headsets, which won't work under open-source AOSP. Think twice before considering 2.X if you're addicted to these Samsung goodies.
On the other hand, ArchiDroid 2.X is the only ArchiDroid with "real" development going on, however all universal changes are also backported back to ArchiDroid 1.X, so you're not missing any feature, which benefits also Sammy's base.
That's it. I hope that a choice between both of these awesome roms is a bit easier now. If you still can't decide I suggest to flash both of them for some time and then decide which suits you better.
Know Your ArchiDroid
ArchiDroid is not only a rom. It's not only a baked android with third-party apps, modifications and tweaks. ArchiDroid is an universal backend which improves rom by many built-in functions.
Let me tell you a story. During developing first version of ArchiDroid 2.0 I experienced many problems, which were not that easy to solve. First of all - apps data. Trust me or not but you can't simply extract data, put it in /data/data after install and hope that it works. Android will detect such injection, report inconsistent of data and wipe everything attached to that. Okay so... How I should provide you with my boeffla preset? CoolTool settings? STweaks profile? If I put my data during flashing it'll get wiped. If I put my data and deny wiping it then Android will report inconsistent of data to user and work unstable. Yes guys, it's impossible to do so without a trick or without recompiling whole rom.
I won't tell you a whole story, because you probably don't want to hear about ArchiDroid development. I'll simply tell you that I overcome MANY difficulties, simply because I do what I like, and I like what I do. After countless number of hours, I can finally provide you with the ROM, which is the best. Why is it the best? Because I'm improving the base, and I'm not making any trade-offs.
Video Reviews / How ArchiDroid looks like?
@Koogly
@SkywalkerZ
ArchiDroid User Signatures
ArchiDroid Features
Know your ArchiDroid, learn how to use it
Introduction / Basics
Welcome to ArchiDroid's world mortal. In this tutorial we will show you what ArchiDroid has "inside" and what it really offers. All of things included in this post are ArchiDroid-specific, which means that you won't find any ROM with the same features, as they're written from scratch.
Here you can find some definitions of the words used in sections below. You should know most of them, but in case somebody is lost here you can get back on track.
Terminal, Shell - Typical android shell, which may be obtained in three ways.
1. Through native Android Debug Bridge (ADB) with command "adb shell" from the PC or even "ADB through network" (if supported).
2. Through any Android terminal app, f.e. Android Terminal Emulator bundled with ArchiDroid.
3. Through secure shell daemon (sshd), which needs to be turned on firstly. This is extremely useful in terms of pocket debian, which will be described later.
You can use any of these methods to access android's terminal, however usually Android Terminal Emulator will be the easiest one, as it's android app bundled with ArchiDroid. WARNING! Most of the commands below WILL require root access. You can log in to super user shell by "su" command right after obtaining shell. If you're unsure if you're logged as root or not, "whoami" command should print actual user, "root" or "unknown uid 0" are OK, others are not.
ArchiDroid's Pocket Debian
From wikipedia:
From debian site:
How exactly this covers our beloved SGS3 (and countless number of other android arm-based phones)?
As you may (or even should!) know, Android operates on it's own Linux-based kernel. Android's kernel is literally a fork of Linux kernel, with a few special/unique functions which are required, mostly hardware-specific. Because of that kernel itself is VERY compatible with everything based on Linux.
However there have always existed one typical problem, lack of proper environment. We have a great kernel, great power, linux-based android environment, but this environment lacks of very common and required libraries/binaries. If you ever wondered what is or what does busybox, this is the answer. Busybox is just a small package which offers a few standalone GNU/Linux binaries, which are required to make certain things work. For example, swap priorities. Android knows what swap is, and nothing else. It doesn't know that swap could have a priority, so if you use android's swapon command on 4 devices, it will firstly fill first device, and then proceed to the next. That's why we need busybox in ALL custom kernels, because android environment isn't enough.
However busybox sometimes isn't enough. If we focus only on Android itself, it is. But if you for example want to run stricly linux-based service, I don't know, a web server for example... Is it possible to run a native linux web server on an android? No, it's not. You should firstly compile such service on arm architecture, including all dynamic and static libraries (wrrr ) in it only to finally get mad because of missing libraries or other dependencies. Of course if you're patient you'd finally compile everything and set up, however how long would it take? A few days maybe? If you're skilled in what you're doing...
This is why I included built-in "pocket" debian in ArchiDroid. It's FULLY compatible with everything compiled/based on armhf/armel GNU/Linux architecture, for example Raspberry Pi. With two easy commands you can literally jump into debian environment and use every typical GNU/Linux utilities known from debian itself. Of course this means nothing for most of the users, because they'll never have any reason to use such debian environment but from the developer side, it's big step forward. The best example is with github. As you know ArchiDroid has it's own repo on github, from where you can download/manage stuff. There also exists git app for linux and windows. If you want to follow "expert" way of flashing experimental ArchiDroid version, such program is required. The scenario is the same as compiling web server for an android, it requires much more effort than it's worth. And even then you can end up with syncing external dependencies and searching for solutions for the problems you've never seen before... And with ArchiDroid's pocket debian? It's as simple as in any debian/ubuntu distro. "apt-get update && apt-get install git" and voila. Your git is installed and ready for work. Going further I've even included git in pocket debian itself. Okay, I have debian, I have git, and what next? With git utility I can for example provide you with delta updates for ArchiDroid! ArchiDroid can easily use pocket debian to set up and sync ArchiDroid's repository and then pack and flash latest version without even needing of a PC, using 7-zip or anything else. Another example? A web server. I know that it's very dev-specific but if you for any reason need a web server running, just for example to test simple website, you can have it with just one command. Going further, VNC? MySQL server? PHP? Python? Perl? Ruby? Maybe conditional tasks with cron? Persistent minimal IRC client? rtorrent with rutorrent GUI over WWW? The list goes on... Anything based on linux will work. You can even host a server for your favourite game, as long as it has armhf/armel binaries (unfortunately most of the games don't).
So that's it. In short, debian is an operating system built-in in ArchiDroid to provide you with (unfortunately missing) GNU/Linux environment, with full power, ready to handle anything you could request. I made my best to include fully working debian in ArchiDroid for a minimal cost. Whole OS is packed in one big tar file, compressed using highest bzip2. As for now pocket debian has ONLY 40 megabytes of size, maybe in future it will have up to 50 megabytes, but no more. It's a VERY small cost for having such great power, especially if you know how to use it.
This is a really cutting-edge feature, mostly because I have no limitiations what I can include in my ROM right now, and while other developers are dealing with OpenDelta updates and many Android-based problems, I'm just launching my pocket debian and manages linux stuff.
I'm SURE that most of the advanced ArchiDroid user will just LOVE this feature, as much as I love it. I'm looking forward to your responses how YOU use pocket debian with your ArchiDroid. It's also a great time to learn what does the debian offer and how you can simplify your common tasks with just one example debian utility .
Technical informations:
1. Pocket Debian does not cause any additional overhead. We don't need to use emulation, neither virtualization to boot our monster. I used chroot technology to "jump" into debian environment with already running kernel and Android. That means additional required CPU/RAM is based on what you run in pocket debian. Booting itself doesn't require anything, just about one megabyte of ram for /bin/bash shell .
2. Android has some restrictions, mostly sockets. It doesn't allow to create inet sockets by default, even for root users. You will need to add your custom debian users to special group called "inet" (GID 3003) to allow creating of inet sockets, and you may also need to add a group to net_raw group (GID 3004) to allow creating of raw sockets. Please keep in mind that it's only required if you're running an app which required it's own socket, for example mysql server. So apt-get install mysql-server will fail right after booting, you will need to use "addgroup mysql inet" and then apt-get -f install to complete installation. Of course "mysql" is the new user under which mysql-server really operates. I've added root to both of these groups by default.
3. The only "real" restriction is the kernel. Our debian uses Android kernel and it's filesystem. It should work with most common tasks but in some cases our kernel may lack specific modules or built-in code, for example tun/tap required for OpenVPN. Still it's enough to run pretty much everything and if you get in touch with your favourite kernel developer you can also kindly ask for specific missing things.
4. Debian is built and included thanks to debootstrap utility, ArchiDroid command used for creating debian environment is debootstrap --verbose --arch armhf --include=git,ca-certificates,ssh,htop,tightvncserver,xterm,xfonts-base --exclude=manpages,man-db,rsyslog,vim-common,vim-tiny testing debian http://ftp.fr.debian.org/debian
HowTo:
Pocket Debian contains two main terminal commands, "adlinux" and "debian". Both of them are described below. By adlinux and debian you boot and jump into debian's chroot, which means you can use any debian-specific commands.
Examples:
passwd - changes password of actual user. This is needed to login as specific user, for example through ssh.
service ssh start - starts local SSH (secure shell) daemon on native port :22, to which you can easily access via any client supporting ssh, f.e. PuTTY. So basicly after you start shell you can literally connect to your local area network (LAN) IP on port 22 f.e. through PuTTY from your PC.
ifconfig - prints network-related informations about online interfaces, including your local IP, which may be useful for connecting to SSH.
htop - Enhanced top utility. Gives you very good terminal-based view on actual running processes, used ram, load, and more.
apt-get update - Syncs with debian's apt repository. This is mandatory to use many of apt commands because ArchiDroid's debian comes without local repo available, however fully configured to download and access it with just one command
apt-get install XXX - installs packet XXX from debian's repository.
apt-cache search XXX - searches for all packets including keyword "XXX". Ultra useful in terms of searching for specific packet.
Please note that pocket debian is VERY similar to normal native Debian/Ubuntu distribution, therefore above commands are not ArchiDroid's magic, they're very widely used in Debian/Ubuntu distros. If you want to learn more, most of the Debian/Ubuntu tutorials will be very helpful.
ArchiDroid's Pocket Debian Booter (adlinux)
You can call "adlinux" command from your favourite terminal.
adlinux is designed to boot and prepare ArchiDroid's Pocket Debian environment. It requires mode to be specified, and also respects any extra arguments passed.
If you call standalone "adlinux" command then it will print usage and then ask you what you want to do with giving proper informations about every choice. Additionally if you know what you want to do, you can also pass arguments directly to adlinux command, f.e. by executing "adlinux default", which will execute adlinux with "default" mode.
Available modes:
default - Will mount /data /system /storage/sdcard0 /storage/sdcard1 and core filesystems in chroot. Default suggested mode
safe - Will mount only core filesystems in chroot. Useful if you don't want to share your storage in chroot
bare - Won't mount even core filesystems such as /proc /dev or /sys. Requires "debian force" to enter chroot. This is the "real" safe mode. You won't be able to interact with an android in any way, while debian itself will work in very limited environment, making core functions unavailable. Suggested only for testing purposes
rebuild - Will automatically reboot your device and remove debian folder in the safe way. WILL CAUSE ALL DEBIAN DATA TO BE LOST!
unmount - Will automatically reboot your device to safely unmount debian environment
Extra options:
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard), if possible
intsd - Use internal sd card (/data/media/0)
Additional information about modes:
Debian shares core kernel filesystems in "safe" and "default" modes, while it also shares your internal and external sd card in "default" mode. This is nothing to be scared of, as you have full control of what you run in debian, however please note that you CAN'T do whatever you want. All mounted partitions in debian are "binded". "Bind" means that it's mirrored to the mount point and all changes on mounted partition WILL affect the mount point, which is logical. This is nothing to be scared of, as long as you know that debian only extends your environment, it does not fully works in it's own and you CAN cause serious problems from inside of chroot. The only really safe mode is "bare" mode, however in "bare" mode debian can't really do anything, as kernel filesystems are absolutely required for most of the functions. Okay so, you need to know one thing. If you have booted debian you SHOULD NOT touch debian's folder, which is ArchiDroid/debian (on your internal or external sd card, depends what you choosed).. As you know debian for example binds /data to it's folder /data, which is physically ArchiDroid/debian/data. If you for example delete ArchiDroid/debian through root explorer WITH mounted debian then it will ALSO delete debian/data folder, which is binded to /data, and therefore will delete your whole internal sd card, that's why it's extremely important to take care because booted debian becomes part of the android and deleting it can cause at least soft bricks, with a possibility of hard as well. If you want to delete debian folder PLEASE use "rebuild" mode, only through this way you're absolutely sure that nothing bad happens and you won't delete your whole system partition by accident.
Note about extsd option:
Debian requires symlink functionality, typically native windows filesystems DON'T support symlinks, therefore you need to have your external sd card formatted in one of the native linux filesystems, f.e. ext4. adlinux will automatically tell you if debian can be unpacked and used on your external sd card, however it won't be possible under most common filesystems, such as exFAT or FAT32.
Technical informations:
1. Pocket debian archive is located in ArchiDroid/System/debian.tar.gz file. This is "bare" system used for creating environment for the first time, you should not touch it.
2. adlinux detects if debian is already extracted when booting, if not, it's firstly extracted from the file described above.
3. After extracting (if required), core filesystems are mounted with "bind" option based on the mode you've selected in "mode" question above. Typically it mounts /data /system /storage/sdcard0 /storage/sdcard1 /storage/extSdCard /dev /proc /sys.
4. Unmounting is not fully supported right now (linux barrier), therefore both "unmount" and "rebuild" options require a restart to execute properly.
ArchiDroid's Pocket Debian Shell/Chroot (debian)
You can call "debian" command from your favourite terminal.
debian command is designed to allow you "jumping" into debian chroot created by adlinux. Please read how adlinux command works firstly if you haven't done that already. debian command checks if core filesystems are available (if debian is booted), and if they are then it firstly modifies required environment variables to make debian happy (such as TERM, HOME, PATH), then it changes root (chroots) into debian folder, therefore allowing you to execute everything from inside of chroot. It's very generic command, therefore standalone "debian" command won't give you a choice the way adlinux did.
Available options (parameters):
force - required for jumping into bare debian, created with "adlinux bare" command above. This skips debian checks for mounted core filesystems, normally you should avoid it at all cost, unless you know what you're doing. If core filesystems are missing then it's very likely that your debian will be disabled in more than 90%.
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard), if possible
intsd - Use internal sd card (/data/media/0)
cmd - Executes command in debian chroot
WARNING! cmd parameter will cause all further parameters to be threated as a command passed to debian, therefore you need to make sure that this is the last debian parameter which you want. For example "debian force cmd service ssh start" will skip filesystems checks and execute "service ssh start" in debian's chroot, however "debian cmd force service ssh start" will pass "force service ssh start" to debian, therefore respecting filesystems checks and passing invalid command.
This function is extremely useful for making init.d and other startup scripts. For example you can easily call "adlinux default" and then "debian cmd service ssh start" to call secure shell daemon on every boot with two easy steps.
Technical informations:
1. debian command uses chroot technology to change root of current shell to debian shell.
2. After chrooting to debian directory, /bin/bash shell is automatically called as default debian shell.
ArchiDroid's Flasher (adflash)
You can call "adflash" command from your favourite terminal.
adflash is a great small utility, which allows you to easily update your ArchiDroid to latest stable or experimental version with one easy command and delta upgrade. It utilizes ArchiDroid functions, therefore you must be running ArchiDroid to use it.
If you call standalone "adflash" command then it will print usage and then ask you what you want to do with giving proper informations about every choice. Additionally if you know what you want to do, you can also pass arguments directly to adflash command, f.e. by executing "adflash 2e git", which will execute adflash with 2.X-EXPERIMENTAL version using git mode.
Available versions:
2e - 2.X-EXPERIMENTAL
2s - 2.X-STABLE
1e - 1.X-EXPERIMENTAL
1s - 1.X-STABLE
Extra options:
git - Sets up local git repository, which gives you delta upgrades and bandwidth saving
direct - Downloads targeted branch as .zip file directly from github
clean - Cleans everything up, including local repo and tmp folder from ArchiDroid directory specified below
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard)
intsd - Use internal sd card (/data/media/0)
nozip - Shows changelog and changes only
Okay so, the most interesting option is the mode...
Direct mode is simple, fast and effective. It downloads target version (stable or experimental) from GitHub server, then it repacks downloaded zip file and makes it available for flash. You should use this mode for one-time downloads, such as once per stable version or two. The only advantage of this method is the ability to download from github (and with one command).
Git mode is complex. It uses ArchiDroid's Pocket Debian (read above) for cloning and updating local ArchiDroid repo. This gives several number of advantages, mostly for using experimental versions. Firstly, by having local ArchiDroid repo you have to download ONLY changes between your snapshot and server's snapshot, which means delta upgrades. Secondly, you have access to all commits from target branch, so you know exactly what has changed since your latest download. Again, this is extremely useful for experimental branch, as changelog may not be up-to-date. Keep in mind that git mode will require additional space on your device for keeping ArchiDroid repository, therefore you sacrifice some space for delta upgrades. This mode is extremely useful for flashing ArchiDroid often, for example daily experimental versions, because in fact you download only new commits instead of whole repo/archive.
ArchiDroid's RunOnce (Backend)
ArchiDroid's Init (Backend)
ArchiDroid's Backend Control
ArchiDroid Backend Control is a set of settings, which controls behaviour of ArchiDroid's Init. It's located in /system/archidroid/dev and contains a number of files, which are recognized by ArchiDroid's Init. You shouldn't directly touch /system/archidroid/dev, instead you can control behaviour of ArchiDroid's Backend through /system/archidroid/scripts. They can be easily executed through any script manager, f.e. Root Browser or Android Terminal Emulator. Some of the settings are also located in /system/archidroid/etc folder, mostly configurations for binaries utilized by ArchiDroid's Init.
ArchiDroid's HArdware Volatile Entropy Gathering and Expansion Daemon (Haveged)
The haveged project is an attempt to provide an easy-to-use, unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads, especially on headless servers. Current development of haveged is directed towards improving overall reliablity and adaptability while minimizing the barriers to using haveged for other tasks.
The original HAVEGE research dates back to 2003 and much of the original haveged documentation is now quite dated. Recent work on haveged has included an effort to provide more recent information on the project and its applications.
The original research behind HAVEGE use was based upon studies of the behavior of processor caches from a hardware level. The 'Flutter' documents attempt to provide a modern view of HAVEGE at software level through the use of a diagnostic build of haveged that captures the non deterministic inputs to haveged for analysis by external tools.
ArchiDroid has built-in haveged entropy generator. It's controlable through ArchiDroid's Backend Control - ArchiDroid_Haveged_EnableDisable.sh. It's turned on in default configuration, through HAVEGED_ENABLED
ArchiDroid's Fast Random Number Generator (Frandom)
Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux' built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
ArchiDroid has built-in frandom activator. It's controlable through ArchiDroid's Backend Control - ArchiDroid_Frandom_EnableDisable.sh. It's turned on in default configuration, through FRANDOM_ENABLED.
Notice: Kernel must support frandom module to actually make use of that. Init will try to search for frandom.ko module and load it, then use /dev/erandom for both /dev/random and /dev/urandom. If your kernel supports frandom, it will work. If it doesn't, obviously this will be skipped even if you have FRANDOM_ENABLED. Check ArchiDroid Init log located in /data/media/0/ArchiDroid/Init.log to check if frandom works properly for you.
ArchiDroid's Adblock (dnsmasq/dnrd, dnsproxy2, pixelserv)
dnsproxy2 is a replacement DNS proxy for Android 4.3+
This currently allows the user to manually override the DNS server IP,
and it sets the correct UID on outbound requests so they can be filtered
via iptables / AFWall+ / DroidWall / etc.
Dnsmasq is a lightweight server designed to provide DNS, DHCP and TFTP services to a small-scale network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP for network booting of diskless machines.
Dnrd, Domain Name Relay Daemon is a caching, forwarding DNS proxy server. Most useful on vpn or dialup firewalls but it is also a nice DNS cache for minor networks and workstations.
Pixelserv is a super minimal webserver, it's one and only purpose is serving a 1x1 pixel transparent gif file. Using some creative firewalling (netfilter/iptables) rules you can redirect some webrequests (for adds for example) to pixelserv.
ArchiDroid has built-in Adblock. It's controlable through ArchiDroid's Backend Control:
ArchiDroid_Adblock_DnsmasqDnrdModeSwitch.sh
ArchiDroid_Adblock_EnableDisable.sh
ArchiDroid_Adblock_EnableDisableLocalDNSes.sh
ArchiDroid_Adblock_EnableDisableLocalDNSesDaemon.sh
ArchiDroid_Adblock_LockUnlockHosts.sh
ArchiDroid_Adblock_MoabAdawayHostsSwitch.sh
ArchiDroid_Adblock_Reload.sh
It's turned on in default configuration, through:
ADBLOCK_ENABLED
ADBLOCK_LOCAL_DNSES_DAEMON_ENABLED
ADBLOCK_LOCAL_DNSES_ENABLED
ADBLOCK_USE_ADAWAY_HOSTS
ADBLOCK_USE_DNSMASQ
In short. This is a very advanced and powerful solution for blocking ads through DNS queries. First of all we're forwarding all DNS traffic to localhost (127.0.0.1). Then we're handling them through local DNS server - dnsmasq (default), or dnrd (option). Our local DNS server reads blocked hostnames through special /system/archidroid/etc/hosts file, then if no record is found, it forwards DNS query to OpenDNS/Google DNS servers, or if it's found, returns 127.0.0.1 as the address. Lastly, pixelserv is providing a 1x1 NULLGIF response on local web server, so instead of big black/white screen instead of the AD, we get 1x1 transparent pixel, which usually perfectly hides ad from the app or the website.
Extra features:
1. You can specify if you want to use dnsmasq (default), or dnrd (option) as a local dns server. Dnsmasq is more flexible, modern, faster and has less memory footprint, however I also left dnrd as an option, because it's proven to work stable.
2. You can specify hosts file, which you want to use. In default configuration we use AdAway's hosts file, with more than 30 thousand of records, which results in extra ~2.5 MB memory usage. You have also an option to use MOAB (Mother Of Ad Blocking) hosts file, with more than 330 thousand of records, which will result in about ~30 MB memory usage. Eventually you can append your own rules or use non-standard hosts file, available in /system/archidroid/etc/hosts. Pro tip: You can point AdAway to use this hosts file (/system/archidroid/etc/hosts_adaway), which will result in automatic updates. /system/archidroid/etc/hosts is a symbolic link, either to hosts_away or hosts_moab, if you want to specify your own hosts, you can delete symbolic link and write your own rules.
3. Original /system/etc/hosts file has been locked from editing. This is to ensure that AdAway or other adblockers won't use obsolete and slow method of blocking ads through hosts. The whole point of implementing Adblock in ArchiDroid is to provide you with super-fast, flexible and effective way of blocking ads, also with getting rid of black/white ad screen. In 99% situations you don't want to touch ArchiDroid's default behaviour, as it blocks ads perfectly. Eventually, if you have a very good reason, you can unlock original hosts file through ArchiDroid's Backend Control and modify them, however keep in mind that every additional rule WILL slow down your network speed.
4. In default configuration local dns server uses two OpenDNS servers at port 5353, two Google DNS servers at port 53 and up to two local DNS servers provided by your Wi-Fi/3G connection, which overall gives a sum of 6 remote dns servers. In some rare scenarios (f.e. some wi-fi hotspots) you can notice that a moron, administrator of this wi-fi, blocked all dns queries and forces you to use his DNSes. This is BAD because of freedom and so on, but it's very common practice, that's why I turned on local DNSes as well. If you want to improve your privacy at least a bit, you can disable local DNS servers and then use only OpenDNS and Google DNS.
5. Above option initialy has been written to allow you one-time access to such non-trusty wi-fi's. But if you for any reason need automatic update of your local DNSes (3G and Wi-Fi's will use different local DNSes), you can also turn on Local DNSes Daemon, which will automatically query and update local DNSes if needed. This is also turned on in addition to local dnses above, of course in default preset.
ArchiDroid's Forced Update (RunOnce)
Forced update selected during mode selection in aroma tells RunOnce to work in "INSTALL" mode even on "UPDATE" mode, apart from that it works exactly the same as update mode, only RunOnce is affected.
Credits
First of all many thanks to JustArchi, who gave me the permission to port this rom
and helped me not only one time to get all things to work :good:!!!
Many many thanks JustArchi for the help and support!
ArchiDroid Core
- AROMA Installer
- AROMA Filemanager
- Didhiy Kernel
- Neo Kernel
- PhilZ Touch Recovery
- SuperSU
- Nova Launcher
- TouchPal Keyboard
- Hacker's Keyboard
- Android Terminal Emulator
- BetterBatteryStats
- Cool Tool
- Greenify
- MX Player & Custom Codec
- LMT
- Root Browser
- Titanium Backup
- CrossBreeder
- Online Nandroid
- Xposed Framework
- App Settings
- XPrivacy
- Debian
- cURL
- GitHub
ArchiDroid 2.X
- OmniROM for GT-I9300
- Linaro Toolchain
- Spirit 2
- Wanam Xposed
Special thanks to:
- Kenshin, for graphic design and ArchiDroid Touhou bootanimation
- @mrtur, for graphic design and helpful hand during ArchiDroid experimental tests
- @malachow, for helping users across both international and polish board, sharing the spirit of ArchiDroid
- All ArchiDroid Contributors, for improving and making ArchiDroid better!
- ArchiDroid Facebook Group, for beta-testing the very first alphas of ArchiDroid 2.0.0
- ROM Cleaner, for awesome generic list of bloatware
- Android Revolution HD, for being ex-ArchiDroid 1.X base
- WanamLite, for being ex-ArchiDroid 1.X base
- Temasek's Unofficial Build, for being ex-ArchiDroid 2.X base
- crDroid, for being ex-ArchiDroid 2.X base
- You, for choosing ArchiDroid over other available ROMs
I'm very happy to see ArchiDroid running also on Galaxy S .
Let me know @rodman01 if you need any help or a helpful hand, and watch my github for ArchiDroid updates .
Thanks, yes I am happy too, that I got it to work finally (kernel choice is working, but selectable modes I skipped for the moment)...your help to get this all was highly appreciated and needed and I am sure I will come back again with questions . And yes sure, I will watch your github and when I as soon as I have time, I will create branch on my repo with the changes I made :good:.
rodman01 said:
Thanks, yes I am happy too, that I got it to work finally (kernel choice is working, but selectable modes I skipped for the moment)...your help to get this all was highly appreciated and needed and I am sure I will come back again with questions . And yes sure, I will watch your github and when I as soon as I have time, I will create branch on my repo with the changes I made :good:.
Click to expand...
Click to collapse
If I can suggest anything...
Make sure that my backend works properly on SGS, you can check logs in /data/media/0/ArchiDroid, and use ArchiDroid app to check if everything works properly (haveged, dnsmasq, dnsproxy2, pixelserv etc. should be ON). This give you a few ArchiDroid-unique features described in development thread. I used advanced SGS3-optimizations, so I'm wondering if you can launch it on SGS .
Apart from that my github is a real mine of knowledge, so if you dig deep enough you should get answers to everything .
And of course, I'm very glad to see that you made it!
Yes sure you can and I will check it...to be honest haven't realized this and afraid that this won't work , but will see and probably can fix this in one of the next versions (if possible in general for and with the S1?).
rodman01 said:
Yes sure you can and I will check it...to be honest haven't realized this and afraid that this won't work , but will see and probably can fix this in one of the next versions (if possible in general for and with the S1?).
Click to expand...
Click to collapse
I'll need to recompile these binaries for generic ARM target instead of SGS3 then, just watch my github and cherry-pick proper commit when it arrives .
haveged, dnsmasq, dnsproxy2, pixelserv are on and it seems that they are running. In init.log there are a few lines mentioning for example: no such file or directory. If you want and if helpfull I can pass you the logs you want.
rodman01 said:
haveged, dnsmasq, dnsproxy2, pixelserv are on and it seems that they are running. In init.log there are a few lines mentioning for example: no such file or directory. If you want and if helpfull I can pass you the logs you want.
Click to expand...
Click to collapse
If my binaries are running properly then it's great, you should have working adblock and entropy >= 1024.
Send me RunOnce and Init logs .
Yes sure no problem. Here are the log files attached....
rodman01 said:
Yes sure no problem. Here are the log files attached....
Click to expand...
Click to collapse
Wed Apr 23 00:17:20 CEST 2014
ArchiDroid 2.4.3 EXPERIMENTAL [KVT49L]
Linux localhost 3.0.101-KK44-x-aries-cma #1 PREEMPT Tue Apr 1 07:47:49 WIB 2014 armv7l GNU/Linux
INFO: ArchiDroid_RunOnce executed!
INFO: I'm a child!
WARNING: Forcing Install mode, even if Update mode found!
INFO: Install mode detected, I'm either after full wipe or forced to think so. Turning on ADMANY and DBUPDATE
I found ./de.robv.android.xposed.installer which need merging (data)
I found ./ds.cpuoverlay which need merging (data)
I found ./com.android.settings which need merging (data)
I found ./eu.chainfire.supersu which need merging (data)
I found ./org.omnirom.device which need merging (data)
INFO: I found 5 folders which need merging (data)
INFO: boot-dmesg NOT detected, turning off logcat banner
INFO: RunOnce Semaphore started
INFO: Android created settings.db for me, how cute! Performing DBUPDATE
INFO: Applying AOSP-specific DBUPDATE
INFO: Finished DBUPDATE
INFO: I'm currently merging com.android.settings, called by ADMANY
INFO: Done! 4 to go
INFO: I'm currently merging de.robv.android.xposed.installer, called by ADMANY
INFO: Done! 3 to go
INFO: I'm currently merging ds.cpuoverlay, called by ADMANY
INFO: Done! 2 to go
INFO: I'm currently merging eu.chainfire.supersu, called by ADMANY
INFO: Done! 1 to go
INFO: I'm currently merging org.omnirom.device, called by ADMANY
INFO: Done! 0 to go
INFO: I looped 91 times and didn't have to exit from infinite loop, that's nice (RunOnce Semaphore)
INFO: Calling Post-Installation functions (if any)
INFO: Could not detect RunOnce in init.d after cleanup, that's good
INFO: Reboot required, I'm rebooting the device right now
INFO: ArchiDroid RunOnce finished
Wed Apr 23 00:21:17 CEST 2014
Click to expand...
Click to collapse
RunOnce works great!
However Init not so .
HAVEGED: ArchiDroid entropy set to: 1024. Available entropy can't get below this level
HAVEGED: Current available entropy: 183
Click to expand...
Click to collapse
Looks like haveged is not working at all.
Apart from that, one more issue found:
/system/xbin/ARCHIDROID_INIT[438]: can't create /dev/archidroid/cron/events/internal/MONITOR_START_HAVEGED: No such file or directory
Click to expand...
Click to collapse
Is /dev directory available in your system?
Code:
ADPROC="/dev/archidroid"
mkdir -p "$ADPROC"
Because this piece of code should create archidroid dir in /dev.
---------- Post added at 10:37 PM ---------- Previous post was at 10:29 PM ----------
Also, check Cron.log in ArchiDroid dir (/data/media/0/ArchiDroid) if it's not infinite-looping due to that... .
JustArchi said:
Is /dev directory available in your system?
Code:
ADPROC="/dev/archidroid"
mkdir -p "$ADPROC"
Because this piece of code should create archidroid dir in /dev.
Click to expand...
Click to collapse
Yes the folder is available, but almost all files have 0.0 b size, could it be that sym links and/or missing or wrong permissions are the reason?
rodman01 said:
Yes the folder is available, but almost all files have 0.0 b size, could it be that sym links and/or missing or wrong permissions are the reason?
Click to expand...
Click to collapse
Check if you can create a folder in it as root: mkdir /dev/whatever
Perhaps I'll need to move my ADPROC somewhere else, as your device may not support folders in /dev.
Also, I added a safety check for that .
https://github.com/JustArchi/ArchiDroid/commit/b8cae2000d8802e7f9e270eb43b3c621895d9340
JustArchi said:
Check if you can create a folder in it as root: mkdir /dev/whatever
Perhaps I'll need to move my ADPROC somewhere else, as your device may not support folders in /dev.
Also, I added a safety check for that .
https://github.com/JustArchi/ArchiDroid/commit/b8cae2000d8802e7f9e270eb43b3c621895d9340
Click to expand...
Click to collapse
Yes you are right, seems that creating folders in /dev is not possible.
rodman01 said:
Yes you are right, seems that creating folders in /dev is not possible.
Click to expand...
Click to collapse
Try as root, as user you'll always get permission denied .
ok sorry, but no folder wasn't created, although terminal has asked for su permissions and had been given. But no new folder to see.
rodman01 said:
ok sorry, but no folder wasn't created, although terminal has asked for su permissions and had been given. But no new folder to see.
Click to expand...
Click to collapse
I'll need to add some more tunables to properly support your device. As for now you should sync with my work (mostly https://github.com/JustArchi/ArchiDroid/commit/b8cae2000d8802e7f9e270eb43b3c621895d9340) and ignore those errors .
Thanks for your help and as for now :good:...will sync it and try a new build, think tomorrow.