Common reason for black screen and its solution.

[ric96]

Most of the issues that i receive on the topic of "blank screen" are from TV owners. Most lcd TVs do a tonn of post processing, most (in)famously they upscale the input refresh rate from 30hz to as much as 100hz. These manufacturers also advertise the product as a 100hz tv.

Now the gpu driver for the rpi is in a early development stage and such post processing confuses it and hence the blank screen.

SOLUTION: I do not own a tv so not a 100% sure but most TV have a game-mode or pc-mode option, enabling this disables almost all post processing and should work.

[Aradyn]

Unfortunately ric, there is no pc-mode or game-mode option. The solution was discovered today that can resolve the black screen flashing for most people though, wondering if it would resolve the blank screen issue for others as well. There are 2-3 changes that need to be made under the boot partition -> Config.txt
hdmi_drive = 2 for HDMI, 1 for DVI (it is supposed to be for audio purposes, but I found audio was going through either way.) -> Select 2 since they are going through HDMI to TV
hdmi_group = 1 (for cea/tv) , 2 ( for dmt/monitor) ->  TV users select 1
hdmi_mode = 16 for 1080p/60hz or 4 for 720p/60hz (note: the hdmi_mode is different based on the hdmi_group you select)

[Joao Bosco Santos]

Long I've been trying to install android on raspberry pi, but it is only in black screen , now managed to install the VGA monitor with an adapter, more on my Sony Bravia TV can not , please help me .

[ma...@marktheeditor.com]

Same here, just a black screen on Sony Bravia, tried various modes with no luck and tweeked config with no luck.

[patri...@gmail.com]

Yup seems as if the GPU drivers are still having issues. Post processing isn't the issue at all. It's simply detection support. 

[joaobo...@gmail.com]

The following video specifications of my TV

[h4chik...@gmail.com]

Hi, i tried the setting above but i still can not get my raspberry pi 3 running android marshmallow past the rainbow splash screen when i use our tv set as monitor using rca cable. My rpi3 and marshmallow works just fine with my lcd monitor using hdmi-to-dvi cable. The rpi3 also works fine with raspbian jessie and open elect together with our tv set. So i guess i just need the right setting for the marshmallow. If you have other suggestions, i will appreciate it very much. Our tv set only has rca ports, no dvi nor hdmi. Thank.

[mate...@gmail.com]

Hello i have recently installed RTAndroid on my PI3 and it says unsuported signal on my Sony TV, Tried on LG TV everything works brilliant.

Tried changing config file, still no luck, any help? 

[Igor Kalkov]

If you tried setting every possible resolution and your TV doesn't support it, don't know either. Maybe a TV issue?!

You used "hdmi_group=1", correct?

[mate...@gmail.com]

yes,

my config

hdmi_force_hotplug=1

hdmi_drive=2

hdmi_group=1

hdmi_mode=16

[marin....@gmail.com]

i have the same issue with my panasonic 42"

do you have an idea for the best parameter?

[Giorgio]

Yeah me too with a panasonic 42" I also tried play with the frequency I can choose 50hz or 100hz but nothing changed

[Igor Kalkov]

You can also try using higher values for hdmi_boost and / or include ignore_edid. Example here: https://github.com/RTAndroid/android_device_brcm_rpi3/blob/80e93ecaa964d485ce5dd2147b4bf7c15886a85a/boot/config.txt

[marin....@gmail.com]

hello,

i find a begin of solution.

For me i see now the rainbow at the start of the boot with parameter 

hdmi_group=1 

hdmi_mode=31

But nothing is working after.

Before i don't see the starting rainbow...

[denny...@gmail.com]

Edit the Config.txt file and deactivate the drivers if your display goes blank. Just put a # infront of the entry for dtoverlay=vc4-kms-v3d.

When itś not working, you must upgrade your raspi firmware. I think, the problem is opengl driver.

[Marin Dumont]

When you say « deactive the driver »

You speak about witch line ?

 

