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.

[bjs...@gmail.com]

Take a look at the post from ice...

 /system/build.prop file

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

I had to change the entry in the file on the SD card to exactly 1280x720 to get this to work.  I made the change by mounting the SD card on my linux workstation.  If you have windows, you'll need to mount and edit it with whatever tools you have.  ADB doesn't work because wireless isn't enabled and you can't enable it without a monitor.

[Mike Dice]

I was able to get to a spinning RTAndroid logo but no further. Just stuck on that screen for hours until I unplugged the PI. Monitor connected or not, no way I can find to connect to ADB. PI has Ethernet cable plugged in

Sent from my iPhone

--

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/f5b31fff-e4cb-4a65-92d2-920844fb5b85%40googlegroups.com.

[Igor Kalkov]

Hi Mike, please try to reinstall the RTAndroid image with "-f" flag only and boot it without a monitor connected. Wait 10 minutes and try to connect via ADB (in case you can find out RPi's IP address).

[bjs...@gmail.com]

Try changing this line in build.prop from:
        debug.drm.mode.force=1280x800
to
        debug.drm.mode.force=1280x720

This worked so that I could see the display on my TV.  I was then able to activate wireless.  You might be able to connect to it if you use an ethernet cable for the PI.  I think a wired connection comes up when wireless may not.

[bjs...@gmail.com]

Never mind about wired vs. wireless.  I see you already tried that.  That section didn't register in my feeble brain.

[fferrar...@gmail.com]

Hi,

I downloaded some time ago from the Geek Till It Hertz website the image for Android TV 7.1 and tried to let it run on my RPi3 without any success.

I don't have a PC monitor to test, but 3 TVs (one 19" 720p Samsung, one a bit old 37" 1080p Panasonic and a 26" 720p Sony Bravia) connected to RPi through the HDMI (real HDMI cable, no adapters).

Just to avoid one possible variable, I used same HDMI cable to connect the Pi to all these TVs.

I searched a bit in this forum and in several other sources on the web, so this is what I did:

1) RPi update

Loaded the latest Raspbian image on the Rpi, then from command line i launched

sudo apt-get install rpi-update

sudo rpi-update

sudo apt-get upgrade

sudo apt-get update

Seems like this was needed to update the firmware of CPU and GPU of the RPi hardware, or am I wrong?

Anyway after this the system booted correctly with Raspbian, LibreElec and OSMC, but not for Android TV

2) Edit config.txt

Tried lots of combination of settings for parameters hdmi_drive, hdmi_group, hdmi_mode and hdmi_boost.

I can not post all the combinations I tried, even forcing lower resolutions like 800x600.

Tried the combinations both with parameter dtoverlay=vc4-kms-v3d activated or deactivated by putting the # in front of the line

3) Edit build.prop

One of last suggestions in this thread was to edit the build.prop line

debug.drm.mode.force=1280x800

into

debug.drm.mode.force=1280x720

so I mounted the SD from an Ubuntu distro and saw that the parameter was already set at 1280x720, so I did not change anything.

Maybe the only thing I might try is to change it into 1280x800 but I fear this will make thigs not working anyway.

Result:

Some settings hang the system at boot (with a fixed rainbow screen and no apparent activity from the RPi LEDs), but the best results I got with some configurations were

- Panasonic TV: rainbow screen, then black screen after a couple of seconds. RPi shows activity from LED.

After waiting 20/25 minutes I unplugged the power and mounted the SD on a PC: two new EXT4 partitions were created on the SD, so the RPi was doing something behind that black screen

- Samsung TV: rainbow screen, then the Android word after a couple of seconds. Then after 15/20 seconds the image becomes garbled and full of grey pixels and stays like that till I turn the Pi off

RPi shows activity from LED as well and also in this case the two new EXT4 partitions were created on the SD.

- Sony TV: same as Samsung TV

If you have other suggestions let me know.

For the GTIH guys, are you planning some future development for this build to fix the issue or we must take as it is?

Thanks

[reece...@gmail.com]

Same issues here with an old Sony Bravia KDL-37V4000 TV, it always says "Out of Range".  Interestingly, it does seem to be something to do with the Android image itself as the TV correctly identifies the input signal set by config.txt (I've tried many different configurations) for the first few seconds, but then afterwards it fails with the "Out of range" message.  (Raspberry Pi 3).

[haa...@gmail.com]

It looks like (after the first screen with the rainbow/android text with a resolution based on boot/config.txt) it always continues with the RTandroid logo and uses the settings in build.prop on all my monitors/tvs which by default is set to:

debug.drm.mode.force=1280x800

[D3ADWA1T]

Hey Sahaj, i have your AndroidTV 6.0 version working on my Pi3...i was having a few issues, can you PLEASE help me with ANY of them??

1) I installed open gapps with adb, but it keeps auto-updating the play store app. 

    and then it stops working and asks to uninstall updates and then it works for some time and then again updates. how to stop this??

2) It seems it can't recognize USB devices! Does it need some drivers? How to get it to work??

