Related
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.
If I answer the question of "what is a kernel" it wouldn't tell you much, besides there are enough other threads on XDA and other websites to answer this question.
The best question is "Why to use a custom Kernel?", which answers not only what it is, but also what it can do.
I like the way its explained here:
http://www.makeuseof.com/tag/consider-using-custom-android-kernel/
The next most important thing you need besides the custom kernel is an app to manage it.
Yes, you can change the code directly, but for most non-nerds an app tends to be best, providing a nice GUI to facilitate tuning.
And since I am aiming for this guide to be N00b proof, I am gonna provide as much information as possible.
There aren't many apps which give you control over all features of the kernel and, personally, I hate having to download multiple apps to control every feature of the kernel.
So these are my top 3 recommendations:
The original app from the kernel's dev. You know, the one made specifically for use with that Kernel?
Device Control [root] by Alexander Martinz (Not gonna explain why, just go and test it for yourself or at least look at the play store page)
Kernel Adiutor by Willi Ye (It has a nice material GUI, + Extra features such as tweaking low memory killer, sysctl & sysfs)
What I most found lacking in other kernel guides was a well organised and comprehensive list of things custom kernels can offer. And since there is so much a Kernel could offer I'm going to try to provide it in categories with a couple examples so you get a good idea.
If I there is anything not accounted for, you are welcome to reply to this post and I will be checking every day to expand with any new info.
So without any further ado:
Feature List
General Settings:
These are things which do not fall within any of the other categories to follow. They are things which are usually classed separately in the App used to control the kernel. Examples include but are not limited to Fast Charge, Gesture (Knock on, Swipe2Wake), Color Calibration, Vibration Strength.
Advanced Settings:
These are similar to the general settings, but as the name suggests they are a bit more advanced and require a bit more knowledge/research to use effectively.
This includes Entropy (if you have no idea what this is look for Seeder App. The description of the App explains this very well.), Voltage Control (Ever heard of UnderVolting?), TCP Congestion Control (As a Networking Student I had no trouble understanding the technical documents about this, but knowing many who will be reading aren't knowledgeable of technical jargon I have included a nice link.)
http://androidmodguide.blogspot.co.uk/p/tcp-algorithms.html
As I know that there will probably be things I'm missing here, if you find anything which I have not explained, a quick google might be very helpful. Otherwise you are welcome to post a reply to this thread (even including the results of your Google if you need someone to explain it to you in a simple way.)
UPDATE 21/12/16: After getting my new HTC 10 I begun doing some research to understand the big.LITTLE configuration. It turns out that there are in fact some tweakable tunables for this. I won't be providing any recommended settings, since currently I am using a modded PnP which dynamically manages Kernel tunables for me, and as far as I know this is a feature unique to HTC.
But for those interested in finding out more here is a guide you could look through, if you want to learn more. The tunables are at the very end.
https://android.googlesource.com/ke...llow-dr/Documentation/scheduler/sched-hmp.txt
CPU Settings:
This is what you're most likely here for, this is the home of Over (and Under) Clocking.
But it also provides other very useful settings which might not look so simple at first. Here you can select a CPU governor (No guys, I will not list and explain what each one is, there are just too many and too many with stupid names. Instead I will leave you guys with a link to another guide specific about CPU Govs.)
http://androidmodguide.blogspot.co.uk/p/blog-page.html
While we're still talking about CPU Governors, there is a further option that you have if your app supports it. You can tune the specific tunables for each specific Governor, to get the best result possible and most suited to you. Whether you want more performance or battery savings from that specific governor.
Here you can also find toggles for HotPlugging or its counter part CPUquiet (Available only for NVIDIA CPUs I believe.) Hotplugging is simply the technology which decides when and which cores to turn off. CPUquiet is similar but rather than turning off the cores it simply makes the idle. The advantage is debated but the possibility is still there.
GPU Settings:
This one doesn't have many features (That I know of), it allows you to Over/UnderClock your GPU and also change its Governor.
Memory Settings:
(EDIT: I have included a Memory settings after doing a bit more of research about it, since its slightly more complicated compared to the other settings. Although most of these settings are available in both custom or stock kernels they can be tweaked to experience performance and battery improvements. So I'll try to cover as much as I can.)
Here you can tweak anything related to RAM and Cache. For tweaking these settings I suggest using the app Kernel Adiutor which I recommended earlier.
Things which you can find in all kernels are Low Memory Killer (Out of memory killer function on Android.) There is no need for me to explain it, what it does is self explanatory, to better understand the tunables I will provide this link:
http://forum.xda-developers.com/showthread.php?t=622666
You can also find tunables for Virtual Memory (Caching parameters), which is part of "sysctl" in the kernel. Tweaking this improves cache management, helping improve load times of cached apps, battery saving by emptying cache less often etc...
Here is a link which will give you a description for each parameter: https://www.kernel.org/doc/Documentation/sysctl/vm.txt
But there are also things which are not active or part of all kernels. zRAM is part of stock, and some custom kernels disable it. While KSM (Kernel Samepage Merging) can be added by some customs.
zRAM is just compressed RAM space. So you can store more in RAM by compressing the data you can fit more data inside your RAM.
Now obviously it is slower than actual normal RAM (since you have to encrypt and decrypt the data), but apparently it still is faster than using swap (which is in your internal memory rather than RAM). The principle works based on that Android prefers to keep data stored as much as possible in RAM to keep recently used apps running quickly. The more you use an app the more priority it has, therefore will stay in normal RAM, things you use sometimes but not very often are kept in zRAM (regardless of how full your actual RAM is), but since you don't use this very often you don't notice the performance hiccup of decrypting that data.
Then last case scenario things you barely use are kept in swap.
For you IT enthusiasts you should have realised already that "z" is the technology prefix for Compression. So it shouldn't come as a surprise that zRAM is compressed RAM.
KSM (Kernel Samepage Merging), this is simple, but it requires knowledge of some terminology. I will try to explain as simple as possible.
It allows the system to merge/share identical memory pages in RAM from different Applications/Processes. Thus it frees up RAM memory.
The only drawback to this is that it's up to your CPU to perform this task, therefore while it will increase performance it will also use up battery. But this is negligibly small (In my experience).
Therefore my recommendation is that if your Kernel offers this keep it turned on.
File System Settings:
The most desired setting available here is I/O schedulers. Again, I will not specify each scheduler since there are enough guides on the interbebs to give you all the info you need. On the other hand, I will leave you with my favourite of those guides.
http://androidmodguide.blogspot.co.uk/p/io-schedulers.html
The next most interesting settings is Read Ahead Buffer, this simply lets you choose how much data to load the buffer cache with. According to most benchmarks/tests the best value for this is 3 mb aka 3072 kb. This link gives you a better idea of it: https://broodplank.net/?p=788
Thermal Driver:
Here you can find toggles to manage overheating of the CPU and GPU. An example of which is MSM-Thermal and Core Control. I'm not gonna go into detail about these, since they are pretty self explanatory, and in my experience they both had descriptions beneath the toggles.
The most important thing to keep note of here is that only one should be on at any given time. If you turn 2 or more of these on together it may give you some issues. (It did with me.)
Tips & Recommendations
This is where as usual the writer gets to voice his opinion
Don't hate if you don't agree, just reply with your own opinion!!
I believe that any good custom Kernel should consistently provide some common settings.
We could say the minimum required to be considered a good custom Kernel.
Here is my list of basics:
General Settings:
Knock On (AKA double tap to wake)
Fast Charge
Advanced Settings:
Entropy
TCP Congestion Control
CPU Settings, all of it.
File System Settings, all of it.
Also my recommendation and tips for ideal CPU tuning and I/O schedulers.
FIrstly, CPU governors can be tuned to improve performance or battery saving. I found a good guide which explains the tunables:
http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
My recommendations will not take into account all the possible governors, but obviously if you take into account my recommendations and swap my choice of governor for an improved version of the same, or a similar one, then it should be even better.
While regarding the I/O schedulers, they are extremely under documented in comparison to CPU governors. And I have not managed to find a guide on how to best tune the tunables for the schedulers, so I will not cover this. If any one reading has any idea about this, please feel free to share your knowledge with us lowly humans!!
Actual testing reports and comparisons among schedulers are extremely difficult to find. So I will only recommend ones which I have found enough articles for or ones which I have tested myself.
Now for my list of recommendations:
Ideal CPU Governor
For general use, with a battery saving focus I would recommend the Conservative governor. And if you need a bit more of performance then it can be tuned to provide such.
For performance I would use Wheatley. If unavailable, then Elemental X or Interactive will be fine.
N/B: I added wheatley as an update after using it for a couple months, it has a double focus on both performance and battery saving. It follows the idea of "race to idle", that since idle saves the most battery then dealing with processes quicker means more time spent in idle. Therefore it will scale up to higher frequencies than ondemand and interactive, and it will try to deal with all processes in as quick a time as possible.
But it also focuses on battery, and if a process queue is taking long it will resort to scaling down the frequency to save battery while still getting work done.
In my experience I have not felt it glitch, and its very stable. It has improved my battery life (not as much as conservative), but it also has allowed me to use my device at full power.
But as with anything, there's always a downfall, which for wheatley is that it is a rare governor to find in most kernels. Currently I only have it on skydragon kernel. Most other kernels do not feature this governor.
EDIT 29/02/2016: I have learned of a new way to tune the parameters for Interactive governor, for optimum efficiency, when wheatley governor is unavailable. Since Interactive is always available - it is one of the stock governors.
In short it is tuning the parameters to use and spend more time in efficient frequency steps, in order to save battery while keeping the performance as high as possible. Using the fastest frequency steps before a huge jump in voltage consumption.
The links which helped me do it are the following:
http://forum.xda-developers.com/showthread.php?t=2769899
https://vjnaik.wordpress.com/2015/06/25/kernel-tweak-interactive-governor-paramaters-rooted-phone/
Ideal I/O Scheduler
For general use of your phone or tablet I would recommend using ZEN. It can provide good performance and better than average multitasking while having an average battery consumption. Being considerably better than ROW while at only slightly more battery intensive.
Obviously ROW is second choice, but if both of the above are unavailable, then B] FIOPS[/B] is a good replacement, ensuring an above average visual experience, good battery saving, at the expense of multitasking capabilities.
If battery isn't an issue, or you stream a lot of videos, then BFQ appears to provide similar experience to FIOPS plus excellent multitasking, at the expense of battery.
For Gaming, this was hard to find since there weren't any specific articles focusing on this, but from the descriptions and certain comments it appears that SIO provides a good experience. Others mentioned BFQ since it reduces lag.
For gaming you should absolutely avoid ROW and FIOPS since both have reported to increase lag during gaming.
For best battery saving the recommendation is definitely FIOPS. While it isn't the most battery saving scheduler (Noop is), it will provide the most battery saving while also efficiently giving you a great user experience.
For general multitasking the best one is BFQ. It will provide the best transfer rates (aka copy paste and install kind of thing), best for streaming & watching HD videos, and great for keeping loads of apps open at the same time.
N/B: I added ZEN to the list after using it for a couple months. At the time I first released this guide I could not find a kernel which offered this scheduler to test it. But after a while it started becoming more popular, and now it is easily accessible through most major kernels.
In my experience with it it has improved my multitasking slightly, while also reducing lag on general use. Battery increase unnoticeable.
Virtual Memory tuning
This one is a bit more complicated, and I have heard a whole bunch of stuff... Which is why I decided to test it myself and then come back to give you guys a report for it. The effects of VM tuning are not obvious at first glance and but affects the overall feel of the device. (Whether it feels like new, or sluggish etc...)
The main tunables you need to worry about are: Dirty Ratio, Dirty Background Ratio, Overcommit Ratio and Swappiness.
The guide I added above under "Memory Settings" will explain what each of these are.
Dirty Ratio & Dirty Background Ratio - Most people say that these need to be high, so that more stuff is stored in Cache. This will make your phone quick. Because cache is quick. But in reality this is only good advice if all you need to load on your phone is the system UI. Because as soon as you start loading different apps this cache fills quickly, and whenever you want to open an app/file/webpage that is not in cache, your CPU is tasked with both emptying whatever is filling up cache memory and load your new app into cache. Thus making multitasking a nightmare within the first day. A simple reboot of the phone is not enough, nor is clearing RAM (Note: Cache is not RAM).
Often the only solution to speed up your device is to Wipe Cache and Dalvik Cache from recovery every day. And for people with 150+ Apps installed which need to be optimized on boot, this means a lot of time is wasted.
My personal recommendation is to keep Dirty Ratio at around 40, which is double the stock value. Thus you have enough room before your phone freezes to free up cache. While Dirty Background Ration at 10, so that in the background without freezing the app you're currently in the kernel is constantly clearing cache. Allowing enough space for whatever you need to load.
Overcommit Ratio - While increasing allows more multitasking, I recommend leaving this at 0. It keeps RAM from completely filling up, thus avoiding "app xxx not responding" issues.
Swappiness - You have three kinds of fast memory on your phone, from quickest to slowest: Cache, RAM, Swap.
Swap is the last resort for your phone's memory. It is usually used when your RAM is nearly full. Swap is used for app data which is not currently being used, but part of the group of apps you use the most. (This is related to the Low memory killer, so for more information check that link. )
Since app data stored in Swap is stuff you don't use often it doesn't affect your phone greatly. But the more data kept in RAM, rather than Swap, the better.
Therefore after loads of try and testing I found that 40 is the perfect sweet spot. Allowing higher performance while keeping some data rather than completely deleting it when RAM is full.
This is my Guide to Kernels, if you find that it has helped you and would like to thank me remember to press thanks.
If you have any questions please do ask them, I'll answer the best I can.
If you would like to add more, dispute any of the things I said, give extra info on any specific thing which you believe deserves a more thorough breakdown, then go ahead, fell free to comment below.
Thank you for reading this Guide.
Nice guide and thanks for linking to my website
gsstudios
gsstudios said:
Nice guide and thanks for linking to my website
gsstudios
Click to expand...
Click to collapse
It was a pleasure, you have one of the most well informed and well organised guides to the stuff I could find.
Most others are just all over the place.
Keep blogging!
Very useful guide
Just a question: would it be possible gathering info about the "power suspend mode" that is often found in Kernel Adiutor?
{
"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 are the differences among the available options?
Thanks again for your guide
luke! said:
Very useful guide
Just a question: would it be possible gathering info about the "power suspend mode" that is often found in Kernel Adiutor?
What are the differences among the available options?
Thanks again for your guide
Click to expand...
Click to collapse
It took me ages to research, because initially when I did I found nothing. Whenever I searched this I would only find stuff about wakelocks. The wakelock system is more important to developers than actual users, so it was of no use to me.
But after a bit of research I THINK I found the original source code for this feature...I will put a couple links at the bottom for the enthusiasts to see.
(N.B. I will keep researching as I get more time to see if I can find more info on this, because it puzzles me also.)
Before I explain anything you must understand what the suspend state is, usually it is called sleep.
I usually cba to explain anything...since I am awful at explaining stuff in written form...I usually like to explain verbally. So I will leave you with a couple links:
Power suspend in Linux - http://unix.stackexchange.com/questions/162886/what-does-pm-suspend-hybrid-do
Power suspend in Android - http://bamboopuppy.com/android-suspend-a-brief-overview/
How it interacts with the hardware - https://source.android.com/devices/sensors/suspend-mode.html
Now for this kernel feature... I seems from what I have read that it is not activating or deactivating suspend mode....instead it is simply deciding on what "metric" to use.
Generally you could say that suspend state would be achieved on request by the kernel. But what if you want to automate the process so that it uses less requests, and thus goes to sleep quicker and more efficiently?
You make it so it bases on something else's output in order to initiate the count down.
This could be screen on/off (LCD panel), idle time (autosleep function), hybrid (autosleep & LCD panel whichever comes first), or userspace (defined by user.)
In all honesty, how it all works in detail I have no idea. But that is the basic idea.
I also have no idea why it keeps locking to userspace, as if it was default.
It seems that this function is not fully functional yet, or maybe it needs some fixing.
The gerrit page for the source code says that this project was abandoned by the main devs.
Gerrit page - https://gerrit.omnirom.org/#/c/9137/2
In summary, from other things I have read they say that Hybrid is the best one for battery life. But for me it never stays on Hybrid, it keeps resetting to userspace. Therefore I am unable to give you any further information about this.
I hope I helped.
Thank you, thank you, thank you, for putting this up so organized, the only problem on xda is proper guides, I can understand how much time and energy you have put into finding and putting up this guide, and the best part you have given links to the original author and not just copied their hard work and spread their knowledge combined. Well Done mate. That's a real example of how member of xda should be. this will help a lot of people. will share links to this thread.
Edit: added your thread link in my signature, hope you don't mind. I thought it would be better this way for people to see.
luke! said:
Very useful guide
Just a question: would it be possible gathering info about the "power suspend mode" that is often found in Kernel Adiutor?
What are the differences among the available options?
Thanks again for your guide
Click to expand...
Click to collapse
I have some new info about this, I don't remember specifics of where I got this, but it was in a thread about custom kernels.
A lost of people were asking why the setting was stuck.
And if I remember correctly it seems that this feature is a left-over stub from a failed project, which now has been superseded by Doze on Marshmallow.
It works exactly as I described, with the exception of Userspace, which rather than being defined by user it is defined by app. e.g. when app x says it's time to sleep phone will sleep. The other options are automated, and hybrid is the default option and we as users have no way to change it. It's been this way for a while, idk why Adiutor still has the option available.
Also finally understood fully why wakelocks kept popping up when I searched for this...it's because apps can set wakelocks to prevent the "power suspend" from happening, or even to wake the phone from a "power suspend" in order to not stop the app from running. This would be things like facebook, or other messenger apps which want to have a constant running service.
This created huge battery drains in KK and Lollipop, but now in Marshmallow Doze is a bit tougher to get around. Simple wakelocks won't do anymore.
billysam said:
Thank you, thank you, thank you, for putting this up so organized, the only problem on xda is proper guides, I can understand how much time and energy you have put into finding and putting up this guide, and the best part you have given links to the original author and not just copied their hard work and spread their knowledge combined. Well Done mate. That's a real example of how member of xda should be. this will help a lot of people. will share links to this thread.
Edit: added your thread link in my signature, hope you don't mind. I thought it would be better this way for people to see.
Click to expand...
Click to collapse
It's honestly been a pleasure.
I have been learning even more and soon I will re-update this thread with a lot of new info I have found.
I'm glad you liked this Guide, it did take me time and it's good that it has been recognized. You've made my day
This brings to mind the fact that I have been thinking on a new guide to newcomers into rooting and XDA, just explaining all that which is possible in a short but well organized guide .
Feel free to copy the link and share however you would like, it is honestly a huge help!
Thank you for making this guide, it helped me to understand my device further more
Thanks!
Android小楼阁-QQ群 439637151
来自搭载Android 2.3 GingerBread的华为Y220-T10
hello dude can i get your screenshot your setting on your kernel adiutor for daily, power save, and Gaming
.c.t.r. said:
hello dude can i get your screenshot your setting on your kernel adiutor for daily, power save, and Gaming
Click to expand...
Click to collapse
Unfortunately I don't keep presents.
I change on the fly as needed.
It just works better for testing rather than having specific presets to use, because I am constantly changing the actual values I use, also as apps get updated and their RAM usage increase or decrease, the values are always very fluid for me. I just keep changing until I find a comfortable value.
If there is anything specific you would like to know ask, and I'll advise you accordingly.
Thermal Driver:
Here you can find toggles to manage overheating of the CPU and GPU. An example of which is MSM-Thermal and Core Control. ...
Click to expand...
Click to collapse
Is there a way to manually set a temperature at which the CPU is clocked down to a specific MHz?
For example:
Temperature rises to 38 ° C = CPU clocks not higher than 800Mhz
thanks for this thread bro...
i have zero knowledge about kernel issues
and im so curious about how it work's and what it did
to our mobile phone's. but now i found your thread.
thanks for specific and detailed explanation..
even though i did understand only a little part of it
only the specific settings. I didn't know exactly how to use by changing
the number's of each settings under each codes and how it will
response to the performance of the device ..
i hope i will get it soon.. thanks again for putting this thread
it is very helpful in the likes of me newbie with zero knowledge
but willing to learn and understand how it is..
very big thanks bro...:highfive::good:
heross said:
Thermal Driver:
Here you can find toggles to manage overheating of the CPU and GPU. An example of which is MSM-Thermal and Core Control. ...
Is there a way to manually set a temperature at which the CPU is clocked down to a specific MHz?
For example:
Temperature rises to 38 ° C = CPU clocks not higher than 800Mhz
Click to expand...
Click to collapse
Unfortunately I don't know if that is even possible, you might have to mess with source code and add your own patches.
Good luck finding this out!
If and when you do share the knowledge with the community!
bearthing said:
thanks for this thread bro...
i have zero knowledge about kernel issues
and im so curious about how it work's and what it did
to our mobile phone's. but now i found your thread.
thanks for specific and detailed explanation..
even though i did understand only a little part of it
only the specific settings. I didn't know exactly how to use by changing
the number's of each settings under each codes and how it will
response to the performance of the device ..
i hope i will get it soon.. thanks again for putting this thread
it is very helpful in the likes of me newbie with zero knowledge
but willing to learn and understand how it is..
very big thanks bro...:highfive::good:
Click to expand...
Click to collapse
Dude, it's an absolute pleasure. It's mainly for people like you that I have made this guide.
I was like you too, and i didnt find a straightforward guide to help me out in the beginning...
There was a wealth of information but it was all over the place. A bit here a bit there.
I urge you to keep researching and keep learning. If ever you find that something you need doesn't exist, then make your own research and create that which you needed so that others who follow after you don't have to go through the same struggle!
Kyuubi10 said:
Dude, it's an absolute pleasure. It's mainly for people like you that I have made this guide.
I was like you too, and i didnt find a straightforward guide to help me out in the beginning...
There was a wealth of information but it was all over the place. A bit here a bit there.
I urge you to keep researching and keep learning. If ever you find that something you need doesn't exist, then make your own research and create that which you needed so that others who follow after you don't have to go through the same struggle!
Click to expand...
Click to collapse
some device not supported the tuning like my lg g4 h818p the noop doesn't tunable and cubic? thanks again bro
bearthing said:
some device not supported the tuning like my lg g4 h818p the noop doesn't tunable and cubic? thanks again bro
Click to expand...
Click to collapse
it's not the device, but the Kernel.
If the developer of the kernel adds support for certain features you will be able to use them.
You need to search and find the custom Kernel which has the features you are looking for.
Kyuubi10 said:
it's not the device, but the Kernel.
If the developer of the kernel adds support for certain features you will be able to use them.
You need to search and find the custom Kernel which has the features you are looking for.
Click to expand...
Click to collapse
any kernel is compatible to my g4 h818p? or
i search for specific kernel that compatible to my device?
thanks bro
bearthing said:
any kernel is compatible to my g4 h818p? or
i search for specific kernel that compatible to my device?
thanks bro
Click to expand...
Click to collapse
Find the thread for your device and you'll pretty much have found jackpot
i need help.i use kernel auditor to increase my headphones volume when playing music.( just use hdp slider to increase )
but happens that wen i unplugg the headphones and awnser a call the other persons dont hear me.
what to do?
What in the world is CAF?
Remember CAF? You might have seen that name all over the forums back when kernel developers for Qualcomm Snapdragon devices maintained two separate forks of their work. One for code based on Google’s AOSP, and another based on CAF. Code Aurora Forum is maintained by the Linux Foundation, and is where Qualcomm releases the reference sources for their various platforms. Most OEMs base their kernel source off of what’s provided by Qualcomm. On the other hand AOSP works off of a fork of CAF for each Android software iteration, introducing new features for all Android devices along the way. Over time, CAF then introduces its own optimizations intended specifically for Snapdragon devices.
Chromium Browser
Chromium is the open-source version of Google’s Chrome browser. To little fanfare, a group of developers at the Code Aurora Forum have been working on optimizing Chromium for Snapdragon devices. You can follow their progress on their project page where you can also build the source code into an APK. Some users who have built an APK out of the source report that the Chromium browser version is only on v42, and is thus outdated. It is generally not advisable to run outdated browser software due to the many security flaws that are discovered and promptly patched between each version. However, it seems that the latest stable version of Chromium, v46, has recently been merged into the project source so you should expect to be able to run the latest version very soon.
Features
The developers maintaining the CAF build have not only optimized the browser for Snapdragon devices, but have also introduced many key features that users on our forums clamor for from other web browsers. In addition to all of the features you’ll find in the official Google Chrome builds, the Snapdragon optimized Chromium browser includes:
Night Mode
In-built ad-blocker
Power Saving mode that limits the number of processor cores and throttles core speeds to reduce power draw
Revamped download page with the ability to select which directory to save each file
Side-swiping ability to allow you to move forward/back depending on which edge you swipe from (right/left respectively)
AndroidFileHost
We have compiled the apk and SWE is the caf browser.
XDA:DevDB Information
CAF Snapdragon Optimized Chromium, App for all devices (see above for details)
Contributors
Shahan_mik3, vasishath
Version Information
Status: Beta
Created 2015-11-08
Last Updated 2015-11-08
Finally v46.
Link not working, says not found
there's another version on oneplus forum
elderonj said:
there's another version on oneplus forum
Click to expand...
Click to collapse
V46? we have uploaded all the 3 outputs.
link?
Can someone provide link to Play Store version? I can't find it
Shahan_mik3 said:
V46? we have uploaded all the 3 outputs.
link?
Click to expand...
Click to collapse
http://51.254.243.6/SWE_Browser5-11-15.apk
there are so many 46 versions floating around. still baffled what to use as daily
I think the browser is fast and awesome will run a little longer and report back.
OT-Xtreme said:
there are so many 46 versions floating around. still baffled what to use as daily
Click to expand...
Click to collapse
well i have used v48 chromium but i like caf v46 more
Adblock
The adblock doesn't work for me, not in UI options and all the ads are showed :/ What happens?
Greck98 said:
The adblock doesn't work for me, not in UI options and all the ads are showed :/ What happens?
Click to expand...
Click to collapse
Not working for me either. The one linked 5 post above does though.
Sent from my E6653
I've compiled m46 myself and google sync isn't implemented yet, at least not on a pure source. I guess it's not implemented in this release either? @Shahan_mik3
pemell said:
I've compiled m46 myself and google sync isn't implemented yet, at least not on a pure source. I guess it's not implemented in this release either? @Shahan_mik3
Click to expand...
Click to collapse
not implemented.
but in contentshell apk it is implemented but fc xD
Why doesn't the adblock work ?
I'm on the Snapdragon Version 25.11. The option for Adblock doesn't show up under Sitesettings. WebRefiner button is missing.
Any fix?
Anyone figured out how to sync bookmarks with the chromium builds?
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
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better.
Download
https://download.mokeedev.com/?device=tulip
I found this on another forum and have not tried it myself - However it does sound intersting
Community
https://plus.google.com/communities/112433388317801966872
Good eye! And wow, what a find. I might try it out myself to see what it's all about.
good contribution, but when there is already an official construction of LineageOS, MokeeOS takes it immediately
I have two bugs in my experience to report...
(Bug 1) On first bootup after flashing and going through the setup, and when you get to the main screen, it has a hard time importing contacts from your Google account.
(Bug 2) If you have the phone plugged into the charger box and you slowly pull the USB out of the box, not all the way out just until the light goes off and the plig it back in, it says your phone is charging but it isn't and you lose battery percentage.
Those are all the bugs for me so far.
report the bug to mokeeOS
I like it Rom, and I use it es my daily driver.
Bat gogle keyboard not working perfectly, and I installed Xperia keyboard.
Any feedback for this rom? Like battery life, hi-fi dac, 5ghz wifi, performance, etc.?