CyanogenMod Dropping ROM Manager For Its Own OTA Update System - Android General

SOURCE : Kickedface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you've ever used CyanogenMod, then you already know it comes bundled with ROM Manager. That's the case for one reason: so users can quickly and easily pull updates to the ROM. However, this presents a problem of sorts. CyanogenMod is completely open source, but ROM Manager isn't. Therefore, the team wanted an update solution that will allow CM users to pull the latest builds to their devices, but is still open source. So they made their own, which will replace ROM Manager in upcoming builds.
The new updater should be available in the latest nightlies (rolling out tonight). Once you flash, head into Settings > About to set your update preferences!
This is actually a rehash of an old version of the updater from CM5 and 6 (that seems like so long ago, doesn't it?) that has been updated to work with CM9/10 and beyond.
Since push notifications for updates require Google Apps framework, the CM updater won't actually include that functionality. What it will do, however, is automatically check for updates at user-defined intervals, and pull the update once something is available.
The updater will pull directly from get.cm, so you'll always be getting official CM builds directly from the source. As you can see, it can be customized to check for new stable builds, new nightlies, or all builds from either channel.
This will be a huge improvement over any other method of pulling updates (especially manually), so we're definitely looking forward to seeing it debut. As always, however, there's no official timeline as to when it may make its way into nightlies.

Related

[10.2][official]Cyagnomod 10.2 official nightly build rolled out for some devices

Hi everyone!
Android 4.3 rolled out before some weeks, while at that time everyone was thinking about when I will get update. But you have to wait to get official update. Android 4.3 ROMs are out now. Get the best ROM which is known as cyagenomod, has built a ROM for it. As posted in their official post at Google+ they told
"CyanogenMod 10.2 Nightlies
Not sure we'd classify the smell as an "oily clutch", but to each their own. Smells like CPU fans to us.
Tonight, we are not building for every device we support - there are always some stragglers. The rest will come when they are given the green light and that will happen when they are ready.
Update your third party addons. Don't complain if you break your build by flashing incompatible (ie 4.2) zips on top of CM.
These are nightlies - meaning no bug reports.
+Koushik Dutta has fired off a batch of recovery builds as well, so updated/new CWM recoveries will be available tonight as well (http://goo.gl/Ybufgh).
As these builds are in progress (and some may fail) a full 10.2 build roster will be posted later. "
Here are some pics for it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source: +CyagnoMod
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...
The list is uploaded here.
Go to my Google drive: https://docs.google.com/viewer?a=v&pid=explorer&srcid=0B-xNAbEWF-2ldGJpUVJzVHlma1k
Check whether your device is there or not, if yes then go to get.cm
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...

[ROM] Evervolv | 3.3.0p1 [AOSP]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Evervolv?
Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Jellybean (Android 4.3.x).
Current version: 3.3.0p1
Pre-Requisites:
1. CWM or TWRP
2. S-Off, or thorough understanding of how you work around S-On to get the kernel included in this ROM flashed. FAUX, CM kernels are not compatible and will result in functionality issues if it boots at all.
3. Desire to be helpful in an appropriate manner. Logcats, dmesgs, etc are very helpful, and necessary to assist.
4. Full data wipe/factory reset
Downloads:
http://www.evervolv.com/devices/supersonic
This requires gapps for 4.3, do not use 4.2 gapps.
This post confuses me.
1> We have an Evervolv thread in original development.
2> Your link is to the speedy version (Evo Shift) even though you said spuerpsonic, your link is still wrong.
3> Neither the Evo or the Evo Shift version has a 3.3.0 release. Our current "stable" is 3.2.0p1 which is still Android 4.2.
4> That said, if your using release build, you should be using gapps 4.2. If your using nightly build, you need gapps 4.3.
And lastly, I haven't looked in a while, but unless something is changed, you either need TWRP to install the nightly build, OR you need CMW/Smelkus and you have to modify it by hand before it will install.
@ op are you even part of the evervolv team? i dont see your name any where in the maintainers list not trying to be a d1ck but i just want to be sure thats all.

[REF] ROM Pre-installed Packages Comparison Sheet

Hi all,
I combined the default installed packages on most of the popular ROMs for this phone in an easy to read spreadsheet. Now you can see what differences each ROM has in stock installed packages, for me it was useful to check if a particular system app was available on another ROM without having to install that ROM. All the ROM maintainers do a great job, it was hard to decide.
Included is the stock Motorola 24.49.18.3 (Marshmallow) ROM, compared to TrupureXMM, Temasek, Vanilla CM13, AICP, Bliss, Dirty Unicorns and the Nexus 5X CM13 ROM (as it uses the SD808 as well, some of the system and radio packages will be the same).
The motivation for this was noticing a few unrecognised system apps in the ROM I was using, then I wondered if they existed on other ROMs, or the stock ROM as well. I built the list by extracting the system .dat images and pulling the package names from the manifest XMLs to make comparing easier. It's now all scripted so adding more ROMs is quick.
Hopefully this will help some people decide on ROMs or raise some questions as to what different packages are. For example, what is com.motorola.motocit or com.verizon.omadm or com.android.sprint.lifetimedata doing on AOSP and is it required?
Full Spreadsheet can be viewed/downloaded here:
https://docs.google.com/spreadsheets/d/1YRD2NDWg9JPvOy6WMytF3HXQu69fTX-OlJfWT4MRJjg/edit?usp=sharing
Screenshot (partial):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note:
* These are just packages only, does not correlate to features, or performance/reliability, etc. Just for reference/curiosity only. Any questions about the ROMs themselves please go to the ROM thread, the maintainers have put in alot of hard work on their ROMs.
* Removing pre-installed apps may have adverse effects, also will not free up space as the /system partition has a pre-set size.
* If there are other ROMs you want added, let me know. Depending on public interest, I might add human-friendly names, or more information like permissions required / file size.

New Verizon Update (not Q/10)

So I was playing around in Verizon's ota server when I got a strange update to trigger. Software version is 21A. ... Security patch is more recent than the 20g version (June 2020 vs April 2020) .. I'm still playing around to see if there's any Android 10 OTAs they have stored. Is anyone else running this version or know anything about this update?
UPDATE: For anyone who is curious, I'm having excellent battery life on this build. I'm not sure why this OTA is unreleased... I'm assuming this will be the update that eventually bridges us to Android 10. When I first downloaded the update, I noticed it was larger than previous OTAs so I was really hoping it was Android 10.
If anyone wants to debug, test, or just have the latest security patch:
https://drive.google.com/file/d/1aPnc9gmQC_D8V46eQfYNFO365By8tP_-/view?usp=drivesdk
Or download it the way I did from Verizon's server:
https://cdn2.vzwdm.com/LG_G710VM_20g_21a_02.bin
Installation Instructions:
1. Be on latest Verizon firmware. (20g)
2. Download OTA file above.
3. Rename file to LGUP_FOTA.UP
4. Place directly onto the root of your internal storage (not in any folder, just directly in your internal storage)
5. Download Activity Launcher from Google Play
6. Type FOTA
7. Choose option one (should say test)
8. Let the OTA install to 100%, then reboot.
For root users who are curious, Magisk is working just fine on this build.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I made an Android App where you can get all custom ROMS and Recoveries (Custom-RR)

Hello there
Check out my project called Custom RR​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its an Android application to serve as the home of all custom ROMS and Recoveries.
What can you do in the App?​
1: Download official Custom ROMS builds from the respective creators.
2: Download official Custom Recoveries builds from the respective creators.
3: Instructions on how to flash Custom ROMS and Recoveries.
What will you be able to do in the future?​
1: Download Unofficial builds of Custom ROMS.
2: Download Unofficial builds of Custom Recoveries.
3: A dedicated Magisk install section.
4: Many more.
Check it out here: https://github.com/monsiu/Custom-RR
Tell me what you think!
Hi there,
Seems like a nice idea! Buuuut I need to report a first small bug:
The text for Potato AOSP in the custom ROM section is cut off after the first line, saw it on a Galaxy Note10.
Looking forward to further development.
Cheers!
Nic0_ said:
Hi there,
Seems like a nice idea! Buuuut I need to report a first small bug:
The text for Potato AOSP in the custom ROM section is cut off after the first line, saw it on a Galaxy Note10.
Looking forward to further development.
Cheers!
Click to expand...
Click to collapse
thank you i'll look into this....stay tuned on the repo for updates. Big changes coming too!
Nice project. Translations would be nice.

Categories

Resources