Announcement of Jafier Roms - General Topics

Calling up and all the moderators at XDA we have started our project and those who are interested opportunities
The name of the ROM is JafierRoms and we have intentions to make it available for vast number of devices including those omap4xxx devices as well as those device which have safetrap and locked device which can run 2initd recoveries as well
Our source is based on CyanogenMod 11 and as soon as the source get finalized and cleaning up is done we would start a build for the nexus series as the latest once even the tabs too ,lg g2 ,etc.
As soon as the cleaning up is done u ppl will be able too see builds on JFtexx and all the JFs
s3 variant and tabs will followed too
To james carter I request if we can have a space in custom ROM centrals and can be displayed at the portal so we get intiallized and funded
we will only have the beta versions for this month.
Followed by weeklies and all things done and up 2 months from now ppl can see nigtlies as well
Members and core team
Mohhamad Rehan Madhar (founder)
Raj P (initializing the source forks)
Akshay Chordiya (Developer of apps such as jafier, active notifications and Automaton)
Jishnu Sur (feature porting and camera enhancement)
Adarsh or Audio God ( developer of Sensonic HD Roms and Our community maintainer would not maintain any devices)
Mao Chenxi (fixes here and there)
Napstar (for Xperia devices)
Planned members to include:-
Mohhamad Abid (developer of switcher)
RSen ( developer of Open mic+)
And philz if he agrees can't contact him though
Features:-
1)Stock cm features
2)active display replaced by active notifications and enhancement to make it more like MotoX. As the app by Akshay was made open source
3) full automation on Locking and unlocking the devices and hand and wave gesture there won't be a app but code for this which would be placed in framework and SystemUi, even the gesture would work in gallery
4) Power shell Replaces Superuser
5) a feature in security would be placed which will be like whenever a wrong pin or password is detected at the keygaurd a photo and location of the device would be sent to ur email address
6) A launcher which would never have the skin like the aosp or trebuchet launcher but will be based on Aosp launcher
7) stock icons will be replaced by something new
Planned features :-
1) active notifications and touchless control like feature may get integrated in the nightlies (yes toucless control is possible with pocket sphinx)
2)our very own gapps with Aroma installer where selecting the Google now launcher would be optional
3)delta update app can be created if we get funded and able to get Jenkins server I am bankrupt
4) Our touch less control gets integrated with Google Now that's why there may not be a need of the Gel Launcher
5) don't get over excited we won't have every feature of Moto X or any other phone
And finally nothing from omni and any other Roms only small and tiny fixes to dalvik bionic and art would get cherry-picked
And speaking of cherry-picks we will have gerrit code rewiev by March 10 for sure
Our source is located at
https://github.com/JafierRoms
Sent from my Nexus 5 using XDA Premium 4 mobile app

Regardless of how you call them, placeholder threads are not allowed on XDA. Please feel free to open this thread again for supported devices, in the correct areas, once the ROM is ready. Thread closed.

Related

Are there any Jelly bean 4.2 roms in development?

I was just curious if there are any android 4.2 roms in development for vzw sgs3 cuz i have the keyboard and im sure the phone can run it
Sent from my SCH-I535 using xda app-developers app
No.
From the Cyanogenmod Google+ Page
11/19/12
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, +David van Tonder decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
11/13/12
What's next?
Android 4.2 is getting the OTA treatment from the powers that be. We eagerly await the source to hit the AOSP repos. When it does, we will begin the task of defining what is new, what has changed, and what CM features should stay (or go). We already anticipate removing the CM enhancements to the Clock app (Google made their own), and enhancing the Quick Settings (most likely not porting over the Notification Power Widgets). However, these assessments are preliminary, and won't be finalized until MR1, or whatever tag is used, has the source to go with it.
Edit: Oh and yes, before its asked, 4.2 will be CM 10.1 (not CM11).
Click to expand...
Click to collapse

Multiple Suggestions

