I get this while trying to build the rom http://i.minus.com/iWp8Diqt1SSBB.png.
OK?
Legacy hasn't pushed code for all their devices.
#stayparanoid
Related
As I get more into android development for the Nexus 6 I have yet to figure out how to update to the latest android build while leaving my local changes. So for example I am working on 5.0.0 and made changes. Now 5.0.2 is out I want to update to that build. The only I have found is going a repo init but to my knowledge this wipes out your changes. Is there a way to switch and merge your local changes?
Thanks in advance
http://gitref.org/
DSA said:
http://gitref.org/
Click to expand...
Click to collapse
So say I have a change in every git repo, would doing those commands through a `repo forall` be the proper way?
sorry, use this one instead:
http://jonas.nitro.dk/git/quick-reference.html
just an example:
Code:
Branches:
git checkout branch Switch working tree to branch
-b branch Create branch before switching to it
git branch List local branches
git branch -f branch rev Overwrite existing branch, start from revision
git merge branch Merge changes from branch
or this:
https://confluence.atlassian.com/display/STASH/Basic+Git+commands
another similar example:
Branches
Create a new branch and switch to it: git checkout -b <branchname>
Switch from one branch to another: git checkout <branchname>
List all the branches in your repo, and also tell you what branch you're currently in: git branch
Delete the feature branch: git branch -d <branchname>
Push the branch to your remote repository, so others can use it: git push origin <branchname>
Push all branches to your remote repository: git push --all origin
Delete a branch on your remote repository: git push origin :<branchname
Click to expand...
Click to collapse
It seems google released the device tree for the Nexus 5X!
Code:
git clone https://android.googlesource.com/device/lge/bullhead
Let the development begin!
Started porting the device tree to work with Cyanogenmod
THIS DOESNT WORK AT ALL YET, PLS DON'T TRY!
https://github.com/drsn0w/android_device_lge_bullhead
It was about time! May the developers be with us!
Now if only the proprietary binaries were posted...
is correct !
yes
Started porting the device tree to work with Cyanogenmod
you very geek forum but is good .
Hi. I'm trying to build OmniRom for my msm8974 phone. My camera worked at test applications in 18.02.2016. but after then never worked. repo is synced and my friend who has got very knowledge about omnirom and android development said omni has updated frameworks and av. What can i do to pass this situation?
i'm using caf and send a logcat from 18.02 build or todays build if you want.
Hi I'm just forwarding it from zukfans.eu
Trying to find interested people who want to participate in the project
Device
https://emmaus.pro:3000/emmaus/android_device_zuk_z2pro
Kernel
https://emmaus.pro:3000/emmaus/android_kernel_zuk_msm8996
Vendor
https://emmaus.pro:3000/emmaus/android_vendor_zuk_z2pro
Use cm-14.1 branch to build.
These sources don't work. The cm14.1 branch is exactly the same as cm13.0. I've already tried telling Emmaus about the issue
Edit: sources are fixed now
Hello.
I'd like to help out but I'm new to ROM building. I have a Zuk Z2 (not pro, but afaik they're pretty much the same).
I'm an experienced web developer and a novice Android app developer.
Currently trying my first "repo sync" (using the cm-14.1 branch: repo init -u https://github.com/LineageOS/android.git -b cm-14.1).
I'll then try to set up the manifest that user harsha.pic (on zukfans) gave me today and use that one.
Any advice would be helpful.
MacLaughlin said:
Hi I'm just forwarding it from zukfans.eu
Trying to find interested people who want to participate in the project
Device
https://emmaus.pro:3000/emmaus/android_device_zuk_z2pro
Kernel
https://emmaus.pro:3000/emmaus/android_kernel_zuk_msm8996
Vendor
https://emmaus.pro:3000/emmaus/android_vendor_zuk_z2pro
Use cm-14.1 branch to build.
Click to expand...
Click to collapse
If you are intrested in it you can find something here! We're already working on it but it has a lot of bugs.
https://forum.xda-developers.com/zuk-z2-pro/development/lineageos-unofficial-emmaus-t3534678
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.