[Ring] Android Crash After Creation Or Device Link

[Nathan Royce]

Android build commit: 2b9ae33b51328f0638061b0a8fb848c22e1176b8
Daemon build/fixed commit: 52d944196e2c809db5eded2ae3ad0396a2b08c2d

This is issue has now been fixed. Account creation and linking device
both work without crashing.
Feel free to push the app to the Google Play Store.

As a side note, if you merge a fix, mention it in the ML thread so the
OP knows the fix can be tested.
I only knew about the fix by chance, looking at the git log.

[Ring] Gnome-ring Crash Dump

[Nathan Royce]

gnome-ring[1134]: Loading vcf from: QDir(
"/home/user/.local/share/gnome-ring/profiles" , nameFilters = { "*" },
 QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters(
Dirs|Files|Drives|AllEntries ) )
kernel: gnome-ring[1134]: segfault at 0 ip 0029551580b8 sp
7ffc7d998df0 error 4 in gnome-ring[29550b4000+1ef000]
(gnome-ring) crashed and dumped core
*
systemd-coredump[1171]: Process 1134 (gnome-ring) of user 1000 dumped core.

  Stack trace of thread 1134:
  #0  0x0029551580b8
restore_selected_account (gnome-ring)
  #1  0x002955159577
ring_client_startup (gnome-ring)
  #2  0x7fe464023ead
g_closure_invoke (libgobject-2.0.so.0)
  #3  0x7fe46403657e
n/a (libgobject-2.0.so.0)
  #4  0x7fe46403ec85
g_signal_emit_valist (libgobject-2.0.so.0)
  #5  0x7fe46403f69f
g_signal_emit (libgobject-2.0.so.0)
  #6  0x7fe464306b32
g_application_register (libgio-2.0.so.0)
  #7  0x7fe46430730f
n/a (libgio-2.0.so.0)
  #8  0x7fe464307696
g_application_run (libgio-2.0.so.0)
  #9  0x00295515685a
main (gnome-ring)
  #10 0x7fe459d6e4ca
__libc_start_main (libc.so.6)
  #11 0x00295515662a
_start (gnome-ring)

  Stack trace of thread 1136:
  #0  0x7fe459e31e9d
poll (libc.so.6)
  #1  0x7fe463d4bc09
n/a (libglib-2.0.so.0)
  #2  0x7fe463d4bd1c
g_main_context_iteration (libglib-2.0.so.0)
  #3  0x7fe463d4bd61
n/a (libglib-2.0.so.0)
  #4  0x7fe463d72ae5
n/a (libglib-2.0.so.0)
  #5  0x7fe4598ac049
start_thread (libpthread.so.0)
  #6  0x7fe459e3bf0f
__clone (libc.so.6)

  Stack trace of thread 1135:
  #0  0x7fe4598b21ad
pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
  #1  0x7fe45a6d2ccc
__gthread_cond_wait (libstdc++.so.6)
  #2  0x7fe45b9aac79
_ZN7bmalloc9AsyncTaskINS_4HeapEMS1_FvvEE13threadR
  #3  0x7fe45b9aadca
_ZN7bmalloc9AsyncTaskINS_4HeapEMS1_FvvEE16threadE
  #4  0x7fe45a6d900f
execute_native_thread_routine (libstdc++.so.6)
  #5  0x7fe4598ac049
start_thread (libpthread.so.0)
  #6  0x7fe459e3bf0f
__clone (libc.so.6)

  Stack trace of thread 1138:
  #0  0x7fe459e31e9d
poll (libc.so.6)
  #1  0x7fe463d4bc09
n/a (libglib-2.0.so.0)
  #2  0x7fe463d4bd1c
g_main_context_iteration (libglib-2.0.so.0)
  #3  0x7fe4638f6061
_ZN20QEventDispatcherGlib13processEventsE6QFlagsI
  #4  0x7fe463899ffb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFl
  #5  0x7fe4636b340e
_ZN7QThread4execEv (libQt5Core.so.5)
  #6  0x7fe459ad7396
n/a (libQt5DBus.so.5)
  #7  0x7fe4636b815b
n/a (libQt5Core.so.5)
  #8  0x7fe4598ac049
start_thread (libpthread.so.0)
  #9  0x7fe459e3bf0f
__clone (libc.so.6)

  Stack trace of thread 1167:
  #0  0x7fe459e31e9d
poll (libc.so.6)
  #1  0x7fe463d4bc09
n/a (libglib-2.0.so.0)
  #2  0x7fe463d4bd1c
g_main_context_iteration (libglib-2.0.so.0)
  #3  0x7fe44051c55d
n/a (libdconfsettings.so)
  #4  0x7fe463d72ae5
n/a (libglib-2.0.so.0)
  #5  

[Ring] Multitude Of Problems From Unsent Messages, To UI Functions Not Working

[Nathan Royce]

Ran a recent test with a "stranger(?)" and noticed some issues:

Setup:
Me: 1) Android (bootstrapped to bootstrap.ring.cx), 2) Linux PC
(bootstrapped to local server, gnome client). Both linked together.
Stranger: Linux

1) Some messages don't get sent (or get lost?).
Stranger started with trying to send a message, and I showed as being online.
One has to request first? I think that's what android said.

I started with "test" from my android, and "test1" from my pc.
Stranger saw "test1", but not "test".
Later testing showed that a message from my pc was not sending while
android did (vice-versa in the first test).
Of course, the unsent message also doesn't get synced to the linked device.

