I'm using a Raspberry Pi Compute Module 5 (eMMC) with the Waveshare CM5 PoE BASE A carrier board, running emteria Android 15 (also tested with the latest nightly build).

Problem: CSI cameras are detected by Android but produce no video frames. The built-in Android Camera app shows a black/white screen. Third-party apps (Flutter with CameraX) also fail to render any preview.

Hardware tested:

• Raspberry Pi Camera Module v2.1 (imx219)
• Raspberry Pi Camera Module 3 Wide (imx708)
• Tested on both CAM0 and CAM1 ports

Config (config-overrides.txt):

camera_auto_detect=0 dtoverlay=imx219,cam1

What works:

• The camera IS detected by Android (dumpsys media.camera shows device 1000)
• Camera opens successfully (Camera 1000: Opened in logcat)
• USB cameras (UVC) work perfectly on the same device

What doesn't work:

• No frames are delivered to any app (preview is blank)
• configureStreams logs DataSpace override not allowed for format 0x23 (YUV_420_888)
• Even with preview-only stream (no YUV_420_888), the SurfaceTexture receives no buffers

Is CSI camera support (imx219/imx708) expected to work on the CM5 with Android 15? Is there a specific emteria version or configuration needed?

Thank you.

I've recently built a RPi 5, with the official Touchscreen Display 2. Emteria OS version is 15.5.47. Everything is working well, but when I set the display orientation to 90 degrees within the Emteria settings, the screen does change from Portrait to Landscape, however the "usable" area on the screen is still set to Portrait (see attached picture). Is there some other setting I need to change, or something I need to add to config.txt to get the screen fully working in Landscape mode? Many thanks in advance!

I have several devices equipped with resistive touchscreens, and adjusting their behavior has been quite challenging. I’m currently migrating my system from Linux to Android, and replacing all screens would be costly and impractical.

Even after configuring the .idc file, installing the manufacturer’s driver, and trying several adjustments, Android still seems to interpret the screen as multi-touch. As a result, touch detection is unreliable. For example: I need to press repeatedly for a button to respond, and using a virtual keyboard becomes practically impossible.

Has anyone worked with this type of screen and can share any advice or insights?

P.S.: I’m using eGalax 4-wire resistive touchscreens. Under Windows and Linux, the touch works perfectly.

I have installed Emteria Android 14 and 15 on a Raspberry Pi 5 and I'm trying to use the official Raspberry Pi Camera Module v3 without success. At least the built-in Camera app does not seem to recognize the camera.
Has anybody done this? Is it even supported?
I cannot find any information about it.

This is the one I got: https://www.waveshare.com/8-dsi-touch-a.htm

also tried:-
hdmi_force_hotplug:0=1
hdmi_group:0=2
hdmi_mode:0=87
hdmi_timings:0=720 0 22 10 78 1560 0 13 3 13 0 0 0 57 0 75000000 0
framebuffer_width:0=720
framebuffer_height:0=1560
max_framebuffer_width:0=720
max_framebuffer_height:0=1560
disable_overscan=1

Result is that I see the boot up text displayed on the LCD while in initial booth up, then nothing there after.
Any idea's will be greatly appreciated.

I am running version v15.1.0 on Raspberry Pi 5 with official TouchDisplay 2.

I am unable get USB audio working. I have AudioEngine2+ speakers with DAC built-in (Texas Instruments PCM2704 16-bit stereo audio DAC). I can see it under hardware page of devices in Emteria console. But no way to get it working.

Could you please give me some guidance on how to do it, I can only see 3 options in RPi settings:

3.5 mm jack (RPi 3/4) and Digital Audio
HDMI0
HDMI1

I have set it to first option with 16-bit audio quality.

We're trying to use an SIM7600X 4G HAT in order to provide our Raspberry PI 5 Internet connectivity through it but it doesn't work. In Settings > Networks and Internet you can see "Calls and SMS: No SIM card" and we've just checked that the hat in working (red NET LED is blinking quickly) and we've got to connect it to Internet through the USB interface and use this connection in a Windows PC.