First of all I want to applaud the integrity of the team working on OmniRom and for standing for software freedom. As the only GPL ROM on the phone, I believe it will reach a certain prominence once critical mass of functionality is achieved. I have some suggestions that I was hoping to get feedback for from the Devs here.
1- What is the possibility for devising an in-place upgrade system that works across future OS version upgrades for major changes in AOSP? (something akin the upgrade systems of current GNU/Linux systems)
2- Incorporating apps from the guardianproject (.info) a privacy and security oriented group that make secure messaging apps and TOR for Android. That will be our anwser to the so called secure chat of CM.
3- Cooperation with the largest FOSS software repo F-Droid and perhaps including it as a default app repo option for OmniRom.
4- Now this is a big one, but as a distro that prizes Software Freedom and the GPL above all else you are in a unique position to be a demo showcase for incorporating the major app frameworks being ported to Android like Qt and Gnome. Arranging with the devs from KDE and Gnome to make this a reality would be a major milestone for the FOSS movement's efforts to bring free software in an environment that is being increasingly closed off like what Google is doing with their absorption of features in proprietary apps and the treachery of the CM turncloaks.
Casual observer here. I don't think it's accurate to call it a GPL ROM given how many non-free drivers are required to get working WiFi and so on. OmniROM encourages GPL as a way of keeping the community honest but I don't think it's set in stone.
1. upgrades on Android don't happen in same way as GNu/Linux: it's always a fresh install. CM already does this, or you can use recovery mode.
2. good idea! more generally, system wide proxy settings which would allow all traffic to go through Tor. Tor is one part of remaining anonymous, the browser needs to be locked down for example. Guardian Project say that their companion browser, Or web, doesn't work on Android 4.4, and they might stop developing it. There are other Android techniques for anonymity e.g. xprivacy.
3. F-Droid builds and signs apps, it's hard to see room for cooperation. It will soon have ability to install apps silently if part of a ROM. They dropped their Android.mk; looks like time to bring it back, maybe with package name change option.
4. Qt was announced on day one at the BBQ!

[5.0+] Slab, A Cyanogenmod Dashclock Host project

I have a knack to take up old android projects that have been left in the dust and see if they have potential with our current devices and most used Android OS. This current project takes place of something that some of us remember and some of us that never even knew that it existed because the basic functionality of it was eh... So...Here we go.
Welcome to the Slab Open Beta! Slab is currently in development and you will encounter things of un-natural application behavior or just not working.
Slab is a fork of CyanogenMods CMhome application from cm11 rebooted as a Material application and supporting On-Tap on Android 5+. Android N is not officially supported at this time, more testing is underway. Slab will be open sourced in do time once everything is back to working order. My goal is to see this application back in CyanogenMod builds but I'm probably asking for to much.
Slab is a Dashclock extension host application that uses Dashclock widget apps and showcases them in a dashboard like approach. Use the most right fab to clear the "Slab" and use the most left fab to refresh the "Slab". Use the middle fab to bring up a bottom menu of which has a built in Google Search method for users who want to replace Google On-Tap with Slab. To set Slab as a On-Tap application, navigate to the app settings in the android setting and select the menu item default apps, than select assist apps and choose voice application as Slab. If the "Slab" is clear on launch, simply press the clear fab and refresh fab.
Current Issues:
Slab is still experiencing some force closes on entering and exiting so just ignore those until I find methods around them. Click on the Check menu item to exit the application without it hanging and causing errors after you've exiting and it monitors Dashclock Extensions successfully.
Some Extensions are locked to Dashclock Widget which is running out of date and I hope 3rd party extension devs take the time to understand this and allow them to be more free for apps like Chronus and Slab.
I want Slab to operate without the Dashclock Widget app installed.
Goal is to allow it to monitor Extensions without the use of Dashclock Widget installed.
Contributing:
If you'd like to contribute and have free time, I'll push this to github sooner than I plan to only if devs actively want to contribute. I don't want a grab and go operation. If no one wants to contribute than be patient with updates as I maintain other more important projects. This one is just for experience and free time.
Works well on AOSP and CyanogenMod firmware. Im building this application using Android Studio on Ubuntu 16.10, A Nexus 7 2013 with an AOSP 7.1 rom I built myself (Usually flashing different roms for different project reasons), my HTC10 and ofcourse the Virtual SDK.
Again, Application is not complete so some things are either not working correctly or null.
Join the Google Plus Group for bug reports and other community information.
Google Play Link
XDA:DevDB Information
Slab, App for all devices (see above for details)
Contributors
Nx Biotic
Version Information
Status: Beta
Current Beta Version: 1.10.11
Beta Release Date: 2016-11-06
Created 2016-11-07
Last Updated 2016-11-07
https://youtu.be/L5ZQaj3eQRg
Small demo of the application running. Found that heavily modified or skinned firmware have a hard time running this app. Android 7 has a hard time using the Dashclock host, probably need to build a helper app.
Troubleshooting
The app is not 100 percent yet and you may come to install it and it may seem like its not working but its just hanging and confused so here is a tip to get it working.
Go ahead and Uninstall Slab. Install Dashclock Widget and a few Dashclock Extensions. Now install Slab and check your results.
I may take some time and develop a helper class to replace Dashclock Widget as it seems to be getting outdated. I wish Dlab to be a replacement.