2) Conversations can't be deleted on the PC.
3) Contact doesn't get listed under Contact icon on PC.
4) Add/Remove to contact context menu item does nothing except change
the item state.
5) There should be a Contacts view in android like there is on the PC.
Even though you can add a contact in the android native contacts, it
would be better to have a list of filtered ring users showing in ring.

Are these issues that the developers had not already encountered in
their own tests?
I can't imagine how these issues could have existed and the
application been considered stable or the version bumped up to 1.0.

If a dev would like to test it with me, we can meet up on IRC.

[Ring] Android Crash After Creation Or Device Link

[Nathan Royce]

Android app crashes after successful creation of an account or
successfully linking a device.
After that initial crash, every attempt to open the app results in a
crash until I clear the app data.

*
F/libc( 2629): Fatal signal 11 (SIGSEGV) at 0x (code=1),
thread 4125 (pool-1-thread-1)
I/Vold(  300): [LGE][VOLD][NetlinkHandler.cpp][onEvent()]
subsys:cpu, action:0
I/DEBUG   ( 1806): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG   ( 1806): Build fingerprint:
'lge/x5_spr_us/x5:4.4.2/KOT49I.LS740ZV6/LS740ZV6.1440117223:user/release-keys'
I/DEBUG   ( 1806): Revision: '6'
I/DEBUG   ( 1806): pid: 2629, tid: 4125, name: pool-1-thread-1  >>> cx.ring <<<
I/DEBUG   ( 1806): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault
addr 
I/ActivityManager( 2431): Timeline: Activity_windows_visible id:
ActivityRecord{42f1afd8 u0 cx.ring/.client.HomeActivity t31}
time:8207018
V/ActivityManager( 2431): Moving to FINISHING: ActivityRecord{41eb89f0
u0 cx.ring/.client.AccountWizard t31 f}
V/ActivityManager( 2431): Moving to DESTROYING:
ActivityRecord{41eb89f0 u0 cx.ring/.client.AccountWizard t31 f}
(destroy requested)
I/DEBUG   ( 1806): r0   r1   r2   r3 
I/DEBUG   ( 1806): r4   r5 64e6fac8  r6   r7 64e6fb08
I/DEBUG   ( 1806): r8 62a1dc50  r9 64e6fc40  sl 64e6fac8  fp 64e6fd10
I/DEBUG   ( 1806): ip 6123fb7c  sp 64e6fa30  lr 40130719  pc
40128520  cpsr 40070030
I/DEBUG   ( 1806): d0    d1  
I/DEBUG   ( 1806): d2    d3  
I/DEBUG   ( 1806): d4  4a416f74654d484b  d5  594b537043556d30
I/DEBUG   ( 1806): d6  42393072496a6b64  d7  5676785a4c783277
I/DEBUG   ( 1806): d8    d9  
I/DEBUG   ( 1806): d10   d11 
I/DEBUG   ( 1806): d12   d13 
I/DEBUG   ( 1806): d14   d15 
I/DEBUG   ( 1806): d16 607bfe335002  d17 
I/DEBUG   ( 1806): d18   d19 
I/DEBUG   ( 1806): d20   d21 634e8088000a
I/DEBUG   ( 1806): d22   d23 
I/DEBUG   ( 1806): d24 3f53535a49481831  d25 3fc2f112df3e5244
I/DEBUG   ( 1806): d26 40026bb1bbb55516  d27 4000
I/DEBUG   ( 1806): d28 40008df2d49d41f1  d29 3fb0f4a31edab38b
I/DEBUG   ( 1806): d30 3ff0  d31 3f4de16b9c24a98f
I/DEBUG   ( 1806): scr 6010
I/DEBUG   ( 1806):
I/DEBUG   ( 1806): backtrace:
I/DEBUG   ( 1806): #00  pc 00023520  /system/lib/libc.so (strlen+83)
I/DEBUG   ( 1806): #01  pc 0002b715  /system/lib/libc.so (strdup+4)
I/DEBUG   ( 1806): #02  pc 006d4a07
/data/app-lib/cx.ring-1/libring.so
(restbed::detail::HttpImpl::to_bytes(std::__ndk1::shared_ptr
const&)+1578)
I/DEBUG   ( 1806):
I/DEBUG   ( 1806): stack:
I/DEBUG   ( 1806):  64e6f9f0  633c081f
I/DEBUG   ( 1806):  64e6f9f4  613a8500
I/DEBUG   ( 1806):  64e6f9f8  633c07e0
I/DEBUG   ( 1806):  64e6f9fc  633c07e0
I/DEBUG   ( 1806):  64e6fa00  64e6fac8  [stack:4125]
I/DEBUG   ( 1806):  64e6fa04  64e6fac8  [stack:4125]
I/DEBUG   ( 1806):  64e6fa08  64e6fd10  [stack:4125]
I/DEBUG   ( 1806):  64e6fa0c  60830105
/data/app-lib/cx.ring-1/libring.so
(restbed::String::uppercase(std::__ndk1::basic_string
const&)+36)
I/DEBUG   ( 1806):  64e6fa10  0001
I/DEBUG   ( 1806):  64e6fa14  633c07e0
I/DEBUG   ( 1806):  64e6fa18  64e6fc40  [stack:4125]
I/DEBUG   ( 1806):  64e6fa1c  62a1dc50
I/DEBUG   ( 1806):  64e6fa20  64e6fc40  [stack:4125]
I/DEBUG   ( 1806):  64e6fa24  64e6fac8  [stack:4125]
I/DEBUG   ( 1806):  64e6fa28  64e6fd10  [stack:4125]
I/DEBUG   ( 1806):  64e6fa2c  64e6fac8  [stack:4125]
I/DEBUG   ( 1806): #00  64e6fa30  
I/DEBUG   ( 1806):    
I/DEBUG   ( 1806): #01  64e6fa30  
I/DEBUG   ( 1806):  64e6fa34  64e6fac8  [stack:4125]
I/DEBUG   ( 1806):  64e6fa38  64e6faa0  [stack:4125]
I/DEBUG   ( 1806):  64e6fa3c  60839a0b
/data/app-lib/cx.ring-1/libring.so
(restbed::detail::HttpImpl::to_bytes(std::__ndk1::shared_ptr
const&)+1582)
I/DEBUG   ( 1806): #02  64e6fa40  64e6fa68  [stack:4125]
I/DEBUG   ( 1806):  64e6fa44  62a1ed18
I/DEBUG   ( 1806):  64e6fa48  613a2bf8
I/DEBUG   ( 1806):  64e6fa4c  604c3fe0
/data/app-lib/cx.ring-1/libring.so
(std::__ndk1::char_traits::copy(char*, char const*, unsigned
int)+68)
I/DEBUG   ( 1806):  64e6fa50  64e6fb68  [stack:4125]
I/DEBUG   ( 1806):  64e6fa54  613a2bf8
I/DEBUG   ( 1806):  64e6fa58  64e6fb64  [stack:4125]
I/DEBUG   ( 1806):  64e6fa5c  61cfff70
I/DEBUG   ( 1806):  64e6fa60  629a78b0
I/DEBUG   ( 1806):  

