On Tue, Jan 24, 2017, at 07:13 AM, Mark Murphy wrote:
> On Tue, Jan 24, 2017, at 05:41, Hans-Christoph Steiner wrote:
> > Where did STATUS_OK come from, or is that just a typo?
>
> "Typo" implies just a typing error. I think I was having a synapse
> segfault and kept thinking the name was
On Tue, Jan 24, 2017, at 05:41, Hans-Christoph Steiner wrote:
> Where did STATUS_OK come from, or is that just a typo?
"Typo" implies just a typing error. I think I was having a synapse
segfault and kept thinking the name was STATUS_OK instead of STATUS_ON.
My apologies for the confusion.
Also,
Nathan of Guardian:
>
>
> On Mon, Jan 23, 2017, at 10:11 AM, Mark Murphy wrote:
>> On Mon, Jan 23, 2017, at 10:07, Nathan of Guardian wrote:
>>> Otherwise, yeah, waiting a little bit for all the processes to spin up
>>> is not a bad idea.
>>
>> Should Orbot send out STATUS_OK before the
On Mon, Jan 23, 2017, at 10:11 AM, Mark Murphy wrote:
> On Mon, Jan 23, 2017, at 10:07, Nathan of Guardian wrote:
> > Otherwise, yeah, waiting a little bit for all the processes to spin up
> > is not a bad idea.
>
> Should Orbot send out STATUS_OK before the processes are ready? Or,
> should
I have a new update to Orbot coming soon (with arrase's contributions!)
that addresses some long standing issues with Polipo stability.
Otherwise, yeah, waiting a little bit for all the processes to spin up
is not a bad idea.
On Sun, Jan 22, 2017, at 12:42 PM, arrase wrote:
> Polipo is the orbot
On Sun, Jan 22, 2017, at 12:21, arrase wrote:
> i can not find a place at orbot code where the
> app waits for Polipo before broadcast the state
I do not know what Polipo is, sorry.
If Orbot is sending STATUS_OK without being ready to accept connections,
then either I misunderstood what
With the sample apps it works.
I added .withTorValidation() to my source and now onConnectionException is
raised:
01-22 18:06:45.353 7690 7827 W System.err: java.net.ConnectException:
Failed to connect to /127.0.0.1:8118
I think is a race condition, the sample apps starts orbothelper at
On Sun, Jan 22, 2017, at 11:21, arrase wrote:
> How do you deal with the lag between onEnabled callback of OrbotHelper
> and onConnected callback of okhttp3 and the real available state of
> 127.0.0.1:8118?
There should be no lag.
> I init orbothelper, when onEnabled is called i init
>
Printing the trace was enough, I already have the base of the project
working, I had too many hours programming and forget something so simple
http://onpanic.org
El 21 ene. 2017 22:33, "Mark Murphy" escribió:
On Sat, Jan 21, 2017, at 16:14, arrase wrote:
> Ouch!
Ouch!
I was not printing the trace maybe I should take a break but I'm
so close ... thanks :)
El 21 ene. 2017 22:01, "Mark Murphy" escribió:
> On Sat, Jan 21, 2017, at 15:49, arrase wrote:
> > And then is called:
> >
> > public void
On Sat, Jan 21, 2017, at 15:49, arrase wrote:
> And then is called:
>
> public void onConnectionException(Exception e)
What does the stack trace associated with the exception tell you?
--
Mark Murphy (a Commons Guy)
https://commonsware.com | https://github.com/commonsguy
Hi,
I am fighting with StrongBuilder, currently he wins :) .
What is the correct way to use StrongBuilder + OkHttpClient?
After calling:
try {
StrongOkHttpClientBuilder
.forMaxSecurity(this)
.build(this);
}
12 matches
Mail list logo