Develop Bugs

Setting a friend up, would like some opinions.

I am going to root and set up a friends phone most likely with aokp (I have used it on my note and it seems solid). Is this a strong choice? I am looking to give him back something with all the bells and whistles along with better performance/battery life. I guess that is somewhat redundant of me to say.
Also what kernels have you found to work well with your rom?
I also want it to be something that he does not need to maintain after I give it to him as it will likely be me updating for him until he gets comfortable with having more control of his device.

Smoothface said:
I also want it to be something that he does not need to maintain after I give it to him as it will likely be me updating for him until he gets comfortable with having more control of his device.
Click to expand...
Click to collapse
Leave the device stock and give him a few hints for apps that will help him do what he wants to do.

martonikaj said:
Leave the device stock and give him a few hints for apps that will help him do what he wants to do.
Click to expand...
Click to collapse
+1 for this. Stock is the best way to go (without root) if he doesn't actually know how to maintain a custom rom or know the security issues associated with rooting hour phone. If he decides in the future that he then wants more from his device, he can learn about custom roms and try flashing himself. Trust me this is the best option, I made this mistake a while ago with a friend of mine who wasn't a tech geek and all he did was complain about the issues associated with the custom rom (cm9) as he had no clue how to fix them and most of the time it was an issue with how the user operated.
Sent from my Galaxy Nexus

AOKP is the way to go for a custom ROM in my opinion. It has so many options over stock that just help ease the use and make so much more of the device.
There is no reason why he would need to keep updating custon Roms if you put something solid on there. It is not like when he runs stock he would update it all the time. He would be running the same stock Rom for a while so what would be the difference if he runs a custom Rom for while. Why would he need to go through every build as others are saying...
Build 33 was just released for AOKP. I would wait to see the bug list before loading something on his device that will be on there for a while. Your best bet would wait till the next milestone build comes out so all the bugs will be squashed and he won't have to worry update updating...
I have also found the stock 4.0.4 kernel to be the best so far. I have tried other kernels and unless you are into playing with voltages and overclocking stock is your best bet.

As a new gnex user I found that stock kernel and rom ate battery quickly.
Coming from a nexus s 4g aokp was my top choice. So I went with that and lean kernel.
I put min/Max @ 7something/920
Using interactive
Battery life increased significantly
Also speed and my phone is fully customized to my liking... just my personal experience and opinion
sent from my so icey GalaXxy Nexus

Aokp is the way to go. Also he doesn't need to constantly update the rom. Just flash the latest milestone and he can use it for the next 2 years really.

[Q] Are the risks worth the benefits?

I got a brand new Galaxy S3 on Monday. Coming from an Inspire 4g and an HD2 before that, I'm not new to flashing ROMs or anything. I rooted that phone almost instantly, because it was a refurbished phone and didn't have a warranty. Now on this one, I'm a bit hesitant to root or flash any custom ROMs.
I've also read a bit about stock vs AOSP ROMs... can any one give me an example of each? Preferably a stable, JB based ROM? I would like to use a stock based ROM so I can have all my apps and settings back when I flash. This stock ROM is eating up battery life rather quickly so I want something quick, stable, and visually pleasing without any bloatware.
I am aware that I can just return my phone to the store within 14 days if it doesn't work... an employee told me they don't even look to see if it's rooted or has a custom ROM.

Synyster06Gates said:
I got a brand new Galaxy S3 on Monday. Coming from an Inspire 4g and an HD2 before that, I'm not new to flashing ROMs or anything. I rooted that phone almost instantly, because it was a refurbished phone and didn't have a warranty. Now on this one, I'm a bit hesitant to root or flash any custom ROMs.
I've also read a bit about stock vs AOSP ROMs... can any one give me an example of each? Preferably a stable, JB based ROM? I would like to use a stock based ROM so I can have all my apps and settings back when I flash. This stock ROM is eating up battery life rather quickly so I want something quick, stable, and visually pleasing without any bloatware.
I am aware that I can just return my phone to the store within 14 days if it doesn't work... an employee told me they don't even look to see if it's rooted or has a custom ROM.
Click to expand...
Click to collapse
I think it is worth it. Look through the S3 forums and you'll find various options for ROMs that meet your needs. I'm running Serenity v1.1 which is a JB GNote2 port. It is stable and works well for me.
I would also read MrRobinsons stickied post about Rooting. Towards the bottom of the OP there is a tool mentioned that he made that will help you de-bloat. It works wonderfully. http://forum.xda-developers.com/showthread.php?t=1739426

