Didi any of you were lucky with setting up orbot to work under JB rom?
Currently I am on CM10 rom with Semaphore 2.0.6 kernel but although netfilter is supported in both CM10 and Semaphore kernels Orbot did not succeeded in setting up transparency proxying. Advice on kernel or any hint what might be wrong is highly appreciated
Thanks
kingdom_fjr said:
Didi any of you were lucky with setting up orbot to work under JB rom?
Currently I am on CM10 rom with Semaphore 2.0.6 kernel but although netfilter is supported in both CM10 and Semaphore kernels Orbot did not succeeded in setting up transparency proxying. Advice on kernel or any hint what might be wrong is highly appreciated
Click to expand...
Click to collapse
Yeah, something changed in JB. You now have to go into Orbot settings and tick the box for "Use default iptables". You should get transparent proxying then.
groksteady said:
Yeah, something changed in JB. You now have to go into Orbot settings and tick the box for "Use default iptables". You should get transparent proxying then.
Click to expand...
Click to collapse
Perfect!. Thanks for pointing me in right direction. I must have been blind not seeing that.
No sweat. It also doesn't seem like that info was very widely spread. I'd assume we're on a very small minority of Orbot users trying JB.
sent from a telephonic device
Related
Since some of you have bad luck with OC kernels, I decided to build a non-OC kernel but still with a few features..such as UV support (no OC), Voodoo Lagfix and Sound..etc..
Think of this kernel as SP-Voodoo for 2.3.4
This Kernel is an i9000 sourced 2.3.4 kernel for I9000 Gingerbread JVP
This kernel is built off of Xcals Reorient v2.0 and is only tested on JVP!
As always, flash at your own risk, im not responsible for any damages!
Get support at #suckerpunch
Latest sources can be found on Github
Remember, I cant fix stupid or lazy. Please read the whole OP and the first and last 5 pages of this thead!
Custom Boot Animations
The bootanimation.zip needs to be /system/media/sanim.zip <- notice the name change
To install:
Flash .tar with Odin/Heimdall
If using Odin place tar in PDA slot
Enable/Disable Voodoo Lagfix in CWM->Voodoo
Delete Voltage Control settings in CWM->Advanced
Kernel Features
Voodoo Lagfix
Voodoo Sound v9
339MB RAM
BLN support
Uses Gamma 2.2
Speedmod Color Fix
Ondemand Governor
Smartass/Interactive Governor
Custom CWM3 (from Talon)
Wired Headset Support
Audio Dock Support
Battery Polling set to 60s
Set Light Sensor Polling to 1s
Security Fixes from FuguMod Kernel
Updated to latest Samsung source
Fixed KTLO with new Samsung source
UV support up to 1ghz (no OC)
Full list of changes found HERE
JVP-Voodoo-1.0.0.tar MD5: d7d9b4b025cc25a096fe41956fa0e000
JVP-Voodoo-2.0.0.tar MD5: 7b72d5f84cfeeb43d0411057f4f2c136
2.0.0
-add smartass governor
-add interactive governor
1.0.0
-initial release
NOTE
This kernel will remain closer to Samsung source and not as extreme as Talon.. This is for those of you who want a semi-modded stock kernel.
To check frequency time used, use Storm717's app HERE
Thanks to Hardcore, Ytt3r, Xcal, Supercurio, Chainfire, Raspdeep, sztupy, DG, Laststufo, Kodos96, zacharias.maladroit, Kang and Morfic (if I forgot you, let me know and ill add you)
reserved
10char
first
10 char!
second 10 char
Nice!
Apexifying now
'slacker' was a cool name for it
watsaa said:
'slacker' was a cool name for it
Click to expand...
Click to collapse
Lol..yea i might stick with that name..not sure yet. I didnt want it to come off the wrong way, it was not directed towards anyone but me.. I simply cherry-picked things from what we had already done with Talon, but i might end up using it.. Vivified is working on a boot image, just wanted to get it released, will brand it in the next version
Interesting
pbclst said:
Nice!
Apexifying now
Click to expand...
Click to collapse
Presently running it on Continuum 5.6 for those who might be interested..
Use ODIN - no reboot - clear dalvik,etc to avoid issues
seems to work great.. no BT problems or wifi issues as yet with 5.6
sstarre said:
Presently running it on Continuum 5.6 for those who might be interested..
Use ODIN - no reboot - clear dalvik,etc to avoid issues
seems to work great.. no BT problems or wifi issues as yet with 5.6
Click to expand...
Click to collapse
Yes, this will not have BT issues, and bootanimation works again!
Vivified said:
Yes, this will not have BT issues, and bootanimation works again!
Click to expand...
Click to collapse
This!
Black is a scarey thing sometimes...
Vivified said:
Yes, this will not have BT issues, and bootanimation works again!
Click to expand...
Click to collapse
hmmmm ... interesting sig
Yea it might be black on first boot...Xcal has an explanation on his thread about it, but after first boot bootanimation will work
Also, yea there will be no BT issue with this one, the problem was from Chainfires initramfs...we have also updated Talon to use Voodoo lagfix/initramfs..will be in next version of Talon
sstarre said:
hmmmm ... interesting sig
Click to expand...
Click to collapse
oh that old thing..
existz said:
Yea it might be black on first boot...Xcal has an explanation on his thread about it, but after first boot bootanimation will work
Also, yea there will be no BT issue with this one, the problem was from Chainfires initramfs...we have also updated Talon to use Voodoo lagfix/initramfs..will be in next version of Talon
Click to expand...
Click to collapse
existz..does that mean we should not use chainfire's CWM manger? It seemed a little wonky when I tried to use it to start a CWM backup...
existz said:
Yea it might be black on first boot...Xcal has an explanation on his thread about it, but after first boot bootanimation will work
Also, yea there will be no BT issue with this one, the problem was from Chainfires initramfs...we have also updated Talon to use Voodoo lagfix/initramfs..will be in next version of Talon
Click to expand...
Click to collapse
Looking forward to the next Talon.. soon I hope
sstarre said:
existz..does that mean we should not use chainfire's CWM manger? It seemed a little wonky when I tried to use it to start a CWM backup...
Click to expand...
Click to collapse
Ah thats up to you...i usually just do a backup from inside CWM manually..but thats just me
existz said:
Ah thats up to you...i usually just do a backup from inside CWM manually..but thats just me
Click to expand...
Click to collapse
Yeah, that's what I did...
BTW - XDA PM'd you last night...
Thanks again for this...
existz said:
Yea it might be black on first boot...Xcal has an explanation on his thread about it, but after first boot bootanimation will work
Also, yea there will be no BT issue with this one, the problem was from Chainfires initramfs...we have also updated Talon to use Voodoo lagfix/initramfs..will be in next version of Talon
Click to expand...
Click to collapse
Talon will rock next apex update then. cant wait to get talon back
watsaa said:
Talon will rock next apex update then. cant wait to get talon back
Click to expand...
Click to collapse
JVP-Voodoo 1.0.0 is SUPER STABLE AND SMOOTH!
My nexus 7 is rebooting after a while using trinity kernel. I'm in stock 4.2.1 and I had random reboots even when no it applying any kind of OC just the kernel's default settings! What can I do to prevent that from happening?
Flash a different kernel.
Not all tablets are created equal. Whereas one will play nice with a particular kernel, the very next one off the assembly line may not.
najaboy said:
Flash a different kernel.
Not all tablets are created equal. Whereas one will play nice with a particular kernel, the very next one off the assembly line may not.
Click to expand...
Click to collapse
I flashed motley kernel without any oc and I still get random reboots. Should I go back to stock kernel?
jeff.murillo said:
I flashed motley kernel without any oc and I still get random reboots. Should I go back to stock kernel?
Click to expand...
Click to collapse
i bet its an app causing it.
Don't know why I initially glanced over you being on 4.2.1. Random reboots are actually a known issue with 4.2.x due to a problem at the OS level. Essentially, anything that uses geolocation can inadvertently trigger a reboot. Apps such as HD Widgets have updated to use a workaround until Google themselves fixes the issue. In the meantime, the only certain way to avoid the reboots is to turn off location services or downgrade to 4.1.2.
Unfortunately, this bug isn't consistently reproducible, but it does affect the entire Nexus line of devices using 4.2 and 4.2.1.
najaboy said:
Don't know why I initially glanced over you being on 4.2.1. Random reboots are actually a known issue with 4.2.x due to a problem at the OS level. Essentially, anything that uses geolocation can inadvertently trigger a reboot. Apps such as HD Widgets have updated to use a workaround until Google themselves fixes the issue. In the meantime, the only certain way to avoid the reboots is to turn off location services or downgrade to 4.1.2.
Unfortunately, this bug isn't consistently reproducible, but it does affect the entire Nexus line of devices using 4.2 and 4.2.1.
Click to expand...
Click to collapse
Thanks buddy, with motley kernel I've just had 1 reboot. I'm going to test turning location services off and see what happens. BTW any idea how to oc the GPU in motley kernel? in trickster mod there's no option for it.
jeff.murillo said:
Thanks buddy, with motley kernel I've just had 1 reboot. I'm going to test turning location services off and see what happens. BTW any idea how to oc the GPU in motley kernel? in trickster mod there's no option for it.
Click to expand...
Click to collapse
is ocing the gpu enabled in motley kernel? it has to be a feature of the kernel to be able to do it, an app cant do it if the kernel doesnt include the mod.
simms22 said:
is ocing the gpu enabled in motley kernel? it has to be a feature of the kernel to be able to do it, an app cant do it if the kernel doesnt include the mod.
Click to expand...
Click to collapse
According to the kernels features, it supports GPU oc
jeff.murillo said:
According to the kernels features, it supports GPU oc
Click to expand...
Click to collapse
the kernel might use a different method than the one the app "knows". for an example, cm color control with trinity kernel on the gnex. both cm and trinity have color control enabled, but since cm uses a different method of color control, you cant use the native cm rom color control option with trinity kernel, nor can you use the trinity kernel toolbox to control color on a cm rom/kernel. as they say, theres more than one way to skin a cat.
simms22 said:
the kernel might use a different method than the one the app "knows". for an example, cm color control with trinity kernel on the gnex. both cm and trinity have color control enabled, but since cm uses a different method of color control, you cant use the native cm rom color control option with trinity kernel, nor can you use the trinity kernel toolbox to control color on a cm rom/kernel. as they say, theres more than one way to skin a cat.
Click to expand...
Click to collapse
That's what I thought, any idea how to do it in motley kernel?
jeff.murillo said:
That's what I thought, any idea how to do it in motley kernel?
Click to expand...
Click to collapse
honestly i dont, id assume that motley used francos method since thats the most popular way. you should probably ask in the motley thread. but for some reason, i dont think it does, not the 4.2.1 kernel at least. maybe he just didnt update his op to reflext this. ask in the thread anyways
Does any one know how to remove this?
Thanks for looking
Sent from my GT-P3113 using XDA Premium HD app
custom ROMs are the only way, AOKP and CM have a setting in sound that you uncheck, it's something like safe volume limit or something.
If you need to maintain a mostly stock ROM (in that all hardware works) you can try stock based ROMs like Romswell 4.0.4 (he seams to have removed it) or try a JB stock based and see if its gone.
daniel644 said:
custom ROMs are the only way, AOKP and CM have a setting in sound that you uncheck, it's something like safe volume limit or something.
If you need to maintain a mostly stock ROM (in that all hardware works) you can try stock based ROMs like Romswell 4.0.4 (he seams to have removed it) or try a JB stock based and see if its gone.
Click to expand...
Click to collapse
What about PA 3.60 and Franco Kernel?
Thanks
rohitrajan2012 said:
What about PA 3.60 and Franco Kernel?
Thanks
Click to expand...
Click to collapse
Well PA is similar to AOKP and CM so it may have the same setting, you'll just have to look for it.
Hi everyone.
Currently I've flashed franco.Kernel M1 on my Nexus 4. I love this kernel except for its modified color settings. I prefer the original color settings from the stock kernel and may I ask how can I get "exactly" the same color settings from the stock kernel in franco kernel? Thanks!
Agnes.m said:
Hi everyone.
Currently I've flashed franco.Kernel M1 on my Nexus 4. I love this kernel except for its modified color settings. I prefer the original color settings from the stock kernel and may I ask how can I get "exactly" the same color settings from the stock kernel in franco kernel? Thanks!
Click to expand...
Click to collapse
Erm unless you clicked on recommended values then it will be the stock colours. If you clicked on recommended settings then you will also be able to find set kernel defaults which is somewhere there.
Rizy7 said:
Erm unless you clicked on recommended values then it will be the stock colours. If you clicked on recommended settings then you will also be able to find set kernel defaults which is somewhere there.
Click to expand...
Click to collapse
But I think the kernel default from franco kernel is not the same with that of the stock kernel. The color setting seems to have been modified since certain nightly(r70?). Anyway thanks for your help!
Your right afaik, Franco uses LG presets for default.
Can't help with the settings though, Franco has changed it too many times for me to keep up, and I think some of the needed settings are unexposed.
meangreenie said:
Your right afaik, Franco uses LG presets for default.
Can't help with the settings though, Franco has changed it too many times for me to keep up, and I think some of the needed settings are unexposed.
Click to expand...
Click to collapse
Oh it has disheartened me a bit. Anyway thanks a lot!
Agnes.m said:
Oh it has disheartened me a bit. Anyway thanks a lot!
Click to expand...
Click to collapse
Just download trickster mod and set the colours to default. You will most probably not notice any difference because like I said when you flash franco the colours are still the stock ones.
Rizy7 said:
Just download trickster mod and set the colours to default. You will most probably not notice any difference because like I said when you flash franco the colours are still the stock ones.
Click to expand...
Click to collapse
As has already been pointed out above, Franco kernel does *not* use the same colours as the stock kernel.
steviewevie said:
As has already been pointed out above, Franco kernel does *not* use the same colours as the stock kernel.
Click to expand...
Click to collapse
Yh sorry your right.. Im pretty sure he can still use trickster as they have the google presets as well as the pa ones
I have PA 3.99 4.3 jellybean.
zertix said:
I have PA 3.99 4.3 jellybean.
Click to expand...
Click to collapse
Flash a kernel that supports overclocking.
Use a kernel that supports overclocking, such as Faux kernel, Trinity, Neo and etc. After flashing the kernel, use an app to change the frequencies and such. I use tricksters mod + Trinity kernel. Hope this helped
Ok perfect. Anybody can pass me the right kernel for my rom ?
zertix said:
Ok perfect. Anybody can pass me the right kernel for my rom ?
Click to expand...
Click to collapse
there is no right kernel, thats for you to decide. every device will react differently, and you will use your device completely differently than anybody else, so only you will have the right answer. try them all