Open RalfWerner opened 1 month ago
I still don't get what your question is....
I still don't get what your question is....
The question is actually whether someone is interested and is ready to solve a variety of TB tranfer problems in Termux from Windows-TB. At first I moved description from the package Issue here.
I still have to explain the shots so that the problems in it are recognized - still comes. I thank you again very much for setting up the package at Termux. If you are an expert in Linux-TB, I would be happy if you take part.
In the German TB Forum, I have unsuccessfully searched for solutions for 2 months. Almost all participants only use Windows. The problems with small windows were able to understand many, but it also bothered nobody (they do not use small devices).
Also that a lot from Windows in Linux did not arrive at the transfer of profile data. The example contains an IMAP, a POP3 account and a local folder. Except for IMAP, no synchronizations are carried out. TB uses the mouse wheel very extensively, which is currently only weakly supported in X11 with fingers.
I also work on the description of this object. It does not need a development environment (make) like most others that I use and can be reduced. I am currently at 1.4 GB (484MB as *.TGZ backup without TB profiles) - in progress
In order for TB to be used effectively on Android, a few problems need to be solved that are not yet solved with the "formal installability". They require in-depth knowledge of Linux-TB and the special features of the XServer.
If these are to be solved in Termux, knowledge of the TB build process and description of patches are probably also necessary. The gigaset has no split/pop view function, is 1083x600 px and has the armv7l architecture. If TB works well on it, it won't be a problem on better equipped devices either.
The tf object allows a complete TB installation without development tools, which also includes firefox, openbox and an X11 server as well as the management of TB profiles and the start of all tools when opening Termux (bashrc). TB can also be used in the ip object with development tools. If you want to use it, you need at least _onebackup.zip file with your accounts to reproduce my examples. The tf object initially only contains bashrc with further descriptions.
Installation and checks on my moto and gigaset devices
@licy183 your instructions and the
zip
file were successful. I did this on the two devices above as follows:cd .thunderbird; unzip debs-arm*.zip; tar xf debs-arm*.tar; pkg in -- ./debs/*.deb
. The daily versions are now constantly updated.This means that TB can be used on all my devices after troubleshooting (Devices described there) I had already done checks on the Moto device with 115.13, as I described in the DE forum with Video. I make comparisons between the versions on Android and Windows, where I have been working with the tool for 10 years.
Win+Linux (moto (1512x720 px in portrait diagonal 13cm) TB versions (firefox with MB_HELPER and EK).
on moto the X11 App (date: 01.07.24 fullscreen) is used, with four TB windows in the 1st workspace of fluxbox, mirrored on a Win10 PC and the TB Win version reduced in size on the left. In both, a text area is selected in the compose window (VF) that is to be assigned an alternative color. At the bottom, parts of the X11 EK bar (single line) are visible.
The preferences are opened above the KB symbol (Output: 100% scaled, Pointer: Direct touch). Above the EK bar is the fluxbox icon bar. The usable area of TB is reduced by these bars and the window decorations. The fixed OS KB would also take up half the screen. This device can only do split screen in the middle with half screen each (e.g. X11+Termux).
This makes the usable area very (too) small (diagonal <3cm) for all 3 TB default areas + VF + Pop menues + (MB_HELPER. One solution would be to use an external KB and mouse and multiple workspaces (WS). When opening web links, TB switches to the other WS.
In the shot, the VF is mostly visible and because it is larger than 740 px, the entire text and the vertical scrollbar inside are also visible. The typical position of the phone is vertical! In this case, no VF editing is possible if the output is not scaled to 80%.
Installation from scratch by tf object
Values from bootstrap=3078/70 after apk install in
../usr
takes place with files/packages and each next install .first successful Process with shot and log
If I restore the backup (with `usr home` in `..`). I only checked TB. With termux-reset the `../home` data is retained and only the uninstallation would remove it. In both cases start with **_bootstrap_**. If you then do `pkg up` (5xEnter) the initial values are **_3465/78_**. If that **not the case**, you may need to _delete the cache_ by `rm -rf /data/data/com.termux/cache/apt` - **bug-reason ??** ![image](https://github.com/user-attachments/assets/e4afaa03-44c4-4d65-88be-e64b6c59bb1d) With `pkg in x11-repo && pkg in thunderbird -y` this increases to **_26430/203_**. With additional `pkg in firefox` the check then shows **_26467/204_** which is 1.1Gb. My first attempt (with cache) failed.Installation and execution log
``` [~]$ TB=thunderbird;pkg in x11-repo;pkg up -y;pkg in $TB -y;$TB --display=192.168.178.32:0 ... [~]$ ```The previous backup is 1.5Gb in size and contains many other packages needed in the useful Termux vor developer. The typical OTS starts with an action (
uu.sh
) after bootstrap, where a minimal set of packages and plugins be installed, which includes Xserver,sshd and some others. Values are now 27685/223integration in an OTS Process in progress ...
There are several issues that need to be resolved to use **TB** effectively on small devices and when exchanging **TB** profiles The `uu.sh` script is outside of Termux on `sdcard` (**sd**) and is run on every OTS. The same applies to the **sd/tf** project directory (i=sd/tf), in which bashrc (`i/bashrc` is linked to `~/.bashrc`. Once all installations have been completed, `bashrc` can be started with parameters TB (alias t=...) that were previously entered in `.shortcuts` and are displayed on the start screen via the widget plugin. On the Gigaset, **sd** and all other installation data are actually on a memory chip (64Gb). **sd/tf** contains several **TB** profiles and/or backups. In `~/.thunderbird`, the `*.ini` are replaced by links to **sd/tf**. Access to **sd** is possible via USB from any device, which makes exchanging profiles, for example, easy.