Elm: tablet mode: Virtual keyboard sometimes disappears until reboot |
||||||||
Issue descriptionChrome Version: 56.0.2924.28 Chrome OS Version: 9000.29.0 Chrome OS Platform: Elm Steps To Reproduce: (1) Enter tablet mode (2) Show onscreen keyboard (3) Expected Result: Onscreen keyboard always appears. Actual Result: Onscreen keyboard does not show. Shows again after reboot. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Sometimes (after an hour of use?). What is the impact to the user, and is there a workaround? If so, what is it? Must reboot to use onscreen keyboard. Please provide any additional information below. Attach a screen shot or log if possible. https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=50470046103 I'm not sure if it is related, but the logs show error messages like: 2016-12-19 08:33:47.230 I AppGlobals: UI scale: using 125. 2016-12-19 08:33:47.230 I NonClientDecorView: Scaled caption height: 40 scale: 0.8 2016-12-19 08:33:47.230 D ArcHome : Skip configuration change event:{1.0 ?mcc?mnc en_US ldltr sw1020dp w1920dp h1020dp 160dpi xlrg long land finger qwerty/v/v -nav/h s.21}. 2016-12-19 08:33:47.244 I am_on_resume_called: [0,org.chromium.arc.home.HomeActivity] 2016-12-19 08:33:47.248 I AppGlobals: UI scale: using 125. 2016-12-19 08:33:47.248 I NonClientDecorView: Scaled caption height: 40 scale: 0.8 2016-12-19 08:33:47.457 I notification_enqueue: [10068,3671,com.sonelli.juicessh,2001,NULL,0,Notification(pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x10 color=0x00000000 actions=2 vis=PRIVATE),0] 2016-12-19 08:33:51.771 I sysui_histogram: [arc_app_launch_method,0] 2016-12-19 08:33:51.796 I sysui_histogram: [arc_app_launch_method,0] 2016-12-19 08:33:51.845 I sysui_histogram: [arc_app_launch_method,0] 2016-12-19 08:33:51.876 I sysui_histogram: [arc_app_launch_method,0] 2016-12-19 08:33:51.901 I sysui_histogram: [arc_app_launch_method,0] 2016-12-19 08:33:52.000 6 daemon.cc(1325): Saw user activity 2016-12-19 08:33:52.039 I InputDispatcher: Dropping event because there is no touchable window at (767, 875). 2016-12-19 08:33:52.047 I InputDispatcher: Dropping event because there is no touchable window at (766, 875). 2016-12-19 08:33:52.055 I InputDispatcher: Dropping event because there is no touchable window at (765, 875). 2016-12-19 08:33:52.055 I InputDispatcher: Dropping event because there is no touchable window at (766, 876). 2016-12-19 08:33:52.071 I InputDispatcher: Dropping event because there is no touchable window at (765, 875). 2016-12-19 08:33:52.073 I InputDispatcher: Dropping event because there is no touchable window at (766, 877). 2016-12-19 08:33:52.086 I InputDispatcher: Dropping event because there is no touchable window at (766, 878). ... 2016-12-19 08:34:12.384 I InputDispatcher: Dropping event because there is no touchable window at (1800, 1018). 2016-12-19 08:34:12.396 I InputDispatcher: Dropping event because there is no touchable window at (1801, 1018). 2016-12-19 08:34:12.902 I GCoreUlr: Starting service, intent=Intent { act=com.google.android.location.reporting.ACTION_UPDATE_ACTIVE_STATE cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService (has extras) }, extras=Bundle[{source=PowerModeReceiver}] 2016-12-19 08:34:12.908 I GCoreUlr: DispatchingService.updateActiveState+PowerModeReceiver: Ensuring that reporting is active for [account#-8#] 2016-12-19 08:34:12.914 I GCoreUlr: GMS FLP location and AR updates requested: {"description":"stationary","newRequest":true,"samplePeriodMs":2160000,"sampleReason":"stationary","sampleSource":"internal","timestampMs":1482158052905} 2016-12-19 08:34:12.916 I GCoreUlr: Place inference reporting - stop 2016-12-19 08:34:15.000 6 daemon.cc(1325): Saw user activity 2016-12-19 08:34:18.434 I am_task_to_front: [0,63] 2016-12-19 08:34:18.439 I InputDispatcher: Dropping event because there is no touchable window at (1555, 947). 2016-12-19 08:34:18.866 W ContentTaskController: Invalid task was provided to stopTracking. The UI log has errors like: [1307:1307:1218/220320.406628:ERROR:render_widget_host_view_base.cc(358)] Not implemented reached in virtual void content<IPv6: 2>RenderWidgetHostViewBas<IPv6: 3>SetInsets(const gfx<IPv6: 2>Insets&) [1307:1307:1218/220320.406963:ERROR:render_widget_host_view_base.cc(358)] Not implemented reached in virtual void content<IPv6: 2>RenderWidgetHostViewBas<IPv6: 3>SetInsets(const gfx<IPv6: 2>Insets&) [1307:1307:1218/220320.407155:ERROR:render_widget_host_view_base.cc(358)] Not implemented reached in virtual void content<IPv6: 2>RenderWidgetHostViewBas<IPv6: 3>SetInsets(const gfx<IPv6: 2>Insets&) ... And hundreds of these, roughly around the same time as the above errors: [1307:1552:1219/083312.669348:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083312.670082:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083312.672956:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083312.676229:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083312.676369:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083312.677042:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.052779:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.054612:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.054710:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.054801:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.055308:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.055491:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.055896:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.056310:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.066653:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.066865:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.067660:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.067890:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.068025:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.072818:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.074055:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.074803:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.075050:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.075782:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.076390:ERROR:values.cc(183)] NOTREACHED() hit. [1307:1552:1219/083509.076456:ERROR:values.cc(183)] NOTREACHED() hit.
,
Jan 1 2017
A
,
Jan 3 2017
To be sure it is not a hardware sensor issue: Looking at system_logs.txt in the feedback report, I noticed that ARC++ has use the accelerometer sensor at around 8;34: 08:34:12 de-activated package=aiyb handle=0x00000001 08:34:12 de-activated package=ajat handle=0x00000001 08:34:09 activated package=ajat handle=0x00000001 samplingRate=20000us maxReportLatency=0us 08:34:04 de-activated package=ajat handle=0x00000001 Was the keyboard still working after 8:34? Did the keyboard fail to show up after a resume? I fixed an issue in the EC related to the Accelerometers: they may fail to be available when resuming. (CL https://chromium-review.googlesource.com/394750) The change is in elm-8438.54.0 firmware. I notice elm does have its sensor working in S3: from what I can see, we will wake up on keyboard keypress in S3, even when the device is in tablet mode.
,
Jan 24 2017
,
Jan 24 2017
this is affecting all virtual keyboards and not only onscreen.
,
Jan 24 2017
> this is affecting all virtual keyboards and not only onscreen. by "onscreen", omri meant that "accessibility keyboards" :)
,
Jan 24 2017
,
Feb 20 2017
Another feedback report related to this. https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=53448864972 This also has a lot of of implemented reached in virtual void content<IPv6: 2>RenderWidgetHostViewBas<IPv6: 3>SetInsets(const gfx<IPv6: 2>Insets&)
,
Feb 22 2017
,
Feb 27 2017
I should do sheriff duty for several days. yhanada@, feel free to grab this if you want.
,
Mar 28 2017
Ping. Any progress on this issue?
,
Mar 28 2017
I don't find the root cause yet. I'm adding more logs on canary to make it easy to detect where things went wrong when the issue happens.
,
May 4 2017
Are there reliable steps for reproducing?
,
Jun 1 2017
,
Aug 4 2017
I believe this has been fixed with 719905. Please reopen if it still reproduces. Thanks.
,
Jan 22 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by djkurtz@chromium.org
, Dec 30 2016The NOTREACHED is: ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 180) FundamentalValue::FundamentalValue(double in_value) ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 181) : Value(TYPE_DOUBLE), double_value_(in_value) { ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 182) if (!std::isfinite(double_value_)) { ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 183) NOTREACHED() << "Non-finite (i.e. NaN or positive/negative infinity) " ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 184) << "values cannot be represented in JSON"; ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 185) double_value_ = 0.0; ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 186) } ^789ee89 (mostynb 2015-09-09 03:27:23 -0700 187) }