Vote for upcoming Custom ROMs for Redmi Note 5 / Redmi Note 5 Pro

Hi,
I just want you all to vote for your favourite custom ROM for Redmi Note 5 / Redmi Note 5 Pro. This will help the developer community to better understand the general public demand.
Here is a short description f each type of custom ROM given above(may not be in same order!)
1. LineageOS
We start off with the biggest name in the custom ROM scene – LineageOS. While many of you might not be familiar with the name, LineageOS is actually the same custom ROM that started as CyanogenMod. Back in the fall of 2016, Cyanogen Inc. announced that it was discontinuing development and shut down the infrastructure behind the project. Since then, the developer community has kept the project alive, but under the name of LineageOS. Built on top of Google’s AOSP code and adding their own custom code to it, LineageOS works as a standalone ROM as well as the source code for many other custom ROMs out there. It has the biggest developer team under its name and officially has support for over 190 devices. The ROM includes basic but useful features that include but are not limited to customizing the status bar, changing the overall theme, editing the navbar and much more. While Google’s AOSP is barebones, LineageOS gives it a sense of customizability while maintaining stability.
The ROM offers builds for Android Marshmallow (6.x) and Nougat (7.x), with support for Oreo (8.0) coming soon. Also, the list of officially supported devices includes offerings from Samsung, HTC, Motorola, LG, Xiaomi, OnePlus and more.
2. SlimRoms
If minimalism is what you’re looking for, SlimRoms is right up your alley. Possibly the lightest and most functional custom ROM out there, the SlimRoms project is based on the AOSP code while adding useful tweaks to it. The most notable features of the SlimRoms project is the inclusion of the Slim Recents and the Slim PIE. The recents alternative is used to display the recent apps in a sidebar, as opposed to occupying the entire screen. The PIE, on the other hand, comes as a navbar replacement, that proves to be highly useful when using your device in Immersive mode. Other SlimRoms features include a custom dialer, custom Quick Settings tiles, lock screen shortcuts, Privacy Guard, and more. The SlimRoms project offers simple and minimalistic transitions that end up resulting in a clean and neat interface, that can further be customized should the user choose to.
SlimRoms have been around for a while and is available on all major OEMs such as Google, LG, HTC, Moto, Samsung, Xiaomi, OnePlus and more. The latest supported version is Android Nougat 7.1.2, and a build for Android Oreo (8.0) is expected to be released soon.
3. Paranoid Android
Another great ROM that doubles up as a source for many other custom ROMs out there, Paranoid Android is one of the most acclaimed custom ROMs of all times. The development team focuses on bringing a polished and refined experience while using minimum resources. While it may not boast of the plethora of features and customizations that other ROMs offer, Paranoid Android or PA, does promise a soothing user experience overall. It comes with its own unique features such as Hover mode, which allows the user to view and interact with their notifications from any screen, (which was then integrated into AOSP as part of Heads-up notifications). It also offers its own version of the PIE menu, as well as a fully immersive mode for Android. Paranoid Android has long been regarded as the main project from which Google has brought over a lot of features, one biggest feature being the Ambient Mode, which was present in PA as Peek.
While PA did experience a few bumps lately, causing the development scene to slow down a bit, it is now back and is better than ever, with officially supporting Android Nougat 7.1.2, and support for Android Oreo 8.0 to be released soon. It’s available for devices from Nexus, Pixel, OnePlus, Sony, Oppo and more.
4. Resurrection Remix
For all those users who like to boast about the tons of features that their device has, you can’t do better than Resurrection Remix. Probably one of the most famous custom ROMs out there, Resurrection Remix (RR) has been around for a long time now and is preferred by a huge number of people. RR’s ideology has been to offer the maximum number of features available to the user, and it delivers it in a great fashion. It uses AOSP, LineageOS, SlimRoms, and Paranoid Android; all as its main source code, and then adds extra features to it. While most ROMs cherry pick selected features and add them to their code, RR adds just about anything and everything there is to offer. This does, of course, come at a cost. The ROM itself is quite hefty and seems to be a bit heavier on system resources. Also, having tons of features all mixed up in the code do end up making the ROM unstable at times.
RR currently supports all major devices from manufacturers like Samsung, HTC, LG, Moto, Lenovo, Huawei, OnePlus,and more. Also, it is one of the fastest ROMs to be delivered, so expect Android Oreo 8.0 anytime soon.
5. Dirty Unicorns
If I were to describe Dirty Unicorns in my own words, I’d have to say it is the stable version of Resurrection Remix. This is because of the plethora of customization features it offers is great, and it does so without any loss in the stability of the ROM. This is because the major difference between DU and RR is that while RR simply merges the various codes into one main project, RR’s team actually rewrites the entire code from scratch to ensure system stability. While this does mean that updates come a little slower, they are still able to deliver fortnightly updates. Also, DU has its own DU-SmartBar as well as FlingBar, that are both navigation bar replacements. While the former one functions to add more buttons to the normal navigation bar, the latter one replaces the navbar with a gesture-enabled panel that you can customize. Lately, the development team behind DU decided to remove certain features from the ROM, but those features were simply the ones users like to have on their device but never use it in real life. As a result, the latest versions are stable than ever and goes easier on the system’s resources.
DU currently supports Android Nougat 7.1.2 , and Oreo 8.0 is expected to be released in a couple of weeks for all major devices from Samsung, Moto, LG, OnePlus, Nexus, Pixel, and more.
6. AOSP Extended
As the name suggests, AOSP Extended is built directly from the AOSP source code and adds various cherry-picked commits from multiple other projects. Like all custom ROMs out there that are based on AOSP, AOSP Extended provides a smooth and lag-free experience out of the box. The AOSP Extended is also not short on features (or as the dev team likes to call it – Extensions), boasting of multiple customizability options available to modify the status bar, lock screen, and other Android settings. It also exhibits DU’s navbar/Flingbar, as well as other carefully selected features that mix well with Google’s imagination of Android. The development team behind AOSP Extended is also highly active, rolling out timely updates at the start of each month. AOSP Extended is in most ways, one of the most dependable custom ROMs out there that can be used as a daily driver.
It’s currently available for many devices including the likes of LG, Xiaomi, Lenovo, HTC, Samsung, OnePlus and more, and currently runs on Android Nougat 7.1.2.
7. Pure Nexus
Imagine being on your device’s stock ROM, but with slight tweaks here and there that allow you to customize your device to your choice without losing out on the stock stability. Well, if you own a Nexus or a Pixel device, this is easily possible for you. The Pure Nexus project has been around ever since Nexus 4 and has grown on to support all the Nexus and Pixel devices, with active development on all of them. It offers the same AOSP experience that’s exclusive to Google’s lineup, along with truly tested features and minimal or no bugs. In my experience with this ROM, the battery life was just the same as the stock ROM, but I was able to customize a few things here and there. To put it into better words, think of Pure Nexus as custom ROM that delivers the same experience that you’d get if you had installed Xposed and Gravity Box on the stock AOSP ROM.
The Pure Nexus project is only officially available for the Pixel and Nexus lineup, though it has been ported to other devices as well. It already has support for Android Oreo 8.0.
8. Carbon ROM
To define Carbon ROM would take up more than a couple of words. In your first run of this ROM, you’d find it similar to just about every other custom ROM out there. Use it for a couple of days, and you literally start experiencing the true beauty of Carbon ROM. One of the first ROMs to successfully implement Substratum (initially RRO and Layers), Carbon ROM is regarded as one of the most stable ROMs out there. The added functionalities in the form of CarbonFibers include tons of mods for the System, Status bar, buttons, lights, gestures and other various options. While it still lacks behind RR in the race for maximum customizability features, Carbon ROM still manages to hold its ground. Longtime users find it really hard to switch to any other ROM, for even though the features may be present on other ROMs as well, the smoothness and stability is unmatched. CarbonROM is available on a plethora of devices, thanks to its long-running development, and officially supports major offerings from Samsung, HTC, LG, OnePlus and more. It currently runs on Android Nougat 7.1.2, with support for Android Oreo 8.0 coming soon.
9. ViperOS
Another ROM based on the AOSP Gerrit but having its own custom mods is the ViperOS. You might not have heard of its name, considering its a rather new project, having surfaced around the launch of Android Nougat 7.1 only. Despite being a relatively new project, the ROM has quickly evolved into becoming a very stable and reliable ROM and gives plenty of other competitors a run for their money. A simple and neat ROM, ViperOS does not feature multiple customizability options but instead offers a great balance between battery and performance. The ROM recently even updated their source code for the latest in Android, that is, Android Oreo 8.0. Personally, I feel ViperOS is a near perfect mixture of stock ROM with several customizability features and amazing battery life. Since it is a growing project, it doesn’t have a long list of supported devices, yet, but is soon expected to grow to support all the major devices, with support for Android Oreo 8.0 already been announced.
10. FlymeOS
Okay, so if you’re located just about anywhere outside of China, chances are that you haven’t heard of FlymeOS. Well, FlymeOS is the official OS that powers up Meizu’s range of devices, and it does it amazingly. Originally developed by and for Meizu, the custom ROM project has since then been ported to support other OEM devices as well. FlymeOS stands as a direct competitor to MIUI, having more or less the same interface, combined with a great mixture of colors and details. Some unique features of FlymeOS include an in-built Toolbox that offers a compass, a leveler, a ruler, and toggles for various Android settings right from the corner of your screen. Then, it features its own Security Center as well as support for FlymeOS themes. Lastly, the ROM also comes with mBack key and gestures, that allow you to navigate through the entire UI using just the home key and a couple of gestures. If you’re bored of the stock Android look and MIUI looks a little too cliche for you, FlymeOS might just be what you’re looking for. While Flyme officially supports Android Marshmallow, with its beta announced for Nougat just a couple of weeks ago, the ROM’s features more than makeup for the slow development.
Thanks for voting!
DU, AOSPA and Pure Nexus...aint coming officially for sure....other will definitly
and wrong sub forum for post
LineageOS.
Sent from my MotoG3 using XDA Labs
Viper os
Slim ROM!
why you even started this thread @ap6709
LOS is a must for me
RR, AOSPE
I voted LOS because that is the one that I used the most. I haven't used Slim or AOSP extended. Are they open source and not based on LOS?
So if I don't flash GAPPS there is no proprietary code?
Lineage OS
Resurrection remix , AOSPE.
methuselah said:
why you even started this thread @ap6709
Click to expand...
Click to collapse
Just to get a public opinion on the most sought after custom ROMs and also to make the custom ROM developers aware of the demand. That is all. Am I doing something wrong? Please tell frankly.
:angel:
What is the code name of this device?
jilx said:
What is the code name of this device?
Click to expand...
Click to collapse
AFAIk Vassace
Nitrogen os
I don't know why this thread is made....but it should be removed.
It all depends on developers whether and which rom they will build. @MikeChannon please look after this and close this thread
This is the official Telegram Group for Redmi Note 5 Pro:
********************************************************************
Telegram Group Link - https://telegram.me/redminote5proofficial
********************************************************************
Guys please join! ​
Aosp extended, Resurrection remix ?
A couple of days back, a dev made Project Treble possible in a RN4 by using the MIUI partition for device and component firmware as required for Treble. I personally don't own a RN4 so didn't get to test it, neither am I am following that thread. But if it's possible to do so, then the ROMs with 8.1 and above should be a lot more stable ( talking about you RR ) . And if I'm not mistaken many devs already know about this and some devs of RN4 we'll move into RN5P. So as for custom ROMs are concerned, let's wait it out. The devs understand the device a lot better than us end users. Let the devs figure out a standard for the OS/ROMs. Till then MIUI isn't bad. Personally I dislike the bloat and lack of an App Drawer, contradicts the minimal approach which I prefer. But that's just me, but I think in general is not unusable.
The phone was up for sale first time 2 days ago and so I think instead of drooling for ROMs, give the devs their own time. They are doing it for free for us. Let's respect that and not be greedy.
Nitrogen os
Loving in kenzo now i want on rn5 pro

