• 6
name

A PHP Error was encountered

Severity: Notice

Message: Undefined index: userid

Filename: views/question.php

Line Number: 191

Backtrace:

File: /home/prodcxja/public_html/questions/application/views/question.php
Line: 191
Function: _error_handler

File: /home/prodcxja/public_html/questions/application/controllers/Questions.php
Line: 433
Function: view

File: /home/prodcxja/public_html/questions/index.php
Line: 315
Function: require_once

The emulator used to accept numerical input from my number-pad with num lock on, now, however, it acts as if num lock is off. For example, if I type "7" on my number-pad, it responds as if "Home" has been pressed.

The numerical keys along the top are still fine, and it makes no difference if I toggle num lock.

Emulator version output:

Android emulator version 29.0.9.0 (build_id 5537588) (CL:N/A)
Copyright (C) 2006-2017 The Android Open Source Project and many others.
This program is a derivative of the QEMU CPU emulator (www.qemu.org).

  This software is licensed under the terms of the GNU General Public
  License version 2, as published by the Free Software Foundation, and
  may be copied, distributed, and modified under those terms.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

I'm running Ubuntu 18.04

Does anyone know what I've changed or is this a bug?

This appears to be a bug in the Android Emulator.

See: https://issuetracker.google.com/issues/135141621

  • 1
Reply Report
    • And now this has been fixed and I can acknowledge that the latest updated to Emulator today fixes it. Please mark this as answer.
    • It looks like this has introduced a new bug, as my keyboard entry now seems to be entering special characters.
    • Yes but I was able to turn it off somehow but now the keyboard entered in upper case. Anyway, you can just mark this as answer as it is the correct answer, it's a bug in Emulator.