De : andro...@googlegroups.com [mailto:andro...@googlegroups.com] De la part de denny...@gmail.com
Envoyé : samedi 24 septembre 2016 19:05
À : Android-rpi
Cc : giorgiop...@gmail.com; marin....@gmail.com
Objet : Re: Common reason for black screen and its solution.

--
You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/ciILTnABiKA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-rpi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/d2a3e50f-c0ec-45ff-8135-9a8dd92d94b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[denny...@gmail.com]

You must only put a # infront of dtoverlay=vc4-kms-v3d. Thatś it.

When this is not working, than you must make a firmware update with  "sudo BRANCH=next rpi-update"

I think itś a problem with opengl driver. See here: https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=140865



[Marin DUMONT]

I do that but I have the same issue. It's block at the raspberry boit screen

--

Marin Dumont

Rue de bonne 97/6 

1080 Bruxelles

GSM: 0479805939

site: 

http://www.cedricgervy.be

http://www.marindumont.be 

[denny...@gmail.com]

Do you have make a "sudo BRANCH=next rpi-update"?

I hope this thread can help you: https://github.com/Hexxeh/rpi-update



[Marin DUMONT]

No because I can't boot correctly.  Tomorrow I try to Boot with an other screen and after I can do that :-)

Sorry  for my bad english

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/1f405a6e-b8e3-4fff-849b-7d77b5b67664%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[denny...@gmail.com]

OpenGL for Raspi3: http://www.raspberryconnect.com/gamessoftware/item/314-trying_out_opengl_on_raspberry_pi_3

[Marin DUMONT]

I try it tomorrow

--

You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/ciILTnABiKA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-rpi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/7d183beb-f891-46b2-a0ea-73ad596e14f0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[abdulreh...@gmail.com]

hello

[Marin Dumont]

No more news ?

 

De : andro...@googlegroups.com [mailto:andro...@googlegroups.com] De la part de abdulreh...@gmail.com
Envoyé : mardi 27 septembre 2016 16:45
À : Android-rpi
Cc : mate...@gmail.com; "mate..."@gmail.com

Objet : Re: Common reason for black screen and its solution.

 

hello

--
You received this message because you are subscribed to a topic in the Google Groups "Android-rpi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-rpi/ciILTnABiKA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-rpi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-rpi/1ca6d9c8-05aa-4d3e-9453-df4377c519d9%40googlegroups.com.

[WalkOnATYCLB]

