briar issueshttps://code.briarproject.org/briar/briar/-/issues2022-06-06T13:28:06Zhttps://code.briarproject.org/briar/briar/-/issues/1687Check whether workaround for Tor bug #28027 is still needed2022-06-06T13:28:06ZakwizgranCheck whether workaround for Tor bug #28027 is still neededThe Tor plugin contains a workaround for Tor bug #28027. The fix for that ticket's parent was backported to the 0.3.5 series, so the workaround may not be needed any more. Test whether it's still needed and remove if not.
https://trac.t...The Tor plugin contains a workaround for Tor bug #28027. The fix for that ticket's parent was backported to the 0.3.5 series, so the workaround may not be needed any more. Test whether it's still needed and remove if not.
https://trac.torproject.org/projects/tor/ticket/28027
https://trac.torproject.org/projects/tor/ticket/29875https://code.briarproject.org/briar/briar/-/issues/1682No obvious way to tell which version of briar I am running2020-01-08T17:26:40Zcano wigNo obvious way to tell which version of briar I am runningI tried digging everywhere but I couldn't find which version of briar I am running from the app. I could see it only through f-droid. Every app has an obvious way to see which version you run, usually in the 'about' page. I suggest to ad...I tried digging everywhere but I couldn't find which version of briar I am running from the app. I could see it only through f-droid. Every app has an obvious way to see which version you run, usually in the 'about' page. I suggest to add the version number to briar next to the logo and BRIAR.
So by clicking on the 3 lines you open the side bar, see the logo, BRIAR and version.
Example: Logo BRIAR 1.2.4https://code.briarproject.org/briar/briar/-/issues/1681Bug when signing in to briar2019-12-21T18:12:50ZjomocuBug when signing in to briarBriar version: 1.2.4
Once the session has started, the application does not allow creating new forums, new blogs, and new groups.
Bug solutions:
- Turning the screen resolves the error.
- Pressing on configuration and going back to sol...Briar version: 1.2.4
Once the session has started, the application does not allow creating new forums, new blogs, and new groups.
Bug solutions:
- Turning the screen resolves the error.
- Pressing on configuration and going back to solve the error.
- When closing and opening the application without logging in, the error is also solved.https://code.briarproject.org/briar/briar/-/issues/1679Ephemeral messages and self cleaning2019-12-20T20:08:39ZjomocuEphemeral messages and self cleaningIt would be good to add an option to be able to automatically delete the messages of a particular converacion every x time.
This function would delete the messages every x time for all the participants of the conversation.
The function s...It would be good to add an option to be able to automatically delete the messages of a particular converacion every x time.
This function would delete the messages every x time for all the participants of the conversation.
The function should be available in private conversations and in groups.
On the other hand, in the general configuration of the application, a self-cleaning option could be added, in order to automatically erase the contents of the oldest chats.
And add some extra options, such as these:
** Cleaning of messages for recipients **
- "Delete messages for the receiver" (True / False)
** Cleaning filters **
- "Do not self-delete Files" (True / False)
- "Do not self-delete Videos" (True / False)
- "Do not self-delete Images" (True / False)
- "Do not self-remove Sounds" (True / False)
- "Do not self-remove Gifs" (True / False)
- "Do not self-remove Audios" (True / False)
- "Do not self-delete Video Messages" (True / False)
- "Do not self-delete Links (URL)" (True / False)
I hope you like the suggestion, regardshttps://code.briarproject.org/briar/briar/-/issues/1677Headless: alias missing from contacts response when same as author's name2020-10-31T12:52:40ZNicoHeadless: alias missing from contacts response when same as author's nameIn [headless' readme](https://code.briarproject.org/briar/briar/blob/6a31274b76781d540e3a2875160dd352a48a8335/briar-headless/README.md#listing-all-contacts) an example of a response is shown that contains the key `alias`. When `alias` is...In [headless' readme](https://code.briarproject.org/briar/briar/blob/6a31274b76781d540e3a2875160dd352a48a8335/briar-headless/README.md#listing-all-contacts) an example of a response is shown that contains the key `alias`. When `alias` is the same as `author->name`, Briar headless leaves out the `alias` key and only answers with `author->name`.
### Steps to reproduce
Add a contact remotely and give it an alias equal to the contact's self chosen nickname.
### Excepted behavior
Both @fphemeral and I thought that the response would always contain an alias. At least when the user gives the contact an alias.
### Actual behavior
If `alias` matches `author->name`, `alias` is dropped from the response.
### Proposed solution
Either explicitly state in the documentation that the `alias` key is not guaranteed to get delivered all the time, or change the output to always contain an `alias` key.
### Related resources
* [the commit where I added a check for this](https://code.briarproject.org/nicoalt/briar-gtk/commit/4d1acc7c4c278ece5cb4e920a38d9910d70b5b95) in Briar GTK
* [my proposed merge request](https://code.briarproject.org/fphemeral/briar_repl/merge_requests/1) at _briar_repl_NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1669Request to send images2019-11-20T09:50:50ZfwholdRequest to send imagesCongratulations! Fantastic project! When will you be able to send the images? Is this update planned?
* [ ] Congratulations! Fantastic project! When will you be able to send the images? Is this update planned?
* [ ] https://code.briarproject.org/briar/briar/-/issues/1668Keyboard opens when returning from Huawei protected apps screen2021-08-27T11:31:33ZakwizgranKeyboard opens when returning from Huawei protected apps screenWhen creating an account on the Huawei Ascend Y330, the soft keyboard opens when returning from the Huawei protected apps screen to the DozeFragment.
Probably a bug I introduced in !1043.When creating an account on the Huawei Ascend Y330, the soft keyboard opens when returning from the Huawei protected apps screen to the DozeFragment.
Probably a bug I introduced in !1043.Android 1.3akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1667Create group/create forum/write blog post button sometimes not showing2021-03-01T16:35:34ZakwizgranCreate group/create forum/write blog post button sometimes not showing* Android version: 4.2.2
* Phone model: Huawei Ascend Y330
* Briar version: 1.2.4 (ae0fa35)
The plus button in the toolbar of the private group and forum lists sometimes isn't shown. I can reproduce this on the Y330 by going straight to...* Android version: 4.2.2
* Phone model: Huawei Ascend Y330
* Briar version: 1.2.4 (ae0fa35)
The plus button in the toolbar of the private group and forum lists sometimes isn't shown. I can reproduce this on the Y330 by going straight to the group/forum list after signing in. After turning the screen off and on, the button appears.
![device-2019-11-14-144506](/uploads/e8509869bc226c46604f4bac8c6da4cb/device-2019-11-14-144506.png) ![device-2019-11-14-144520](/uploads/528b3c43f9381495b5e370af565edb3a/device-2019-11-14-144520.png)Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1666F-droid version is outdated (please, keep it up to date)2019-11-14T15:28:31ZtuquequeF-droid version is outdated (please, keep it up to date)Hello. I don't know if this can be called an "issue", but to me it is. I want to try the new version of Briar and I haven't been able to because the F-droid version of Briar is still in the 1.1.6. I've waited several days, but no sign of...Hello. I don't know if this can be called an "issue", but to me it is. I want to try the new version of Briar and I haven't been able to because the F-droid version of Briar is still in the 1.1.6. I've waited several days, but no sign of new version. It's a bit frustrating/disappointing having to write here for such a thing, but I made a comment on your Twitter account also several days ago and no response yet.
Thank you for your time and investment on this great app. Just try to keep it up to date on all stores.https://code.briarproject.org/briar/briar/-/issues/1665Crash when deleting introduction message2020-03-24T17:35:17ZakwizgranCrash when deleting introduction message* Android version: 8.0.0
* Phone model: Sony F5321
* Briar version: 1.2.4 (debug build, no commit hash)
* User feedback: "Delete introduction message crash Briar."
Stacktrace:
```
java.lang.IllegalStateException: Range start point not s...* Android version: 8.0.0
* Phone model: Sony F5321
* Briar version: 1.2.4 (debug build, no commit hash)
* User feedback: "Delete introduction message crash Briar."
Stacktrace:
```
java.lang.IllegalStateException: Range start point not set.
at androidx.core.util.Preconditions.checkState(Preconditions.java:96)
at androidx.recyclerview.selection.DefaultSelectionTracker.extendProvisionalRange(DefaultSelectionTracker.java:281)
at androidx.recyclerview.selection.GestureSelectionHelper.extendSelection(GestureSelectionHelper.java:227)
at androidx.recyclerview.selection.GestureSelectionHelper.handleMoveEvent(GestureSelectionHelper.java:204)
at androidx.recyclerview.selection.GestureSelectionHelper.handleTouch(GestureSelectionHelper.java:151)
at androidx.recyclerview.selection.GestureSelectionHelper.onInterceptTouchEvent(GestureSelectionHelper.java:118)
at androidx.recyclerview.selection.TouchEventRouter.onInterceptTouchEvent(TouchEventRouter.java:91)
at androidx.recyclerview.widget.RecyclerView.findInterceptingOnItemTouchListener(RecyclerView.java:3149)
at androidx.recyclerview.widget.RecyclerView.dispatchToOnItemTouchListeners(RecyclerView.java:3120)
at androidx.recyclerview.widget.RecyclerView.onTouchEvent(RecyclerView.java:3281)
at android.view.View.dispatchTouchEvent(View.java:11731)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2955)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2636)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2961)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:453)
at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1828)
at android.app.Activity.dispatchTouchEvent(Activity.java:3292)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)
at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:415)
at android.view.View.dispatchPointerEvent(View.java:11970)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4790)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4604)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4142)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4195)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4161)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4288)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4169)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4345)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4142)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4195)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4161)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4169)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4142)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:6663)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:6637)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:6598)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:6766)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:186)
at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:177)
at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:6737)
at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:6789)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:966)
at android.view.Choreographer.doCallbacks(Choreographer.java:778)
at android.view.Choreographer.doFrame(Choreographer.java:707)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:952)
at android.os.Handler.handleCallback(Handler.java:789)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:251)
at android.app.ActivityThread.main(ActivityThread.java:6589)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
```Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1663Android 11 Scoped Storage - Android future completely Google dependent (centr...2019-11-13T10:13:34ZGhost UserAndroid 11 Scoped Storage - Android future completely Google dependent (centralization)I read some details (Scoped Storage) about what should come in Android Q (Android 10), but was aborted first and will be introduced with Android 11.
Why Google lies to the users and what the honest developers have to say about it and ha...I read some details (Scoped Storage) about what should come in Android Q (Android 10), but was aborted first and will be introduced with Android 11.
Why Google lies to the users and what the honest developers have to say about it and have recognized it correctly.
https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/
> Google touts the security and privacy benefits of this change, but technically speaking, there is no improvement. Apps have had the ability to privately store files since Android 1.0, and almost all apps make use of this capability. When you grant an app access to the root directory of your storage via SAF, it can read, write, and send any file it wants to its nefarious developer in the exact same fashion it could when you granted an app access to storage in Pie.
> The only “security improvement” comes about because it’s now a more arduous process for a user to do this. Unless of course an app only wants to steal your most personal information, like photos and videos you’ve taken, for which Google has added an alternative access solution which uses a simple pop-up click-yes security dialog.
> It is not known what benefits Google hopes to achieve with this change. The official stated reason in the Android Q beta documentation is to “give users more control over their files and to limit file clutter.” Scoped storage, in its present form, is a new limitation of what the user is allowed to do, not an extension of their control. The claim of reducing clutter may be somewhat valid, but only because the change reduces the ability to use files at all. And “clutter” is increased when you consider the problem of some apps now having to duplicate files to work with them.
> If Google is truly concerned about giving users more control over files and clutter, they should architect a solution that directly addresses that, rather than falsely branding the current Android Q design as such an improvement. The simplest answer would be to let users decide if they want an app to have scoped or general filesystem access, using the extant storage permission request dialog. If there is a particular concern for users making poor decisions here, it’s certainly possible to make that dialog more prominent and require additional user interaction to approve an app for full access.
> The answer to how Android can give users more control of their files is to actually give users more control, not to take it away and fundamentally constrain the capabilities of the Android platform.
What do we see here?
The developers knew exactly how to really improve it for the users and the added value behind it.
Why does Google lie and want to include it in Android Q even though it's not an improvement? Google wants to limit Android even further, just like Apple does with their iOS system and products that use this system e.g. iPhone.
Google is pursuing the same goals as Apple and Microsoft in the final stages. Building a centralized system. No more control by users or developers, only server dependent.
The problem that most Android or Linux developers have known about for a long time and therefore do not develop apps for centralized systems. But the consumers don't know it yet or don't see the interrelations and that's a problem.
Since Google is able to integrate it into Android 11, they will try again and again in the future to make the Android platform similar to the Apple platform.
What many do not know Google does these steps in small steps. So it always starts first.
Only in a few years one sees the effects. Apps can only be installed from the Google Play Store. Everything else goes only by an software which one sends to Google, in order to get a permission, so that the App can be installed. No offline setup/use possible anymore! Android devices can only be set up and used via Internet activation at some point (as with iPhone).
We have to act otherwise we will be more and more controlled by global corporations that only pursue their own interests (centralization, control, economic growth, fake security problems to limit the operating system, more market power, etc).
But the cause is in reality the consumers. The majority currently believe that Google, Apple, etc... are on the users' side. No, that's not true. It's just an illusion to distract.
The fact is that without the users' money, corporations like Google cannot exist. The decision is always ours!
We millions of users can spend more money in independent systems, hardware, software. We users can support even more independent developers. It's really possible. Don't forget!https://code.briarproject.org/briar/briar/-/issues/16626. The Briar apk name should contain the version number in the name as well2019-11-13T10:09:26ZGhost User6. The Briar apk name should contain the version number in the name as wellDownload the Briar app for Android here: https://briarproject.org/apk/briar.apk
In the name is no version number. it's just: **briar.apk**
Perhaps more details should be added to better organize your apk library faster and more accurat...Download the Briar app for Android here: https://briarproject.org/apk/briar.apk
In the name is no version number. it's just: **briar.apk**
Perhaps more details should be added to better organize your apk library faster and more accurately.
Like this, for example: **Briar v1.2.4.apk** or **Briar-1.2.4.apk**https://code.briarproject.org/briar/briar/-/issues/1661The feedback window is too small2022-07-20T10:38:40ZGhost UserThe feedback window is too smallThe feedback window is too small. If I type more details, I cannot see the beginning more.
Tested with Briar 1.2.4 versionThe feedback window is too small. If I type more details, I cannot see the beginning more.
Tested with Briar 1.2.4 versionhttps://code.briarproject.org/briar/briar/-/issues/16582. The app version + the revision number is missing2019-11-13T10:04:31ZGhost User2. The app version + the revision number is missingWhy can't see it in the settings of Briar. The app version + the revision number.
Tested with Briar 1.2.4 versionWhy can't see it in the settings of Briar. The app version + the revision number.
Tested with Briar 1.2.4 versionhttps://code.briarproject.org/briar/briar/-/issues/16571. Feedback function really works? I'm skeptical.2019-11-13T10:01:55ZGhost User1. Feedback function really works? I'm skeptical.Hello,
I'm using the current **Briar 1.2.4 version** and sent several feedbacks about 1 week ago. I always got this message: **Report saved. It will be sent the next time you log into Briar.**
I use mobile data and Wifi connection. The...Hello,
I'm using the current **Briar 1.2.4 version** and sent several feedbacks about 1 week ago. I always got this message: **Report saved. It will be sent the next time you log into Briar.**
I use mobile data and Wifi connection. The problem I am very skeptical if the feedback really arrived with you. When I sent it I didn't see any traffic. Then log out from Briar app.
When I start the app again there was some traffic, but you don't know if the feedback was really sent. There was no small message that it was sent.
Why is the report saved? If I do have internet conncection via mobile data or wifi, why not send it immediately?https://code.briarproject.org/briar/briar/-/issues/1656Explain better why messages can not be deleted2019-12-10T12:38:35ZTorsten GroteExplain better why messages can not be deletedCurrently, we show a long, but still incomplete list of reasons why not all messages maybe could not have been deleted. We should add some kind of enum or ORable number, so we can only show the reasons that actually apply to the current ...Currently, we show a long, but still incomplete list of reasons why not all messages maybe could not have been deleted. We should add some kind of enum or ORable number, so we can only show the reasons that actually apply to the current situation.Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1655ActivityNotFoundException for REQUEST_DISCOVERABLE intent2019-11-06T09:42:18ZakwizgranActivityNotFoundException for REQUEST_DISCOVERABLE intent* Android version: 5.1
* Phone model: Oale X2
* Briar version: 1.1.9 (b1dfd86)
* Bluetooth address: 47:[scrubbed]:A4
* Bluetooth status: Available, not enabled, not connectable, not discoverable
Stacktrace:
```
android.content.ActivityN...* Android version: 5.1
* Phone model: Oale X2
* Briar version: 1.1.9 (b1dfd86)
* Bluetooth address: 47:[scrubbed]:A4
* Bluetooth status: Available, not enabled, not connectable, not discoverable
Stacktrace:
```
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.bluetooth.adapter.action.REQUEST_DISCOVERABLE }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1792)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1512)
at android.app.Activity.startActivityForResult(Activity.java:3810)
at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:767)
at android.app.Activity.startActivityForResult(Activity.java:3761)
at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:754)
at org.briarproject.briar.android.keyagreement.KeyAgreementActivity.requestBluetoothDiscoverable(KeyAgreementActivity.java:189)
at org.briarproject.briar.android.keyagreement.KeyAgreementActivity.showQrCodeFragmentIfAllowed(KeyAgreementActivity.java:154)
at org.briarproject.briar.android.keyagreement.KeyAgreementActivity.onRequestPermissionsResult(KeyAgreementActivity.java:316)
at android.support.v4.app.ActivityCompat$1.run(ActivityCompat.java:519)
at android.os.Handler.handleCallback(Handler.java:815)
at android.os.Handler.dispatchMessage(Handler.java:104)
at android.os.Looper.loop(Looper.java:194)
at android.app.ActivityThread.main(ActivityThread.java:5631)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)
```
Looks like the device has a Bluetooth adapter, so I have no idea why this intent is missing.Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1654ActivityNotFoundException for CHANNEL_NOTIFICATION_SETTINGS intent2019-11-06T09:49:37ZakwizgranActivityNotFoundException for CHANNEL_NOTIFICATION_SETTINGS intent* Android version: 8.1.0
* Phone model: Smartisan OE106 (ocean)
* Briar version: 1.1.7 (37d0b61)
Stacktrace:
```
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.CHANNEL_NOTIFICATION_S...* Android version: 8.1.0
* Phone model: Smartisan OE106 (ocean)
* Briar version: 1.1.7 (37d0b61)
Stacktrace:
```
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.CHANNEL_NOTIFICATION_SETTINGS (has extras) }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1951)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1619)
at android.app.Activity.startActivityForResult(Activity.java:4743)
at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:767)
at android.support.v4.app.ActivityCompat.startActivityForResult(ActivityCompat.java:234)
at android.support.v4.app.FragmentActivity.startActivityFromFragment(FragmentActivity.java:881)
at android.support.v4.app.FragmentActivity$HostCallbacks.onStartActivityFromFragment(FragmentActivity.java:995)
at android.support.v4.app.Fragment.startActivity(Fragment.java:1084)
at android.support.v4.app.Fragment.startActivity(Fragment.java:1073)
at org.briarproject.briar.android.settings.SettingsFragment.lambda$setupNotificationPreference$6$SettingsFragment(SettingsFragment.java:492)
at org.briarproject.briar.android.settings.-$$Lambda$SettingsFragment$cYspmIOr_7rwGYgKSD-5SJndzsI.onPreferenceClick(Unknown Source:4)
at android.support.v7.preference.Preference.performClick(Preference.java:1165)
at android.support.v7.preference.Preference.performClick(Preference.java:1148)
at android.support.v14.preference.SwitchPreference.performClick(SwitchPreference.java:213)
at android.support.v7.preference.Preference$1.onClick(Preference.java:172)
at android.view.View.performClick(View.java:6436)
at android.view.View$PerformClick.run(View.java:25372)
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:6901)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:820)
```
Maybe an OEM ROM that doesn't have the standard notification settings activity?Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1653NPE in SettingsFragment2019-11-07T15:30:08ZakwizgranNPE in SettingsFragment* Android version: 8.1.0
* Phone model: Samsung SM-J727T1 (j7popeltemtr)
* Briar version: 1.2.3 (b464dcc)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'int org.briarproject.bramble.api.StringMap.getIn...* Android version: 8.1.0
* Phone model: Samsung SM-J727T1 (j7popeltemtr)
* Briar version: 1.2.3 (b464dcc)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'int org.briarproject.bramble.api.StringMap.getInt(java.lang.String, int)' on a null object reference
at org.briarproject.briar.android.settings.SettingsFragment.lambda$displaySettings$5$SettingsFragment(SettingsFragment.java:362)
at org.briarproject.briar.android.settings.-$$Lambda$SettingsFragment$xRJquGmI1azWoHeyvk2gdi8cc28.run(Unknown Source:2)
at org.briarproject.briar.android.activity.BaseActivity.lambda$runOnUiThreadUnlessDestroyed$0$BaseActivity(BaseActivity.java:216)
at org.briarproject.briar.android.activity.-$$Lambda$BaseActivity$fOFM6FuIkzfuGdAaggyXMoMGR0E.run(Unknown Source:4)
at android.app.Activity.runOnUiThread(Activity.java:6355)
at org.briarproject.briar.android.activity.BaseActivity.runOnUiThreadUnlessDestroyed(BaseActivity.java:215)
at org.briarproject.briar.android.settings.SettingsFragment.displaySettings(SettingsFragment.java:357)
at org.briarproject.briar.android.settings.SettingsFragment.eventOccurred(SettingsFragment.java:675)
at org.briarproject.bramble.event.EventBusImpl.lambda$broadcast$0$EventBusImpl(EventBusImpl.java:42)
at org.briarproject.bramble.event.-$$Lambda$EventBusImpl$bRn946wCXST7O6nsMZt_9tnkiuk.run(Unknown Source:4)
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:6958)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)
```Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1652IllegalArgumentException: pointerIndex out of range2021-06-14T10:46:13ZakwizgranIllegalArgumentException: pointerIndex out of range* Android version: 9
* Phone model: Android Pixel 3a (aosp_sargo)
* Briar version: 1.1.7 (d145a08)
* User feedback: "Zoomed in into a picture."
Stacktrace:
```
java.lang.IllegalArgumentException: pointerIndex out of range
at and...* Android version: 9
* Phone model: Android Pixel 3a (aosp_sargo)
* Briar version: 1.1.7 (d145a08)
* User feedback: "Zoomed in into a picture."
Stacktrace:
```
java.lang.IllegalArgumentException: pointerIndex out of range
at android.view.MotionEvent.nativeGetAxisValue(Native Method)
at android.view.MotionEvent.getX(MotionEvent.java:2205)
at android.support.v4.view.ViewPager.onInterceptTouchEvent(ViewPager.java:2072)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2573)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3030)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2719)
at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:440)
at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1830)
at android.app.Activity.dispatchTouchEvent(Activity.java:3401)
at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)
at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)
at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:398)
at android.view.View.dispatchPointerEvent(View.java:12752)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:5113)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4916)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4433)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4486)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4452)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4592)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4460)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4649)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4433)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4486)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4452)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4460)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4433)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:7099)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:7068)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:7029)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:7202)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:186)
at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:177)
at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:7173)
at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:7225)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:949)
at android.view.Choreographer.doCallbacks(Choreographer.java:761)
at android.view.Choreographer.doFrame(Choreographer.java:690)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:935)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:876)
```
Looks like a platform bug that would be hard for us to work around.