briar issueshttps://code.briarproject.org/groups/briar/-/issues2018-06-12T11:32:37Zhttps://code.briarproject.org/briar/briar/-/issues/136Release Bramble as a separate library2018-06-12T11:32:37ZakwizgranRelease Bramble as a separate librarySeparate the Bramble protocol stack from the Briar app so that it can be released as a separate library usable by other projects.Separate the Bramble protocol stack from the Briar app so that it can be released as a separate library usable by other projects.Milestone Fakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/894Remember list position and restore it2017-12-18T07:40:22ZTorsten GroteRemember list position and restore itOne of the testers moved a conversation from a forum discussion (that was supposed to be for more people) to a private conversation, because "forums are hard to read". When asked for more details and he said that you have to scroll down ...One of the testers moved a conversation from a forum discussion (that was supposed to be for more people) to a private conversation, because "forums are hard to read". When asked for more details and he said that you have to scroll down every time to the last message, so you have to real all the thread again and again like in a non-quoted email thread.
He said that it would help immensely, if Briar would remember the last message you had read and show it again when you re-enter the forum.
So this ticket is about remembering the list position and then restoring it when the screen is rotated or the user re-enters the list.
There are several list positions we could restore depending on which list is concerned:
* just the last known scrolling position before the list was left
* the position of the message that was marked as read last
* the position of the message that was marked as read first when the conversation was enteredAndroid Beta 1https://code.briarproject.org/briar/briar/-/issues/47Remind the user to sign in2018-08-06T09:38:28ZakwizgranRemind the user to sign inUsers may forget that they need to sign in to be notified of new messages. We can run a small service at startup that reminds the user to sign in after a certain amount of time has elapsed - maybe a day, then a week, then a month. Touchi...Users may forget that they need to sign in to be notified of new messages. We can run a small service at startup that reminds the user to sign in after a certain amount of time has elapsed - maybe a day, then a week, then a month. Touching the notification should launch the app.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2311Remind user to wipe mailbox if it's unreachable when unpairing2022-05-02T16:06:29ZakwizgranRemind user to wipe mailbox if it's unreachable when unpairingIf we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.If we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.Mailbox: UnpairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1583Remote contact layout is too tall for small screens2019-09-27T14:58:54ZakwizgranRemote contact layout is too tall for small screensThe layouts for LinkExchangeFragment and NicknameFragment don't work well on small screens: for LinkExchangeFragment the Continue button is mostly offscreen, and for NicknameFragment the nickname field and Add Contact button are entirely...The layouts for LinkExchangeFragment and NicknameFragment don't work well on small screens: for LinkExchangeFragment the Continue button is mostly offscreen, and for NicknameFragment the nickname field and Add Contact button are entirely offscreen, making it unclear what the user's meant to do next.
Screenshots come from the Huawei Ascend Y330 (480x800 px).
![device-2019-06-08-101532](/uploads/83053a95ddee99302b91b0b79c659113/device-2019-06-08-101532.png)
![device-2019-06-08-101545](/uploads/33ff8c3896463d1be367479d956b781b/device-2019-06-08-101545.png)
Possible workarounds:
* Scroll to the bottom of each fragment when it's opened
* Remove the illustration from NicknameActivity or make it smaller
* Move the stepper to the bottom, below the button (I know we decided it was better at the top, and apart from this issue I'd prefer to keep it there)
* Divide the workflow into three steps rather than two: send link, enter link, and enter nickname (this has disadvantages for the flows where the user opens the activity by sharing a link from another app, or with a link already in the clipboard)Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/155Remote wiping when Mailbox screen asleep => Wiping Complete screen presents t...2023-01-19T13:07:59ZIvanaRemote wiping when Mailbox screen asleep => Wiping Complete screen presents twice**Steps to reproduce**
Briar device: Samsung A01S Core, Android 10
Mailbox device: Motorola E2, Android 6
do not keep activities = On for both devices, but results are the same iwth do not keep activities = OFF on mailbox
- when Briar...**Steps to reproduce**
Briar device: Samsung A01S Core, Android 10
Mailbox device: Motorola E2, Android 6
do not keep activities = On for both devices, but results are the same iwth do not keep activities = OFF on mailbox
- when Briar and Mailbox are connected, wait for the Mailbox device screen to be askeep (ie to turn black)
- then tap Unlink on Briar side
- When the process finishes, and the Briar settings screen presents again, tap the Mailbox device screen to activate it
**Expected results:**
- Wiping complete screen presents on mailbox device.
- On taping the Finish button, the mailbox exits.
**Actual results**
- Wiping complete screen does present, but when the user taps the Finish button, instead of the mailbox app exiting, the same screen presents again, via a couple of other briefly visible screens. See video attached.
- The video screen is black initially because I started recording via Android Studio when I tapped Unlink on the Briar screen. The mailbox device screen was asleep at that time, and when the wiping finishes on Briar side, I tap the mailbox device to reactivate that screen...
![device-2022-08-09-124536](/uploads/2ad5c1e1aaf6460ddb4554b62e27ad94/device-2022-08-09-124536.mp4)https://code.briarproject.org/briar/briar/-/issues/1471remotely added contacts: cannot send messages2018-11-24T07:32:10ZWikinautremotely added contacts: cannot send messagesI installed the Briar Test apk on two devices (Huawei P8 Lite and Y6) and added the contacts remotely (by exchanging the keys manually using "Zxing Barcode Scanner" app). Both contacts show "green" light. but no messages can be sent.
A...I installed the Briar Test apk on two devices (Huawei P8 Lite and Y6) and added the contacts remotely (by exchanging the keys manually using "Zxing Barcode Scanner" app). Both contacts show "green" light. but no messages can be sent.
After closing and restarting the Briar Test Apps, the contacts are not even marked "green" any more.https://code.briarproject.org/briar/briar/-/issues/1630Remove anonymous author status2022-09-06T09:56:47ZakwizgranRemove anonymous author statusRemove the obsolete AuthorInfo.Status.ANONYMOUS constant and the corresponding drawable for the trust indicator.Remove the obsolete AuthorInfo.Status.ANONYMOUS constant and the corresponding drawable for the trust indicator.Android 1.4https://code.briarproject.org/briar/briar/-/issues/293Remove avatar code and layout from ConversationActivity and ConversationAdapter2018-06-12T11:32:31ZakwizgranRemove avatar code and layout from ConversationActivity and ConversationAdapterThis code is currently unused, remove it if we're definitely not going to use it.This code is currently unused, remove it if we're definitely not going to use it.Milestone CTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/317Remove binaries from git history2022-01-21T09:59:52ZakwizgranRemove binaries from git historyThe git repo is huge. Rewrite the commit history to remove unnecessary binaries (fonts, android.jar, etc).
We could also remove the Tor binaries and any jars that have been converted to Gradle dependencies, but that would make it imposs...The git repo is huge. Rewrite the commit history to remove unnecessary binaries (fonts, android.jar, etc).
We could also remove the Tor binaries and any jars that have been converted to Gradle dependencies, but that would make it impossible to build old commits that used those binaries.https://code.briarproject.org/briar/briar/-/issues/1861Remove calls to WifiManager#getConfiguredNetworks()2021-01-06T12:31:58ZakwizgranRemove calls to WifiManager#getConfiguredNetworks()AndroidSecureRandomProvider calls WifiManager#getConfiguredNetworks() at startup. This call requires ACCESS_FINE_LOCATION on API 30. Remove this call, and any other calls to this method.
Subtask of #1827.AndroidSecureRandomProvider calls WifiManager#getConfiguredNetworks() at startup. This call requires ACCESS_FINE_LOCATION on API 30. Remove this call, and any other calls to this method.
Subtask of #1827.Adapt to changes in the Android platformTorsten GroteTorsten Grote2021-04-30https://code.briarproject.org/briar/briar/-/issues/234Remove consumers from BdfWriter2018-06-12T11:32:33ZakwizgranRemove consumers from BdfWriterMilestone Bakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/449Remove Contact FAB button and use header instead2018-06-12T11:32:25ZErnir ErlingssonRemove Contact FAB button and use header insteadI feel this was decided ages ago but it somehow fell through the cracks. Is there anything blocking this ? Did Akwizgran want to keep it ? I feel this was decided ages ago but it somehow fell through the cracks. Is there anything blocking this ? Did Akwizgran want to keep it ? Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/2071Remove ContactIds from RemovableDriveManager's task management2021-07-06T09:41:47ZTorsten GroteRemove ContactIds from RemovableDriveManager's task managementRemove `ContactId`s from `RemovableDriveManager`'s task management, so we just have one writer and one reader task globally.
* For writer tasks we'll still need to pass a `ContactId` when creating the task, but not when checking for an ...Remove `ContactId`s from `RemovableDriveManager`'s task management, so we just have one writer and one reader task globally.
* For writer tasks we'll still need to pass a `ContactId` when creating the task, but not when checking for an existing task.
* For reader tasks, we don't provide any progress information. We can just remove the progress monitoring stuff from the reader task, and have it post a single progress update when it's complete (success or error).Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/601Remove content type from forum posts2018-06-12T11:32:20ZakwizgranRemove content type from forum postsThe content type field is unused and we don't yet have a plan for when it will be used. Remove it until it's needed.The content type field is unused and we don't yet have a plan for when it will be used. Remove it until it's needed.https://code.briarproject.org/briar/briar/-/issues/600Remove content type from private messages2018-06-12T11:32:20ZakwizgranRemove content type from private messagesThe content type field is unused and we don't yet have a plan for when it will be used. Remove it until it's needed.The content type field is unused and we don't yet have a plan for when it will be used. Remove it until it's needed.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-desktop/-/issues/193Remove conversation menu items that do not work yet2022-01-12T11:36:06ZSebastianRemove conversation menu items that do not work yet* self-destructing messages
* Connections submenu
* rename contact (unless we move #158 into the 0.1.0 milestone)* self-destructing messages
* Connections submenu
* rename contact (unless we move #158 into the 0.1.0 milestone)Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/492Remove crash report settings2018-06-12T11:32:24ZakwizgranRemove crash report settingsMost users should never see the crash reporter, so we don't need to allow them to configure it.Most users should never see the crash reporter, so we don't need to allow them to configure it.Milestone CTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/180Remove DatabaseCleaner and message expiry logic2018-06-12T11:32:35ZakwizgranRemove DatabaseCleaner and message expiry logicRemove the old message expiry code. Leave the infrastructure for measuring free disk space intact, we'll need it later.
Subtask of #112.Remove the old message expiry code. Leave the infrastructure for measuring free disk space intact, we'll need it later.
Subtask of #112.Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/757Remove DeviceId code2017-12-18T07:40:36ZakwizgranRemove DeviceId codeThe DeviceId is a leftover from an early attempt to add multi-device support. Remove it as part of the Grand Refactoring of #136.The DeviceId is a leftover from an early attempt to add multi-device support. Remove it as part of the Grand Refactoring of #136.Milestone FTorsten GroteTorsten Grote