With all these tweaks, ROMS, and kernels out there to completely customize your Evo or whatever phone you have. My question is, how to make sure to you don't over do it.
I know that I will look at signatures and see what posters have done to their evos...and try some of those things myself. You can see my signature to see what I've done too.
I am a noob, but I have almost graduated to the next level (whatever that may be). There might be several people like myself who sees all these tweaks and tweaks out themselves in excitement over what you can do to your new toy.
I get the feeling that some tweaks (kernels, CPU governors, ROMS) can often have functions that can overlap and actually worsen performance rather then improve.
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
We can start off with my Evo. Been using Linpack as a reference for performance, and have averaged 36.5 MFLOPS on single thread. How does this stack up?
Interesting, and i am by no means an expert, but here some things I have found out.
Don't use Collins ph battery tweak and Setcpu together. Your CPU will peg and kill your battery life.
Setcpu with a Screenoff profile is unnecessary if you have the kernel governor set to smartass. Smartass sets the cpu to 384 with the screenoff anyway.
Don't let your daughter take your EVO in the tub. That limits performance as well.
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
I meant running at once...
HipKat said:
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
Click to expand...
Click to collapse
Too many things running at once. I figure these phones can handle a lot given the roms people float between...
And you have to remember that all phones are different and that just because I can do something that works great on my phone doesn't mean it will do anything for yours. Or make it worse... Just sayin'
Sent from my PC36100 using xda premium
This question is also hard to answer because peoples taste varies so much.
A good example is myself, I like Sense, but I could care less if it is version 1, 2, or 3, I just want it to work good with no problems. I have never seen a theme that I liked better than stock with just a nice photo as a background. In fact, I could really care less what it looks like as long as everything works well when I want to use it. On the other hand, I have almost no use for any of the bloat apps that came with the phone. I remove almost all of them, Including Facebook, the stock browser, the calender and all Sprint specific apps. But I do have a lot of apps on my phone, about 141 user apps, last time I checked for a total of 264 total apps, including the system apps I have left.
I run Fresh 4.2 rom, that I have modified by removing the aforementioned Sprint bloat and built in apps that I don't want or need. I like Flipz rom's the best because they are stable, reliable, and not updated every day, because no update is needed. Plus he removes the CIQ, which runs all the time in the background. I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock (trying out various kernels now so can't say which one I will end up going with). The only other mods I have done is I have changed the splash screen, because the white one would wake up my wife when I would boot my phone in bed at night. I also made a battery indicator mod that reads percentage and is easier to see. And I am running the V6 script to eliminate the Sense reloads when exiting apps.
Works for me, but I am sure a lot of guys/girls wouldn't like it at all. So, in the end, it really doesn't matter what I am running, unless someone else has the same tastes as me. And isn't that really the point?
I think I do a lot for my phone. But not too much. Everything in my sig + setcpu, chainfire 3d, juice defender etc
Deck's + SZ + SuperCharger script + ViperMod script.
Journeyman83 said:
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
Click to expand...
Click to collapse
How much becomes too much the day you bork your phone when you tweaked something you shouldn't have tweaked, and then turn to the forums for help, only to get an attitude at the people who are trying to help you fix your own f'up. That is when it becomes too much.
wfrandy said:
I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock ...
Click to expand...
Click to collapse
Just curious about which kernel you're referring to here ... thanks.
Nothing is to much as long as you are comfortable with the mods. Nand restore if you mess something up. If you need any help pm me ill help ya.
Sent from my PC36100 using XDA App
Related
CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again
snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.
goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.
DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.
I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.
I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.
Why not the 7.6 with turbo...just wonderin
Running EL29 Odexed Blue Rom with EL26 stock kernal.
Just came from eVo 4G and have no idea if its worth it and if so what setting.
Any advice would be appreciated.
Sent from my SPH-D710 using XDA App
I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.
cidica said:
I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.
Click to expand...
Click to collapse
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.
feelingnerdi said:
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.
Click to expand...
Click to collapse
I think viper mad some stuff for the phone. I know he has a rom out for the phone already so maybe his tweaks are there you could always check the dev section.
My phone had freezing issues at anything higher than 1.4ghz, but even then the only real difference I saw was quadrant scores. Games ran the same, in fact I think the UI actually was choppier when OC'ed. Never really looked into it much though.
I don't even know why I tried it in the first place, I never said to myself "gee, this could be faster.." I guess coming from an HTC Hero it was a habit.
this phone does NOT need to be over clocked; it is so much faster than your Evo, that you won't believe it!
Undervolting and under clocking can give you extra battery life; do a search on the Dev thread, and you will learn lots about it..
I have to say I have tried EVERY ROM on the SGH-T989 and can say none are as stable and have the battery life to match the stock ROM.
I tried Darkside today. It is a clean ROM. Close to stock. I had two complete lockups on the phone that required battery removal in about a 6 hour period. I am not overclocking at all. The ROM has an underclock by default.
I just think it's time to give Samsung and the programmers there a thumbs up for doing such a great job on this phone.
It would be nice if they could release more of the header and source so the developers here could have a better chance of getting a stable ROM built...but until that happens I will just stay with a rooted and stock ROM.
Peace.
I've had no lockups or any problems in the 150 hour uptime I had with Juggernaut 5.0 with 009m faux's kernel.
Battery life is much better as well. Dropping down to 80% after 1 hour of display time.
Cool story bro
chlehqls said:
I've had no lockups or any problems in the 150 hour uptime I had with Juggernaut 5.0 with 009m faux's kernel.
Battery life is much better as well. Dropping down to 80% after 1 hour of display time.
Click to expand...
Click to collapse
I was on the stock ROM for 6 hours yesterday. Surfing, playing games, wifi enabled. Used a bit over 30% from a full charge.
I jumped right into custom ROM's when I got this phone. After going back to stock is when I realized how much the custom ROM's actually degrade the phone.
I have ran Jugg's 4.x with Faux kernel and Bullet kernels. Bullet was faster by a good bit. Battery sucker from hell though.
Do these phones really need the overclocks and tweaks? After going back to stock my opinion is no.
Peace.
You probably didnt follow the directions when installing any of the roms you tried.
If companies like samsung were as awesome as you say they are, would XDA exist at all in the 1st place?
Enjoy your bloatware.
Sent from my SGH-T989 using XDA App
ninrocket2 said:
I was on the stock ROM for 6 hours yesterday. Surfing, playing games, wifi enabled. Used a bit over 30% from a full charge.
I jumped right into custom ROM's when I got this phone. After going back to stock is when I realized how much the custom ROM's actually degrade the phone.
I have ran Jugg's 4.x with Faux kernel and Bullet kernels. Bullet was faster by a good bit. Battery sucker from hell though.
Do these phones really need the overclocks and tweaks? After going back to stock my opinion is no.
Peace.
Click to expand...
Click to collapse
Battery proof? Heres mine with Darkside:
http://db.tt/Dndk1SLW
http://db.tt/qxYSJxJv
http://db.tt/AydX5Jxx
Sent from my SGH-T989 using xda premium
Me being the analytical type....and to just keep this topic fact filled and useful will create a test bed to compare the 'popular' roms versus stock.
I will create a post in the next week to share the results.
Peace.
ninrocket2 said:
Me being the analytical type....and to just keep this topic fact filled and useful will create a test bed to compare the 'popular' roms versus stock.
I will create a post in the next week to share the results.
Peace.
Click to expand...
Click to collapse
Theres already a thread for that:
forum.xda-developers.com/showthread.php?t=1524569
Sent from my SGH-T989 using XDA App
jordanishere said:
You probably didnt follow the directions when installing any of the roms you tried.
If companies like samsung were as awesome as you say they are, would XDA exist at all in the 1st place?
Enjoy your bloatware.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
ninrocket2 said:
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
Click to expand...
Click to collapse
I look forward to your battery testing!
Please include multiple kernels as you test various ROMs, especially faux and Synergy
And perhaps install Juice Defender as a best case.
Personally I haven't experienced any lockups with the two custom T989 ROMs I've tested, but have benefited from the improved battery life dramatically. I'd still love to see a more controlled experiment, however.
jordanishere said:
Theres already a thread for that:
forum.xda-developers.com/showthread.php?t=1524569
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Read it. It is basically a generic thread. No stats or true testing methods just some user comments.
I want to actually test the phone in real life conditions. Watch some vids, talk on the phone, skype/gtalk/YM video call...etc. Actually run consecutive tests across the best ROMS and stock and see how they match up.
Benchmarking is a bit ridiculous....in several aspects.
If a game runs 30 fps or greater...you won't see the difference.
If a game runs a stable 30 fps versus a ROM that peaks at 50 but valleys at 15....you will definitely see the difference.
If a ROM runs 50 fps versus 30 and both are stable...you won't see the difference. The question then is which one uses less battery. The obvious answer is the one running 30fps. Less frames means less redraws and less CPU and GPU.
I just want to once an for all be able to definitively say what each ROM is really doing to the phone with graphs.
Not hard to do. Just takes a real world test model and some time. I think I can test one ROM a day. I will test the most popular ROM's....Juggs, Beast, Darkside, Bombardier, Gingersnap, etc... I have tested them all. I know which ones are legit and which ones aren't.
Peace
ninrocket2 said:
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
Click to expand...
Click to collapse
Agree 100%
Nothing has performed better than stock 2.3.6, rooted and debloated.
Sent from my T989 hunting for Siri Connor
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
zander21510 said:
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
Click to expand...
Click to collapse
Strictly aesthetics can be achieved through the use of different launchers/lockscreens. The point of ROMs/Kernels need to be more than aesthetics. Hence, "some" of the ROMs offered [strictly speaking] are a pretty big disappointment because they're nothing more than themed stuff baked in and offer no real functionality.
I'm REALLY interested in a controlled experiment of battery claims of different ROMs/kernels. Preferably all at stock speeds.
djxcee said:
Battery proof? Heres mine with Darkside:
http://db.tt/Dndk1SLW
http://db.tt/qxYSJxJv
http://db.tt/AydX5Jxx
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Sorry but there is absolutely NO proof in these pictures.
I can see that your phone was on battery for a bit over 1 day.
I can also see that 45% of your phones battery usage was the display...and that the display was on for a bit over 7 hours.
What I don't know is what was your screen brightness set at?
Does the display percentage represent JUST the LED power for the screen or does it also include the GPU/CPU driving the display?
Where are the numbers for the stock ROM?
Those numbers mean nothing when you don't have a standardized test bed and procedure.
Peace.
zander21510 said:
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
Click to expand...
Click to collapse
You can use a home launcher on the stock debloated ROM and get the same results with more stability and better battery life.
I recommend you check DXHOME out to see a smooth launcher.
Peace.
ninrocket2 said:
Sorry but there is absolutely NO proof in these pictures.
I can see that your phone was on battery for a bit over 1 day.
I can also see that 45% of your phones battery usage was the display...and that the display was on for a bit over 7 hours.
What I don't know is what was your screen brightness set at?
Does the display percentage represent JUST the LED power for the screen or does it also include the GPU/CPU driving the display?
Where are the numbers for the stock ROM?
Those numbers mean nothing when you don't have a standardized test bed and procedure.
Peace.
Click to expand...
Click to collapse
Actually, unless that test was completely skewed (e.g. screen on displaying black screen), 7 hours of screen on time + 20 odd hours of standby time with use of radios/connectivity is very very impressive.
2hvy4grvty said:
Strictly aesthetics can be achieved through the use of different launchers/lockscreens. The point of ROMs/Kernels need to be more than aesthetics. Hence, "some" of the ROMs offered [strictly speaking] are a pretty big disappointment because they're nothing more than themed stuff baked in and offer no real functionality.
I'm REALLY interested in a controlled experiment of battery claims of different ROMs/kernels. Preferably all at stock speeds.
Click to expand...
Click to collapse
I agree with your first paragraph 100% and will get the experiment underway with Stock speeds.
Peace.
2hvy4grvty said:
Actually, unless that test was completely skewed (e.g. screen on displaying black screen), 7 hours of screen on time + 20 odd hours of standby time with use of radios/connectivity is very very impressive.
Click to expand...
Click to collapse
When you can refer us to pictures of a base ROM with the same parameters and settings for comparison then I might say it is impressive. But with no base ROM data it is purely speculation.
Peace.
enjoy the drm laden ciq enabled features... That cannot be removed by titanium unless it can magically decompile recompile frameworks on the fly...
Enjoy the Memeroy leaked jobsmanager....
Anyways now thats oout of the way
How much time did you spend between stock firmwares and custom firmwares?
Did you fully wipe the device before flashing and after
Did you do dirty nanoid restores?
A little more info woud be helpfull
at the end of the day if you enjoy stock more great for you.... Use it n move on...
Still missing the point of this thread on a dev website unless you like being trolled.
Hi,
i was wondering which effects the Supercharger script may have on the Desire. I am currently on Sandvolt's ICS Rom, and I read about some people using this. As I don't know that much about technical details of memory management and the original thread on it is a bit confusing, i'd like to know if the Rom really runs faster with it, if it is just some placebo effect or if it even might make the system more unstable.
Do you mean the zRam function in the evervolv toolbox. If so then i tried 18% and used the antutu benchmark before (2783 score with 0%) and after (2648 score with 18%) by just changing the percentage setting. So no cigar for zRam.
I don't know much about the technical nitty gritty of ROMs, Kernels, Mem management etc either, but I can say that yes, Supercharger really does work. I installed on my phone yesterday and, although the changes are subtle and hard to quantify, there is definitely a smoothness to my phone now that wasn't there before.
If you are expecting stars to fall from the sky, or your fingers to burn from the blazing heat of the extra speed, you will be disappointed. But you will notice everything running just that little more fluidly.
Thanks, i just wanted to know if it works and didn't expect it to make my Desire as fast as todays high-end phones. Which options do you recommend?
muellersmattes said:
Thanks, i just wanted to know if it works and didn't expect it to make my Desire as fast as todays high-end phones. Which options do you recommend?
Click to expand...
Click to collapse
I tried it, i think it was option 6 (not sure and can't give it a tru now).
It worked, I did not see much more smoothness as it already was smooth, but it stopped random reboot.
What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?
Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.
berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.
task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )
Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app
Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.