Howdy Y’all!

Thanks for choosing the Overcome Experience! This document is an attempt to guide you through the basics of
the Overcome ROM & Kernel. I’ve decided to separate this guide from the installation guide, as it was becoming
too unwieldy and important information were being pushed way too far down to be noticed. One of the aims of this
guide is to provide the latest information with regards to the many possible issues, and to act as into one
comprehensive trouble-shooting guide as well (as you know how it is, when searching for the solution to the
possible issues you might face, where the information could be located in one particular post in this massive 300+
page thread.)

My disclaimer: Refer to the above – NEITHER DO I! ;-)

Copyright Notice: Copyright? What copyright? If you feel my rubbish is worth stealing, please go ahead, no
attribution necessary. (Saw this somewhere and I agreed with this so much, I had to put it here! ;-)

Urgent notes:

 None for the moment... just remember to install the GPS fix yeah? Yeah, the one on Page 2! A
reminder by alterbridge86: This fix should be applied each time you flash a new version of the ROM!
IT STILL APPLIES ON GINGERBREAD TOO!!!

- thepittbull (12 May 2011)

OK… here are a couple of strongly suggested tweaks that you should really do:

1) For Your GPS To Work Well (The LbsTestMode aka AngryGPS fix!):
a. Make sure your GPS is on.
b. Fire up your phone app and enter this dialer code: *#*#3214789650#*#* and you should get this:

(If you don't get this... clear the data from AngryGPS (Settings -> Applications -> Manage
Applications. Thanks kashortiexda!)

c. Click on "Settings" and you should get this:

d. Now click on "General Settings" and match the following settings below:
 e. Hit the back button, and now click on the "SUPL Settings" and match the following settings:

f. Now hit the back button twice, and you should be in the main AngryGPS page (picture under Item
2)... Now click on the "Delete GPS Data" button.
g. That's it! You can use the "TTFF Test" (TTFF = Time To First Fix!) and "Tracking Test" to test your
GPS too. I also use GPS Status app from the market to test as well.
h. Remember however, the first cold fix after flashing a new ROM WILL take a longer amount of time.
Subsequent locks will be lightning quick however 

2) Enabling Full Screen Hack For Applications:

a. Go to Market from your galaxy tab and search for “Spare Part”.
b. Start it and scroll down till you find “Compatibility Mode” option, it must be ticked already, un-tick it
then tick it again. Reboot your Samsung Galaxy Tab.
c. Now start “Spare Part” again, now remove the “Compatibility Mode” option and reboot again. You
are all set.
d. Now fire up any application that was previously not running in full screen, it will now run in full
screen, now enjoy all your games and applications in full screen on your Galaxy Tab.
Why the hell are you asking us to restock?
OK, this has always been a contentious issue, and one that will never please everyone, but we’ve decided to make
it a mandatory process for everyone to restock according to the installation guide. Now why for the love of God,
you may ask, could there be a rationale for such a drastic mandate?

Well, as you’ll note, with the new Overcome 2.x ROMs, we’re basically shifting over to the Gingerbread (Android
2.3.x) version, and with that, there’s bound to be loads of bugs to squash. It’s going to be a headlong rush to test
out all the various inevitable “Help” requests and posts… and as such, this is a much needed step, as it’ll help
eliminate all the huge potential issues that could happen by installing it the non-mandatory way. I’m sure you want
alterbridge to focus on tweaking and polishing the Gingerbread-based ROM and kernels, more than wasting time
supporting issues that is bound to happen, when following non-standard procedures as well. It’ll also help in cutting
down testing durations, as it’ll allow us to test via one standard installation configuration, which will also allow for
the new ROMs and kernels to reach your good hands in a more timely manner too. As such, it’s imperative from
now on, that when posting to the thread, that you make sure that YOU’VE INSTALLED IT ACCORDING TO THE
GUIDE beforehand, as a harder stance will be taken when we’ve found out the installation of the ROMs weren’t
according to the guide, or short-cuts were taken.
Battery Recalibration and Reconditioning...
One of the most frequently asked questions we’ve received at the original
Overcome ROM thread deals with the topic of battery life. Before I
expand futher, do take a look at the steps in the big red box on the right.
OK now those are the basic steps to take.

So, some of you may say, that, despite doing all of that, the battery life
still suck, even after you’ve wiped the stats. Here’s the deal and one of
the things people don't realize, (and I didn’t do a better job in the previous
Tips & Tweaks guide explaining this!) is that a battery wipe by itself
would not immediately "improve" your battery life. IN FACT, during
the first charge cycle after a battery wipe, you might notice a slightly
less than optimal battery-life! This is because, the stats have to be
rebuilt, which is why after a couple of FULL charge cycles after the
battery wipe, when the stats are properly "repopulated", which is when
you'll see the difference.

