Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Release of 0.5.0

edited December 2017 in General

Dear all,

We have just released a new platform version with a lot of new features and improvements. The most prominent ones are probably:

  • Introduced support for automatic updates (In beta state, please use with care!)
  • Fixed the wifi reconnect problem (no internet access after loss of connection)
  • Updated RPi firmware and latest kernel from the official repository

Thank you for your help and support! More features and improvements will follow soon :)

Best regards
Igor

Comments

  • Hi Igor,
    Is it possible to release 2 versions.

    1- For the touch screens with BGRA8888 pixel format.
    2- For HDMI screens with RGBA8888 pixel format.

    As i read in the discussions that the latter causes a problem with the touch screen driver.

    Or that would be too much work for you? :smile:

  • Good Evening Igor,

    Thanks for the new release, you know by chance tell me if there is or will there be support for the cast broadcast?
    Thanks and congratulations for the great work

  • i click download it show : automatic update isn't possible yet.

    dose it mean i need reinstall ?

  • that what I did @kai , I thought that the autoupdate wasn't working in the previous versions, so now I think it is

  • If you release the next version of Emteria.OS, is it possible to improve the activation of the GPS-USB-Dongle? Because my Dongle won´t start every time, somehow it is a lottery. But perhaps it is a problem of the APP. I´m using GNSS commander - GPS status.

  • Hi @roxette,

    yes, we have been thinking about this solution. It would indeed create a pretty big overhead, so we would like to evaluate other possibilities first. Its not that the RGBA isn't compatible with the touchscreen's driver, it actually is. But it isn't compatible with the fkms overlay we are using. Switching to kms leads to a very limited color depth and/or issues with the i2c touch driver. The fkms even supports other color modes (like RBGA8888), but not the one we need :disappointed:

    There are two different solutions: asking Broadcom to extend their firmware to support RGBA8888 (Stefan has already opened an issue somewhere) or stop using fkms. In the meantime we are evaluating the newest Linux kernel 4.14, which apparently supports full color mode for the touchscreen, but still has problems with the i2c touch driver. I think Stefan was already in contact with their developers, so if we get some support from either Broadcom or the Linux community, we will be able to fix this very quickly.

  • Hi @Pomilpetan,

    we didn't test it yet. Probably it is affected by the same problem roxette is referring to. As soon we found a solution to the graphics, it shouldn't be difficult to add support for screen casting.

  • @kai, 0.4.6 didn't have auto-update functionality included, so you can't update from 0.4.6 to anything else. Starting with 0.5.0, in-place updates should be possible. It is still beta, though. We hope we didn't forget something important :)

  • @David, please take a look at your logs. If you can tell us what exactly isn't working properly, we will be happy to fix it.

  • edited December 2017

    @ kalkov
    could you please tell me shortly how to access the logfile? do I have to activate it somewhere? or do I find it somewhere?

    What I can tell, is, that the USB is neither starting at its own nor at starting the APP. This refers only to the GPS-Dongle. The USB-Stick with music and the USB-Soundcard is recognized.

  • Do you have a Linux machine? If so, you can mount your sdcard (after success/failure with your dongle) and check in /userdata/cache/logs. If you only have windows, you will need to use ADB.

  • edited December 2017

    which log do I have to post, the kernel or the logcat?

    I think I found it:

    [ 2.431213] usb 1-1.3.4: new full-speed USB device number 6 using dwc_otg
    [ 2.524523] usb 1-1.3.4: New USB device found, idVendor=1546, idProduct=01a7
    [ 2.527452] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 2.530427] usb 1-1.3.4: Product: u-blox 7 - GPS/GNSS Receiver
    [ 2.533438] usb 1-1.3.4: Manufacturer: u-blox AG - www.u-blox.com
    [ 2.538062] cdc_acm 1-1.3.4:1.0: ttyACM0: USB ACM device

    [........]

    <38>[ 84.772827] type=1400 audit(1513114357.215:9): avc: denied { read } for pid=1267 comm="u.gnsscommander" name="usb" dev="tmpfs" ino=10252 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:usb_device:s0 tclass=dir permissive=1
    <38>[ 84.829047] type=1400 audit(1513114357.215:10): avc: denied { open } for pid=1267 comm="u.gnsscommander" path="/dev/bus/usb" dev="tmpfs" ino=10252 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:usb_device:s0 tclass=dir permissive=1
    <38>[ 84.845742] type=1400 audit(1513114357.215:11): avc: denied { read } for pid=1267 comm="u.gnsscommander" name="devices" dev="sysfs" ino=3896 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=1
    <38>[ 84.862760] ty

  • Hi,

    There are a lot of VR apps on the google store.
    Is it possible to add support for de PiMax 4K goggle?

    cheers!
    Alan

  • Hi!
    Igor, has the revised 0.5.0 been preserved? Does the former 0.5.0 update or reinstall?

  • @kalkov said:
    @kai, 0.4.6 didn't have auto-update functionality included, so you can't update from 0.4.6 to anything else. Starting with 0.5.0, in-place updates should be possible. It is still beta, though. We hope we didn't forget something important :)

    i reinstalled 0.5.0, but i find it will halt when i just run system. but not sure just accidentally or not.

    one thing i'm wondering why so many TV box run android system very well but it's so hard to run on raspberry pi?

    TV box and raspberry pi no big diference one is bring system from cmos to ram, one is from SD card to ram.

    what is the mian point for android hard to run on raspberry pi?

  • edited December 2017

    @Igor, thank you for replying and for explaning the problem.
    I hope it can be fixed soon, however i'm not using a touch screen hence if that issue isn't fixed within 2-3 weeks then please postpond RGBA support for touch screens then release RGBA support version for HDMI screens :smile:

  • @roxette said:
    @Igor, thank you for replying and for explaning the problem.
    I hope it can be fixed soon, however i'm not using a touch screen hence if that issue isn't fixed within 2-3 weeks then please postpond RGBA support for touch screens then release RGBA support version for HDMI screens :smile:

    I'm following the issue too. In one or 2 weeks, it will condition buying a licence or changing my strategy.

  • @David, the kernel log shows that the dongle was detected correctly. No problems so far. The Logcat output includes a bunch of SELinux warnings, but they shouldn't be the reason for your problems. SELinux is set to permissive, which logs probable security issues, but still allows the operation to be executed. To test it, you can try to run "setenforce 0" in the terminal or set the SELinux to disabled in the file cmdline.txt on the boot partition.

  • @AlJan, this sounds like a very cool application. To get there, we need to finish 2 different things: (1) support for Android's native color mode (see my replies to roxette) (2) hardware acceleration for video decoding (we have a semi-working solution, which will be released soon).

  • @obero, sorry, I didn't understand your question. We will release 0.5.1 with fixed GApps support today or tomorrow. We hope, that you will be able to do an in-place update without using the installer. However, we didn't test it in production yet, so there is a chance something may go wrong :blush:

  • @kai, it is a complex topic I can write a whole book about. The main difference is: most TV boxes rely on i.MX, Snapdragon or Intel CPUs, which have huge communities and ready-to-use Android distributions. There is no such thing for Raspberry Pi, so Stefan and I have to implement a lot of existing drivers and adapters from scratch, as we can't reuse existing ones. Another problem is Broadcom's closed-source firmware, which heavily obstructs the development (see my replies about the color mode). Yet another problem is the limited performance: RPi3 has a very slow sdcard interface (in comparison to eMMC) and only 1GB of memory, which is shared between CPU and GPU. This means we have to optimize the platform even further, since all modern TV boxes have at least 2 GB of RAM and dedicated GPU memory.

  • @roxette, @juanitomaille, I'm afraid 2-3 weeks won't be enough for us to release a generic fix for both setups. The biggest order we have received so far is for a touchscreen-based product, so we have to keep this functionality in focus for now. On the other hand, if we can close this deal, we might be able to hire an additional developer to handle this issue.

  • edited December 2017

    @Igor, That period was an estimated time for you to think whether the i2c touch driver issue could fixed or not.
    If not then you can move on and fix the RGBA issue for HDMI screens.
    I was not asking for a generic fix for both setups within 2-3 weeks :)
    Nevertheless, you are the boss :wink:, so it's you who should decide what to do next, just please don't forget about the voice calls which is a lot more important for me that vnc server.

  • @kalkov said:
    Hi @Pomilpetan,

    we didn't test it yet. Probably it is affected by the same problem roxette is referring to. As soon we found a solution to the graphics, it shouldn't be difficult to add support for screen casting.

    Hi Kalkov,
    thanks for the repost. I look forward to developments. Thanks again

  • Hi,
    one comment regarding the hardware comparison, would it be possible to install Emteria Android on a BananaPi Pro or a BananaPi M3 maybe? The first one has more CPU Power and the advantage to use a SSD for example (real HDD speed, no USB channel break). The M3 has much more CPU power and 2GB of RAM (but the HD connector uses a USB channel internally again - how stupid).
    I'm using a BananaPro as mail- and file server with Debian, but never tried to install Android on that platform.

    Best regards,
    Sascha

  • We are working on support for a couple of other boards, but BananaPi is not in the list for now. The main reason is the high overhead. Supporting a new platform may require several months of work, which has to be somehow financially covered. The RPi is the most popular maker board out there, so the demand is sufficiently high. Developments for other boards will be covered by our cooperations with hardware manufacturers.

Sign In or Register to comment.