Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 24 17:29
    @xeffyr banned @zhonjarlby
  • Aug 31 07:55
    @xeffyr banned @HackGod-RS
  • Aug 26 10:48
    @xeffyr banned @Tisaba
  • Jun 21 13:11
    @xeffyr banned @irem347
  • Jun 14 09:25
    @xeffyr banned @Rishabhjn7102
  • Jun 14 09:25
    User @xeffyr unbanned @Anarkista
  • Jun 02 10:29
    @xeffyr banned @Anarkista
  • Dec 22 2019 14:04
    User @xeffyr unbanned @httpRooLz
  • Dec 22 2019 14:04
    User @xeffyr unbanned @sdrausty
  • Sep 14 2019 10:52
    @xeffyr banned @httpRooLz
  • Jan 20 2019 16:28
    @xeffyr banned @sdrausty
RalfWerner
@RalfWerner
ok thanks i am not an expert like you:)
glow
@Neo-Oli
@xeffyr I think feh needs to be rebuild because of libexif upgrade
Leonid Pliushch
@xeffyr
Ok
Fahad Ali
@fahadali32
Hello i need help i got Some error like dlopen locate local sysmbol how can i fix this pls help expert please
GrimlerBot
@GrimlerBot
<kbeflo> @Grimler, can you please review my wpd PR on termux-root-packages. Build is still failing. Can you help me out?
Fahad Ali
@fahadali32
Hey developers please help me i can't install opencv
stacypowell29
@stacypowell29
I need help with this dpkg error code can someone help me please
Errors were encountered while processing:
/data/data/com.termux/files/usr/var/cache/apt/archives/libutil_0.4-1_aarch64.deb
E: Sub-process /data/data/com.termux/files/usr/bin/dpkg returned an error code (1)
stacypowell29
@stacypowell29
dpkg -i -D1 /data/data/com.termux/files/usr/var/cache/apt/archives/libutil_0.4-1_aarch64.deb
D000001: ensure_diversions: none, resetting
D000001: ensure_statoverrides: none, resetting
(Reading database ... 41968 files and directories currently installed.)
Preparing to unpack .../libutil_0.4-1_aarch64.deb ...
D000001: process_archive oldversionstatus=not installed
Unpacking libutil (0.4-1) ...
dpkg: error processing archive /data/data/com.termux/files/usr/var/cache/apt/archives/libutil_0.4-1_aarch64.deb (--install):
trying to overwrite '/data/data/com.termux/files/usr/lib/libutil.so', which is also in package ndk-sysroot 20-8
Errors were encountered while processing:
/data/data/com.termux/files/usr/var/cache/apt/archives/libutil_0.4-1_aarch64.deb
$
Leonid Pliushch
@xeffyr
@stacypowell29 What you are trying to do ? Why you need libutil ?
It was purged from repositories as unneeded since was replaced by libc when we switched to API 24.
RalfWerner
@RalfWerner
@xeffyr both of your *2?.apk versions work the same and treat commands ($c) as proot-exec, as well as my proot-wrapper u rt $c. The process check then shows two processes: proot in which$c is executed. I would have expected the behavior at *29.apk but not at *28.apk (in the manifest is compile/platform 28 but target still 29). Could you please create this version again?
Leonid Pliushch
@xeffyr

Could you explain what should be changed in APK ? Everything I did is just changed the target SDK version and nothing more. All code is same, from https://github.com/termux/termux-app/pull/1427/files. As TERMUX_ANDROID10=1 is set, the proot will be used regardless of SDK version.

I really can't understand why there should be difference in proot usage. Proot will be always used as soon as the compiled version is termux/termux-app#1427. The only difference you will see is SELinux behavior with non-proot'ed binaries.

And here is build protocol:
asciicast
Just to clear doubts about "same SDK".
stacypowell29
@stacypowell29
I cant install anything dpkg error
Leonid Pliushch
@xeffyr
@stacypowell29 I have asked: What you are trying to do ? Why you need libutil ? So please, answer to these questions.
As now you have I cant install anything dpkg error, I'm suggesting to reinstall Termux.
Also Android 5 (6) is out of support.
RalfWerner
@RalfWerner

Thank you @xeffyr with this version (shot 2) I can check better than with the previous one from Jun 19 (shot 1) In the 3rd shot you can see how env (prevents Bad address in a 4th emulation with your new *28.apk) and OTS ist possible too.
grafik
With your am patch I was able to install the current app (0.95) with Studio in api30 Emulator. Still impossible is:

s=storage; sd=/$s/emulated/0; a=Android/data/com.termux/files; [ ! -w $sd ]&& sd+=/$a; c=com.termux.app.reload_style; am broadcast --es $c $s -a $c com.termux