That being said, there could be a lot of factors that come into play when it
comes to battery life, especially on the Overcome ROM. Obvious things
like overclocking (especially without under-volting) and display brightness
(don't forget, we've got quite a big LCD screen to power - and the display
would always be one of the biggest power drainers of them all) comes to
play.

There's also the not-so-obvious factors, and like you say, they could
include the apps you use, whether you've calibrated the battery, and the
services that you use, and the battery counter too, as they all come into
play as well. Whenever alterbridge prepares a new ROM for release, one
of the things we'd test against would be battery consumption, and I'm one
of those that are watches the battery counter like a hawk too for any signs
of possible battery drains.

We can only conduct the tests against a control environment and the
apps that you’ve installed would also impact battery life too! The team
recently helped a member that has shown a marked decline in battery-life.
So much so, if you were to plot the battery consumption, the graph would look like a straight line decline, EVEN in
idle. So, after investigating his usage patterns, we saw an obvious trend - he's been installing apps like a Vicodin
junkie popping the pills, with some apps he doesn't even use or even know what they're for - but more for the "just
in case" or "Oooo... sounds nice..." factor. After working with him though a clean restock, and app-by-app
installation and monitoring, he saw it for himself where the drain was coming from... Errant apps that were sucking
down juice like nobody's business in the background. The battery info tool within the settings just ain't good enough
to really see this. And then, there's also the placebo effect of the Battery Counter in the notification bar - when in
stock, where the battery was represented in just one solid icon with less information, you tend not to see the same
battery "drain" there, as there's no detailed information to really "fool" you into thinking otherwise.
Anyway, I've done a few experiments, in the past, with as controlled an environment as I possibly could achieve,
with both the stock ROMs, some other custom ROMs, with the same set of 292 apps (each tested so that I know
their battery consumption patterns) that I normally installed (all re-installed via Titanium, all with battery wipes and
a couple of charge cycles to ensure full optimizations) and discounting for changes in usage patterns -- I've come
to the conclusion that yes, the Overcome ROM doesn't have the best battery life amongst the ROM, BUT, it's still
one of the better ones (it comes within 95% of the battery life profile of the "what-we-can-call-ancient-by-now-with-
hopefully-no-disrespect-implied" MoDaCo Custom ROM R1. All of this was done at default, without overclocking or
undervolting. So, with the trade-off of the optimizations that alterbridge had done with the Overcome ROM, that's
5% I can live without. In fact, with moderate under-volting at the 1Ghz clock-speed, I was able to achieve the same
battery life profile as the vaunted MoDaCo ROM.

Granted, this is with the older 1.4.x and 1.6.x ROMs, as the new 2.0 base is still too new for me to form a thorough
opinion, especially with reports of a drain in the Gingerbread implementation on the I9000 devices, so it’s early
days yet – however the lessons learned above would still apply. As such, here’s again what I’d suggert: do the
battery wipe when you’ve charged it to 100%. Let it do a couple of full-cycle charges (100% -> empty -> full charge
constituting 1 full cycle, again… with best results being uninterrupted power rundowns and charges) and monitor
your apps.
 FOR NOW: OVERCOME 2.0.0 BETAS ROMS/KERNEL DO NOT SUPPORT
OVERCLOCKING!
Basic Over-clockin’ & Under-Voltin’…
Ah... here’s where the fun begins. One of the coolest thing about installing
and running a custom ROM is the ability to Over-Clock (OC) your device’s
CPU as well as to Under-Volt (UV) the amount of juice feeding the CPU!
Depending on the various configurations and scenario available, you can
either turn your Overcome-infused Galaxy Tab into running like a steroids-
addled raging bull running on full throttle high on the CPU cycles you’re
able to feed it or a battery-friendly smoothie that sips battery juice with a
pinkie turned up like a nun with Mother Superior casting a watchful eye on
her!

However, for most people, and depending on use, the key is to finding a
wonderful balance in between – where you get the exceptional smoothness
of a well-oiled CPU with great power savings that UV provides. So without
further ado, here’s some of the OC/UV tips that’ll get you on the way...

AN IMPORTANT NOTE: One of most frequently asked questions about

over-clocking and under-volting: Is there a fixed/recommended setting to
this complicated looking over-clocking/under-volting thingie?

The answer would be NO! This is because the correct answer would be
“Your Mileage Might Vary...” or YMMV. Why is this so? While at the
surface, all CPUs might look the same, thanks to the hocus-pocus, black
magic-infused, arcane runes-a-chanting process of engineering and
manufacturing the piece of silicone, metal and whatever crap they use to
build the Hummingbird CPU that powers the Galaxy Tab, there’s no two
exact pieces of silicone, metal and whatever crap that forms the CPU at the
molecular level. As such, some CPU can take a lickin’ while some have a
glass-chin so fragile that they fold at the mere whisper of a feather stroking
them. It’s the luck of the draw when you get your Tab. Unfair? Yup...Wanna
cry over it? Well, as they used to say in the playgrounds when I was a kid:

“Awww... Boo FREAKIN’ hoo... too bad, so sad!” ;-)

