briar issueshttps://code.briarproject.org/briar/briar/-/issues2020-11-15T15:32:03Zhttps://code.briarproject.org/briar/briar/-/issues/1749Blog post dividers are hard to see2020-11-15T15:32:03ZakwizgranBlog post dividers are hard to seeA user reported that the dividers between sections of a reblogged/commented post are hard to see (there isn't enough contrast between the grey divider and the white background).A user reported that the dividers between sections of a reblogged/commented post are hard to see (there isn't enough contrast between the grey divider and the white background).https://code.briarproject.org/briar/briar/-/issues/1750Text should adapt to system text size setting2021-03-04T14:29:55ZakwizgranText should adapt to system text size settingA user asked for text in Briar to follow the system text size setting.
I'm labelling this as a bug because as far as I can tell it's already the intended behaviour - we're using `sp` rather than `dp` or `px` for all text sizes. But chan...A user asked for text in Briar to follow the system text size setting.
I'm labelling this as a bug because as far as I can tell it's already the intended behaviour - we're using `sp` rather than `dp` or `px` for all text sizes. But changing the system text size doesn't affect Briar, even after signing out and relaunching.
https://developer.android.com/training/multiscreen/screendensities.html#TaskUseDP
> When defining text sizes, however, you should instead use scalable pixels (sp) as your units (but never use sp for layout sizes). The sp unit is the same size as dp, by default, but it resizes based on the user's preferred text size.https://code.briarproject.org/briar/briar/-/issues/1751Explain visibility of reblogs/comments2020-11-15T15:29:27ZakwizgranExplain visibility of reblogs/commentsA user was surprised to learn that a reblogged post was visible to all contacts of the user who reblogged the post, rather than all contacts of user who wrote the original post. We should add some onboarding to explain this the first tim...A user was surprised to learn that a reblogged post was visible to all contacts of the user who reblogged the post, rather than all contacts of user who wrote the original post. We should add some onboarding to explain this the first time the reblog/comment feature is used.https://code.briarproject.org/briar/briar/-/issues/1752After internal emulated sdcard's zero bytes disk space free condition, the da...2020-11-16T10:46:50ZmathAfter internal emulated sdcard's zero bytes disk space free condition, the database became corrupted and all Briar data was losthttps://code.briarproject.org/briar/briar/-/issues/1753API 30: Access to installed packages is restricted2021-01-12T11:22:23ZakwizgranAPI 30: Access to installed packages is restrictedWhen we target API 30 we'll need to make changes to retain the ability to check whether power management apps are installed:
https://medium.com/androiddevelopers/package-visibility-in-android-11-cc857f221cd9
* [x] `AndroidTorPlugin`: `...When we target API 30 we'll need to make changes to retain the ability to check whether power management apps are installed:
https://medium.com/androiddevelopers/package-visibility-in-android-11-cc857f221cd9
* [x] `AndroidTorPlugin`: `pm.getPackageInfo(app.getPackageName(), 0)`
* [x] `AndroidWakeLockManagerImpl`: `packageName.startsWith()`
* [x] `PanicPreferencesFragment`: `pm.getApplicationInfo(panicTriggerApp)`
* [x] `PanicPreferencesFragment`: `intent.resolveActivity(pm)`
* [x] `PanicPreferencesFragment`: `PanicResponder.resolveTriggerApps(pm)`
* [x] `ScreenFilterMonitorImpl`: `pm.getInstalledPackages(GET_PERMISSIONS)`
* [x] `ScreenFilterMonitorImpl`: `pm.getPackageInfo(PLAY_SERVICES_PACKAGE, GET_SIGNATURES)`
* [x] `SettingsFragment`: `intent.resolveActivity(pm)`
* [x] `HuaweiView`: `pm.queryIntentActivities(i, PackageManager.MATCH_DEFAULT_ONLY)`
* [x] `KeyAgreementActivity`: `Intent(ACTION_REQUEST_DISCOVERABLE).resolveActivity(pm)`
* [x] `LinkDialogFragment`: `pm.queryIntentActivities()`Adapt to changes in the Android platformTorsten GroteTorsten Grote2021-04-30https://code.briarproject.org/briar/briar/-/issues/1754Test whether hiding UI still works on Android 102020-09-04T10:56:53ZakwizgranTest whether hiding UI still works on Android 10Android 10 places new restrictions on background apps starting activities:
https://developer.android.com/guide/components/activities/background-starts
Check whether BriarService#hideUi(), which is called on low memory and when the devi...Android 10 places new restrictions on background apps starting activities:
https://developer.android.com/guide/components/activities/background-starts
Check whether BriarService#hideUi(), which is called on low memory and when the device shuts down, works under the following circumstances:
* Briar is visible in recent apps
* Briar has been cleared from recent apps but is still running
It's not a big deal if hideUi() stops working, as long as we don't get a crash or unexpected behaviour when calling it or when relaunching the app.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1755Test whether panic button response still works on Android 102020-09-04T11:35:02ZakwizgranTest whether panic button response still works on Android 10Android 10 places new restrictions on background apps starting activities:
https://developer.android.com/guide/components/activities/background-starts
Test whether this affects the panic button response, which uses two invisible activi...Android 10 places new restrictions on background apps starting activities:
https://developer.android.com/guide/components/activities/background-starts
Test whether this affects the panic button response, which uses two invisible activities (PanicResponderActivity and ExitActivity), under the following circumstances:
* Briar isn't running
* Briar is running and visible in recent apps
* Briar is running but not visible in recent appsakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1756Investigate connectivity changes when entering/exiting sleep and doze2020-11-15T15:03:26ZakwizgranInvestigate connectivity changes when entering/exiting sleep and dozeAndroidNetworkManager makes a connectivity check when it receives a broadcast associated with entering or exiting sleep or doze (ACTION_SCREEN_ON, ACTION_SCREEN_OFF or ACTION_DEVICE_IDLE_MODE_CHANGED). A second connectivity check is sche...AndroidNetworkManager makes a connectivity check when it receives a broadcast associated with entering or exiting sleep or doze (ACTION_SCREEN_ON, ACTION_SCREEN_OFF or ACTION_DEVICE_IDLE_MODE_CHANGED). A second connectivity check is scheduled 1 minute after the broadcast, because we've sometimes seen connectivity changes shortly after entering or exiting sleep or doze.
We want to detect these delayed connectivity changes reliably, but we don't want to hold a wake lock for a full minute after every screen on/off event, and in any case that might just cause the connectivity changes to be deferred until we release the wake lock.
Investigate the circumstances under which these delayed connectivity changes happen (on various devices), find out whether our current approach detects them reliably (with and without Tor enabled), and if not, work out how to do so.https://code.briarproject.org/briar/briar/-/issues/1757Investigate whether LAN connections need wake locks2020-11-15T15:46:21ZakwizgranInvestigate whether LAN connections need wake locksWe've added wake locks to Bluetooth connections to ensure keepalives are sent regularly and dead connections are detected in a reasonable amount of time. Investigate whether we need to do the same for LAN connections.We've added wake locks to Bluetooth connections to ensure keepalives are sent regularly and dead connections are detected in a reasonable amount of time. Investigate whether we need to do the same for LAN connections.https://code.briarproject.org/briar/briar/-/issues/1758Periodic timeout monitor task is not cancelled2020-08-14T11:43:47ZakwizgranPeriodic timeout monitor task is not cancelledThe periodic timeout monitor task is meant to be cancelled when the last TimeoutInputStream is closed, but this doesn't happen unless every stream's close() method is called. Transport connections are often closed without calling close()...The periodic timeout monitor task is meant to be cancelled when the last TimeoutInputStream is closed, but this doesn't happen unless every stream's close() method is called. Transport connections are often closed without calling close() on the input stream, leaving the periodic task running unnecessarily and leaking a reference to the closed stream.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1759AndroidTaskScheduler doesn't correctly handle cancellation of periodic tasks2020-08-14T13:04:06ZakwizgranAndroidTaskScheduler doesn't correctly handle cancellation of periodic tasksAndroidTaskScheduler#scheduleWithFixedRate() returns a Future that can be used to cancel the task. But if the Future is cancelled after the first execution of the task, subsequent executions aren't cancelled.AndroidTaskScheduler#scheduleWithFixedRate() returns a Future that can be used to cancel the task. But if the Future is cancelled after the first execution of the task, subsequent executions aren't cancelled.Android 1.2akwizgranakwizgranhttps://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/1761Implement connection potential. For Bluetooth, Lan connections.2020-11-15T14:58:36ZVladislavImplement connection potential. For Bluetooth, Lan connections.Implement connection potential. For Bluetooth, Lan connections.
For example:
1. If users are interconnected through Bluetooth:
Allow any attachment type
2. Through LAN:
Allow calls.
Allow any attachment type and size
Or e...Implement connection potential. For Bluetooth, Lan connections.
For example:
1. If users are interconnected through Bluetooth:
Allow any attachment type
2. Through LAN:
Allow calls.
Allow any attachment type and size
Or explain please why only images are allowed to send.https://code.briarproject.org/briar/briar/-/issues/1762allow connection through Wan avoiding TOR2020-08-28T14:34:06ZVladislavallow connection through Wan avoiding TORAllow connection through Wan avoiding TOR for thouse who need just to send quick message, and at this moment don't care about privacy.Allow connection through Wan avoiding TOR for thouse who need just to send quick message, and at this moment don't care about privacy.https://code.briarproject.org/briar/briar/-/issues/1763Not optimized for throttled internet connection (SIM Card - Data plans)2020-11-16T10:59:49ZN6P4CFB1BSRSLNot optimized for throttled internet connection (SIM Card - Data plans)**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Hello
I use Briar (Tor network) on my Android devices. But it can't send and receive messages when using a throttled internet connection.
I have SIM cards (5G,...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Hello
I use Briar (Tor network) on my Android devices. But it can't send and receive messages when using a throttled internet connection.
I have SIM cards (5G, 4G, 3G and 2G) with data plans, but the speed is throttled to 64 Kbps or 32 Kbps.
Can the developers optimize Briar to send and receive messages even with throttled or very slow Internet connections (64 Kbps and 32 Kbps)?
For comparison I tried Signal Android and here it works fine with throttled internet connection.https://code.briarproject.org/briar/briar/-/issues/1764Change app language does not work2021-02-18T10:28:52ZN6P4CFB1BSRSLChange app language does not work**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Hello,
have installed the Briar app and go to Settings -> Language & region and select a different language than the Android system language.
After restarting ...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Hello,
have installed the Briar app and go to Settings -> Language & region and select a different language than the Android system language.
After restarting the Briar app the app language was not changed. It still uses the system language.Android 1.2IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1765Does not reconnect despite existing Wi-Fi Direct connection2020-11-15T14:30:47ZN6P4CFB1BSRSLDoes not reconnect despite existing Wi-Fi Direct connection**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
1. Connect two Android 10 devices (smartphones) via Wi-Fi Direct
2. Install the Briar app on both Android devices
3. Open the Briar app and add the Android device...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
1. Connect two Android 10 devices (smartphones) via Wi-Fi Direct
2. Install the Briar app on both Android devices
3. Open the Briar app and add the Android devices to contacts
4. Now can send and receive messages. A green icon will light up.
5. On the first Android device in Briar app tap "Sign out" and open Briar app again and enter the password.
6. Now there is no more green icon on both Android devices and can no longer send and receive messages.
Note:
The Wi-Fi Direct connection was not disconnected. Same problem also with Bluetooth.
Can you reproduce it?https://code.briarproject.org/briar/briar/-/issues/1766Possibility to add local chat without external contacts2020-11-15T14:29:25ZN6P4CFB1BSRSLPossibility to add local chat without external contacts**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
There is no way to start a local chat under "Contacts" without adding external contacts.
Private Groups, Forums and Blogs have this possibility. But I prefer to...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
There is no way to start a local chat under "Contacts" without adding external contacts.
Private Groups, Forums and Blogs have this possibility. But I prefer to start a local chat under "Contacts" because the UI looks nicer and I want to test how the Chat UI is in general.https://code.briarproject.org/briar/briar/-/issues/1767Improves animation and design2020-09-05T10:15:34ZN6P4CFB1BSRSLImproves animation and design**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
When select a contact and tap the "Back" button. The animatiom does not look even, does not look clean and is illogical. Additionally there are some design probl...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
When select a contact and tap the "Back" button. The animatiom does not look even, does not look clean and is illogical. Additionally there are some design problems (circle symbol).
**Steps to reproduce**
1. Open the Briar app and enter the password.
2. The main view is "Contacts". Tap on a contact and tap on the "Back" button in the upper left corner.
3. The animatiom does not look even, does not look clean and is illogical.
Note:
Why illogical? The contact is not online and on the main view it shows the online status for this contact with a circle symbol, in this case white color in the middle of the circle symbol and the border is grey. I use Light theme.
When I tap on contact it shows in the title bar a grey circle symbol with white border. Now when I tap on the "Back" button the animation appears and the circle symbol of title bar returns to the main view, but as I said before the color of the circle symbol in title bar and main view are different.https://code.briarproject.org/briar/briar/-/issues/1768Declined introduction cannot be sent again immediately2020-11-15T14:26:46ZN6P4CFB1BSRSLDeclined introduction cannot be sent again immediately**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
If an introduction is accidentally declined there is no quick and easy way to undo it and accept a resend of the introduction.
Generally whether accidentally de...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
If an introduction is accidentally declined there is no quick and easy way to undo it and accept a resend of the introduction.
Generally whether accidentally declined or really declined. The messages generated by this introduction function cannot be deleted immediately and the user does not know when it is possible to make introduction again for the same contact.