coderus / aliendalvik-control Goto Github PK

Filing this issue here in order not to be forgotten:
http://talk.maemo.org/showthread.php?p=1556221
It was quite nice to gain that additional screen space, so please check, if the suspicion is true, and fix AlienDalvik-control, if necessary.
Thanks!

Although "Toggle Android navbar" of Aliendalvik control 1.2.2 is selectable (with new icon) as an Eventsview shortcut (in Settings -> Events view -> Select shortcuts), it invisible and non-functional in the Eventsview proper on SFOS 2.
In contrast to that it is properly displayed and works fine in the Top Menu of SFOS 3.
The "Toggle Android navbar" was working fine in previous Aliendalvik control versions (below 1.2) under SFOS 2.

Tested on a Jolla 1 phone with SFOS 2.2.1.18 (and counter-tested on an Xperia X with SFOS 3.0.1.11).

P.S. (related issue): Please also restore the old "Toggle Android navbar" icon in the Aliendalvik control branch for the AOSP 4.x based Android runtime environment, as the new icon does not resemble the actual navigation bar button icon (of Android 4.x) at all.

When using the new feature onehand control on my XA2 with Sailfish 3.0.3.9, the current Android app opens again. The app then appears twice on the home screen - same app, two cards.
It happens not every time, but very often. It is reproducible with normal usage of the onehand control or by simply tapping on the new right bar.

Hello !

Currently, Sailfish seems to be still afflicted by this usability bug/security feature, which leads to users still not being able to open pictures received over bluetooth using Android apps.

That's due to Sailfish trying to make things a bit more secure by not systematically making the received files world-readable, (they're 0640 instead of 0644) combined with Android trying to be secure by giving each apps its own UID:GID. Thus app can't immediately open files received over Bluetooth (you would need to first chmod them from the cli or from your favourite file manager).

Do you think if it would be a nice feature if the plug-in's empty screen where you swipe to trigger the sharing (the empty screen, with the top right "Share to Android" tab-trigger), has in-tab text that reports if the file is world readable, and offers a button to change permissions before the user right-swipes ?

That would be - I would thing - a nice features :

• that works around the current Sailfish usability bug/security feature
• that would do a useful check due to Android UID:GID based security.

Thank you for your wonderful work.

See https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0/10656/311

Having "AlienDalvik control" running seems to prevent SailfishOS from starting AlienDalvik automatically, when an Android app is started (i.e. when AlienDalvik is not automatically started at SailfishOS start-up).
Observed with aliendalvik-control 1.0.10-1 (regardless of the SFOS version) on Jolla 1 phones.

Well, while it is unfortunate to have lost this feature of SailfishOS with AlienDalvik, "AlienDalvik control" is essential for using AlienDalvik nicely, IMO.
Hence fixing this would be much appreciated.

Open Android URL just plain doesn't work.
Open Android URL Selector does work, but only if the browser has been started before, it can not launch the browser and open the URL in it.

EDIT: for some reason 'Android Open URL' now also behaves like 'Open Android URL selector' except it DOES open firefox on the correct page even if firefox wasn't running before?

Is there any way to just get it to open Firefox reliably, without any pop-ups?

RPM/Zypper packaging should get an update so that Storeman shows this update just on devices with 3.4 installed. Thanks & kind regards!

SFOS: 4.3.0.12

I installed the most recent version (9.3.1-1) of aliendalvik-control from open repos via storeman.
After installing no option was enabled in the dalvik settings. I noticed that the service aliendalvik-control.service was not running.
The installer did create /lib/systemd/system/aliendalvik-control.service however sfos did not find or start that service.
I tried manually starting it over ssh with systemctl start aliendalvik-control.service (both with and without devel-su) - still service not found.

I then manually created a symlink from /lib/systemd/system/aliendalvik-control.service to /etc/systemd/system/aliendalvik-control.service. After that i was able to start the service.

I honestly don't know much about systemd and where it looks for service files but my guess would be that for some reason it does not find %{_datadir}/dbus-1/services/org.coderus.aliendalvikcontrol.service (found that in the .spec file)

any thoughts?

For the details see here

The problem when upgrading a package is that the scriplet will be executed this way:

• %pre of new package
• (package install)
• %post of new package
• %preun of old package
• (removal of old package)
• %postun of old package

Thus your %preun will get unconditionally executed after your %post and the package will be left in an uninstalled state.

Whenever a scriplet is started, parameter $1 contains the number of instance currently on the system.

So when upgrading, %preun will get a 1 (there's still the new version left, we're only uninstalling the old version), and when uninstalling it will get 0 (no more copies of the package left).

You can avoid accidentally uninstalling a just-upgraded package, by checking $1.

on sailfish 3.3.0.16 there is nothing happening when i try to start Contacts from DALVIK-control.

further my contacts dont work well in DALVIK.
please assist me how to debug this, so i can get conatact working (again)

br