[Android Software/Hacking General [Developers Only]] zeppelinrox:
I honestly know anything about rooting phones apart from milestone and the atrix since I hacked a friend's atrix :p

Yep... I intend on making it into an app... family doesn't think the name SuperCharger is a good name for it :p

Well it's been a long day and to keep it simple:

Just unsupercharge and wipe caches and reboot.

SuperCharge with RC3.2 and reboot... let's see what happens :p

Why are you using an older beta? Try with RC3.2

Did you try experimental 2 (with null values) and it still didn't work?

Did you do any other tweaks or only the 3g?

I had a huge problem with my friend's atrix (cm7) with data not working after applying everything.

At first I thought it was supercharging or 3g but uninstalling those still didn't fix it.

Finally uninstalling the kernelizer fixed it.

BUT previously, it would still connect with the kernelizer but no supercharger.

It made no sense apart from one thing: the rom/kernel just doesn't like the init.d boot scripts.

I can leave it supercharged and kernelized and 3g'ed and data will connect no problem - but only if I delete the init.d scripts and have script manager run the 99supercharger.sh and 98kickasskernel.sh from the data folder :p

I figure something was prevented from initializing on boot and so the APN's weren't being registered and therefore no data.

It could be that the same can be happeing regarding the wifi.. something isn't being initalized.

If I run the OOM Stick, I can see a process called wpa_supplicant running... check on your device to verify that it is running.

As far as setprop goes: once ro.ril* settings (which are used for 3g turbocharger) are appied, they cannot be changed after boot so that wouldn't work.

That's why I needed to put the entries at the top of build.prop... any ro.ril* setting that comes afterward don't get applied.

Yep just run it, pick an option, and reboot.

Did you try all the settings and reboot between each change?

No init.d file.

RC1 specifies that the entries are put in build.prop.

I was just about to ask about the actual difference... cool.

Which setting gave you the best results?

The 3g build.prop tweaks aren't really anything new... but I did put a new spin on it.

You can find vaious individual configurations but as far as I know, my script is the only one that lets the user choose more than one configuration.

Options 1 and 2 aren't anything out of the ordinary... they are pretty much typical 3g tweaks. I may have tweaked a couple of values in each one.

Option 3 are maximum values from initial 3g tweaks.

Option 4 are maximum values taking from newer 3g tweaks and personal research.

Option 5 are mximum, perhaps unconfirmed maximum values that aren't very well known.. googling hsxpa=5 or gprsclass=34 won't give many results...

Option 6 is pretty cool came about by accident - nulled values. I made a scripting error on a beta/test and all options applied no values so you had gprsclass= and hsxpa= etc etc... but many users reported great results.

So I figured, in theory, that could make sense too - instead of applying maximum values, apply NO values and let the OS figure it out and without limitation.

So, I pretty much came up with configurations/options 3 to 6 based on research and user results from this thread :D