kalkov
About
- Username
- kalkov
- Joined
- Visits
- 1,041
- Last Active
- Roles
- Member, Administrator
Comments
-
We did not change the standard camera application. Check https://android.googlesource.com/platform/packages/apps/Camera2/+/refs/tags/android-7.1.2_r39 for reference.
-
https://help.emteria.com/kb/devices-rpi-3
-
We also have a dedicated device management system for emteria devices.
-
Can you provide a full description? What exactly isn't working? What did you change?
-
Go ahead and try it. The OS should have no issues with booting without a screen.
-
You have to re-install from scratch. What problems do you have?
-
Our logs say that you are > @Win10User said: Obviously the password is correct. How is that obvious? Our server logs say it isn't correct. What am I doing wrong? You are using a wrong password. If you forgot your passw…
-
We don't plan to add this feature anytime soon.
-
@simpz said: Are 0.9.0 and 1.0.0 still not considered stable to be pushed to the stable (non-beta) update devices? Yes, there are some experimental things included in those builds on RPi we don't want to push to stable devices without fur…
-
If you are using the official screen, it might be related to https://forum.emteria.com/discussion/831/rpi3-freeze-at-start-up-with-v0-9-0#latest But your device is also complaining about USB current change. You should check your power supply.
-
We are not certified for Google Mobile Services, so we can't preinstall it.
-
What OS? 32 bit or 64 bit? I've just uploaded a new version for Win x64.
-
No, sorry, USB boot is not supported.
-
Can you post a screenshot? You shouldn't be using any other resolution except for 800x480@60. You also shouldn't be adding any properties to /system/build.prop, since the tutorial is not up-to-date for 0.9.x.
-
Lock screen support will be part of v0.9.1. A power button should be able to enable it.
-
No, I think the problem is on our side. This line is bothering me: [persist.rpi.mode.force]: [1280x720@60] Can you try running adb shell setprop persist.rpi.mode.force 800x480@60 and reboot the device afterwards? EDIT: The official …
-
Sorry, but I need it altogether: 1) Keep fkms overlay 2) Set 800 600 60 resolution in config.txt 3) Reboot and wait for the system to boot 4) Call adb shell getprop
-
Did you change the overlay as I proposed above? Please also post the content of adb shell getprop. It would be great if we can find out the cause, so the next stable version will have it fixed.
-
Thanks for reporting, it has been restored now.
-
I think hdmi_cvt=800 480 60 is fine. The first thing you should try is changing dtoverlay=vc4-kms-v3d,cma-256 to dtoverlay=vc4-fkms-v3d,cma-256 Also, if you have ADB working, please do "adb shell getprop" and paste the r…
-
Thanks for the screenshot. I don't think it is frozen. Probably just a resolution issue. Can you copy&paste the content of your config.txt file?
-
In general, yes. We don't have a hardware sample in our lab to build Android for it.
-
Please read https://forum.emteria.com/discussion/comment/3871#Comment_3871
-
Please read https://source.android.com/devices/input/input-device-configuration-files You can either mount your sd card in Linux or use ADB over Ethernet.
-
Checked it now, seems to work just fine. What is the problem?
-
I'll check tomorrow, thanks for reporting @raven
-
Did you try installing 0.7.1? If it works, should read DrRokko's comment.
-
@cemoi71 you need to read about SSH key pairs
-
1) Simple & dirty solution: write your own init script (check /data/init.d for more details) 2) Proper & safe solution: call "su" in your application and reset the permissions after communication is finished (you can google specific example…
-
There is no root password. The user is authenticated by the private/public key pair. Android doesn't support passwords for now.
-
Thank you for this information. Is it possible for you to mount the sdcard on you PC (is it Linux or Windows?) and check the contents of the /boot/config.txt file?
-
For SFTP only sftpd_config is needed.
-
Please try to flash again & wait for at least one minute. Check if device reboots itself once or twice.
-
You can fix it yourself by changing line StrictModes yes to StrictModes no in sshd/sftp config files in /data/ssh Don't forget to remove any hashes (#) in front of the line, if present.
-
I can confirm it isn't working. The problem is that the project we use has updated the OpenSSH version from 6 to 8, which is great, but the responsible maintainers obviously didn't check whether both servers still work as desired. We will fix it in …
-
Thanks for reporting, I'll check it. Do you know if SSH/SFTP works on a fresh installation?
-
Thanks for reporting. Is it a fresh installation or update?
-
We can release an update at any time. If it's not urgent, I'll create a new release for CM3 as soon as the re-activation feature is finished (https://forum.emteria.com/discussion/821/activate-devices-via-license-file#latest).
-
We are working on this right now. It will allow automatic (re-) activation of devices when using universal licenses (see https://emteria.com/Provisioning). We plan to release the first beta of this feature by the end of next week.
-
More details would be great. What screen is it, what instructions did you get?
-
You cannot. Maybe we should make it possible through MDM.
-
Assign the letter manually. Or you a Linux distro.
-
Does Codesys generate Android-compliant code? How would you start it?
-
The bootanimation is stopped as soon as the system is booted, so there is no additional waiting. If you bypass the animation, you will be waiting with a black screen.
-
After calling "su" you will see a permission dialog. You need to confirm it once.
-
USB? Should be plug-and-play. You can check this too: https://forum.emteria.com/discussion/comment/3078
-
Sorry for the delay, I was out of office. It is merged now and will be part of the next release.
-
Yes, the OS is being actively developed. There will be no solution for BT with Android 7 and RPi 3B/+. Further Android versions are likely to have working BT.
-
It maybe due to a bug in our resolution detection logic. We will be rolling out an updated version in the next days. Hope it will fix it for you!
-
Sorry guys, I was out of office for a while and it looks like we had an issue with the official touchscreen. It is fixed now and we will be releasing a new version ASAP.