yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] MysteryEmotionz:
I got the evo on release day. It was my first smart phone. I thought it was bad ass. I dropped it in the toilet and then my problems started. I called sprint to issue an insurance claim. I told them I lost it. They told me I didn't have insurance on the phone. After fighting with them for a a week about it they told me they if I signed I new 2 year contract I cab get another evo as I upgraded again. They also credited my account 150. I couldn't find another evo any where. Then I found out bout the epic. I haven't looked back yet.
[Epic 4G General] Walzbeer:
I got my evo on 6/12, just picked up my epic 9/25. It was long enough for me to realize that while the evo is quite baller, especilly coming from the G1, it was undercooked.

We all know the problems it had/has. The one that gets me the most though is having all that power and still having to cap the framerate. That, and the insane compression of mms images, but that's a sense issue.

So far I'm REAL ****ing happy with it. I really missed a good hw keyboard. The screen and camera are mighty impressive and touchwhiz isn't nearly as offensive/intrusive as sense (its more like a theme imo) when you get adw on it.

This thing is going to set the standard once it receives 2.2.
[Epic 4G General] J3ff:
listen bryan, I'm asking him because I am playing with the IDEA of trading the epic for the evo. however if the EVO is WORSE on battery in stock form then I guess I should just go jump of the Brooklyn bridge
[Epic 4G General] lordsandwich:
Let us know if you get 4G on the way down.
[Epic 4G General] MvP77:
Just thought I chime in. I'm the opposite. I went from a epic to a evo. I love my evo, but the epic is also a great phone and I'm sure it will get better with 2.2 (and hopefully touchwiz 3). You can't go wrong with either imo. My favorite phone is still my nexus one though.

If gaming and moving watching is important to you then its hard to beat the epics gpu and codec support, plus beautiful screen.

Evo 4G on XDA app
[Epic 4G General] saywhat4118:
Definitely a lot happier with the Epic 4G. kinda wish I could buy something to stop the keyboard from coming out. I don't use it at all and i would love to buy a case or something to strap it up.
[Epic 4G General] ultra78721:
I bought an evo and i liked it ;) But then the epic was announced with a better screen and faster cpu supposedly!!And the Full slide out keyboard :D

I was under the 30 day return, so I took it back after 28 days of having it.

When I got the epic I noticed the more beautiful rich color bright screen,the camera was way better than the evos especially in dark conditions.

With the evo I could not take a clear picture or video of my aquarium.It Was to dark no matter what settings I set it to.My aquarium had good lighting ,but i could not add extra light from the outside because then u get reflection.:mad:

When i got the epic first thing i did ,was go straight to my aquarium and started snapping pictures.

Instantly Without any adjustments, nice pictures and video came out:D

Besides that.. faster noticeable scrolling and opening apps. The full keyboard I love it.

Once the Epic has all its issues worked out !! The EPIC is gonna be a beast.

I like the evo ...but i love the EPIC...no regrets whatsoever.
[Epic 4G General] stever5:
Epic or EVO?

I've had both, I got rid of my EVO over the root being taken away with no way to downgrade after one of the updates, and some major bugs in that update - Probably they've been fixed, HTC Is fairly responsive. I didn't care about root until some of the bugs, but after using it I won't be going back to non-rootable phone again.

