search

splondike / polipoid

Android wrapper for the polipo proxy
GNU General Public License v3.0
35 stars 12 forks source link

Not working on lollipop 5.0.2 #11

Closed mauny closed 8 years ago

mauny commented 9 years ago

Polipoid version 1.1.0 from F-Droid: same as other reports here with LP 5.0.2 on oneplus one with CM12s: fails to start, red icon.

Should I try another version? If yes, where should I get it from?

Thanks

splondike commented 9 years ago

I don't have a physical device capable of running CM unfortunately, nor am I sure how to run it on an emulator.

You could try a couple of things to help diagnose this issue:

  1. Try running the previous version of Polipoid. You can do this by opening it up in f-droid and tapping 'Version 1.0.1'.
  2. If you have root access and a terminal emulator (or adb) you can try running the Polipo binary directly and looking for error messages. To do this open up your shell (e.g. using adb shell from your host computer). Next switch to root with su. Next change directories using cd /data/data/com.polipoid/app_polipo/. Finally try running the polipo binary using ./polipo or ./polipo-pie depending on what is present in the directory. This presumably will crash with some error message.
mauny commented 9 years ago

Hi, thanks for your message. I tried both suggestions (2/ then 1/)

Tried 2/ (that is, run ./polipo-pie in a shell as root) . Here are the error-messages: DNS: couldn't open /etc/resolv.conf: No such file or directory Couldn't determine host name -- using ``polipo'' Disabling disk cache: No such file or directory Disabling local tree: No such file or directory Couldn't bind: Address already in use Couldn't establish listening socket: Address already in use

About 1/, I then uninstalled my current version and installed the older version (1.0.1). In a shell, whe I execute ./polipo, I get a message saying that only PIE are supported. Precisely: error: only position independent executables (PIE) are supported

I can provide you with more info on my config and perform tests on my phone, if you need. Thanks in advance,

splondike commented 9 years ago

Ok, the problem seems to be that some other service is listening on port 8123. If you create a file with the following contents and upload it using the settings interface in 1.1.0 (open the menu and press settings) you should be able to get it working:

proxyPort = 8124
cacheIsShared=false
chunkHighMark=1048576

Note that I've changed the port the thing is listening on to 8124. The UI won't reflect this, but you should use this as the port in your configuration instead of 8123.

splondike commented 8 years ago

Closing ticket due to inactivity.