Hi kalkov, hi at everyone else in the thread.
Thought you would like to here that I did some progress one the problem.
Firstly, to compile the clientapp or crosscompile it from raspbian to android wont clear the request for two reasons.
One is that the client neccessarily need the python-smbus pkg which i think isnt available for android. Second and also simple is the fact that I dont own the sourcecode of it because its written by Olmatic GmbH itself and the shutdown commands wouldnt work because android isnt debian or raspbian. Which leads me to another problem.
But next I've to tell some good news.
Based on sven-olas debian-kit (available on f-droid) I was able to install debian jessie side-by-sido to emteria based on the kernel. I was also able to update and upgrade the distro after having some trouble with i think non probably mounted directorys where some commands helped me to fix for the moment (mount -o remount,ro /sys/fs/selinux and mount -o remount,rw /sys/fs/selinux).
After this step i was also able to install i2c-tools and the needed python-smbus packages into debian and to install the client too.
So far... the client also works and after i did some search in the emteria-forum and made some changes based on timezone in debian i was also able to wrote the actual time into the rtc which is a ds1307 as seen in this threads wich helped me alot (as mentioned above)
#53111
#522
Now I've two major issues left and some little ones which aren't the case at the moment.
First major issue is when emteria gets the shutdown command from the shutdown app included in the system it seems emteria isn't completly shutdown. Because after switching the psu off, the pi is sucking the ups's (and thats also the rtcs) battery emtpy and then turns off completly. The correct behavior based on my experience in raspbian with the clientapp for the ups is, that the client gets the shutdown command to and after shutting down the os cutting down the power until you hit the powerbutton (integrated) or if it was a powerfail shutdown cutting down the power until (psu) is restored.
Second major issue based on the first one is, when it comes to a powerfail shutdown the client tries to shutdown or maybe shutdown the debian running sidy-by but only one thing in emteria happens, the message that my power is insufficient. And i think the problem is here different commands to the kernel for shutting down the OS.
Which leads me at last to my question for kalkov. Is there a way to send commands from the debian to the android side without ssh or anything else? i can complet handle both sides on the shell with connectBot app which is also available on f-droid.
Best Regards Kevin.
