briar issueshttps://code.briarproject.org/briar/briar/-/issues2020-11-15T18:54:25Zhttps://code.briarproject.org/briar/briar/-/issues/1539Retrieving the onion address of a specific contact2020-11-15T18:54:25ZalexRetrieving the onion address of a specific contactHello;
This is more a question than an issue, and it will help many others develop this app.
I was looking for very long hours, for the onion address of the target contact when sending a message.
I followed the 'createMessage()' method ...Hello;
This is more a question than an issue, and it will help many others develop this app.
I was looking for very long hours, for the onion address of the target contact when sending a message.
I followed the 'createMessage()' method and it's usage/declaration but found no clue .
I/WE will be very grateful if you show us the location of these onion addresses to where the packets are sent to;
and how to retrieve them.
Thank you for your time , and again, this is gonna help us develop new features and finally commit them.https://code.briarproject.org/briar/briar/-/issues/1535Tryin to import SharedPreferences into AccountManagerImpl2019-04-19T14:54:16ZnicedeveloperTryin to import SharedPreferences into AccountManagerImplTryin to import SharedPreferences into AccountManagerImpl in package package org.briarproject.bramble.account;
SharedPreferences highlights RedTryin to import SharedPreferences into AccountManagerImpl in package package org.briarproject.bramble.account;
SharedPreferences highlights Redhttps://code.briarproject.org/briar/briar/-/issues/1533support Netguard2020-11-15T18:55:42Zbillfromisletasupport NetguardIssue #1284 and #1400 make it clear that users have trouble trusting whether Briar is not leaking on the clearnet. It raises some questions:
* what happens if Orbot is not installed?
* how does Briar work if Tor is enabled and also Net...Issue #1284 and #1400 make it clear that users have trouble trusting whether Briar is not leaking on the clearnet. It raises some questions:
* what happens if Orbot is not installed?
* how does Briar work if Tor is enabled and also Netguard is using transparent proxying to force Briar packets over Tor? On a desktop system, such a scenario would break because the app would be trying to connect to 127.0.0.1:9050 on the WAN. But on Android it functions, which seems to imply that Netguard is being bypassed.
Netguard's *lockdown mode* does not work on Briar apparently because Netguard is being bypassed. If Briar supported a non-Tor configuration, then users could use Netguard to force it over Tor and automatically have more confidence that there are likely no leaks. Although I don't know if netguard and orbot can handle whatever onion addressing Briar uses.https://code.briarproject.org/briar/briar/-/issues/1531Update threat model document2020-11-15T18:57:13ZakwizgranUpdate threat model documentThe [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.The [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1530images doesn't get sent even after changing 'hasSupport' to true2019-04-10T13:58:50Zaleximages doesn't get sent even after changing 'hasSupport' to trueWhen attempting to send an image, an overlay comes with
> "Images unavailable" "Your contact's Briar does not yet support image attachments. Once they upgrade you'll see a different icon."
Then, I changed the constant `FEATURE_FLAG_IM...When attempting to send an image, an overlay comes with
> "Images unavailable" "Your contact's Briar does not yet support image attachments. Once they upgrade you'll see a different icon."
Then, I changed the constant `FEATURE_FLAG_IMAGE_ATTACHMENTS` to `TRUE` in TestingConstants.java
With no luck, So I changed the following code -> (in android/conversation/conversationActivity.java - Line 267)
```
observeOnce(viewModel.hasImageSupport(), this, hasSupport -> {
if (hasSupport != null && hasSupport) {
// remove cast when removing FEATURE_FLAG_IMAGE_ATTACHMENTS
((TextAttachmentController) sendController)
.setImagesSupported();
}
});
```
to
```
((TextAttachmentController) sendController).setImagesSupported();
```
also, as another attempt with the same manner, I left the code as is but I changed the value of `hasSupport=true` manually ;
After that , whenever sending an image, nothing goes and only 'null' is sent.
knowing that the same version of the build is used in both android devises.
Is it a bug ? or i am lacking something important ?
in both cases i'd love hearing from you.
By the way, thank you for this great application !https://code.briarproject.org/briar/briar/-/issues/1527Expiry message for debug builds is out of date2021-04-15T11:43:36ZDanielExpiry message for debug builds is out of dateWhen I am running the app it says I should download the updated version how to fix this thy.When I am running the app it says I should download the updated version how to fix this thy.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1524DeadSystemException2022-07-13T14:58:33ZakwizgranDeadSystemException* Android version: 8.1.0
* Briar version: "N/A" (perhaps the package manager is unavailable?)
* Phone model: Motorola Moto G4 Plus (lineage_athene)
Stacktrace:
```
android.os.DeadSystemException
at android.os.PowerManager$WakeLo...* Android version: 8.1.0
* Briar version: "N/A" (perhaps the package manager is unavailable?)
* Phone model: Motorola Moto G4 Plus (lineage_athene)
Stacktrace:
```
android.os.DeadSystemException
at android.os.PowerManager$WakeLock.release(PowerManager.java:1463)
at android.os.PowerManager$WakeLock$1.run(PowerManager.java:1328)
at android.os.Handler.handleCallback(Handler.java:790)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
```
[Docs](https://developer.android.com/reference/android/os/DeadSystemException.html) for this exception:
> The core Android system has died and is going through a runtime restart. All running apps will be promptly killed.
[This thread](https://groups.google.com/forum/#!topic/android-platform/VVHA6-eRB3c) explains that a runtime restart is a form of soft reboot.
Doesn't look like there's anything we can do here. Creating this ticket for documentation only.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/1521Cannot resolve symbol R after build2020-11-15T19:06:59ZnicedeveloperCannot resolve symbol R after buildI'm also encountering "can not resolve symbol R" error
import org.briarproject.briar.R; , where R is in redI'm also encountering "can not resolve symbol R" error
import org.briarproject.briar.R; , where R is in redhttps://code.briarproject.org/briar/briar/-/issues/1520Stale scroll position is restored after opening blog post2020-11-15T19:08:03ZakwizgranStale scroll position is restored after opening blog postSteps to reproduce:
* Ensure the blog feed has at least a screenful of posts
* Scroll down a few posts
* Rotate the screen to landscape and back to portrait
* The scroll position is remembered, as expected
* Scroll down a few more posts
...Steps to reproduce:
* Ensure the blog feed has at least a screenful of posts
* Scroll down a few posts
* Rotate the screen to landscape and back to portrait
* The scroll position is remembered, as expected
* Scroll down a few more posts
* Tap on a post to open it
* Use the back button to return to the feed
* The scroll position jumps back to where it was when the screen was rotatedhttps://code.briarproject.org/briar/briar/-/issues/1519Password entry and confirmation fields should have descriptions2020-11-15T19:09:36ZakwizgranPassword entry and confirmation fields should have descriptionsGoogle Play's pre-launch report warns that the password entry and confirmation fields should have descriptions for screen reader accessibility.
https://support.google.com/accessibility/android/answer/7158690
This may apply to other fie...Google Play's pre-launch report warns that the password entry and confirmation fields should have descriptions for screen reader accessibility.
https://support.google.com/accessibility/android/answer/7158690
This may apply to other fields in the app, but the automated tests don't yet get past the setup screen.https://code.briarproject.org/briar/briar/-/issues/1518Touch target for screen filter checkbox is too small2020-11-15T19:10:24ZakwizgranTouch target for screen filter checkbox is too smallGoogle Play's pre-launch report warns that the screen filter checkbox should be at least 48dp high for accessibility. The current size varies from 32 to 36dp depending on the device.
The same may be true of other checkboxes, but the aut...Google Play's pre-launch report warns that the screen filter checkbox should be at least 48dp high for accessibility. The current size varies from 32 to 36dp depending on the device.
The same may be true of other checkboxes, but the automated testing doesn't go past the setup screen yet (I'm working on a script to allow it to do so).https://code.briarproject.org/briar/briar/-/issues/1515No dependency for integrity assertion 'com.android.tools.analytics-library:pr...2019-08-14T14:22:52ZnicedeveloperNo dependency for integrity assertion 'com.android.tools.analytics-library:protos:26.2.1:protosi 've got android studio 3.3.2
and receiving an error No dependency for integrity assertion 'com.android.tools.analytics-library:protos:26.2.1:protos-26.2.1.jar:2f371f5b1f551e85ab08be4d6a2873471b3d44afd1ebf6aa3298f3b796bf691f'
everyth...i 've got android studio 3.3.2
and receiving an error No dependency for integrity assertion 'com.android.tools.analytics-library:protos:26.2.1:protos-26.2.1.jar:2f371f5b1f551e85ab08be4d6a2873471b3d44afd1ebf6aa3298f3b796bf691f'
everything is uptodate including SDK Tools, SDK Platforms and SDK Update Sites
What is wrong ? I've searched the Internet, couldn't find anythinghttps://code.briarproject.org/briar/briar/-/issues/1513Bluetooth dialog needs to be dismissed multiple times after rotating screen2020-11-15T19:12:00ZakwizgranBluetooth dialog needs to be dismissed multiple times after rotating screenSteps to reproduce:
* Start to add a nearby contact
* When the Bluetooth permission dialog is visible, rotate the screen
* Dismiss the dialog
* Expected: The dialog only needs to be dismissed once
* Actual: The dialog needs to be dismiss...Steps to reproduce:
* Start to add a nearby contact
* When the Bluetooth permission dialog is visible, rotate the screen
* Dismiss the dialog
* Expected: The dialog only needs to be dismissed once
* Actual: The dialog needs to be dismissed once, plus once for every time the screen was rotated
Test devices:
* Sony Xperia Tipo (Android 4.0.4)
* Motorola Moto E3 (Android 6.0)https://code.briarproject.org/briar/briar/-/issues/1511Settings to increase polling time2021-12-13T14:13:45ZDmitry RubtsovSettings to increase polling timeSince Briar takes a lot of battery power (up to 20% of my Galaxy Note 9), I want to customize update frequency for incoming messages. I think, that it is easy and usefulSince Briar takes a lot of battery power (up to 20% of my Galaxy Note 9), I want to customize update frequency for incoming messages. I think, that it is easy and usefulhttps://code.briarproject.org/briar/briar/-/issues/1505API 28: Show Soft Keyboard When Activities no longer receive focus2020-02-14T10:34:52ZTorsten GroteAPI 28: Show Soft Keyboard When Activities no longer receive focushttps://developer.android.com/about/versions/pie/android-9.0-changes-28#focus
> Additionally, activities no longer implicitly assign initial focus in touch-mode. Instead, it is up to you to explicitly request initial focus, if desired.
...https://developer.android.com/about/versions/pie/android-9.0-changes-28#focus
> Additionally, activities no longer implicitly assign initial focus in touch-mode. Instead, it is up to you to explicitly request initial focus, if desired.
When entering the password, creating groups, forums or writing blog posts, the keyboard is shown initially, because the input fields receive focus. On API 28, we can't rely on this anymore and should use explicit keyboard states instead.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1504Nokia's power management app kills Briar2019-04-25T09:31:44ZakwizgranNokia's power management app kills BriarNokia phones running Android 8+ have a power management app with the package name com.evenwell.powersaving.g3 or com.evenwell.emm that kills all background apps 20 minutes after the screen turns off, prevents alarms from firing, and prev...Nokia phones running Android 8+ have a power management app with the package name com.evenwell.powersaving.g3 or com.evenwell.emm that kills all background apps 20 minutes after the screen turns off, prevents alarms from firing, and prevents background apps from starting foreground services. Doze whitelisting doesn't help.
https://code.briarproject.org/briar/briar/issues/992#note_33135
https://code.briarproject.org/briar/briar/issues/992#note_34764
https://dontkillmyapp.com/nokia
The only known workaround for users without ADB is to force close the power saving app. Presumably this needs to be done after every boot.
We can detect whether the device is affected by this issue by looking at the list of installed packages (and maybe the manufacturer and Android version), but we can't prevent the issue from happening. Perhaps we should show a warning that Briar won't work properly on this device?
Related to #992.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1503Apk sharing while offline2019-02-19T09:00:38ZMarcus HowserApk sharing while offlineUser here, I have come across a Bluetooth chat app that has the ability to share its apk to other people without an internet connection.
Github: https://github.com/glodanif/BluetoothChat
Playstore: https://play.google.com/store/apps/det...User here, I have come across a Bluetooth chat app that has the ability to share its apk to other people without an internet connection.
Github: https://github.com/glodanif/BluetoothChat
Playstore: https://play.google.com/store/apps/details?id=com.glodanif.bluetoothchat
It would be quite helpful if Briar had this functionality for users out in the field with no internet access.https://code.briarproject.org/briar/briar/-/issues/1502Restart obfs4proxy if it crashes2023-03-15T12:55:10ZakwizgranRestart obfs4proxy if it crashesIf the obfs4proxy process is killed (e.g. due to low memory), Tor detects that it's died but doesn't restart it. Setting `DisableNetwork` to 1 and then back to 0 causes Tor to restart obfs4proxy.
Log message from Tor when obfs4proxy die...If the obfs4proxy process is killed (e.g. due to low memory), Tor detects that it's died but doesn't restart it. Setting `DisableNetwork` to 1 and then back to 0 causes Tor to restart obfs4proxy.
Log message from Tor when obfs4proxy dies:
```
TorPlugin: WARN The connection to the SOCKS5 proxy server at 127.0.0.1:42125 just failed. Make sure that the proxy server is up and running.
```https://code.briarproject.org/briar/briar/-/issues/1497Check whether ongoing notification's priority and importance need to be incre...2019-02-21T12:41:39ZakwizgranCheck whether ongoing notification's priority and importance need to be increasedThis blog post describes some "guidelines" for a foreground service's ongoing notification:
https://android-developers.googleblog.com/2018/12/effective-foreground-services-on-android_11.html
> There are some guidelines around creating ...This blog post describes some "guidelines" for a foreground service's ongoing notification:
https://android-developers.googleblog.com/2018/12/effective-foreground-services-on-android_11.html
> There are some guidelines around creating and managing foreground services. For all API levels, a persistent notification with at least PRIORITY_LOW must be shown while the service is created. When targeting API 26+ you will also need to set the notification channel to at least IMPORTANCE_LOW.
Our ongoing notification uses PRIORITY_MIN and the channel uses IMPORTANCE_NONE. Find out whether this affects how the system treats our foreground service, especially on API 26+.
Related to #1146. Subtask of #1260.Torsten GroteTorsten Grote