kalkov
About
- Username
- kalkov
- Joined
- Visits
- 1,077
- Last Active
- Roles
- Member, Administrator
Comments
-
The official one should support 800x480 only. The behavior of v1.1 is correct.
If you want to see more on your screen you should try increasing the density instead. Check system display settings for modifying display size. -
Yes, but not in the way I'd expect it. Modifying standard Linux drivers is a very bad idea.
The simplest way - and it isn't as simple as it should be - is to build a display module, to put it on the device and to load it dynamically. … -
What kind of a monitor/screen are you using?
-
Don't think so. What exactly is the issue?
-
Can you provide a description for how you would do it in Linux? Maybe there is a way to translate those steps without rebuilding the kernel.
-
What kind of display/touchscreen do you have connected?
Please post the content of /bbot/config.txt (you will see it when you put the sdcard into your pc). -
Please compare resolution values in Settings -> Raspberry Pi for 0.7 and 1.1. They should be the same.
-
I have no idea what GApps are doing - we don't recommend installing GApps at all. Check your system settings -> raspberry pi settings to change the resolution.
-
There is no such thing in Android. See /data/init.d instead.
-
Closing this thread as the original topic was resolved.
-
I will comment on the other thread then. Forget about the screenshot for now.
-
@cemoi71, Yes, please open a new thread. Ideally with pictures showing the difference between 0.7 and 1.1. Also, it would be great to know what resolution was used in 0.7. Check settings -> Raspberry pi settings.
-
Works fine on any on my networks. How sure are you that the problem is in the OS?
-
Is it a fresh installation or upgrade? On 0.7.1, which resolution does the system choose (settings -> raspberry pi settings)?
-
What exactly? Showing beta version only if they are activated? Yes.
-
The same way you would do it in Linux. Or via SysFS.
-
@Talkabout Two days ago
-
I never tried using WinSCP with RPi boards myself. Was it a clean installation or an upgrade?
-
Yes
-
Don't use Windows 8 or use Live CD of Ubuntu 18.04.
-
We have updated our resolution detection recently. Chances are good that it will work with next release.
-
Sorry, @che2, we don't support pluggable USB WIFI adapters. You should use a USB Ethernet adapter instead. We have several different onces at the lab and all of them are working out of the box. Android's WIFI HAL isn't very flexible.
-
Maybe creating your own GPIO key mapping using idc files?
-
Not 100% sure, but I assume you'd have to rebuild the uboot to disable its output.
-
That is a valid question. We are working on this.
-
Probably not, as ASUS never released proprietary files required for Android 9 and we would like to switch as soon as possible.
-
Closing, since it is a duplicate of https://forum.emteria.com/discussion/850/rpi3b-and-7-screen-only-shows-console#latest
-
Make sure those files are accessible from your application. Check Linux file permissions.
-
You can remount the partition at runtime if you wish, but I wouldn't recommend you doing this. Put the sdcard into your PC and do it there.
-
We have fixed this issue yesterday. It will be working in the next release.
-
Read https://about.emteria.com/index.php/knowledgebase/using-integrated-ssh-server/
-
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.