However, it’s not to say that the differences are entirely as apparent as the
paragraph above suggests, but again, do note the idea behind it. Most Tabs
should be able to over-clock to 1.2Ghz and some remain relatively stable at
1.4Ghz. Again, your mileage might vary and depending on the CPU you’ve
got, how far you can push it really does depends on how well it was
constructed. As for my unit, I’ve been able to push it at 1.4Ghz for a couple
of days running without any issue – though I’m not one to really over-clock my
CPUs much. In fact, I tend to under-clock my CPU to 800Mhz. Why? Answers here! & here! As to under-volting,
again, the vagaries and eccentricities of each individual CPU comes into play too. Some can easily handle a -
200mV across the board at all clock settings, while some would freeze up even at the slightest withholding of their
jamba juice.

Please note however, that it’s not as bad as it seems and the key thing for you to do is to experiment. Choose a
setting, for example in under-clocking with -200mV across the board and let it run for a day or two as how you’d
normally do it. Use the “Apply for now” option (which will allow the settings to hold until your next reboot) and see
how it goes. If it freezes up, or refuses to wake up after being on standby for a while, just hold down the power
button till it powers down and reboots, and you’re back to the standard settings – no harm done. Dial down the
under-clock a bit and let it run again for a day or two again. Once you’ve found the perfect settings that your Tab
can handle, then choose the “Save as boot settings” and you’re all set. See, it’s not that scary right? Worst come
to worst, it’s just a momentary freeze/lock-up that’s easily remedied with a reboot... no harm, no foul! In return,
what do you get? A better battery life with under-clocking – which is great for “Battery Wh*res™” like me! ;-) It’s the
same with your over-clocking settings as well. Bump your CPU clock speed up (or down) according to your liking,
needs or whatever that rocks your boat and experiment to see which clock level is stable, and suitable for your
needs.

So, with that long-winded preamble out of the way, let’s see how you’re going to get about to under-clocking and
over-clocking, shall we?

First and foremost get the Voltage Control application apk from the following link:
http://www.mediafire.com/?m2ybg2v4oqdtknn

 Install it and allow it to have root access/permission. You

should get a screen like the one on the right, if you’re
running Overcome ROM 1.4.5 with the Overcome Kernel
2.1.4, which has the Simple I/O Scheduler set as default.
 Here’s the basics now:
o The “Scheduler:” drop down menu allows you to
select a scheduler of your choice. The scheduler
basically is the method that governs the I/O
(input/output) queue. I’d suggest you leave it at the
default settings, or sio if you’re running Overcome
Kernel 2.1.4.
o The “Limit clock to:” drop down menu allows you
to choose the upper limit that the CPU runs at.
This is where you can do basic over-clocking
of your Tab’s CPU. So, if you’ve set it at 1,200
Mhz, basically, the Tab will scale up to 1.2Ghz
whenever it’s running at full steam. Again, please
take note that when you’re over-clocking the CPU,
either by Voltage Control or SetCPU or any other
app, it doesn’t mean that your CPU’s going to be
running at full-bore at the upper limits all the time
(unless you’ve specifically set it that way, of
course...) These mobile CPUs are meant to scale
 up and down according to the various stepping levels at the
