Forum Discussion

bpraj8's avatar
bpraj8
Copper Contributor
Jul 17, 2026

TEAMS - Extra Space between Keyboard and Typing Window

Dear All,

I am also facing the issue in TEAMS. During the typing, a large space appears between Keyboard and Typing Window. This is happening only in TEAMS app. I moved from my Nothing phone to Vivo X200Fe, then this problem started. This may be a bug in TEAMS to be fixed for VIVO phones. I use VIVO X200 FE with Android 16 and Google Keyboard. It's very annoying to see this big gap and making us 

uncomfortable while typing. Please help me how to resolve this. Thanks for your help.

Mobile : Vivo X200FE

Operating System : Origin OS Android 16

Teams Version : 1416 / 1.0.0.2026123608

Keyboard : Google Keyboard - Version 17.7.4.93236420

 

 

microsoft teams

2 Replies

  • yosua34's avatar
    yosua34
    Copper Contributor
    Jul 21, 2026

    This is also happen on me with Vivo iQOO Z9 5G

    Running OriginOS 6

    This happens to everyone using many models of Vivo phones in my office, for non Vivo phone, this problem didnt occur.

     

    already clear data for Teams, Teams version are up to date, installed from Play Store, and start happening around a week ago.

  • Jamony's avatar
    Jamony
    MCT
    Jul 19, 2026

    You’re seeing a blank band between Gboard and the Teams composer on a Vivo X200 FE running OriginOS/Android 16, while the keyboard appears normally elsewhere. That Teams-only scope makes client troubleshooting the safest first path; it does not prove whether Teams, OriginOS, or Gboard is responsible. In Teams, open profile picture > Settings > About, record the version, then install any update from Google Play. Next, open Settings > Data and storage > Clear app data > Clear data, sign in again, and test. If spacing remains, uninstall and reinstall Teams from Google Play, then retest before changing keyboard settings. Finally, open Settings > Help and feedback > Send feedback, attach logs if offered, and include a screenshot, phone model, OS build, Teams version, and reproduction steps. I could not find a Microsoft-published fix for this exact combination, so submitting those diagnostics is the appropriate next step.