[Galaxy S II Q&A, Help & Troubleshooting] dezzadk:
Anyone here having success with ORBOT ?

It's a jungle out there trying to find out which ROM launches Orbot fine (I've tried several) and then a kernel with the simple module included loaded by issuing:

"modprobe ipt_owner"

So god damn simple.

Orbot is such a gain on an Android. Firstly, it opens up the opportunity to only route/proxy things such as syncing.

Other than that, it provides it's "Hidden Services", deepweb or what you would like to call it.

And lastly, it opens up Pandora for some users, it opens up ThePirateBay for others, and many other country restrictions.

I'm beginning to think many of the people who make ROMs and compile kernels never actually used a Linux computer, or know who to treat one, if they do at all know what the difference between a module and a built-in one is and what the "performance" gain is from leaving one module (especially ipt_owner) out of the kernel "for performance" ..

Yeah right, Ninphetamine (or other stimulants that fry your head), SpeedMod (or just amphetamine) ..

Well .. Actually, I think sometimes people patch too much just to write a long changelog, having NO god damn clue about new and old lines of code.

People not using Git at first when patching, well, it's up to them, if they can maintain it and make incremental backups.

So recently I tried "Tegrak Kernel 26" and the newest "Lulz Kernel Build 14" .. Very fine kernel !

Guess what ?

1. First clean Reboot (su, reboot)

2. Start 'Tegrak Kernel' app (works fine)

3. Start Orbot (manually) (disabled on boot to debug logcat)

3.5. Orbot is yellow (Not fully connected)

4. Start 'Tegrak Kernel' again .. This time, lost background connection.

5. Orbot magically turns green instantly when I started 'Tegrak Kernel' app ..

"Connected to the Tor Network" notification pops up, and the missing TRAY icon magically appears !

6. But the Orbot app still shows "YELLOW" incomplete

7. "Check connection" in Orbot is success .. Orbot is running, but is it functioning correctly ?

8. NO- Force Close. And what's the gain? A broken 'Tegrak Kernel' background service.

LOGCAT: http://paste.pocoo.org/show/495957/

I'm beginning to think there is no such thing as people developing for stability, for flexibility, and to support functions in the kernel that certain apps REQUIRE! This is more important than the average battery gauge mod or the so important script and cache tweak that increased your devices performance with about 0.0025% ?

Siyah says it's a unified kernel, well what's unified or flexible if it can't do Orbot ? "One Kernel to Rule Them All" - OK- then start supporting more devices, start supporting more features ;)

And what is good about an "optimized" but unified kernel? Doesn't that mean it is compiled for several arch's and devices ?? Then you could just as well throw the ipt_owner module in and catch all orbot users while you're playing one-size-fits-all (Unified) .. Instead, release several builds, optimized for size, or whatever works for you. One with ipt_owner module and one without ..

And apparently, I'm not alone:

http://www.insecuresystem.org/2010/04/ultimate-droid-and-orbot.html