Forum Discussion
Impact of Google Scribe Changes on Samsung S-Pen Usability in Industrial Contexts
Hello,
We have observed a significant change in S-Pen behavior following the integration of Google Scribe into Android 15 / 16 on our Galaxy Tab Active 5. Previously, the stylus allowed cursor movement (or select an write area) within text fields without triggering handwriting input. This was essential for our use case.
Our technicians are working in proximity to high-voltage electricity and must wear protective gloves. The stylus is their only means of interacting with the tablet during operations. With the recent change, the stylus now immediately writes in text areas instead of moving the cursor, making it impossible to position the cursor without touching the screen with a finger (which is not feasible in our environment).
Before with old firmware (Android 14): https://youtube.com/shorts/RXaPRRXaNcs?feature=share
After with latest version of Android with Google Scribe (Android 15/16) : https://youtu.be/ZfKKCKcfxUc / https://youtube.com/shorts/EbuibT211lg
This modification introduces a critical usability issue for industrial and safety-related workflows. Is there any documented workaround or configuration option to restore the previous behaviour (cursor movement without writing / select area)?
If not, could this scenario be considered for future updates of Android?
Thank you for your attention to this matter.
Best regards,
10 Replies
Do you have any commercial support with Samsung? Unfortunately they'd be best placed to receive this sort of product feedback. Lizzie may be able to direct feedback to the Scribe folks within Google though, if there's a path for it
Hello Jason,
Thank you for your reply. Yes, we do have commercial support with Samsung, and we’ve already raised this issue with their Enterprise Technical Support team. They confirmed that the behavior change is due to modifications in AOSP related to Google Scribe integration (specifically onUpdateEditorToolType and Flag.useHandwritingListenerForToolType).
Samsung clarify that this behavior was due to the addition of the following API:
As part of this transition, Samsung removed its previous SpentoText framework, which previously allowed unique functionalities such as cursor movement and toolbar activation without triggering handwriting input. This removal, combined with the new AOSP behavior, means that the stylus now immediately writes in text fields instead of allowing cursor positioning.
Just thinking out loud here, would it help to block Scribe on the device (you need an MDM for that)?
You can use Samsung knox as your portal to Samsung directly, do you have a Knox portal? If not, create one. Its free and you don't have to upload the devices to Knox if you don't want to in order for you to log tickets.
Depending on where you bought them, your reseller can reach out to Samsung for you. But they need to be a Samsung partner.
If everything fails I can try and get in contact with Samsung in your country, i'm seeing French text I think? Are you from france?
Hello Michel,
Thank you for your suggestions. Yes, we are based in France, and we already have a Knox portal and an active commercial support contract with Samsung. We’ve opened a ticket with their ETS team, and they confirmed that the issue is linked to the removal of their SpentoText framework and the integration of Google Scribe in AOSP.
We’ll continue working with Samsung, but if Lizzie can escalate this feedback to the Google Scribe team, that would be extremely valuable. This is a safety-critical use case for our technicians, where the stylus is the only interaction method due to protective gloves. They can't move cursor, or with this change, double-tapping in the text selection area immediately writes, inserting unwanted characters.
Good to hear you are already using ETS! Its very helpfull in most cases. But I wasn't aware Samsung removed their own framework.
Hope you get this sorted. Can you keep us informed about the solution when you have it? (wether it's via lizzie or another route).
Hi Aurelien12345, we've passed your query on to our internal team for guidance. Just a heads-up that it may take a few days to hear back. Thanks for sharing those videos, btw, they are very helpful.
Thanks jasonbayton and Michel for your input as well, much appreciated.Hello,
Do you have any updates on this incident, please?
Best regards,
Hello SebGR and Aurelien12345
Unfortunately, we haven't heard back from the team yet - this likely means they're in the midst of trying to replicate the issue to find a fix.
We'll keep you posted as soon as we hear back from them 🙂
Hello,
Has Android 17 beta arrived, and is there the same issue with the S Pen?
Best regards,
