briar issueshttps://code.briarproject.org/briar/briar/-/issues2019-02-25T10:11:34Zhttps://code.briarproject.org/briar/briar/-/issues/840Blogs: Strange behaviour when tapping an entry2019-02-25T10:11:34ZMegaloxBlogs: Strange behaviour when tapping an entryI made a video:
![blog_strange_tapping_behaviour](/uploads/3ab9c30610f56a24abafc99f70458392/blog_strange_tapping_behaviour.mp4)
I'll try to explain what happens here and what I think is the problem:
(1) I'm in the Blog view an...I made a video:
![blog_strange_tapping_behaviour](/uploads/3ab9c30610f56a24abafc99f70458392/blog_strange_tapping_behaviour.mp4)
I'll try to explain what happens here and what I think is the problem:
(1) I'm in the Blog view and tap on Rinre's name
(2) Rinre's personal blog opens (so far so good)
(3) Than I tap on Rinre's name again and get a "Back" transition, but I don't get back to the blog but am still in the personal blog (I repeat this three times in the video)
(4) Next I tap on an entry outside of Rinre's name and the single view for the blog opens. I would only expect the single view to open when I reblog. The appbar still tells me I'm in Rinres personal blog.
(5) Tapping on Rinres name again brings me to his personal blog (That is correct I think)
(6) The rest of the video I'm having some fun tapping here and there, essentially I'm only repeating the steps I took before.https://code.briarproject.org/briar/briar/-/issues/784Blogs: Reblogging snackbar is not shown correctly2019-02-25T10:10:11ZMegaloxBlogs: Reblogging snackbar is not shown correctlyPlease take a look at the recording:
![device-2016-11-29-092645](/uploads/d013b9f701f6ae4230808354ceb6fc6f/device-2016-11-29-092645.mp4)
First I'm creating a blogpost (everything is fine) but when I reblog, the snackbar is not shown...Please take a look at the recording:
![device-2016-11-29-092645](/uploads/d013b9f701f6ae4230808354ceb6fc6f/device-2016-11-29-092645.mp4)
First I'm creating a blogpost (everything is fine) but when I reblog, the snackbar is not shown correctly. The first time you can only see a small upper part above the software keys, the second time I reblog without commentary and there is no snackbar at all and the third time I reblog you can see a little bit more of the snackbar, but it gets definitley cut. I could reproduce this several times.https://code.briarproject.org/briar/briar/-/issues/740App silently quits when out of memory2019-02-25T10:04:29ZTorsten GroteApp silently quits when out of memory```
11-07 13:04:42.066 D/dalvikvm: GC_FOR_ALLOC freed 618K, 40% free 28656K/47559K, paused 75ms, total 76ms
11-07 13:04:42.066 I/dalvikvm-heap: Forcing collection of SoftReferences for 2385116-byte allocation
11-07 13:04:42.146 D/dalv...```
11-07 13:04:42.066 D/dalvikvm: GC_FOR_ALLOC freed 618K, 40% free 28656K/47559K, paused 75ms, total 76ms
11-07 13:04:42.066 I/dalvikvm-heap: Forcing collection of SoftReferences for 2385116-byte allocation
11-07 13:04:42.146 D/dalvikvm: GC_BEFORE_OOM freed 26K, 40% free 28629K/47559K, paused 84ms, total 84ms
11-07 13:04:42.146 E/dalvikvm-heap: Out of memory on a 2385116-byte allocation.
11-07 13:04:42.146 I/dalvikvm: "main" prio=5 tid=1 RUNNABLE
11-07 13:04:42.146 I/dalvikvm: | group="main" sCount=0 dsCount=0 obj=0x2b545568 self=0x12ad8
11-07 13:04:42.146 I/dalvikvm: | sysTid=24662 nice=0 sched=0/0 cgrp=apps handle=715976496
11-07 13:04:42.146 I/dalvikvm: | schedstat=( 0 0 0 ) utm=5505 stm=1699 core=0
11-07 13:04:42.146 I/dalvikvm: at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
11-07 13:04:42.146 I/dalvikvm: at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:500)
11-07 13:04:42.146 I/dalvikvm: at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:353)
11-07 13:04:42.146 I/dalvikvm: at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:781)
11-07 13:04:42.146 I/dalvikvm: at android.content.res.Resources.loadDrawable(Resources.java:1959)
11-07 13:04:42.146 I/dalvikvm: at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
11-07 13:04:42.146 I/dalvikvm: at android.widget.ImageView.<init>(ImageView.java:120)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.widget.AppCompatImageView.<init>(AppCompatImageView.java:57)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.widget.AppCompatImageView.<init>(AppCompatImageView.java:53)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.app.AppCompatViewInflater.createView(AppCompatViewInflater.java:106)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.app.AppCompatDelegateImplV7.createView(AppCompatDelegateImplV7.java:972)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.app.AppCompatDelegateImplV7.onCreateView(AppCompatDelegateImplV7.java:1031)
11-07 13:04:42.156 I/dalvikvm: at android.support.v4.view.LayoutInflaterCompatHC$FactoryWrapperHC.onCreateView(LayoutInflaterCompatHC.java:44)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:675)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:466)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
11-07 13:04:42.156 I/dalvikvm: at android.support.design.internal.NavigationMenuPresenter.inflateHeaderView(NavigationMenuPresenter.java:189)
11-07 13:04:42.156 I/dalvikvm: at android.support.design.widget.NavigationView.inflateHeaderView(NavigationView.java:258)
11-07 13:04:42.156 I/dalvikvm: at android.support.design.widget.NavigationView.<init>(NavigationView.java:173)
11-07 13:04:42.156 I/dalvikvm: at android.support.design.widget.NavigationView.<init>(NavigationView.java:95)
11-07 13:04:42.156 I/dalvikvm: at java.lang.reflect.Constructor.constructNative(Native Method)
11-07 13:04:42.156 I/dalvikvm: at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.createView(LayoutInflater.java:587)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:687)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.parseInclude(LayoutInflater.java:830)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.rInflate(LayoutInflater.java:736)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
11-07 13:04:42.156 I/dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.app.AppCompatDelegateImplV7.setContentView(AppCompatDelegateImplV7.java:276)
11-07 13:04:42.156 I/dalvikvm: at android.support.v7.app.AppCompatActivity.setContentView(AppCompatActivity.java:139)
11-07 13:04:42.156 I/dalvikvm: at org.briarproject.android.NavDrawerActivity.onCreate(NavDrawerActivity.java:96)
```https://code.briarproject.org/briar/briar/-/issues/692Forum/blog sharing layout is too large for small screens2019-02-25T10:03:19ZakwizgranForum/blog sharing layout is too large for small screensThe screenshot comes from the Sony Xperia Tipo (Android 4.0.4, 320x480 screen).
![device-2016-10-04-155033](/uploads/b5f3f5b4c2ef7fd007e4df0603384e9a/device-2016-10-04-155033.png)
Suggested solution: remove the "You may compose..." mes...The screenshot comes from the Sony Xperia Tipo (Android 4.0.4, 320x480 screen).
![device-2016-10-04-155033](/uploads/b5f3f5b4c2ef7fd007e4df0603384e9a/device-2016-10-04-155033.png)
Suggested solution: remove the "You may compose..." message, replace the text field's hint text with "Add a message (optional)".https://code.briarproject.org/briar/briar/-/issues/361Testers could not connect to their contacts2019-02-25T09:56:36ZakwizgranTesters could not connect to their contactsDuring a multi-day test, testers were sometimes unable to connect to their contacts and messages were delayed for days. This happened whether they were connected to wifi or mobile data.During a multi-day test, testers were sometimes unable to connect to their contacts and messages were delayed for days. This happened whether they were connected to wifi or mobile data.https://code.briarproject.org/briar/briar/-/issues/434Tor: Could not parse my own descriptor2019-02-25T09:55:40ZTorsten GroteTor: Could not parse my own descriptorI am running Briar in an emulator and suddenly my log gets spamed with these:
```
6-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:17.656 10108-11546/org.bri...I am running Briar in an emulator and suddenly my log gets spamed with these:
```
6-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor zzqy2x5mk2kgo4lie44345uzc37xp7gk version 2 permanent-key -----BEGIN RSA PUBLIC KEY----- MIGJAoGBAO8OZaFqUOdslKsUllgU2pHZ4byDLgQF3MeXBRq6NGGCHdQ0k0OAqmq7 AE/F8MPlfi4Nxv8gr3Cn3ePjLqP6ylEaL7sFEHtVDMEZYk9PSQ/o+UkzwMfu967y UymPH/vzAiytgBc4zQSbjatlUPFyrHgEkppcERzlCl0wjseKhUERAgMBAAE= -----END RSA PUBLIC KEY----- secret-id-part qbpaetzw5utrk5bs5y2j2wf7zsp5mrgp publication-time 1880-05-09 07:31:44 protocol-versions 2,3 introduction-points -----BEGIN MESSAGE----- aW50cm9kdWN0aW9uLXBvaW50IGJ5NnQ3dHJnNjJsanc2eGliemdrbnJncHZmNHly NHk2CmlwLWFkZHJlc3MgOTQuMjMuMjAuMjgKb25pb24tcG9ydCAyMzQyCm9uaW9u LWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlHSkFvR0JBTTZU akpxQ1BQZVVKQ0E0OVc1NGx0TEp6eEk2OXJtYjlZeTRLU1Y3SlRPbEV2NEVqZmt6 d3NERgplMWttaDRSeWE3alFoOG9XdlVBR2Uwb3E3ZFFUa1lCQ296azRtQ3dQOTA2 SkVPcVIxNjMwZ0phTTB6RXBib1Z2CmlHZWhzWjdwWEtGM1FVMVYxRjM3eFVkQldK aUdLcERyOW9pQ3FkWGhPSWVuZDAzNWh4VEhBZ01CQUFFPQotLS0tLUVORCBSU0Eg UFVCTElDIEtFWS0tLS0tCnNlcnZpY2Uta2V5Ci0tLS0tQkVHSU4gUlNBIFBVQkxJ QyBLRVktLS0tLQpNSUdKQW9HQkFPTFlRL3hhM1hoMFpCdkR6OS9Jcll4UWZid01I NDFZdmFVTjVrRVRnOUwranduYm84SHNBSTBPCjU4VjFGWTRyT2xyT3cvNWFsbzh4 TVdvSEpMMUlKMmhSMXBFRkt3cVNaN2pyMkozOHVKWHNXWGE0LzlFZWNOTEsKcFVU ZHFXellDbEJSSU9EOCt1TDNnK3lUUi9KcXdUa2R4Sk4yVHZtNUdwd0NneUpjMkZW aEFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMgS0VZLS0tLS0KaW50cm9kdWN0 aW9uLXBvaW50IGl3dnI2dXNjY2h2bWNxdnBoM3JwcHZibjJoYnh2MnoyCmlwLWFk ZHJlc3MgODEuMjI5LjM2LjIwMwpvbmlvbi1wb3J0IDE3ODgKb25pb24ta2V5Ci0t LS0tQkVHSU4gUlNBIFBVQkxJQyBLRVktLS0tLQpNSUdKQW9HQkFOSzA3NzUxZUlp bmZRa3Q4MFZ0ai9nZU5lVjJNdGxUM0ZyTE9HUGcybHNhb09ydWV1SVdSekxZCkxR VGlUemlyTDJ2TzBlUnZLVkJ1VVpiNklLSWtmb0FRZEMzODFSd2VRc2xBMkk3MzMv VXpRYm9nTHlhREFIZEEKRVR4QmQ3V0tLNFExQWpxVGIwUDNyOTBoQ3J2RWk5MDN3 QmxOakRxbTR6b2JaVG1VUVRyOUFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMg S0VZLS0tLS0Kc2VydmljZS1rZXkKLS0tLS1CRUdJTiBSU0EgUFVCTElDIEtFWS0t LS0tCk1JR0pBb0dCQU1UQTQ5RUUyYkxZN1NXU0xkVXZHZXhRVDZ1UVFPUDBoL1Vi MU9CZVFuQkIxVkxxNFRoU3FNK0oKaDlXSlAwTUk0TGlNeHV3ODBhZjJHK0REczlv MGNUakRUdmxVNlQvc0lXdlVDSWVHVTlRcDVBRm5KSThmRTM2QwpjYUovNGJ1Vi90 L0JVODRpR2Fvd3pObG9zNmllK3pUbVZMcU9uU1I2S2l4cjh3cEZvWUU5QWdNQkFB RT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0tLQppbnRyb2R1Y3Rpb24tcG9p bnQgZ213bmpjaXhwNHFjazRmaGFpanNyaWwyc2c3eWVvZWoKaXAtYWRkcmVzcyAx OTIuMTUwLjk0LjQ5Cm9uaW9uLXBvcnQgOTAwMQpvbmlvbi1rZXkKLS0tLS1CRUdJ TiBSU0EgUFVCTElDIEtFWS0tLS0tCk1JR0pBb0dCQUxpWXppQ1gwSFM5eVd1VTNo TFRrZ0F6TGhYS0l3eFRyanVtQmVrdXBYRzRJM0laOWNPbmttNmEKcFhzUlRGaTF5 NXBiWWNvTzRMTmw1SnBndVJaYVJGR29KZmVJallkNTdXTW5xTkRoUlhzWHVrVW5l TkVHaHFZeApSVEJiMlRZWTlpVW1JSEZSMElrblZtOEFCVFIrNDlJRUFZaUkvNy9s a2FTMlQza2lSZ3NqQWdNQkFBRT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0t LQpzZXJ2aWNlLWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlH SkFvR0JBTEtCYXNHN09MNGYyUDdrQW5INDFIV1RSY092TnRlMkFRdkc0VkxKOXJ5 SjBLN0NCN3Zqd3dMbAo1L21WaVh0ZzNid3JDQ3MvYnI4S2pOd29MZEhIRHU1cmJP S3VlNWxnV0VSYzV4cXk0eGkzcGtORk0wUDlTaUZaCm9QOUlRcCtDeUZRZVlLVlNP K3RPOFBzVHozK0xQdjlRcEFDSmdJSnlaTnMwMnA5L0VOeGhBZ01CQUFFPQotLS0t LUVORCBSU0EgUFVCTElDIEtFWS0tLS0tCgo= -----END MESSAGE----- signature -----BEGIN SIGNATURE----- NILJpinHVXuLzc/FKxxcXsB8cQXmPvD4xi6+D/JDM6SiRffsRRWoWcIufOvWRUZM gAf55SxV1M+jVFhw1gGNfjbBo56hytfmPQdhF9ucoPHlZA90kytyTgBtPiw9qeQG n5pcPq8qmpG9dlEfYOK1EJkYTIieYkXrNB4B5Zyju0I= -----END SIGNATURE----- (on Tor 0.2.7.6 )
06-15 11:17:17.656 10108-11546/org.briarproject I/TorPlugin: WARN upload_service_descriptor(): Bug: Internal error: couldn't encode service descriptor; not uploading. (on Tor 0.2.7.6 )
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN ISO time "1880-05-09 07:31:44" was nonsensical
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor zzqy2x5mk2kgo4lie44345uzc37xp7gk version 2 permanent-key -----BEGIN RSA PUBLIC KEY----- MIGJAoGBAO8OZaFqUOdslKsUllgU2pHZ4byDLgQF3MeXBRq6NGGCHdQ0k0OAqmq7 AE/F8MPlfi4Nxv8gr3Cn3ePjLqP6ylEaL7sFEHtVDMEZYk9PSQ/o+UkzwMfu967y UymPH/vzAiytgBc4zQSbjatlUPFyrHgEkppcERzlCl0wjseKhUERAgMBAAE= -----END RSA PUBLIC KEY----- secret-id-part qbpaetzw5utrk5bs5y2j2wf7zsp5mrgp publication-time 1880-05-09 07:31:44 protocol-versions 2,3 introduction-points -----BEGIN MESSAGE----- aW50cm9kdWN0aW9uLXBvaW50IGJ5NnQ3dHJnNjJsanc2eGliemdrbnJncHZmNHly NHk2CmlwLWFkZHJlc3MgOTQuMjMuMjAuMjgKb25pb24tcG9ydCAyMzQyCm9uaW9u LWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlHSkFvR0JBTTZU akpxQ1BQZVVKQ0E0OVc1NGx0TEp6eEk2OXJtYjlZeTRLU1Y3SlRPbEV2NEVqZmt6 d3NERgplMWttaDRSeWE3alFoOG9XdlVBR2Uwb3E3ZFFUa1lCQ296azRtQ3dQOTA2 SkVPcVIxNjMwZ0phTTB6RXBib1Z2CmlHZWhzWjdwWEtGM1FVMVYxRjM3eFVkQldK aUdLcERyOW9pQ3FkWGhPSWVuZDAzNWh4VEhBZ01CQUFFPQotLS0tLUVORCBSU0Eg UFVCTElDIEtFWS0tLS0tCnNlcnZpY2Uta2V5Ci0tLS0tQkVHSU4gUlNBIFBVQkxJ QyBLRVktLS0tLQpNSUdKQW9HQkFPTFlRL3hhM1hoMFpCdkR6OS9Jcll4UWZid01I NDFZdmFVTjVrRVRnOUwranduYm84SHNBSTBPCjU4VjFGWTRyT2xyT3cvNWFsbzh4 TVdvSEpMMUlKMmhSMXBFRkt3cVNaN2pyMkozOHVKWHNXWGE0LzlFZWNOTEsKcFVU ZHFXellDbEJSSU9EOCt1TDNnK3lUUi9KcXdUa2R4Sk4yVHZtNUdwd0NneUpjMkZW aEFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMgS0VZLS0tLS0KaW50cm9kdWN0 aW9uLXBvaW50IGl3dnI2dXNjY2h2bWNxdnBoM3JwcHZibjJoYnh2MnoyCmlwLWFk ZHJlc3MgODEuMjI5LjM2LjIwMwpvbmlvbi1wb3J0IDE3ODgKb25pb24ta2V5Ci0t LS0tQkVHSU4gUlNBIFBVQkxJQyBLRVktLS0tLQpNSUdKQW9HQkFOSzA3NzUxZUlp bmZRa3Q4MFZ0ai9nZU5lVjJNdGxUM0ZyTE9HUGcybHNhb09ydWV1SVdSekxZCkxR VGlUemlyTDJ2TzBlUnZLVkJ1VVpiNklLSWtmb0FRZEMzODFSd2VRc2xBMkk3MzMv VXpRYm9nTHlhREFIZEEKRVR4QmQ3V0tLNFExQWpxVGIwUDNyOTBoQ3J2RWk5MDN3 QmxOakRxbTR6b2JaVG1VUVRyOUFnTUJBQUU9Ci0tLS0tRU5EIFJTQSBQVUJMSUMg S0VZLS0tLS0Kc2VydmljZS1rZXkKLS0tLS1CRUdJTiBSU0EgUFVCTElDIEtFWS0t LS0tCk1JR0pBb0dCQU1UQTQ5RUUyYkxZN1NXU0xkVXZHZXhRVDZ1UVFPUDBoL1Vi MU9CZVFuQkIxVkxxNFRoU3FNK0oKaDlXSlAwTUk0TGlNeHV3ODBhZjJHK0REczlv MGNUakRUdmxVNlQvc0lXdlVDSWVHVTlRcDVBRm5KSThmRTM2QwpjYUovNGJ1Vi90 L0JVODRpR2Fvd3pObG9zNmllK3pUbVZMcU9uU1I2S2l4cjh3cEZvWUU5QWdNQkFB RT0KLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0tLQppbnRyb2R1Y3Rpb24tcG9p bnQgZ213bmpjaXhwNHFjazRmaGFpanNyaWwyc2c3eWVvZWoKaXAtYWRkcmVzcyAx OTIuMTUwLjk0LjQ5Cm9uaW9uLXBvcnQgOTAwMQpvbmlvbi1rZXkKLS0tLS1CRUdJ TiBSU0EgUFVCTElDIEtFWS0tLS0tCk1JR0pBb0dCQUxpWXppQ1gwSFM5eVd1VTNo TFRrZ0F6TGhYS0l3eFRyanVtQmVrdXBYRzRJM0laOWNPbmttNmEKcFhzUlRGaTF5 NXBiWWNvTzRMTmw1SnBndVJqYVJGR29KZmVJallkNTdXTW5xTkRoUlhzWHVrVW5l TkVHaHFZeApSVEJiMlRZWTlpVW1JSEZSMElrblZtOEFCVFIrNDlJRUFZaUkvNy9s a2FTMlQza2lSZ3NqQWdNQkFBRT0BLS0tLS1FTkQgUlNBIFBVQkxJQyBLRVktLS0t LQpzZXJ2aWNlLWtleQotLS0tLUJFR0lOIFJTQSBQVUJMSUMgS0VZLS0tLS0KTUlH SkFvR0JBTEtCYXNHN09MNGYyUDdrQW5INDFIV1RSY092TnRlMkFRdkc0VkxKOXJ5 SjBLN0NCN3Zqd3dMbAo1L21WaVh0ZzNid3JDQ3MvYnI4S2pOd29MZEhIRHU1cmJP S3VlNWxnV0VSYzV4cXk0eGkzcGtORk0wUDlTaUZaCm9QOUlRcCtDeUZRZVlLVlNP K3RPOFBzVHozK0xQdjlRcEFDSmdJSnlaTnMwMnA5L0VOeGhBZ01CQUFFPQotLS0t LUVORCBSU0EgUFVCTElDIEtFWS0tLS0tCgo= -----END MESSAGE----- signature -----BEGIN SIGNATURE----- NILJpinHVXuLzc/FKxxcXsB8cQXmPvD4xi6+D/JDM6SiRffsRRWoWcIufOvWRUZM gAf55SxV1M+jVFhw1gGNfjbBo56hytfmPQdhF9ucoPHlZA90kytyTgBtPiw9qeQG n5pcPq8qmpG9dlEfYOK1EJkYTIieYkXrNB4B5Zyju0I= -----END SIGNATURE----- (on Tor 0.2.7.6 )
06-15 11:17:18.657 10108-11546/org.briarproject I/TorPlugin: WARN upload_service_descriptor(): Bug: Internal error: couldn't encode service descriptor; not uploading. (on Tor 0.2.7.6 )
06-15 11:17:19.656 10108-11546/org.briarproject I/TorPlugin: WARN ISO time "1880-05-09 07:31:44" was nonsensical
06-15 11:17:19.657 10108-11546/org.briarproject I/TorPlugin: WARN Invalid publication time: '1880-05-09 07:31:44'
```
Please note that the time of the emulator is correct.https://code.briarproject.org/briar/briar/-/issues/13Validating keys and verifying signatures is very slow2019-02-25T09:52:49ZakwizgranValidating keys and verifying signatures is very slowValidating a public key takes around 1.7 seconds on the Galaxy Nexus. Verifying a pseudonymous message takes around 2.9 seconds, versus 1 ms for an anonymous message.
We can cache validated public keys, but we'll need to find some oth...Validating a public key takes around 1.7 seconds on the Galaxy Nexus. Verifying a pseudonymous message takes around 2.9 seconds, versus 1 ms for an anonymous message.
We can cache validated public keys, but we'll need to find some other way to improve the performance of signature verification.
https://code.briarproject.org/briar/briar/-/issues/505highlighting/marking for copy/paste in dark speech bubbles not visible2019-02-22T15:28:30ZMegaloxhighlighting/marking for copy/paste in dark speech bubbles not visiblea tester tried to copy text from his own speech bubble. the highlighting cannot be seen clearly on the dark background.a tester tried to copy text from his own speech bubble. the highlighting cannot be seen clearly on the dark background.https://code.briarproject.org/briar/briar/-/issues/1498Use Meek-Lite pluggable transport in China2019-02-22T12:28:21ZTorsten GroteUse Meek-Lite pluggable transport in ChinaThe obfs4 project [includes a meek-likte transport](https://github.com/Yawning/obfs4/tree/master/transports/meeklite) that we could use to circumvent Tor censorship in China.The obfs4 project [includes a meek-likte transport](https://github.com/Yawning/obfs4/tree/master/transports/meeklite) that we could use to circumvent Tor censorship in China.Android 1.1Torsten GroteTorsten Grote2019-02-28https://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/1477Implement UX for finding out whether contacts support image attachments2019-02-21T10:34:38ZakwizgranImplement UX for finding out whether contacts support image attachmentsImplement the design from #1476 for finding out whether each contact supports image attachments.
Subtask of #1438.Implement the design from #1476 for finding out whether each contact supports image attachments.
Subtask of #1438.Android 1.3Torsten 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/1385Link in error message for adding contacts doesn't cover entire word2019-02-21T10:34:00ZakwizgranLink in error message for adding contacts doesn't cover entire wordLooks like there's an off-by-one error in the code that turns "send feedback" into a link:
![device-2018-09-19-165301](/uploads/179050fb18775c1832076056acf8cf93/device-2018-09-19-165301.png)Looks like there's an off-by-one error in the code that turns "send feedback" into a link:
![device-2018-09-19-165301](/uploads/179050fb18775c1832076056acf8cf93/device-2018-09-19-165301.png)Android 1.1https://code.briarproject.org/briar/briar/-/issues/1392List of panic button apps isn't updated after installing app2019-02-21T10:34:00ZakwizgranList of panic button apps isn't updated after installing appSteps to reproduce:
* Uninstall Ripple
* Start Briar
* Go to "Settings > Panic button setup > Panic Button App"
* A dialog opens showing "None" as the only choice
* An app chooser opens to install Ripple (if you only have one market app...Steps to reproduce:
* Uninstall Ripple
* Start Briar
* Go to "Settings > Panic button setup > Panic Button App"
* A dialog opens showing "None" as the only choice
* An app chooser opens to install Ripple (if you only have one market app, perhaps it opens automatically?)
* Install Ripple from F-Droid
* Press back to return to Briar
* Expected:
* The dialog has closed
* Pressing "Panic Button App" again shows a list that includes Ripple
* Pressing "Panic Button App" again doesn't open the app chooser to install Ripple again
* Actual:
* The dialog is still open showing "None" as the only choice
* Pressing "Panic Button App" again shows a list with "None" as the only choice
* Pressing "Panic Button App" again opens the app chooser to install Ripple againAndroid 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