I noticed it says the ATT one is " New Image Based off ATT I747UCALG1"
I have the newest software, would I be able to update after doing this? Or will that put me right back where I am now

I just put CM 10 over the stock ICE. Incredible difference. Go for it!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

It really depends on what kind of user you are. If you're a user that prefers stability and is not that much of a 'power user', then the risks might be troublesome for you. If you're the user that wants adventure and doesn't mind fixing bugs every now and then, then give it a go. I'm a user that's in a middle of both - I like stability and I'm kind of a power user and I also enjoy fixing bugs because I learn something new and the experience of fixing bugs increases my knowledge of how my phone works. IMO, the most stable ROM I've used so far is CM10 - I'm currently using a nightly build and it works great so far - although it kinda has a few problems like some programs crashing unexpectedly and some phone functions not working properly. My advice is that you decide first what type of user you are and then evaluate the risks you're going to take - there's a high chance that you might brick your phone even if you've rooted a phone before as there are different specs for every phoen and one mistake could cause a serious trouble.

SGS3 aokp jb, d2att 3.9.12 by task 650+ktoonsez kt747 kernel
Rooting is easy on this phone, use galaxys3root.com for figuring out rooting and here's a link to aokp jelly bean 4.1.2 by task650 and ktoonsez it is by far in my opinion the best ROM out for the att variant right now its very light and very fast with more customods then you can imagine! Just get rooted install latest cmw recovery I reccomend the touch version and read all of task650's steps for flashing and I guarantee you will be pleased rooting this phone is definitely worth it just wait til you try it with it over clocked to 2100megahertz it crazy fast! I phone ain't got jack on this!
http://forum.xda-developers.com/showthread.php?t=1766684

bg4710 said:
Rooting is easy on this phone, use galaxys3root.com for figuring out rooting and here's a link to aokp jelly bean 4.1.2 by task650 and ktoonsez it is by far in my opinion the best ROM out for the att variant right now its very light and very fast with more customods then you can imagine! Just get rooted install latest cmw recovery I reccomend the touch version and read all of task650's steps for flashing and I guarantee you will be pleased rooting this phone is definitely worth it just wait til you try it with it over clocked to 2100megahertz it crazy fast! I phone ain't got jack on this!
http://forum.xda-developers.com/showthread.php?t=1766684
Click to expand...
Click to collapse
In my opinion, I would prefer this guide first before that: http://forum.xda-developers.com/showthread.php?t=1739426
That guide shows information that's what you're probably going to need if you don't want your phone to get out of warranty and if you want your phone's radio functioning properly. I followed that guide step-by-step and thoroughly and so far, I've achieved the desired result which is not to trip the flash counter. Also, I would also suggest that you search through the forums for revised rooting guides before you root your S3.

