Develop Bugs

[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.

Lineage OS on LeEco Le Pro 3

Hello everyone,
the question and disscussion is:
Do we get Lineage OS support in the Future? it does not matter if unofficial or official, but what do you think?
I saw the LeEco le Max 2 get some unofficial support, so it could be that some Devs will try it.
It would be awesome *_*
I think the problem is, that the community isn't that big like for the le Max 2, but maybe it will get bigger in the future.
What do you think? :good:

I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3

I think, it's not discussion, but it is a question. So, it should be in "QUESTIONS & ANSWERS". Le Max 2 have bigger community, because this phone is cheaper and cheapest Le Max 2 was for 180-200$. This mobile is older. Our Le Pro 3 have few months and in future it could have more community and ROMs like this.

corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Wooow! Someone interested?
It would be awesome!
:fingers-crossed:

Who could we talk to in order to get official support?

I dont know, but to get official support there should be at first a stable unofficial lineage OS Version. I do not know much about creating ROMs but i hope someone does and will create a masterpiece for le pro 3

I hope so

I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.

corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.

jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Would be awesome. I will try your build!
Good project looking forward to

manuelbvb said:
Would be awesome. I will try your build!
Good project looking forward to
Click to expand...
Click to collapse
I'll edit a link to the thread I make with to-dos based off the source code I can see.
Here's where I'll post progress!: https://forum.xda-developers.com/le-pro3/development/progress-lineage-os-13-t3546126

jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
robertzas said:
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
Click to expand...
Click to collapse
For Slim, please use the fork from where I get the code. See it in github. It's TS source, so it should work.

corvus said:
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
Click to expand...
Click to collapse
I forked your repo and shared it in my post. I'll work on what you mentioned. One of my top (long term) goals is complete CTS compatibility. With safetynet passed, there'd be nothing that would really pull you back to stock.

Definitely, I'm preparing the Kernel code after code to ensure we get a very clean and functional Kernel for the future, instead of just merging the one from LeEco with more than 80% of unneeded bits due to their other devices being at the same place (shameful).
This will get a ~30MB Kernel reduced to around 12MB and thus make custom ROMs perform a lot better and boot immensely faster after all.
I'd only need one sense of common attitude which is asking LeTV to keep the Kernel source up-to-date when they launch OTAs as well, I've seen some comments regarding their image stabilization fix at latest release (OTA) which is only possible at Kernel/blob level and thus if we want to have this feature working (at least partially) we need the source code "right off the bat" to get those fixes. Please, make pressure on their forums for 5.9 x720 Kernel source code and for nougat preview builds, I'd appreciate to even help with their own EUI for that matter, I'll see if I can get in touch with them concerning those points.
Do we have someone from China or someone with experience with Chinese so we can attach our discussions there?

I do hope they keep the open source up to date, but it seems they are doing the bare minimum to apply to Google's open source policy. I'm in the US, so I have the x727 with 1 SIM. We would need someone to test with a x720 as well.

@GalaticStryder, Leeco only will post the sources needed to avoid license problems with GPL, so dont wait much help from them. But we can ask...
@jts2111, I have a 720, so I can test your builds.

@jts2111
I received my X720 this week and I could also test your experimental build.
It would be nice to already start with a LineageOS custom ROM as first ROM to avoid a lot of reinstallation / reconfiguration of apps with other kind of custom ROMs.

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire

I need that so much any ETA ?
By the way keep up the good work !

Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs

Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk

great!!! thanks

Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:

thankx you great hard work and good luck my friend

I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.

drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire

but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?

xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.

@PDesire :
You're the man...keep up a good work ???

Hey @PDesire , any news? I'm sooooo hyped!!!

Thank bro I hope

Thanks for this!

So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire

PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???

Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app

Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...

Thank you very much, hope you will finish it without problems~!

[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.

Question which time can we have ROMs for xperia 10 III ?

I just can't wait anymore

Deemooo said:
I just can't wait anymore
Click to expand...
Click to collapse
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself

PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
sorry, i don't understand the system domain, i just a normal xperia user, just want to use native android likes los,dotos,rr etc. I'm sorry i can't help you, All i can do is wait, that's some sad.

PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
Yes I see xperia merge fix in sources actually for kernel sources issue compile . I will create custom kernel for start . lineage later

PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android

vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
I guess we can create repo vendor and extract proprietary blobs from stock vendor...

I tested phh gsi lineage and its fully stable guy - in bonus green tint is fixed -

Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?

Kyrimeas said:
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Click to expand...
Click to collapse
for now no . I run actually gsi phh in daily use for stability . for sources I still work on it I have worked for compile kernel xperia https://github.com/Aarqw12/kernel_PDX213/commits/aosp/LA.UM.9.12.r1 but no luck actually its bootlop only for unknow reason.

Kyrimeas said:
Are you also building recovery?
Click to expand...
Click to collapse
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.

zpk787 said:
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
Click to expand...
Click to collapse
for stability build-in is very recommanded

vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
no need vendor image, need only flash oem.img xperia give really everything . lena sodp is no completly done for now , new features need to be implemented team sodp work on it. I guess just wait more

now xperia 10 III is officially added to open-source programm
Xperia 10 III added to Sony's Open Devices program - Sony Developer World
developer.sony.com
software binary released now we can compile rom

Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?

xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.

xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
yeah，i also think we can have roms in the furture，im waiting

Kyrimeas said:
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
Click to expand...
Click to collapse
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.

xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
You can check "e foundation" GSI. It's ungoogled phones

ada12 said:
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
Click to expand...
Click to collapse
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?

xinniethewuflooh said:
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
Click to expand...
Click to collapse
GSI is no a custom rom its a Generic System image , its update only /system ( os framework ) and use blobs,drivers from your /vendor , GSI is universal and run in all devices treble .
They are no custom rom available in public actually for this devices , source for custom rom is availlable but unstable in use ( sound only in headset , ril bug ... )
actually if you want run lineage or other custom android os use PHH GSI , or wait for custom rom ( NO ETA ).