I now have the EPIC, the keyboard is good (not great, it misses keys often if you type fast), the screen is small but better colors (For many things, like email, the larger screen was nicer), the swype is ok (I prefer the physical keyboard, but I'm finding I usually use swype instead of on screen keyboard if I'm doing something very small and don't want to open the phone), and speed overall seems better as others have said.

One BIG thing I'd point out to users on xda especially - Samsung released the source of their update BEFORE the update got pushed out - That's nice sign for developer community support. HTC on the other hand hasn't been THAT good about source.

The single biggest deciding factor for me to like the Epic more - I find the keyboard absolutely necessary for remote desktop / vnc type work, the on screen keyboards just don't cut it when you lose most of the information on the screen - iPads have a transparent keyboard available but I didn't have much luck finding one for my EVO - I haven't looked lately, but that seems like a major missing feature of the EVO, at least for that specific type of work on the phone.

It would be nice to see 2.2 running on the Epic with support from Samsung, they've done bad about supporting their other Android devices (Samsung Moment especially) so I'm reluctant about that - But I'll be keeping my Epic.. Next year I'm sure I'll have another phone but this has 90% of the features I want.

Steve Radich

www.BitShop.com/blogs.aspx
[Epic 4G General] SwimDrewid:
What kernel are you running?
[Epic 4G General] dever76:
In my case, yep, the battery life is much better with the Epic. I average about 12 hours of heavy use per battery. I carry 4 spares since they are small, just in case I'm not able to reach a charger for a few days. Carrying extra batteries is like rule #23 of the man law, never leave home without a knife and always be prepared.

Of course you have to be pro-active on setting your phone up to last, use juice defender, condition your batteries properly before use, don't run bluetooth, wifi, or GPS unless you need it. Underclock when you don't plan on using the phone to its maximum capabilities, but just need to stream some music, and maybe undervolt if your unit is stable. Preventing apps that don't need to sync or run, or otherwise use resources when you don't need them leveraging your batteries life versus their need to update is also very important. I constantly run into Android setups that have a bunch of crap loaded on start that just doesn't need to be. It's no wonder some people only get 4-6 hours out of a charge.

I'm not saying that you need to even run a task killer, just run something that prevents stuff like Pandora, Facebook, Media Hub, AppBrain etc from running and using your data connection on startup.

If you're of the mindset that you can't be bothered to do these things, then it's really a matter of ignorance is bliss and lack of understanding of what your phone is doing that's preventing you from possibly getting 12+ hours out of a charge.

Root it, back it up, tweak it, flash it, don't settle for stock, make it yours and you'll be happy.:cool:
[Legend Android Development] TheGrammarFreak:
As of CyanogenMod 6.1 this is built in. As long as you're using RC1 or above you don't need this. If you want to overclock stock 2.2 you need to use BlaY0's latest kernel

Everything is the quote below is there for history. If I had control of the second post I'd put it there... Over the next few days I'll write a bit about overclocking on the newer ROMs (BlaY0's ROM, post CM 6.1 ROMs). Essentially, you do not need to flash a new kernel to overclock on those, they have it built in. All that has changed is that you need to use scripts or SetCPU (or similar) to boost the CPU speed on boot. BlaY0's ROM will got to 806, CM will go to 864.
[Legend Android Development] snowhs:
nice job dude.

In last days I tried up to 806.after all the afternoon I got the first reboot.And I noticed the reduce of battery life.

Now my Legend running at 787
[Legend Android Development] BlaY0:
Nice job m8 ;) newbys will now most probably stop whining and start grinning :D

Or not ;)
[Legend Android Development] beer2nd:
nice post ^^
[Legend Android Development] Learners Lisence:
GrammarFreak, please dont mind my being a little critical.

The subject does deserve a place amongst the other "How Tos" in the very first post in this forum but it needs to be handled with some degree of maturity IMO.

You must also give credit to Kyosa and dumfuq with appropriate links alongside because they were the very first ones to bring this idea to our community. Its unfortunate that Kyosa could not come back and give it a "complete" form as such.A link to the Benchmarks of various roms with oc by snakehult should also be given even though it may not have much significance.

Then again, overclocking Legend is possible with stock roms as well.

You may say that I should go ahead and do such a 'how to'.....in that case thanks for the effort. carry on....
[Legend Android Development] TheGrammarFreak:
Arghh, I knew I forgot something. Credits are on their way. Thanks for the heads up.

May I ask what you mean by "maturity"? Where am I not mature?
[Legend Android Development] TheGrammarFreak:
I really hope so. Oh well, patience and they'll learn.
[Legend Android Development] rajasyaitan:
Excellent guide Grammar. Hopefully with this thread people will stop asking and start learning aout overclocking. Job well done an a guide well written.

Cheers mate.
[Legend Android Development] Corra:
It would be useful to explain how to enter clockworkmod recovery and flash another kernel in the case the phone doesn't complete the boot
[Legend Android Development] LuckyPhil88:
In my opinion it isn't necessary, that are basics you have to know otherwise this howto have to start with "how i root my legend"

Btw thanks for this howto, one month earlier and i would have saved a lot of time :D
[Legend Android Development] Corra:
Many people asks what to do when encountering boot loops
[Legend Android Development] LuckyPhil88:
okay, you are right, but in dumfuq's thread it is described that not every legend is able to run with 806 or 844 mhz...so those boot loops are signs that you have to try another frequency/kernel, aren't they?

