How to recreate my stable releases using manifests - Omni Q&A

I want to build a stable 4.4.2 omni, but omni codes in github had updated to 4.4.4, and I do not know how to roll back.
In CM, there is always a build-manifest.xml in its rom and I can easily roll back to the status defined by build-manifest.xml (http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests#The_local_manifest).
Then I wonder how can I get the xml file to obtain the same repos as you guys in a stable release?

Related

[Q] Devs to built KitKat 4.4 from source

Hey there!
Are there any devs that want to built KitKat from source for our find5?
Thanks in advance.
I believe all 3rd party roms for Find 5 will upgrade to 4.4. At least the active ones who keep getting updates.
brakke97 said:
Hey there!
Are there any devs that want to built KitKat from the source for our find5?
Thanks in advance.
Click to expand...
Click to collapse
As soon as aosp Master branch is being updated to kitkat, cfxe will go for it hopefully it will come soon so we can get started
A side node: omni rom uses branch :android-4-4_r1 , whats diffrent from master branch is , that is the first release, and master branch is the dev branch. If we use 4-4_r1 99% sure nothing is being merged to aosp, but when we use master branch , changes is being merged to aosp sources.
AOSP reviews by synergy

UNOFFICIAL CM 12.1 ROM FOR ALL US VARIANTS

Download Link - CM 12.1/Android 5.1.1:
Update CM 12..1 05/01 -
AndroidFileHost
Instructions:
Flash ROM(Link above)
BaNkS GAPPS - GAPPS
Donations
Please donate to keep this project alive!! It costs to maintain the hardware, Internet for the frequent updates and various fixes
Change log for 04/22 Build:
Android 5.1.1_r1
Stable Camera
USB OTG Update - This will make OTG super stable - This will be part of next release
Reboot Fix
CM Code Catch-up
Bluetooth updates
Memory optimisation
New CM SMart Dialer
Return of Silent mode
Silent mode toggle
CM File Manager update - I am not sure if anyone uses this
MMS Updates
Time to switch back to nuplayer
Things which are broken:
You tell me
*NewCM team have introduced couple of new apps which are included in this build. Check the build for the surprise
Ignore the titles of the download files, I have to fix those
XDA:DevDB Information
Lolli POP, ROM for the LG G4
Contributors
supy99, matrixzone
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-07
Last Updated 2015-05-07
Reserved
Also Reserved
What is this rom based off of? Since the U.S. Variants aren't released yet, is this a port from the G3? Or from a Korean variant?
How do you flash when you can't root or install twrp?
No kernel source and placeholders are not allowed.
Provide GPL-compliant kernel source and something to actually download and flash, and the thread will be opened.

stable / good battery custom rom for mom (no need to be Nougat)

hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
msfrox said:
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
Click to expand...
Click to collapse
Try MOKEE rom (History)...
https://download.mokeedev.com/?device=wt88047
What's the difference between history and release
msfrox said:
What's the difference between history and release
Click to expand...
Click to collapse
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
Nice thanks
History means stablest

Security Update Integration?

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.

Lineageos version explanation

while traversing the gerrit of Lineageos I observed updates of old versions and even cyanogenmod, while we have the obligation to upgrade to the next version with the update tool, is there a way to stay on a old version and take advantage of new features without fully compiling android

Categories

Resources