Develop Bugs

[Q] Compiling HTC desire roms from AOSP

Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.

You could start with building ROMs from Oxygen or CM source. That way you can familiarize yourself with the AOSP project without worrying about drivers etc. (DevNull source is completely stock AOSP with drivers for the Desire etc.)
Later on, when you know how everything works, you can start your own project.
If you want to start building AOSP from Google source, you might want to read the tutorials over at Google for a couple of times + checking the wiki's over at CM. They pretty much explain everything that there's to it.
If you're looking for a guide specific for the HTC Desire, then I think you're out of luck. Most dev's over here start off with the tutorials over at android.com and even with tutorials etc. at CM.

Is DevNull definitely 100% AOSP + drivers? If so, then it would be pointless compiling from source anyway.
I already ran that through dsixda, but the options there are quite limited.
What I had hoped I could do was make a tiny tiny AOSP. DevNull is pretty small though, so maybe it can't get much smaller.

rootSU said:
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
Click to expand...
Click to collapse
Hi Dan, for a start, the best place to start would be building a Cyanogen Rom from source as per Cyanogen's guide here. This guide is specific for the Desire
My suggestion is to build/modify this source first, since it's actively supported by a community. Once you get a fair idea, you could move on to the vanilla source..
Btw..Linux knowledge isnt crucial for building it, and you can easily follow the guide
Edit: Oops, just reallized that I just mirrored Pyr0wl's advice

[Q] Nexus 5 Factory Image Porting to I747?

Hello, I have been looking to port Android 4.4 from the nexus 5 factory image, is this do-able? Thanks guys

Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk

FabC87 said:
Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
CM11 source is now out. Some things need worked on though like CM Launcher, lock screen, etc.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Porting the kit kat ROM from the nexus 4 should work though a lot of our specs are the same. I've been trying to work on that.

There's no need to "port" kitkat to this device as Google has released source for kitkat. Just setup your device trees and make sure you have all the hardware repos necessary for this device. Then compile from source.

Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.

joemommasfat said:
Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.
Click to expand...
Click to collapse
You'll need some knowledge on compiling and messing with AOSP.
There's already a developer working on 4.4 for the i747. The Dev manages Quantum for the S3. It would be a little bit easier to build from CM11 but the code is very rough but it just did get released last night.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.

joemommasfat said:
I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.
Click to expand...
Click to collapse
This may help you building from CM. This may also help too.
A tutorial may not give you all the information you're looking for either. Its all about researching the device.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

Older versions of LineageOS?

CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?

Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.

It goes back to 6.0.1 but no further.

It will do both, apparently.....

Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk

MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.

LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."

MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol

The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.

Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk

Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris

jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.

How to create rom for OP3 ?

Hi !
I was searching for a new rom on my OP3 and i asked myself : But how did they do that ???. So I search for tutorial but I can't find anything except kitchen or obsolet tutorial. So, where can I Find a good way to learn ? The goal is to create my first custom rom.
Thanks
(Sorry if my english is bad, it's not my primary language)

Download "Brain.zip"

Elarmix said:
Hi !
I was searching for a new rom on my OP3 and i asked myself : But how did they do that ???. So I search for tutorial but I can't find anything except kitchen or obsolet tutorial. So, where can I Find a good way to learn ? The goal is to create my first custom rom.
Thanks
(Sorry if my english is bad, it's not my primary language)
Click to expand...
Click to collapse
Depending if you mean a stock based build or lineage, AOSP based etc. Stock based, you don't build, or compile. Mainly taking a clean stock build and tweaking it to what you want. A lineage based build is compiled by basically syncing source code, compile it and if you want you can cherry pick from other repos if you see extra functions, possible bug fixes etc. Most non stock builds are lineage based, compiled with some cherry picks.
There's a big difference between compiling a build a pulling others sources and actually developing. You can find numerous guides to get started with lineage, checking the wiki for whatever device they support will guide you.
You need a fairly modern CPU, recommended minimum of 8gb ram, SSD HD would speed it up, decently fast internet and when I compile I'll use Ubuntu as IMO it's easiest to get started with, tho I have compiled using ARCH as well, just took more fiddling.

https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763

I think he mean how to coding etc
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Sidenote question, in the newer nougat builds how can you repack system.new.dat? The file_contexts is no longer a plain text file but a .bin and haven't found a workaround. Any tips?
Thanks

Hi ! And first, thanks to everyone
To be more precise in my question : If I want to make my own AOSP / LineageOS rom, I have to sync the source code and, if I want, tweak it then, compile and flash it ? Or there is another way ?
And, I don't have a good computer for that. It will be more slowly but is it alway possible ?

you can start by looking at http://wiki.lineageos.org/oneplus3_build.html for building LineageOS

How to build AOSP from Google for the OnePlus 3/3T?

I'm trying to build Stock AOSP (Not LineageOS) straight from Google for the OnePlus 3/3T?
I searched for a guide, but haven't found one.
Thanks in advance!

You can't
AOSP source is available for Pixel and Nexus devices
But you can build CAF for OnePlus 3, is clean and close to AOSP
Sent from my ONEPLUS A3003 using Tapatalk

Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development

liam_davenport said:
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
Click to expand...
Click to collapse
That would be doing him a great dis-service. Buy using anothers base you dont learn everything you need and rely on others code way too much. Not to mention if a cm/los issue happens (underlying bug in their base code so you are waiting for them to fix it) This is the reason that whole project will not work.
Starting from scratch is a great start and a place everyone should start

... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.

HolyAngel said:
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
Click to expand...
Click to collapse
I mean in Biology, you don't start at the organism, you start at the atom. You start at the base and build from there.