no offense, if you tune your car for example and your engine won't start because you tuned too much you go back to defaults, don't you?
[Legend Android Development] TheGrammarFreak:
FML

I just spent half an hour writing a bit on clockworkMOD, and recovering from bootloops, and my internet died when I clicked "save". I've now regained my internet, but lost all my work. Grr... I'll rewrite it a bit later.
[Legend Android Development] Corra:
Of course, but people need to know how to go back to defaults without using rom manager, if their system doesn't boot
[Legend Android Development] TheGrammarFreak:
I'm working on it. Check back later on today

EDIT:

Check back now actually, just finished. Also, do these OC kernels work on ROMs that aren't CM based?
[Legend Android Development] Corra:
In the case of boot loops, from clockworkmod recovery I find way more practical to flash a different kernel with less OC (downloaded before or copied to sd from the pc). Why restore an entire backup? :)
[Legend Android Development] dumfuq:
I gotta say thanks for this. The part about the optical trackpad while in recovery just made my life much easier :)
[Legend Android Development] TheGrammarFreak:
How so?
[Legend Android Development] AllWin:
I've tested for a short time "768" and "804" kernels on stock 2.03 ROM, both seemed to work fine.
[Legend Android Development] TheGrammarFreak:
Cool, thanks for that. I'll update the op later on, when I'm home.
[Legend Android Development] BlaY0:
That's right! If you are testing kernels, there's really no need to do the whole nandorid backup/restore. You just have to have last working kernel update (just kernel or whole boot.img) handy on SD which you flash via recovery if something goes wrong while testing.
[Legend Android Development] TheGrammarFreak:
This is a guide for newbies, this is the easiest way of doing it...

EDIT:

Also, updated OP a bit. I will add more "further reading" links as I come across them/remember them. :D
[Legend Android Development] rajasyaitan:
Or if you want to revert the kernel back just do an advance restore of system and boot img.
[Legend Android Development] TheGrammarFreak:
Which is precisely what I said to do in my guide... Try re-reading it...

I don't backup for every new kernel (I very rarely backup using nandroid actually) but what I've written here is by far the easiest thing to use for newbies.
[Legend Android Development] Kwen:
Faster way to get into recovery: Vol Down & Power and select recovery

As opposed to Back & power, bootloader, recovery.

Thanks for the fake flash tip lol, didnt know you could do that :eek:

Though you had to use the batch file route...
[Legend Android Development] TheGrammarFreak:
Thanks for the tip, I'll update the OP when I'm home.
[Legend Android Development] rajasyaitan:
Sorry, didn't see that you've updated the OP. Wanted to add something useful. Lol. :)
[Legend Android Development] TheGrammarFreak:
Aww... Well, next time I make a guide I'll leave something for you to point out to me. Ok?
[Legend Android Development] rajasyaitan:
Haha. That is awfully nice of you. It's a deal then.
[Legend Android Development] TheGrammarFreak:
I've updated the OP with more links, I'll add the quicker way to get to recovery in a mo (done).

@rajasyaitan, you can provide me with some helpful links if you like... Lol
[Legend Android Development] BlaY0:
Well, you should at least add http://www.google.com as it is realy good source of overclocking information :D
[Legend Android Development] TheGrammarFreak:
Done and done. :D
[Legend Android Development] maxq1:
er..i think the latest OC kernels from dumfuq doesn't anymore require setcpu for the OC to work, at least in my case. (or is it just me? :confused:) just a minor input though. cheers!
[Legend Android Development] TheGrammarFreak:
They've never needed setCPU. It's always been an optional thing to gain more control. For his first releases he recommended not using setCPU. Have fun overclocking!

Swyped from my HTC Legend
[Legend Android Development] maxq1:
to quote you again: "BOOM!". all along i was under the impression that setcpu was required for older releases. now i know! thanks, man!
[Legend Android Development] TheGrammarFreak:
No worries, only happy to help.

Swyped from my HTC Legend
[Legend Android Development] greenolive:
undervoltage?

Do these kernels have support for undervoltage?

My device tends to run fairly hot and lowering the

processors voltage might just fix that for me.
[Legend Android Development] TheGrammarFreak:
Hmm. I think lower frequencies undervolt it anyway. So use setCPU to throttle the speed. Having said that my phone runs quite warm when I use it lots, and it always has. Even before I rooted and overclocked. It's just a problem with a metal body... I hope this helps...

