postmarketOS is a general purpose Linux distribution based on Alpine Linux running on more than 200 different phones/tablets (although most of them have only little functionality working). Various different UI interfaces can be configured for installation and flashed through Fastboot (or on a SD card).
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. The mainline kernel port for asus-me176c (also used in the LineageOS ROM) has the advantage that it works well on any kind of distribution. The postmarketOS port has the same hardware functionality working as LineageOS (so basically everything except Camera and GPS).
With me176c-boot, Linux can be installed in dual/multi boot configurations together with Android.
Installation
Everything is documented on the postmarketOS wiki page for asus-me176c.
If you need any help or further suggestions, do not hesitate to ask in this thread! Alternatively, use one of the postmarketOS chat channels (make sure to mention "me176c"), or open an issue.
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
XDA:DevDB Information
postmarketOS for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid, Mis012
Source Code: https://gitlab.com/postmarketOS/pmaports
Version Information
Status: Stable
Created 2020-05-12
Last Updated 2020-05-12
I've tried for a day to build this, but am hopelessly stuck... Is there any mechanism available to get some assistance?
rodbacon said:
I've tried for a day to build this, but am hopelessly stuck... Is there any mechanism available to get some assistance?
Click to expand...
Click to collapse
Hi, sorry about that. I have to admit that I'm not checking XDA very often at the moment. If anyone needs help here I would recommend to join the postmarketOS chat channels on Matrix or IRC: https://wiki.postmarketos.org/wiki/Matrix_and_IRC. If you mention "me176c" I should be notified and will reply as soon as possible. Thanks!
Related
Hello,
My device is a Lenovo Yoga Tab 2 830f running stock Lollipop 5.0 at the moment. Bootloader unlocked and permanent TWRP recovery.
I am trying to learn about Android development while building CM13 for this device. I am using the following as my references:
surdu_petru's TWRP recovery
Olivier's CM12.1 port
Lenovo's open source code for Yoga Tab 2
CyanogenMod's porting guide
I have the following questions:
* What exactly are we supposed to do with the files in the archive supplied by Lenovo?
* Why did Olivier start porting CM12.1 instead of CM13? Also, why x86 instead of x86_64?
* Is there any agreed-upon device configuration I should be using for this Baytrail tablet? How about this BoardConfig.mk for Minnowboard Max from Intel Android-IA?
The CyanogenMod porting guide is not exactly specific on any particular strategy how to set up the BoardConfig.mk and other files in ./device/. I get it that it's trial and error for the most part, but is there any general guideline I should be following?
I expect this learning experience to take at least a couple of months, so I'll be keeping this thread open for more questions as soon as I have them.
Hello, I am also interested in working on this device. I am currently trying to build using these instructions: https://forum.xda-developers.com/th...-cyanogenmod-12-1-lenovo-yoga-tablet-t3333360
Lenovo is the only company to have released an Android Nougat update for an Intel Atom Cherry Trail SoC powered device.
If Lenovo releases the kernel sources for the Android N version created for its Lenovo Yoga Book (Lenovo YB1-X90F/L), developers can start working on Android N upgrades for other devices powered by the Intel Atom Cherry Trail SoCs.
Lenovo has previously released the Android Marshmallow kernel sources for the Yoga Book (https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515 Thus it shouldn't be a problem abiding by the General Public License v2 (GPLv2), which requires Android device makers to publish the kernel source code.
Please consider signing here: https://www.change.org/p/lenovo-kernel-sources-for-lenovo-yoga-book-android-n-7-1-1 . Thank you
True, we really Need to make Lenovo release the source Code, i hope you could edit your Petition by adding that also we Need Infos about how to use the source Code.
Greetings
I'm not sure that it would make a difference, but has anyone tried posting on their support forums or contacting them directly?
It might help our case to note that the device (the Android version, anyway) has been discontinued. I doubt we'll see any further official updates from Lenovo.
Take a look , Hope this will work for you:
https://forum.xda-developers.com/yoga-book/development/sources-yoga-book-nougat-source-code-t3765211
beltani said:
I'm not sure that it would make a difference, but has anyone tried posting on their support forums or contacting them directly?
It might help our case to note that the device (the Android version, anyway) has been discontinued. I doubt we'll see any further official updates from Lenovo.
Click to expand...
Click to collapse
Only via Facebook. Got this answer:
"Thanks for reaching out. Currently, this the only open source http://lnv.gy/2DMoObI we have for Yoga Book. You can keep an eye on the support website as it will be updated if a new open source will be released. Let us know if you have other inquiries."
Feel free to post the link to the petition on the Lenovo forums or even ask them via Facebook/scoial media. The more attention, the greater the chances.
Palm Trees said:
Lenovo is the only company to have released an Android Nougat update for an Intel Atom Cherry Trail SoC powered device.
If Lenovo releases the kernel sources for the Android N version created for its Lenovo Yoga Book (Lenovo YB1-X90F/L), developers can start working on Android N upgrades for other devices powered by the Intel Atom Cherry Trail SoCs.
Lenovo has previously released the Android Marshmallow kernel sources for the Yoga Book (https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515 Thus it shouldn't be a problem abiding by the General Public License v2 (GPLv2), which requires Android device makers to publish the kernel source code.
Please consider signing here: https://www.change.org/p/lenovo-kernel-sources-for-lenovo-yoga-book-android-n-7-1-1 . Thank you
Click to expand...
Click to collapse
THEY UPDATED IT AFTER I CONTACT THEM
CHECK IT OUT https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515
THE MAXIMUM POWER said:
THEY UPDATED IT AFTER I CONTACT THEM
CHECK IT OUT https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515
Click to expand...
Click to collapse
WOW! I've passed this information along. Thanks a lot, this hopefully opens some doors
What did you do exactly?
UPDATE: It's another Marshmallow kernel source code. We need the Android Nougat kernel source code!
Palm Trees said:
WOW! I've passed this information along. Thanks a lot, this hopefully opens some doors
What did you do exactly?
UPDATE: It's another Marshmallow kernel source code. We need the Android Nougat kernel source code!
Click to expand...
Click to collapse
True, i open it and it was another MM sources, i will rewrite to them again, however, i figure it out how to use it, for example specially for yoga Book Windows owners, i tried to install Android distro (Phoenixos, blissos,......) but some Drivers were missing i mean no Sound, no Bluetooth,....... but today i understood how it work, in lib/Firmware we Can add this files in any Android distro to get some or all Drivers work, but im trying to figure out how to copy-paste them inside System.sfs under Windows enviroment :fingers-crossed:
THE MAXIMUM POWER said:
True, i open it and it was another MM sources, i will rewrite to them again, however, i figure it out how to use it, for example specially for yoga Book Windows owners, i tried to install Android distro (Phoenixos, blissos,......) but some Drivers were missing i mean no Sound, no Bluetooth,....... but today i understood how it work, in lib/Firmware we Can add this files in any Android distro to get some or all Drivers work, but im trying to figure out how to copy-paste them inside System.sfs under Windows enviroment :fingers-crossed:
Click to expand...
Click to collapse
Thanks! Hopefully Lenovo releases them - let me know
Get in touch with KonstaT from http://www.modaco.com/forums/forum/445-other-devices/ if you need help with the Android side.
Palm Trees said:
Thanks! Hopefully Lenovo releases them - let me know
Get in touch with KonstaT from http://www.modaco.com/forums/forum/445-other-devices/ if you need help with the Android side.
Click to expand...
Click to collapse
Thanks, i will try to contact him:good:
Hi, I just set up a build environment to be able to compile LineageOS from source for my Galaxy S3 (I know it's an old device, but I'll move over to a Galaxy S4 as soon as the replacement screen comes in the mail). I followed the official instructions on LOS's website for my particular device, without knowing I wouldn't be able to build the latest version (15.1 at this point in time) because they only support 14.1 for the Galaxy S3. So my question is: is there a way I can "port" a newer version of lineageos, in this case, 15.1 to a device that is already supported by 14.1? If so how? I'm new to the rom building community and I've always relied on other people's builds but I want to move on to building my own, that implies that I have some basic knowledge of linux commands and computers in general, but if you could point me to a comprehensive tutorial or just write instructions on how to do it
FYI I'm using Google Compute Engine's VM through SSH to build but I can also free up some space on my physical machine's SSD and build from there if that's easier.
Thanks.
Hi Users and Devs
im writing my test results here about dual booting and other operating Systems that i have installed them on my yoga book Windows Version and i will try to explain lot of Details about this stuff
First i will share the operating Systems and Details about what work and what not on yoga book.
Ubuntu(17.10.1), PhoenixOS(2.6.2 based on Android-x86 Nougat 7.1.1), BlissOS(10.1 based on Android-x86 Oreo 8.1.0), DeepinOS (15.5): no Sound, no halo Keyboard, no Auto rotating, no sensors, no Bluetooth, only Booting, Touch Screen, Screen brightness controling and WiFi are working
Android-x86(7.1.2), Openthos(Based on Android-x86 Lolipop 5.1): nothings at all
There might be a lot of other OSs that i might Forget to mention above, but i released why some Hardware cant work like Sound, Bluetooth,......
the main Problem is the KERNEL(the kernel is a big Collection of modules and Drivers that boot up our Hardwares as soon as we enter any Operation system), some kernels 4,9.x cant boot or wifi and touch Screen cant work, all kernels 4.12.x Support booting, touch Screen and wifi, all kernels 4.15.x Support booting, touch Screen, brightness controling and wifi
the only kernel that will make other OSs work like a charm and without any missing Drivers is buildslave kernel, this kernel came pre-load with most of Lenovo Yoga series + Yoga Book (for yoga Book Android users go to about tablet and check out it), the Problem is that i dont have a 100 GB (i will explain this later) ( in 22 mar 2018 they released the second Version of the Open Source Code for Lenovo YB1-X90F/L https://pcsupport.lenovo.com/au/en/products/TABLETS/YOGA-SERIES/YOGA-BOOK/downloads/DS118515 ) also depend on my Tests the kernel is only for Android 6.0.1, not for 7.1.1
i tried to build Android x86 from sources using Yoga Book Open Source Code from Lenovo but AOSP files are Need at least 100 GB with Additional files from Android x86 abot 20 gb, unfortunatly i dont have this big size of hard disk on my SSD
Yoga Book Android and Windows versions are 99.99% contain the same hardwares (0.01% are only the Keyboard shapes but also the halo Keyboard is the same in both) thats why it make my optimistic about running Stock yb Android Rom on Windows (Windows Version of yb used same bios as yoga Windows series, but yb Android Version use the same bios as yoga Android series does and all of yoga win and Android series based on Insyde bios)
Android yoga Book System based on Android-IA Project which is from Intel to allow Android run in Intel CPUs https://01.org/android-ia as yoga Book based on cherry Trails cpu
for Android yb users you can install Windows and other OSs on your device but you will force same Bugs above and you need to buy a licence key to get Windows updates on it (i only have yb Windows so i dont know lot of informations about this)
Windows yb BIOS contains a very basic informations and options (for example there is no UEFI and legacy option, there is also no ACPI enable;disable option, cpu overclocking......)
I believe there is a way to install Android stock in yb windows, i mean through reimagie the eMMC, for more infos, visit http://en.miui.com/thread-419845-1-1.html
our yoga book Telegram for devs and users:
MOD EDIT: LINK REMOVED
i will add more informations in the future:fingers-crossed: Also i might be wrong about stuff, after all its my expermints and thoughts
THE MAXIMUM POWER said:
yoga win and Android series based on Insyde bios
Click to expand...
Click to collapse
Same Bios? Not really...
jamespmi said:
Same Bios? Not really...
Click to expand...
Click to collapse
i didnt say same bios, i said both based on insyde
THE MAXIMUM POWER said:
i didnt say same bios, i said both based on insyde
Click to expand...
Click to collapse
What makes you believe the Android YB has an Insyde Bios? Not really, and as many tests demonstrated it not even has a proper ACPI implementation.
jamespmi said:
What makes you believe the Android YB has an Insyde Bios? Not really, and as many tests demonstrated it not even has a proper ACPI implementation.
Click to expand...
Click to collapse
Windows BIOS dont support ACPI implementation, that because its hidden and it need to be edited through platform.ini editor tools (inside yb win version bios), the chipset on yb win and android (so far i know both are insyde).
after all you might be correct
correct me if i was wrong
THE MAXIMUM POWER said:
Windows BIOS dont support ACPI implementation
Click to expand...
Click to collapse
It's quite the opposite...
Beginning with Windows Vista, the operating system supports only a computer with an ACPI-compliant BIOS
Android however does not use APM or ACPI directly for power management. Android instead has its own Linux power extension (wakelock).
That's why Lenovo uses a basic BIOS on those devices..
jamespmi said:
It's quite the opposite...
Beginning with Windows Vista, the operating system supports only a computer with an ACPI-compliant BIOS
Android however does not use APM or ACPI directly for power management. Android instead has its own Linux power extension (wakelock).
That's why Lenovo uses a basic BIOS on those devices..
Click to expand...
Click to collapse
Aha, didnt know this before, is there is a way to install fastboot mode alongside with bios ? i mean like mi pad 2, chuwi,.....
THE MAXIMUM POWER said:
Aha, didnt know this before, is there is a way to install fastboot mode alongside with bios ? i mean like mi pad 2, chuwi,.....
Click to expand...
Click to collapse
Fastboot is a Kernel feature introduced ages ago with 2.6.29 (2009) to allow asynchronous function calls (mainly to direct probe things like SCSI or libdata port scans). Nothing to do with the Bios.
Chuwi and some Chinese manufacturers use the special Insyde H20 Bios. Which the Yoga Book is not (by intention), the EEPROM is on a totally different basis.
@THE MAXIMUM POWER What is the best possible Android for playing around on the yoga book at the moment? I know, many things dont work for now, but if i want to try, would blissrom be the best way for now?
moviecut said:
@THE MAXIMUM POWER What is the best possible Android for playing around on the yoga book at the moment? I know, many things dont work for now, but if i want to try, would blissrom be the best way for now?
Click to expand...
Click to collapse
Yes, Bliss is the best one (till now)
Hey Man !
I'm not sure if you're still following this; but, I thought maybe I'd better ask if you're still keen on development of this as I'm a kernel dev and have very recently migrated to this lovely new tab. So , I thought maybe if you're still into this, maybe we could gather a team to work on I'd be happy to help with the kernel part as far as my experience beside the medical school allows me to :laugh:
Kind Regards
Hitman1376
hitman1376 said:
Hey Man !
I'm not sure if you're still following this; but, I thought maybe I'd better ask if you're still keen on development of this as I'm a kernel dev and have very recently migrated to this lovely new tab. So , I thought maybe if you're still into this, maybe we could gather a team to work on I'd be happy to help with the kernel part as far as my experience beside the medical school allows me to :laugh:
Kind Regards
Hitman1376
Click to expand...
Click to collapse
Hi,
You can join us on MOD EDIT: LINK REMOVED, we Need a Kernel Developer so could help us Fixing some Bugs, we are working also on a Linux that support YB
Regards
THE MAXIMUM POWER said:
Hi,
You can join us on MOD EDIT: LINK REMOVED, we Need a Kernel Developer so could help us Fixing some Bugs, we are working also on a Linux that support YB
Regards
Click to expand...
Click to collapse
I'm afraid this doesn't seem to work. I think you people should have changed the address, mate
hitman1376 said:
I'm afraid this doesn't seem to work. I think you people should have changed the address, mate
Click to expand...
Click to collapse
Hi,
Did the URL work? you can search at Telegram Lenovo yoga book and you suppose to find us:fingers-crossed:
Regards
As there is no interest nor popularity on this device to stimulate a healthy developer community, I have decided to look into ROM building and what is required. I have followed this three part video in explaining how to build Lineage OS from source to a device. I have made it to part two where I download the Lineage OS source code to my Linux work-space. Where I get stuck is adding the source to the ROM. The question now is How do I attach the Lineage OS source code to the kernel source code for this device?
Information sources...
Part 1 https://www.youtube.com/watch?v=iZmjOlUq_3c&t=1s
Part 2 https://www.youtube.com/watch?v=MGI3NSJFtKA
Part 3 https://www.youtube.com/watch?v=AJCgOHtli64&t=153s
Current Kernel source code from Asus https://www.asus.com/ca-en/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
Just ordered one. I've never built Lineage OS either, but maybe we can work together to figure it out.
I have the lineage OS sorce code ready to compile on my system. I just need to know how to add the nesary kernel with it. Any ideas?
Any progress?
Sent from my [device_name] using XDA-Developers Legacy app
Nope! Unless you have anything to contribute.
someaguy said:
As there is no interest nor popularity on this device to stimulate a healthy developer community, I have decided to look into ROM building and what is required. I have followed this three part video in explaining how to build Lineage OS from source to a device. I have made it to part two where I download the Lineage OS source code to my Linux work-space. Where I get stuck is adding the source to the ROM. The question now is How do I attach the Lineage OS source code to the kernel source code for this device?
Click to expand...
Click to collapse
I also looked into building Lineage, seems like it's going to be more than I'm willing to commit to, so I'll share what I found in hopes that it will help you or anyone else move forward with this.
I found this restored CM wiki page on the subject: fat-tire.github.io/porting-intro.html (Sorry, can't make it clickable since I'm new)
The gist seems to be that you need to make three directories in the lineage source (note z01kd appears to be the codename for the Zenfone 4 based on the build.prop file I pulled from my phone)
device/asus/z01kd - Device file tree
kernel/asus/z01kd - Kernel
vendor/asus/z01kd - Proprietary blobs
In the above CM guide, it says to use ./build/tools/device/mkvendor.sh to generate the Device file tree from a boot.img file extracted from an update.zip (from Asus) or extracted from the phone, but that didn't work with the version I was trying to do (15.1), mkvendor.sh wasn't there at all. So I explored option #2 which was to fork an existing device file tree repo from a similar device and tweak it for the device you want to port and I found that the Zenfone Max Pro M1 (X00TD) (github.com/LineageOS/android_device_asus_X00TD) is the closest lineage supported device that we could copy from (at least that I could find). It looks like you might even be able to use the same kernel as that device (github.com/LineageOS/android_kernel_asus_sdm660) because the SOCs are pretty close (Snapdragon 630 vs Snapdragon 636), but you may need to use the stock kernel that you linked to in your original post, not sure.
There's a part in the lineage docs about building from source (only for supported devices) (wiki.lineageos.org/devices/X00TD/build#extract-proprietary-blobs) about extracting proprietary blobs (wiki.lineageos.org/extracting_blobs_from_zips.html) for the vendor/asus/z01kd folder. It said that you could use a lineage update.zip, but I was able to do it with the Asus update.zip. Don't know if that will work or not, but it seems like the only option since the Zenfone 4 doesn't have a lineage update.zip to pull proprietary blobs from.
And that's about as far as I got
Once you have those three folders set up and properly configured you should in theory be able to build it.
Update 9/3/2018
I just found the device file tree and kernel for Zenfone 4 that @shakalaca used to build TWRP. Looks like there are some different naming conventions from what lineage would expect (omni_Z01K.mk vs lineage.mk), but a lot of the stuff looks to be the same (eg BoardConfig.mk) and the files that do have a different name look like they're roughly equivalent.
github.com/TeamWin/android_device_asus_Z01K - Zenfone 4 TWRP device file tree
github.com/shakalaca/android_kernel_asus_ze554kl - Zenfone 4 TWRP kernel
Between these and the above X00TD device file tree and kernel links, we should be able to get pretty close to a working config.
What if you compile what you have and see if it boots on your device?
someaguy said:
What if you compile what you have and see if it boots on your device?
Click to expand...
Click to collapse
Sorry...I already deleted the environment I had set up, to reclaim the 50+ GB of disk space.
If it's any consolation, I never made it far enough for it to build successfully.
I am trying to build Lineage OS too
In this guide(https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763)
It says we need three files(device tree,kernel,vendor) to build it.
We have kernel and device tree from github(https://github.com/TeamWin/android_device_asus_Z01K)
but we still need vendor from our device,and the commend under this guide(https://www.isthnew.com/archives/build-lineageos.html) says that we can get vendor files by running "extract-files.sh".
But where can we find that?
(Sorry for my bad English
rol.
try to look here.https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
I have tried that CLT project,but it didn't work
Maybe use this?
https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517