Develop Bugs

[ROM][Linux] Ubuntu Touch Preview on TF300T [WIP]

I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet.
The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet.
I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.

Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.

Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium

Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.

matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.

ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...

How did you load the patch in your make file? I am adapting your patch to my device.

secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.

giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?

Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2

What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?

matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.

Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.

It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files

f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github

-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.

Guardian Rom [Secure] [Privacy] [Beta]

Guardian Rom by x942​Thanks to:​
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?​
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?​
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:​
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
​
Click to expand...
Click to collapse
How to use:​
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:​Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.​

always been curious about this rom, so I may give this a whirl! thanks for the hard work!

Any reviews?
Sent from my Nexus 7 using Tapatalk 4 Beta

Since these NSA Android stories are rolling out there might be more traffic coming this way.
SAMSUNG S4

Will this be available for an unbranded international S2, GT-I9100 ?
I am currently trying out CM10.1 and installed most of the included apps manually, but there is a problem with encryption and updating the nightlies and CWM, so I'd like to try out Guardian Rom.

danw1028 said:
Since these NSA Android stories are rolling out there might be more traffic coming this way.
SAMSUNG S4
Click to expand...
Click to collapse
Those stories are FUD. Don't believe them. The only code the NSA put in android is SeLinux which hardens android. It's opensource and has been in linux for years.
MrWil said:
Will this be available for an unbranded international S2, GT-I9100 ?
I am currently trying out CM10.1 and installed most of the included apps manually, but there is a problem with encryption and updating the nightlies and CWM, so I'd like to try out Guardian Rom.
Click to expand...
Click to collapse
Not for now. Nexus device get primary support as they have an AOSP Source tree.

A very worthwhile effort. I wish I would own one of the supported devices to see how it goes.
I hope that more developers will start to put liberty and privacy into Android.
Keep up the good work.

zurpher said:
A very worthwhile effort. I wish I would own one of the supported devices to see how it goes.
I hope that more developers will start to put liberty and privacy into Android.
Keep up the good work.
Click to expand...
Click to collapse
More is coming soon. Guardian Rom is going to be on more device soon, We have a working once-click installer for all supported devices at this point, easy setup for Full Disk Encryption and Deniable Encryption, Policy Management and more. We are about to launch for a round of funding so stay tuned. Things are going to get exciting.

Dead?
Is this project dead? There is not much information on their site and its out of date.

I cant seem to find a download link for jflte

sonymsam said:
I cant seem to find a download link for jflte
Click to expand...
Click to collapse
To be honest, I hope these guys are okay. Privacy rights are important and these guys are also helping protect whistle blowers. Given that, I hope they haven't been whisked away to a black site. Yeah, that's a paranoid statement but not outside the realm of possibility.
.

sorrow777 said:
Is this project dead? There is not much information on their site and its out of date.
Click to expand...
Click to collapse
sonymsam said:
I cant seem to find a download link for jflte
Click to expand...
Click to collapse
Locoman_ said:
To be honest, I hope these guys are okay. Privacy rights are important and these guys are also helping protect whistle blowers. Given that, I hope they haven't been whisked away to a black site. Yeah, that's a paranoid statement but not outside the realm of possibility.
.
Click to expand...
Click to collapse
Looked into this project earlier. You can't find a dl link for jflte because it's only currently got beta release for the nexus line. The guy has a page on Kickstarter trying to raise 35 thousand dollars to support development. He promises to make a stable build and support more devices only if his 35k support fund is together by april 30th. Don't think it's gonna happen bc he's only at 1500.

sonymsam said:
I cant seem to find a download link for jflte
Click to expand...
Click to collapse
I take it this ROM is dead?

Milamber said:
I take it this ROM is dead?
Click to expand...
Click to collapse
If it is don't take it!

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13

Reserved

Edit 1:initial build didn't boot for me, no adb can't get log

Ok im gonna try it.
If you want, i can leave logcat for you

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.

Ofc, it doesn't boot. And don't create threads without testing.

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought

Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

[WIP] [Looking for help] PostMarketOS on the Xiaomi Mi A2 Lite