Swyped from my HTC Legend
[Legend Android Development] greenolive:
Sure it helps! I'll just stop thinking about the temperature. I've set a profile up to underclock the hell out of the phone when reaching critical temperature so it should be fine. If any solid undervoltage options do turn up on these kernels though, please feel free to add info on your sticky. It would be nice to be able to undervolt but keeping the same frequency! Of course, for battery-life perservation
[Legend Android Development] fatthumb:
Shame on my Legend, can't even get past 768 MHz... And I was hoping for at least 800 MHz =.= Any poor soul out there like me?
[Legend Android Development] TheGrammarFreak:
Me... I'm stuck on 787..

Swyped from my HTC Legend
[Legend Android Development] rajasyaitan:
We're on the same boat.
[Legend Android Development] fatthumb:
You are not, at least you can pass 768 :mad: :D

My dear friend, I welcome thee, haaa :o :p
[Legend Android Development] TheGrammarFreak:
I suppose. I'd rather go to 864 though. It kinda bugs me to know that my friends, who haven't rooted and never will, might have legends that can OC properly.

Swyped from my HTC Legend
[Legend Android Development] greenolive:
I truly am really sorry to say that me, my dumb self and that weird guy in the corner with ease can reach 806. It seemed stable at least. No problems booting, no rebooting and I played angry birds for about 15 minutes without any hiccups. Tough my, my dumb self and that weird guy in the corner feels safer going down to 678 for daily use.

Strange how this can differ this much. Perhaps it's batch-specific.

My phone and I are both in Sweden so maybe the cold weather helps :)
[Legend Android Development] fatthumb:
I can understand what you mean. Some people are happy with a smartphone that just works, and don't bother to try maximise the potential of their device. I have 2 colleagues who are like that, I'm thinking to swap my Legend with theirs to try out, haha.

CM6.1 Nightly build 25
[Legend Android Development] Caifan09:
well guys im sitting so confortably at 806 mhz.....cheerss
[Legend Android Development] fatthumb:
Hi GrammarFreak,

I suppose with v4.0 now we can go lower than 768 MHz (i.e. 710, 729, 748)? Probably will be useful for people like me who live in the tropic and have a lousy CPU :o Do you think it will works like that:confused:

I still need to do my part on the reading though :)
[Legend Android Development] TheGrammarFreak:
A very good set of questions my friend. v3.5 works absolutely fine and is easier to set up, so I'd stick with that one. And no, you couldn;t go lower than 768. You could make a request in the OC thread. :p

The way the OC works:

There's a base clock speed on all CPUs, and in our case it's 19200KHz, so all OCs (when measure in KHz) need to be divisible by that number. I'm sure you already know this though. If you want to go lower than 768MHz then you'll need to find a frequency that is divisible by 19.2MHz There might be one, but none of the numbers you suggested work. Sorry.

