Database Users

[REQ] Development Environment Setup for Moto G 2014

Hey there,
INTRO:
I'm a relatively new member to XDA and the Android Community as well. The Moto G (2014) is my first Android phone since ever. I was using iPhones (4,4S,5,5S), iPads and Mac and have Jailbroken and Developed Tweaks, Apps etc for iOS.
Now that I got my hands on this amazing device, I would love to contribute to the Community by developing and porting ROMs for the Moto G 2014.
WHAT? WHY?:
So if it isnt too much trouble could someone post a device-specific instructions, checklist and downloads to setup a development environment for Moto G (2014). I'm a pretty fast learner so any crude form of instructions would suffice. With the right heading and instructions I'm sure that I can contribute to this community.
PAST CONTRIBUTIONS:
If you're curious about what I've preciously done, just Google "Krishna Sagar iPhone" and you'll see. I've developed apps, Jailbreak tweaks and I've even been mentioned and credited by CNET.com for discovering the first solid evidence about 4G in the iPhone 5. (Before it was announced or released. Yea!! )
So any help at all is appreciated! You know.. Help Me to Help You!
Regards
Krishna Sagar
http://www.krishna.bz
PS: I've searched XDA and found some tutorials but I'm looking for some device specific instructions and downloads such as Device Tree, Kernal, ROM sources etc.. and crude up-to-date instructions on how to setup a Build-Environment. Thanks

Reserved by OP:
Once I get a working set of instruction and successfully setup my Dev Environment, I will post concise step-by-step instructions on how I set it up so that others can use it as a reference.

Okay....i just learned these things past month.
So tell me where you reached so that i can guide you.

N.K.V. said:
Okay....i just learned these things past month.
So tell me where you reached so that i can guide you.
Click to expand...
Click to collapse
I am at the very beginning... From the start would be great. Like i said.. I dont want a lengthy tutorial.. I'll find the instructions myself
For eg: just say setup Android Kitchen instead of walking me through the installation setup.
I just need a crude checklist to begin. I've doing some searxhing of my own.. But like i said, i need a bit more devicr specific approach!

Device specific approach would start once you have downloaded the repo.
Till then.... Approach for all the devices would be same.
Que: You are talking about building the rom from source right??
Or you just want to modify the stock rom!?

N.K.V. said:
Device specific approach would start once you have downloaded the repo.
Till then.... Approach for all the devices would be same.
Que: You are talking about building the rom from source right??
Or you just want to modify the stock rom!?
Click to expand...
Click to collapse
Havent decided really.. Might start by porting ROMs initially.. then gradually work on my own ROM
Thanks btw for your help

KrishnaSagar said:
Havent decided really.. Might start by porting ROMs initially.. then gradually work on my own ROM
Thanks btw for your help
Click to expand...
Click to collapse
And where can I download these device repos?

For Porting ROMs : Usually ports are done from working Cyanogen build or AOSP build, which we doesn't have yet. But, k2wl and shawn are main developers working towards that. Once we get those fully working then only you will be able to port another roms.
Regarding Device Repo: It's required to build rom from source, not for porting one.
repo is a "Source Code" file, which is approx 25-30 GB in size.

REQ rooted kernel 5.1.1 for Sm-t235 (source was published a month or two back)

sometime back this was posted
http://forum.xda-developers.com/showpost.php?p=63556533&postcount=135
unfortunately moonbutt closed his thread just when I and another member posted boot image etc on the board..understand he may have moved on to better things
not knowledgeable here but appreciate if someone can take this up or redirect this to some dev who can make a rooted kernel since the source has been published
thanks

SM-T237P
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.

OKAY so now I know my posts were getting deleted when I asked for T235 kernel root
zitomd said:
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.
Click to expand...
Click to collapse
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)

