<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
<div class="moz-cite-prefix">On 14/11/2017 10:02, Simon Josefsson
wrote:<br>
</div>
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap="">Hi all. As far as I understand, the problem is a genuine Replicant ROM
bug that needs to be fixed. </pre>
</blockquote>
I think we have no element to say that.<br>
That's not to say it isn't. But we need more clues (dmesg and logcat
mainly) to determine where the issue lays.<br>
<br>
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap=""> The problematic DAVDroid version appears
to have been removed from fdroid so everything works fine now. </pre>
</blockquote>
Could be a clue that the problem was in the app itself.<br>
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap="">
Yesterday I upgraded the app 'Call Recorder', and experience something
similar to the DAVdroid boot-loop issue. With the new Call Recorder
app, replicant crashed and on startup 'Trebuchet crashed' just keeps
looping and the background icon page just comes and goes. Removing the
app resolves the issue. Does anyone else see this? Is this the same
ROM bug or something else?</pre>
</blockquote>
Again, it would be useful to have dmesg and logcat logs to get hints
as to where the crashes come from.
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap=""> It seems that whatever problem there is
with the DAVDroid/CallRecorder-apps, it should not be possible for an
app to cause these kind of problems with the phone.</pre>
</blockquote>
I don't know about those apps, but if an application has root access
there's very little (almost nothing) an operating system can do to
prevent damage (be it accidental or malicious).<br>
That's one of the main reasons root access is locked by default on
most (all?) phones on the market.<br>
<br>
Please - if you feel like and if you can - collect some logs about
those crashes, so that we can have a look and try to determine if
it's a Replicant project or not.<br>
If you need guidance doing so, you can email me in private or ask on
the forum.<br>
<br>
Cheers,<br>
<br>
Fil<br>
<br>
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap="">
/Simon</pre>
</blockquote>
<br>
Cheers,<br>
<br>
Fil<br>
<blockquote cite="mid:1510650165.19494.1.camel@josefsson.org"
type="cite">
<pre wrap="">
mån 2017-11-06 klockan 09:27 +0100 skrev Simon Josefsson:
</pre>
<blockquote type="cite">
<pre wrap="">lör 2017-11-04 klockan 12:09 +0100 skrev <a class="moz-txt-link-abbreviated" href="mailto:maurice@prtrc.net">maurice@prtrc.net</a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Simon
</pre>
<blockquote type="cite">
<pre wrap="">I am running Replicant 6.0 0002 on an i9300 and it has been
working
fine. It came with fdroid privileged extension pre-
installed. It
hasn't been possible to upgrade it because it was signed with a
different key, so I have been using the version that came with
6.0
0002.
After upgrading fdroid to 1.0.1, replicant crashes on installing
an
app
through fdroid. Replicant doesn't come up again, and just keeps
looping on startup (boot logo, adb works). After a factory reset
I
reproduced this (stock 0002 image, upgrade fdroid, install any
app
->
crash), so it seems like a geniune bug.
After another factory reset, I upgraded fdroid to 1.0.1 and
disabled
use of the privileged extension and installing apps works fine
and
doesn't cause replicant crashes.
1) Can anyone reproduce this?
</pre>
</blockquote>
<pre wrap="">
I can reproduce the crashing and looping, but for me it doesn't
work
with factory reset and disabling the privileged extension to
install
apps without crashing and looping again.
</pre>
</blockquote>
<pre wrap="">
The privileged extension was a red herring -- the culprit is apps
aapt2-built apk's. The DAVDroid 1.9.1 app in fdroid triggers
this. On
my tests above I didn't try to install DAVDroid, only some other
apps.
See more here:
<a class="moz-txt-link-freetext" href="https://forums.bitfire.at/topic/1603/replicant-lineage-1-9-1-causing">https://forums.bitfire.at/topic/1603/replicant-lineage-1-9-1-causing</a>-
in
stant-crash-and-bootloops
Indeed the way to recover from the bootloop is to (re)move the
/data/app/*davdroid* directory. Then your phone can boot and you can
revert back to davdroid 1.9 or (presumably) wait for 1.9.2.
Hopefully replicant 6 0003 can be released to fix the OS bug too?! I
believe Wolfgang found a patch to fix this.
/Simon</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Replicant mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Replicant@osuosl.org">Replicant@osuosl.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osuosl.org/mailman/listinfo/replicant">https://lists.osuosl.org/mailman/listinfo/replicant</a>
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>