Is it worth overclocking and undervolting Sprints galaxy s 2? - Samsung Epic 4G Touch

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..

Related

Setcpu

Is anyone using setcpu? I bought it back when I had the hero but I'm not sure if it will work now on this phone. I'm rooted using toast's method if that even matters for something like this. thanks in advance!
It's the same CPU as the Nexus and it has settings for the Nexus, so in theory it should work. I had a Nexus before this phone and it worked fine.
I believe, like the Hero, you need a kernel tweak to have true overclocking.
yeah I dont wanna overclock i just want to downclock when the screen is off to save battery. I tried using the nexus one settings but it didnt seem like it was working using on demand. The clock speeds it was showing were kind of goofy. Guess i should wait for the programmer to update it
tkrechel said:
yeah I dont wanna overclock i just want to downclock when the screen is off to save battery. I tried using the nexus one settings but it didnt seem like it was working using on demand. The clock speeds it was showing were kind of goofy. Guess i should wait for the programmer to update it
Click to expand...
Click to collapse
what?!? what do you mean u dont want to oc... theres always room for more speed!
true that but i have always been nervous about burning up the processor hehe
Overclocking would be nice, but I'd also like to save some battery with the on demand profile. Does anyone have it working?
I posted a patch in a thread in the development forum that would enable full support, plus overclocking, but nobody seems to have noticed it.
I might have to buy an EVO just to compile and test kernels... Or, if anybody wants to help me, shoot me a PM.
I used the unrevoked method to root and picked the N1 for the device in setcpu and it seems to be working great with the on demand setting. I have noticed a nice increase in battery life so far.
coolbho3000 said:
I posted a patch in a thread in the development forum that would enable full support, plus overclocking, but nobody seems to have noticed it.
I might have to buy an EVO just to compile and test kernels... Or, if anybody wants to help me, shoot me a PM.
Click to expand...
Click to collapse
Is it linked or built-in?
If it's linked I'd be more than happy to test!
yea i use 1.5.4 pro edition... i make it go to 245mhz while idle/sleep... it works perfectly... and it runs 'ondemand'... if you dont need speed it wont go... i keep it to start at boot, and have ATK to ignore it so it doesnt close... theres no lag btw when it moves back to 998mhz

[Q] overclocking issue

Now me and 4 of my friends have EVOs and I rooted all of them. Some of this EVOs are hardware verson 003 and one of them is 002. 2 are novatec and 3 are epson. We are all running fresh 3.1.0.2 with netarchy-toastmod-4.1.8 bfs, mine has 4.1.9 BETA, but my one friend is running CM6 RC2 because he loves it. Now all of these EVOs can overclock to 1.27 GHz but when we do it they freeze and crash. My one friend can go up to 1.22 just fine but the rest of us are stuck at 1.19. I want to know why this happens. If our phones cant take that much why have it. What's the point we have 5 EVOs here none can handle it. Im I doing something wrong is the a joke WTF!!
All the phones are different. Most can't oc past 1152 without causing reboots, mine included. Other than ridiculous benchmark numbers, I don't think you'll notice a huge difference in performance.
Sent from my FROYO'D EVO using xda app
dglowe343 said:
All the phones are different. Most can't oc past 1152 without causing reboots, mine included. Other than ridiculous benchmark numbers, I don't think you'll notice a huge difference in performance.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
Simple answer, not all chips are made the same. They are made to minimum standards. Your chip is rated to 1 ghz, and thats what the chip company delivered.
Some chips can handle more, but thats just luck.
As far as why do people strive for the high numbers, thats personal preference. Not everyone here cares about 30+ hours of battery life. Some just like the bragging rights.
Unfortunantly, all EVO's are not created equal. You can have the same hardware and version numbers on 2 devices, but one may be able to OC that high, and one may not. This is also why not everyone can run the superbattery kernel from the Baked Snack rom. There doesn't seem to be any rhyme or reason to it.
and c'mon, watch the language. There are rules around here, you know?
fachadick said:
and c'mon, watch the language. There are rules around here, you know?
Click to expand...
Click to collapse
Sorry, I thought we are all adults one swear now and again wont kill anyone
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
actually, cm snap 7.0 and 7.1 are extremely stable, have great battery life and have excellent benchmarks as well. i dont have a single problem with cm snap kernels and i run at 1228mhz when fully charged.
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
that's not going out of the way... it's making the phone as fast as possible. why do anything if you aren't gonna push the limit? how are you gonna develop if you don't push the limit?

