Search new developer for CypherOS 4.1 - Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, &

CypherOS team push new crystal clean update rom 4.1 any chance to create this stuff for zukz2??
CypherOS 4.1 is finally here
A few months back we announced that we would reboot this project in a sense. That meant rebase all of our repositories and starting this project from scratch. We released builds to the community in the form of Beta updates, allowing users to test out the new form factor of this project and help fix any bugs encountered in the process. While the Beta process took longer than we expected, we're happy to say the time has finally come. We have reached a peak of stability and we're ready to start releasing official builds for all of our devices and more to come.
With Android O around the corner, and the project being forced to come to a small hiatus recently, we've decided to fix what we can release this project in it's current state, granted the helpful and positive feedback from the community. Luckily, we have a fully functional OTA system to provide updates across our supported devices for fixes and new features. While our OTA system maybe configured for Delta (Incremental) updates we have not configured it for build automation as of yet. This will come in a future release.
What's new?
We've rebased our work on top of CAF to ensure stabilty with all qualcomm devices. We are still considered an AOSP based rom, just with some CAF additions. Performance has increased by 30%, bugs in aoscp 3 are now squashed, and we took this opportunity to provide a stunning new interface,
to deliver that vanilla android experience. We've added back most of our selected features, with the rest to come in future updates. We've focused on polish and asthetics to give you a rich and minimal experience.
Luna Launcher
With Luna being rebased on the latest AOSP configuration, we've reworked this from scratch as well. We've added in a new interface to be similar to the infamous Pixel Launcher, backported the new Android O notification dot system and provided a stunning icon pack selection experience with abilities to modify the app label, thanks to Paranoid Android. We've always believed that roms should be more than just features in the settings menu, we want to give you some neat bells and whistles throughout the system itself. We've also added new wallpapers out of the box and a refined bootanimation, created by Some One
OTA Updates (COTA)
Throughout our 2 years of existence, we've always wanted to achieve the ability for incremental updates, small patches that apply neccessary fixes, reducing download times and bandwidth. There's only one system that has achieved this properly, OpenDelta. This system was created by Chainfire to supply what we've always wanted. We took the liberty to rewrite our OTA system from scratch on top of the OpenDelta system with updated fixes from +Max Weninger and the OmniRom Team. The system works, but unfortunately we must wait for our genius teammate +Aaron Nixon to automate the delta generation within our build system. So until then, full updates will push to your phone.
Key features
Here's some new key feature's we've added:
- Pie 3.0
- Immersive Mode
- OTS (On The Spot Controls)
- Pocket Lock
- Accidental Touch
- Gestures
- Button remapping
- Clock/Date Customizations
- Battery Customizations
- Feature Reset (Ability to reset OTS based features
- Color Engine
and a lot more. As many may know, we do not hold all of our features in one settings menu, we follow a stock like approach, meaning features are spread out in their appropriate categories. Features that don't have a home will be placed in our new Tuning menu. We also include optimizations for performance and battery life, such as Qualcomm's Boost Framework. A simple framework to boost CPU process in specific scenarios. Boost Framework is available for select devices that can support it such as our Oneplus lineup. More devices will support this in the future.
New devices
We're always looking to expand our roster and give everyone the awesome experience in aoscp. With that said, we've brought a few new devices to the family. These devices are:
- Lenovo ZUK Z1 Ham
- Moto Z Play Addison
- Moto G5 Plus Potter
- Oneplus 5 Cheeseburger
- Oneplus X Onyx
- Redmi Note 4 Mido
We've also dropped support for some devices, whether it be temporary or permanent.
LG G3 D855 - LS990
Redmi Note 3 Kenzo
Are dropped from our official roster. We hate to let these guys go, but they either generated issues out of our reach, or no longer had the community support to further continue development. If you wish to maintain these devices, submit the
application and we'll go from there.
Android O Plans?
We have huge plans for Android O! This will be announced soon in a separate post.
What are you waiting for?
Oh, the update.. right. You know the drill, devices are still building and uploading. Please allow up to 72 hours for your device to receive the update. There's so much more we want to tell, but it's better if you experience it yourself.
#StayClean
Wysłane z mojego Z2 Plus przy użyciu Tapatalka

Related

ROM Review || Under Revision ||

Note: I tried viewing this thread in the XDA app on my phone - mistake! The formatting goes away on the app. If you actually want to read this thread (I'm blushing, really) I recommend hopping on a computer, or at least your browser on your phone.
Post 2: Stock Roms
Post 3: AOSP Roms
*** If you're going from a stock rom to an AOSP rom, read this ***
When you flash an AOSP rom it creates a folder marked 0 on your sdcard, and once it's created, you will ONLY be able to access files in the 0 folder, whether in the rom itself or in recovery. Here's a workaround.
1) Flash back to a stock based rom (If you haven't flashed an AOSP ROM yet you're already here)
2) Using a file explorer (and making sure "show hidden files" is checked) create a folder called 0 in the root of your sdcard if there isn't one there already. Cut and paste everything else in the root of your sdcard into that folder (the one called 0). You can copy and paste if you want but it'll be slower and you'll double the amount of space you're using.
3) Go ahead and reboot into recovery. Do a backup of your current setup and then install your new ROM
4) Everything should be where you expect it to be. If you choose to go back to a stock rom, you'll just have to flash the rom, cut everything out of the 0 folder and into the root of your sdcard, and then make sure you delete the 0 folder once it's empty so that TWRP can see everything it needs to.
Explanation:
I thought it'd be nice to have a central place to see what's what when it comes to sprint Optimus G roms. At first I did this to sort of keep my thoughts straight on the various available roms, but then I thought hey why not share with the community. Also we're coming up on finals week and I have a very special type of procrastination in which I clean, organize, make threads, or otherwise do anything remotely productive that is NOT related to studying. Also also, my intention is to update this post on a semi regular basis, as the development scene is a constantly changing (improving, I should say) place for this phone. That is, assuming people find this thread useful.
About me:
College student who loves his Optimus G. I typically check XDA way more than is healthy, and bounce back and forth between most of the wonderful roms available for this phone.
Thread Etiquette: (please read)
Apparently you're a classy bunch, so I don't think this section is necessary.
Now for the meat of the post! I will not be reviewing ICS roms. Mainly because you have two choices, imperium and lifeless, and their respective jelly bean forms are reviewed here. Plus you should probably upgrade to jelly bean, it's better in most ways. If you need to root, unlock, etc, look here: http://forum.xda-developers.com/showthread.php?t=2050582
Remember, IRC is your friend. If you run into troubles and need immediate aid, go to http://webchat.freenode.net/ and join the channel #lg-optimus-g . They're very friendly over there. Also, there are guides to help you out all over the place on the forums.
Recoveries
Somebody wanted me to say a few words about recoveries, so here goes. We have two options, TWRP (Team Win Recovery Project) and CWM (Clockwork Mod). TWRP is touch enabled, while CWM requires use of volume keys and power button to navigate. Additionally, we're officially supported by TWRP. I'm not so sure about CWM (I don't even know if they do official support,etc).
Honestly, I don't see any reason to not use TWRP. Most users opt for TWRP for its touch friendliness, and ease of use. It also has a nicer UI in my opinion. I used CWM way back on my Optimus S, and it got schtuff done, but I think most of the roms and everything here are tested by flashing through TWRP. So unless you have some special reason for wanting CWM, I'd choose TWRP if I were you.
Thanks to all the devs/testers/users who made these roms possible!
Stock Based
Rom Name: Stock
Developer: Everyone's favorite South Korean electronics manufacturer, LG! (Samsung,pffff)
Link: http://forum.xda-developers.com/showthread.php?t=2176365 (in case you need to flash back to stock)
Brief Description: Not much needed here. Everybody's pretty familiar with this one!
Pros: It's what LG and Sprint want for you. They think this is just the bees knees, and if you think they have your best interests at heart, keep it! Most of the actual pros I'll discuss in lifeless.
Cons: Bloat, primarily. I've yet to meet the person who actually uses Sprint Zone. The messaging app is kind of buggy, I've heard, though since the JB update I haven't encountered much.
Major Bugs: None as far as I know.
Rom Name: Lifeless
Developer: AdriVelazquez
Link: http://forum.xda-developers.com/showthread.php?t=2083320
Brief Description: Essentially (stock) - (bloat) + (tweaks) = lifeless. If you seek (stock)-(nearly everything that isn't necessary) check out imperium. If you like stock but don't like all of the Sprint/LG nonsense, this could be the one. And if it's worth anything to you, this is probably the rom that you'll find on my phone most of the time.
Pros:
- Aroma Installer allows you to get a VERY customized rom experience. Choose boot animation, preinstalled apps, which bloat you like, launchers, tweaks, sotkeys
- Liberty Evolved kernel optional. For most up to date version, see note at end of section.
- You can get just about as close to or as far from stock as you'd like while still being stock. If you don't think you can as far from stock as you'd like to be, consider Imperium (also stock based) or an AOSP rom.
- Performance/battery options like eco-mode and power saver.
- Pretty customizable lockscreen, with the cool dewdrop animation.
Cons: (note that these aren't really faults of the rom itself, it dos what it purports to do quite admirably)
- Still looks like stock, which is only a con if you hate the stock look. The notification pull-down menu is still cluttered. The settings app is still goofy looking.
- 4.1.2, not 4.2. So no lockscreen widgets, or any other advantages that 4.2 has to offer.
Major Bugs: None. One of the more bug-free roms, and if that's something you value, you should seriously consider this.
Rom Name: Imperium Initiative
Developer: Lokifish Marz
Link: http://forum.xda-developers.com/showthread.php?t=2111607
Brief Description: This is basically stock totally stripped down and outfitted to look like AOSP. Conceived and manifested at a time when there wasn't any taste of AOSP available for our Optimus G, this rom did a good job emulating AOSP. However, it is stock based, however little it may look it. The developer behind it, Lokifish Marz, wanted me to mention that it's not really a rom, it just plays one on TV. In his words, it's "more a lightweight tuned base and series of mods for other devs and tinkerers to build and test on for their own ROMs and kernels". (If you want more info, his post is on the second page.)
However I'm going to leave it listed as a ROM, since I think that's what most users (myself included, up until mere hours ago) view it as. ROM or not, I think it's the most "barebones" option available.
Pros:
- Liberty Evolved Kernel included, though not the most up to date version. See note at the end of this section.
- AOSP look and feel, for the most part
- Relative stability of a stock based rom
- Quite nearly zero bloat
- Itsy bitsy (<500 mb) size. For reference, the stock ZVB rom is over a gig.
- Has a fun martian theme, right down to the background and boot image.
- Total feature list (copied from thread)
Almost all bloat and Google apps have been removed
AOSP/CM calculator, calendar and email replaces LG calculator, calendar and email
ES Explorer replaces LG file browser
AOSP lockscreen
AOSP 4.2 Keyboard
Jelly Bean Softkeys (change qemu.hw.mainkeys=0 to qemu.hw.mainkeys=1 in build.prop to disable)
Google Wallet
Android Tuner as system app
ROMstats added (server currently down)
Removed OTA service
Removed Connection Optimizer
Removed Qualcomm location enhancer
GPS tweaks
Liberty-Evolved v1.13 kernel (thanks Evolutionmods)
Camera tweaks (thanks _Epic)
Thermal mod (thanks Adri)
Awesome Beats Audio (Acid Audio was a major source of issues in the previous release)
Tuned to provide better battery life
Wifi scan changed to 300
Network tweaks (included tweaks for all network types the hardware supports)
Over 200,000 AdBlock hosts built in
build.prop edits and cleaning
Has my personal "loki" init.d script
Imperium standard issue default wallpaper
Martian Imperium boot animation with device info, build info and credits
Frees up tons of RAM and space in /system
Tons of other tweaks I can't remember
Cons:
- If there are any stock features you DO like, you might have to jump through hoops to reimplement them on this rom. Lifeless has the edge in that you can selectively remove things upon install.
Major Bugs: Again, fairly bug free as far as I know. While I ran it I had no major issues.
Note/Plug:
Liberty Evolved Kernel: http://forum.xda-developers.com/showthread.php?t=2181976
Developer: EvolutionMods
I highly recommend this kernel. It's very stable, still in active development, and can only help. It's currently for stock based roms only.
There's now an alternate kernel for those running AOSP.
Houcha kernel: http://forum.xda-developers.com/showthread.php?t=2246163
I haven't really used it yet but it's always nice to have choices!
AOSP-Wide Bugs: These bugs apply to every AOSP rom, aka any rom in this post.
-Camera focus: Some camera daemon keeps running when it shouldn't, or doesn't run when it should, or something. But that's immaterial, the end result is that after closing and reopening any camera app, autofocus will not work. There's a workaround that involves running a script every time you need to use a camera app. This is the biggest bug for me, and is what keeps me on stock in spite of the Play Music problems.
-Audio over headset: Some users have reported audio problems when on the phone and using a headset. On the phone meaning in a call.
-GPS: If GPS isn't working, flashing a stock rom, getting a GPS lock, then flashing back should fix the problem
AOSP Based
- AOSP based. It's the general consensus that since AOSP is maintained by Google, it is the pure android experience and is what Google thinks their operating system should be. Google's motives are for the most part believed to be more for the end user's benefits, as carrier and manufacturer modifications are either (a) well meant but poorly implemented or (b) commercially motivated and irritating. Google wants its OS to be the best in the world, and many think that it is
Rom Name: CyanogenMod 10.1 (Unofficial)
Developer (for our phone): Shellnutt2 (Other people are certainly involved, I'm just listing whoever's name is on the thread, this goes for all roms)
Link: http://forum.xda-developers.com/showthread.php?t=2189788
Brief Description: A source build (thanks jblazea50) of probably the most famous rom in the android world, though that may be debatable. AOSP goodness, plus some extras. Stable for the most part, and actively being worked on by our fabulous devs.
Pros:
- General advantages of running CyanogenMod can be found here http://www.cyanogenmod.org/about/features
- Reader's digest version? Customizable user interface, lockscreen, very themeable, powerful equalizer, and more...
Major Bugs: None. Only minor bugs, and they're being steadily ironed out.
Rom Name: EOS 4.0
NO LONGER UNDER ACTIVE DEVELOPMENT: This is not to say it's not a serviceable rom, but if you're looking for updates, look elsewhere.
Developer: teamEOS/rlasalle15
Link: http://forum.xda-developers.com/showthread.php?t=2219393
Brief Description: Another AOSP based rom, that concentrates on stability. Implements some features of CyanogenMod, and some of its own. Maintained by teamEOS. (If it matters, this is my AOSP rom of choice)
Pros:
- Full feature list, copied from original thread
NX Gesture Navigation Bar
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Custom Navigation Bar Ring Quick Launch Targets
EOS Status Bar Toggles
Navigation Bar Color w/ Project Glass (Auto-Transparency, not the Google Project Glass )
Status Bar Color
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Hide System Bars
Performance Settings
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
Eos Control Center
MORE...
- Reader's Digest version? Very themeable, like CM 10, EOS control center includes performance and UI tweaks all in a central place. The volume keys switch according to the orientation of the phone, resulting in a more intuitive volume control. Reboot options include reboot to recovery and bootloader, which is convenient if you spend a lot of time in recovery. Personally I'm paranoid about holding buttons down all the time, I don't want things to break or loosen or whatever, so software tweaks like that make me happy.
- You can turn off the screen off animation, which is something I like to be able to do. I couldn't figure out how to do this on CM10.1, please PM me or something if you know how and I'll amend this. When it's late at night and my room is dark, it's irritating to have the brightness very low but the screen off animation flashing very brightly.
Major Bugs: None aside from universal bugs.
Rom Name: AOKP (CAVEAT - I have not personally tried this rom. Take my opinions with a large grain of salt. Actually I've tried not to put my opinion in this part at all, just reporting what I've read)
Developer: spleef
Link: http://forum.xda-developers.com/showthread.php?t=2235291
Brief Description: Stands for Android Open Kang Project. Another fork of AOSP, with its own special features and modifications. It's now a source build, boots up fine, runs well. Being very actively developed, so for the latest and greatest check the thread.
Pros:
- General AOKP features can be found here http://aokp.co/
Cons:
- Again, has its own feature set, but if you're looking for particular features then make sure you do your research and check out all of the roms available.
Major Bugs: None in addition to the universal ones.
Rom Name: Liquid Smooth
Developer: spleef
Link: http://forum.xda-developers.com/showthread.php?t=2373267
Brief Description: LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave! (Quoted from thread)
What makes this ROM special?
It seems like the main differentiator with this ROM is how smooth it is, or purports to be. I tested it for a day or so, and found that it was indeed smooth, though I've yet to find a stuttery ROM for this phone. What I did notice was that there seemed to be a different set of animations, which may make things seem even smoother. It's hard to quantify smoothness, and what's smooth for me could be even smoother for you. Or less smooth. Or of comparable smoothivity. Smoov. Anyhow. Try it out.
Detailed Features:
SaberMod GCC 4.7
-O3 Optimizations
ARM Optimized String Handling Routines
Linaro and Code Aurora Optimizations
Customizable lock screen buttons/sliders
Chronus & Dashclock widgets
Customizable hardware and software keys
Transparent navbar and status bar
Customizable navbar ring
Navigation bar widgets
Customizable power menu
Notification power widget
Customizable quick settings panel
Status bar mods
Theme engine
Quiet hours
Volume rocker music controls
Full Rotation
Customizable battery and notification light
Don't enable GPS if the requesting app is blacklisted.
Add permission that allows cancelling notifications from other apps.
Notification cancellation fixes
Ensure install-during-restore is like install-then-restore
libdrm: fix bad strncpy / snprintf calls
Make contacts app aware of blacklist being disabled
Frameworks: a bit taste of android 4.3
Frameworks: add reset option to clock color and cleanup
Frameworks: activate qs and notifications toggle for navring
Correctly release lockscreen lock on tile destroy
Add an option to allow a (subtle) notification vibration during calls.
NotificationManager : Fix security exception
Frameworks: privacy guard fix UI freeze
Prevent notification acces via HALO on protected lockscreens
HALO: keep apps in recents
HALO: halo can save last position now
HALO: Minimal Style
HALO: Master Switch
HALO: Custom Colors
SMS: add middleware layer
Add Statusbar Quick Peek
Frameworks: Privacy Guard
Profiles: Add bluetooth triggers
FIx: Phablet UI NavBar in landscape
Profiles: Add 2g/3g connection option
Profiles: Add a profile picker activity
Speed up statusbar/notification drawer
Use sticky broadcast to convey torch state
Keep notification LED on while daydreaming
Add Settings shortcut to Interface Settings Activity
WebSettings: Move Liquid tag to the end of the user-agent
Show application's package name in the "App info" screen
Settings: fixed HALO options so now they stick and function
Close notification panel when swiping away the last clearable
Frameworks: Reduce Navbar, Navrings, Slimpie observer footprints
Don't bring home to the front if we're opening a floating activity
Profiles: Fix turning bluetooth on/off when its in intermediate state
Settings: Rename 'Power sounds' to 'Charging sounds' and add summary
custom PIE features
smart capture and true shot camera features
And Many More...
Disclaimer: I am merely human. I make mistakes. This guide is by no means comprehensive. If you see an error I've made, inform me! Through PM or thread response, whichever you deem more appropriate (though if you think a post wouldn't be constructive, I recommend a PM). But please do so politely. To borrow a phrase that a fellow XDA'er seems to be fond of (crwolv) and that I have become fond of as a result (fondness by association?), let's all be couth. I really really really dislike personal attacks that I see in the forums, and while I'm by no means immune to getting upset and posting in that state, I think resolving issues with another user is a great use for the PM feature.
This is sort of similar to this...
http://forum.xda-developers.com/showthread.php?t=2173532
Sent from my LG-LS970 using xda premium
I can't adequately express in writing the noise of frustration that I just made. But upon further thought, this is at least slightly different in that it goes into more detail? In the time it took me to type this, I've calmed down, decided this thread is not completely redundant. That's my story and I'm sticking to it.
_Epic said:
This is sort of similar to this...
http://forum.xda-developers.com/showthread.php?t=2173532
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Not so, as this is a review. I'd hate to see this closed cause it's great to know what to expect from a ROM and others troubles.
Great job with the reviews! I'm running CM 10.1 now
CM10.1 isn't a port. It is based on source.
stevek216 said:
I can't adequately express in writing the noise of frustration that I just made. But upon further thought, this is at least slightly different in that it goes into more detail? In the time it took me to type this, I've calmed down, decided this thread is not completely redundant. That's my story and I'm sticking to it.
Click to expand...
Click to collapse
I didn't mean any harm or "noise of frustration" that you made. Carry on!
EDIT: Just an FYI, mods will probably see this as a ROM opinion thread, which they don't like. I just don't want you to be surprised if it does get locked.
Sent from my LG-LS970 using xda premium
Good stuff. While those of use who flash frequently know already most of what is going on with these ROMs, this will here very helpful to new members as they arrive.
Thanks for your time.
Sent from my Transformer Prime TF201 using xda app-developers app
_Epic said:
I didn't mean any harm or "noise of frustration" that you made. Carry on!
EDIT: Just an FYI, mods will probably see this as a ROM opinion thread, which they don't like. I just don't want you to be surprised if it does get locked.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Oof. I hope not! I tried to keep it pretty factual. But what happens, happens. I didn't know opinion threads were frowned upon. And of course I know you didn't intend frustration
I dont know about everybody else but I actually enjoyed reading the reviews of all roms.
I hope you continue to update the first post everytime a rom updates, so we can stay up-to-date
Thanks for taking the time for a review. This should help new users coming in, as well as explain what's going on with these Roms so you don't have to read through 1000 posts.
Very well done
This was a great overview of the choice of options we have. very well written and through. I don't know about anyone else here, but I really hope we get a team nocturnal release. i loved the sony ui!
Great review
Sent from my LG-LS970 using xda premium
I appreciate the effort and time you put into this. When something big goes down such as when cm 10.1 became available, it doesn't take too long to get way behind and then have to sit and read through pages of posts. This will be a good source. Thanks
What about custom recoveries? TWRP and CWM are rather varying in functionlaities, layout, input methods ect.
TWRP vs CMW
Haven't used cwm for awhile, but twrp easy to use plus has touch screen interface. Last time I used cwm it wasn't as easy. But as with anything, it slop depends on your preferences.
Just thought I'd drop in and clarify something about Initiative. It really isn't a ROM, it's just packaged as such for ease of distribution. Like Initiative on other devices, it more a lightweight tuned base and series of mods for other devs and tinkerers to build and test on for their own ROMs and kernels. That's part of the reason it's called "Initiative". Except for a couple things, there is little difference between "Initiative" and "Agent". Also except for the bug fixes it tends to only get updated when the stock base changes.
BTW, thanks for the review/guide. It's something a lot of newcomers really need when playing with their new toy.
Lokifish Marz said:
Just thought I'd drop in and clarify something about Initiative. It really isn't a ROM, it's just packaged as such for ease of distribution. Like Initiative on other devices, it more a lightweight tuned base and series of mods for other devs and tinkerers to build and test on for their own ROMs and kernels. That's part of the reason it's called "Initiative". Except for a couple things, there is little difference between "Initiative" and "Agent". Also except for the bug fixes it tends to only get updated when the stock base changes.
BTW, thanks for the review/guide. It's something a lot of newcomers really need when playing with their new toy.
Click to expand...
Click to collapse
Updated the OP to reflect this. Among other things. And you're welcome.
Vibrate is way better on AOKP now with Trickster MOD
Sent from my Optimus G using xda premium

Cm 14 nexus 5x

Hey is there any rom for nexus 5x with android version 7.0
Here are some of the features we expect from CM14 or Cyanogenmod 14
1. CM14 Multi-window Mode
Well, multitasking is the key feature that every user is looking for nowadays. And, CM14 is all set to enhance this feature by multi-window mode that will allow the users to run multiple apps at the same time on the screen. With this split screen feature, you can also drag and drop text in between apps, when required instead of typing the content all over again or copy/pasting either.
Multi-window mode CM14
The app developers have to add support for the split screen mode to make their apps compatible to use this feature on the all-new upcoming CM14 ROM. Users can open apps side by side and resize the app window using a slider and adjust it according to their preferences.
2. New System UI in CM14
Cyanogenmod 14 may follow Android N as it would introduce a completely new User Interface that will not include the famous app drawer. If not, then the latest ROM from Cyanogenmod may allow the option to switch between the two different UIs, one containing the app drawer and the other without it. Such UI are highly favoured and seen on iOS and MIUI devices.
3. CM14 will have a Better Optimized Battery Management
Battery optimization has been the concern for Android developers as well as the community at Cyanogenmod as Android devices are highly criticized for low battery life compared to iOS devices. However, CM14 is expected to enhance its battery optimization feature that would boost the battery life up to 20% with the Doze mode as seen on Android 6.0 Marshmallow.
Cynogenmod is already developing rom for nexus 5x
is there any news about this topic...... if you have plz comment
CM 14 is coming....
I'm going to start making CM 14 UNOFFICIAL for BULLHEAD expect it to be up very soon.. :fingers-crossed: :fingers-crossed:

[SCRIPT] Build LineageOS EASY

If you are interested in building LineageOS for Bonito or Sargo you can use my script on Github to compile for either device. The script I link in this post will build my daily driver ROM. To consider running this script you will need the following:
- A PC running Ubuntu 18.04 or a distro based off Ubuntu 18.04 (I use ZorinOS)
- This PC needs at least 8gb RAM, a quad core processor and 300GB of available space on a drive (preferably SSD)
- Patience
* These are the instructions for running the script:
Open a terminal and run the following commands
git clone https://github.com/stevn4127/scripts
(This clones my scripts to a directory called scripts)
cd scripts
(This navigates you to the scripts directory)
bash lineage.sh
(This runs the script)
You will need to enter your root password to update the OS and install build tools. You may also need to run the following command with your Github credentials following the text:
git config --global user.email
git config --global user.name
Here is a direct link to my scripts repository on Github:
https://github.com/stevn4127/scripts
Join my Telegram chat for help: NugTowers HQ
Test builds and a ton of OT. We are mainly Pixel/Pixel 3a users but everyone is welcome! Just don't be a POS Please... No nudity. DONT be a pervert. (Mod Edit: Certain descriptions removed)
https://t.me/nugtowers
Good Luck!
Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)
PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)
Click to expand...
Click to collapse
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!
blksith0 said:
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!
Click to expand...
Click to collapse
I am not a developer. This is just my hobby. Lol. Thank you though. I'll be doing this stuff for as long as it's still possible. Long live the custom community!
PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project;
Click to expand...
Click to collapse
Is this skinny build box project available?
tvoneicken said:
Is this skinny build box project available?
Click to expand...
Click to collapse
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.
A followup
PGHammer said:
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.
Click to expand...
Click to collapse
I'm still shooting for the two-core target; however, as a backup, I'm doing a slightly-beefier four-core version based on the stebomurkn scripts - for the honest reason that I find them personally extremely useful.
CPU - Intel Core i5 (Socket 1151 or later)
Motherboard - any H or Z chipset that can take the same
RAM - 16 GB
HDD - 4 TB or larger
SSD - optional
GPU - optional
I'm doing a rebuild of my current system based on this spec. While my current system is G3258-based, I actually have a bigger budget than I did when I built "Baby Beastie" - my current '58 PC. The GPU will be the same GTX 1050Ti that drives "Baby Beastie" currently, as I have no need to upgrade it based on my gaming drivers. The HDD will be larger, because pricing for such has dropped dramatically. The PSU - like the GPU - is carryover (Corsair CX550M) - why replace what isn't broke? Same with the case - a full-size ATX. An SSD is an option - as my gaming needs don't require one. (My motherboard choices support both traditional SSDs and the M.2 sorts.) I'm still trying to stay under $1000USD - and I'll be purchasing everything via Amazon.com - which I did with "Baby Beastie".
ADDENDUM - Can you use both stebomurkn's scripts AND the scripts referenced in Nathan Chancellor's AOSP build guide? Absolutely - you simply need two script directories - ~/scripts and ~/scripts2; they can be in either order. (The reason why you need two directories is that you can't simply add them to the existing ~/scripts directory because it's not empty - hence you need a new place to put them - ~/scripts2.)
ADDENDUM - the core of the "skinny box" has been acquired - and it's the platter drive.
First off - why a platter drive? Platter drives are not pricey, and have gobs of capacity; further, thanks to onboard cache, they need not be snails. In my case, I went with the midrange Seagate 4 TB Barracuda Compute - which has been on sale at Amazon (AKA "Smiley's") for a mere $80USD (Prime). The Compute series is in three ranges - 2.5-inch for portables - 3.5-inch for desktops - and Compute Pro for workstations. The Compute I chose - for that $80USD - is from the 3.5-inch formfactor desktop range - which makes it physically no larger than the 1 TB previous-generation Barracuda it replaced, despite the four times larger storage capacity AND fifty percent faster (according to Windows 10) I/O performance - so much for making snap judgements! You don't need speed from a build box storage medium; what you DO need, though, is capaciousness - and 4 TB is plenty.
With the new core acquired, next came moving the data from the old drive to the new. Normally, I would use old-friend Acronis True Image; however, it has grown unwieldy in its age - so I wound up replacing it with Macrium Reflect 7. It has all the features that the older version of Acronis did - operates natively in Windows - and costs nothing.
Once you have the old data moved to the new home, re-sync your repos - remember, you have a LOT more space than you used to! (If you had a 1 TB (or smaller) platter drive, you may find yourself KICKING yourself, thinking "I was that silly in terms of lack of storage space?" Not exactly fun. Don't overeat - but don't skimp, either.)
Due to issues starting a new thread with a new post, I am making this one here; could someone with the proper access move it where it should go once I am finished? The subject involves running GSI (Generic System Image) ROMs on the Pixel 3a.
Why would anyone do so? The reasons are - unfortunately - twofold; it is getting harder and harder to find - or build, in fact - ROMs based on Android 10 and later for THE utility-infielder phone for Android 10 - the Pixel 3a. The second I have uncovered in my own running of Android 10-based GSI Havoc OS 3.8 for the past week - it is, in fact, better than the purpose-built Havoc ROM for the same hardware based on the same code - which makes not a lick of sense, but there it is.
There are two differences - Pixel Launcher is missing; instead, it uses Havoc's Shady Launcher - also, it cannot use Google Camera. Still, that is, in fact, all.
Now comes the $0.64 USD (sixty-four cents in US dollars) question - how does it run, and especially compared to purpose-built? Here's the scary part - for the most part, it actually runs BETTER than purpose-built based on the same code. The display is better. The performance is also better for the most part. As I said earlier, it makes not a lick of sense for "generic" to be better than "name-brand" - even when it comes to ROMs - yet here it is.
I have run it for the last week, and am STILL running it; either tomorrow or Monday, I will replace it with Havoc OS v. 4.1 (also GSI) for additional thrashing.
My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.
stebomurkn420 said:
My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.
Click to expand...
Click to collapse
Hi, I've tried to build Bliss using your script, and it failed at Building Kernel Image (Image.lz4) :-(
Most likely I'm the problem - I have no clue how android and Linux works nor any clue what scripts do and how they work, but since everything seemed to be working fine for a couple of hours, I hope it wasn't me (=fixable) this time. I can provide you with the log, just let me know where can I find it... Thank You!
ADDENDUM/FOLLOWUP - Can this be used with Windows 11? Yes - and with no changes whatever.