So, the v4.0 kernel won't allow what you're asking, but dumfuq might put that in his kernels if you ask nicely. :D You could get 748.8, 729.6, 710.4 (the fact these numbers are so close suggests to me that you know what you're talking about, but I'll put 'em here anyway.) or 691.2.
[Legend Android Development] fatthumb:
Yes regarding the frequency actually I had some knowledge from overclocking good old Celeron 300 MHz by increasing the multiplier. Too bad for me, this things (kernel, etc) are out of my league (hence I need further reading).

I did some spreadsheet with 19200 as starting "FSB" and multiply it with increment of 1 from 15 to 45. I found out that those frequencies that dumfuq included in v3.5 are actually quite similar (i.e. 768000 - 672000, 825600 - 729600, etc). It kinda bugs me if 768 and 825 MHz could works why 672 and 729 MHz can't?

I'm not very good with words so forgive my new-b explanation :o What do you think?
[Legend Android Development] TheGrammarFreak:
I don't see a reason why it can't (in future kernels), but I may be very wrong. I'm no expert on overclocking, I just bothered to write a guide. :D From what I know those frequencies could be made to work, but you'll need to ask dumfuq to make a kernel that allows those frequencies. The kernel essentially says: "Right then CPU, you're allowed these frequency steppings: lots of numbers here" V4 doesn't include the frequencies you want, but dumfuq might make one that does.
[Legend Android Development] BlaY0:
Have you read this post?
[Legend Android Development] fatthumb:
Hmm, if you look at dumfuq's thread some ppl actually tried higher frequencies than those originally included in v4 (>864 MHz). Maybe I'll try to ask those guys :D

Thanks for the help! Maybe you can include some more details for v4 in your guide here for ppl like me :p

edit: to Blay0.. I'm reading it now. Thanks for the link :)
[Legend Android Development] BlaY0:
Hey Grammar,

I have just read your HOWTO and have come to "boot loop". Is it really boot loop or just framework restarting? Would you care to test this one? Because if it is just framework restarting, then there's no need to take the battery out. Lemme know if you're up for some testing...
[Legend Android Development] TheGrammarFreak:
I'll install a high frequency kernel and 'ave a look-see. :D

EDIT, no I won't. I has V4, I'll change 00banner again. Lol

EDIT 2: Ahh, crap. The thing still boots, then it just freezes. It's most likely to be a framework restart, I'll try again with the 3.5 kernel...

EDIT 3: WTF?! That damn phone still boots. SetCPU tells me that it's running 245/844MHz interactive, then the phone freezes up. Stupid thing

EDIT 4: I can't make my phone "bootloop" Which is odd, it used to do this on anything above 806... I'll try setting the minimum frequency, see what that does. Also, that link you gave is a really interesting read. Cheers. :D

EDIT 5: Yeah, more edits. It won't "bootloop" I have no idea why. I just set it to 844 min, it still booted. It just froze once setCPU got root permissions is all...
[Legend Android Development] BlaY0:
Either way hook it up with your PC and try adb shell. If you can get in, there's no need to take the battery out, just issue adb reboot recovery. It's the same with "boot loop", no need for battery removal... but if you encounter proc freeze or kernel panic, you will have to remove it.

EDIT: There's no need to change init.d script every time you need to change that speed. You are testing right, so you have your gizmo connected to your PC anywayz. So set that top speed to some reasonable value like 768, reboot and then rise that speed via adb. When you get a boot loop set it back to previous value and you're set. But be careful if you are using SetCPU... SetCPU itself does change those values in /sys/devices/system/cpu/cpu0/cpufreq too so it will most probably override your setting the next time it switches from one profile to another.

EDIT 2: While testing it is wise to stop SetCPU or even unistall it for that testing period. You can set all the parameters in /sys/devices/system/cpu/cpu0/cpufreq manually using echo via adb...
[Legend Android Development] TheGrammarFreak:
Ok, cheers for the info there. In terms of this guide, I'll add what you've said about adb reboot recovery, but leave in the battery pull as well (noobs).

On another note, any idea why my phone can suddenly boot at 844 when it couldn't before?

EDIT: Ok, OP updated. I'll add in a bit about the V4 kernel as well, but now I need to do some work.
[Legend Android Development] BlaY0:
What's causing those "boot loops" is actually (I guess) incompatibility in stepping through some frequencies... but if you uninstall SetCPU and set upper and lower speed limit to the same value using performance governor (via init.d), there's really a slight chance of "boot loop".
[Legend Android Development] dumfuq:
including the frequencies between 600 and 768 is actually my next goal. The problem is it is not as simple as just adding them, the steppings need to be adjusted or the phones will freeze/reboot when changing between certain frequencies. this is not trivial (at least for me) but I do plan on working on it when I have time.
[Legend Android Development] BlaY0:
It is not actually a good idea to have so many frequencies being used... that way processor would be too busy stepping through them using too many cycles just for that. Using 3 or 4 tops would be much better but then again U would have to compile like 20 kernels for all tastes.
[Legend Android Development] dumfuq:
Agreed. Personally I just want one between 600 and 768 (like 672) but as it stands I have not gotten it stable with it added.

My goal is to ultimately have 245, 400, 480, 600, ~700, and the higher ones. And yes the reason for all the frequencies in one kernel is so I don't have a bazillion to compile.
[Legend Android Development] TheGrammarFreak:
It's great to hear (read) that you're s working on these things. Cheers dumfuq. :D

Swyped from my HTC Legend
[Legend Android Development] colors:
I have now tried to run the phone with 768 and 787 and since that angry birds hangs now and then. Can´t see any aprovement. Is it just for me? the reason was almost just for angry birds because it´s so laggy. i play it a lot so an important part=)