This is an extract from termux-setup-storage that should ask/allow for access to /$s and create 6-7 symlinks to 2-12 empty folders. First is important because otherwise $(dirname /storage/*-*/. (sdcard) won't work. Do you have experience with shared sdcard (*.img) with several emulators?

glow
@Neo-Oli
I think cryptsetup needs to be bumped because of libpopt
Henrik Grimler
@Grimler91
@Neo-Oli thanks, done
RalfWerner
@RalfWerner

@xeffyr /$s access is apparently more complex with api30 and to my sdcard-question you obviously have no experience. Since in the last three weeks (without reboot) the same data was never in two emulators, but all data where lost several times on the sdcard, I give up the attempt.

Addition to the last shot (above): The export action is mostly valid for one follow-up action and sshd is a special case. I've done the following check with Q10 (*95.apk process status is displayed twice and the ssh demon is referenced to PPID 1 - as in P9 too) and the same with R11 (*29.apk) with the following result:

[~]$ alias a pp; pp;sshd; a pp;sshd
alias a='export TERMUX_ANDROID10;'
alias pp='ps -eo pid,ppid,comm,etime'
bash: /data/data/com.termux/files/usr/bin/ps: Bad address
bash: /data/data/com.termux/files/usr/bin/sshd: Bad address
  PID  PPID COMMAND             ELAPSED
20045 16280 com.termux            24:42 # PID1 of OTS
20079 20045 bash                  24:39 # PID2 of OTS (X11 service)
20144 20079 proot                 24:36
20147 20144 Xwayland              24:36 # PID3 of OTS
20151 20079 bash                  24:36
20159 20151 proot                 24:36
20161 20159 fluxbox               24:36 # PID4 of OTS
20176 20161 fbset <defunct>       24:34
20344 20045 sh                    22:45 # open by widget selection 
20348 20344 mc                    22:45 # to edit .bashrc (insert alias a)
20491 20045 bash                  19:04
21105 20079 proot                 00:01
21107 21105 ps                    00:01
# here the SESSION 1 stalled until open a NEW SESSION and do there:
[~]$ a pp; export TERMUX_ANDROID10; pkill sshd
  PID  PPID COMMAND             ELAPSED
20045 16280 com.termux            24:11
...
21063 20491 bash                  00:29
21064 21063 proot                 00:29
21067     1 sshd                  00:29
21094 20491 proot                 00:01
21096 21094 ps                    00:01 # next (pkill) relase stalled in SESSION 1 - here in .bashrc
[2]+  Done                    [ -z "$f" ] && sshd

I have added comments above. In Q10 emulation export is superfluous and R11 Termux in stalled mode cannot be ended even not with ctrl+c. The only way is in a NEW SESSION with pkill sshd (above) or [-z "$f"] && sshd & in bashrc. With R30 (* 28.apk and the emulation ../sdk/system-images/android-30 should be identical to yours) I behaved the same.

Can you explain to me when alias a is necessary and when not?

Leonid Pliushch
@xeffyr
Check echo $TERMUX_ANDROID10. This variable should be set by app. However I did export TERMUX_ANDROID10_DEBUG=1 instead.
And if you are setting TERMUX_ANDROID10, do this with export TERMUX_ANDROID10=1. Not just export TERMUX_ANDROID10.
You can try unset TERMUX_ANDROID10 TERMUX_ANDROID10_DEBUG and then exec bash.
RalfWerner
@RalfWerner
I've checkt echo and got 1 but was only valid for one command and try *=0 and other values - always the same behavior!
But you @xeffyr are indescribable :) Your suggestion works well. sshd is no longer a problem! In my Studio-0.95-Version I have also inserted "DEX2OATBOOTCLASSPATH" (your last commit) is this necessary for the effect?
Leonid Pliushch
@xeffyr
@RalfWerner You shouldn't need DEX2OATBOOTCLASSPATH unless you are using the dalvikvm.
RalfWerner
@RalfWerner

Ok! I've used my Studio-0.95-api30-emulator to check api28 (default termux) on it. Is dalvikvm needed to extend it to the new versions and how can I do it?

This variable should be set by app. However I did export TERMUX_ANDROID10_DEBUG=1 instead.

I've checked:[ -z "$TERMUX_ANDROID10_DEBUG" ]&& export TERMUX_ANDROID10_DEBUG=1 only in .bashrc is not a solution but with unset TERMUX_ANDROID10 it works.

RalfWerner
@RalfWerner
@xeffyr did not get an answer (no /$s access and ... how can I do it?). The debug output doesn't bother me, but the action:
IP=$(ip address|grep -m 1 /24|cut -d / -f1|sed -e 's/inet//' -e 's/\ //g') therefore fails! With unset of both variables in .bashrc works on api30/ *28.apkemulator as on real devices (without proot e.g. 20144, 20159 above). How do I turn back to proot-exec without the unwanted effects? $IP is constant in all wifi networks10.0.2.16 (I was traveling) with you or @fornwall too?
I repeated it with your *.29.apk emulator (also api30/R) and surprised got the same OTS process, although PID3-4 are not in~/nl - why? To be sure, I have run successful two of my make-loops and checked again your *29.apk (all versions are 29) - that shouldn't have happened?!
Question about pkg in openssh (here an am process): First I get the dialog: allow installation from other sources? Which is then ended with the message: not done. I usually have this effect when trying to install *.apk with different signatures. I previously unified all 4 plugins of the emulator with apksigner, could be a keystore parameter a solution - what's your experience?
Leonid Pliushch
@xeffyr

