Arch Linux is an independently developed, x86-64 general-purpose GNU/Linux distribution that strives to provide the latest stable versions of most software by following a rolling-release model. The default installation is a minimal base system, configured by the user to only add what is purposely required.¹
NOTE: The Arch Linux packages are no longer updated. Consider taking a look at the postmarketOS port instead.
Introduction
With Android 5.0 (Lollipop), the ASUS MeMO Pad 7 (ME176C(X)) was updated with UEFI boot, making it possible to boot any Linux distribution on it. archlinux-me176c aims to make Arch Linux fully work on the ASUS MeMO Pad 7 (ME176C(X)). It provides additional packages and documentation for using Arch Linux on this device.
With me176c-boot, Linux can be installed in dual/multi boot configurations together with Android. Arch Linux is a minimal distribution, therefore most of the setup (partitioning, installing a desktop environment, ...) will be left up to you. However, it also allows you to customize it entirely to your liking, and configure it for any use case you can imagine.
Installation
Warning: Although the wiki article below provides many recommendations, at the end, setting up the installation will be left up to you. There is no step-by-step guide. If you have never used Arch Linux before, you may want to try it on a desktop PC or virtual machine first. You can easily brick your tablet if you don't know what you are doing!
All documentation is available in ASUS MeMO Pad 7 (ME176C(X)) - ArchWiki. As a wiki article, I encourage everyone to contribute and share their experiences with everyone else.
If you need any help or further suggestions, do not hesitate to ask in this thread!
FAQ
Can I use other Linux distributions on this tablet? Yes! However, you will need to set up more things manually. There are a few notes for this in linux-me176c: Porting - Using linux-me176c in other distributions
Source Code
Documentation: ArchWiki
Packages: archlinux-me176c (GitHub)
¹ Source: https://wiki.archlinux.org/index.php/Arch_Linux (GFDL 1.3)
XDA:DevDB Information
Arch Linux for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev/archlinux-me176c
Version Information
Status: No Longer Updated
Created 2019-04-02
Last Updated 2020-05-12
Reserved
Hi!
Seem awesome!
Do this have a full hardware accelerated graphics support?
Is this compatible with k013 ?
shim80 said:
Do this have a full hardware accelerated graphics support?
Click to expand...
Click to collapse
Yes. (It has Intel Graphics just like on normal Intel PCs, and therefore OpenGL and Vulkan support is provided by Mesa.)
shim80 said:
Is this compatible with k013 ?
Click to expand...
Click to collapse
Yes, K013 == ME176C(X).
Thanks for the answers.
Also, if wan't to go back to Android, can I do it?
shim80 said:
Also, if wan't to go back to Android, can I do it?
Click to expand...
Click to collapse
The recommended setup is to keep Arch Linux on an external SD card. Then you can have Android and Arch Linux installed at the same time ("dual boot").
@lambdadroid man when running
# pacman -Sy me176c
or trying to install base packages it says
error: me176c:signature from "lambdadroid is known trust error: failed to update me176c (invalid or corrupted database (GPG signature)
when running
$ pacman-key --finger keyid
it says pub
ed25519 2017-08-10 [sc] [expired: 2019-08-17] uid [expired]
should I try an offline instalation?
No longer updated
The binary repository has been down for a while now - I have no plans to update the Arch Linux packages again. This is mostly because I'm no longer using Arch Linux myself on the me176c / K013.
However, as a replacement a postmarketOS port with same functionality has been around for a while. Since it's much more comfortable to install (simply through Fastboot/SD card with a large number of selectable UI interfaces) I prefer it over Arch Linux at this point. I would recommend it to anyone who would like to use a more standard "Linux" distribution on me176c / K013.
Related
Hello all,
Is there a way to build the native android kernel for your device, to include other linux applications?
I would like to build X11 inside of android and use the existing GUI of android.
I'd also like to be able to compile other linux apps isde android as well.
all the searching I have is about linux inside of a chroot, and that's not what i'm looking for.
since android is build upon linux, then really it should only be a matter of runing a few scripts to call init files and other libraries?
I did see this "Build native GNU/Linux applications: the easy way"
But nothings been done since early 2012.
If I'm going to be compiling an android and its kernel for a device from scratch, then it makes sense to extend the linux to include the functionality to build native linux apps as well, right?
hi, is it possible to install any GNU Linux on this beast? Didn't found anything about pure linux clone, etc.
This would be really amazing. Driver support would be non-existent but its possible to use libhybris with the Android binaries as a stop-gap.
Lineage CICD Project
This is my personal effort given to you, the community, which spends a lot of hours to craft a fully-functional and perfectly tuned ROM for our beloved Smartphones!
What is it?
This project aims to provide a Build system for Android Developers which will be able to build an Android ROM for a different set of Codenames given, automatically for you, ( by default ) every night. Not only built stock sources that are already available on LineageOS Github account, but feel free to build even your custom code thanks to the support of local_manifests/*.xml fully supported by this Docker.
Where can I find it
CICD
- Github: https://github.com/julianxhokaxhiu/docker-lineage-cicd
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/docker-lineage-cicd/
OTA
- GIthub: https://github.com/julianxhokaxhiu/LineageOTA
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/lineageota/
- XDA: https://forum.xda-developers.com/showthread.php?t=2636334
Why?
As you all remember the transition from CyanogenMod to LineageOS was not smooth. Even today we are not granted with Nightly Builds, but with Weekly, because of capacity issues on providing such an amazing plethora of supported Devices ROM ZIPs ready to be flashed.
Therefore this projects aims on providing an easy-to-use build system which may help you on providing a Ready-To-Flash ZIP at the end of each Build round.
How does it work?
This is a pre-packaged Docker system based on Debian, with all the dependencies in place to correctly build ( even in an optimized way ) any LineageOS codename ROM. A cronjob will take care to start the build script on the configured time ( by default 10:00 UTC ~= 02:00 PDT ), which then will take care to build every codename given with an environment variable to the Docker.
All you need from now on is just the Docker Engine installed on your favourite Linux distribution.
Bonus!
Of course the ZIP that will be produced needs to be transferred to the device in order to flash it. Such a boring task...what if we can automate it through OTA?
As you all know, my first big project I've ever started for XDA was the OTA Server which perfectly emulates all the required calls to make it working with ( old and deprecated now ) CyanogenMod ROMS, as well as with ( long life to ) LineageOS, right now, today!
All you need to do is to configure an Environment variable in the Docker to say where your OTA Server is located. The URL will the be added automatically for you inside the build.prop file as cm.updater.uri=$OTA_URL.
...but wait, there is more!
Since the OTA Server is written in PHP, you all know that is a headache to prepare the system to make it working. A lot of user complained in the original Thread that was difficult for them to understand how to setup it correctly, therefore a fully working autonomous Docker is there for you, ready to serve the OTA Layer for you built ROMs!
I want to use it right now!
I am pretty sure you want! The Docker has now been tested for a nearly a Month and I'm successfully installing my own builds for a couple of weeks on my devices ( really a great satisfaction! ).
If you want to run it as well, I suggest you to take a look at this Bash script that will run for you the Dockers, already talking to each other. Since the script has been studied to work on top of the "VPS Powered By Docker" project, I suggest you to take a look at it. Although nothing is preventing you to use it in your favourite way.
Requirements
See the detailed list on the project README.
What about License
All my projects are always developed with MIT license, which means feel free to do what you want with it. I don't really care if you do business with it, it was a great challenge for me reaching this autonomous entity to run, therefore I don't mind of possible outcomes of it. Although Issues are always welcome for improvements, if any found, of suggestion for a possible feature enhancements.
Future plans?
At the moment I have some ideas, which I may, or may not, be able to implement as I am not a professional Android Developer. Although some nice to have points are:
- Possibility to build ANY Android distro ( from AOSP to any fork of it )
- Possibility to have changelogs of every nightly build ( attached as *.txt and *.html format, next to the built ROM )
- Maybe a logo?
Thanks for Awesome Work
Thanks for awesome work.
TWRP CICD Project
This is my personal effort given to you, the community, which spends a lot of hours to craft a fully-functional and perfectly tuned ROM for our beloved Smartphones!
What is it?
This project aims to provide a Build system for Android Developers which will be able to build a TWRP recovery image for a different set of Codenames given, automatically for you, ( by default ) every night. Not only built stock sources that are already available on TWRP Github account, but feel free to build even your custom code thanks to the support of local_manifests/*.xml fully supported by this Docker.
Where can I find it
CICD
- Github: https://github.com/julianxhokaxhiu/docker-twrp-cicd
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/docker-twrp-cicd
Why?
At the current status I find very time consuming the task to always setup the environment the right way to build a sporadic recovery for any kind of device, depending on the tree.
Therefore this projects aims on providing an easy-to-use build system which may help you on providing a Ready-To-Flash IMG at the end of each Build round. The same you would download from twrp.me website.
How does it work?
This is a pre-packaged Docker system based on Debian, with all the dependencies in place to correctly build ( even in an optimized way ) any TWRP codename image. A cronjob will take care to start the build script on the configured time ( by default 10:00 UTC ~= 02:00 PDT ), which then will take care to build every codename given with an environment variable to the Docker.
All you need from now on is just the Docker Engine installed on your favourite Linux distribution.
I want to use it right now!
I am pretty sure you want! The Docker has now been tested for a nearly a Month and I'm successfully installing my own builds for a couple of weeks on different devices ( really a great satisfaction! ).
If you want to run it as well, I suggest you to take a look at this Bash script that will run for you the Docker. Since the script has been studied to work on top of the "VPS Powered By Docker" project, I suggest you to take a look at it. Although nothing is preventing you to use it in your favourite way.
Requirements
See the detailed list on the project README.
What about License
All my projects are always developed with MIT license, which means feel free to do what you want with it. I don't really care if you do business with it, it was a great challenge for me reaching this autonomous entity to run, therefore I don't mind of possible outcomes of it. Although Issues are always welcome for improvements, if any found, of suggestion for a possible feature enhancements.
Enjoy!
I'm trying to compile Android for a dragonboard 410 clone, and would like to enable a firmware level functionality so that the device reboots if there is some kind of OS level failure.
I noticed on the Linux Github (Documentation/watchdog/watchdog-API.txt) that the Linux source has exactly what I'm trying to implement. (sorry, new user so can't post links)
I'm unfamiliar with compilation from source on Android, is there a compilation flag or option I can use to enable this functionality on Android?