Project *Core Apps » Bazaar » ChatSecure:Android » KeySync » Orbot » Orfox Private Browser » Orweb » Secure ReaderCacheWordIOCipherNetCipherPanicTrusted Intents » CheckeyLibreoSpideyStoryMaker™SecureSmartCam » CameraV (InformaCam Project) » ObscuraCam
Tracker *Bug Feature Task
Subject *
Description Issue: New installations of Orbot on March 26 on an SIII and Note 2 (running Android 4.1.2 and 4.3 respectively) resulted in identical behavior: When launched, Orbot indicated *immediately* that it had successfully connected to Tor, while Orweb indicated (correctly) that Orbot had not been successful and should be started. Scope of issue: This only occurred on two devices out of nine. The lead trainer also ran an SIII and did not have this issue, which really puzzled us. Troubleshooting: Using Application Manager, we force-quit Orbot and re-started it. No joy. Solution: We power-cycled both devices and, in both cases, Orbot worked properly afterwards. (Would advise low priority unless you hear from many others spotting the same behavior)
Status *New
Priority *Low Normal High Urgent Immediate
Assignee << me >>amoghbl1hansn8fr8Anonymous
Target version v14 - April Anons v15 - MayPhlowerz backlog
Start date
Due date
Estimated time Hours
% Done0 % 10 % 20 % 30 % 40 % 50 % 60 % 70 % 80 % 90 % 100 %
Component
Files (Maximum size: 195 MB)