Xiyaun, could you provide any feedback on "no network" vs "sleep" in Kiosk mode?

The app developer should have offline_mode enabled. Also, as soon as the app starts, the app developer should use chrome.power API and prevent the device from going to sleep.

Check out StartupAppLauncher::MaybeInitializeNetwork [1]. |requires_network| is true on the following two scenarios:
1. App is not installed and there is no cached crx to install it;
2. App is installed but does not claim "offline_enabled": true;

When any of the two happens, the device would stay on the splash screen and wait for the Internet before it attempts to install or launch the app. The default power policy would be in effect.

If the app handles internet connection, it should "offline_enabled": true in its manifest so that app launching code skips the network check.

[1] https://cs.chromium.org/chromium/src/chrome/browser/chromeos/app_mode/startup_app_launcher.cc?rcl=08b8e66cea8b533cbdbf6ec4649a9b58837d0f31&l=188

ChromeOS version: 62.0.3202.82 (Official Build) (64-bit)
ChromeOS device model: AOpen Chromebox Commercial
Platform: 9901.66.0 (Official Build) stable-channel ninja 
Firmware Version: Google_Ninja.5216.383.7 

Case#: 14056779

Steps to reproduce: 
1. Setup Kiosk Settings
Public Session 
Kiosk>Allow Public Session Kiosk.

Auto-Launch Kiosk App>Kiosk for Teamviewer-Remote Desktop (actual customer is using MealViewer Kiosk app)