3) I used a 64GB MicroSD card, but the build only uses ~6GB...how do i utilize the maximum space?? This is a built-in feature for Raspbian, but how do i achieve this in Android?

Please can you help me in any of these areas?Any help will be greatly appreciated!!

[D3ADWA1T]

Hey Sahaj, i posted the same (as above) in the Marshmallow thread some weeks ago, i thought it didn't give you a notification or got lost in translation somehow because i didn't get a reply from anyone so i posted it here... i hope it's okay

And I'm sure everyone with working screens also will have these problems, so did you at least encounter them?

[Azeo]

I've posted this in another topic but this is closer "to the top" so hope I haven't made a newbie etiquette faux pas!

I had problems setting refresh rates for an old monitor using config.txt and found a great resource here, Examining build.prop tweaks for Android ICS: A comprehensive guide (Part 1) by Jeff Mixon.

Using Jeff's info, added an extra line to build.prop -  windowsmgr.max_events_per_sec=90 which apparently equates to a (default) refresh rate of 60Hz. Magically, this kicked back the refresh so the old 107 would display at a higher resolution than 1024x768.

This may be something worth trying/playing with for monitors or TV's that are getting garbled or out of range displays to see if the refresh can be explicitly set. I don't know yet if removing the display setting in build.prop allows config to take control of resolution and refresh, but will give that a go.

I don't have an hdmi monitor or tv so don't know how problematic the CEA settings may be with android, but as most tv's seem to have vga as well, it may well be worth people getting a cheap hdmi-vga converter to try the vga settings if nothing else has worked, particularly if adb testing shows Android is awake on the pi. I guess this ties in with Sahaj's solution above to try game-mode or pc-mode.... I didn't know TV's do all that post processing, good to know!

[mail....@gmail.com]

I have it working on Sony KDL40650W TV just by commenting the line in build.prop (#debug.drm.mode.force=1280x800)  and set config.txt according to TV 720p (hdmi_group=1, hdmi_mode=4, commenting the framebuffer values)

[aeb0...@nifty.com]

I made androidTV start more than a SD card, but a screen is while being black.
Is it the cause that VGA-HDMI change is being used?
The first iridescent picture is output and sticks to a green LED, and I disappear, and it's being repeated.
A change cable cause or additionally please tell me a clue.

2016年6月22日水曜日 19時48分34秒 UTC+9 Sahaj Sarup:

[bpe...@gmail.com]

Thanks!!!! That worked on my Sony Bravia too !!

[openbs...@gmail.com]

Great can you publish one .img with the final Android image with this change. Thank you!

[bpe...@gmail.com]

Bad news, I though that it was working when I saw the Android logo for the first time, but the OS doesn't load, it gets stuck at this screen.

[pj.ne...@gmail.com]

I'm trying to debug this issue as well. I haven't dealt with the raspberry pie much, how are you capturing logs? 

[boris...@bihelios.de]

Same Problem here. Tested 2 TVs with edited and unedited config.txt. "No Signal". Green LED on RPI shows ativity. I don´t have a "/system/build.prop file" file.

[Broten Technologies Corporation]

You have a build.prop file it is on the system partition. A linux partition.

[boris...@bihelios.de]

Thanks, found it. But still no signal, after I set the right resolution in the build.prop.

[Thursor Holdings Limited]

hello all ....

Any news ??

maybe any Android version that is working whit Sony TV ??


Saludos

[pj.ne...@gmail.com]

I pretty sure this is an issue across multiple TV brands. I have done testing across multiple TV brands. I don't know if anyones notice this but once you get stuck on the grey/black screen, if you have a keyboard connected, all you have to do is hit the down arrow key three times and hit enter then it will take to to the launcher

[chris.cann...@gmail.com]

My screen is not completely black. It says Android. Appears to be terminal of some sort with a flashing cursor. But nothing beyond this

Any ideas

[bigyanc...@gmail.com]

Hey buddy,

I tried both androidthings and rtandroid. When I tried to configure androidthings I got stuck in the logo screen for more than 6 hours and then I tried to reconfigure, something went wrong this time in an another way. Then I tried RTAndroid from Linux. I followed the instruction as mentioned there. At last of the installation it said: "Installation Successful. You can now put your sdcard in the RPi." And then I did as mentioned and connected my RPi to my monitor via HDMI cable. And now I see no response at all in my monitor. Do you notice, where have I done wrong? Thank You

[Igor Kalkov]

Are you using VirtualBox with Linux? Or full Linux installation?

Do you have a DVI->HDMI or any other converters in the line?

Does your monitor support the default 1280x720 resolution? Is something else is connected at the same time via DPI port?

[gg]

Configuration works also on a Sony KDL-40EX605, thanks.

[sanket...@gmail.com]

On Wednesday, 22 June 2016 16:18:34 UTC+5:30, Sahaj Sarup wrote:
> 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.

I used some display related configuration from below gist of mi box. It worked for me. And commented drm.mode.force

https://gist.github.com/ayufan/38f578cbff788afa7b8aea85422f2957