various load levels your Tab is experiencing – if not, your
batteries would be running flat very fast! As mentioned, I run
my CPU at 800Mhz normally, and scale it up, when I need to
do a lot of processing, like doing a full Titanium Backup, etc.
With the Tab running the Overcome Kernel 2.1.4, and the
CPU clocked at 800Mhz, I can do intensive game like Angry
Birds, Nova or Cordy, etc running quite smoothly, with nary a
hiccup. So, tweak this settings according to your needs. As
ever, remember, YMMV!
o Now below those two drop down menus, you’ll have a list of
eight (8) CPU clock-speed stepping, from which you can
individually set the amount of volt juice the Tab supplies
when the CPU is running at that level. When you select each
stepping, it’ll drop down to present you with a slider, like the
one on the right. You’ll slide it left or right, with each step to
the left representing a -25mV cut in power supplied to the
CPU at that particular stepping. It goes from -0mV all the way
to the right, to -200mV all the way to the left. Repeat for each
stepping till you get the combination of your choice for each
individual clock speed stepping.

As mentioned, on my Tab, I can run -200mV across the board without much stability problems.
Some people would prefer a more conservative power-cut at the lower end of the spectrum. Again,
it’s up to you to experiment with the settings of your choice that’ll allow you to have the best balance
of power/battery life without sacrificing stability.
o Once you’ve tweaked the necessary under-volting/over-clocking combination of your choice... say, -
200mV across the board, with a CPU clock speed limited to
1,200Mhz, you can now test it out. Just hit the “Menu” button
and select the “Apply for now” option. This will allow you to
give your Voltage Control settings a test run. By using the
“Apply for now” option, it’ll run these setting on a temporary
basis and the settings will be reverted to default settings
once you reboot. This will allow you to regain back your Tab
at default setting should anything go wrong or it freezes – so
don’t complain, it’s a safety/backup feature, not a flaw! Run it
for say 1-2 days, and if your Tab runs smoothly, fire it up
again, hit the “Menu” button and select the “Save as boot
settings” option. Saving as boot settings, save the settings
you’ve chosen to be the default setup, so that you don’t have
to re-tweak this each time you reboot.
o I’ll mentioned what I wrote earlier, if your Tab freezes up, or
refuses to wake up after being on standby for a while, just
hold down the power button till it powers down and reboots,
and you’re back to the standard settings – no harm done.
 *******************************************************************************************************************

One more thing about over-clocking: Just remember to keep your eye out on the temperature levels
like the battery temperature as well when you’re over-clocking! Make sure it doesn’t spike too high too,
or you might end up damaging some components as well, like the SIM card (I’m not sure if this is
possible, or how much of this is true, but we all know heat kills electronics, don’t we? It does shorten
battery life as in the physical life span of the battery – that much I’m sure...) According to the user
Darkwoof, the telco rep that he spoke to mentioned something like this: “When I called my telco today
and explained the issue (without mentioning the battery temp), he asked me if the device I was using
at the moment of failure felt hotter than usual. He then went on to explain that SIM cards tend to fail in
the midst of using devices when the components nearby gets beyond a certain temperature. I am then
advised that I will need to replace the SIM card.” So, keep an eye out, yeah?

*******************************************************************************************************************

Now let’s take a look at the SetCPU application. There’s various ways where you can get the apk, so I won’t bother
discussing that part here. Anyway, SetCPU allows you to have a finer-grained control over your over-clocking
settings, like setting the lower limit where the CPU runs at, choosing the CPU governor of your choice, different
over-clocking profiles to suit different settings and scenarios, (like running a lower clock-speed when your
temperature is running a bit high, lowering your CPU’s upper threshold when your screen is off, etc.)

I’ll mention my opinion of it here. For my daily needs, I’m just happy to leave it to Voltage Control for all my over-
clocking needs, as I’m quite happy with the lower CPU threshold being at 100Mhz, I don’t need to set different
profiles for different scenarios, etc, and there’s always the fact that, without the need for such fine-grained control
of the over-clocking process, installing the SetCPU, is just going waste CPU cycles, RAM space and storage space
too. So I just don’t install it. But it doesn’t mean that SetCPU is bad or anything, in fact it’s a great application,
should you have a need for it. I just don’t use it on the Tab. I use it on my HTC Hero all the time though, and I’ve
been using it there for almost a couple of years on the Hero now. So, it’s entirely up to you... again, YMMV!

So, take a gander over to the XDA boards to look up SetCPU and its various potential setting, alright?

Cheers for now... if you’ve got any opinions, criticism (good or bad) about the guide or anything you feel should be
included, please look me up and send me a PM. Please, though, do NOT send me specific questions about the
ROM or your individual issues on PM, as I get tons of PMs a day, as well as the fact that I feel that by posting your
issues on the board itself, and having people answer it, it might help others as well. And if you liked these guides
I’ve written or any help I’ve rendered, just hit the Thanks button on any of my post... Thanks yeah?

- thepittbull -