Please, any help with this? Many thanks in advance,

Dani.

I use a RPi 4B with the 10 inch Touch Display of uperfect. The Display is connected via HDMI (display) and USB (touch input).

I used the Raspberry Pi Imager (v1.9.0) to write Emteria (Android 14, published 2023-11-23) to my SD Card and everything worked fine.

After upgrading Emteria from v14.2.0 to v14.7.0 the touchscreen did not respond to touch inputs anymore. I was able to get this output from dmesg via ssh:

# Disconnect USB-Connector of display
[Sun Mar  9 20:37:59 2025] usb 1-1.4: USB disconnect, device number 3
[Sun Mar  9 20:37:59 2025] ueventd: Loading module /vendor/lib/modules/joydev.ko with args ''
[Sun Mar  9 20:37:59 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0004v00000416p0000C168
[Sun Mar  9 20:37:59 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip02in00
[Sun Mar  9 20:37:59 2025] ueventd: LoadWithAliases was unable to load input:b0003v0416pC168e0111-e0,1,4,14,k71,72,73,74,75,77,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8C,8E,96,98,9E,9F,A1,A3,A4,A5,A6,AD,B0,B1,B2,B3,B4,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,F0,ram4,lsfw
[Sun Mar  9 20:37:59 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0001v00000416p0000C168
[Sun Mar  9 20:37:59 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip01in01

# Reconnect USB-Connector of display
[Sun Mar  9 20:38:14 2025] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
[Sun Mar  9 20:38:14 2025] usb 1-1.4: New USB device found, idVendor=0416, idProduct=c168, bcdDevice= 0.00
[Sun Mar  9 20:38:14 2025] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Mar  9 20:38:14 2025] usb 1-1.4: Product: MTouch
[Sun Mar  9 20:38:14 2025] usb 1-1.4: Manufacturer: TSTP
[Sun Mar  9 20:38:14 2025] usb 1-1.4: SerialNumber: CMTP_1.0
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip02in00
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0004v00000416p0000C168
[Sun Mar  9 20:38:14 2025] input: TSTP MTouch as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0416:C168.0003/input/input2
[Sun Mar  9 20:38:14 2025] hid-multitouch 0003:0416:C168.0003: input,hidraw0: USB HID v1.11 Device [TSTP MTouch] on usb-0000:01:00.0-1.4/input0
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load input:b0003v0416pC168e0111-e0,1,3,4,k14A,ra0,1,2F,35,36,39,m5,lsfw
[Sun Mar  9 20:38:14 2025] input: TSTP MTouch as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:0416:C168.0004/input/input3
[Sun Mar  9 20:38:14 2025] hid-generic 0003:0416:C168.0004: input,hidraw1: USB HID v1.11 Keyboard [TSTP MTouch] on usb-0000:01:00.0-1.4/input1
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0004v00000416p0000C168
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip02in00
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip01in01
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0001v00000416p0000C168
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load input:b0003v0416pC168e0111-e0,1,4,14,k71,72,73,74,75,77,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8C,8E,96,98,9E,9F,A1,A3,A4,A5,A6,AD,B0,B1,B2,B3,B4,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,F0,ram4,lsfw
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load hid:b0003g0001v00000416p0000C168
[Sun Mar  9 20:38:14 2025] ueventd: LoadWithAliases was unable to load usb:v0416pC168d0000dc00dsc00dp00ic03isc01ip01in01
[Sun Mar  9 20:38:14 2025] type=1400 audit(1741549095.341:7461): avc:  denied  { read } for  comm="InputReader" name="country" dev="sysfs" ino=33260 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[Sun Mar  9 20:38:14 2025] type=1400 audit(1741549095.341:7462): avc:  denied  { open } for  comm="InputReader" path="/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0416:C168.0003/country" dev="sysfs" ino=33260 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[Sun Mar  9 20:38:14 2025] type=1400 audit(1741549095.341:7463): avc:  denied  { getattr } for  comm="InputReader" path="/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0416:C168.0003/country" dev="sysfs" ino=33260 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1

I tried to reinstall Emteria using the appimage provided for Linux x64. The device booted properly after writing the image to the sd card but it did not respond to any touch inputs. The problem is reproducible in my setup.

How can this be solved?

Thank you.

We are trying to develop an integration of this module by connecting it to a Raspberry PI 5 with the latest version of Emteria. Using the UsbGps app we see that it cannot locate any satellite. After confirming its operation with Google Maps, we see that there is indeed no location available; in fact, it ends up stopping indicating too many errors; please; could you help us?

Thank you very much in advance!

(https://forum.emteria.com/uploads/editor/c5/q20awqumd0n3.jpg)

We currently have a MIDAS display, but we can't figure out how to make the 'touch' parte to work.
https://www.midasdisplays.com/product-explorer/tfts/7-inch-tfts/mct101hdmi-a

Any suggestion?

As a backup solution, we identified this screen as compatible, given the hardware list available on the Emteria site.
Could you please confirm this Waveshare screen is fully compatible with the latest Android Emteria.os?
https://www.amazon.it/10-1inch-Capacitive-Raspberry-Supports-mini-PCs/dp/B075J7JNKH/ref=sr_1_1?__mk_it_IT=ÅMÅŽÕÑ&keywords=waveshare+10.1&qid=1557935863&s=electronics&sr=1-1#HLCXComparisonWidget_feature_div

Thank you very much!!
Alex

Is there any way for the back,home,drawer buttons to be rotated according to the screen orientation?
I've changed my screen's orientation from the Emteria settings app but the buttons still remained on the length of the screen.

Thanks for everything!

I've tried to install emteria on a Raspberry PI 5 with a HMDI monitor connected to. After writing the MicroSD with the installer, I booted it up Rapsberry but no video.

I had to put video=HDMI-A-1:1024x768@60D on cmdline.txt in order to see the video.

Why does this happen?
Where can I look at (logs and others) to trace the problem? I think it should boot without modifications.

Thanks

Ps: I'm using a raspberry pi b+ with the stable version of emteria android 7.1 nougat.

Can someone please help me?

I have an C790 module (tc358743) that I want to get to run with my RPi 4B.
Android: Emteria v14.4.0

In the /boot/config.txt I added 2 lines via adb:
dtoverlay=tc358743
dtoverlay=tc358743-audio

After a restart I expected to see the module as /dev/video0 which wasn't the case.

BR

It won't boot at all without changing
dtoverlay=vc4-kms-v3d,cma-384
to
dtoverlay=vc4-fkms-v3d,cma-384

in the config.txt, but this gets reset after a reboot it seems. Is there some way to alter this in the config-overrides.txt?

Secondly - the touch detection is 180 degrees off from the screen. I've tried display_rotate=2 etc but no luck. Is there a solution for this?

Thanks in advance for any help.

Jon

I'm developing an application
that uses a USB memory stick in an environment where emteria.OS v11.11.0
is installed on a Raspberry Pi Compute Module 4 (RPI-CM4),
but when I connect a USB memory stick to the IO board of the RPI-CM4,
it doesn't mount.
The USB memory stick doesn't appear when I check it with the "Files" application.
However,
when I check with the dmesg command or adb logcat,
it is recognized in /dev/block as sdb1 and sdc1.
What does that mean? Why isn't it mounted?

So, I also have a Raspberry Pi 4,
so I installed the same v11.11.0 on it and connected a USB memory stick in the same way,
and not only was it recognized as sdb1 and sdc1,
it was also mounted under the /storage directory.

Why is it behaving differently even though it's the same version?
I'm waiting for any advice, no matter how trivial it may be.

Has anyone successfully used a circular display either 3.4inch or 4inch display?
I have tried the options of enabling fkms as mentioned in the document and also have added the entries to config_overrides.txt as mentioned in their wiki https://www.waveshare.com/wiki/3.4inch_DSI_LCD_(C)

But i couldnt get the display working. The green light in the display keeps blicking meaning the display is not getting any active.

Any idea how to get this display working with Emteria?

Thanks in advance

Looks like Emteria OS does not support WiFi 5GHz networks for Compute Module 4 or Raspberry PI. Could you please confirm on this issue, was not able to spot it in any release notes.

Regards
Sai Ram M

• Read values of gpios
• Write values of gpios
• Set direction (read/write) of gpio
• Set edges interruption and get events
• Optional: Set pull up o pull down

Desire solution

• Use any existing lib to access GPIO, like wiringPi, pigpio, raspi-gpio
• Import it to android using JNI

Problem
Can't get access to /dev/mem through JNI on my android app.

Especifically, I'm try to: "open("/dev/mem", O_RDWR | O_SYNC)"
but it doesn't work. In one of my tests, I tried to change the access permissions of the file to 777 but nothing changed, always got -1.

Do you have any idea of how I can access it?

I read in this forum, "To open /dev/mem you need both regular access permissions on the device file and the security capability CAP_SYS_RAWIO, or to be root"

In other forum says,
"
1) Run the program via "sudo" (this will be the most common advice given on this forum)
2) Make the program setuid root - or setgid kmem
3) Make pi be in the kmem group (and reboot to make it take effect)
"

But I can't run the program as root and setuid is not a valid command on the shell of emteria OS.

Do you know if I can "setuid root" to an App on Emteria?

Does Emteria OS have any libs to be able to manage GPIO?

https://www.amazon.com/dp/B0CFQP51J4?psc=1&ref=ppx_yo2ov_dt_b_product_details

All of the devices I have tested will capture 1080p input on Windows, Mac, and Linux, but when I test them on Emteria OS the capture is limited to 720x480 or 640x480.

I can confirm the screen works with Raspberry Pi OS after installing the drivers. And separately, Emteria is installed and working fine. I'm unsure how to install the drivers on the Emteria OS to get it working (if that will actually work?)

I am trying to get my waveshare 7” (c) screen to work on my raspberry pi4B but having no success.

I have added the strings that waveshare state in the config.txt. This fixed the resolution for me, but all I get is the Uboot show up on screen, that shows all the commands but then the screen doesn’t display anything.( where the emteria logo usually shows).

I’m on the latest version of emteriaos, I get a display as normal if I plug in a normal hdmi monitor.
I’ve tried to Google and search for stuff to no avail.

Link to the screen I’m trying to use: https://www.waveshare.com/wiki/7inch_HDMI_LCD_(C)

The string I’ve added to config:

hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=1

This is my first time with any kind of scripting and first time with a raspberry pi, so I apologise in advance- i have no idea what I’m doing 😂

Any help is really appreciated, I refuse to give up as I’m planning on using this as a Rash dash in my track car.

I am trying to implement the example Serial app code provide in Emteria github on a Raspberry Pi Compute Module 4. I have updated the code to use sushell instead of su. But i am getting the following errors

type=1400 audit(0.0:2024): avc: denied { read } for name="ttyS0" dev="tmpfs" ino=406 scontext=u:r:untrusted_app_27:s0:c97,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.emteria.serial

type=1400 audit(0.0:2025): avc: denied { write } for name="ttyS0" dev="tmpfs" ino=406 scontext=u:r:untrusted_app_27:s0:c97,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.emteria.serial

type=1400 audit(0.0:2026): avc: denied { open } for path="/dev/ttyS0" dev="tmpfs" ino=406 scontext=u:r:untrusted_app_27:s0:c97,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.emteria.serial

type=1400 audit(0.0:2027): avc: denied { ioctl } for path="/dev/ttyS0" dev="tmpfs" ino=406 ioctlcmd=0x5401 scontext=u:r:untrusted_app_27:s0:c97,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.emteria.serial

Kindly let me know how to resolve for the same.

Regards
Sai Ram

What do I need to do to allow a custom APK to run in Kiosk mode?

Emteria 13.5, RPi4B

Thanks

it is easy to enable the SPI interface in Emteria OS 7.6 on Rasp 3 B+. Just add "dtparam=spi=on" in config.txt.

I try the same approach in Emteria OS 13.3 on Rasp 4. It does not work.

Does anybody known, if SPI is supported on Rasp 4 ? If yes, how to Enable it ?

Thanks a lot in advance !

I have an Arduno 64MP camera module that I was hoping to use kind of like a smartphone-style camera with a touchscreen, but when I launch the camera app it immediately closes, and if I press it enough times it just says "Camera app keeps closing", but with no error information. I've loaded the arduno-64mp driver in config.txt, has anyone had luck getting Emteria to work with it? It works fine under Raspberry PI Os, but I feel like Android's camera app would be a better interface overall compared to typing in commands in the terminal.

Using the standard 64-bit kernel, v.6.1.21-v8, I have followed the instructions given at:

https://www.osaelectronics.com/learn/tutorials/dacberry-400-series-quick-start-guide/

This terminates with:

Checking environment...
Updating apt indexes...
.....................

Using OS v.5.10.103-v7l, the result is:better abd termineates with:

Checking hardware requirements...
\nChecking for dependencies...
\nDownloading examples and documentation...

Enabling DACBERRY400 Driver

Finalising Install...

i2c1 overlay already active

dacberry400 overlay already active
Already GPIO active
Default sound driver currently not loaded

There then follows a "speaker-test" and an instruction to reboot.

But I cannot ever get sound out of the board. Does anyone here know what else I need to configure to achieve this goal?

Thanks for any pointers!

David

I am using emteria on a Raspberry Pi 3B connected to a flat-panel plasma television. The display stretches beyond the screen, thus cropping the display. I have tried changing display resolution to a standard ratio as well as using a custom resolution. The size of objects in the display changes, but the display as a whole is still cropped.

Ubuntu 18.04 has a setting for display on a TV that handles this nicely. The Nvidia card on my home theatre PC allows me to me adjust the display size manually. Is there any such feature in emteria.OS?

Thanks

esprimme

As stated in known issues, EmteriaOS for Raspberry Pi 4B currently doesn't support GSM connection via USB or GPIO. I'm working on a system for my car and it would be nice to know if this feature would be available in the near future (like months) or it's better to stick to different solution?

If it wouldn't be available in some time, what is the recommended way of obtaining internet access in such situations?

Could you please enable and distribute an update? The module is CONFIG_TOUCHSCREEN_USB_COMPOSITE, and it includes lots of drivers.

I bought this amoled screen that is designed for Raspberry pi 4B 8GB: https://www.waveshare.com/5.5inch-HDMI-AMOLED.htm

I have tried all possible versions of Android for Raspberry (LineageOS, Omnirom, Raspand) and Emteria OS now but all Android OS have the same problem, i.e. display is not supported load for this screen.
I tested on my tv screen and Android works well.

I have tried to find the solution which should probably be to add something to the config.txt file but no one so far has been able to help me, also on all forums. If you have a solution for me that would be great!

Thanks for your help,

I'm trying to use the Sensor DS1820 for temperature mesure. I need to run a command using modprobe but it shows the message "No modules given", and the folders in path "/sys/bus/w1/devices/" are not there / created.

I found another thread about this, and it's still unresolved:
https://forum.emteria.com/discussion/368/1-wire-on-wiringpi-missing-w1-folder-by-path-sys-bus-w1-devices

Any news on that? It is possible to use this sensor with the emteria.OS?

Thanks

New to Emteria and first-ever attempt to setup a Raspberry Pi 4 with Android and Apps. I have a multi-boot SD card with Touch Screen working on the below display no issues with 3-4 standard OS builds (Pi default, Ubuntu etc). However my new SD with Emteria has no touchscreen functioning. I believe this is a known issue? This is needed as I am booting to this display as a wall mounted kiosk-mode device.

Any ideas from users - or thoughts on future support (or try older build for possible support)? Thanks.

Amazon link: https://www.amazon.com/Portable-Touchscreen-Monitor-KENOWA-1920x1080/dp/B08SC6BDBH?ref_=ast_sto_dp&th=1

Details: 13.3 inch Portable touch screen display Kenowa mobile display Ultra-thin display 1920x1080, 2 standard HDMI ports and DC power supply, USB port, full HD IPS touch screen compatible switch XBOX PS4 laptop Raspberry Pi

This is the code I use to run the DcMotor

using System;
using Iot.Device.MotorHat;
public class DCMotorController : BaseClass
{
public void StartMotor()
{
using (var motorHat = new MotorHat(1600, 0x40))
{
var dcMotorOne = motorHat.CreateDCMotor(1);
dcMotorOne.Speed = 1;
Wait(1500);
dcMotorOne.Speed = 0;
}
}
}


But I am getting this error:
Unhandled exception. System.InvalidOperationException: Unexpected value of duty cycle (9766, 10280)
at Iot.Device.Pwm.Pca9685.g__OnOffToDutyCycleSampled|16_0(UInt16 onCycles, UInt16 offCycles)
at Iot.Device.Pwm.Pca9685.OnOffToDutyCycle(UInt16 on, UInt16 off)
at Iot.Device.Pwm.Pca9685.GetDutyCycle(Int32 channel)
at Iot.Device.Pwm.Pca9685PwmChannel.get_ActualDutyCycle()
at Iot.Device.Pwm.Pca9685PwmChannel..ctor(Pca9685 parent, Int32 channel)
at Iot.Device.Pwm.Pca9685.CreatePwmChannel(Int32 channel)
at Iot.Device.MotorHat.MotorHat.CreateDCMotor(Int32 motorNumber)

I have a RPi 4B 8GB and the reportedly supported Waveshare 7.9" display. No matter what I try, I simply cannot get to the Emteria boot logo. FWIW, The basic Raspberry Pi Debian build works flawlessly after adding the Waveshare HDMI lines to config.sys.

Here's what I've tried:

In this thread, in the second comment, OP says he has same setup as me. He says

In addition to this I want to add that the same RPI [4B] with the same Emteria.OS [11.3.0] installed on it works well with my PC's screen and with another Waveshare screen (with this one https://www.waveshare.com/7.9inch-hdmi-lcd.htm ) and does it out-of-box.

(a) I tried the same thing: flash from tool > eject > + boot from SD card
upon applying power, a distorted rainbow shows up, which fades out and stays black.

(b) I added the Waveshare code at the bottom of config.sys
hdmi_group=2
hdmi_mode=87
hdmi_timings=400 0 100 10 140 1280 10 20 20 2 0 0 0 60 0 43000000 3
Better! upon applying power, a single clear rainbow square shows up, followed by a fast scroll of text (with 4x raspberries on top), but immediately after this, the screen turns black (presumably here is when the Emteria logo should have shown).

(c) I commented out dtoverlay=vc4-kms-v3d-pi4,noaudio
The same text scrolling shows up, but is slower and continues infinitely like OP states in the thread above

(d) I un-commented the line and added an F for fake kms to make dtoverlay=vc4-fkms-v3d-pi4,noaudio
Same result as (c).

(e) I went back to (b) and kept dtoverlay=vc4-kms-v3d-pi4,noaudio but commented out disable_fw_kms_setup=1
Same result as (b).

Now when I look at config.sys, mysteriously, my timings line has disappeared from the config.sys and a cma-256 has shown up before noaudio in the kms line

(f) I added the timings line again, kept dtoverlay=vc4-kms-v3d-pi4,cma-256,noaudio untouched and disable_fw_kms_setup=1 commented out
A clear rainbow square shows up, followed by the infinite scrolling text BUT the text is interlaced and unreadable.

I've tried versions 11.8.0, 11.6.0, 11.5.0 with all variations above. I think I have close to 400 boots on my raspberry pi at this point, which is probably bad for its electronics, so before I fry the components - what can I do to get this to boot?

If a HDMI display is connected, the device starts on it without using the touchscreen.

Did anybody managed to get the official 7” touch screen to work?

I am having difficulty using a brand new Raspberry Pi 4 B with the official 7" touchscreen. I have it hooked up using the DSI connector + 5V/GND on the GPIO. It displays great, and keyboard and mouse input work fine, but as soon as I try to touch anything on the screen the input locks up.

I've tried this with both 11.6.0 Live and 11.6.1 Nightly (the latest nightly).

I am happy to take a short video and link to it as well if that would be helpful.

Thanks for your help!
-Erik

There is not enough frequency. The minimum pulse duration is 50 milliseconds, to supply control to the address tape, a duration of 350 nanoseconds and 900 nanoseconds is needed, respectively, for 0 and 1.

These commands show that the PWM is not enabled:
cat /sys/kernel/debug/pwm
ls /sys/class/pwm/

To do this, pin 13 is used as a PWM, described in the device tree.

Tell me how to enable PWM for 13 pins in Emerita, Advanced license?

I´m running Emteria.OS v11.3.0 on a Rspberry Pi4 Model B 2GB.
We installed some App´s, most important google chrome and easescreen (digital signage)
On both is the same problem. I can install the App but if I want to start it - it looks like the app want to start but jumps back into the Android interface.

With the Raspberry Pi 3 it works.

Any ideas???

KR Ramon Theussen

1. How you are justifying the emteria.OS is supported commercial use.

2. What is the advantage compare to LineageOS (non commercial).

3. How to change the boot image & boot animation

4. Will you support to use android IO drivers (SPI, I2C, UART & GPIOs)

5. How to download the Emteria.OS android 7 for both raspberrypi 3B & 4B

We have some issues with a connected kiosk printer: if the Raspberry 3 gets restarted, the app always asks the "Allow the app {APPNAME} to access the USB device?" question. If I allow it and check the "Use by default for this USB device" it works and doesn't ask again if I restart the app - however, as soon as the RB3 gets restarted, this message pops up again. One of the sites where we installed our device experience power loss a few times per week and this already causing issues for us.

As the machine is running as an unattended terminal, this is a pretty serious issue for our project - are there any solutions or workaround for this?

Thank you.

The modem is a generic Qualcomm device, which can be turned into a serial device with usb_modeswitch from the shell.

I can then directly issue the relevant AT commands from the shell to make it connect.

However, the version of pppd does not seem to be compatible with any of the guides online, and refuses to start a connection. The Emteria install doesn't appear to have a chat binary either.

Ideally I'd like to find/build a working pppd/chat/wvdial (whatever works) connection script that can be run at boot, but I'm not very well versed on which versions of these tools can be built to run in this environment.

Options like the infamous PPPWidget are off the table as (a) It requires Play Store and (b) It allows user interaction, both of which are unsuitable for a kiosk product.

Can someone advise on a correct build of these executables, or appropriate binaries? The existing discussions don't appear to reflect the current version of the tools in question.

I have installed Emteria on IOT Artist Board with Raspberry CM3 and I would like to send and receive bytes with the UART.
I downloaded "sample apps serial" for Emteria Github but it doesn't compile in Android Studio:

A problem occurred configuring project ': app'.
java.lang.NullPointerException (no error message)

Thank you
Donatello

how to fix it?

Emteria (1.3.53) is booting with it, although eventually get the "No signal" issue, but the touch screen is not working.
Is there a way to load these drivers on Emteria?

Thanks.