mac231us said:
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)
Click to expand...
Click to collapse
mac,
i had your post removed because it was interfering in H's thread. I tried with this device a little while ago but testers seem to think they are at liberty to not follow instruction, or just change their minds mid-stream like they haven't just wasted my time and resources. . The upside would be if you have the source and the setup to compile it and thereby test your own work then, i can absolutely run you through what you need to do, The tricky part is knowing which tools you need for the packing/unpacking of the ramdisk.
If this is a qcom/msm device you will need AIK which is the best solution.
If this is a marvell variant you will need ketut's degas bootimg toolkit which is the best solution.
You need [likely] to apply the patch mentioned in my thread to security/selinux/selinuxfs.c
Be aware that samsung's source releases are usually incredibly sloppy and the defconfigs for devices are usually somewhat off, missing config settings.
Check for sdcardfs xattrs, virtual xattrs, etc . you need to make sure those are selected in order for your internal and external storage to mount.
Find the correct defconfig for your device and post it as a zipped attachment. or check my thread and look at my sources on git, specifically the commit history [msm devices mostly] to get an idea of what you need. You can get a linux os running in a virtual machine and compile just fine as long as you have all the pre-requisites installed. The getting started link in my signature is a rough/general guide to help get you up and running.
m
ps, my thread is just locked, not closed, i was getting too many OT/non-dev postings. I open it when/if i have something new and then close it again.

thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)

mac231us said:
thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)
Click to expand...
Click to collapse
mac,
no prob, recommended step 1, get your linux distro set up, stongly recoommend kali/debian 2.0, either in vm or better as 2nd os in a dual boot scenario.
m

Need help wrapping my head around building AOSP for HTC One M9

Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique

Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible

AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...

Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.

So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?

I can't help you, but that is a very good idea! Hope you can solve this issue.

Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!

I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?

Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk

Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.

If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?

Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).

Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it

Any news @vivremetrique ? Or did you drop the project?

While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.

Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand

can't help, but my hopes are so high for this one!

Devs wanted for giving birth to a Stable Nougat Rom

This thread is being made by me bcuz I don't have the proper tools for rom building(slow internet, no Ubuntu, and mainly exams).
So all the devs are requested to put forth their efforts to build nougat roms which is eligible for daily usage.
The open source kernel at this page
Direct:https://redirect.viglink.com/?forma...3.letv.cn/211/25/72/lefoss/0...OpenSource.zip
Mirror:https://redirect.viglink.com/?forma...mega.nz/#!8MF23RQB!4oqmXRNJr...2Ql74Pn_p0_3WI
I have edited the kernel but not with a toolchain, so it is not working.
If we make a stable kernel by editing it, we may be able to fix camera, VoLTE, and all the problems in the nougat and marshmallow roms.
I will get a proper internet connection in a few days. And eventually install Ubuntu in my desktop. Until then keep this thread alive mates.
So I request all the devs to make a proper Nougat ROM.
Sorry if I have told something wrong.

I can help you.
I have all the tools. I will team up with you. But the vendor blobs are so old. I have checked the kernel. Very less stability for Nougat. First, let us make a stable Marshmallow rom and wait for a few more people. Looking forward to hear from you.

OMFG

Builders thread only!!
Looking for pioneer compilers. I know I'm capable of bringing los 15.1 to kiwi but I lack the resources at this time to build.
For those who already have trees set up I can guide u through commits to make a successful compilation.
Use this thread for commits and compilation inquiries only!!
1. Check commits from los for same chipset on kernel and device config.
2. Trial build on your private tree before making commits to github.
3. Never post untested builds.
All the commits are out there. Our respective builders on los have so many other devices to build for.
I've pioneered lg and Samsung devices w help from @ShadySquirrel to unsuspecting platforms.

dave71670 said:
Builders thread only!!
Looking for pioneer compilers. I know I'm capable of bringing los 15.1 to kiwi.
For those who already have trees set up I can guide u through commits to make a successful compilation.
.
Click to expand...
Click to collapse
Not to spam but ,compilation is a thing but will it boot correctly ?

I have trees. See your PMs.

To add more detail...
We're already compiling and have plenty of logs. Everything bootloops at ROM logo. See github.com/kiwi-o

Great to see you guys trying, fantastic !

Keep up the great work guys. Maybe this will become one of those great legacy phones.

Are you still working on this guys? I haven't seen any commits for a while

TheRealIntence said:
Are you still working on this guys? I haven't seen any commits for a while
Click to expand...
Click to collapse
odds are yes, but its an old device and a crappy budget one so dont get your hopes up. i just got a 1+5t 128GB for $475 USD. i suggest you move on and find another device. the devs will probably succeed in porting Oreo but it will take along time since its not a very easy thing to do.
you should check in maybe every few weeks and if you really want oreo on this device, i suggest that you donate to the kind devs that develop for this device. btw, they do this for free so keep that in mind. cheers!

Do you need beta testers for lineage 15.1 ?

ljukigrobar said:
Do you need beta testers for lineage 15.1 ?
Click to expand...
Click to collapse
There's nothing to test, because it bootloops.