briar issueshttps://code.briarproject.org/briar/briar/-/issues2021-03-29T13:00:18Zhttps://code.briarproject.org/briar/briar/-/issues/1945Previous/next unread message buttons sometimes don't appear2021-03-29T13:00:18ZakwizgranPrevious/next unread message buttons sometimes don't appearOn the Galaxy Ace 2 (Android 4.1.2), the previous/next unread message buttons in forums and private groups don't always appear. The small badge showing the number of unread messages above/below is shown, but not the large button it's sup...On the Galaxy Ace 2 (Android 4.1.2), the previous/next unread message buttons in forums and private groups don't always appear. The small badge showing the number of unread messages above/below is shown, but not the large button it's supposed to be attached to.
Sometimes the large button appears late, after the badge, and sometimes it doesn't appear at all. Turning the screen off and on doesn't make a difference, but scrolling causes the large button to appear.
![device-2021-02-19-154020](/uploads/25f68f4b6ce2652f62d0a2d963675d12/device-2021-02-19-154020.png)https://code.briarproject.org/briar/briar/-/issues/1983Add CalyxOS panic button to list of supported panic button apps2021-03-24T17:16:18ZakwizgranAdd CalyxOS panic button to list of supported panic button appsCalyxOS has a built-in panic button based on Ripple. Add its signature to our panic responder so Briar responds to it.CalyxOS has a built-in panic button based on Ripple. Add its signature to our panic responder so Briar responds to it.https://code.briarproject.org/briar/briar/-/issues/1523RuntimeException: Camera is being used after Camera.release() was called2021-03-24T16:26:51ZakwizgranRuntimeException: Camera is being used after Camera.release() was called* Android version: 6.0.1
* Briar version: 1.1.5 (8f4c3c4)
* Phone models: Samsung GT-I9100 and GT-I9300 (m0xx)
* User feedback: "I could not scan other device. They could scan me. I have Replicant 6.003."
Stacktrace:
```
java.lang.Runti...* Android version: 6.0.1
* Briar version: 1.1.5 (8f4c3c4)
* Phone models: Samsung GT-I9100 and GT-I9300 (m0xx)
* User feedback: "I could not scan other device. They could scan me. I have Replicant 6.003."
Stacktrace:
```
java.lang.RuntimeException: Camera is being used after Camera.release() was called
at android.hardware.Camera.native_getParameters(Native Method)
at android.hardware.Camera.getParameters(Camera.java:1999)
at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1152)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5461)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
```
We have four reports of this crash, one on the GT-I9100 (running Replicant) and three on the GT-I9300 (probably also running Replicant, as it's the same Android version as the GT-I9100, and the version's too high to be a factory ROM).
This looks like a Replicant bug: camera calls are being made asynchronously. I'll report it upstream. I'm not adding it to the current milestone as there doesn't seem to be anything we can do.https://code.briarproject.org/briar/briar/-/issues/1901TimeoutException: android.view.ThreadedRenderer.finalize() timed out after 10...2021-03-24T16:19:49ZakwizgranTimeoutException: android.view.ThreadedRenderer.finalize() timed out after 10 seconds* Android version: 6.0.1
* Phone model: ZTE Z837VL
* Briar version: 1.2.7 (eb562f8)
Stacktrace:
```
java.util.concurrent.TimeoutException: android.view.ThreadedRenderer.finalize() timed out after 10 seconds
at android.view.Threa...* Android version: 6.0.1
* Phone model: ZTE Z837VL
* Briar version: 1.2.7 (eb562f8)
Stacktrace:
```
java.util.concurrent.TimeoutException: android.view.ThreadedRenderer.finalize() timed out after 10 seconds
at android.view.ThreadedRenderer.nDeleteProxy(Native Method)
at android.view.ThreadedRenderer.finalize(ThreadedRenderer.java:413)
at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:202)
at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:185)
at java.lang.Thread.run(Thread.java:818)
```
Edited log:
```
06-08 00:15:24.325 I/IdentityManagerImpl: Identity loaded
06-08 00:15:24.447 I/LifecycleManagerImpl: Starting services
06-08 00:15:24.467 I/AndroidNetworkManager: Received broadcast android.net.conn.CONNECTIVITY_CHANGE
06-08 00:15:24.656 I/PluginManagerImpl: Starting simplex plugins
06-08 00:15:24.656 I/PluginManagerImpl: Starting duplex plugins
06-08 00:15:24.974 I/BriarActivity: Recreating NavDrawerActivity after signing in
06-08 00:15:25.007 I/BaseActivity: Starting NavDrawerActivity
06-08 00:15:25.843 I/BaseActivity: Stopping NavDrawerActivity
06-08 00:15:26.023 I/BaseActivity: Starting NavDrawerActivity
06-08 00:15:26.702 I/BaseActivity: Stopping StartupActivity
06-08 00:15:36.099 I/BaseActivity: Starting SettingsActivity
06-08 00:15:37.574 I/BaseActivity: Stopping SettingsActivity
06-08 00:15:43.860 I/BaseActivity: Starting SettingsActivity
06-08 00:15:44.606 I/BaseActivity: Stopping NavDrawerActivity
06-08 00:15:51.527 I/DevReporterImpl: Sending reports to developers
06-08 00:15:51.531 I/FeedManagerImpl: Tor started, scheduling RSS feed fetcher
06-08 00:15:52.572 I/BaseActivity: Starting NavDrawerActivity
06-08 00:15:53.068 I/BaseActivity: Stopping SettingsActivity
06-08 00:15:56.591 I/BaseActivity: Starting ConversationActivity
06-08 00:15:56.836 I/ConversationActivity: Eagerly loading text for latest message
06-08 00:15:57.155 I/BaseActivity: Stopping NavDrawerActivity
06-08 00:16:01.661 I/DevReporterImpl: Reports sent
06-08 00:16:51.538 I/FeedManagerImpl: Updating RSS feeds...
06-08 00:16:51.587 I/FeedManagerImpl: Done updating RSS feeds
06-08 00:17:32.023 I/ConnectionRegistryImpl: Incoming connection registered: org.briarproject.bramble.tor
06-08 00:17:32.023 I/ConnectionRegistryImpl: Contact connected
```
Looks like this may be a platform bug; recording it just in case.https://code.briarproject.org/briar/briar/-/issues/1976TimeoutException: android.os.BinderProxy.finalize() timed out after 10 seconds2021-03-24T16:19:38ZakwizgranTimeoutException: android.os.BinderProxy.finalize() timed out after 10 seconds* Android version: 7.1.2
* Phone model: Samsung SM-N7505 (hlltexx)
* Briar version: 1.2.16 (8a534b4)
Stacktrace:
```
android.os.BinderProxy.finalize() timed out after 10 seconds
java.util.concurrent.TimeoutException: android.os.BinderPr...* Android version: 7.1.2
* Phone model: Samsung SM-N7505 (hlltexx)
* Briar version: 1.2.16 (8a534b4)
Stacktrace:
```
android.os.BinderProxy.finalize() timed out after 10 seconds
java.util.concurrent.TimeoutException: android.os.BinderProxy.finalize() timed out after 10 seconds
at android.os.BinderProxy.destroy(Native Method)
at android.os.BinderProxy.finalize(Binder.java:677)
at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:222)
at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:209)
at java.lang.Thread.run(Thread.java:761)
```
Possibly related to #1901?https://code.briarproject.org/briar/briar/-/issues/1974briar-headless: multiple SLF4J bindings on tests2021-03-23T06:57:05ZSebastianbriar-headless: multiple SLF4J bindings on testsWhen running the tests on the `briar-headless` module, multiple bindings for SLF4J are found on the classpath, resulting in this warning:
```
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/z/...When running the tests on the `briar-headless` module, multiple bindings for SLF4J are found on the classpath, resulting in this warning:
```
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/z/gitlab/briar/briar-swing/briar-headless/build/libs/briar-headless.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/z/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-simple/1.7.26/dfb0de47f433c2a37dd44449c88d84b698cd5cf7/slf4j-simple-1.7.26.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]
```
It's not too bad as it's actually the same binding that's being found twice. However I was wondering, why this is the case and if there's something misconfigured. I took a look and my analysis is: briar-headless builds a fat jar with all the dependencies included (including slf4j) and for the tests both the fat jar as well as all the dependencies are put on the classpath. That means, we have everything twice on the classpath, not just the slf4j bindings.
I think it would be good to solve this somehow and the solution would probably be to fix the classpath of the tests. Either
* (A) let the tests run with the non-fat (regular) headless jar plus dependencies, or
* (B) run it with the fat jar but exclude the dependencies from the testing classpathhttps://code.briarproject.org/briar/briar/-/issues/1578Improve structure of Briar Headless API documentation2021-03-22T10:52:52ZNicoImprove structure of Briar Headless API documentationCurrently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first ...Currently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first prototype with it](https://nico.dorfbrunnen.eu/posts/2019/briar-first-demo/).
However, I suggest to improve the structure of the documentation by moving it into a separate repository. My suggestion was to create a Hugo page with a docs theme (or some other static site generator) at docs.briarproject.org.
@grote's response to this was (loosely translated by me): "Best to make the documentation directly into the code with swagger"
My response to this now: OK, we can do this, but I don't know how much sense it makes to put a lot of basic explanations into code. E.g. all the valuable information collected in https://code.briarproject.org/briar/briar/issues/1577.
**Update:** I agree with Torsten that it's best to generate the documentation from code. That's what I do with [`briar_wrapper`](https://code.briarproject.org/briar/python-briar-wrapper), too, at https://wrapper.docs.briarproject.org/ and the API's docs can be hosted at https://api.docs.briarproject.org/, imho.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1965Enable taking pictures directly from the message menu and store pictures take...2021-03-10T12:36:13ZSilent ResearchEnable taking pictures directly from the message menu and store pictures taken in the briar db only.For security reasons it would be very helpful if we could take pictures directly from the briar chat window and store pictures taken in the encrypted briar db only. At the moment I need to take a picture with the phones camera app and st...For security reasons it would be very helpful if we could take pictures directly from the briar chat window and store pictures taken in the encrypted briar db only. At the moment I need to take a picture with the phones camera app and store it in the standard photos folder of my device.https://code.briarproject.org/briar/briar/-/issues/811Tester did not understand difference between Forum and Private Group2021-02-27T21:49:14ZTorsten GroteTester did not understand difference between Forum and Private GroupOne of the testers from Cryptorave tried Briar again and wondered what the difference between forums and private groups is. Both seem to be a place where you can add people to talk together and both use the same message layout.One of the testers from Cryptorave tried Briar again and wondered what the difference between forums and private groups is. Both seem to be a place where you can add people to talk together and both use the same message layout.https://code.briarproject.org/briar/briar/-/issues/1760Connection protocols (mock-up)2021-02-27T21:46:09ZtuquequeConnection protocols (mock-up)Hey... I participated a few weeks ago in the usability testing calls you're running from time to time and I mentioned in that call that I would create a quick mock-up of what I think would improve, simplify and unify the redundancy of th...Hey... I participated a few weeks ago in the usability testing calls you're running from time to time and I mentioned in that call that I would create a quick mock-up of what I think would improve, simplify and unify the redundancy of the connection protocols present in the lower part of the screen in the Hamburger menu and inside the Settings.
![BriarMockUp2](/uploads/c329efbf4d5582906ca0de7afa588de3/BriarMockUp2.gif)
Hopefully the animated gif is pretty self explanatory. I think this concept would unify those settings (so there's no need to actually go to the settings to get more information about the switches)... and it makes those frequently accessed settings much more readily available to the user.
Greets!https://code.briarproject.org/briar/briar/-/issues/1474Check for view recycling issues when language is changed2021-02-26T18:39:12ZakwizgranCheck for view recycling issues when language is changedIn a code review discussion (https://code.briarproject.org/briar/briar/merge_requests/997#note_33406) we identified the possibility of views being recycled without being bound to new view holders when the app or system language changes (...In a code review discussion (https://code.briarproject.org/briar/briar/merge_requests/997#note_33406) we identified the possibility of views being recycled without being bound to new view holders when the app or system language changes (especially when it changes from RTL to LTR or vice versa).
This seems to be prevented at the moment because we (always?) clear the adapter when the activity stops, and the language can't be changed without stopping the activity. The issue might become live in the future if we change our adapters, so this ticket exists to remind us to check for the issue if we do that.https://code.briarproject.org/briar/briar/-/issues/1948Improve unread message highlighting in forums and private groups2021-02-20T11:46:50ZakwizgranImprove unread message highlighting in forums and private groupsIn a recent testing session we noticed that it's hard to distinguish between read and unread messages in forums and private groups, especially when using the dark theme.
Adding some kind of border or badge to unread messages, as well as...In a recent testing session we noticed that it's hard to distinguish between read and unread messages in forums and private groups, especially when using the dark theme.
Adding some kind of border or badge to unread messages, as well as or instead of using a different background colour, might help.https://code.briarproject.org/briar/briar/-/issues/1949Make it easier to distinguish between replying and writing a new post in a fo...2021-02-20T11:46:47ZakwizgranMake it easier to distinguish between replying and writing a new post in a forum or private groupIn a recent testing session we noticed that it was easy to accidentally write a top-level post in a forum or private group when intending to reply to another post.
Some things that might help:
* Increase the visual difference between th...In a recent testing session we noticed that it was easy to accidentally write a top-level post in a forum or private group when intending to reply to another post.
Some things that might help:
* Increase the visual difference between the "replying" state and the "writing a new post" state (eg look at what Signal does)
* Increase the size of the reply button so it's easier to hit
* Allow a reply to be started by right-swiping a post
Related to #1948, as we currently use the same highlighting for the post being replied to as we use for unread posts.https://code.briarproject.org/briar/briar/-/issues/86Explain the app's privacy properties2021-02-17T19:06:53ZakwizgranExplain the app's privacy propertiesA user asked for a screen to be shown when the app was first run, explaining what privacy properties the app could and couldn't provide.A user asked for a screen to be shown when the app was first run, explaining what privacy properties the app could and couldn't provide.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1940Check if Localizer requires context.createConfigurationContext()2021-02-17T18:49:59ZSebastianCheck if Localizer requires context.createConfigurationContext()It's possible that we can remove this entirely:
https://code.briarproject.org/briar/briar/-/merge_requests/1367#note_46627
Should be tested on many API levels and with toggling themes while testing.It's possible that we can remove this entirely:
https://code.briarproject.org/briar/briar/-/merge_requests/1367#note_46627
Should be tested on many API levels and with toggling themes while testing.https://code.briarproject.org/briar/briar/-/issues/1938UnknownServiceException: Cleartext communication not permitted2021-02-17T12:27:36ZakwizgranUnknownServiceException: Cleartext communication not permitted* Android version: 10
* Phone model: Fairphone FP3
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Import RSS fail"
Log snippet:
```
02-14 16:15:58.259 W/RssFeedImportActivity: java.net.UnknownServiceException: CLEARTEXT communicati...* Android version: 10
* Phone model: Fairphone FP3
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Import RSS fail"
Log snippet:
```
02-14 16:15:58.259 W/RssFeedImportActivity: java.net.UnknownServiceException: CLEARTEXT communication to [scrubbed] not permitted by network security policy
java.net.UnknownServiceException: CLEARTEXT communication to [scrubbed] not permitted by network security policy
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:148)
at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:257)
at okhttp3.RealCall.execute(RealCall.java:93)
at org.briarproject.briar.feed.FeedManagerImpl.getFeedInputStream(FeedManagerImpl.java:385)
at org.briarproject.briar.feed.FeedManagerImpl.fetchSyndFeed(FeedManagerImpl.java:332)
at org.briarproject.briar.feed.FeedManagerImpl.addFeed(FeedManagerImpl.java:171)
at org.briarproject.briar.android.blog.RssFeedImportActivity.lambda$importFeed$2(RssFeedImportActivity.java:137)
at org.briarproject.briar.android.blog.RssFeedImportActivity.lambda$importFeed$2$RssFeedImportActivity(Unknown Source:0)
at org.briarproject.briar.android.blog.-$$Lambda$RssFeedImportActivity$yMsHehcx_j-aBTiyhHwsHyxrpIs.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
```
Note: the domain name wasn't scrubbed from the original log. We should fix that.https://code.briarproject.org/briar/briar/-/issues/1936Contact was shown as offline when online2021-02-17T11:15:26ZakwizgranContact was shown as offline when online* Android version: 10
* Phone model: Huawei LYA-L29 (LYA-L29RU)
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Very often displays incorrect information about the network status of another contact. The interlocutor is online for all...* Android version: 10
* Phone model: Huawei LYA-L29 (LYA-L29RU)
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Very often displays incorrect information about the network status of another contact. The interlocutor is online for all network conditions, and displays as if he is not available."
Edited log:
```
02-12 20:59:14.597 I/DuplexOutgoingSession: Sending keepalive
02-12 20:59:44.598 I/DuplexOutgoingSession: Sending keepalive
02-12 20:59:53.360 I/AndroidNetworkManager: Received broadcast android.intent.action.SCREEN_ON
02-12 20:59:53.367 I/TorPlugin: Online: true, wifi: true, IPv6 only: false
02-12 20:59:53.367 I/TorPlugin: Country code: RU
02-12 20:59:53.367 I/TorPlugin: Charging: false
02-12 20:59:53.367 I/TorPlugin: Enabling network
02-12 20:59:53.367 I/TorPlugin: Using obfs4 bridges
02-12 20:59:53.367 I/TorPlugin: Disabling connection padding
02-12 21:00:02.666 I/PollerImpl: Polling plugin org.briarproject.bramble.bluetooth
02-12 21:00:02.672 I/ConnectionRegistryImpl: 0 contacts connected or better: org.briarproject.bramble.bluetooth
02-12 21:00:09.531 I/BaseActivity: Creating SplashScreenActivity
02-12 21:00:09.575 I/BaseActivity: Creating NavDrawerActivity
02-12 21:00:09.597 I/BaseActivity: Starting NavDrawerActivity
02-12 21:00:09.598 I/BaseActivity: Resuming NavDrawerActivity
02-12 21:00:10.158 I/BaseActivity: Destroying SplashScreenActivity
02-12 21:00:14.598 I/DuplexOutgoingSession: Sending keepalive
02-12 21:00:16.395 I/BaseActivity: Pausing NavDrawerActivity
02-12 21:00:16.818 I/BaseActivity: Stopping NavDrawerActivity
02-12 21:00:17.015 I/PollerImpl: Polling plugin org.briarproject.bramble.tor
02-12 21:00:17.019 I/ConnectionRegistryImpl: 1 contacts connected or better: org.briarproject.bramble.tor
02-12 21:00:17.020 I/TorPlugin: Connecting to v3 wwi[scrubbed]
02-12 21:00:17.793 I/TorPlugin: Connected to v3 wwi[scrubbed]
02-12 21:00:17.824 I/DuplexOutgoingSession: Generated ack: false
02-12 21:00:17.827 I/DuplexOutgoingSession: Generated batch: false
02-12 21:00:17.830 I/DuplexOutgoingSession: Generated offer: false
02-12 21:00:17.830 I/DuplexOutgoingSession: Generated request: false
02-12 21:00:18.981 I/ConnectionRegistryImpl: Outgoing connection registered: org.briarproject.bramble.tor
02-12 21:00:18.982 I/ConnectionRegistryImpl: Contact connected
02-12 21:00:18.982 I/ConnectionRegistryImpl: Setting connection priority: org.briarproject.bramble.tor
02-12 21:00:28.954 I/AndroidNetworkManager: Received broadcast android.intent.action.SCREEN_OFF
02-12 21:00:28.959 I/TorPlugin: Online: true, wifi: true, IPv6 only: false
02-12 21:00:28.959 I/TorPlugin: Country code: RU
02-12 21:00:28.959 I/TorPlugin: Charging: false
02-12 21:00:28.959 I/TorPlugin: Enabling network
02-12 21:00:28.959 I/TorPlugin: Using obfs4 bridges
02-12 21:00:28.959 I/TorPlugin: Disabling connection padding
02-12 21:00:33.955 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:34.584 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:34.720 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:34.942 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:35.030 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:39.403 I/TorPlugin: V3 descriptor uploaded
02-12 21:00:44.598 I/DuplexOutgoingSession: Sending keepalive
02-12 21:00:47.823 I/DuplexOutgoingSession: Sending keepalive
02-12 21:00:50.914 I/AndroidNetworkManager: Received broadcast android.intent.action.SCREEN_ON
02-12 21:00:50.918 I/TorPlugin: Online: true, wifi: true, IPv6 only: false
02-12 21:00:50.918 I/TorPlugin: Country code: RU
02-12 21:00:50.918 I/TorPlugin: Charging: false
02-12 21:00:50.918 I/TorPlugin: Enabling network
02-12 21:00:50.918 I/TorPlugin: Using obfs4 bridges
02-12 21:00:50.918 I/TorPlugin: Disabling connection padding
02-12 21:00:57.771 I/BaseActivity: Starting NavDrawerActivity
02-12 21:00:57.772 I/BaseActivity: Resuming NavDrawerActivity
02-12 21:01:02.667 I/PollerImpl: Polling plugin org.briarproject.bramble.bluetooth
02-12 21:01:02.673 I/ConnectionRegistryImpl: 0 contacts connected or better: org.briarproject.bramble.bluetooth
02-12 21:01:05.717 I/TorPlugin: V3 descriptor uploaded
02-12 21:01:06.601 I/TorPlugin: V3 descriptor uploaded
02-12 21:01:06.988 I/BaseActivity: Pausing NavDrawerActivity
02-12 21:01:07.007 I/BaseActivity: Creating SettingsActivity
02-12 21:01:07.026 I/BaseActivity: Starting SettingsActivity
02-12 21:01:07.060 I/BaseActivity: Resuming SettingsActivity
02-12 21:01:07.539 I/BaseActivity: Stopping NavDrawerActivity
02-12 21:01:11.405 I/PollerImpl: Polling plugin org.briarproject.bramble.lan
02-12 21:01:11.418 I/ConnectionRegistryImpl: 0 contacts connected or better: org.briarproject.bramble.lan
02-12 21:01:11.539 I/BaseActivity: Pausing SettingsActivity
02-12 21:01:11.551 I/BaseActivity: Creating FeedbackActivity
```
Notes:
* A duplex connection to a contact is open at the start of the log
* Later log messages from the poller show that this is a Tor connection, rather than Bluetooth or LAN
* A second Tor connection is made at 21:00:17
* The Tor hidden service descriptor is being uploaded, which may indicate that the device recently came online, or may be the daily republishing of the descriptor
The reported issue could be a UI bug (failing to show/update the online state of one or both contacts), or it could be a network or power management issue at the contact's end, causing the contact's Tor connection to be lost.https://code.briarproject.org/briar/briar/-/issues/1925More config options for metered connection/mobile data2021-02-16T23:17:23ZJens KorteMore config options for metered connection/mobile dataAndroid distinguishes between metered and non-metered connections. It could be useful, if users can decide, when to connect to the tor-network. The mobile option is a similar option.
~~Does an option like "connect once per hour until al...Android distinguishes between metered and non-metered connections. It could be useful, if users can decide, when to connect to the tor-network. The mobile option is a similar option.
~~Does an option like "connect once per hour until all messages are received" or "disconnect after fetching all messages" make sense? An extreme way to configure this would be to offer an repeating event configuration like a calendar software, but I am unsure, if this would be a privacy related issue, because the connections could get predictable. On the other hand this could save bandwidth and battery, if people would agree upon connect every beginning of an hour for some minutes.~~ see #1588
Original issue: https://code.briarproject.org/briar/briar-manual/-/issues/7https://code.briarproject.org/briar/briar/-/issues/1932API 28 emulator stalled on "decrypting database..." screen2021-02-16T23:16:46ZSebastianAPI 28 emulator stalled on "decrypting database..." screenI tested the current master on a bunch of devices and emulators.
On API 28 I got the problem that briar does not get past the "decrypting database..." screen after entering the password. When switching back to a different app and then ba...I tested the current master on a bunch of devices and emulators.
On API 28 I got the problem that briar does not get past the "decrypting database..." screen after entering the password. When switching back to a different app and then back to briar, I'm properly logged in and can see the contact list.
Tried to reproduce on other devices, but it only appears on my API 28 emulator. Also tried emulators with levels 23, 24, 29 and 30 as well as real devices with levels 16 and 23. All work fine.
@akwizgran you do have API level 28 devices, maybe you could try and see if the problem can be reproduced there?https://code.briarproject.org/briar/briar/-/issues/1923Mailing list migration2021-02-16T23:06:44ZsysterMailing list migrationMailing list migration:
For the reasons:
https://code.briarproject.org/briar/briar/-/issues/988
https://code.briarproject.org/briar/briar/-/issues/1741
"_sourceforge doesn't give us access to the subscriptions_"
migration is bet...Mailing list migration:
For the reasons:
https://code.briarproject.org/briar/briar/-/issues/988
https://code.briarproject.org/briar/briar/-/issues/1741
"_sourceforge doesn't give us access to the subscriptions_"
migration is better done soonish, then later.
-----------------------------------------------------------
**Solution 1:**
Creating new lists and announcing them. Letting the old lists run for 1 year or something and regular invite folks to join the new lists.
**Solution 2:**
There is access to subscribers email pre-2017. They can be migrated to new service and sending them an email asking for confirmation. Sending announcement via sourceforge to all, that there's a new email list. There is no option that pre-2017 subscribers won't receive that same email, even if they're already part of the new list. Potential legal issue: Do you have the consent, that allows you to switch the pre-2017 subscribers to new service?
**Solution 3:**
?
Concern:
- discussion in devel list will be split between 2 lists until everyone participating switched to the new one, or if this issue is mitigated by bridging the lists (could be as simple as coping the digest of the daily mails into the other list with a link to read them in the browser)