Community day with hackathon for the Volla Phone with custom ROM

Hello,
I'm Marc Aurel and I'm working with some other developers on the Volla Phone with a custom Android without Google Apps and Play Services. In addition to privacy protection the focus is a new simplified user experience beyond the app centered paradigm of current mobile operating systems.
We'll soon publish our code to invite developers to join the project or just have a look, what we are doing. We want to invite developers to our 2nd community days from 6 to 7 of June with a hackathon. You can find the announcement of the event with a live stream right here in our blog post. https:// volla.online /blog/files/community-days-2020.html
As a developer I will have some questions and I'm happy to answer some questions. I work on the launcher of the Volla OS, implemented with Qt, by the way. So I may can help or exchange experiences with developers working with this technology.
Very nice to see a phone that ships without any Google stuff out of the box. As many users switch to open source operating systems to avoid bloatware and manufacturer stuff sniffing their privacy this is a great project!
I hope the announced hackathon will result in many good ideas and approaches to improve the OSs compatible with the phone (as it also will support Ubuntu touch).
I'm looking forward to hear the results!
SHA_NDY said:
Very nice to see a phone that ships without any Google stuff out of the box. As many users switch to open source operating systems to avoid bloatware and manufacturer stuff sniffing their privacy this is a great project!
I hope the announced hackathon will result in many good ideas and approaches to improve the OSs compatible with the phone (as it also will support Ubuntu touch).
I'm looking forward to hear the results!
Click to expand...
Click to collapse
Thanks you for your motivating replay. We'll soon publish our source code of the Android based Volla OS after we have already published our source code for the Ubuntu Touch port in GitHub..
Beyond a discussion on measures to improve data protection, for which short presentations are welcome, we would like to explore ways to improve the user experience in the hackathon. One challenge will be the implementation of a system-wide sidebar that can be displayed with a border gesture. I'll post screenshots as soon I have the rights to post links.
Here the announcement for the community day:
https://volla.online/blog/files/community-days-2020.html
We have prepared an event page, that will be updated soon. You find it on volla.online/vcd2020 for Volla Community Days 2020. We hope to have participants of the Android developer community for our hackathon.

Categories

Resources