Closed GoogleCodeExporter closed 9 years ago
1. 你需要在启用服务的同时记录 logcat,现在的 logcat
文件无效。
2. 检查你的防火墙设置,关闭LBE等软件后再尝试。
Original comment by max.c...@gmail.com
on 11 May 2013 at 5:14
请问如何记录 logcat?
Original comment by gdxiao...@gmail.com
on 11 May 2013 at 5:16
在打开GAE开关的同时,重复你之前的所有操作。
Original comment by max.c...@gmail.com
on 11 May 2013 at 5:19
我是在win7下操作的,裸机,已关Windows防火墙以及LBE,N7100,�
��版4.1.2,仍然提示
root@android:/sdcard # http_proxy=http://127.0.0.1:1984 wget http://twitter.com
1984 wget http://twitter.com <
Connecting to 127.0.0.1:1984 (127.0.0.1:1984)
wget: error getting response: Connection reset by peer
1|root@android:/sdcard # cat index.html | grep twitter.com
cat index.html | grep twitter.com
sh: cat: index.html: No such file or directory
郁闷……
Original comment by gdxiao...@gmail.com
on 11 May 2013 at 5:50
不是cmd.txt里的内容,而是重新收集你的log.txt
Original comment by max.c...@gmail.com
on 11 May 2013 at 5:52
重新生成,请问如何判断log文件是否有效,我好把有效的文��
�上传,以节省你们的时间和精力
Original comment by gdxiao...@gmail.com
on 11 May 2013 at 6:04
Attachments:
你的代理地址填写错误,不是「https://xxx.appspot.com/fetch.php」��
�应该是「https://xxx.appspot.com/2」。
Original comment by max.c...@gmail.com
on 11 May 2013 at 6:08
[deleted comment]
接上面的红色字样:
killall: python-cl:no process killed
killall: redsocks:no process killed
/data/data/org.gaeproxy/proxy.sh[53]:kill:5616: No such process
/data/data/org.gaeproxy/proxy.sh[53]:kill:*****: No such process
……(连续很多行上面一样的字样,就是后面的数字不一样��
�
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
Original comment by gdxiao...@gmail.com
on 11 May 2013 at 6:32
1. 更新你的服务器端到2.1.17。
2. 卸载客户端后,重新安装0.21.7版。
Original comment by max.c...@gmail.com
on 11 May 2013 at 6:35
好的,谢谢你:-)
Original comment by gdxiao...@gmail.com
on 11 May 2013 at 6:37
Original comment by max.c...@gmail.com
on 11 May 2013 at 3:02
管理员请更新下FAQ,这个跟issue
515我发的帖子一样,明显也是因为supersu吧。
Original comment by hnt...@gmail.com
on 14 May 2013 at 1:06
谢谢LS的兄弟,果然是supersu的问题,终于解决了,再次感谢
Original comment by gdxiao...@gmail.com
on 14 May 2013 at 3:55
Original issue reported on code.google.com by
gdxiao...@gmail.com
on 11 May 2013 at 5:08Attachments: