9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] Drawterm on F-Droid
Date: Thu, 22 Dec 2022 10:37:01 +0900	[thread overview]
Message-ID: <a47e9622c1af8aa7a9d5200dbe2e0ff3@hera.eonet.ne.jp> (raw)
In-Reply-To: <43c5a00fec54b3766792bdf278e639ae@hera.eonet.ne.jp>

> On another BlissOS 15(android 12), drawterm crashes at the beginning.
> Hmm, very ....

I'm trying to this again.
I compiled drawterm-fdroid by the Make.android.config as:
SDKPREFIX=/home/okamoto/Android/Sdk
JAVA_HOME=/usr
BUILDTOOLS=30.0.2
PLATFORM=21
NDKPREFIX=/home/okamoto/Android/Sdk/ndk/25.1.8937393/toolchains/llvm/prebuilt/linux-x86_64/bin
~

and got drawterm.apk drawterm-unsigned.apk etc successfully.

I tryed to install those onto Android12 PC machine(Blissos 15), and got:
<<<for drawterm.apk>>>
adb install drawterm.apk
Performing Streamed Install
adb: failed to install drawterm.apk: Failure [INSTALL_FAILED_INVALID_APK: Scanning Failed.: Package /data/app/~~NFLd-f6pqvIYChr8tac-TA==/org.echoline.drawterm-Po8k-b3wqCVb8Hr7AquS0A==/base.apk code is missing]

<<<for drawterm-unsigned.apk>>>
okamoto@saturn:~/src/drawterm-fdroid$ adb install drawterm-unsigned.apk
Performing Streamed Install
adb: failed to install drawterm-unsigned.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed collecting certificates for /data/app/vmdl1159481301.tmp/base.apk: Failed to collect certificates from /data/app/vmdl1159481301.tmp/base.apk: Attempt to get length of null array]

I'm not familiar with android...
If someone can explain the meaning of above error messages...(Maybe I'm writung wrong place...).

Kenji


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T61300a35947fa972-Mb9645ba69fd4ddb564c4901d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2022-12-22  1:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  6:37 sirjofri
2022-10-01 10:55 ` mkf9
2022-10-02 18:26 ` ori
2022-10-02 20:02   ` sirjofri
2022-12-08  1:18 ` kokamoto
2022-12-09  2:21   ` kokamoto
2022-12-09  7:05     ` sirjofri
2022-12-10  1:13       ` kokamoto
2022-12-10  9:24         ` sirjofri
2022-12-15  3:07   ` kokamoto
2022-12-15  3:26     ` Kenji Okamoto
2022-12-15  8:24       ` sirjofri
2022-12-16  3:45     ` kokamoto
2022-12-22  1:37     ` kokamoto [this message]
2022-12-23  5:09       ` kokamoto
2022-12-23 10:17         ` sirjofri
2022-12-24  4:24           ` kokamoto
2022-12-24  7:24             ` kokamoto
2022-12-26  5:10               ` kokamoto
2022-12-26  5:14                 ` kokamoto
2022-12-27  4:43                   ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a47e9622c1af8aa7a9d5200dbe2e0ff3@hera.eonet.ne.jp \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).