Android: Difference between revisions

From Tučňák Wiki
Jump to navigation Jump to search
← Older edit
Ok1zia (talk | contribs)
2,390 edits
Ok1zia (talk | contribs)
2,390 edits
 
(17 intermediate revisions by 2 users not shown)
Line 3: Line 3:


=Hardware requirements=
=Hardware requirements=
Some history:
[[File:Tucnak_android.png]]
[[File:Tucnak_android.png]]


''ARRL DX contest on Samsung galaxy IIs''
''ARRL DX contest on Samsung galaxy IIs''


* Android 4.1 (API level 16). For older Android, try Tucnak 4.15.
=Branch 5=
* Recommended screen resolution at least 640x480.  
'''Tucnak 5.xx is experimental!'''
* Lower resolution use 640x480 internally and output is scaled to native resolution. Tested 480x360, is usable but not optimal.
 
* SD card with 'reasonable' capacity
Android build was rewritten to allow run on new 64-bit devices. Now it supports devices since Android 9 (API level 28). Some special notes for Android:
* Files are now stored in Downloads folder. This is breaking change because newer Android versions block access to application files
* New two finger zoom in map
 
=Branch 4=
* Android 5 (API level 21) to Android 14 (API level 34). For older Andorid 4.1 (API level 16), try 4.61.
* Only for '''devices capable running 32 bit apps''' (armeabi-v7a). Due to [https://android-developers.googleblog.com/2026/03/android-developer-verification.html bad news like this] I will probably '''stop working on the Android port'''.
* Some new (2024) devices tells about Tucnak incompatibility. They expect 64 bit app (arm64-v8a) which is unsupported by Tucnak. For example latest Google Pixel.
* Recommended internet access for DXC/KST
* Recommended internet access for DXC/KST


Line 22: Line 31:
* Bluetooth devices because of no official support for BT from native code
* Bluetooth devices because of no official support for BT from native code
* Serial ports - maybe with alternative kernel with proper drivers
* Serial ports - maybe with alternative kernel with proper drivers
* Since Oct 2023 the Aircraft scatter :-(
* Hamlib


=Limited support=
=Limited support=
* USB devices (Davac4, Rotar4) - It is compiled but it seems it works only on rooted devices. User must be member of 'usb' group.
* USB devices (Davac4, Rotar4) - It is compiled but it seems it works only on rooted devices. User must be member of 'usb' group.
* Hamlib - It is compiled but only usable rig type is 'NET rigctl'.


=Touch control=
=Touch control=
Line 33: Line 41:


To send F1 to F10, use FN key, numeric keys will switch to F's.
To send F1 to F10, use FN key, numeric keys will switch to F's.
=Known bugs=
* Alt hardware key on devices like Asus TF-101 does not work


=Bugreports=
=Bugreports=
Line 56: Line 61:


Tucnak in FullHD on Rikomagic MK802. TNX to OK1CDJ.
Tucnak in FullHD on Rikomagic MK802. TNX to OK1CDJ.
[[File:Onyx_Boox_Note.jpg|border|800px]]
Tucnak on a very old Onyx Boox Note with BT keyboard in 2025. TNX to OK1IAK.


=Notes=
=Notes=
* Pepa OK2WO recommends capacitive stylus CELLY (about 10€) for accurate control also for other applications
* Pepa OK2WO recommends capacitive stylus CELLY (about 10€) for accurate control also for other applications

Latest revision as of 20:54, 28 October 2026

Since 3.16 there is also Android port of Tucnak available. Focused on tablets but can be used also on cell phones. Due touch control, not all features must be accessible.


Hardware requirements

Some history:

ARRL DX contest on Samsung galaxy IIs

Branch 5

Tucnak 5.xx is experimental!

Android build was rewritten to allow run on new 64-bit devices. Now it supports devices since Android 9 (API level 28). Some special notes for Android:

  • Files are now stored in Downloads folder. This is breaking change because newer Android versions block access to application files
  • New two finger zoom in map

Branch 4

  • Android 5 (API level 21) to Android 14 (API level 34). For older Andorid 4.1 (API level 16), try 4.61.
  • Only for devices capable running 32 bit apps (armeabi-v7a). Due to bad news like this I will probably stop working on the Android port.
  • Some new (2024) devices tells about Tucnak incompatibility. They expect 64 bit app (arm64-v8a) which is unsupported by Tucnak. For example latest Google Pixel.
  • Recommended internet access for DXC/KST

Install

Tucnak is not on Google Play. To install you must allow install of untrusted applications. Then download Tucnak APK package from http://tucnak.nagano.cz/download.php#android and install it manually.

Features not included

  • Sound recording
  • FFT spectrum display
  • Parallel port keying
  • Bluetooth devices because of no official support for BT from native code
  • Serial ports - maybe with alternative kernel with proper drivers
  • Hamlib

Limited support

  • USB devices (Davac4, Rotar4) - It is compiled but it seems it works only on rooted devices. User must be member of 'usb' group.

Touch control

Tucnak on screen keyboard

Start touch on-screen keyboard by click on input line. The behavior of Enter is context-depended. Sometimes send Enter to Tucnak. Sometimes closes keyboard. Comments are welcome.

To send F1 to F10, use FN key, numeric keys will switch to F's.

Bugreports

Bugreports are welcome by e-mail. In case of problems please install alogcat and send it to me with next informations.

M5 ESP32 CW keyer

https://github.com/ok1cdj/M5-ESP32-keyer

See this video:

Gallery

Tucnak in Portrait mode with floating on-screen keyboard.


Tucnak in FullHD on Rikomagic MK802. TNX to OK1CDJ.


Tucnak on a very old Onyx Boox Note with BT keyboard in 2025. TNX to OK1IAK.

Notes

  • Pepa OK2WO recommends capacitive stylus CELLY (about 10€) for accurate control also for other applications
Retrieved from "https://tucnak.nagano.cz/wiki/index.php?title=Android&oldid=3303"