I check this group everyday. Very quiet :(

[geor...@googlemail.com]

Hi,

i have the same isue with a Dell ST2220t display.
I tried all described configurations and get only an raspberry boit screen.

Someone have successfuly fix this problem?

[ma...@pleskac.net]

Hi,

Any news regarding the fix?

Thanks!

Dne středa 22. června 2016 12:48:34 UTC+2 ric96 napsal(a):

[daniel...@gmail.com]

I have an old SANYO TV, it runs fine with chormecast 720p 1280x720 @ 60Hz. It also run with Raspbian and NOOBs. However I cannot make it run with Android Raspbery Pi.

I tried different images, and config.txt configurations. I get the rainbow boot screen then it seems to crash, got a (blue) no signal screen in my case. 

I tried every possible configuration in config.sys, finally I disabled the openGL. Now it hangs on rainbow screen forever. But no boot.

Driver is not stable and with no debugging output I have no clue how to fix it. :(

Perhaps the developer can give some pointers on how to debug the driver and contribute to the project?

Below is my config:

--

hdmi_force_hotplug=1

hdmi_drive=2

hdmi_group=1

hdmi_mode=4

disable_overscan=1

config_hdmi_boost=5

kernel=zImage

device_tree=bcm2710-rpi-3-b.dtb

dtparam=audio=on

dtparam=i2c1=on

dtparam=i2c_arm=on

#dtoverlay=vc4-kms-v3d,cma-256

initramfs ramdisk.img 0x01f00000

mask_gpu_interrupt0=0x400

avoid_warnings=2

gpu_mem=256

enable_uart=1

--

[ice...@gmail.com]

problem can be solved by change
debug.drm.mode.force= "pixel_width x pixel_height"
in /system/build.prop file

for this you should install adb on you PC
than

adb connect ip_of_device
adb root
adb remount
adb pull /system/build.prop

change line for example
debug.drm.mode.force="

1280x720"

than

adb push build.prop /system/build.prop

суббота, 15 октября 2016 г., 23:24:09 UTC+3 пользователь daniel...@gmail.com написал:

[bnpo...@gmail.com]

ADB seems to only work if you have an Android device that's actually running.  I can't get rtandroid to boot (because of the resolution issue), so I can't access the system files via adb.  Are there any other ways to edit the build.prop file?

[ice...@gmail.com]

Strange, if you have resolution issue, android should run, need to wait when it will be booted.

Solution for edit file: use linux -> enter to system folder and with su premission edit it or for windows use some program that can see ext4 format of partition.

[Igor Kalkov]

If it doesn't boot with a monitor connected, just pull the HDMI cable and try it again. RTAndroid can boot without a connected display and you will get ADB access.

[Alexander Abibas]

I think the config does not affect the resolution and refresh rate of the display in the Android!
Because i lnstall RTandroid with config:
hdmi_force_hotplug=1
hdmi_drive=2
hdmi_group=1
hdmi_mode=16
hdmi_ignore_edid=0xa5000080
config_hdmi_boost=4
disable_overscan=1

When connecting the RPi to the TV I see the inscription "Android_" But I do not see the logo. the screen goes black.
When connecting the RPi to the PC monitor I see the inscription "Android_", logo and everything loads fine.
My monitor (Dell UltraSharp U2410) shows that the signal by HDMI has a resolution of 1280x800 and the refresh rate of 53Hz. But my TV (AOC L32W751A http://www.hdtvreview.com/pdf/aoc-l32w751a-specs.pdf ) does not support this refresh rate.
Why 1280*800@53Hz ? if hdmi mode of my config is = 1080p 60Hz! That's why I think so.

[miked...@gmail.com]

THe RPI is turned on with a USB Keyboard, USB Mouse, power cable and ethernet cable attached. With the recommendation to start ADB and attach to it, I'm not sure how I get the RPI3's IP address when it is booted to an OS that I can't access in any way. What I tried was booting the same device into raspbian, running ifconfig and getting the eth0 MAC address. Then I booted back into android, and went to my network router's DHCP table and searched for the MAC address. Then from my Ubuntu console I tried ./adb connect 192.168.1.48:5555 and got back unable to connect to 192.168.1.48:5555: No route to host. I read that ADB can connect through USB too. On the PI the micro-usb port is being used for power and 2 of the four USB ports on the back are being used for keyboard and mouse. Can one of the remaining two be connected directly to my Ubuntu?

Thanks,

Mike

PS my config.txt and build.prop files are below. I pulled these off the microSD card while it was attached to my PC

config.txt

====================================

hdmi_force_hotplug=1

hdmi_ignore_edid=0xa5000080

config_hdmi_boost=4

hdmi_group=2

hdmi_mode=69

disable_overscan=0

overscan_left=24

overscan_right=24

overscan_top=24

overscan_bottom=24

#hdmi_force_hotplug=1

#hdmi_drive=2

#hdmi_group=2

#hdmi_mode=69

#hdmi_ignore_edid=0xa5000080

disable_overscan=1

config_hdmi_boost=5

kernel=zImage

device_tree=bcm2710-rpi-3-b.dtb

dtparam=audio=on

dtparam=i2c1=on

dtparam=i2c_arm=on

dtoverlay=vc4-kms-v3d,cma-256

initramfs ramdisk.img 0x01f00000

mask_gpu_interrupt0=0x400

avoid_warnings=2

gpu_mem=256

enable_uart=1

build.prop

======================================================

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=NDE63P

ro.build.display.id=rpi3-userdebug 7.1 NDE63P 11 test-keys

ro.build.version.incremental=11

ro.build.version.sdk=25

ro.build.version.preview_sdk=0

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=7.1

ro.build.version.security_patch=2016-10-05

ro.build.version.base_os=

ro.build.date=Sa 5. Nov 01:52:41 CET 2016

ro.build.date.utc=1478307161

ro.build.type=userdebug

ro.build.user=jenkins

ro.build.host=halhof

ro.build.tags=test-keys

ro.build.flavor=rpi3-userdebug

ro.product.model=Raspberry Pi 3

ro.product.brand=Android

ro.product.name=rpi3

ro.product.device=rpi3

ro.product.board=

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.cpu.abilist=armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.product.manufacturer=brcm

ro.product.locale=en-US,ko-KR,ja-JP,zh-CN,hi-IN,en-GB,de-DE,fr-FR,it-IT,ru-RU,es-ES,pt-PT

ro.wifi.channels=

ro.board.platform=bcm2710

# ro.build.product is obsolete; use ro.product.device

ro.build.product=rpi3

# Do not try to parse description, fingerprint, or thumbprint

ro.build.description=rpi3-userdebug 7.1 NDE63P 11 test-keys

ro.build.fingerprint=Android/rpi3/rpi3:7.1/NDE63P/11:userdebug/test-keys

ro.build.characteristics=tablet

# end build properties

#

# from device/brcm/rpi3/system.prop

#

debug.drm.mode.force=1280x800

ril.function.dataonly=1

ro.build.selinux=1

ro.opengles.version=131072

ro.radio.noril=1

ro.rfkilldisabled=1

ro.sf.lcd_density=213

wifi.interface=wlan0

#

# ADDITIONAL_BUILD_PROPERTIES

#

keyguard.no_require_sim=true

ro.com.android.dataroaming=true

ro.config.ringtone=Ring_Synth_04.ogg

ro.config.notification_sound=pixiedust.ogg

ro.carrier=unknown

ro.config.alarm_alert=Alarm_Classic.ogg

ro.ril.hsxpa=1

ro.ril.gprsclass=10

ro.adb.qemud=1

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=80m

dalvik.vm.heapsize=384m

dalvik.vm.heaptargetutilization=0.75

dalvik.vm.heapminfree=512k

dalvik.vm.heapmaxfree=8m

persist.sys.dalvik.vm.lib.2=libart.so

dalvik.vm.isa.arm.variant=cortex-a7

dalvik.vm.isa.arm.features=default

dalvik.vm.lockprof.threshold=500

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

[Alexander Abibas]

Nnow i install android AOSP android-7.1.0_r4 + GApps for RPi3
When connecting the RPi to the TV  the screen goes black.(unknown HDMI signal)
When connecting the RPi to the PC monitor everything loads fine. My monitor (Dell UltraSharp U2410) shows that the signal by HDMI has a resolution 720p. App Aida64 show me 1280x720 and the refresh rate of 60Hz.
I do not understand what is wrong with my TV?!
I think the screen turn black when the kernel is included

[bjs...@gmail.com]

You aren't able to connect using adb because networking isn't enabled.  You need a monitor and keyboard/mouse to turn on wireless every boot.

On Saturday, November 5, 2016 at 1:15:10 AM UTC-7, Igor Kalkov wrote:

[geor...@googlemail.com]

Hi,

Somone tried to edit the /system/build.prop directly on the sd-card with a windows pc?

thx

[openbs...@gmail.com]

Two months later, do you have any solution for this issue?

On Tuesday, September 13, 2016 at 9:36:24 AM UTC-5, mate...@gmail.com wrote:

Hello i have recently installed RTAndroid on my PI3 and it says unsuported signal on my Sony TV, Tried on LG TV everything works brilliant.

Tried changing config file, still no luck, any help? 

[Igor Kalkov]

There will be no solution until somebody figures out the correct resolution for your TV.