[
    {
        "role": "user",
        "content": "I%20have%20got%20a%20book%20from%20bookshare.ie%20and%20I%20am%20trying%20to%20read%20it%20in%20easy%20reader%20using%20my%20dot%20pad%20X%20on%20the%20dat%20pad%20there%20are%20buttons%20Function%201%20to%20fuction%204%20in%20this%20case%20F1%20to%20F4%20the%20F4%20button%20is%20to%20go%20to%20next%20page%2C%20but%20when%20i%20have%20turned%20on%20Braille%20reading%20mode%20and%20press%20F4%20it%20scrolls%20to%20the%20next%20page%20but%20after%202%20or%20sometimes%203%20pages%20it%20moves%20to%20play%20pause%20next%20and%20stops%20moving%20forward%20I%20know%20using%20the%2020%20cells%20I%20can%20press%20pan%20forward%20but%20I%20do%20want%20to%20use%20the%20F4%20button%20can%20you%20find%20a%20way%20that%20this%20will%20work%20please"
    },
    {
        "role": "assistant",
        "content": "Here are several ideas and settings to try, plus some explanations of how F1\u2013F4 work on the Dot Pad X. These should help you get F4 to reliably advance to the next page in Braille reading mode in EasyReader without unintentionally switching to play/pause/next modes.\n\n---\n\n## What \u201cF4\u201d is really doing on the Dot Pad X\n\nFrom the Dot Pad X manual:\n\n- F1 and F4 are used to **move the multiline braille and tactile-graphics area** to the *previous or next item or text*. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n- The two triangular buttons next to F1/F4 are *panning (previous/next)* \u2014 these shift the 20-cell braille line forward or back within one page of multiline Braille text. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n\nSo pressing F4 is not exactly \u201cturn page\u201d in all contexts \u2014 depending on how EasyReader or VoiceOver/Rotor is handling Braille Text Mode and the current focus, it may switch function (e.g. change reading mode, images vs text, etc.).\n\n---\n\n## Why it stops after 2-3 presses\n\nBased on what you described, this likely happens because you\u2019re triggering different \u201cfocus\u201d states: text, images, headings, or sync points. After moving beyond certain items, F4 starts doing something else (play/pause/next) because EasyReader (or VoiceOver) has reinterpreted what \u201cnext\u201d means in that context\u2014probably moving to the next heading or media element rather than the next page of text.\n\n---\n\n## Things you can try\n\nHere are specific settings and steps to adjust to make F4 work more like \u201cnext page\u201d when in Braille reading mode:\n\n| Step | What to check / set | How to do it |\n|------|----------------------|--------------|\n| **1. Confirm Braille Reading Mode** | Ensure you're in *Braille Text Mode \u2192 Reading Mode*. This is VoiceOver\u2019s mode where the multiline Braille display shows text (or text & images depending on settings). It may also help to use *Reading Mode (No Images)* if images are slowing things down or adding extra focus items. ([selvasblv.com](https://selvasblv.com/wp-content/uploads/2025/11/Dot-Pad-X-Quick-Start-Guide-and-FAQ-2.pdf?utm_source=openai)) |\n| **2. Check EasyReader\u2019s reading settings** | In EasyReader, sometimes the app will set navigation or headings differently depending on the file format (DAISY, EPUB, PDF, BRF). Try using a version that has fewer images or simplify the format. |\n| **3. Use the \u201cnext panning button\u201d** | To move within the current page multiline text, before switching pages, use the triangular *next panning* control. That ensures you\u2019re not accidentally skipping parts of the page before \u201cturning\u201d. On Dot Pad X it's the triangle shape next to F1\u2013F4. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai)) |\n| **4. Check if EasyReader hotkeys are overlapping** | If EasyReader or your system has assigned F4 to \u201cnext heading\u201d or \u201cplay/pause/next media\u201d, then pressing F4 on the hardware might send that command. You can try remapping hotkeys in EasyReader (if possible) so that F4 only controls \u201cnext page\u201d. |\n| **5. Keep software up to date** | Make sure Dot Pad X firmware is current, and that EasyReader is fully updated. Sometimes odd behaviors arise from mismatched versions. |\n| **6. Contact support** | Because this behavior is very likely tied to how EasyReader integrates with VoiceOver and Dot Pad X, you may want to get technical support from:  \n   \u2022 Dolphin (makers of EasyReader)  \n   \u2022 Dot Inc / SELVAS BLV (for Dot Pad X hardware)  \n   Describe exactly: file type (DAISY, EPUB, PDF, etc.), what mode in VoiceOver you are in, and how many pages you can go with F4 before it shifts to the wrong behavior. |\n\n---\n\nIf you like, I can look up step-by-step instructions from EasyReader or VoiceOver (on your specific device: iPad, Windows, etc.) to configure this behaviour precisely. Do you want me to do that?"
    },
    {
        "role": "user",
        "content": "yes%20on%20the%20iphone%20and%20it%20works%20fine%20in%20kindle%20reading%20but%20not%20in%20easy%20reader%20and%20voice%20dream%20reader%20I%20do%20have%20Braille%20reading%20and%20no%20images%20and%20the%20book%20is%20all%20text"
    },
    {
        "role": "assistant",
        "content": "Here are detailed suggestions for iOS settings and steps you can try to get F4 on your Dot Pad X (connected via VoiceOver) to reliably mean \u201cnext page\u201d in **EasyReader** and **VoiceDream Reader**, especially when the book is pure text, Braille Reading Mode, no images.\n\n---\n\n## Key iOS / VoiceOver Settings to Check or Change\n\n1. **Turn off \u201cPages While Panning\u201d**  \n   Some iOS users report that having *\u201cPages While Panning\u201d* enabled in VoiceOver\u2019s Braille settings causes weird behavior\u2014such as jumping to play/pause/next media instead of pages. Turning it off may make F4 or similar commands more consistent. ([mail.applevis.com](https://mail.applevis.com/bugs/ios/turn-pages-while-panning-feature-braille-displays-not-placing-reader-top-next-page-when?utm_source=openai))\n\n2. **Ensure \u201cCursor Position\u201d is set to On Page (not Centered) in VoiceDream**  \n   In VoiceDream Reader, there is a setting under *Visual Settings \u2192 Advanced Visual Settings \u2192 Cursor Position*. If it\u2019s set to \u201cCentered,\u201d it can cause the reading to skip or repeat lines when you go to the next page; switching to \u201cOn Page\u201d helps keep the continuity. ([perkins.org](https://www.perkins.org/resource/ios-devices-and-focus-braille-displays/?utm_source=openai))\n\n3. **Check Braille Display Key Mapping / Function Keys on Dot Pad X**  \n   The Dot Pad X has six function keys which may be customizable. It\u2019s possible that when reading text-only books, the context shifts and F4 stops acting as \u201cnext page.\u201d Checking whether the function keys are mapped correctly in Dot Pad X settings or in the VoiceOver braille settings may help. ([dotincorp.com](https://www.dotincorp.com/en/product/dotpadx?utm_source=openai))\n\n4. **Ensure App\u2019s Navigation Settings are Compatible**  \n   In both EasyReader and VoiceDream, ensure the reading navigation units are set to \u201cpage\u201d instead of line, paragraph, or heading. If the app has a setting for navigation units, page-by-page navigation will be more reliable with F4. (VoiceDream supports navigation units like page, paragraph, etc.) ([voicedream.com](https://www.voicedream.com/support/reader-help/?utm_source=openai))\n\n---\n\n## Steps to Try on Your iPhone\n\nHere is a step-by-step sequence you might follow to set things up and troubleshoot.\n\n| Step | What to Do | Why It Helps |\n|------|------------|---------------|\n| 1 | Go to **Settings \u2192 Accessibility \u2192 VoiceOver \u2192 Braille** on your iPhone. Find **Pages While Panning** and turn it **off**. | Prevents VoiceOver from automatically turning pages when you pan, which seems to interfere with hardware key functions like F4. ([mail.applevis.com](https://mail.applevis.com/bugs/ios/turn-pages-while-panning-feature-braille-displays-not-placing-reader-top-next-page-when?utm_source=openai)) |\n| 2 | Open **VoiceDream Reader** \u2192 go to **Settings \u2192 Visual Settings \u2192 Advanced Visual Settings \u2192 Cursor Position** and change it to **On Page** (if currently set to Centered). | Helps avoid duplicating or skipping lines at page turns. ([perkins.org](https://www.perkins.org/resource/ios-devices-and-focus-braille-displays/?utm_source=openai)) |\n| 3 | In VoiceDream, check **Navigation Units** (this may also be under Settings). Set Navigation Unit to **Page**. | So that when you use F4 (or Space+Dots etc.) it advances entire page units. ([voicedream.com](https://www.voicedream.com/support/reader-help/?utm_source=openai)) |\n| 4 | In Dot Pad X firmware or settings (if you can access them from iPhone or PC/mac), see if you can remap the F4 function to always send the \u201cnext item\u201d or \u201cpage down\u201d command in VoiceOver. | Ensures F4 doesn\u2019t change function depending on context. Dot Pad X supports customizable function keys. ([dotincorp.com](https://www.dotincorp.com/ko/product/dotpadx?utm_source=openai)) |\n| 5 | Restart your iPhone and ensure both VoiceOver and the reading app are active. Test with a simple text-only book (like a Bookshare book with only text) in both EasyReader and VoiceDream, after making those changes. | Helps isolate whether the issue is with particular books or app behavior. |\n\n---\n\n## Why Kindle Works Better and These Others Don\u2019t\n\n- Kindle for iOS probably has more stable or built-in handling of VoiceOver + Braille + page turns, especially for text-only content.\n- EasyReader and VoiceDream may internally switch focus at end of page (e.g., to a trailing element like a footer, bookmark, next chapter marker), and F4 then navigates to that focus instead of turning the page\u2014unless \u201cPages While Panning\u201d is off and navigation units are set properly.\n\n---\n\nIf you want, I can try digging up up\u2010to\u2010date user\u2010guide steps *specifically* for EasyReader + Dot Pad X + iOS 18 or 19 (whichever you have), to see if there are newly available options or patches. Do you want me to check that version\u2010specific info?"
    }
]