Ok! I've used my Studio-0.95-api30-emulator to check api28 (default termux) on it. Is dalvikvm needed to extend it to the new versions and how can I do it?

You don't need dalvikvm if you even didn't know what is it. (that is a small thing to execute *.dex files).

$IP is constant in all wifi networks10.0.2.16 (I was traveling) with you or @fornwall too?

Why it should differ? That is a NAT IP for emulator. As I don't think that virtual devices have shared network, IPs returned by DHCP should be same (in per-device scope).

that shouldn't have happened?!

Havent't you noticed that APKs are same with only exception of different target SDK affecting SELinux?

Which is then ended with the message: not done. I usually have this effect when trying to install *.apk with different signatures.

Did you expected something else? I do not use/have signature key of Fornwall.

Btw, what you really trying to accomplish? There a lot more things to check in Android 10/11+ than just working "make-loops" or what you doing.
GrimlerBot
@GrimlerBot
<live_the_dream> yeah im going to update my stuff
<live_the_dream> now c++ is updated
RalfWerner
@RalfWerner
Thanks @xeffyr for answer here
道玄
@yozman
hey guys, I found <sys/msg> & <sys/shm> is available on bionic for API level 26, read this https://android.googlesource.com/platform/bionic/+/master/docs/status.md, but why still missing in termux?
道玄
@yozman
@xeffyr would u please look into it. really need ur help. thanks alot
Leonid Pliushch
@xeffyr

I found <sys/msg> & <sys/shm> is available on bionic for API level 26

I know about this but current Termux packages target level is API 24 which corresponds to Android 7.0. We don't have any plans on creating dedicated repo targeting at API level 26.

why still missing in termux?

We removed it because it is not supported on devices with API lower than 26. As I wrote, our repository is Android 7.0 compatible.

It is still possible to build packages for higher API levels.
道玄
@yozman
got it, how can I make my own lib package to include these implements? @xeffyr
Leonid Pliushch
@xeffyr
Just build package with higher TERMUX_PKG_API_LEVEL. But make sure that chosen API level corresponds of one of your device.
Note that most Android devices have POSIX message queues disabled at kernel level.
RalfWerner
@RalfWerner
@xeffyr, @fornwall Unfortunately *29.apk is not yet the solution, so mixed apk/proot-exec is still necessary and unset TERMUX_ANDROID10 unfortunately does not work. I did not find your *_DEBUG there and both work poorly. In addition to asking for a Studio-bundle the following three urgent questions:
  • With termux-info andgetprop ro.build.version.release I only get the device/package versions and with aapt I need the source. How can I determine the termux version and its targetSdk if I don't know the installation history or if it is supplemented/changed by plugins?
  • I have read little of @fornwall the past few weeks and he has not responded to my last checks (privately). Have you re-divided the tasks or is he on parental leave?
  • With pkg I use both methods (apt and am) in my installation script, whereby apt with proot-exec is not a problem and am is only possible for @fornwall. How is that solved?
Leonid Pliushch
@xeffyr
https://developer.android.com/preview/privacy/package-visibility can disrupt the APK-based packaging solution.
That could be an answer why shared user id is going to be deprecated.
RalfWerner
@RalfWerner

can disrupt the APK-based packaging solution

Should this be the answer to my last question (pkg)? With the full data access of the file-app to everything in termux I have no longer problems but with *.qcow2 files in Emulators. @fornwall has at least read my post and is not out of the world :)
A Studio-bundle for your @xeffyr *29.apk would help me mostly, so that I can increase my code-experience on it.

Leonid Pliushch
@xeffyr

Should this be the answer to my last question (pkg)?

No. That change is not released in developer preview.

Technically it is possible to bypass it by re-implementing the APK solution to use intents and IPC, but I don't know what to do with $PREFIX. As in this case packages won't be copied to Termux prefix, each package will have to be compiled with its own. That will result in further degradation of Termux usability, probably qemu-system + full blown Linux distro variant for solving SELinux issues will be more preferable even at the cost of performance.

I'm personally ok with in-APK packaging, but I'm against the case where packages will be sandboxed. If this going to happen, I'm voting for QEMU-based variant.

A Studio-bundle for your @xeffyr *29.apk would help me mostly

  1. You should be downloaded my previous APKs posted here. Where are they, why you can't use them?
  2. You can build APKs yourself.

I will not provide any new builds as previous were sufficient.