Synyster06Gates said:
I got a brand new Galaxy S3 on Monday. Coming from an Inspire 4g and an HD2 before that, I'm not new to flashing ROMs or anything. I rooted that phone almost instantly, because it was a refurbished phone and didn't have a warranty. Now on this one, I'm a bit hesitant to root or flash any custom ROMs.
I've also read a bit about stock vs AOSP ROMs... can any one give me an example of each? Preferably a stable, JB based ROM? I would like to use a stock based ROM so I can have all my apps and settings back when I flash. This stock ROM is eating up battery life rather quickly so I want something quick, stable, and visually pleasing without any bloatware.
I am aware that I can just return my phone to the store within 14 days if it doesn't work... an employee told me they don't even look to see if it's rooted or has a custom ROM.
Click to expand...
Click to collapse
Here's another thought.
I came from an HD2 which from day one, I was flashing roms and kernels like crazy. I became very good at customizing and finding what I liked. I even worked very closely and aided some of the more popular rom devs. I even designed or hacked out some of my own mods including a memory management system. BUT...I could never achieve with the amazing HD2 (ahead of it' time in many ways) what the Stock Rom ICS and my S3 has done out of the box.
I meant to go to CM10 or a custom rom of some sort, but the stock rom has been a DREAM of stability which I never achieved with the HD2. It's rooted and that allows me to customize features and have more choices for apps that require root etc. I fixed a few things, added Go Launcher EX which was a huge improvement and offers awesome features, tweaked etc., and this thing runs near perfect. It's plenty fast enough. My I747m has 2gb ram and I could write a book as to why I think the 2gb makes a world of potential difference depending on setup. Also, as usual, I have frozen quite a few stock apps with Titanium Backup and replaced them with my favorite apps. (eg Handcent SMS, Kaiten Email, Boat Browser) I miss some CM features that I used to have but I have great speed, fluidity, reliability and generous flexibility....so for now...I am not doing a custom rom. FOR ME personally, I need to stay with a stable rom because I just came from near 2 years of FIXING and tweaking and killing hours upon hours.

I would be happy with just rooting it, as long as I could remove bloatware!

Synyster06Gates said:
I would be happy with just rooting it, as long as I could remove bloatware!
Click to expand...
Click to collapse
That's what I would do Synyster. It's great to explore, tweak, flash....etc., but if you want the best bang for the buck, best use of time, least amount of troubleshooting and testing.... imho...
- root and install custom CWM for easy flashing of updates/tweaks and for easy backup.
-buy/install Titanium Backup pro and either remove or safer....FREEZE bloatware.

There's a lot of cool things with the AOSP roms. However, I'm at the point where I've become OCD with flashing nightlies. The more I flash ROMs the more nit picky I have been. I'm looking to go back to stock firmware, debloat, root, and CWM. I think that'll be good enough for stability IMO...

I'd say so!

[Q] Battery life: stock VS custom roms and remedies

Hi guys!
I've been playing around with my GNex (GSM, stock 1750mAh battery) since last july and my biggest concern is (still) the battery life.
I've noticed that the couple stock rom + stock kernel (the ones the phone come with) is much better than any other custom rom+kernel.
Here comes my (maybe stupid) question: is the battery life somewhat related to the (de)odexed status of the rom?
I mean, I've been looking for all kinds of solutions to take advantage of those features offered by AOKP or PA without suffering from BL issues, but I find silly to sacrifice stability/smoothness/responsiveness/always-on-connection/brightness/whatsoever to gain not that many mins of juice. And I really wonder what is the sourcery Google adopts to make its roms so stable, responsive and battery friendly (e.g. no custom rom/kernel can achieve as much BL as the stock ones). Put differently, with the stock rom/kernel, I can leave 3G always on, auto-sync always on, haptic feedbacks on, location services always on (but GPS) and the battery survives for more than 24h; while, with custom roms/kernels, I could switch everything in the list off and still the battery wouldn't last that long (ceteris paribus).
Could you, please, explain me how it works?
Is there really no way to improve BL other than those listed above?
And, finally, does odexing the system apps (on custom roms) do the trick?
Cheers!
P.s.: the answers I'm looking for may already be in other threads.
If so, I apologize, but I tried googling different keywords many times, and got no interesting results.

For me the biggest source of battery drain is the screen by far. Maybe you enjoy custom ROMs more than the stock one and you keep the screen on more I would think that a custom ROM would be more battery friendly. Which ROMs have you tried?

Endriu90 said:
Hi guys!
I've been playing around with my GNex (GSM, stock 1750mAh battery) since last july and my biggest concern is (still) the battery life.
I've noticed that the couple stock rom + stock kernel (the ones the phone come with) is much better than any other custom rom+kernel.
Here comes my (maybe stupid) question: is the battery life somewhat related to the (de)odexed status of the rom?
I mean, I've been looking for all kinds of solutions to take advantage of those features offered by AOKP or PA without suffering from BL issues, but I find silly to sacrifice stability/smoothness/responsiveness/always-on-connection/brightness/whatsoever to gain not that many mins of juice. And I really wonder what is the sourcery Google adopts to make its roms so stable, responsive and battery friendly (e.g. no custom rom/kernel can achieve as much BL as the stock ones). Put differently, with the stock rom/kernel, I can leave 3G always on, auto-sync always on, haptic feedbacks on, location services always on (but GPS) and the battery survives for more than 24h; while, with custom roms/kernels, I could switch everything in the list off and still the battery wouldn't last that long (ceteris paribus).
Could you, please, explain me how it works?
Is there really no way to improve BL other than those listed above?
And, finally, does odexing the system apps (on custom roms) do the trick?
Cheers!
P.s.: the answers I'm looking for may already be in other threads.
If so, I apologize, but I tried googling different keywords many times, and got no interesting results.
Click to expand...
Click to collapse
Thats strange, to me battery life is better with custom ROMs and kernels

R: [Q] Battery life: stock VS custom roms and remedies
sirxdroid said:
For me the biggest source of battery drain is the screen by far. Maybe you enjoy custom ROMs more than the stock one and you keep the screen on more I would think that a custom ROM would be more battery friendly. Which ROMs have you tried?
Click to expand...
Click to collapse
Lol, maybe you're right!
Until now, I tried AOKP and PA roms and franco, AirKernel, GlaDOS and stock kernels (all possible combinations). I found that PA and GlaDOS are the best custom couple, but still not comparable with the factory ones.
However, even tough I have no technical numbers, the usage on custom stuff had been more or less the same as on stock things (although I became a pie-control addict). And what I know for sure, the BL gap is mostly due to screen (i.e. by staring at the launcher home screen for 5 minutes, the battery drains faster with custom roms than with stock roms - still, ceteris paribus).
NexusS4gFreak said:
Thats strange, to me battery life is better with custom ROMs and kernels
Click to expand...
Click to collapse
I know that's strange. Things used to work as you say with my HTC Desire. But since I've switched to the Nexus S (and then to the GNex), I strongly preferred stock stuff just because of battery life
Sent from my stockish Galaxy Nexus using xda app

[Q] ROMs that enhance battery performance?

I recently bought a used Sprint Galaxy S3, it is the SPH-L710 model.
It works great, I like it, I got it rooted with no problem, and got CWM flashed to it and I'm getting ready to flash a ROM.
I've been searching forums and sites for about 2 days for the ROM I want to use.
I'm mainly looking for something that enhances my battery performance, the reason for this is when I first got the phone, I updated it to the 4.4.2 KitKat when I first turned the phone on and the battery life was terrible, like I would charge it to 100% and use it browsing the web for about 10 mins and lose sometimes upwards of 10+% within that 10 minutes.
I searched around and found 2 Apps that I am using right now, one is a battery doctor type thing, the other is an app called Battery Saver (root) it changes some stuff and is supposed to make battery life better, since I have started using these 2 apps my battery life has increased, but it still seems to drain a little fast. So I would like to try and find a ROM that perhaps has tweaked the battery life.
Does anyone have any opinions on battery life for any of the ROMs here that would work for my device, like perhaps which one that you have tried that extended your battery life? I know I could just try them myself, but I am hoping to save a bit of time and see if anyone has some input.
Also another quick question, is there a way to test my battery and see if its just bad? A friend mentioned that the battery could have just gone bad so I'd like to check that if possible.

A. S3s aren't known for their amazing battery life. My battery does not go very far either, talking on the phone, which I do a lot for work, gobbles up the battery immensely. (Like 100% to 80% in 30 minutes.) Web browsing is another battery hog.
B. ROMs are only going to do so much as far as extending your battery life. Just bear in mind -- the lighter the ROM, the less battery it'll likely consume.
You'll do more to save battery by flashing a custom kernel on top of a light ROM that'll allow you undervolt/underclock. But, you want to make sure you flash the correct kernel to the correct ROM base (e.g. Touchwiz kernel for Touchwiz ROMs, AOSP/CM based kernels for AOSP/CM based ROMs).
I personally use the DKP kernel found here in the S3 original development thread.
Be careful w/ underclocking and especially undervolting, as this can cause the phone to freeze up. It's also important to choose a governor that has a nice balance between performance and power savings. (I like the freelunch governor.)
Hope this helps.

Higgs_Boson said:
A. S3s aren't known for their amazing battery life. My battery does not go very far either, talking on the phone, which I do a lot for work, gobbles up the battery immensely. (Like 100% to 80% in 30 minutes.) Web browsing is another battery hog.
B. ROMs are only going to do so much as far as extending your battery life. Just bear in mind -- the lighter the ROM, the less battery it'll likely consume.
You'll do more to save battery by flashing a custom kernel on top of a light ROM that'll allow you undervolt/underclock. But, you want to make sure you flash the correct kernel to the correct ROM base (e.g. Touchwiz kernel for Touchwiz ROMs, AOSP/CM based kernels for AOSP/CM based ROMs).
I personally use the DKP kernel found here in the S3 original development thread.
Be careful w/ underclocking and especially undervolting, as this can cause the phone to freeze up. It's also important to choose a governor that has a nice balance between performance and power savings. (I like the freelunch governor.)
Hope this helps.
Click to expand...
Click to collapse
Thanks!
That gives me an idea of what I should start looking for, and I'll check out the DKP kernel as well..
I just thought of another question I had, maybe you can help me with it too.
Since I'm running Android 4.4.2 on my device, would I need to find a 4.4.2 ROM to flash?
For instance could I use a 4.3.1 ROM on my 4.4.2 device?

vagabond007 said:
Thanks!
That gives me an idea of what I should start looking for, and I'll check out the DKP kernel as well..
I just thought of another question I had, maybe you can help me with it too.
Since I'm running Android 4.4.2 on my device, would I need to find a 4.4.2 ROM to flash?
For instance could I use a 4.3.1 ROM on my 4.4.2 device?
Click to expand...
Click to collapse
It doesn't matter which Android version you decide to go with. Just avoid two things:
1. Do not flash an older bootloader than the one you are currently on (e.g. If you are currently on ND8, do not flash any older bootloaders like MK5 or MD4).
2. Do not flash any modems older than the one you're currently on. Your modem version can be found in Settings -->About Phone --> and the last three letter/number combination under "Baseband Version". Hint: The baseband version also tells you which bootloader/ROM you're on.
Doing either of these, will trip Samsung's KNOX security feature, tripping the kill-fuse, and suddenly, you'll have yourself a nice hard brick.
I know that probably sounds intimidating, but I assure you if you avoid those two things, you can flash any D2LTE ROM you please. (D2LTE ROMs will work with the Sprint S3.)

idk man the batter life of my S3 lasts 2 days where my Infuse 4g would last less then one with a new battery.....so by far the best battery life I've had in a while

Higgs_Boson said:
It doesn't matter which Android version you decide to go with. Just avoid two things:
1. Do not flash an older bootloader than the one you are currently on (e.g. If you are currently on ND8, do not flash any older bootloaders like MK5 or MD4).
2. Do not flash any modems older than the one you're currently on. Your modem version can be found in Settings -->About Phone --> and the last three letter/number combination under "Baseband Version". Hint: The baseband version also tells you which bootloader/ROM you're on.
Doing either of these, will trip Samsung's KNOX security feature, tripping the kill-fuse, and suddenly, you'll have yourself a nice hard brick.
I know that probably sounds intimidating, but I assure you if you avoid those two things, you can flash any D2LTE ROM you please. (D2LTE ROMs will work with the Sprint S3.)
Click to expand...
Click to collapse
Wew! Thanks for that info, you may have saved me from a terrible mistake lol.
One of the ROMs I was looking at was using the MD4 bootloader, so that would have been a no-no xD
Thanks a lot for all your help, I learned a few things from it, epspecially about the bootloaders and modems having to match, I had no idea about that. Now that I know that, it opens up a few more possibilities for ROMs I can use!

vagabond007 said:
Wew! Thanks for that info, you may have saved me from a terrible mistake lol.
One of the ROMs I was looking at was using the MD4 bootloader, so that would have been a no-no xD
Thanks a lot for all your help, I learned a few things from it, epspecially about the bootloaders and modems having to match, I had no idea about that. Now that I know that, it opens up a few more possibilities for ROMs I can use!
Click to expand...
Click to collapse
Fun fact: The bootloaders and modems didn't always have to match.
Samsung wanted to be able to market their devices to business entities, and in order to do that, they developed the KNOX security feature.
Once it's on your phone, it's not coming off. It matters to corporate security policy people, because they want devices that aren't going to be compromised if someone tampers with them.
And, as you can see, the wrong kind of tampering makes the phone completely unusable and unrecoverable.

Higgs_Boson said:
Fun fact: The bootloaders and modems didn't always have to match.
Samsung wanted to be able to market their devices to business entities, and in order to do that, they developed the KNOX security feature.
Once it's on your phone, it's not coming off. It matters to corporate security policy people, because they want devices that aren't going to be compromised if someone tampers with them.
And, as you can see, the wrong kind of tampering makes the phone completely unusable and unrecoverable.
Click to expand...
Click to collapse
Right now I'm sort of leaning towards LiquidSmooth, Quantam4, or Tribute ROM, still sort of looking around though.
If you don't mind me asking @Higgs_Boson, which ROM are you using?
Also, to the other poster, my mothers GS3 is the same way, hers will last upwards of a day and a half, then again she doesn;t use hers for much, while I'm on mine like a computer lol.

vagabond007 said:
Right now I'm sort of leaning towards LiquidSmooth, Quantam4, or Tribute ROM, still sort of looking around though.
If you don't mind me asking @Higgs_Boson, which ROM are you using?
Also, to the other poster, my mothers GS3 is the same way, hers will last upwards of a day and a half, then again she doesn;t use hers for much, while I'm on mine like a computer lol.
Click to expand...
Click to collapse
Right now, I'm on CM11.
I usually switch between two that are my favorites:
CyanogenMod or Paranoid Android.
If you want an all-in-one, there is always PAC-ROM, which includes Paranoid Android, AOKP, and CM all under the same roof. (But then, we get back to that thing about light ROMs.)

issmal out
Higgs_Boson said:
Right now, I'm on CM11.
I usually switch between two that are my favorites:
CyanogenMod or Paranoid Android.
If you want an all-in-one, there is always PAC-ROM, which includes Paranoid Android, AOKP, and CM all under the same roof. (But then, we get back to that thing about light ROMs.)
Click to expand...
Click to collapse
I completely overlooked CM
Is CM11 compatible with the DKP Kernel you were telling me about?

yep
Yes it is. I'm that combo at the moment

im currently running wicked X 8.0

6th_Hokage said:
im currently running wicked X 8.0
Click to expand...
Click to collapse
I'm in the process of d/ing that right now. U like it?

jbnorton0524 said:
I'm in the process of d/ing that right now. U like it?
Click to expand...
Click to collapse
personally yes after i replace the system UI with the Stock ND8/NDC one and same with the TW Framework and TWframework-res.apk and use the Stockish theme for it.....i like the stock look what can i say but im using xposed at the same time for little things here and there but if you don't want to replace somethings and want it to work 100% use the PCB theme that it comes with.......but either way its pretty smooth and fast and the battery lasts for 2 days with some gaming and listening to music with viper4android installed and making calls and texting the one thing that i would say drains my battery is watching videos but you'll be satisfied

Wow you arent joking. This is one of the best ive seen lately. Nice.

jbnorton0524 said:
I'm in the process of d/ing that right now. U like it?
Click to expand...
Click to collapse
Wicked X, Tribute and Conquest Singularity are all 3 very good ROMs with pretty fair battery life. As stated, Kernal Settings do make a world of difference! I'm on Singularity with latest KT747 Kernal and love it :]

Cm 11 or paranoid

ROM with best battery life!

*If a good thread already exists about this, please link it.*
Hey Peeps!
I have probably tried all ROM's (Sense & Stock) on my aging M8, and the only ROM that comes with good battery life is ARHD. But, as we all know, it has its weaknesses.
Waiting for responses from you guys!

We do not compare ROM's that has the greatest etc. The best way to find it out is to try each ROM which fits you.
Sent from my HTC One_M8 using Tapatalk

There is no such thing as a ROM with "best battery life" that applies to everyone, in every situation. There are simply too many variable on how different folks use their phones (what apps, screen on time, etc.) your local reception, whether on LTE or 3g, WiFi, Bluetooth in use, etc. etc. etc.
Folks have very different experiences for each ROM. Seriously, I've seen some ROMs where I can get 2 days of light usage, where others on the same ROM will say battery life sucks and only lasts a few hours.
You need to use trial and error, and use what ROM works best for you. There are no shortcuts to that process.

XDA changed their rules some time ago to allow comparison threads as long as they dont turn into a flame war. Please keep this thread civil and respect everyone opinion.
Thanks
Wolf

redpoint73 said:
There is no such thing as a ROM with "best battery life" that applies to everyone, in every situation. There are simply too many variable on how different folks use their phones (what apps, screen on time, etc.) your local reception, whether on LTE or 3g, WiFi, Bluetooth in use, etc. etc. etc.
Folks have very different experiences for each ROM. Seriously, I've seen some ROMs where I can get 2 days of light usage, where others on the same ROM will say battery life sucks and only lasts a few hours.
You need to use trial and error, and use what ROM works best for you. There are no shortcuts to that process.
Click to expand...
Click to collapse
what type of effect does it exist on kernel with battery life?
what are the good & bad things of custom kernel? and also can kernel affect on radio?

umesh.lk said:
what type of effect does it exist on kernel with battery life?
what are the good & bad things of custom kernel? and also can kernel affect on radio?
Click to expand...
Click to collapse
I'm not that knowledgeable about kernels, and in particular don't mess much with custom kernels.
But what I would say, is that those questions aren't any more answerable then the previous points about custom ROM vs. battery life. Overclocking and undervolting allowed by custom kernels, as well as the choice of governors (which provide various balances of performance versus power usage) will all have some affect on battery life. But the experience is going to vary greatly from one user to another.
Similar to trying custom ROMs, just make a TWRP backup before flashing anything; try some custom kernels, or tweaking kernel settings; and see if the results are desirable to you.
The only real "bad" thing about custom kernels, is that some settings may result in instability, boot loops or no boot. But as long as you make a TWRP backup (before flashing kernels or changing kernel settings), you can easily recover from any such problems.
You also may or may not get the performance or battery life you are looking for, from custom kernels. Which is the main reason I've not been one to personally mess with custom kernels too much. With what kernel tweaking I did on other devices, I never saw a significant performance difference. And certainly not enough to warrant the hassles of system crashes and no boots I was getting.
But others will swear by custom kernels, different governors, etc. Again, your results can and will vary. So that is why its best to try for yourself; and not take another's advice as gospel.

Viper rom is quite good.