Re: [Ring] Fwd: Gnome Contact Names

[Nathan Royce]

Video 2: I should've looked first before sending the last message, but
webkitwebprocess is still using 40-45% when ring is open (visible),
and 22-27% when minimized.
I think the only reason I looked during the screen-capture is because
my fan was really kicking after opening ring. It is unrelated to
miracast/obs (as expected).

On Mon, Aug 7, 2017 at 3:24 PM, Sébastien Blin
 wrote:
> Hi Nathan.
>
> First, thanks for the videos it's very useful.
>
> I can't answer now about your first video.
>
> Video 2: => Wow... not good (and weird). Which distrib do you use? And
> did you install Ring from the official package or build it from sources?
>
> Video 3 + your note: We are currently working on this issue. It will be
> fixed in a few weeks. The thing is when you add/remove contacts, the
> VCard can be duplicated and you'll have multiple contacts.
>
> Have a nice day,
>
> Sébastien.

Re: [Ring] Fwd: Gnome Contact Names

[Nathan Royce]

Video 2: Dist=Archlinux, Ring=Manually built from the latest git
(daemon, lrc, gnome (git fetch/pull all up to date since today))
following the same method listed in the PKGBUILD in the AUR.
This is the first time I noticed it happening. I might use miracast
and obs to see if it can be replicated (though I don't see the
correlation).

I should put this out there, my internet goes through cellular so I
may be affected by double/triple NAT. I first found out about this
possibility when my server no longer could be reached from the
internet (ddns used) and I'd get different results when using
different sites to get my ip address.
arch client -> arch server -> wifi (dmz to server) -> cellular
android --> wifi -> cellular

Oh, something else I didn't mention (though may have been in a
previous post) is that while conversations can be deleted from
android, not so with gnome, nor is there an option to block contacts.

On Mon, Aug 7, 2017 at 3:24 PM, Sébastien Blin
 wrote:
> Hi Nathan.
>
> First, thanks for the videos it's very useful.
>
> I can't answer now about your first video.
>
> Video 2: => Wow... not good (and weird). Which distrib do you use? And
> did you install Ring from the official package or build it from sources?
>
> Video 3 + your note: We are currently working on this issue. It will be
> fixed in a few weeks. The thing is when you add/remove contacts, the
> VCard can be duplicated and you'll have multiple contacts.
>
> Have a nice day,
>
> Sébastien.

[Ring] Gnome Contact Names

[Nathan Royce]

When does a contact displayed name change from the ring id to a name?

Maybe allow the client to manually create a nickname in case of same peer names.

I submitted a contact request and my peer accepted, but the ring id
still showed until I started a call or something.
Even then, there were 2 instances of the same conversation listed in
the conversation tab, 1 with the ring id, the other with the name.
Adding/removing contact was jacked in this case, but after gnome
crashed (from a previous report), the contact and conversation is
showing correctly.

[Ring] Android Notifications

[Nathan Royce]

There is a notification for EVERY message received.

A notification should ONLY occur when ring isn't the focused app.

When ring is NOT focused, a notification probably shouldn't happen for
every message received from the same peer, or at least group the
messages (like slickdeals does).

Also don't vibrate a notification for every notification, but only if
there is NOT already a ring notification.
For example, first notification from a new message vibrates, another 5
messages received do not vibrate while the user has not swiped away
notification, user swipes away notification group, new message is
received and device vibrates (again, while ring is not focused app).

[Ring] Duplicate Messages Received In Android

[Nathan Royce]

Sent a message from gnome, received it twice on android.
It happened multiple times, but when I closed out ring on android,
sent another message from gnome, opened the notification on android,
the message received was single uhhh, I take that back, from the
corner of my eye, I saw the duplicate show up.

Every message is duplicated... Hm, while I've seen duplicates before,
I think they were temporary. But I DID just rebuild the daemon, lrc
and gnome client after fetching the latest PRs.

Whatever the case, when I close out ring on android and reopen, all
the duplicates become single.

[Ring] Android Not Sending Anymore

[Nathan Royce]

Sooo very weird. I closed out of ring on android and maybe 10 minutes
after I sent the last message (unknown since I had deleted the
conversation and blocked), it finally arrived in gnome, though there
are many other messages that did not arrive.

[Ring] Coredump From Accepting Contact Request

[Nathan Royce]

Per IRC earlier, I submit here the coredump which occurred on my first
use of gnome-client and accepting a contact request.
It comes from the latest
daemon(0d7545cb034d6222511ef42329c6d540bcc955f6)/lrc(0137d9f3585161bdca6426f0a6ce94abcf1ca33b)/gnome-client(8dcd25426d58df55bc5429f59c8da2bdf74627ec)
git:
*
Process 16737 (gnome-ring) of user 1000 dumped core.

   Stack trace of thread 16737:
   #0  0x7fa590ab38a0
raise (libc.so.6)
   #1  0x7fa590ab4f09
abort (libc.so.6)
   #2  0x7fa591428d77
_ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6)
   #3  0x7fa5914268e6
_ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6)
   #4  0x7fa591426933
_ZSt9terminatev (libstdc++.so.6)
   #5  0x7fa591426b88
__cxa_throw (libstdc++.so.6)
   #6  0x7fa591451223
_ZSt20__throw_out_of_rangePKc (libstdc++.so.6)
   #7  0x55bdfd7bddcd
_ZNSt3mapImN3lrc3api11interaction4InfoESt4lessImESaISt4pairIKmS3_EEE2atERS7_
(gnome-ring)
   #8  0x55bdfd7bbaee
create_and_fill_model (gnome-ring)
   #9  0x55bdfd7bcc6b
_ZZL24build_conversations_viewP18_ConversationsViewENKUlvE0_clEv
(gnome-ring)
   #10 0x55bdfd7bdb0e
call (gnome-ring)
   #11 0x55bdfd7bda88
call, void> (gnome-ring)
   #12 0x55bdfd7bda2c
impl (gnome-ring)
   #13 0x7fa59a92b24f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
   #14 0x55bdfd75a8a6
_ZZL13ring_init_lrcP15_RingMainWindowRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcNKUlS8_E2_clES8_
(gnome-ring)
   #15 0x55bdfd761fc8
call (gnome-ring)
   #16 0x55bdfd761d50
call&>, void> (gnome-ring)
   #17 0x55bdfd7618cc
impl (gnome-ring)
   #18 0x7fa59a92b24f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
   #19 0x7fa59d29c305
_ZNK3lrc3api17ConversationModel15newConversationERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(libringclient.so.1.0.0)
   #20 0x7fa59d2a37e8
_ZN3lrc22ConversationModelPimpl16slotContactAddedERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(libringclient.so.1.0.0)
   #21 0x7fa59a92b24f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
   #22 0x7fa59d288fa5
_ZNK3lrc3api12ContactModel12contactAddedERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(libringclient.so.1.0.0)
   #23 0x7fa59d290583
_ZN3lrc17ContactModelPimpl16slotContactAddedERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_b
(libringclient.so.1.0.0)
   #24 0x7fa59a92b24f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
   #25 0x7fa59d34030b
_ZN3lrc16CallbacksHandler12contactAddedERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_b
(libringclient.so.1.0.0)
   #26 0x7fa59d2de59d
_ZN3lrc16CallbacksHandler16slotContactAddedERK7QStringS3_b
(libringclient.so.1.0.0)
   #27 0x7fa59a92b24f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
   #28 0x7fa59d32688b
_ZN29ConfigurationManagerInterface12contactAddedERK7QStringS2_b
(libringclient.so.1.0.0)
   #29 0x7fa59d328a0b
_ZN29ConfigurationManagerInterface18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv
(libringclient.so.1.0.0)
   #30 0x7fa59d32a675
_ZN29ConfigurationManagerInterface11qt_metacallEN11QMetaObject4CallEiPPv
(libringclient.so.1.0.0)
   #31 0x7fa590814abd
n/a (libQt5DBus.so.5)
   #32 0x7fa59a92bb72
_ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
   #33 0x7fa59a8fb552

Re: [Ring] Settings Cancel Button

[Nathan Royce]

Copied/Pasted:
I will not be creating another account just to open an "issue".
I have a github account and an account for gnu (which encompasses
multiple projects) and am not keen on creating another account solely
for ring issues.
You have the information here in the mailing-list (what is the ML
for?) and that is good enough for me.
Feel free to post it on tuleap yourself. You have my permission.

I don't know why you would force a user to accept any changes made to settings.
The changes could be accidental and a Cancel button would allow them
to leave the settings as they were previously and come back in and try
again to make any changes. EG. changing the bootstrap address without
first saving the existing value somewhere else as a backup, then
hoping the default can be found via some online search.

On Mon, Dec 11, 2017 at 7:52 AM, Nicolas Jäger
 wrote:
> Hi,
>
> Could you open a enhancement issue on tuleap ? https://tuleap.ring.cx/
>
> not sure it will accepted though.
>
> thank you.
>
> Nicolas Jäger
> (514) 276-5468 Poste 121

Re: [Ring] Android Call StatusBar Exception/MultiDex

[Nathan Royce]

Nope, still no go.
I even went to that icon site and took a very simplistic one, but alas
that failed as well:
http://schemas.android.com/apk/res/android;
android:height="24dp"
android:width="24dp"
android:viewportWidth="24"
android:viewportHeight="24">



I'm sure you could test it on your side without an old phone by just
making a temporary notification message display on loading and using a
virtual kitkat device.

On Fri, May 4, 2018 at 4:38 PM, Pierre Duchemin
 wrote:
> Thank you Nathan for this report.
>
> This issue is quite common on Android.
> It's caused by the library that convert vector pictures to raster in order to 
> keep compatibility with api < 21.
>
> However, vectors brings lots of improvements so I'd rather find a vector that 
> don't make the lib crash instead of using a png like you did.
>
> Here is a patch for this issue:
> https://gerrit-ring.savoirfairelinux.com/#/c/9374/
> The vector drawable is taken from http://materialdesignicons.com/ and look 
> like the old one.
>
> Since the emulator is crashing on call and our oldest phones are out of 
> order, I was not able to test it.
> Can you tell me if it helps?

Re: [Ring] Android Call StatusBar Exception/MultiDex

[Nathan Royce]

Re-sending since I neglected to Reply-To-All...
I pulled the latest commit (81cb605e6c72c9947826ad489898a4deb0abe1b6)
which also included the previous fix for Android 4.4 and can confirm I
don't have issue sending/receiving calls, so it can be pushed to the
Play Store.

On Fri, May 4, 2018 at 4:38 PM, Pierre Duchemin
 wrote:
> Thank you Nathan for this report.
>
> This issue is quite common on Android.
> It's caused by the library that convert vector pictures to raster in order to 
> keep compatibility with api < 21.
>
> However, vectors brings lots of improvements so I'd rather find a vector that 
> don't make the lib crash instead of using a png like you did.
>
> Here is a patch for this issue:
> https://gerrit-ring.savoirfairelinux.com/#/c/9374/
> The vector drawable is taken from http://materialdesignicons.com/ and look 
> like the old one.
>
> Since the emulator is crashing on call and our oldest phones are out of 
> order, I was not able to test it.
> Can you tell me if it helps?

[Ring] Android Crash; Windows Update; Gnome Tray

[Nathan Royce]

I think I found the cause for the android (kitkat/4.4.2) crash when it
came to calls...

I came across "multidex" in my searching and when I went to analyze
the apk using Android Studio, I see it say it has 29413 methods AND
references 36906 methods, exceeding the 64K method limit.

https://developer.android.com/studio/build/multidex

[Ring] Gnome Crash

[Nathan Royce]

I just did a fetch/pull/compile (daemon/lrc/gnome)/install as well as
installed the android client, and I got a crash dump after accepting
the chat sent from my android client and I think I started to type
back in gnome. I did notice what I sent from my android client was
displayed twice in gnome before crashing.
*
Apr 30 03:55:40 computername systemd-coredump[17629]: Process 17395
(gnome-ring) of user 1000 dumped core.

Stack trace of thread 17395:
#0  0x5636593893e4
_ZNKSt15__uniq_ptr_implIN3lrc3api12ContactModelESt14default_deleteIS2_EE6_M_ptrEv
(gnome-ring)
#1  0x563659388842
_ZNKSt10unique_ptrIN3lrc3api12ContactModelESt14default_deleteIS2_EE3getEv
(gnome-ring)
#2  0x563659387b48
_ZNKSt10unique_ptrIN3lrc3api12ContactModelESt14default_deleteIS2_EEptEv
(gnome-ring)
#3  0x5636593db36c
chat_view_update_temporary (gnome-ring)
#4  0x563659383094
slotShowChatView (gnome-ring)
#5  0x56365938050e
_ZZN12_GLOBAL__N_17details7CppImpl9updateLrcERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_ENKUlS9_N3lrc3api12conversation4InfoEE4_clES9_SD_
(gnome-ring)
#6  0x563659386ba6
call (gnome-ring)
#7  0x563659386754
call&, const
lrc::api::conversation::Info&>, void> (gnome-ring)
#8  0x56365938645c
impl (gnome-ring)
#9  0x7f910f98a72f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#10 0x7f91125510e7
_ZNK3lrc3api18BehaviorController12showChatViewERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS0_12conversation4InfoE
(libringclient.so.1.0.0)
#11 0x7f9112505246
_ZNK3lrc3api17ConversationModel18selectConversationERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(libringclient.so.1.0.0)
#12 0x5636593e5288
select_conversation (gnome-ring)
#13 0x7f91100ebc96
n/a (libgobject-2.0.so.0)
#14 0x7f91101079e9
g_signal_emit_valist (libgobject-2.0.so.0)
#15 0x7f9110108130
g_signal_emit (libgobject-2.0.so.0)
#16 0x7f9111cff49f
gtk_tree_selection_select_path (libgtk-3.so.0)
#17 0x7f9111cff5ae
gtk_tree_selection_select_iter (libgtk-3.so.0)
#18 0x5636593e677a
conversations_view_select_conversation (gnome-ring)
#19 0x5636593820fb
slotFilterChanged (gnome-ring)
#20 0x56365938044b
_ZZN12_GLOBAL__N_17details7CppImpl9updateLrcERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_ENKUlvE1_clEv
(gnome-ring)
#21 0x563659386a3d
call (gnome-ring)
#22 0x5636593866d6
call, void> (gnome-ring)
#23 0x5636593862b8
impl (gnome-ring)
#24 0x7f910f98a72f
_ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#25 0x563659380f82
updateLrc (gnome-ring)
#26 0x56365937fed1
onAccountSelectionChange (gnome-ring)
#27 0x56365937b440
on_account_changed (gnome-ring)
#28 0x7f91100eba4d
g_closure_invoke (libgobject-2.0.so.0)
#29 0x7f91100fee40
n/a (libgobject-2.0.so.0)
#30 0x7f91101076f6
g_signal_emit_valist (libgobject-2.0.so.0)
#31 0x7f9110108130
g_signal_emit (libgobject-2.0.so.0)
#32 0x7f9111b02c7b
n/a (libgtk-3.so.0)
#33 0x7f9111b05398
gtk_combo_box_set_active (libgtk-3.so.0)
#34 0x56365937fa19
refreshAccountSelectorWidget (gnome-ring)
#35 0x563659381469
slotAccountStatusChanged 

[Ring] Android Call StatusBar Exception/MultiDex

[Nathan Royce]

Looks like the reply I made to my other thread actually needs to be a
new different thread.
*
05-03 15:27:06.947 1029-1198/? D/WifiNative-wlan0: doString: SIGNAL_POLL
05-03 15:27:07.007 1215-1215/? E/StatusBar: couldn't inflate view for
notification cx.ring/0xf83e638

android.content.res.Resources$NotFoundException: File
res/drawable/ic_call_end_white.xml from drawable resource ID
#0x7f08006f
at
android.content.res.Resources.loadDrawable(Resources.java:2136)
at
android.content.res.Resources.getDrawable(Resources.java:715)
at
android.widget.TextView.setCompoundDrawablesRelativeWithIntrinsicBounds(TextView.java:2377)
at
android.widget.RemoteViews$TextViewDrawableAction.apply(RemoteViews.java:1417)
at
android.widget.RemoteViews.performApply(RemoteViews.java:2458)
at
android.widget.RemoteViews.apply(RemoteViews.java:2417)
at
android.widget.RemoteViews$ViewGroupAction.apply(RemoteViews.java:1345)
at
android.widget.RemoteViews.performApply(RemoteViews.java:2458)
at
android.widget.RemoteViews.apply(RemoteViews.java:2417)
at
com.android.systemui.statusbar.BaseStatusBar.inflateViews(BaseStatusBar.java:732)
at
com.android.systemui.statusbar.BaseStatusBar.createNotificationViews(BaseStatusBar.java:938)
at
com.android.systemui.statusbar.phone.PhoneStatusBar.addNotification(PhoneStatusBar.java:1307)
at
com.android.systemui.statusbar.CommandQueue$H.handleMessage(CommandQueue.java:326)
at
android.os.Handler.dispatchMessage(Handler.java:102)
at
android.os.Looper.loop(Looper.java:136)
at
android.app.ActivityThread.main(ActivityThread.java:5103)
at
java.lang.reflect.Method.invokeNative(Native Method)
at
java.lang.reflect.Method.invoke(Method.java:515)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:606)
at
dalvik.system.NativeStart.main(Native Method)
 Caused by:
org.xmlpull.v1.XmlPullParserException: Binary XML file line #1:
invalid drawable tag vector
at
android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:933)
at
android.graphics.drawable.Drawable.createFromXml(Drawable.java:877)
at
android.content.res.Resources.loadDrawable(Resources.java:2132)
at
android.content.res.Resources.getDrawable(Resources.java:715)
at
android.widget.TextView.setCompoundDrawablesRelativeWithIntrinsicBounds(TextView.java:2377)
at
android.widget.RemoteViews$TextViewDrawableAction.apply(RemoteViews.java:1417)
at
android.widget.RemoteViews.performApply(RemoteViews.java:2458)
at
android.widget.RemoteViews.apply(RemoteViews.java:2417)
at
android.widget.RemoteViews$ViewGroupAction.apply(RemoteViews.java:1345)
at
android.widget.RemoteViews.performApply(RemoteViews.java:2458)
at
android.widget.RemoteViews.apply(RemoteViews.java:2417)
at
com.android.systemui.statusbar.BaseStatusBar.inflateViews(BaseStatusBar.java:732)
at
com.android.systemui.statusbar.BaseStatusBar.createNotificationViews(BaseStatusBar.java:938)
at
com.android.systemui.statusbar.phone.PhoneStatusBar.addNotification(PhoneStatusBar.java:1307)
at
com.android.systemui.statusbar.CommandQueue$H.handleMessage(CommandQueue.java:326)
at
android.os.Handler.dispatchMessage(Handler.java:102)

Re: [Ring] Android Crash; Windows Update; Gnome Tray

[Nathan Royce]

Yeah, the apk I analyzed was the one that I compiled (commit
e7c305c0d2f387ed66b605aefa89f63cf18fe863)
Interesting that android studio 3.0.1 never complained about it during
compilation, analyzed what was built and showed those numbers I
mentioned earlier, installed and ran the debug apk.

On Thu, May 3, 2018 at 8:57 AM, Pierre Duchemin
 wrote:
> Hi Nathan,
>
> I just analyzed the apk files produced by our CI system.
> I don't have the same results.
> Can you tell us where did you downloaded you apk file from and explain how 
> you got theses results?
>
> Furthermore, if you try to compile such an apk, Android studio would throws 
> that kind of error:
>
> com.android.dex.DexIndexOverflowException: method ID not in [0, 0x]: 65536
> at com.android.dx.merge.DexMerger$6.updateIndex(DexMerger.java:502)
> at com.android.dx.merge.DexMerger$IdMerger.mergeSorted(DexMerger.java:277)
> at com.android.dx.merge.DexMerger.mergeMethodIds(DexMerger.java:491)
> at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:168)
> at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
> at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
> at com.android.dx.command.dexer.Main.runMonoDex(Main.java:302)
> at com.android.dx.command.dexer.Main.run(Main.java:245)
> at com.android.dx.command.dexer.Main.main(Main.java:214)
> at com.android.dx.command.Main.main(Main.java:106)
>
> At this time, our apk compile without any error.
>
> Pierre Duchemin
> Free software consultant | Montreal, Qc
> Savoir-faire Linux
> Ring: pierreduchemin
>
> Confidentiality Message: This communication (including any files
> transmitted with it) is intended solely for the person or entity
> to whom it is addressed, and may contain confidential or
> privileged information.
> The disclosure, distribution or copying of this message is
> strictly forbidden. Should you have received this communication
> in error, kindly contact the sender promptly, destroy any copies
> and delete this message from your computer system.

