Skip to main content

Oracle dealt patent defeat in Google Android case

oracle-headquarters
Image used with permission by copyright holder

The U.S. Patent and Trademark Office dealt Oracle a bit of a setback in its high-stakes patent litigation against Google over Android. In a filing just before the Christmas holiday, the USPTO effectively threw out one of the seven patents Oracle is using against Google (full text available at Groklaw), rejecting some 17 of the 21 claims asserted in U.S. patent 6,192,476. Although only one of those claims was being leveraged against Google—claim 14—the rejection of so many claims basically means the entire patent has been invalidated.

Recommended Videos

Google requested the patent be re-examined by the USPTO, along with others Oracle is asserting against it in the case. The request for re-examination is common in patent litigation: defendants typically assert both that the aren’t infringing on a particular patent, and furthermore that the patent ought not to have been issued in the first place, and therefore is invalid and nobody could infringe on it even if they tried.

Oracle’s infringement case against Google hinges on the Java virtual machine included in Google’s Android operating system; Oracle claims the technology violates a number of Java patents it acquired along with Sun Microsystems in early 2010. Oracle initially asserted 132 infringement claims against seven patents; the list of claims was reduced to a list of 50 on the request of the judge handling the case; of those, only one (claim 14) was against patent 6,192,476. However, that means Oracle still has six patents in play in its case against Google. The judge has requested Oracle further limit the number of claims it brings to trail; Oracle had been hoping to bring 21 claims, but the judge had suggested Oracle focus on just three claims to streamline proceedings.

Generally speaking, Oracle would prefer to go to trail sooner than later. The case was originally supposed to go to trail in October, but a scheduling conflict lead to a delay. Oracle then asked for a January start date, but Google has dragged its feet, saying it can’t be ready for trail before July.

Oracle has until February 20 to request an appeal the preliminary ruling. Preliminary rulings against patents have been later been overturned upon full review, so Oracle may have a chance of hanging on to the patent after all. If Oracle does nothing, it will likely be stripped of the patent.

Geoff Duncan
Former Digital Trends Contributor
Geoff Duncan writes, programs, edits, plays music, and delights in making software misbehave. He's probably the only member…
Android 16 brings a blind fingerprint unlock perk to Pixel phones
Enabling off screen fingerprint unlock feature in Android 16.

Google is currently moving full steam ahead with the development of Android 16. Following the release of a third beta update just over a week ago, Android 16 has reached the platform stability milestone. Though the latest test build is light on feature updates, it brings a cool new trick.
On Pixel smartphones, users can now unlock their phone even if the screen is completely dark. First spotted by the folks over at Android Authority, the new “Screen-off Fingerprint Unlock” feature has been integrated within the phone’s Security & Privacy dashboard.
So far, Pixel smartphone users had to wake up the screen and put their thumb atop the fingerprint sensor icon on the Lock Screen. This had to be done either by waking up the screen with a tap gesture, or by pressing the power button.
Thanks to the new screen-off unlock convenience, users can simply place their thumb atop the in-display fingerprint sensor and get past the Lock Screen. There is no longer an intermittent hassle of lighting up the screen.

 
I was able to enable this feature after installing the Android 16 Beta 3.1 build, which runs atop the March 2025 security update, on a Pixel 8 smartphone. The new feature is a thoughtful convenience and works flawlessly.
It does, however, take a bit of muscle memory to land the thumb right above the fingerprint sensor on an otherwise dark screen. Also worth noting here is the fact that Google won’t be the first smartphone maker to offer this convenience.
I tried unlocking my OnePlus 13 and Samsung Galaxy S25 without waking up the screen, and it works just fine. Both devices are currently running Android 15, and notably, offer a faster fingerprint unlock experience compared to the Pixel 8, irrespective of whether the screen is on or off.
I’d like to point out that the screen-off fingerprint unlock system has arrived with a beta build, and Google might remove — or delay it — when the stable Android 16 update starts rolling out widely in the coming months. 
For now, your only option to experience it is by enrolling in the Android 16 beta-testing program on a compatible Google Pixel smartphone. I would, however, recommend waiting out a few more weeks for the stable update to land on your Pixel smartphone, and save yourself the buggy mess of test builds. 

Read more
Google is working on a cleaner backup interface for Android users
google is working on a cleaner backup interface for android users pixel home screenf

Google is redesigning the backup page on Android to give it a cleaner and more organized appearance. This update is part of the Google Play Services version 25.11.32 beta, as reported by Android Authority.

The Android backup page can be found in the Settings app under System > Backup. It allows users to manage and control the data backed up from their phones or tablets to their Google Accounts. You can initiate backups for various data types, including apps and app data, contacts, SMS, and MMS messages.

Read more
Getting a Google Play services error? You’re not the only one
Rose Quartz Pixel 9 Pro on a peppermint background.

If you've received an alert from Google Play Services to install an update but you can't find, don't worry: you aren't alone. The error message warns that certain official Google apps won't work unless you update through the Play Store, but no update is available. The problem seems to be affecting a wide number of people, many of whom took to social media to find an answer to the problem.

Tipster CID (@theonecid) reports this same error, and it has been confirmed from several other outlets. The source of the bug isn't clear, but it seems to affect users on both the stable and beta releases of Play Services.

Read more