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,
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
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
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
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
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
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
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
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
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.
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)
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
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
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
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.
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
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
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,
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
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
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
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
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
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.
24 matches
Mail list logo