[Ring] Android 4.4.2 Crash On Message Reception (Notification)

[Nathan Royce]

Fix one issue, and another lies beneath...
When I send a message to my android device:
*
W/BrunchUsedCodecImpl( 4376): [isUsedCodec] Used codec! = audio/vorbis
V/MediaPlayer[Native](16140): message received msg=8, ext1=0, ext2=0
V/MediaPlayer[Native](16140): notify(8, 0, 0) callback on disconnected
mediaplayer
E/NotificationService( 5203): unable to notify listener (removed):
android.service.notification.INotificationListener$Stub$Proxy@426a2188
E/NotificationService( 5203): android.os.DeadObjectException
E/NotificationService( 5203): at android.os.BinderProxy.transact(Native Method)
E/NotificationService( 5203): at
android.service.notification.INotificationListener$Stub$Proxy.onNotificationRemoved(INotificationListener.java:120)
E/NotificationService( 5203): at
com.android.server.NotificationManagerService$NotificationListenerInfo.notifyRemovedIfUserMatch(NotificationManagerService.java:278)
E/NotificationService( 5203): at
com.android.server.NotificationManagerService$3.run(NotificationManagerService.java:859)
E/NotificationService( 5203): at
android.os.Handler.handleCallback(Handler.java:733)
E/NotificationService( 5203): at
android.os.Handler.dispatchMessage(Handler.java:95)
E/NotificationService( 5203): at android.os.Looper.loop(Looper.java:136)
E/NotificationService( 5203): at
com.android.server.ServerThread.initAndLoop(SystemServer.java:1380)
E/NotificationService( 5203): at
com.android.server.SystemServer.main(SystemServer.java:1484)
E/NotificationService( 5203): at
java.lang.reflect.Method.invokeNative(Native Method)
E/NotificationService( 5203): at
java.lang.reflect.Method.invoke(Method.java:515)
E/NotificationService( 5203): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/NotificationService( 5203): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:606)
E/NotificationService( 5203): at dalvik.system.NativeStart.main(Native Method)
D/NotificationService( 5203): updateLightListLocked
:r=NotificationRecord(0x4303d320: pkg=cx.ring user=UserHandle{0}
id=-943724268 tag=null score=10: Notification(pri=1
contentView=cx.ring/0x1090064 vibrate=default sound=default
defaults=0x flags=0x11 kind=[null] 1 action)), action=2
D/NotificationService( 5203): notification=Notification(pri=1
contentView=cx.ring/0x1090064 vibrate=default sound=default
defaults=0x flags=0x11 kind=[null] 1 action)
D/EmotionalLed( 9865): updateLightListInternal: action=2 pkg=cx.ring
D/AndroidRuntime( 8508): Shutting down VM
W/dalvikvm( 8508): threadid=1: thread exiting with uncaught exception
(group=0x419aae48)
E/cx.ring.application.RingApplication( 8508): Uncaught Exception
detected in thread
E/cx.ring.application.RingApplication( 8508):
android.app.RemoteServiceException: Bad notification posted from
package cx.ring: Couldn't create icon: StatusBarIcon(pkg=cx.ringuser=0
id=0x7f080097 level=0 visible=true num=0 )
E/cx.ring.application.RingApplication( 8508): at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1367)
E/cx.ring.application.RingApplication( 8508): at
android.os.Handler.dispatchMessage(Handler.java:102)
E/cx.ring.application.RingApplication( 8508): at
android.os.Looper.loop(Looper.java:136)
E/cx.ring.application.RingApplication( 8508): at
android.app.ActivityThread.main(ActivityThread.java:5103)
E/cx.ring.application.RingApplication( 8508): at
java.lang.reflect.Method.invokeNative(Native Method)
E/cx.ring.application.RingApplication( 8508): at
java.lang.reflect.Method.invoke(Method.java:515)
E/cx.ring.application.RingApplication( 8508): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/cx.ring.application.RingApplication( 8508): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:606)
E/cx.ring.application.RingApplication( 8508): at
dalvik.system.NativeStart.main(Native Method)
I/Process ( 8508): Sending signal. PID: 8508 SIG: 9
V/AwesomePlayer( 4376): track of type 'audio/vorbis' does not publish bitrate
*

Re: [Ring] Stability and communication issues with ring-gnome 20180201.1.1c179b2

[Nathan Royce]

Hey Baptiste, thanks for maintaining the arch package.

What was suggested to me before was to run dring with --console and
--debug. With that, I was able to find a certificate problem that
caused messages to be dropped.

HOWEVER, I do still experience messages not arriving/sending and
sometimes arriving an hour later. And that has been a lng ongoing
issue for months that just won't be recognized. Even the KDE client
dev experienced it and I think an opendht dev chatted with us in IRC
and sounds like the issue was just going to be tossed off to the side
(really torqued off the 2 of us).
I don't even see the KDE client dev's name (elv13) in IRC chat
anymore. Don't know if it relates to KDE essentially being kicked out
of the car.

I can't test it anymore since the app for android 4.4 broke again
(which I posted about, but still no reply).

I still contend this program is nowhere near 1.0 in terms of
functionality/stability (based on my nearly unusable experience).

Man, they really want people to use their tuleap, even though you
provide them with the info in the ML. I never will.

On Fri, Feb 2, 2018 at 10:52 AM, Guillaume Roguez
 wrote:
