Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2011-02-15T22:59:33Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1957Do not start/stop tor when touch on log view2011-02-15T22:59:33ZTracDo not start/stop tor when touch on log viewDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding whe...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding when more log added into view.
BTW: the font size is too small in log view.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1958Orbot stopped after I press Home/Back button2011-05-03T07:00:49ZTracOrbot stopped after I press Home/Back buttonDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, ...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, 1.0.4
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1960Orbot website points to wrong svn location2011-02-15T23:08:58ZRoger DingledineOrbot website points to wrong svn locationhttps://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torp...https://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torproject.org/svn/projects/android/trunk/Orbot/Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2069Orbot fails to start if configured as a relay2020-06-12T23:54:18ZTracOrbot fails to start if configured as a relayOrbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config option...Orbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config options left us in a broken state. Dying."
Selected lines from the log:
Orbit is starting....
got tor proc id: 18938
Tor process id=18938
Starting Tor...
Setting up control...
SUCCESS connected to control port
SUCCESS authenticated to control port
Setting up control...complete.
adding control port event handle
SUCCESS added control port event handle
You ContactInfo config option is not set .Please ...
Opening OR listener on 0.0.0.0:9001
You Tor server's identify key fingerprint is 'Skevek 73DD7A435...'
Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory
set_options(): Bug: Acting on config options left us in a broken state. Dying.
**Trac**:
**Username**: aglNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2168Privoxy file missing from Orbot2012-04-06T01:04:03ZTracPrivoxy file missing from OrbotOn Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy ...On Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy encountered an error while processing your request:
Could not load template file forwarding - failed or one of its included components.
Please contact your proxy administrator.
If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy Install directory, or /etc/privoxy/).
As a user rather than a technogeek, I have no idea how to fix this, but I think it should be in the Orbot installation package.
**Trac**:
**Username**: 4u2guessNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2423OrBot transproxy silently fails open2011-05-10T01:57:25ZcypherpunksOrBot transproxy silently fails openOn rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are s...On rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are still present after it creates them.
Ideally, it should also ping check.torproject.org, which provides a minimal, easy to parse XHTML response at https://check.torproject.org/?TorButton=trueNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2424Android purges firewall rules after network disable/airplane mode.2020-06-13T00:01:39ZcypherpunksAndroid purges firewall rules after network disable/airplane mode.Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orb...Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orbot config screen to cause it to reapply them.
OrBot should listen for these network disable/loss/disconnect events if possible, and reinstate the iptables rules after this happens.
Someone should also test if switching from cell data to+from wifi also triggers this iptables reset. I have not tested that yet.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2493orbot is not working on Android (Froyo 2.2)2011-02-06T12:14:14ZTracorbot is not working on Android (Froyo 2.2)Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor...Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor is working with your web check page, it says " sorry but you are not using Tor"
It looks like I'm not the only one that I have this issue, others from xda-developers have the same issue.
Is it possible to fix this ?
Kind Regards,
Dinu
**Trac**:
**Username**: dinocNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2635Orbot continuously tries to kill Privoxy using the wrong PID2011-05-10T02:01:20ZNathan FreitasOrbot continuously tries to kill Privoxy using the wrong PIDorbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the C...orbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the CPU, making it look like the orbot app has crashed and preventing orbot from starting up correctly or shutting down correctly.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2636Orbot doesn't redirect connections to tor2011-05-10T02:04:20ZNathan FreitasOrbot doesn't redirect connections to tororbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active...orbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active chains). I can't see any mention of iptables in the log, but I don't know if there should be anything.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2662Gibberbot does not stay signed in2011-03-06T05:05:11ZcypherpunksGibberbot does not stay signed inGibberbot should have an option to stay signed in. I keep getting logged out after leaving the app in the background...Gibberbot should have an option to stay signed in. I keep getting logged out after leaving the app in the background...Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2761Orbot Service not shutting down2020-06-13T00:08:40ZTracOrbot Service not shutting downBehaviour:
When closing tor network with big Button and exiting Orbot after tor is "deactivated", privoxy is still running and the Orbot service is not stopped.
Actions:
- Killing Privoxy from shell stops the privoxy process (OK)
- Kill...Behaviour:
When closing tor network with big Button and exiting Orbot after tor is "deactivated", privoxy is still running and the Orbot service is not stopped.
Actions:
- Killing Privoxy from shell stops the privoxy process (OK)
- Killing Orbot process simply restarts the process (BAD)
Env:
- Running Orbot v1.0.4.1
- Android Froyo 2.2.1 speedmod kernel
- Samsung Galaxy
**Trac**:
**Username**: AlBotNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2775Orbot doesn't show iptables failure2011-05-10T02:03:47ZChristian FrommeOrbot doesn't show iptables failureOrbot iptables settings fail to apply for Orbot on Android 2.3.3, cm7 port. The problem seems to be related to bionic library, not Orbot itself. Still, maybe Orbot should not show a green onion in case the iptables command fails.
Here i...Orbot iptables settings fail to apply for Orbot on Android 2.3.3, cm7 port. The problem seems to be related to bionic library, not Orbot itself. Still, maybe Orbot should not show a green onion in case the iptables command fails.
Here is an example of how iptables fails on 2.3.3.
```
# whoami
root
# iptables -A INPUT -p icmp -j ACCEPT
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:378
```
A Google search for the error message shows that lots of other projects also encouter the same problem.
Thanks to cubi for testing & reporting this issue.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2935privoxy not the right http proxy2012-04-06T01:01:45ZRoger Dingledineprivoxy not the right http proxyprivoxy doesn't do http 1.1, so no pipelining for you. Also, it reads the whole page before it passes any of it on to Tor, introducing considerable latency from the user's perspective.
You might be happier moving to polipo, assuming it ...privoxy doesn't do http 1.1, so no pipelining for you. Also, it reads the whole page before it passes any of it on to Tor, introducing considerable latency from the user's perspective.
You might be happier moving to polipo, assuming it builds in android land. (Does it?)
You will likely be happier still moving to 'no http proxy', if you can manage it. (Can you?)Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2981Progress bar in an infinite loop while loading2020-06-13T00:12:50ZSathyanarayanan GunasekaranProgress bar in an infinite loop while loadingOrbot Version - 1.0.5
Device - HTC Legend
1. Start Orbot
2. While the progress bar loads, press Back/home
3. Return to Orbot
The progress bar is in an infinite loop, with no text.
The only way to exit, is to force quit or reboot.Orbot Version - 1.0.5
Device - HTC Legend
1. Start Orbot
2. While the progress bar loads, press Back/home
3. Return to Orbot
The progress bar is in an infinite loop, with no text.
The only way to exit, is to force quit or reboot.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2989ORBot install fails when installing/uncompressing tor binary2011-05-10T02:05:42ZTracORBot install fails when installing/uncompressing tor binaryThis is a bug report for 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev, running on CM6.1.0-RC2 (Desire HD).
It seems like ORBot fails to unzip the tor binary to the data directory, as it is too large to fit in the dedicated memory for that o...This is a bug report for 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev, running on CM6.1.0-RC2 (Desire HD).
It seems like ORBot fails to unzip the tor binary to the data directory, as it is too large to fit in the dedicated memory for that operation (...or so Google tells me).
Additionally (not sure if that should be a second bug), ORBot still declares the operation successful, even though it is caught by the exception handler. This, of course, leads to ORBot trying (and failing) to start afterwards, constantly receiving -1 as the pid (if you want to detect unrecoverable situations, that _might_ be one approach - keep in mind that I haven't read the corresponding code, maybe ORBot is already doing that).
Logcat (useless messages redacted):
---------------
I/ActivityManager( 1487): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.torproject.android/.Orbot }
I/ActivityManager( 1487): Start proc org.torproject.android for activity org.torproject.android/.Orbot: pid=23812 uid=10105 gids={3003}
I/ORBOT (23812): service started: org.torproject.android.service.TOR_SERVICE
D/ORBOT (23812): Tor binary exists=false
D/ORBOT (23812): Privoxy binary exists=false
D/asset (23812): Data exceeds UNCOMPRESS_DATA_MAX (3188430 vs 3145728)
D/ORBOT (23812): Error writing output file '/data/data/org.torproject.android/app_bin/tor': java.io.IOException
D/ORBOT (23812): SUCCESS: installed tor, privoxy binaries from raw
------------
Should I try running it on CM7 instead?
**Trac**:
**Username**: __sporkbombNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2993ORBot Alpha [GUI]: Blank semi-permanent status box2011-05-10T02:06:06ZTracORBot Alpha [GUI]: Blank semi-permanent status boxVersion: 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev
ROM: CM 7.0.2-DesireHD
Side note: Should bugs like this posted on guardian-dev instead?
The ORBot status box (in the center of the screen, should probably contain status messages regard...Version: 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev
ROM: CM 7.0.2-DesireHD
Side note: Should bugs like this posted on guardian-dev instead?
The ORBot status box (in the center of the screen, should probably contain status messages regarding connection establishment) remains black, only containing the white "ring" animation. Meanwhile, the Android in the background remains yellow.
This remains constant - even if the connection is already established and transproxying enabled - until the screen is re-drawn (e.g. by unlocking the screen after the blanking timeout or by selecting any of the ORBot notificiations), at which point the expected UI state is established (green Android, no status box, "Connected to Tor").
Expected behaviour is of course that the "connected" UI state is displayed as soon as ORBot has finished connection setup.
**Trac**:
**Username**: __sporkbombNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3081Orbot start up problem/looping dialog2020-06-13T00:14:36ZNathan FreitasOrbot start up problem/looping dialog#1. Almost always it takes two (sometimes three) starts for Orbot to connect properly. One symptom is in #2 below. Another is that all looks good (connection sequence looks correct, drop down alert looks correct) but testing via check....#1. Almost always it takes two (sometimes three) starts for Orbot to connect properly. One symptom is in #2 below. Another is that all looks good (connection sequence looks correct, drop down alert looks correct) but testing via check.torproject.org shows no connection. Exiting and restarting usually yields a working connection.
#2. Frequently on the first try, the app shows the spinning white circular pattern in the black rectangle in front of the Orbot logo, "Orbot is starting" message under the logo, and then stays in that mode indefinitely.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3082Orbot problems on rooted x10 with jit installed.2020-06-13T00:14:36ZNathan FreitasOrbot problems on rooted x10 with jit installed.JIT is the just in time compiler developed by someone on XDA for the X10. Apparently SE pulled it from the 2.1 build due to a risk of processor overheating. When you put it back you get a performance increase of 50% based on benchmarks...JIT is the just in time compiler developed by someone on XDA for the X10. Apparently SE pulled it from the 2.1 build due to a risk of processor overheating. When you put it back you get a performance increase of 50% based on benchmarks, with the slight cost that when the processor is maxed out it sometimes casues a reboot, although i dont think that was the issue here. Not had a problem with overheating yet, but got safeguards in place.
Went into settings (note given previous problems I had disabled start on boot, might be worth making this default initially?) and enabled logs, attatched to this email.
Note display was helpful on one attempt but blank apart from waiting animation on 2 others. No easy way to stop process apart from task killer.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3226Screen orientation change ends configuration wizard2011-10-31T03:40:43ZTracScreen orientation change ends configuration wizard**moved from github issue #6 (https://github.com/guardianproject/Orbot/issues/6)**
Last reproduced on Orbot-1.0.5.2 on CM-7.05132011-NIGHTLY-N1
When the screen orientation changes while the configuration wizard is active, the user gets...**moved from github issue #6 (https://github.com/guardianproject/Orbot/issues/6)**
Last reproduced on Orbot-1.0.5.2 on CM-7.05132011-NIGHTLY-N1
When the screen orientation changes while the configuration wizard is active, the user gets dropped into the Orbot main activity screen. There seems to be no way to resume the wizard. This does not seem to impair any of Orbot's functions.
I observed the same issue with other pop-up activities like the first Tor connection confirmation.
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitas