Hi everyone,
I am wanting to compile stock AOSP from the master branch per the instructions provided on the AOSP website. However, when looking for the proprietary binaries that are needed to enable hardware functionality, there are no binaries available for my Nexus 7 (WiFi, 2012). Has anyone managed to find any binaries that would be compatible that I could install into the source tree prior to commencing the build? I'm honestly not sure what I should be Googling for, if such binaries even exist. I can find binary blobs for the 2013 model (Flo), but the newest blobs I can find for the 2012 model are for 5.1.1.
Thanks in advance for all your help!
Tyler K.
Related
Does anyone have a recent or mako specific guide on how to build Paranoid Android builds, I'd like to cherry pick a few smaller features into the already powerful ROM.
Would following the OmniRom guide and basically replacing the Omni values with the correct Paranoid Android values work out? Or is there other specific stuff I need to do?
I've got Ubuntu 13.04 & currently building OmniRom whenever I see there's a bit of a decent update but other then that I'm pretty much a noob .
http://forum.xda-developers.com/showthread.php?t=1863547
Basically just clone the PA source, add the mako specific stuff (kernel, device, and vendor from TheMuppets repo) and compile. If you have any other questions just ask in the thread a linked above.
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.
Hello!
I've an older rom, that is marshmellow based. I wanted to know how to integrate security updates to it. It is a CM based AICP 11.1
Anyone know of any guides? Or Tools? I've looked through google and i dont get any answers, just what security updates do and so on.
Much appriciated, thank you.
KitsuneFoxy said:
Hello!
I've an older rom, that is marshmellow based. I wanted to know how to integrate security updates to it. It is a CM based AICP 11.1
Anyone know of any guides? Or Tools? I've looked through google and i dont get any answers, just what security updates do and so on.
Much appriciated, thank you.
Click to expand...
Click to collapse
First of all, AICP has already merged till July 2017 security patches in MM. Google has released security patches for MM till October 2017 (that was "android-6.0.1_r81") as seen here. So, afaik, for Marshmallow, you can get the security updates till r81 only.
Sync the AICP Rom repos from MM branch. I believe it is this: https://github.com/AICP/platform_manifest/tree/mm6.0
1. open the "default.xml" file and modify this line to
Code:
<default revision="refs/tags/android-6.0.1_r81"
2. you need to cd into .repo/manifests and commit the change
3. Now you can do a "repo sync --force-sync"
4. After it's done, open the AICP github page so you can see all the repos you'll upgrade.
Now you'll have to cd into each AICP repository (that's available on the AOSP page too ( https://android.googlesource.com/platform/ ).
You need to make sure you're on the default branch by running "git branch". If not, run "git checkout -b mm6.0" (replace "mm6.0" with whatever you think fit).
So, for example:
Code:
cd frameworks/base
git branch
git checkout -b mm6.0 (only if you're not on a branch, like I previously mentioned)
git remote add aosp [url]https://android.googlesource.com/platform/frameworks/base[/url]
git pull aosp android-6.0.1_r81
You'll now see the merging screen in the terminal if there aren't any conflicts. Press "Ctrl+O" then "Ctrl+X" and done.
You gotta do the same thing for all the other repositories, but with the correct aosp link for each of them.
Please note: as AICP tracks many repos from CM, Slim ROMs, DU and Omni, you'll have to make sure you are tracking appropriate branches for the repos used from those ROMs.
Hope this helps :highfive:
Nitin
Thank you, nitin! This rom is actually your edit, at least if i remember right from one of your threads. I'll have a go at getting the security patches installed on my nexus 4
Hi @nitin.chobhe
This is the rom i use. https://forum.xda-developers.com/nexus-4/development/rom-aicp-mako-t3274469
with the intergrated adaway/wakeblock/privacy and stuff.
using the OTA update doesnt give any updates, and there is no more mako listed on the AICP site.
What do i use to do the CD commands? Terminal in my android? Do i change the default xml on my phone or?
The only thing on this rom is Omni, as far as i can tell.
Unfortunately that wasnt made too clear what program i use to pull and stuff! Sorry.
KitsuneFoxy said:
Hi @nitin.chobhe
This is the rom i use. https://forum.xda-developers.com/nexus-4/development/rom-aicp-mako-t3274469
with the intergrated adaway/wakeblock/privacy and stuff.
using the OTA update doesnt give any updates, and there is no more mako listed on the AICP site.
What do i use to do the CD commands? Terminal in my android? Do i change the default xml on my phone or?
The only thing on this rom is Omni, as far as i can tell.
Unfortunately that wasnt made too clear what program i use to pull and stuff! Sorry.
Click to expand...
Click to collapse
You'll have to do a lot of reading and searching before trying to merge the security patches. It is not as easy as copy/ pasting some stuff/ files from server to your phone. Search on xda about how to build a ROM and when you build it successfully, then refer the steps I mentioned above.
Nitin
Thanks!
Since i like your specific version. I'll try my best.
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see