- using both DP and HDMI ports and HDMI display was the main monitor.
2. Assign AOpen Chromebox Commercial for this OU.
3. Reboot AOpen Chromebox Commercial and make sure that Kiosk works as well.
4. Disconnect internet connection from a hotspot and shut down the device.
5. Reboot AOpen Chromebox Commercial and the start up process stops at "Network not available" window. 
6. Leave AOpen Chromebox Commercial for 10 minutes + and the monitors go to sleep(device's power button is not flashing).
7. Try to restart/awake from the attached keyboard and mouse however the device does not response.
8. Press and hold the power button for 10 second + and the device shutdown.

Current Behavior / Reproduction: 
AOpen Chromebox Commercial does not start/wake from sleep mode.

Expected Behavior: 
AOpen Chromebox Commercial should awake by keyboard / mouse action.


Additional info.
I could reproduce the same issue at locally but only 2,3 times.
After completed above test, and I was testing below single monitor test, since then I can not reproduce the same issue.(even dual monitors)
-Could not reproduce the issue when using a single monitor with DP >DVI monitor(HP).
-Could not reproduce the issue when using a single monitor with HDMI >HDMI  monitor(I was using LG Chromebase HDMI).

- I tested from Chromebook 11 Model 3180(kefka) M62.0.3202.82 and ASUS Chromebox CN60 (Panther) M62.0.3202.82 with HDMI however could not reproduce the same issue.
-there is other display issue case for Ninja crbug.com/780122,but not 100% sure it is relating with this.

-Log files.

ASUS CN60 Device log.(tested: Nov 15 14:42) Could not reproduce.
https://drive.google.com/open?id=1bhvZxw35mhulEd-H6q260KDvGQ7ywVQc

Repro video.
https://drive.google.com/open?id=1N-8atvgT6YZOILzM6Uh4XQfbkaAG-cpD


AOpen Chromebox device log.(tested: Nov 15 13:54) could reproduce.
https://drive.google.com/open?id=1E1JAZjjHCxPnwME3MZgfhFOce8y5jC0F

Repro video.
https://drive.google.com/open?id=1cGtk0m6eQVrKf297FKPm8Om66Vp7pnmk

Policy.
https://drive.google.com/a/google.com/file/d/1h8eVYwE9v0rvzcrRVS_j3LeZXSMLC4xi/view?usp=sharing

Version
https://drive.google.com/open?id=1yPPHoo_hIM9fq-XHmmizNanbODY6tgHE

+benzh, marcheu, tbroch

Took a quick look at the repro log of ninja. The failed wake-up happens around 11/15 13:54.

In power manager log, it failed to ask frecon to power on the monitor:
====
[1115/135444:INFO:display_power_setter.cc(81)] Asking DisplayService to turn all displays on
[1115/135449:ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.DisplayServiceInterface.SetPower: object_path= /org/chromium/DisplayService: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Around same time, kernel log shows:
=====
2017-11-15T13:54:45.288428+11:00 WARNING kernel: [ 1474.116338] ------------[ cut here ]------------
2017-11-15T13:54:45.288456+11:00 WARNING kernel: [ 1474.116388] WARNING: CPU: 2 PID: 1123 at /mnt/host/source/src/third_party/kernel/v4.4/drivers/gpu/drm/i915/intel_display.c:1711 vlv_wait_port_ready+0x128/0x15a()
2017-11-15T13:54:45.288461+11:00 WARNING kernel: [ 1474.116407] timed out waiting for port B ready: got 0xf, expected 0x0
2017-11-15T13:54:45.288465+11:00 WARNING kernel: [ 1474.116420] Modules linked in: uinput ccm rfcomm snd_soc_sst_baytrail_pcm snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_sst_byt_max98090_mach btusb btrtl btbcm btintel ip6t_REJECT nf_reject_ipv6 snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_intel_sst_acpi snd_intel_sst_core snd_soc_max98090 snd_soc_sst_mfld_platform snd_soc_sst_acpi snd_soc_sst_match bluetooth zram fuse ip6table_filter iwlmvm iwl7000_mac80211 r8169 mii iwlwifi cfg80211 pl2303
2017-11-15T13:54:45.288468+11:00 WARNING kernel: [ 1474.116506] CPU: 2 PID: 1123 Comm: DrmThread Not tainted 4.4.79-11650-ge987f76b729a #1
2017-11-15T13:54:45.288471+11:00 WARNING kernel: [ 1474.116511] Hardware name: GOOGLE Ninja, BIOS Google_Ninja.5216.383.7 08/10/2015
2017-11-15T13:54:45.288474+11:00 WARNING kernel: [ 1474.116515]  0000000000000286 987d8970f3b2eb61 ffff880070d13958 ffffffff860941ce
2017-11-15T13:54:45.288477+11:00 WARNING kernel: [ 1474.116526]  ffff880070d139a0 0000000000000009 ffff880070d13990 ffffffff85e69858
2017-11-15T13:54:45.288480+11:00 WARNING kernel: [ 1474.116536]  ffffffff861f3a2d 0000000000186014 ffff88017a120000 000000000000000f
2017-11-15T13:54:45.288483+11:00 WARNING kernel: [ 1474.116546] Call Trace:
2017-11-15T13:54:45.288486+11:00 WARNING kernel: [ 1474.116557]  [<ffffffff860941ce>] dump_stack+0x4d/0x63
2017-11-15T13:54:45.288489+11:00 WARNING kernel: [ 1474.116565]  [<ffffffff85e69858>] warn_slowpath_common+0x9f/0xb8
2017-11-15T13:54:45.288492+11:00 WARNING kernel: [ 1474.116571]  [<ffffffff861f3a2d>] ? vlv_wait_port_ready+0x128/0x15a
2017-11-15T13:54:45.288494+11:00 WARNING kernel: [ 1474.116577]  [<ffffffff85e698c8>] warn_slowpath_fmt+0x57/0x73
2017-11-15T13:54:45.288497+11:00 WARNING kernel: [ 1474.116583]  [<ffffffff861dd702>] ? fwtable_read32+0xab/0xba
2017-11-15T13:54:45.288500+11:00 WARNING kernel: [ 1474.116589]  [<ffffffff861f3a2d>] vlv_wait_port_ready+0x128/0x15a
2017-11-15T13:54:45.288503+11:00 WARNING kernel: [ 1474.116597]  [<ffffffff86224fb3>] vlv_hdmi_pre_enable+0x70/0x79
2017-11-15T13:54:45.288506+11:00 WARNING kernel: [ 1474.116604]  [<ffffffff861e877f>] intel_encoders_pre_enable+0x56/0x63
2017-11-15T13:54:45.288509+11:00 WARNING kernel: [ 1474.116610]  [<ffffffff861f7ab3>] valleyview_crtc_enable+0x16e/0x1b7
2017-11-15T13:54:45.288511+11:00 WARNING kernel: [ 1474.116616]  [<ffffffff861f6b51>] intel_update_crtc+0x4c/0xc8
2017-11-15T13:54:45.288514+11:00 WARNING kernel: [ 1474.116623]  [<ffffffff861f6c1e>] intel_update_crtcs+0x51/0x5c
2017-11-15T13:54:45.288517+11:00 WARNING kernel: [ 1474.116629]  [<ffffffff861fb8cc>] intel_atomic_commit_tail+0x4d0/0xd9e
2017-11-15T13:54:45.288520+11:00 WARNING kernel: [ 1474.116636]  [<ffffffff861f0560>] ? intel_atomic_commit_ready+0x64/0x69
2017-11-15T13:54:45.288523+11:00 WARNING kernel: [ 1474.116643]  [<ffffffff85e8b596>] ? ___might_sleep+0x44/0x14e
2017-11-15T13:54:45.288526+11:00 WARNING kernel: [ 1474.116649]  [<ffffffff861fc5b8>] intel_atomic_commit+0x41e/0x444
2017-11-15T13:54:45.288528+11:00 WARNING kernel: [ 1474.116657]  [<ffffffff8617fbcd>] ? drm_atomic_set_crtc_for_connector+0xc0/0xe6
2017-11-15T13:54:45.288531+11:00 WARNING kernel: [ 1474.116664]  [<ffffffff86180945>] drm_atomic_commit+0x4b/0x50
2017-11-15T13:54:45.288534+11:00 WARNING kernel: [ 1474.116672]  [<ffffffff8616942e>] drm_atomic_helper_set_config+0x53/0x98
2017-11-15T13:54:45.288537+11:00 WARNING kernel: [ 1474.116678]  [<ffffffff86176a97>] drm_mode_set_config_internal+0x5e/0xff
2017-11-15T13:54:45.288540+11:00 WARNING kernel: [ 1474.116684]  [<ffffffff861777f6>] drm_mode_setcrtc+0x3ce/0x47d
2017-11-15T13:54:45.288543+11:00 WARNING kernel: [ 1474.116691]  [<ffffffff8603fbfa>] ? avc_has_extended_perms+0x28b/0x37e
2017-11-15T13:54:45.288545+11:00 WARNING kernel: [ 1474.116698]  [<ffffffff8616f75c>] drm_ioctl+0x2a8/0x3dd
2017-11-15T13:54:45.288548+11:00 WARNING kernel: [ 1474.116704]  [<ffffffff86177428>] ? drm_mode_getcrtc+0x11a/0x11a
2017-11-15T13:54:45.288551+11:00 WARNING kernel: [ 1474.116710]  [<ffffffff86043972>] ? selinux_file_ioctl+0x141/0x185
2017-11-15T13:54:45.288554+11:00 WARNING kernel: [ 1474.116718]  [<ffffffff85f74cfa>] do_vfs_ioctl+0x42e/0x501
2017-11-15T13:54:45.288557+11:00 WARNING kernel: [ 1474.116724]  [<ffffffff8603d222>] ? security_file_ioctl+0x35/0x49
2017-11-15T13:54:45.288559+11:00 WARNING kernel: [ 1474.116731]  [<ffffffff85f74e24>] SyS_ioctl+0x57/0x79
2017-11-15T13:54:45.288562+11:00 WARNING kernel: [ 1474.116738]  [<ffffffff865060a1>] entry_SYSCALL_64_fastpath+0x1c/0x74
2017-11-15T13:54:45.288565+11:00 WARNING kernel: [ 1474.116743] ---[ end trace d28d3e77f70bb952 ]---

This "vlv_wait_port_ready" looks similar to #12 of issue 780122,

the customer at C#4 has added some information:
-hardware info, such as, which port(s) are used: 
HDMI
-Display model info: 
LG SM5KD/C to any number of commercial or consumer TVs our customer's may have
-When having the issue, please check the power button and let us know it is flashing or not: 
The power button is flashing, yes.

Unable to reproduce on Ninja and Veyron-Fieval using M67 Dev build.