[KERNEL]1.28Ghz?!

Just wondering if anybody has tried this kernel yet? Found it over on AndroidMobileJunkie.com (Followed a link in somebody's sig here n XDA that said 1.28Ghz so naturally I was curious lol) Anyways, here's the link for the post over on AMJ. http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-22-oct.11/
yea ziggy's kernel. It's been in discussion in both of the Desire rom port threads. 1.28 is very rough on the processor though, and mostly unstable for a lot of people's phones (mine included), even ziggy admits it's a risky business, but he has proven it is possible.
I am so tempted to try this, but I'm afraid to fry my phone. My go big or go home mentality may make me give in. Wish there was someone who posted on the thread link
I ran it. No problems a 1.28 but really didn't use it long. Here's my Quadrant post in the Desire Z port thread:
http://forum.xda-developers.com/showpost.php?p=8775977&postcount=168
X
I'd imagine that clocking the processor that high wouldn't make much difference than say, 1.19GHz.
In fact, in plenty of ROMs I've tried, anything clocking over 1152mhz actually gives me a decrease in my quadrant scores. Not to say its not a stability issue - I'd assume that most Snapdragons actually clock higher than 998mhz, but then are reduced because that's baseline performance, anything less than 998mhz would get kicked.
I've never had a ROM crash, even running at 1.19GHz, but didn't notice any performance gains, plus, unless you just happen to get a chip that is capable of 1.28GHz no problem, it's probably near bottle-neck anyway.
And Quadrant has several variables way outside of clock speed that can pull 1800's, including just your flavor ROM.
Bottom Line: It's not worth frying your phone just for a barely-existent performance gain. If you happen to have a processor that is incapable of stability at 1.28GHz, you might fry out some transistors, then get stuck with something that freezes if you clock it over 700, let alone the 998 stock.
For me personally 1.28 is no improvement over 1.152. In fact, it gives me worse benchmarks.
sorry for repost
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
I tried this kernal and my camera stopped working...
HeyItsLou said:
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
Click to expand...
Click to collapse
Lou hit the nail on the head. I love the .17 kernel. Im using the new guy with great performance, battery life, charging, and neat transitions. its like a new phone.
I'm using this with a vanilla froyo ROM and my battery life is amazing. Haven't noticed any freezing or any program not working.
Wow!
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
dimebagdan65 said:
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
Click to expand...
Click to collapse
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Nevermind...found it!
ziggy471 said:
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Click to expand...
Click to collapse
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
hajabooja said:
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Click to expand...
Click to collapse
What AOSP kernel??? I only see one kernel, and it references skyraider, which leads me to believe it is a sense kernel
edit: I am dumb. It is a different thread on the same site as listed above
http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-aosp-23-oct.24/
rmaccamr said:
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
Click to expand...
Click to collapse
I didn't take it as such, and I agree with you fully. I prefer somewhere between 1.113 and 1.15. That's the reason I included the init script to set the max at 1.113, which I find very stable and fast, hell I'd say 1865 quad with ID's Z port isn't too shabby at 1.13.
I should be able to get 1.28 more stable with playing with the voltages, it's just that takes time, and I wasted too much this morning doing both AOSP INC and Evo kernels, so I'm worn out for awhile on kernels. I still need to fix the Evo for puertoblack, since it appears I left the debug port out, so no adb for it. lol
Z

So is it just my epic?

So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL
Sounds like you need to do the classic Wipe 3X before flashing.
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.
Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.

[Q] For Noobs: How much is too much?

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

Categories

Resources