ToDo beta & SwiftKey keyboard on Android

I just ruled out this being a problem with Samsung's recent update (8.0) of OneUI. I installed ToDo on a Samsung S10e running Android 12 and OneUI 4.1. The same problem exists, I was unable to scroll to the bottom of the text of a long note when in edit mode. The last 17-18 lines are overlaid by the keyboard and can not be accessed.

I tried creating an example anyone (who reads this) could try. I pasted your response to my initial post into a ToDo task note. I learned that the problem isn't that long text won't scroll at all, you just can't scroll all the way to the bottom. I could scroll down until the last line of text was at the bottom of the screen, rather than at the top of the keyboard. So whatever text is under the keyboard can't be accessed or edited. (I tried editing it blind using the arrow keys, but I don't think it was successful.)

I padded the bottom of this long note with twenty blank lines, which enabled me to scroll down to the last line of actual text. However I hope I don't have to put twenty blank lines at the bottom of every ToDo note that is longer than the 2/3 of a page so I allow "scrolling room" for the keyboard.

I understand your workaround suggestions, but since this is a new defective change in behavior (ToDo notes used to scroll fine, regardless of length), I assumed it would be acknowledged as a defect, unless no one else is experiencing it and it is unique to my setup. Is entering long notes in ToDo uncommon so that is the reason there are not more reports of this? I find the floating keyboard both disorienting and burdensome to keep moving around to accommodate where the text I'm editing is located on the screen.

• None of the three keyboards (Gboard, Samsung, or SwiftKey) allow scrolling in ToDo, so I assume what I am experiencing is a defect in a recent release of ToDo (or OneUI or Android).
  • Should I assume you have not experienced this in your version of ToDo with any keyboard? If you do not experience the non-scrolling behavior, can you tell me what Android UI you are using? Samsung released a major OneUI update in October(?) that might be the problem.
• I do not have "Report a Problem" under Help & Feedback in my version of ToDo beta.
• What product do you recommend for screen recording?

Hi, CC WILSON

Thanks for getting back.

I appreciate the further information you gave me. Here are some viable options you can try at the moment in case you still need to use Microsoft ToDo:

First, report this issue to the product team. Since the in‑app “Report a problem” option isn’t present in your beta build, Play Store developer feedback is the most direct path. A short screen recording is enough, no deep explanation needed. On Samsung devices, you can use the built-in recorder (Quick Settings > Screen Recorder).

Second, keep using the padding trick you discovered, leaving some empty space at the bottom of long notes so the text you care about stays above the keyboard.

Third, for very long notes, edit them on the To Do web app first, then only make small edits on the phone.

These are the realistic options that you can try at the moment. Keep staying for further updates, and if you need more support, don't hesitate to get back.

Have a nice day.

Hi, CC WILSON

Thanks for reaching out to Microsoft Q&A forum.

Sorry for this frustrating experience that you're encountering. On Android, apps must correctly handle window insets when the IME appears. If the editor view doesn’t adjust its bottom padding or the nested scroll container doesn’t consume the insets, the visible region ends above the keyboard, so scrolling “halts” even though content exists below. Different keyboards (SwiftKey vs Samsung vs Gboard) present slightly different insets and toolbars, which is why changing the IME often changes the outcome.

Here are some workarounds you can try to resolve this issue:

Option 1: In SwiftKey, slide down on the keys to minimize the keyboard. In Samsung Keyboard, tap the down‑arrow on the toolbar or use the gesture, then scroll to your target line and tap the text to re‑open the keyboard. If you use SwiftKey’s gestures, “slide down on the keys to minimize” is supported.

Option 2: SwiftKey > Toolbar > Modes > Float, then drag the keyboard higher so it no longer overlaps the last lines of the note. (You can also reduce keyboard height.)

Option 3: Install Gboard or use Samsung Keyboard if you’re on SwiftKey, or vice‑versa. Several Android apps exhibit keyboard‑specific display quirks; swapping the IME often changes how insets are applied and restores full scroll.

Option 4: In Samsung Keyboard settings, lower Keyboard size (and hide the toolbar if available). Less vertical height means more lines remain visible above the IME.

Option 5: Open To Do, then enter Android split‑screen with a lightweight app above (e.g., Clock). Making To Do the top pane changes how the system applies insets; you can often scroll the editor to the bottom while the keyboard is open.

Option 6: If the note is very long (>40 lines), open to‑do.microsoft.com in a mobile browser and edit there, then continue on the Android app once the text is in place. (This sidesteps the mobile IME overlay entirely.)

Settings to check (they impact scrolling)

SwiftKey > Typing > (Full‑screen typing / Resize / Modes)

• Try turning off any “full‑screen” editor behavior, use Float, and reduce height.

Samsung Keyboard > Keyboard size & transparency

• Lower the height and disable extra toolbars while editing long notes.

Display > Navigation / “Hide keyboard on swipe down”

• Ensure the “hide keyboard” gesture is enabled so you can quickly scroll.

Clean‑state test (helps pinpoint if it’s app or keyboard)

• In To Do (beta), create a new task and paste a 50‑line dummy note.
• With SwiftKey, confirm the scroll‑stop (about ~18 lines).
• Switch to Gboard/Samsung Keyboard, repeat.

If one keyboard scrolls to the end while the other doesn’t, it’s an IME‑specific layout issue (common across Microsoft mobile apps, as seen in other keyboard interactions).

If you want to report it (strong signal for a fix)

Collect To Do diagnostics right after reproducing the problem and attach a short screen recording:

• To Do > Settings > Help & Feedback > Report a problem (upload the video).
• For Outlook Mobile, Microsoft documents similar log collection flows; To Do uses a comparable path in the mobile clients family.

Tips for the recording

• Show note length (50+ lines), demonstrate the scroll stopping at ~18 lines with keyboard open, then hide the keyboard and scroll further, and finally show that Float mode or another keyboard allows reaching the bottom.

Hope this helps. Feel free to get back if you need further assistance.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.