> Hi Baptiste,
>
> Is the Android account was accepted as contacts on the gnome client side?
> I mean do you have accepted the Android trust request on the gnome client 
> before?
>
> - Le 2 Fév 18, à 3:59, Baptiste Jonglez bapti...@bitsofnetworks.org a 
> écrit :
>
>> Hi,
>>
>> The latest update (20180201.1.1c179b2, with opendht 1.6.0rc1 and so on, on
>> Arch Linux) seems a bit buggy:
>>
>> - with the gnome client, trying to send text messages to an Android client
>>  never completes, and the ring-daemon process goes to 100% CPU
>>
>> - but I can successfully receive text messages from the same Android client
>>
>> - similarly, I can successfully call from Android to Gnome, but the fails
>>  after a few seconds when trying to call from Gnome to Android
>>
>> - when stopping the Gnome client, WebKitWebProces crashes with a segfault,
>>  I have attached the stacktrace to this email (not sure it is useful but
>>  anyway)
>>
>> Hopes this helps,
>> Baptiste
>

Re: [Ring] Android 4.4.2 Crash On Message Reception (Notification)

[Nathan Royce]

The android update I installed today/yesterday is working with no
problems so far... AND... wait for it... from trying various bootstrap
tests I've posted about before (ring/ring;ring/local;local/local),
messages are both sending AND receiving at both linux and android!
MAJOR DEAL! I hope it's not a fluke.

The only thing is with gnome client in KDE, X still won't
close/minimize the window, but I believe I already posted about that.
I have to use Quit from the system tray icon context menu.

Arch Linux opendht: 1:1.5.0-2 (waiting for 1.6, but am aware of the
issues that were posted here recently)
daemon: 9179735a649cc0167e1312625d17f8d08a0c2587
lrc: 1f7b84cd7b8cb71fd2d5eb525e3130807b6842fa
gnome client: a8804820558189ceac7fda85223001ef6e7a5237

[Ring] Android Crash; Windows Update; Gnome Tray

[Nathan Royce]

There doesn't seem to have been any work done with windows/uwp for
months still...

I just updated android and gnome, and gnome still doesn't
close/minimize to the KDE system tray.

Android 4.4 v20180406 stacktrace:
*
D/RingApplication( 6900): onServiceConnected: cx.ring.service.DRingService
D/RingApplication( 6900): bootstrapDaemon: At least one camera
available. Initializing video...
E/RingApplication( 6900): Uncaught Exception detected in thread
E/RingApplication( 6900):
android.content.res.Resources$NotFoundException: File
res/drawable/ic_contact_picture_box_default.xml from drawable resource
ID #0x7f080079. If the resource you are trying to use is a vector
resource, you may be referencing it in an unsupported way. See
AppCompatDelegate.setCompatVectorFromResourcesEnabled() for more info.
E/RingApplication( 6900): at
android.content.res.Resources.loadDrawable(Resources.java:2136)
E/RingApplication( 6900): at
android.content.res.Resources.getDrawable(Resources.java:715)
E/RingApplication( 6900): at android.support.v4.content.a.a(Unknown Source)
E/RingApplication( 6900): at
cx.ring.contacts.AvatarFactory.createDefaultAvatar(Unknown Source)
E/RingApplication( 6900): at
cx.ring.contacts.AvatarFactory.getAvatar(Unknown Source)
E/RingApplication( 6900): at
cx.ring.contacts.AvatarFactory.getAvatar(Unknown Source)
E/RingApplication( 6900): at
cx.ring.contacts.AvatarFactory.getAvatar(Unknown Source)
E/RingApplication( 6900): at
cx.ring.navigation.RingNavigationFragment.updateUserView(Unknown
Source)
E/RingApplication( 6900): at
cx.ring.navigation.RingNavigationFragment.lambda$showViewModel$4$RingNavigationFragment(Unknown
Source)
E/RingApplication( 6900): at
cx.ring.navigation.RingNavigationFragment$$Lambda$4.run(Unknown
Source)
E/RingApplication( 6900): at android.os.Handler.handleCallback(Handler.java:733)
E/RingApplication( 6900): at android.os.Handler.dispatchMessage(Handler.java:95)
E/RingApplication( 6900): at android.os.Looper.loop(Looper.java:136)
E/RingApplication( 6900): at
android.app.ActivityThread.main(ActivityThread.java:5103)
E/RingApplication( 6900): at
java.lang.reflect.Method.invokeNative(Native Method)
E/RingApplication( 6900): at java.lang.reflect.Method.invoke(Method.java:515)
E/RingApplication( 6900): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/RingApplication( 6900): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:606)
E/RingApplication( 6900): at dalvik.system.NativeStart.main(Native Method)
E/RingApplication( 6900): Caused by:
org.xmlpull.v1.XmlPullParserException: Binary XML file line #2:
invalid drawable tag vector
E/RingApplication( 6900): at
android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:933)
E/RingApplication( 6900): at
android.graphics.drawable.Drawable.createFromXml(Drawable.java:877)
E/RingApplication( 6900): at
android.content.res.Resources.loadDrawable(Resources.java:2132)
E/RingApplication( 6900): ... 18 more
*

[Ring] Android Crash; Windows Update; Gnome Tray

[Nathan Royce]

Update, thanks to borschty in the gnome/gtk IRC channels who was able
to figure out that my .config/dconf/user file was corrupt and by
simply removing that file and letting it get recreated, Ring is now
able to minimize to the system tray.
Whoo Hoo! Thanks borschty.

So that's 1 down for the minimize to system tray.

[Ring] Archlinux Package Flagged At 1.7.4. Current Is 1.8.0

[Nathan Royce]

I'm hoping the Archlinux package can be updated soon.
I tried to build the latest daemon and am having build issues which I
think may be related.