How to build AOSP for Motorola devices? - Moto G4 Questions & Answers

I am having trouble finding decent instructions for getting the sources for a standard build for Motorola devices, specifically for athene.
I have built for Freescale products before and it usually involves some combination of repo init and patches, but that doesn't seem to be the case for Motorola.
I know the kernel and other sources are available on Github (https://github.com/MotorolaMobilityLL), but I don't see a manifest repository there. Nor can I find a device repo.
The closest thing to instructions I found was this readme (https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-MPJ24.139-23.4.txt) (xda wont let me post links, I'm too new a user here).
I am starting to suspect that Motorola is being as lazy as possible and only fulfilling the bare minimum of open source obligations, and thus doesn't provide a device repo, or manifest repo, etc.
Is that the case? I am new to running builds for standard phone manufacturers - are ROM developers around here forced to do legwork filling in what the manufacturers refuse to publish?
Or am I just missing the rest of the instructions from somewhere?

I have the same issue, did you ever manage to successfully complete a build? Thanks.

TheGreatCabbage said:
I have the same issue, did you ever manage to successfully complete a build? Thanks.
Click to expand...
Click to collapse
Nope, my impression of the situation remains the same, though I have not re-investigated. I would like if someone more knowledgeable confirmed though.
It is a shame, as I would really like a "known good" base to work off of and put in root support and remove unnecessary softwares in a legitimate way.
You *can* build LineageOS for athene: (https://wiki.lineageos.org/devices/athene/build)
I ran LineageOS for several months, but eventually switched back to stock. Has some strange issues in regards to texting (seems to only work when making a call).

Thanks for your reply. I've just managed to build Lineage OS for my device, and it seems to work ok.
I was previously using Resurrection Remix OS (which I didn't build, just downloaded a zip) and it worked very well, so if I have any issues with Lineage then I'll try to restore my TWRP backup of RR.
I wish I could use the AOSP codebase directly, though...

Related

TLS Wifi login problems -- Cloudpath

Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!

LineageOS on Xperia X Compact?

Hi there,
does anyone know a working version of LineageOS (V14.X) for our Xperia X Compact?
The last version i´ve found is not updated since April:
https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504
Is there a newer Version?
Kind regards,
Chris
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
I'm not a developer, but I've made an attempt yesterday to build LineageOS. After several build errors (and dirty (possibly horribly wrong) hacks to circumvent them), the build completed but I was unable to successfully boot the resulting zipfile (it bootloops every couple of seconds). I then flashed the kernel (boot.img) from the older LineageOS-rom that is shared on androidfilehost, and I was able to boot the rom but the simcard isn't detected, so the rom is basically useless...
It is sad that there are no people out there that can maintain a weekly build for LineageOS. If an inexperienced builder like me can build and boot a rom it really shouldn't be that hard to improve the build.
Coirpre said:
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
Click to expand...
Click to collapse
Thanks! Could you say anything about the differences between Lineage and Omni? Omni's website is extremely sparse - no main point of differentiation, no feature list, no installation instructions - nothing. All it says is, it's AOSP "enriched", but not how. Their wiki link goes to a github page with a Code of conduct and a License Agreement - not very useful either.
Just noticed this - https://www.lineageosroms.org/forums/forum/sony/xperia-x-compact-kugo-f5321/
Plus AOSP Oreo - https://androidfilehost.com/?fid=817906626617948176
lineageosroms.org
lineageosroms.org
any more infos about that site?
looks quite impressive with the ammount of unofficial devices.
@Tom Mix: Looks to me like a lot of pointless clicking without any actual roms being offered. Seems like a scam (although I cant figure out their revenue model)

Port of lineageOS

Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help

Can I get a full AOSP build?

I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
No... You are misinformed, there is no official build of AOSP or source code available, just kernel source like many devices. This is not a developer device and Moto does not treat it as one. Even stock factory images are difficult to get at times. That said, the device is very "basic" and has few things added on top of AOSP code, it is very close to "pure".
That said, there are lots of ROM options that are unofficial, both pre-built and as source code you can build yourself.
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
I don't now if you know the unlegacy android project , it's a PURE AOSP experience, nothing extra "not required" options. I used it on my samsung nexus (replaced by the G5+) and on my nexus 7 '12 ( it runs very smooth), different devices are supported. I find it fantastic, stable and light (my nexus7 flies and it is an old device).
It will be a great rom for our potter.
acejavelin said:
No... You are misinformed, there is no official build of AOSP or source code available, just kernel source like many devices. This is not a developer device and Moto does not treat it as one. Even stock factory images are difficult to get at times. That said, the device is very "basic" and has few things added on top of AOSP code, it is very close to "pure".
That said, there are lots of ROM options that are unofficial, both pre-built and as source code you can build yourself.
Click to expand...
Click to collapse
Thank you for the info! I'll check out a different device.
tlamb96 said:
Thank you for the info! I'll check out a different device.
Click to expand...
Click to collapse
TBH... About the only choices that fit your requirements are Google Pixel or OnePlus, at 3+ times the price. Your call and good luck.
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
You're skipping a lot here, that's not how AOSP works... "For this phone" means it's already code that's been worked on by other developers, a distribution of Android (and not AOS itself). The only "official" Android source for this phone would be Motorola's stock distribution, all the others would be third-party like Lineage...
https://en.wikipedia.org/wiki/List_of_custom_Android_distributions
If you want to start your own distribution for the G5 Plus, that's a much bigger problem to solve and countless hours of work, but I suspect if you really knew about this you wouldn't have asked the question to begin with

Rom request (Dot OS)

Hello, i was in the process of finding out how to compile Dot OS rom to share here but realized that my my computer isnt strong enough to do so. Is there anyone willing to compile the rom for those of us who would like to use it? please and thanks. Also, if asking for a rom is in violation of anything please remove this post ;D
That would be great
I am actually planning to do a personal build of DotOS, if I succeed I will share it. (this only depends on my internet connection - which is slow: I will probably buy a VPS to do so).
That great yes
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: I removed my build because of some issues with system overlays
AnierinB said:
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: well here is my build based on the mentioned sources https://androidfilehost.com/?w=files&flid=279723
Click to expand...
Click to collapse
I actually wasn't planning to maintain it, you are free to do so. I successfully built my own version as well, but I have some issues with DotUICenter - basically the overlays do not work.
I am trying to download your build but AFH has a temporary mirror and it's extremely slow (60 to 80KB/s). Do the overlays work on your build?
Hello Any news about rom thanks
jet-27 said:
Hello Any news about rom thanks
Click to expand...
Click to collapse
Well I've personally discontinued work due to some overlay issues that I don't have the time to look into and fix.

Resources