PostMarketOS on the Xiaomi Mi A2 Lite
KEEP IN MIND THIS PROJECT IS VERY WIP AND I'M LOOKING FOR HELPERS TO GET A WORKING OS. THIS IS IN NO WAY SHAPE OR FORM A FUNCTIONAL ROM AS OF NOW.
I'm trying to make progress on running postmarketos, a linux distro for various devices including android phones, on the Mi A2 Lite.
I have gotten a lot of stuff to work such as: ssh, screen, Weston, usb, and more stuff. The repo is not updated yet, but will be updated soon.
My progress is logged on this Github repo: https://github.com/matthew-5pl/pmos-xiaomi-daisy
If you feel like helping, write a comment here! There are instructions on how you can help on the github readme.
The requirements are:
A linux machine with the necessary tools installed (pmbootstrap etc.)
A Xiaomi Mi A2 Lite (i have the 4GB ram model, so if you have the 3GB one your mileage may vary) with an unlocked bootloader and access to fastboot and twrp
20-30 Minutes to compile the kernel
The current focus is getting the touchscreen to work.
If you get any further than I did, make sure to make a pull request on the Github repo!
Thanks for reading and good luck :fingers-crossed:!

Interesting project

interesting
i will look at this project, when i take a time

Update:
Weston works!

Matt 123456789 said:
Update:
Weston works!
Click to expand...
Click to collapse
Congrats! Though I think this project is somehow approached backwards. As I've seen on the wiki page all devices can have a screen but only one does the basic functionality of a phone, calls, wifi, gps, camera, sound and such and it's probably the device for which the OS was developed. Honestly I would've been more enthusiastic about this project if it only worked in terminal but had all those functions working. GUI is the easy part these days (that's not a comment on your work).

celrau said:
Congrats! Though I think this project is somehow approached backwards. As I've seen on the wiki page all devices can have a screen but only one does the basic functionality of a phone, calls, wifi, gps, camera, sound and such and it's probably the device for which the OS was developed. Honestly I would've been more enthusiastic about this project if it only worked in terminal but had all those functions working. GUI is the easy part these days (that's not a comment on your work).
Click to expand...
Click to collapse
This is my first experience dealing with compiling kernels, patching drivers etc. so I'm pretty happy I got the framebuffer to work at all. To each his own though!

Matt 123456789 said:
This is my first experience dealing with compiling kernels, patching drivers etc. so I'm pretty happy I got the framebuffer to work at all. To each his own though!
Click to expand...
Click to collapse
Which is commendable, that's why I said "that's not a comment on your work". I was referring to PostmarketOS project in general.

celrau said:
Which is commendable, that's why I said "that's not a comment on your work". I was referring to PostmarketOS project in general.
Click to expand...
Click to collapse
Oh ok!

Ho Postmarketos is interesting project ))
I will compile and test for curiosity
Matt 123456789 said:
PostMarketOS on the Xiaomi Mi A2 Lite
KEEP IN MIND THIS PROJECT IS VERY WIP AND I'M LOOKING FOR HELPERS TO GET A WORKING OS. THIS IS IN NO WAY SHAPE OR FORM A FUNCTIONAL ROM AS OF NOW.
I'm trying to make progress on running postmarketos, a linux distro for various devices including android phones, on the Mi A2 Lite.
While I have gotten two different kernels to compile, (daisy-q by xiaomi and kernel_loki by Aarqw12) and the device to boot both, I have not been able to get to a desktop environment to load.
My progress is logged on this Github repo: https://github.com/matthew-5pl/pmos-xiaomi-daisy
If you feel like helping, write a comment here! There are instructions on how you can help on the github readme.
The requirements are:
A linux machine with the necessary tools installed (pmbootstrap etc.)
A Xiaomi Mi A2 Lite (i have the 4GB ram model, so if you have the 3GB one your mileage may vary) with an unlocked bootloader and access to fastboot and twrp
20-30 Minutes to compile the kernel
The current focus is getting the display/framebuffer to work, to be able to load a desktop or mobile environment, as well as getting functional ssh and telnet connections.
If you get any further than I did, make sure to make a pull request on the Github repo!
Thanks for reading and good luck :fingers-crossed:!
Click to expand...
Click to collapse

Update: Ssh working. Looking for help with patching the touchscreen drivers.

Hi , I can pm you in xda or discuss in telegram app ?
Matt 123456789 said:
Update: Ssh working. Looking for help with patching the touchscreen drivers.
Click to expand...
Click to collapse

ada12 said:
Hi , I can pm you in xda or discuss in telegram app ?
Click to expand...
Click to collapse
Sure, add me on telegram: matthew5pl

Closing thread as a better port of PMOS has been made for daisy.

[ROM][UNOFFICIAL][10] e/OS 0.22 q for Motorola One xt1941-4

Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!

Works just fine, thanks.

LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!

Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian

01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.

Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'

xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...

HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.