Related
I need some catching up on this topic. Does anyone know the improvements of the newer 3.0 kernels over 2.6?
What does it offer, or change, etc specifically for HTC or android phones in comparison to 2.6.x?
at least battery life improvements...
http://www.h-online.com/open/features/What-s-new-in-Linux-3-0-1279552.html
kaijura said:
I need some catching up on this topic. Does anyone know the improvements of the newer 3.0 kernels over 2.6?
What does it offer, or change, etc specifically for HTC or android phones in comparison to 2.6.x?
Click to expand...
Click to collapse
Here is where the transition from 2.6.* to 3.0 is explained.
http://www.muktware.com/1520/linux-30-will-be-faster-2639-linus-torvalds
However when compared with the latest 3.1* kernel I learnt that some fixes that were made to the android's version of the kernel were merged back to the main kernel.
After some researching I have concluded the following:
Custom msm7x30 3.0 kernels are still really in infancy stages with no major changes. If anything it's just a facelift but still the same purpose-wise. Reminds me analogy-wise of WinXP came out with WinXP64. It's still the same, except the drivers and instructions are rewritten for 64bit.
The major change in 3.0 is nothing much except revisions to drivers and code.
Cyanogen mentioned in a post that "All the subsystem changes from 2.6.35 to 3.0 are super tedious, especially sound.”
So in short, there should small reasons to spend the time to make it get to work other than for polishing it 100% up to date or looking good with the 3.0 version.
Founder of Linux posted about 3.0:
Linux said:
So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver
changes, and a lot of random fixes, but the point is that 3.0 is
*just* about renumbering, we are very much *not* doing a KDE-4 or a
Gnome-3 here. No breakage, no special scary new features, nothing at
all like that. We've been doing time-based releases for many years
now, this is in no way about features. If you want an excuse for the
renumbering, you really should look at the time-based one ("20 years")
instead.
So no ABI changes, no API changes, no magical new features - just
steady plodding progress. In addition to the driver changes (and the
bulk really is driver updates), we've had some nice VFS cleanups,
various VM fixes, some nice initial ARM consolidation (yay!) and in
general this is supposed to be a fairly normal release cycle. The
merge window was a few days shorter than usual, but if that ends up
meaning a smaller release and a nice stable 3.0 release, that is all
good. There's absolutely no reason to aim for the traditional ".0"
problems that so many projects have.
In fact, I think that in addition to the shorter merge window, I'm
also considering make this one of my "Linus is being a difficult
^&^hole" releases, where I really want to be pretty strict about what
I pull during the stabilization window. Part of that is that I'm going
to be traveling next week with a slow atom laptop, so you had better
convince me I *really* want to pull from you, because that thing
really is not the most impressive piece of hardware ever built. It
does the "git" workflow quite well, but let's just say that compiling
the kernel is not quite the user experience I've gotten used to.
So be nice to me, and send me only really important fixes. And let's
make sure we really make the next release not just an all new shiny
number, but a good kernel too.
Ok?
Go forth and test,
Linus
Click to expand...
Click to collapse
Thank you for the nice summary so even I - noob- can get the basic.
Sent from my HTC Incredible S using XDA App
Update (10/09/2012):
IDLE2 v0.391 - details here.
Known issues:
Bluetooth sometimes doesn't work correctly in rare cases on some devices. I've done all I can with this. Whenever I test it, it works. So this one is going to be for the community to solve, should anyone wish to fix it.
Excessive battery drain during suspend. Unsure why this occurs, I'm investigating. It actually uses less battery if you kill suspend by holding a wakelock. This suggests to me that the device is 'pretending' to go into suspend, it *is* freezing tasks and calling wfi, but I suspect the SoC isn't being powered off, which may be a syscon issue. Time to do more TRM reading.
Update (09/09/2012):
Current version v0.390, which I'm also going to declare stable. It *may* still have minor bugs, but the blockers are definitely fixed, such as the kernel panics and lockups. The code churn is also over, as the implementation is looking good and cheap.
Development is now in this branch.
Changes here, here and here.
I also deleted a load of old crap from below.
Update (30/08/2012):
Still too busy / lazy to update the first post. Actually getting the damn thing working takes priority.
Current development is all taking place in this branch.
Current version (v0.370) highlights:
It actually saves power now after I fixed a few bugs causing stupidly low residencies.
Enabled continually. TOP block will be left on unless the screen is off, or the USB is plugged in.
CPU frequency set to 800MHz at all times whilst screen off
Tons of code re-written / refactored / deleted / reinvented.
Plenty of code comments added.
Statistics exported to /sys/kernel/debug/idle2/statistics (note the changed path) - Enable in menuconfig (CONFIG_S5P_IDLE2_STATS) (Would be better if this were disabled for 'stable' builds). I will probably remove it once IDLE2 is declared stable.
Hot path code is now cheap as chips.
IDLE / resume stuff reworked to use the S5P platform suspend code instead of specific assembly.
Blah blah blah. Probably loads more, but I forget, I've rewritten 90% of the code 2 or 3 times now, but I've learnt a lot.
Ignore the majority of the below, it's old and inaccurate. Perhaps I will update it sometime.
Any sensible questions regarding the code, ask in the thread.
No n00bs and no moronic questions please, think before post.
Patches and improvement suggestions are more than welcome, particularly now I think the code churn has stopped.
Credits and copyright of IDLE2 v0.3xx:
Originally, the majority was a port of code from Samsungs 2.6.32 P1000 kernel, hence Samsung retained the copyright because the changes were minor.
This is no longer the case as the current status of v0.3xx is that the vast majority of it, over 90%, is original code written by me as I have completely reworked and rewritten pretty much everything.
Describing it as a 'port' is not appropriate either, as it's not a port, it's a completely fresh implementation which has pretty much nothing in common with Samsungs LPAUDIO or Ezekeels didle, other than it achieves the same thing, arguably in a more robust and cheaper way, utilising as much common code as possible such as the platform suspend code.
IDLE2 was inspired by:
Samsungs P1000 kernel (my original port)
OMAP3/4 cpuidle
NVIDIA T2/3 cpuidle
S5PV210 TRM
There are a few portions of code in idle2.c which bear resemblance to the code in Samsungs 2.6.32 kernel, such as the defines and struct for the device checks, the memory allocation in idle2_post_init(), the gpio code in s5p_enter_idle2(), checks for activity in MMC/OneNAND et al, but the rest is entirely my work.
In short: The MMC & OneNAND activity check and the GPIO power down are Samsung code with modifications, but that is the extent of Samsung copyright.
Wilful kanging, not clearly giving proper credits and not contributing back is extremely unwelcome.
Open source is not about copying other peoples work, a principle which some developers don’t get.
The GPL was never designed for the purpose of copying code verbatim and riding on other peoples work, it was designed to allow freedom of code, a continual cycle of improvement and peer review, so consider that please and if you aren't prepared to work like that, perhaps consider the reasons why you are actually 'developing' and releasing stuff on here.
another awesome work by this awesome community. many thanks thalamus
teoserio said:
another awesome work by this awesome community. many thanks thalamus
Click to expand...
Click to collapse
You are very welcome.
I almost forgot...(lol)
If you want to try it out, right now, it's in my latest kernel release, which is available here. Info on my blog here.
Can you be so kind to update your first post and tell us how we use the patch files???
I would like to link to your thread from my tutorial how to compile a kernel.
This way we can teach more people to make kernels and they can make their own also.
djjonastybe said:
Can you be so kind to update your first post and tell us how we use the patch files???
Click to expand...
Click to collapse
There is a readme in the patch directory.
djjonastybe said:
Can you be so kind to update your first post and tell us how we use the patch files???
I would like to link to your thread from my tutorial how to compile a kernel.
This way we can teach more people to make kernels and they can make their own also.
Click to expand...
Click to collapse
It tells you how to use the patch files in the readme which is included in the same directory as the patches.
_thalamus said:
You are very welcome.
I almost forgot...(lol)
If you want to try it out, right now, it's in my latest kernel release, which is available here. Info on my blog here.
Click to expand...
Click to collapse
Okay i'll flash it later and report back with results
look's promising..
I checked and it works on the Jelly Bean. Android 4.1.1 AOSP
Jelly Bean i tapatalk
Astonishing work Thalamus. Ill be testing this as soon as possible, which means not now since its 4am and I just watched the new Batman.
Ill throw out some numbers as soon as I get some sleep, though I very much like some of the improvements you've made. I have high hopes.
Harbb said:
Astonishing work Thalamus. Ill be testing this as soon as possible, which means not now since its 4am and I just watched the new Batman.
Ill throw out some numbers as soon as I get some sleep, though I very much like some of the improvements you've made. I have high hopes.
Click to expand...
Click to collapse
Right on with that. Cannot wait to test this myself. It's a bit sad the development gets so far after the Nexus S gets "phased out" with the release of the Google Nexus. Not exactly its primetime, even though some releases here are top quality material. I cannot imagine someone would be deceived by all this, finally getting DI stable.
ALSO
You guys get the new Batman already? I'm jealous. Gotta wait until the 20th... *shakes fist*
Awesome contribution! I love seeing new kernel patches. Will try it out.
It seems I have a bug which breaks bluetooth audio streaming.
The good news, I know exactly what is causing it. The bad news, I don't really have any way of testing it because I don't own such hardware.
So, anyone who has got a bluetooth headset and can test a fix for me, please PM me.
So, the bluetooth issue is now fixed, thanks to Randomwalker for testing it so promptly.
IDLE2 version is now v0.130 and I have updated my kernel with the fix and released 3.0.37-18.
Info on the fix and kernel here.
When it's 100% stable I will try porting the patches to other devices as well.
djjonastybe said:
When it's 100% stable I will try porting the patches to other devices as well.
Click to expand...
Click to collapse
It is stable. Stability of idle2 is not an issue.
'Porting' won't be required, it should work on any S5PV210 device as is and S5PC110 devices with small alterations to the file paths / Kconfig. It's pretty generic. At the worst, you might have to fix a few conflicts, but that is about it.
The bugs I have fixed today were related to bluetooth audio streaming and the LED torch, neither were a reflection on the stability of the idle2 code, just things that were missed during testing, because myself and the people who tested for me can't test every corner case.
Very nice. Just have a few questions:
Is this a full stand alone kernel? Or like a patch you flash over your existing kernel to add this new feature?
Sorry if I don't make much sense, still kind of noob.
Sent from my Nexus S using Tapatalk 2
MrBigWaffles said:
Very nice. Just have a few questions:
Is this a full stand alone kernel? Or like a patch you flash over your existing kernel to add this new feature?
Click to expand...
Click to collapse
The patch is something you include in your code if you're compiling a kernel, it cannot be flashed over a kernel, like in a ROM.
There is however a kernel available which contains the patch, among others, which is also developed by _thalamus.
Sent from my Nexus S
on my i9023 and Remics rom it seems that there's more battery drain than INK (the version with DI by fear).
Btw I didn't try while listening music so I don't know if it is kernel related or something else
teoserio said:
on my i9023 and Remics rom it seems that there's more battery drain than INK (the version with DI by fear).
Btw I didn't try while listening music so I don't know if it is kernel related or something else
Click to expand...
Click to collapse
'seems that there's more battery drain' isn't massively helpful to be honest. More detail would be appreciated, such as some figures compared to a previous one of *my* kernels.
I'm not sure if there is an issue or not at the moment, looking at the time the device is spending in suspend makes me think that there isn't a problem, but if someone can show me that there is, I will look into it.
Before I begin, I'd like to give a MASSIVE thank you to @Neverendingxsin, who gave me the idea to create a thread like this, after reading his thread in the Verizon Galaxy S3 forums.
Also a big shout out to @xsenman who helped me get this thread up and running - without his help I don't think I could have got this thread started.
Android 6.0 - Marshmallow
Will we ever see Marshmallow land on the good old Galaxy S? Who knows... maybe a developer can work some real magic.
Android 5.0.2 and 5.1.1 - Lollipop
Back in June or July 2014, Google took the wraps off Android 5.0, nicknamed Lollipop. Lollipop is arguably the biggest update to Android since the Gingerbread -> ICS overhaul and brought with it a ton of new features and improvements. The biggest overhaul was the new Material Design UX language used across the entire system, providing an incredibly coherent and fluid experience with tons of eye-candy and animations. Dozens, even hundreds of smaller changes took place as well, such as how notifications were handled, status bar tinting, Smark Lock and so much more.
5.1.1 came at the start of 2015 and brought with it a lot of improvements over 5.0.2. Things such as improvements to Heads Up notifications and RAM management fixes made Lollipop just that little bit better.
Galaxy S 5.1.1 roms/kernels:
ParanoidAndroid 5.1 (alpha)
Omnirom 5.1
Coderom
Omni Kernel
Galaxy S Plus 5.1.1 roms/kernels:
Cyanogenmod 12
Resurrection RemixLP 5.5.5
AOSP rom (alpha)
InfinitiveOS
INTRODUCTION
I've frequented this forum for many, many years now and I've seen the same question being asked over and over again: "What rom should I choose?" The Galaxy S forum, even after 5 years, is still alive, and while the number of devs and roms has definitely decreased there are a select few devs still dedicated to developing for Samsung's 2010 flagship and its Plus sibling.
While I can't cover EVERY single user's wants and needs when selecting a rom, this thread is intended for users, both new and experienced, looking for a new or different rom to try.
So to start things off, just a quick definition of a rom by neverendingxsin:
Here's a very common question, what is a rom? A rom on our android phones is like the operating system on your computer, it controls the user interface, what you see and what you can do.
Click to expand...
Click to collapse
DISCLAIMER: What you do after reading this thread is entirely in your hands. I am not to be held responsible if something goes horribly wrong with your phone - this is merely a guide to help you make a step.
By reading this thread and following through with your rom choice, you accept the above, and every other disclaimer relevant to your rom.
If you are new to this forum, I suggest you take a look at these brilliant guides written by other members, and give them thanks as well:
Frequently Asked Questions
Android Recovery Toolkit
Guide to flashing Gingerbread 2.3.6, then any custom rom
How to downgrade from any custom rom
TUTORIAL on how to unbrick, upgrade, flash and downgrade from Froyo to Kitkat
Also, for ongoing Kitkat discussion, take a look here: I9000 Kitkat Discussion and FAQ
Those threads will give you a good place to start, and all are very important if you want to have a safe and (mostly) error-free custom rom experience.
Every S Plus related section will begin in blue text like this.
So without further ado.
Chapter One: Stock roms
A bit of a refresher: the last official update for the Galaxy S was Gingerbread 2.3.6. This was the "Value Pack" which brought some Galaxy S2 features such as a new Swipe lockscreen, increased RAM, Face Unlock and a few other tidbits here and there.
The Galaxy S Plus is the same - it too, received a "Value Pack" containing the same features, based on Gingerbread 2.3.6.
All stock firmwares can be downloaded from Sammobile's firmware page. Type in I9000 or I9001 in the search box.
Section 1A - Stock, rooted roms
They are exactly as the title says - stock and rooted roms, nothing else. This can easily be done even without the need to use a computer; a nifty little app called Framaroot can root your phone in one click and reboot - and yes, it does work for the Galaxy S. While it may seem a bit pointless having a root-only stock rom, it allows you to have the benefit of root capabilities (Titanium Backup, Root Explorer etc) while keeping every other aspect of stock the same, and also allows users to tweak the rom exactly as they want.
Galaxy S Plus users can be rooted in the same way using Framaroot, or other appropriate methods.
Is this for me? If you want to mess with a rom starting from scratch, or you just want root capabilities but nothing more, this is the rom for you.
Section 1B - Modified stock roms
These kinds of roms are roms that take the stock rom as a base but then change many aspects of it, starting from visual aspects right down to the very core of the system with optimisation tweaks and scripts. Some apps or libs found on the stock roms are removed as they are considered "bloatware" - apps that aren't useful and only take up space. As well as this, often apps are replaced with others - whether it may be the launcher or some other system apps. They are designed to provide improved performance over the stock rom provided by Samsung.
One that is still being updated is davidmore's DMore rom, which changes both the look and feel of Gingerbread.
Some other examples include:
MesoROM
SauROM Projekt
Gamerzrom Ninja V11
Galaxian V6
For S Plus users, here are a few examples:
Crybernation 1.0.1
Broodrom RC5
GIGABREAD+
BlazR™ Zen Edition
And many more from there - you get the idea here.
Is this for me? Often these kinds of roms offer a plethora of features or customisations while improving the speed and the performance of Gingerbread. You'll have the stability of stock mixed in with some visual or under-the-hood tweaking and customisation.
Chapter Two: AOSP roms
AOSP stands for Android Open Source Project, the name given to the whole Android project.
What you won't find in AOSP roms: Things such as the camera app, the contacts or messaging app, the music or video player, FM radio and 3G video calling from Touchwiz all won't be present, as these all depend on the frameworks used in Touchwiz.
Known issues in AOSP roms:
It seems to be quite rare, but for some users the screen turns blue, right through to the recovery. For a solution, take a look at this thread written up by @need4steer.
Ever wanted the newest Android version, or want to feel like you own a Nexus? Keep on reading.
The format of this section will be a bit different than before, as there are literally TONS of custom AOSP roms out there.
Section 1 - Cyanogenmod
Oh, Cyanogenmod. The name is synonymous with Android as a whole - ANYONE who is into Android modding or developing will know the name well. Their roms are build straight from the latest sources from Google, and they throw in their own modifications in such as Power Toggles and Cell Broadcasts, for countries that support it. Their vision? Providing the perfect Android experience one could have.
Before we continue, here are a few terms you may need to know (especially if you are new):
Nightly builds are built, well... nightly. They are daily builds and while mostly stable, can have some bugs or problems. If you're planning on going with Nightlies, don't expect a perfect experience 100% of the time. Yesterday's nightly might be fantastic, today's one might not be your cup of tea.
Release candidate, or RC builds only come around when a new version of Cyanogenmod is about to be released. They are essentially the "finishing touches" of a CM version, and are usually pretty stable as always. They lead up to...
Stable builds. Stable builds are builds that will usually not be updated any further, and are perfectly stable to be used as reliable daily drivers. Often after stable builds, nightly builds of that particular Android/CM version are frozen as they do not need to be updated any further.
Currently, the official maintainer of Cyanogenmod for the Galaxy S is pawitp, and we have:
CM7.2 (Gingerbread 2.3.7) [STABLE]
CM9 (ICS 4.0.4) [STABLE]
CM10 (Jelly Bean 4.1.2) [STABLE]
CM10.1 (Jelly Bean 4.2.2) [STABLE]
CM10.2 (Jelly Bean 4.3.1) [STABLE]
CM11 (Kitkat 4.4.4) [NIGHTLY]
S Plus users, for some reason, never got official CM support. However devs were quick to build the latest and greatest, and they're here below:
CM7.2 (Gingerbread 2.3.7)
CM9 (ICS 4.0.4)
CM10 (Jelly Bean 4.1.2)
CM10.1 (Jelly Bean 4.2.2)
CM10.2 (Jelly Bean 4.3.1)
CM11 (Kitkat 4.4)
Is this for me? Cyanogenmod is the "go-to" rom for many users. If you're looking for a great stock Android experience without too much other stuff thrown in, this is for you.
Section 1A - Cyanogenmod-based roms
These roms are roms based off Cyanogenmod code and often either make tweaks to it or add/remove certain apps or files. This creates an "enhanced" CM experience, and it is up to the developer what they add or remove or change. Bugs from these roms should not be submitted to Cyanogenmod's official bug tracker as they won't be looked into - instead, leave a message in the thread.
Some of these kinds of roms include:
kasper_h's Mackay Rom (there are also 4.1, 4.2 and 4.3 versions)
Mackay ICS (CM9 based)
rodman01's CM-based rom
S Plus users, here are a few examples:
EHNDROIX V (there are also 4.3 and 4.2 versions)
DarkCM
Is this for me? If you're looking for that same stock Android experience and like having those extra added things, these roms are for you. Please take the time to read through the developer's warnings or bugs list so you are aware of what to expect.
Section 2 - AOKP (Android Open Kang Project)
]AOKP was formed as a reaction against CM moving towards a more "clean" feel with CM9, instead of offering the level of customisation that they had in the days of CM7. Because of this, AOKP allows users to customise just about every visual aspect of their rom and how it behaves, bringing in features like Ribbons and custom status bar behaviour and tweaks.
Currently there is no official maintainer for AOKP for the Galaxy S - the official list is actually very small - but there are unofficial builds, such as:
AOKP Milestone 2 (4.2.2)
AOKP Milestone 1 (4.1.2)
AOKP Milestone 6 (ICS 4.0.4)
S Plus users, here's an AOKP build based off Android 4.1.2:
AOKP Release 1
Is this for me? AOKP brought a lot of the features you see in roms that allow heavy customisation. If you want that stock Android experience but also like having heavy customisation capability, then this is for you. Read the OP of each one, and turn your swagger on.
Section 3 - Paranoid Android
Paranoid Android is another popular custom rom, especially amongst Nexus users. They are built off the same Google source code as CM is, but their take on it is completely different. They introduced what is known as Hybrid UI, which allows the user to select either a phone, phablet or tablet display mode for each individual app. This means that for example, you can allow your Dialer app to display like a phone but your browser to display as if it was on a tablet. They also brought other popular new features such as Halo, the multi-tasking window popup and PIE controls, an alternative to hardware and software keys.
Currently the official maintainer is SferaDev, and the two official versions are:
Paranoid Android 3.69 (JB 4.2.2)
Paranoid Android 4 (KK 4.4.4) (PA 3.99, based off JB 4.3, can be found in the same thread)
S Plus users, here's one based off Kitkat 4.4.2: ParanoidAndroid 4.0[WIP]
Also, another based on JB 4.3: ParanoidAndroid 3.99
Is this for me? Paranoid Android brings with it its own unique set of features that have been used in countless other roms. If you like what you hear, or you want pure AOSP goodness, this is for you - #stayparanoid.
Section 4 - Omni
Omni has quickly garnered much attention and is backed by some top-notch devs famous for their work here. While it is still in early stages, Omni promises a lot of new and radical features to change how stock Android should feel; the most notable example being their implementation of Multi-Window, much similar to Samsung's iteration of it. High hopes exist for Omni, a rom which has no doubt excited the rom scene and brought something new to the table.
For the Galaxy S, both kasper_h and SferaDev have been working on Omni:
Omnirom 4.4 ALPHA
OmniRom 4.3.1
S Plus users, here's one based off JB 4.3: Omni ALPHA[WIP]
Is this for me? Omni is another vision on what a perfect, free Android experience should feel like. If you're pretty excited for the features Omni has or will bring, and want an alternative to CM or other roms, this rom is for you.
Section 4A - Omni-derived roms
With Omni's almost meteoric rise in popularity, there are bound to be more and more roms that use Omni as a base over Cyanogenmod. These will be similar in concept to the CM-based roms - roms that take Omni as a base and add smaller tweaks and additions as the developer sees fit.
Currently there is Mackay OMNI, based on 4.4.4.
Is this for me? Similar story here - if you want that little bit extra from Omni, and you like the little additions the developer throws in, this will be for you. Check the OP for bugs and notices and the like.
Section 5 - MIUI
Trust me - MIUI is Android. Its just a LOT different to stock Android. MIUI completely redesigns the Android experience, changing everything like custom toggles in the notification shade, the camera app, messaging and overall, the core experience. It has its own theme engine as well (themes must be designed specifically for MIUI if they are to work on the rom) and also has lockscreen themes that allow you to change how you unlock your lockscreen.
The Galaxy S doesn't have any official builds, although there have been a few ports:
MIUI 4.2.2
MIUI 2.3.7
S Plus users, some MIUI based off JB 4.2.2: MIUI v5[WIP]
Is this for me? Anyone wanting something a lot different from stock Android should definitely have a look at MIUI. It also adds a bit of colour to Android - MIUI is heavily based on visuals, which just might be up your alley.
Section 6 - Pure AOSP
For some people, nothing beats pure AOSP. Sure, you have Cyanogenmod, AOKP, PA, Omni and others, but some people may find that they add too many unneccessary things to stock Anroid or they want a totally clean experience, mimicking the Nexus line perfectly.
Some examples:
Supernexus 4.0 (4.3 and 4.2 versions are available as well)
S Plus users, here's an AOSP build of ICS 4.0.4.
Is this for me? Sometimes the bare-bones experience of true AOSP can't be beaten, and often these kinds of roms are great for performance because they have nothing weighing them down. This might be for you.
Section 7 - Everything Else
Because there are just too many AOSP-based roms for me to list here, I've decided to list them in four "umbrella" groups that describe them best.
Section 7A - Function over form
These roms emphasise speed and performance. They are based on providing the ultimate smooth experience and pushing the performance capabilities of the S to the absolute limit. This may include applying optimising scripts for RAM management or battery life or removing apps or files deemed unneccesary, such as LiveWallpapers. Don't expect the same level of customisation that you find in Cyanogenmod, because that's not the main focus here. The devs of these roms want either unrivalled smoothness or unmatched gaming performance.
Some popular examples include:
Gamerzrom
CyanAOSP (4.3 and 4.2 versions are available)
Sexynogenmod (for those wanting a 4.1.2 base)
ElectROM (for those wanting ICS 4.0.4)
Is this for me? For all those speed-freaks out there or just those people wanting an ultra-smooth experience, the above are definitely for you. As usual, take the time to read through and see if any bugs are present.
Section 7B - Customiseable to no end
These roms are quite opposite to those above - they focus on giving you the ability to customise just about every single aspect of Android, going from your whole system theme right down to how your device vibrates when you receive a notification from certain people. While functionality and stability is still a key point in these roms, they are focused on giving you the freedom of being able to theme and change things to your heart's content. They may also include features from other roms.
Some examples include:
Spirit Rom, which is a fairly new release
Resurrection REMIX
Carbon
C-Rom
Dirty Unicorns (Omni based) (4.3.1 also available)
PAC-ROM (4.3 builds should also be available in the same thread)
S Plus users, here are a few links for you as well:
Carbon 4.4.2
PAC-ROM 4.4.2
Is this for me? These roms allow you to have your phone exactly how you want it. They merge features of CM, AOKP and PA to allow you to change every part of it. If you like what you hear, these kinds of roms are for you - check out the links above to get started.
Section 7C - Finding a balance
Some roms incorporate features found in other roms but at the same time aim to deliver top-notch performance and usability. What you get is a rom that allows you to customise Android how you want it, while not sacrificing the performance or speed. This may mean that not as many options are offered, but at least you still have pretty good speed for daily use.
Some examples include:
SlimKat (SlimBean 4.3, 4.2, 4.1 and SlimICS 4.0.4 is available as well)
Helly Bean (4.2 and 4.1 are available as well)
Liquidsmooth 3.2 (unofficial) (4.3.1 version available as well)
Illusion (4.2 is available as well)
S Plus users, here's one link I've found for SlimKat (unofficial beta)
Is this for me? If you like having some level of customiseable freedom but you don't want to sacrifice good performance, these roms are definitely for you. As usual, check for any bugs present.
Section 7D - UI-based goodness
Some users like the idea of creating an experience that replicates the newest version of Touchwiz like on the Galaxy S4/Note 3 or like the Xperia Z1's UI. These kinds of roms try to emulate an OEM's stock rom found on their devices, and has a themed system and even ported apps such as launchers and other unique apps, like Sony's Walkman. The aim, of course, is stability while emulating a completely different feel to AOSP Android.
Some examples include:
Touchwiz Fusion Rom (based off CM11)
Project Seaspray (Touchwiz UI) (4.3.1 and 4.1.2 versions are available in the same thread)
RemICS-JB (4.1 and 4.0.4 versions are available)
Cyber-SGS4
Xperian UI
Cyber-Xperia
S Plus users, here are a few for you:
XOSP rom
RemICS-JB
Is this for me? If you've always wanted a newer version of a UI or just want something different, these are for you.
~~~~~~~~~~
If you want me to add something, please let me know!
And while I'm usually not one to explicitly ask, if you found this thread useful/like this thread please use the Thanks button!
I hope that this thread helps in making it easier for users for selecting a rom that they want and like. Even helping one person is more than enough
Any feedback, please leave a comment
And, as a final disclaimer/warning:
Please DO NOT copypaste this into another forum and claim it as your work! I asked for permission to adapt this thread from the original OP and so if you do wish to have a thread like this in your forum, please ASK FOR PERMISSION.
Click to expand...
Click to collapse
Unsure about your kernels and battery life as well?
Chaper Three: Kernels
Now we move onto the next part of the custom rom experience: kernels.
So let's have another definition, again from neverendingxsin...
What's a kernel?
Okay kernels are one of the biggest advantages to rooting. They can be used to increase performance vastly, increase your battery life, make your phone faster, increase ram, etc. You can modify the clock speeds using apps to overclock or underclock the cpu, you can increase or decrease the voltage, etc. They are also what makes your phone boot up...
Click to expand...
Click to collapse
Kernels are essential to having a great custom rom experience because they are the very core of the Android system. No kernel? No can do.
What's important to note is that you must flash the right kernel. What do I mean by this?
For example, don't flash a kernel for Gingerbread on a Jelly Bean rom! All kinds of things can go wrong.
NOTE: A lot of roms come with the option of allowing Bigmem, short for "Bigger memory". Quite often there are questions as to what this does.
This increases the amount of ram available on the phone, but gradually breaks video recording and playback capability!
The reason for this is that in the system, some ram is reserved for video drivers, both in terms of recording and playback. Increasing the ram means that there is less space available for these and so the functionality is broken.
To give a general idea:
Stock 2.3.6 and the general CM kernel come with roughly 368MB of ram.
Some kernels and roms come with 392~398MB of ram, though they are patched to still allow for 720p recording.
Then there is an option for roughly 407MB of ram, though that breaks HD playback and 720p recording.
Then finally, if you really want that much ram, there is an option of roughly 439MB of RAM which breaks video capability entirely.
There isn't much else to talk about here; however, these are links to all actively updated kernels which are still being supported:
Kitkat 4.4.4
Arrow Kernel (which I believe is bundled by default with Paranoid builds)
Semaphore (Jelly Bean 4.3, 4.2 and 4.1, as well as ICS and Gingerbread builds are available as well)
Mackay kernel (JB 4.3, 4.2 and 4.1 builds are available)
Cyancore (JB 4.3 and 4.2 available as well)
Stock CM11 kernel + Linaro 4.8 and Mackay TWRP
GearKernel (Builds for JB 4.3, 4.2, 4.1 and ICS 4.0 are available as well and all versions are updated)
NeatKernel (builds from 4.1.2 to. 4.4.2 are available in the thread)
Neo
Domnesu Kernel (supports all JB and Kitkat 4.4.4)
Gingerbread 2.3.6
DMore kernel
Chapter Four: Battery life
This is perhaps one of the most frequently asked questions in any forum, regardless of device: What's the best rom for battery life?
Before I delve into this further, I want to make something abundantly clear. Be realistic about your battery life. Don't expect miracles to occur on a three and a half year old device running software not optimised for one core, especially if you've got a battery that's just as old as your device. Yes, an option is buying an extended battery such as Powercell or Anker batteries, and there are ways of squeezing that extra bit of juice from your device, but even then, please, just be realistic about how much battery you can get.
And another disclaimer: Your mileage will vary no matter what.
So. here are a few ways you can improve your battery life...
Usage - it begins with you
This one is quite self-explanatory. How do you use your device? Are you a heavy web surfer, gamer and a video watcher? Or are you the kind of person who uses their phone only every so often? How you use your phone will obviously affect how the device's battery life goes. Some basic, but helpful tricks that others and myself have found to just get a bit more charge in:
Turn down your brightness. The display is one of the leading causes of battery usage. When you're inside, chances are you won't need to have your brightness on max in order to read. In that case, turn the brightness down to something that's still comfortable for you. I've found that half brightness or quarter brightness works well for me.
Turn Wifi and 3G off when you don't need them.
Turn Auto-Sync off if you don't need it as much. Auto-sync will constantly run in the background every so often and so it may drain your battery, especially if you're syncing large amounts at a time. On Gingerbread, this option is found in Settings -> Accounts and Sync; on ICS and above, this option is found under Data Usage (press the menu key). Alternatively, under Settings -> Accounts and Sync (Gingerbread + ICS) or under your list of accounts (JB+) you can control which apps sync and which don't.
Use apps like Greenify or even the stock application manager to disable apps running in the background, or at all. Memory-hungry apps such as Facebook tend to run in the background even after you've exited the app. Greenify can "hibernate" the app, meaning that it won't run in the background at all.
Rom choice
Some roms, especially those optimised for gaming performance (take a look at 6A in the post above), will have tweaks that optimise battery life. Usually this is more of a non-issue, but different roms will have different battery lives.
Kernel choice
Kernels are another direct influence on the battery life in many ways. The kernel will allow you to change how the phone behaves and performs using "profiles" known as governors. Some governors are based around performance while others, such as the common "conservative" or "powersave" governor, are intended for saving battery.
Alternatively, underclocking in an option - reducing the core's clock speed. This will sacrifice performance, but because the phone is simply not working as hard as it was before, more battery can be saved.
As well as this, kernels may have specific tweaks and options.
Coverage and signal
While its not something that can be easily changed, try not to have the phone in areas of poor reception, both with wifi and cellular reception. If the phone is constantly searching for an access point this will drain battery in the background. This is also more of a non-issue but does apply more to poor wifi signals.
Wakelocks
What are wakelocks? Essentially, they are apps, processes or services that prevent the phone entering a state called deep sleep. Deep sleeping preserves battery life, much in the same way that a computer left alone for some period of time will enter a sleep mode to conserve power. Wakelocks will keep the phone active, which will continue to use more battery.
Thankfully, apps on the Play Store such as betterbatterystats allow you to monitor any wakelocks present and often allow you to change the behaviour of it. Most of the time, wakelocks are caused by the phone syncing data back and forth.
Buy a new battery!
This one is probably one of the easiest ways to extend battery life - simply get a new battery. Extended batteries for the Galaxy S are relatively inexpensive and usually provide you with enough juice to last the day.
Chapter Five... For you gamers out there
Its probably one of the most frequently asked questions when it comes to rom choice... What's the best rom/kernel/setup for gaming?
Let's review what we know about the Galaxy S.
Android 2.3.6 officially, unofficial roms going up to Kitkat 4.4.4 available
480x800 resolution screen.
1GHz Cortex-A8 processor, single core.
512MB of RAM, in which a general amount of 368MB or 396MB is useable.
Also, for the S Plus users out there:
Same Android 2.3.6, with unofficial support for 4.4.4
Same 480x800 screen
1.4GHz Scorpion processor, single core
Same 512MB RAM
In human terms, what does it all mean?
It means that the devices don't have killer specs. The S Plus is a little bit better off having a slightly stronger processor, but still, its important to understand that we are dealing with older devices here. Don't be too surprised if that new game doesn't run smoothly, if at all on the Galaxy S because chances are it won't. The Galaxy S' hardware is nigh upon 4 or 5 years old so don't expect smooth sailing at all with newer games, especially those that are graphics-intensive like Minion Rush or Asphalt (or anything by Gameloft really)
That being said, here are some ways to maximise gaming performance on the Galaxy S.
Step One - Choose the right rom
First off, you want to choose the right rom for gaming. If that's the case, take a look at section 6A in my first post, which lists a few roms for gaming and performance. To repeat myself, these games are optimised for gaming and so on by scripts or tweaks to the system as well as getting rid of apps that may be deemed unneccesary.
In that case you probably don't want a rom with too many features for customisation. These kinds of things do tend to slow the rom down and impact performance (except on roms such as Slim or Illusion).
ICS and Jelly Bean also feature something called hardware acceleration, where the processor is pushed to essentially smoothen things out. This can allow for some serious speed even out of the S/S+ with the right tweaking.
Gingerbread however has stability - the stock rom is really stable and a solid performer, whereas ICS and JB will allow for some pretty insane performance.
Kitkat, being somewhat easier on the system, should have some effect on gaming and performance in general. For more ongoing information about how Kitkat performs, make sure you follow this thread on Kitkat discussion by @xsenman.
EDIT: It seems Kitkat roms can be quite hit-and-miss for some users. Performance, both for gaming and for normal tasks, is reportedly best on ICS.
Step Two - Choose the right kernel
What's the point of trying to optimise the system for gaming if you don't have the right kernel?
Kernels allow for three things:
Overclocking/underclocking. This changes the clock speed of the processor, and overclocking is probably going to be an option you'll want if you want gaming performance. Its simple, increase clock speed, increase power exerted by the processor/chipset. Warning though, the safe limit for the Galaxy S is around 1300~1400MHz. Anything higher than this will cause frequent crashes or bootloops.
Overvolting/undervolting. This changes the voltage delievered to the chipset. Simply said, if you overvolt, in turn you overclock as the core is able to push more. Overvolting can be dangerous if not applied correctly - like overclocking, there are certain limits to overvolting. (If someone could give me values it'd be much appreciated)
Bigmem. This increases the available RAM at the cost of video playback/recording. Refer to my post above to see what kinds of bigmem configurations you can have.
Semaphore is a kernel that is quite popular with gamers here - another one is Devil Kernel.
If you install a rom that's built for games, the kernel will already most likely be heavily optimised to deliver maximum performance (eg. Devil Kernel in Gamerzrom, Cyancore in CyanAOSP). However if you plan on installing this on another rom such as Cyanogenmod, custom kernels will allow you to finetune the above to your liking.
Use apps such as Semaphore Manager (guess which kernel that belongs to), Devil Tools (guess) or NSTools (generic application) or apps such as the built in Performance Control to customise and tweak to your heart's content.
Step Three - Check what's in the background
Apps running in the background are going to use RAM and processing power while you run your game, and even a minimal thing such as data syncing can have an impact on your games. Make it a habit to regularly swipe away apps from the Recents menu that you don't need, or use an app like Clean Master to ensure that your RAM is cleared out mostly for games. Little things can go a long way, and this is one of them.
It may also help to turn wifi off to stop auto-syncing going on in the background, as well as lengthening battery a bit.
More to come!
This part of the thread is still under construction, and as such I'm still in the process of collating more things to add here for gamers. This isn't the end!
~~~~~~~~~~~
That wraps up my thread for now - I'm sure I'll keep adding to this as time goes by and more questions are raised
If you also found this part of the thread helpful, please press the Thanks button!
Changelog!
Changelog
10 October 2015, V4.4
-I've come back to touch up this thread after almost a year of inactivity in the S forums - I've added more links to Lollipop roms right at the very top
22 October 2015, V4.3
-Slight touching up of certain parts of the thread with new links, small bits of added info etc.
I have my own computer now so it'll be easier for me to update this thread where needed. I wrote this thread off a tablet and getting links isn't the easiest thing in the world on an old tablet..
8th March 2014, V4.2
-Current layout will stay as it is for now. It makes it easier on people using the XDA app/Tapatalk, and won't hang so much when loading this thread.
-As many links as I could find (without spending hours and hours just searching) have been added in for both S and S+ roms. S+ users now mostly have at least one or two links. Links for things such as SlimKat, Mackay ICS and Resurrection Remix have been added for S users.
-Neo kernel and NeatKernel have been added for S users in second post
-Changelog version numbers have been changed to mirror Android versions as closely as possible. (Some versions are missing/skipped to reflect the size of some changes in this thread) tell me if it's just too confusing and I'll stick with standard numbering
Note: At this stage I've added in as many links as I could to give both S and S+ users a reasonable selection of roms. Due to time commitments with life and schoolwork, I'm treating the first post as finished, and will not be updating links for at least some time. I will update the first part of this thread when the next version of Android (4.5? 5.0?) is released, or for formatting reasons to make this theead easier to navigate. The kernel/gaming post still needs finishing so that will be updated.
OLDER CHANGELOGS
22nd February 2014, V4.1.2
-As a test, all rom type descriptions and links are now hidden in the hopes that a.) People don't have to scroll too much and b.) only relevant information (depending on what each user wants) can be found.
21st February 2014, V4.1
-Section 6 has now become a Pure AOSP section (Supernexus, stock AOSP builds etc etc). Section 7 now entails everyhing else.
-Every section up until 6 has now got at least one link for S+ users. I'm hoping to add more for different versions of the same rom. If anyone can send me PMs with links this would be greatly appreciated as this would speed up the process.
15 February 2014, V4.0.4
-Added a "Known AOSP Issues" section under the start of Chapter 2.
Note:The reason why I've been updating so infrequently is because for me, school's started and so I'm REALLY busy. I will eventually complete this, but for some time I won't be able to - please bear with me!
26th - 28th January 2014, V4
-Added a gaming section! Still in writing phase, as I still need to collect more info
-Slowly adding in links for S Plus users
22nd December 2013, V2.3
-Added Section 4A, Omni-derived roms
-Removed version numbers from kernel section - because they're frequently updated, its not feasible for me to keep changing the version numbers every time
17 December 2013, V2.2
-Added battery life section!
15 December 2013, V2.1
-Added Bigmem explanation under kernel section
12 December 2013, V2.0
-Added kernel section!
-Added links to older/different Android versions of most roms and kernels such as Mackay, Cyancore etc etc
7 December 2013, V1.6
-Fixed up most/all typos
-Added missing part for MIUI
6 December 2013, V1
-Initial post
To do list:
-Finish gaming section
Great Guide
thank you for your hard work
This Guide will help many users
wow, great start ...would indeed be a very helpful guide for all in this forum, will link this here and adding a link to Custom ROM Comparison database would be an option that you can consider too
Check this out! Links to useful Guides and " Banned " Documentaries
http://forum.xda-developers.com/showthread.php?t=2482420
xsenman said:
wow, great start ...would indeed be a very helpful guide for all in this forum, will link this here and adding a link to Custom ROM Comparison database would be an option that you can consider too
Check this out! Links to useful Guides and " Banned " Documentaries
http://forum.xda-developers.com/showthread.php?t=2482420
Click to expand...
Click to collapse
Thanks so much man, and I'll take a look into what you linked and see if I can get this on there.
Looks great man I really do hope that this will help people here in this forum!
Hey gratulation for the great work writing and create such a Guide !!!:good::good::good:
Because it is a great info-base for newbies and all the others, maybe you should think about asking the Mods to make this thread "sticky" so that it won`t get down from time to time ...
freakymod2120 said:
Hey gratulation for the great work writing and create such a Guide !!!:good::good::good:
Because it is a great info-base for newbies and all the others, maybe you should think about asking the Mods to make this thread "sticky" so that it won`t get down from time to time ...
Click to expand...
Click to collapse
Yup, I'll try get this thread stickied once I finish the whole guide
Sent from my GT-P7510 using Tapatalk
Well done! For me the best overview for newbies and a bit experienced users! Thank!
If i can help you to support this, let me know ...
I think - as Robb Stark had written - it is a great guide for newbies, who want to flash a new ROM and get a general view ...:good:
Soryuu said:
Yup, I'll try get this thread stickied once I finish the whole guide
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
freakymod2120 said:
If i can help you to support this, let me know ...
I think - as Robb Stark had written - it is a great guide for newbies, who want to flash a new ROM and get a general view ...:good:
Click to expand...
Click to collapse
Thank you - its very kind of you. I just need to finish up adding what I feel is neccesary and then I'll apply for a sticky.
Sent from my GT-P7510 using Tapatalk
Thread updated again - I'm hoping to finish this before the end of next week
Sent from my GT-P7510 using Tapatalk
freakymod2120 said:
Hey gratulation for the great work writing and create such a Guide !!!:good::good::good:
Because it is a great info-base for newbies and all the others, maybe you should think about asking the Mods to make this thread "sticky" so that it won`t get down from time to time ...
Click to expand...
Click to collapse
Thread is now stickied
Sent from my GT-P7510 using Tapatalk
Excellent work, mate!
Compliments and multiply clicked "thanks" buttons from me
Now the amount of good souls of the i9000 Help threads is growing bigger!
tetakpatak said:
Excellent work, mate!
Compliments and multiply clicked "thanks" buttons from me
Now the amount of good souls of the i9000 Help threads is growing bigger!
Click to expand...
Click to collapse
Thanks, your thread is great stuff as well
Sent from my GT-P7510 using Tapatalk
This is a very good guide.
Thread updated again, its at a "final" stage for now, until I get back from overseas (where I'll have more time to continue updating this thread)
Sent from my GT-I9300 using Tapatalk
thx for the great guide man!
DaDrdvi forcements
Im using Pa 4.0 :victory:
I have been on the Nexus 6 since early December 2014, and for me, as with many others, the Nexus 6 was my entry point into the pure Google experience, and my simultaneous departure from TouchWiz. From the beginning, I was a noob on this device.
So, after 4 short months, I have found that the rom threads have become congested with endless questions that are not germane to the given rom. The more popular a rom becomes, the problem intensifies.
I can imagine how frustrating it must be for a developer whom has worked hard, flung his or her creation to the xda shadowed wilds, only to return to a thread that has become a thicket of repeated questions.
Compounding the problem is that each developer has a different approach as to how he or she wishes his or her thread to be managed, which in turn can be confusing to any user. Some developers seem happy to remain ensconced in the daily comments, while others have a palpable disdain for off-topic quotes.
Irrespective, I think each has a tipping point, and thus I am sure that none is immune from becoming a bit jaded after a time.
And yet, we still have the very real phenomenon that this device has a learning curve, is available across the globe, and thus the questions still recur. Further, it is in many people's natures to either want to help or at least be cautious prior to rooting their device, etc.
So, I thought it would be fitting to provide a place for all to ask whatever they want. As the title clearly states, this is a noob friendly place, so please feel free to ask whatever you would like about this device. I am certain that all here on these forums would rather you learn what you need prior to availing yourself of the amazing array of resources in the development and themes and apps sections of these forums.
A few preliminary guidelines for this thread:
This is a noob-friendly thread, so ask whatever you like
Read the initial posts of the rom thread, as well as the last 10 or so pages of that thread, before you flash the rom you want. It will give you an idea of how the developer handles his or her thread, the tools you need before you get started, and
Please respect your fellow forum members, developers, and the moderator staff. Moderators have a thankless job, and I can assure you that it is absolutely no fun spending hundreds of hours on what amounts to a volunteer position without benefits.
Towards that end, please read the rules; they are the first post on every forum here on xda.
Thank everyone that develops, and please donate to anyone whom you believe is worthy of your extra gratitude. Donations are never required, but they do motivate those that do the hard work on these forums.
Never downgrade your bootloader. Ever.
I’ve split this into categories so that folks will have some basics right upfront.
1.First Use
1.1:You almost certainly will want to unlock your bootloader, inject root, recovery, etc.
I suggest reading the All-in-One Beginner’s Guide, where you’ll find everything you need to get started.
1.2. Learn Fastboot:
Yes, you have a Google device, and it is very easy to flash anything you want with a few simple command lines. Put bluntly, on Nexuses, the manual steps are very easy.
Hie yourself to this authoritative thread written by the prolific dev and highly respected forum member @rootSU.
1.3:Toolkits: Toolkits are a fantastic way to do all of this from the jump. There's nothing wrong with toolkits themselves; they can be great, useful tools, but please learn to do the steps manually. Why? Simple. If anything goes wrong, and it can, knowledge of fastboot will save you; no knowledge of it, you're waiting on help from others, or learning from scratch that which you should already have learned. Further, should help arrive, that person helping you is bearing two burdens, helping you first learn the basics of command line, and solving your problem. That is downright unfair. OK, onto the toolkits. You can find them in the development sections, specifically:
Wugfresh's Toolkit for Windows Operating System
Nexus One-Click Mac Toolkit for the OSX
Skipsoft Unified Android Toolkit for Windows
1.4: Decrypt or Not Decrypt:
Please note: Decrypting your device will wipe your device, so if you are going to decrypt, please do so before taking all of your time to setup your device the way you like it.
IF you want to remain decrypted, put the zip file located in this thread on your device, throw it in your cloud storage (Dropbox, &c), keep it in your pocket, think well of that file.
IF you want to remain decrypted, that zip should be the LAST file you flash before any new rom or kernel is flashed, or if you are unsure if a rom has a kernel that will force encrypt your device.
There are differing opinions as to the wisdom of decrypting, and I don’t care whether you think it is better or worse; people want to do it.
You can learn more about it here, and can accomplish the task using the link previous link or using any one of the aforementioned toolkits.
1.5: Recovery:
You almost certainly want to make a backup of your device prior to tweaking, flashing an updated nightly, or testing a new rom. Recovery for our device can be found here.
You may want to put a nice theme on that TWRP, go here. Hint: The developer whom does those themes keeps up with each iteration of TWRP, and if a new version requires a new theme, check the theme thread before you update your recovery.
1.6: Starting Over
I believe that this community owes a special thanks to @Q9Nap and @scrosler as each has provided us with amazing tools to return to stock or upgrade your device from 5.01/5.02 to 5.1, sans the need to revert to stock 5.01.
Please go to http://forum.xda-developers.com/showthread.php?t=3066052 thread for flashable zips of entire 5.1 roms or modems ,or this Android File Host page from SCrosler for flashable 5.1 modems + bootloaders...https://www.androidfilehost.com/?w=files&flid=23050
https://www.androidfilehost.com/?w=files&flid=23050
2. Choosing a Rom: Roms generally fall into four discrete categories:
2.1: Stock-Based – these are hewn from Google source, and typically come preinstalled with everything you will need to be up-and-running. Whatever tweaks, performance or otherwise, are added, the rom will most certainly similar to stock, hopefully better than stock.
2.2: AOSP-Based – these are built from the Android Open Source Project, and purists may think of them as closer to what Google intended. You will typically need to flash a Google Apps (Gapps) package separately from the rom itself. Some of these have inline kernels, or stock kernels, but they typically have everything you need baked right into the mix. There is an incredible variety of unique and wonderful roms from which to choose that fall into this category.
2.3: Original Development – Although the lines tend to blur, suffice it to say that roms in Original Development contain something original that merits a rightful place of its own, away from the crowded Development Forum. You will find kernels as well as complete roms in this section.
2.4: Hybrids – The vast majority of roms fall into this category. Much of the joy of Android is customization, and most roms in this category are feature-rich and packed with things, almost more than you will ever use.
Customization - Enhancing the Senses
Rom Customization:
Roms are popular and highly useful, but they are also fun. Instead of using a boring, stock phone laden with what amounts to another's idea of what you should have on your device, you are in control. This starts with how the phone looks. Yes, your phone can and should look exactly how you want it.
Disenthrall yourself from the madness that is a stock looking phone and apps, and stare with wonderment at beautifully themed apps.
1. Hard-Coded Themed Apps:
Anyone can run a themed app, even on a stock, rooted rom. These forums are riddled with themed app threads. Some suggestions to start:
1.1: Team BlackOut, the hardest working devs on xda are there, please go into their thread, enjoy the camaraderie and the beautiful apps they make. Be sure to thank and donate if you are so inclined. You will find themed versions of scores of apps, all available for free from their updater app.
1.2: XDA Recognized Themer @cerj has done a terrific job theming many apps on his own, and of course with the help of other themers. He is a terrific resource and a good friend. Check out his Blue DeLucia and Krome-X apps.
2. Theme Engine and Layers
Many Non-Stock Roms make use of one of these two basic tools that allow you to theme your entire phone. Suffice it to say that these are mutually exclusive means of attaining a beautifully themed rom without much hassle on your end. The CyanogenMod theme engine has its fans, and the fine devs doing the Layers app consider their work stellar (as they should); both are excellent.
2.1: Layers: If your ROM has Layers, and the app is not already on your phone, you'll need to download the free app from the Play Store. You'll find an abundance of themes in the Official MEGA RRO Layers Overlays Collection.
Special mention to one of the finest themers whom I've come to know on these forums; as RRO has had met the steep ramp-up with stunning strides, this terrific dev has been there, every step of the way.. @daveyannihilation, a tosser, wanker, and a very Gary dude, please help...I mean thank this man. He's everything and more. Please help me, inasmuch as I'm far more concerned about the degree to which I'm both a wanker, and a tosser, not to mention completely Gary.
2.2: Theme Engine: If your rom incorporates the CyanongenMod 12.0/12.1 Theme Engine, you can find a ton of beautiful themes in the Official MEGA CM12 Theme Engine Thread.
Please buy the themes you love. Free themes are terrific, but I always believe that people are more motivated to continue delivering these terrific tools if you support their hard work. Buy the damn themes, and don't be a cheapskate...there's enough whining in these forums to make most want to wretch.
Kernels and Tweaking
If you wish to flash a kernel, here are a few guidelines to get you started
Note: Most all of this was written entirely by @wrongway213.
1. Kernel Basics:
1.1: Stock Kernels: You can keep a stock kernel if that is with which you are comfortable. The stock kernel will force encryption, and there are modified stock kernels that will not force encryption.
1.2: Custom Kernels:
1.2.1: Hotplugging: Hotplugging is basically the background process going on telling your phone when it needs to bring CPU cores on and offline. This controls how much power your phone consumes - both how much battery it drains and how snappy it feels. You can use a kernel tweaker app (more below) to set all kinds of things in the kernel, including how hotplugging is done. Different kernels have all sorts of different hotplugging options.
As of 5.1, stock kernel uses all four cores online at all times as opposed to hotplugging. This is said to save power. Some kernel developers have adopted this as the default for their custom kernels, but they are still tuned very differently than stock. The user can still choose to revert back to hotplugging if they prefer it. Prior stock kernel, including 5.0X Lollipop, use something called MP-Decision to scale your frequencies. Some are of the opinion that MP-Decision is entirely too aggressive in how it handles this. It attempts to give the user a snappy and smooth experience, but in the end it mainly drains battery. The same smooth experience can be achieved via hotplugging properly on a custom kernel, and your battery will thank you for it.
1.2.2: Governors: Another awesome thing you can do when you flash a kernel is control the governor it uses. Stock kernel uses an interactive governor, which responds to user input and is generally considered to be a pretty good governor, even for custom kernels, However, it is often modified on these kernels, or at the least assisted with hotplugging in a different way than stock. This governor has been modified by @Imoseyon for leanKernel, one of the most popular kernels for our device, and a great place to start if you want to know if custom kernels are for you or not. Some prefer to use conservative, which is much less jumpy than interactive - meaning it does not scale frequencies up or online cores as quickly as interactive. This governor has been heavily modified for our device by @franciscofranco (Franco Kernel dev), so it is a much more viable option for those whom want to conserve battery and still get great performance. There are many different governors offered with different kernels - you can change your experience on the very same kernel by changing governors sometimes. Or you may find that you flash a new kernel and find a whole new set of governors that are more your style. This is all about trial and learning what you like, as none of us can know what is best for your use.
1.3. Kernel Use and Utility:
1.3.1: Wakelocks, An Example
A kernel can do many things if the kernel dev chooses to make it, or to give the user the option to avail such options, or can be omitted entirely if running stock. Though not the source of your wakelocks, kernels can disable wakelocks can control or disable them. This is a good example of the separation of a kernel's ability and a kernel's use.
1.3.2: The Domain of the Kernel:
Many kernel devs choose to leave the kernel footprint small, and allow the ROM side of things to handle as much as possible. Some kernels use the existing ramdisk that comes with the ROM instead of inserting their own to ensure they will play nice with all roms. Other kernels are highly customized and completely and totally change the feel of your device. Most are somewhere in the middle of these extremes.
1.3.3: What Your Kernel Does Not Control:
Your kernel does not control your radio, your WiFi, etc, so thus your phone calls, your data, your mms and sms messages are not impacted by flashing a kernel. Sometimes flashing a kernel may somehow cause something that is controlled by the ROM side of things not to work correctly - this is not the norm, though. If you are having these issues, you should look to your ROM first.
1.3.4: Random Reboots:
Random reboots are something that may be caused at a kernel level. If you encounter one, you should immediately on boot (ie, right after the random reboot) open your file explorer go to the folder:
sys/fs/pstore
There should be an annotated-ramoops file and a dmesg file (think of these as kernel logcats). Open the files as text, copy and paste to www.hastebin.com and send the link to your kernel developer. This will help him or her determine if it the reboot was caused by the kernel, and if it can be fixed.
1.4: Sound Practices:
1.4.1. Avoid Multiple Kernel Tweaking Apps:
The use of multiple kernel tweaking apps is contraindicated. If your rom comes with a performance app but you like to use your own instead, freeze your rom's performance app in (using the built-in App Manager, or with an app like Titanium Backup) and clear its app data prior to using your app of choice. Most kernels have an app that is either directly associated or supported by them, or recommended to use with them. Find this out in the thread before you tune your kernel, as having the right options available and interfaced correctly makes it much easier to do so. It's also good practice if you have flashed a custom kernel already to re-flash your rom before flashing another to ensure settings stick properly. This is not always necessary, but it only takes a minute and it's better safe than sorry.
1.4.2: Default Kernel Settings or Using Terminal Command Line:
Some kernels don't even require an app at all. A few of them are tuned on initial setup via Aroma installer - you set your values and can leave it at that. Others can be tuned directly via terminal emulator.
1.4.3. Kernel Tuner of Choice:
Most kernels require some sort of an app to set your values. If your kernel does not come with a particular app associated with it, there are a few options for you. A popular option has always been Trickster Mod. This app offers the basics that you need if using a kernel that does not have a whole lot of odd modifications and is good for beginners who are using a kernel with no recommended app. Advanced users often use Synapse - it is a very confusing app and definitely not for beginners, but it gives you control over basically everything your kernel has to offer. Kernel Auditor is something in the middle, as it does not allow you as much control (or confusion) as Synapse, but it can do a lot that Trickster can't. It's a great starting point for those of you using a kernel with needs Trickster does not meet, or a good place to jump to if Trickster is just getting old, but you're not ready for Synapse.
1.5: Afterwards:
To be sure, there is plenty more reading to be done, depending on which kernel you choose to flash and how advanced you would like to get with it. This is just meant to give those of you who don't know why they would want to do something like flash a kernel a starting point. The decision is yours.
Happy flashing!
Thanks for this man! I agree this needed to be done. It will be very helpful!
Войн Дух
So... If I have a OnePlus One can I use the decrypt file you posted in the second post? I'm kind of a noob... [emoji5]
In all seriousness, XDA is better for having someone like you here to help out.
Watch closely people... You might learn something.
Now I just need to get one lol
Awesome work buddy!
If you need more posts added in or want to transfer a post ownership to another person, just let the mod team know (or you can hit me up as well). Anything to reduce the number of non-essential, non-logcat-attaching posts from the Dev threads is most assuredly welcomed.
Good job and keep up the good work.
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk
micmars said:
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah sorry I always do.
Its nothing personal. Nothing to apologise for. I just think a little disclaimer could be put in. I can draft a very small sentence if you like... Or not
Excellent idea, this thread is, Mic - thanks for endeavoring to provide a one-stop-shop resource for all. Let me know if I can be of any assistance along the way.
Very useful thread. Will be checking in to help whenever I can. Thanks @ micmars
TaPpEd FrOm My N-sIx
rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
Click to expand...
Click to collapse
Yeah i agree. That's why it should be a disclaimer rather than an order
DebianDog said:
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I use folder sync as a plug in to Tasker.
Every time I close my camera app, I use bash shell to look for new files in DCIM and move them to a holding location. I then use folder sync under the same trigger, to open up an SFTP connection to my NAS at home and upload the photos immediately. There is one draw back though. I was taking 4k videos the other day and trying to push 1.5GB over sftp voa hspa is not good for battery, so I need to revise that one.
Also a run a times folder sync every couple of days syncing up my /sdcard with my NAS backup directory, over WiFi whilst I sleep.
Also every Saturday at 3am, my phone reboots, takes a nandroid then syn a that to my NAS too.
As you can imagine, I find it difficult to lose files
DebianDog said:
What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way
Click to expand...
Click to collapse
Same here. Only takes a minute.
DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
On the go storage, tiny little things, I know many themers, and rom devs, use the crap out if them.
I have seen these things sold at very reasonable prices, at brick-and-mortar retailers or online.
I personally back up my entire card to my computer on a weekly basis, and throw the entire thing into my Dropbox.
Sent from my Nexus 6 using Tapatalk
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
cerj said:
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
Click to expand...
Click to collapse
your phones cpu can get to 100C. thats when itll automatically shut down/reboot to cool off. but try as hard as you can, i bet youll never reach it. anything below is normal, depending what you are doing. now you say hot, whats your cpu temp? as feel does not give you any temperature. all feel does is tell you if something is hotter than or cooler than your hand. and if your hand is cooler, itll make the phone feel much hotter. so, when talking about being too hot, we need an actual temp to go with it. i say that because many people report a hot device, when the temp is around 40C, when normal body temps average around 37C.
Title is self explanatory, I'm also looking for the best mods, script or whatever to enhance for pure gaming, im also not opposed to switching my Rom or anything but I would prefer to stay with a touchwiz set up but if I can maximize my gaming experience running something else then hook me UP! Currently I'm running a stock 7.0 rooted with neked4nougat which removed all the crapware lol, i then flashed N4N synapse KERNEL (Thanks btw for creating and maintaining this) but I'm just learning about kernels and we'll plainly put synapse is half English the other half Martian as far as im concerned lmao. If there's an option to overclock the gpu then I'm guessing it's in the martian half lmao
Also I guess I was wondering about if I can somehow create two separate partitions on my machine (64gb) to 32 and another 32. I was using dualboot patcher and i was wondering if i could just have 2 Roms but on there own seperate partition. I like to flash Roms and try new stuff a lot and id just prefer an area I could work with not affected on way by what I'm running originally
Last but most certainly least! Lol how can I add a signature onto my msgs it hought it would show my devices but I guess I missed something, Sorry been reading here for years but just started posting and learning more in depth.