Why are you running a custom rom?

I wanted to GTFO Google and (ONE) single ROM has been developed for this phone on XDA without Gapps and it's not even maintained any more. I tried out Lineage with Micro G and I was pretty happy. I asked if anyone here would be interested in GrapheneOS and got no reply. I built it for myself and was happier with the spoofing in Lineage so I went back. But that brings me to the OP question...​​I guess I just don't understand why anyone would build a custom ROM that allows Google to spy on you completely unchecked. I thought I must have been insane since literally nobody here seemed to agree. Then I found this write up......I immediately decided to post it. Not because I want to piss people off. Not because I'm unappreciative. But because WTF ARE WE DOING??​​Why are we even running custom ROMS? Xposed came out and Google screwed us with SafetyNet. Then you had Substratum that got checked from Google but it's being "allowed" right now even though they tried to patch it out. Then Magisk comes and Google buys him out. This has always been a "cat vs mouse" game until recently. Now it's just a "cat vs customizable cat" game. Did we lose? Or is it that people would rather trade their privacy for convenience? The direction we are headed as a community is allowing Google to slowly close off and become Apple pt2 and nobody seems to mind much. But this is XDA! How will it exist without people caring about this?​​Here is part of the write up that applies specifically to the OnePlus7T. Hopefully I'm not alone. Hopefully we can get this train back off the tracks where it belongs. Barreling through the unknown in defiance of these huge entities trying to control you. Link is at the bottom of the write up.​​crDroid​LineageOS-based custom ROM designed to increase performance and reliability over stock Android for your device while also attempting to bring many of the best features existing today, according to their intro & how I think its grammar should be.
Personal remarks: A very good heavyweight ROM (and the best Limbo ROM at the moment), burdened with a soydev website (at least there's no BlockAdBlock unlike Arrow) & lack of Vanilla/GApps enforcement in a way similar to Bootleggers - no Vanilla/GApps branding
Advantages:
Per-app data restriction (Pie, A10, A11)
Signature spoofing (A10 & A11: no toggle)
Inbuilt App Lock
Disadvantages:
No signature spoofing (Pie-only; forgiven & redacted starting with A10, 12/4/2020 build)
If you look at the official site, there's a screenshot that shows this feature, on a toggle. Should have been available at Settings > crDroid Settings > Miscellaneous; but it's not there.
Tested the 12/4/2020 build & found out that microG support is enabled without toggle. This anti-feature is redacted.
Poco X3(N) only (confirmed on 23/3/2021 build) - USB debugging enables itself on boot (redacted per 22/4/2021 7.5 build)
28/4/2021 Update : With inbuilt vendor on 22/4/2021 7.5 X3N build, USB debugging no longer self-enables on boot (it's enabled at 1st boot, but can be disabled without enabling itself on subsequent boots). Welp, guess it's like the F1's Pie era all over again, where most builds (especially userdebug ones) enable USB debugging on boot until developers starts to include vendor partition in their builds.
Poco F1 (A11) : No force encryption
No Vanilla/GApps enforcement, in addition to lack of Vanilla/GApps labeling
List of GApps-infested builds :
OnePlus 7T & 7T "Pro"
Not having an active TWRP development for a device does not excuse the maintainers for releasing GApps-only releases, unless they also make a Vanilla variant. And, since there is an active TWRP development, there shouldn't be any more reason to tolerate a lack of Vanilla build (other than the maintainer being too lazy / unwilling to develop a Vanilla build, in which case per should be replaced).
Poco F3 (switched to Vanilla builds as of 9/7/2021 builds, but still listed for reference)
Redmi K20 / Mi 9T (davinci) (Vanilla build available on GDrive, FWIW.)
OnePlus 9 "Pro"
When its non-"Pro" (the vanilla OnePlus 9) variant gets a Vanilla build (despite a lack of functional TWRP for either) there is no excuse to be lazy & provide GApps-only builds
Custom ROM List
Definitely. Yaap microG by John Galt is very good also. Omni microG is also good
I read through your entire post and while most of the things you have said could be attributed to a subjective basis depending on person to person basis but the overall idea has a couple of inconveniences that I would like to add some insight of my own and would like to explain without sounding too brash
This is just my own personal impression that I have witnessed being part of the greater Android ecosystem in general starting from the early days to where we are now
In my opinion, the lack of interest by developers that originally gave their time and effort into working hard and fixing things has generally not kept up with the pace of Google's development efforts to curb these "hacks". The cat and mouse game what the post you quoted said is nearly at an end. I think Google is winning with everything in broader terms and despite the conveniences offered by microG and custom roms using that implementation, it doesn't come close to what Google offers.
The hassle of finding workarounds to make even the basic of functionality to work on Android requires time and effort which as I have already said earlier, it's something no one can commit to these days. The "enthusiast" aspect of custom rom development has really taken a dive over the past few years as manufacturers generally offer good enough functionality (at least for my use case as I am heavily reliant on my phone for work and general personal use) and Android has come a long way since the early days.
All of what I said boils down to the cost of convenience vs concern for issues that are really issues for a specialist segment of users within the entire community. People de-google their phones to focus on privacy and prevent data mining from these data hungry corporations and I for one for wish I could have something that would decrease my overreliance on Google's services but it is just not possible as the majority of people just use their phones and expect things to work just like that. So, the long lived idea of if it ain't broke, don't fix it plays very well into this. The trouble is generally not worth the inconveniences that come with it. Lack of interest of users therefore means lack of options and thus a lack of development.
Here's my 2 cents
I think for devs or hobby-coders who do this for free, time is more valuable than the luxury of "privacy" (which doesn't really exist if you're using any form of social media, like XDA).
Things changed. Android is more polished now than the Nexus days.

General Current state of AOSP - Lineage/Pixel Exp/Etc...

Wanted to write a thread to give feedback on where AOSP devs are currently at with AOSP ROMs for those who are interested. Don't want you to think that there is no development in this area.
While there are GSI out there, I think ROMs built from source are the better option.
While GSIs are meant to be that, generic, I don't think this is a proper replacement for ROMs since there are many brands it tries to encompass and not to mention, the GSIs devs may not be able to fix bugs for your particular device or brand, it's just the nature of GSI.
Anyway, we currently have a secret testing group where almost daily builds are pushed, trying to polish the builds and fix some of the bugs that are still present. It's getting closer and closer to being bugless.
Here's the current state of AOSP ROMs for A52s:
Working:
- Bluetooth
- BT Audio
- NFC
- Casting
- Vibration
- Brightness and autobrightness
- Display at 60/120hz
- Audio/Mic
- Wifi/Tethering
- All Cameras (rear camera @ 4k 30fps)
- Face unlock
- Factory reset
- Pixel Features (unlim. google photos, game booster...)
- AOD & At a glance widget
Not working:
- RIL
- Fingerprint (only unlocking is broken)
Sensors:
Accelerometer: working
Geom. Field: working
Gyro: working
Light: working
Proximity: working
Gravity: working
GPS: working
The following devs have done an amazing job for AOSP development on this device, I know with their combined contribution, we'll soon start getting stable trees which will lead to better and more stable ROMs:
@Alone0316
@PauloWesley
@BlackMesa123
@Simon1511
@Ryzen5950XT
And of course special thanks to all the testers which have to reset their devices almost daily to get these tests done. You guys are a part of this too. I'll continue to update this thread when anything major breakthrough happens and/or it's stable for release. Most of this doesn't get reported on outside the testing group so I wanted to give this feedback so that users don't lose total hope on this device for people who love AOSP.
LOVE IT
Hats off to all the people trying hard to put a52s in development radar
!!!!!!!
Nice team work
Waiting for official lineage
AOSP? Love it.. very appreciate for those who will make it happens.. salute
thank you for the update, can't wait
Keep up the good work you guys
Is there a possibility to put Samsung apps (Like Samsung Store) in the AOSP version?
heal3r said:
Is there a possibility to put Samsung apps (Like Samsung Store) in the AOSP version?
Click to expand...
Click to collapse
Only AOSP-compatible apps can run on non-Samsung ROM's, such as Galaxy Watch, Samsung Health, Samsung Internet etc.
BlackMesa123 said:
Only AOSP-compatible apps can run on non-Samsung ROM's, such as Galaxy Watch, Samsung Health, Samsung Internet etc.
Click to expand...
Click to collapse
Oh that's sad. I love aosp but I can't give up Samsung Store for now. Guess I'll stick to samsung roms for now.
excellent news. i was always wondering why a hugely popular devices as A52s did not get proper custom ROMs yet, good to hear there is progress being made.
Will the official pixel experience repository be uploaded?
ShaDisNX255 said:
Wanted to write a thread to give feedback on where AOSP devs are currently at with AOSP ROMs for those who are interested. Don't want you to think that there is no development in this area.
While there are GSI out there, I think ROMs built from source are the better option.
While GSIs are meant to be that, generic, I don't think this is a proper replacement for ROMs since there are many brands it tries to encompass and not to mention, the GSIs devs may not be able to fix bugs for your particular device or brand, it's just the nature of GSI.
Anyway, we currently have a secret testing group where almost daily builds are pushed, trying to polish the builds and fix some of the bugs that are still present. It's getting closer and closer to being bugless.
Here's the current state of AOSP ROMs for A52s:
Working:
- Bluetooth
- BT Audio
- NFC
- Casting
- Vibration
- Brightness and autobrightness
- Display at 60/120hz
- Audio/Mic
- Wifi/Tethering
- All Cameras (rear camera @ 4k 30fps)
- Face unlock
- Factory reset
- Pixel Features (unlim. google photos, game booster...)
- AOD & At a glance widget
Not working:
- RIL
- Fingerprint (only unlocking is broken)
Sensors:
Accelerometer: working
Geom. Field: working
Gyro: working
Light: working
Proximity: working
Gravity: working
GPS: working
The following devs have done an amazing job for AOSP development on this device, I know with their combined contribution, we'll soon start getting stable trees which will lead to better and more stable ROMs:
@Alone0316
@PauloWesley
@BlackMesa123
@Simon1511
@Ryzen5950XT
And of course special thanks to all the testers which have to reset their devices almost daily to get these tests done. You guys are a part of this too. I'll continue to update this thread when anything major breakthrough happens and/or it's stable for release. Most of this doesn't get reported on outside the testing group so I wanted to give this feedback so that users don't lose total hope on this device for people who love AOSP.
Click to expand...
Click to collapse
Finally yessss
You are my only hope custom ROMs
I just bought this phone and it was a big mistake.
-It's full of bloatware
-There is 0 customization unless you register a samsung account
-The volume slider is only 15 steps instead of 30 so music is either too loud or too quiet for me
-I can't skip tracks by holding down the volume keys
-The notification at the top of the list doesn't get extended automatically
-When I view the opened apps it switches off the app I'm currently in. (SUPER ANNOYING)
Other than that there are actually a fiew things that are really cool:
-I can turn off the app drawer
-The camera app
-Full black background theme in samsung default apps (like calculator, messages, calendar, etc..)
-The calculator has some cool features
-No navigation bar at the bottom with gesture controls
-Keyboard can be positioned to the bottom of the screen without a gap.
FelixVyra said:
-I can't skip tracks by holding down the volume keys
Click to expand...
Click to collapse
You can download the Sound Assistant module from the Galaxy Store
FelixVyra said:
The notification at the top of the list doesn't get extended automatically
Click to expand...
Click to collapse
You can download Good Lock + QuickStar to have this activated
I think yeah you will need a Samsung account but I'm not sure
Oh! That would be awesome!
I switched from OP3 with HavocOS to A52s in May and... it's been "fine" but I do miss custom AOSP/Lineage features...
Any news about that?
No news, development has slowed down a bit
ShaDisNX255, thanks for the update. Please keep us updated. I keep checking daily for any news. If the development stops or slows down a lot to the point where it's months away before it's ready then I would go with your Android 13 ROM. I prefer bare bone simple ROMs but at the time I don't want to wait years either especially if your ROM is very good and ready to be installed. So if you come across any news please let us know. Thanks.

Categories

Resources