briar issueshttps://code.briarproject.org/briar/briar/-/issues2022-06-13T13:40:52Zhttps://code.briarproject.org/briar/briar/-/issues/2157Power management instructions for Xiaomi/Redmi are wrong2022-06-13T13:40:52ZakwizgranPower management instructions for Xiaomi/Redmi are wrongThe power management setup instructions for Xiaomi/Redmi devices say "If the padlock is not locked, tap to lock it".
But the button shows the effect of the action (tap to lock) rather than the current state (locked). So if the padlock i...The power management setup instructions for Xiaomi/Redmi devices say "If the padlock is not locked, tap to lock it".
But the button shows the effect of the action (tap to lock) rather than the current state (locked). So if the padlock is **already** locked, the user should tap it.
New instructions:
1. Open the recent apps list (also called the app switcher)
2. If Briar has a small padlock next to its name then you don't need to do anything
3. If there's no padlock, press and hold the image of Briar until the padlock button appears, then tap it
We also need to check whether the instructions for MIUI < 10 need to be updated.Android 1.4akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2158Apps can't be locked to recent apps list in MIUI 12.52022-06-13T13:40:38ZakwizgranApps can't be locked to recent apps list in MIUI 12.5The Redmi Note 7 received an update from MIUI 12.0.1 to 12.5.1, and now the instructions for locking an app to the recent apps list no longer work. In MIUI 12.0, long-pressing an app in the recent apps list showed a set of actions, inclu...The Redmi Note 7 received an update from MIUI 12.0.1 to 12.5.1, and now the instructions for locking an app to the recent apps list no longer work. In MIUI 12.0, long-pressing an app in the recent apps list showed a set of actions, including a lock/unlock action. In MIUI 12.5, long-pressing shows the app info screen instead.
This means we don't have a way of protecting Briar against Xiaomi/Redmi's power management on MIUI 12.5, and the instructions we're showing during account creation can't be followed.Android 1.4akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2270Crash during power management setup on Huawei device2022-04-13T10:20:05ZakwizgranCrash during power management setup on Huawei deviceA user reported that Briar crashes during power management setup on a Huawei device. It's not clear whether the crash happened when requesting doze exemption or when opening the battery settings screen (or perhaps even the protected apps...A user reported that Briar crashes during power management setup on a Huawei device. It's not clear whether the crash happened when requesting doze exemption or when opening the battery settings screen (or perhaps even the protected apps list, if it was an old phone).
https://quietplace.xyz/notes/8xa865dc3rAndroid 1.4akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/992continuously disconnected/logged out from Briar2021-09-01T10:10:21Zfedecontinuously disconnected/logged out from BriarThe problem I'm reporting does not concern my Briar setup (I'm using LineageOS 14.1), but my friend Briar setup. She uses a stock Android (can't check the version right now). Here's what happens to her:
- when she power-on the phone, Br...The problem I'm reporting does not concern my Briar setup (I'm using LineageOS 14.1), but my friend Briar setup. She uses a stock Android (can't check the version right now). Here's what happens to her:
- when she power-on the phone, Briar autostarts and asks for the password
- for some time she appears logged in and we can send messages each other
- after some time (less than half an hour) she appears offline and she does not receive any message
- even if she starts again Briar and logs in again, after some time she's put out without any notice
I could not see any obvious mistake in her configuration.
But I'm very new to Briar, so do not take anything for granted.
Any hint on how to debug this problem is appreciated.
Thanks in advanceakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1743Research whether our wake lock tags are still effective2021-09-01T10:10:21ZakwizgranResearch whether our wake lock tags are still effectiveLeave Briar running on devices with recent versions of Huawei PowerGenie and Evenwell PowerMonitor to see whether our wake lock tags still protect us from being killed.Leave Briar running on devices with recent versions of Huawei PowerGenie and Evenwell PowerMonitor to see whether our wake lock tags still protect us from being killed.Adapt to changes in the Android platformakwizgranakwizgran2021-04-30https://code.briarproject.org/briar/briar/-/issues/2009Give instructions during setup for protecting app from Xiaomi/Redmi power man...2021-07-06T10:02:52ZakwizgranGive instructions during setup for protecting app from Xiaomi/Redmi power managementWhile working on #1743 I found that the [Snooze app](https://code.briarproject.org/akwizgran/snooze) was killed when running overnight on the Redmi Note 7. [Locking the app to the recent apps list](https://code.briarproject.org/briar/bri...While working on #1743 I found that the [Snooze app](https://code.briarproject.org/akwizgran/snooze) was killed when running overnight on the Redmi Note 7. [Locking the app to the recent apps list](https://code.briarproject.org/briar/briar/-/issues/1743#note_49341) prevented this from happening. We should recommend this during account setup, as we do for Huawei's protected apps and app launch settings.
(The user can also [change the app's background setting to "No restrictions"](https://code.briarproject.org/briar/briar/-/issues/1743#note_49269), which is recommended in various places but didn't help in the case of the Snooze app.)Adapt to changes in the Android platformIvanaIvana2021-04-30https://code.briarproject.org/briar/briar/-/issues/1824Adapt to power management restrictions2021-04-30T13:42:29ZakwizgranAdapt to power management restrictionsAdapt to changes in the Android platform2021-04-30https://code.briarproject.org/briar/briar/-/issues/1188Close redundant transport connections2020-10-06T16:48:59ZakwizgranClose redundant transport connectionsIt's not unusual to have multiple connections to a given contact open at the same time, especially if both users sign in or activate a transport at roughly the same time. In some cases these connections may be considered redundant. For e...It's not unusual to have multiple connections to a given contact open at the same time, especially if both users sign in or activate a transport at roughly the same time. In some cases these connections may be considered redundant. For example, a Tor connection may be considered redundant if we also have a LAN connection, and if we have incoming and outgoing connections over the same duplex transport, one of them is redundant.
Closing redundant connections would save battery and bandwidth. Performance tests also suggest that redundant connections may slow down sync by increasing the number of database queries triggered by each sync-related event. Syncing 30 forum posts from an Xperia Z3 Compact to a Moto E3 takes about 10% longer when there are four Tor and LAN connections than when there's a single Bluetooth connection, because the DB rather than the network is the bottleneck.
The tricky part is choosing which connections to close, such that the two endpoints don't choose different connections and end up closing too many.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/185Toggle Transport States2020-09-04T12:27:54ZTorsten GroteToggle Transport StatesIt would be great to be able to enable/disable transports by touching the icons in the dashboard.
For this, we should have three states for plugins:
* disabled
* enabled
* ready
that could be shown as grey, amber and green icons.It would be great to be able to enable/disable transports by touching the icons in the dashboard.
For this, we should have three states for plugins:
* disabled
* enabled
* ready
that could be shown as grey, amber and green icons.https://code.briarproject.org/briar/briar/-/issues/1142Use alarms to schedule essential tasks2020-08-14T09:48:13ZakwizgranUse alarms to schedule essential tasksWe use a ScheduledExecutorService to schedule essential tasks such as key rotation and polling for connections. When Tor is disabled or doesn't have internet connectivity, the Tor plugin's wake lock is released and the device may sleep o...We use a ScheduledExecutorService to schedule essential tasks such as key rotation and polling for connections. When Tor is disabled or doesn't have internet connectivity, the Tor plugin's wake lock is released and the device may sleep or doze. To ensure that essential tasks run during sleep or doze, we should schedule them using alarms.Android 1.2akwizgranakwizgranhttps://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/1260Power management improvements2019-04-01T13:19:14ZakwizgranPower management improvementsUmbrella ticket for sponsor 1, objective 6.Umbrella ticket for sponsor 1, objective 6.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 Grotehttps://code.briarproject.org/briar/briar/-/issues/978Add preference for using tor only when having power2019-02-21T10:34:01ZGreg TroxelAdd preference for using tor only when having power(Sorry if this is a dup; I searched but am not confident.)
I just built and installed Briar after being absent for a while. I see there's a preference for using tor never, on wifi, and on cellular. That's great for some, but doesn't a...(Sorry if this is a dup; I searched but am not confident.)
I just built and installed Briar after being absent for a while. I see there's a preference for using tor never, on wifi, and on cellular. That's great for some, but doesn't address my problem. I realize there is tension with UX and complicated config, but given that having a HS is very very costly power wise, and outbound tor is somewhat costly, I'd like to see a config for "Use Tor when not charging" that is "no, outbound only, outbound and inbound". This would probably let me start running briar, and I suspect would let others do so as well.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/268Research how to deal with doze mode on Android 62019-02-21T10:34:00ZakwizgranResearch how to deal with doze mode on Android 6Android 6 has a new doze mode when the device is idle. Apps can't access the network in doze mode, except during short wakeup periods. This will kill our ability to receive messages while the device is idle. The recommended workaround is...Android 6 has a new doze mode when the device is idle. Apps can't access the network in doze mode, except during short wakeup periods. This will kill our ability to receive messages while the device is idle. The recommended workaround is to use Google Cloud Messaging, which obviously won't work for us.
We may need to prompt the user to add Briar to a whitelist. Thanks Google! Love ya!
http://developer.android.com/training/monitoring-device-state/doze-standby.htmlAndroid 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1100Setup wizard page for Samsung's power manager2019-02-21T10:34:00ZakwizgranSetup wizard page for Samsung's power managerhttps://gitlab.com/axet/android-library/blob/master/src/main/java/com/github/axet/androidlibrary/widgets/OptimizationPreferenceCompat.java
https://stackoverflow.com/questions/37205106/how-do-i-avoid-that-my-app-enters-optimization-on-sa...https://gitlab.com/axet/android-library/blob/master/src/main/java/com/github/axet/androidlibrary/widgets/OptimizationPreferenceCompat.java
https://stackoverflow.com/questions/37205106/how-do-i-avoid-that-my-app-enters-optimization-on-samsung-devices
https://stackoverflow.com/questions/34074955/android-exact-alarm-is-always-3-minutes-off/34085645#34085645
Looks like the situation is similar to Huawei - we create an intent for the power manager's whitelisting activity, and if the intent is callable, we're on an affected device. I haven't looked into whether we can detect whether we're already whitelisted.
Apparently the intent's package and class name should be:
* `"com.samsung.android.sm", "com.samsung.android.sm.ui.battery.BatteryActivity"` on Android L
* `"com.samsung.android.lool", "com.samsung.android.sm.ui.battery.BatteryActivity"` on Android N
According to one of the StackOverflow answers, keywords like "alert" and "clock" in the package name will cause the app to be automatically whitelisted. Good grief...Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/821Research whether network traffic can wake an app from sleep or doze2019-02-21T10:34:00ZakwizgranResearch whether network traffic can wake an app from sleep or dozeThe all-knowing oracles of Stack Overflow have conflicting opinions about whether an Android app that's blocked reading from a TCP connection while the device is sleeping will be woken when data arrives. This may be device-dependent. Cer...The all-knowing oracles of Stack Overflow have conflicting opinions about whether an Android app that's blocked reading from a TCP connection while the device is sleeping will be woken when data arrives. This may be device-dependent. Certainly the connection that's used for GCM/Firebase can wake the device, but the same may not be true of other connections. We also need to investigate whether doze behaves differently from sleep in this respect. Some sources claim that wifi behaves differently from mobile data - if so, we should investigate whether holding a wifi lock affects this.
It would also be useful to know whether an incoming connection to a server socket wakes the app.
Related to #44, #268.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1263Tor power management research2019-02-21T10:33:59ZakwizgranTor power management researchUmbrella ticket for sponsor 1, objective 7.Umbrella ticket for sponsor 1, objective 7.Android 1.1https://code.briarproject.org/briar/briar/-/issues/1262Update manual for power management improvements2019-02-21T10:33:59ZakwizgranUpdate manual for power management improvementsSubtask of #1260.Subtask of #1260.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1496Check whether we're affected by implicit broadcast restrictions on Android 8+2019-02-21T10:32:35ZakwizgranCheck whether we're affected by implicit broadcast restrictions on Android 8+Apps targetting Android 8+ don't receive certain implicit broadcasts. Check whether we're affected.
https://developer.android.com/about/versions/oreo/background
Subtask of #1260.Apps targetting Android 8+ don't receive certain implicit broadcasts. Check whether we're affected.
https://developer.android.com/about/versions/oreo/background
Subtask of #1260.Android 1.1Torsten GroteTorsten Grote