Android 4.4.3 continues to show up in various mediums, indicating that the new version of the KitKat operating system should release at some point.

Most recently, Android 4.4.3 has been discovered within an AOSP change log and within an informational video for the Motorola Moto E mid-range smartphone that was announced on Tuesday.

A change log by the name “KK-MR2_changelist.txt” was discovered last week not only contains evidence of Android 4.4.3 but also all of the system modifications for the Android 4.4 firmware. Within the change log, which contains 5293 lines of text, is one line that says “7503e73 4.4.3 is MR2, version boogaloo!” This is among the few direct references of Android 4.3.3. The original change log has since been deleted; however, it has been preserved on Github.

The Moto E announced Tuesday officially runs Android 4.4.2 KitKat; however, Android Central noted that a promo video for the new device mentions Android 4.4.3 in the fine print. Though actual mentions of Android 4.4.3 are still scarce, there are others, such as the Edu Device Setup, listing software support for its app as Android 4.4.3 on the Play Store. Other sightings include the surfacing several build numbers, which are not associated with current Android operating systems.

Rumors about Android 4.4.3 first surfaced when tech website Myce discovered the build number KTU65, which it quickly connected to Android 4.4.3. Later, Italian tech website TuttoAndroid discovered the build number KUT72B and LlabTooFeR, indicated that the build was being tested by Google. Android Police also got its hands on a prospective change log for Android 4.4.3 in addition to a capture of Android 4.4.3 running on a Nexus 5.

Users have been awaiting the Android 4.4.3 update since the current Android 4.4.2 version has a number of bugs, which have plagued devices since December. Nexus users appear to report the most issues with the firmware. Android 4.4.3 will reportedly address more than three dozen bugs brought on by Android 4.4.2.

Many hope to see a resolution to issues with the Nexus 5 camera: the lens’ inability to focus and a bluish tint in the presence of white light. Other glitches users hope to see resolved include Bluetooth and data connection problems as well as various battery draining issues.

One issue having to do with battery drain caused by the Nexus 5 camera is localized within the mm-qcamera-daemon system code, which allows third-party apps (like Snapchat or Skype) access to a device’s camera. The mm-qcamera-daemon process continues to run even when those apps are closed and contributes to battery drain.

So far, Google has not indicated any plans to roll out an Android 4.4.3 update.

Follow me on Twitter.