[
    {
        "role": "user",
        "content": "I%20am%20using%20the%20easy%20reader%20qapp%20from%20dolphin%20but%20when%20reading%20using%20my%20dot%20pad%20X%20it%20doesn%27t%20scroll%20from%20page%20to%20page%20using%20the%20multiline%20part%20I%20have%20to%20pan%20forward%20instead%20of%20press%20function%204%20to%20move%20multiline%20at%20a%20time%20is%20it%20my%20app%3F%20or%20can%20you%20help%20me%20I%20tried%20calling%20dolpin%20but%20they%20just%20said%20checkout%20yourdolpin.com%20and%20there%20is%20nothing%20there%20for%20me"
    },
    {
        "role": "assistant",
        "content": "Hi \u2014 I\u2019ve done some digging and here are a few things to check and try. Some may help fix the issue with moving multiline braille by page using F4 on your Dot Pad X with EasyReader.\n\n---\n\n## What I found: How Dot Pad X and EasyReader handle navigation\n\n### Dot Pad X controls\nAccording to the Dot Pad X user guide:\n\n- There are **panning buttons** (left and right) that move the braille display back/forward by 20 characters *or* move to the previous/next page in multiline braille text. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n- Function keys **F1 and F4** are defined to move the multiline braille/tactile graphics area to the **next item or text** (or previous, depending on context). ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n\nSo, F4 *should* be able to move you forward in multiline content (potentially from one \"page\" of multiline braille/tactile text to the next, depending on how it's set up).  \n\n---\n\n### EasyReader\u2019s keyboard commands on Windows\nFrom EasyReader\u2019s official documentation:\n\n- To scroll one page down: **PAGE DOWN** key. If you are at the end of the document, it may try to open the next document. ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))  \n- To go to next page (only if the book includes page numbers): **CTRL + PAGE DOWN** ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))  \n\nNote: There's no mention in the documentation of F4 being a command for moving by page in EasyReader. ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))  \n\n---\n\n## Why F4 might not be doing what you expect\n\nPutting the two together, here are likely reasons F4 isn't taking you forward by page in multiline text:\n\n1. **Conflicting expectations**: The Dot Pad\u2019s F4 is meant to navigate between \u201citems or text,\u201d not necessarily pages. If the text doesn't have clear item separations (such as headings), F4 may skip only to the next heading or next chunk, not the next page.\n\n2. **Book format limitations**: EasyReader will only allow \"go to next page\" if the text (or the DAISY or PDF file) includes real page numbers or is formatted to support page navigation. If the book doesn\u2019t have page numbers, CTRL + PAGE DOWN won\u2019t work. ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))\n\n3. **Settings may affect behavior**: Multiline braille settings or how the Dot Pad is configured (whether it's using multiline text mode vs. tactile graphics mode) can influence what navigation commands do. If it's not in a mode where multiline text is showing or page numbers are active, commands tied to \u201cpage\u201d may not function.\n\n---\n\n## What you can do: steps to try\n\nHere are some actions to get F4 or some other control working more like what you're expecting:\n\n1. **Check EasyReader settings**  \n   - Open EasyReader on your Windows computer.  \n   - Go to *Text Settings* or *Navigation Settings*. Look for options like \u201cNavigation mode\u201d \u2014 ensure it includes \u201cpages\u201d (rather than just time intervals or headings). ([yourdolphin.com](https://yourdolphin.com/product-help/easyreader-app/375.htm?lid=1&utm_source=openai))  \n   - Also verify whether page numbers are present in the book metadata.\n\n2. **Try alternate hotkeys in EasyReader**  \n   - Press **PAGE DOWN** to scroll one page down. ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))  \n   - Press **CTRL + PAGE DOWN** to go to the next page (if page numbers are available). ([yourdolphin.com](https://yourdolphin.com/support/article?id=96&lid=2&utm_source=openai))  \n\n3. **Test F4 in a known formatted book**  \n   - Use a book or DAISY file you know has real page numbers and see whether F4 moves you to the next page or just next text/heading. This can help see whether the issue is with the book or with the device/app.\n\n4. **Check Dot Pad\u2019s connection and mode**  \n   - Make sure Dot Pad X is in a mode that supports multiline text. If it\u2019s in tactile graphics mode or some alternate mode, navigation commands might behave differently. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n   - Ensure firmware is up to date and it\u2019s properly connected to the computer/app (USB or Bluetooth, depending).\n\n5. **Contact support with specific details**  \n   - If after trying the above you still can\u2019t get it to work, gather details: the name/format of the book (DAISY, PDF, etc.), whether page numbers are present, what specific behavior happens when you press F4, and whether other navigation commands like PAGE DOWN work.  \n   - Share those with Dolphin or Dot support. Sometimes there\u2019s a mismatch between how the device and the app interpret \u201cpage\u201d boundaries.\n\n---\n\nIf you like, I can try locating instructions specific to your Dot Pad X + EasyReader combination (maybe from other users who have done this), to see if there\u2019s a workaround or setting I didn't find yet. Do you want me to pull those up for your specific setup?"
    },
    {
        "role": "user",
        "content": "no%20f4%20is%20on%20the%20dot%20pad%20I%20am%20reading%20on%20an%20iphone%20not%20a%20pc%2C%20I%20just%20said%20F4%20because%20the%20button%20is%20function%204"
    },
    {
        "role": "assistant",
        "content": "Thanks for clarifying \u2014 since you\u2019re using the Dot Pad X with an iPhone + EasyReader (with VoiceOver), the behavior of F4 (Function-4 on the Dot Pad) depends a lot on what VoiceOver supports, and how EasyReader shows the braille text. I went through the manuals and documentation, and here\u2019s what I found plus some suggestions and work-arounds you might try.\n\n---\n\n## What I found about Dot Pad X and iOS\n\nFrom the Dot Pad X Quick Start Guide:\n\n- There are **panning buttons**, triangular, to move the braille display back/forward by 20 characters, *or* move to the previous/next **page of multiline Braille text**. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n- The **Function buttons F1 through F4** are used to move the multiline braille and tactile graphics area to the \u201cnext item or text.\u201d For example, F4 should move the content forward to the next item. But changing \u201citem or text\u201d is not always the same as advancing a page. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n- On iOS, VoiceOver is recognized by Dot Pad X; the unit supports multiline Braille and tactile graphics display when connected via Bluetooth or USB. ([blog.dotincorp.com](https://blog.dotincorp.com/the-multi-line-braille-experience-that-keeps-on-giving-review-of-the-dot-pad-x?utm_source=openai))  \n\nSo F4 *can* do what you expect (move forward by a block of content, possibly a page), but not always \u2014 it might depend on how EasyReader interacts with VoiceOver and the content format.\n\n---\n\n## What I found about EasyReader on iOS\n\nLooking through Dolphin\u2019s support for EasyReader:\n\n- EasyReader works with VoiceOver and supports braille displays. That means when you're reading text with a connected Dot Pad X, the content should show up in multiline if the book and format support it. ([apps.apple.com](https://apps.apple.com/us/app/dolphin-easyreader/id1161662515?utm_source=openai))  \n- EasyReader has \u201cBook navigation\u201d controls on the iPhone screen. You can tap to open a list of headings, page numbers, and bookmarks to move quickly. Also, there is a \u201cNavigation mode\u201d you can set, which controls how far the Next / Previous buttons skip (e.g. by sentence, by paragraph, maybe by page depending on settings). ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai))  \n- But I didn\u2019t find anything in the EasyReader iOS documentation that says \u201cFunction-4 on a connected braille display will always move you exactly one multiline page forward.\u201d In other words: there\u2019s no guarantee F4 acts like \u201cNext page\u201d in all books.  \n\n---\n\n## What likely is going on\n\nPutting it all together, likely reasons why F4 doesn\u2019t move you forward by a full multiline page (instead of just some chunk or you needing to pan):\n\n1. **Content format doesn\u2019t define \u201cpages\u201d**: Some books (especially ePubs, DAISY or other reflowable formats) don\u2019t have fixed pages in the way PDFs or fixed layout files do. Without page numbers or fixed page breaks, F4 may move to \u201cnext item\u201d (heading, section) rather than next page.\n\n2. **EasyReader current navigation mode**: The \u201cNext/Previous\u201d buttons in EasyReader (on screen) skip by something like sentences by default. If the Navigation Mode is set to \u201cSentence,\u201d \u201cParagraph,\u201d etc., rather than \u201cPage,\u201d then voice and braille navigation may follow that. F4 (Function 4) may be getting mapped to \u201cnext item,\u201d not \u201cpage.\u201d \n\n3. **VoiceOver limitations or mapping**: VoiceOver has its own set of commands when handling braille display navigation. The F-buttons on the Dot Pad X are mapped to certain VoiceOver commands, but those commands may not be one\u2010to\u2010one with page navigation in apps (depends on the app). Also, the panning buttons definitely are for moving forward/backward in \u201cchunks,\u201d but those chunks might be lines or blocks, not full pages. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n\n---\n\n## What you can try (suggestions/work-around)\n\nHere are some things you can test/change to see if you can get the behavior you want:\n\n| Try this | How to do it / What to check |\n|---|-----------------------------|\n| **Check Navigation Mode in EasyReader** | In the EasyReader app on your iPhone, look near the bottom of the screen for the \u201cNavigation Mode\u201d button. Tap that and see if you can change the skip size: maybe set it to \u201cPage\u201d or anything like it, instead of \u201cSentence\u201d or \u201cParagraph.\u201d If a \u201cPage\u201d option exists, that will help F4 or Next button behave more like jumping by full multiline content. ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai)) |\n| **Open Book Navigation \u2192 Pages** | Using the Book Navigation screen at the bottom left: if you open that, you should see tabs for Headings, Pages, and Bookmarks. Try selecting \u201cPages\u201d and choose where you want to jump to. This bypasses line or item navigation and goes by page number if pages are present. ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai)) |\n| **Use the panning buttons (triangles)** | If the panning navigation buttons on the Dot Pad X (left/right triangle buttons) are working, those should move forward \u201c20 braille characters or to the next page of multiline Braille text\u201d when in multiline mode. That sometimes does exactly what you want: full page advance rather than item skip. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai)) |\n| **Make sure the book has page numbers / fixed layout** | Try opening a book you know has fixed pages (e.g. PDF, DAISY with page numbering) and see if F4 then moves forward by page. If it does, then the behavior you saw for other books is just because those books are reflowable and lack fixed pages. |\n| **Contact support with details** | If nothing seems to solve it, it could be a bug or limitation. It might help to report to Dolphin or Dot: mention the book format, the skip settings you have in EasyReader, whether you are using VoiceOver, whether other navigation buttons or methods work.  \n\n---\n\nIf you want, I can try to pull up a specific step-by-step for your iPhone & Dot Pad X combo (model, iOS version etc.) to see if there\u2019s a hidden setting you can toggle. Would you like me to do that?"
    },
    {
        "role": "user",
        "content": "%20no%20it%20works%20well%20on%20Kindle%20app%20but%20not%20on%20easy%20reader%20or%20voice%20dream%20reader%20people%20siad%20it%20works%20for%20them%20but%20not%20for%20me"
    },
    {
        "role": "assistant",
        "content": "Thanks for sticking with this \u2014 I found more specific info that seems relevant. It sounds like the problem might be a mismatch between how your apps (EasyReader or Voice Dream Reader) are set to navigate vs. what your Dot Pad X + VoiceOver is doing. Here\u2019s what I discovered + some concrete steps you can try to fix it.\n\n---\n\n## What I found on Voice Dream Reader\n\n- Voice Dream has a **Navigation Unit** setting (in the player controls) that determines how much \u201cjump\u201d happens when you use next/previous or similar skip commands: it could be by **sentence, paragraph, page, chapter**, etc. ([voicedream.com](https://www.voicedream.com/support/reader-help/?utm_source=openai))  \n- Some users report that **page-based navigation** won\u2019t work in certain books \u2014 usually when the text doesn\u2019t have strong page markers (e.g. in DAISY or reflowable EPUBs) or if the book file was arranged without fixed page structure. ([daisy.org](https://daisy.org/guidance/info-help/guidance-training/reading-systems/voice-dream-reader-overview/?utm_source=openai))  \n- In Voice Dream, to use a Braille display effectively, once connected via VoiceOver, there are commands using Braille keys (like space with dots 1-4-5-6 or 3-4-5-6) to scroll up/down a page. These commands operate independently of a \u201cpage\u201d concept in the document\u2014effectively simulating a full display page scroll. But they rely on VoiceOver reading mode and correct Braille display compatibility. ([voicedream.com](https://www.voicedream.com/faq-items/how-do-i-read-using-a-braille-display/?utm_source=openai))\n\nSo, **Voice Dream Reader** supports page jumps via the Braille commands, but it\u2019s dependent on your settings and the format of the text.\n\n---\n\n## What I found on EasyReader\n\n- EasyReader on iOS has a **Navigation Mode** button, where you can control how much the \u201cPrevious\u201d and \u201cNext\u201d buttons skip. That might include \u201cpage,\u201d though not always with every file. ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai))  \n- The app also provides **Book Navigation**, which lets you choose among page numbers, headings, and bookmarks. If the book has fixed page numbers, this lets you jump by page. ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai))  \n\n---\n\n## What I found about Dot Pad X\n\n- The Dot Pad X supports multiline Braille (and tactile graphics), and its \u201cpanning buttons\u201d (the triangular buttons) are meant to move back or forward by the previous/next 20 characters *or* to the previous/next page of multiline Braille text \u2014 when the display is in multiline mode. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n- The Function buttons F1 and F4 are labeled to \u201cmove the multi-line Braille and tactile graphics area to the next item or text.\u201d The \u201citem or text\u201d part is important: if the content doesn\u2019t define items clearly, the jump may not behave like page jumps. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n\n---\n\n## Why it \u201cworks for some people but not you\u201d\n\nPutting all this together, it seems likely your setup is **correctly supported**, but some settings or content format are preventing it from giving you the \u201cfull page\u201d behavior. Possible issues:\n\n- Your Navigation Unit (in Voice Dream) might be set to \u201csentence\u201d or \u201cparagraph,\u201d not \u201cpage.\u201d  \n- EasyReader might have Navigation Mode set to skip by smaller units rather than page.  \n- The specific book you are reading might **not have fixed page numbers or breaks**, which means \u201cpage-based navigation\u201d won\u2019t work properly.  \n- VoiceOver + Dot Pad X may not recognize the content\u2019s \u201cpage\u201d boundaries because of how it\u2019s structured.  \n- The Braille reading mode may not be multiline (or may be defaulting to line-by-line) in some apps or with certain settings.  \n\n---\n\n## What *you can try* to fix it\n\nHere are steps tailored to your situation (iPhone + Dot Pad X + EasyReader / Voice Dream Reader) to try to get that full-page skipping:\n\n1. **Check Navigation Unit in Voice Dream Reader**  \n   - Open Voice Dream with your book.  \n   - Look just right of the play button \u2014 there should be something showing \u201cNavigation Unit: ___\u201d.  \n   - If it\u2019s set to \u201csentence\u201d or \u201cparagraph,\u201d change it to \u201cpage.\u201d ([applevis.com](https://applevis.com/forum/ios-ipados/turning-pages-using-bookshare-voice-dream-reader?utm_source=openai))  \n\n2. **Ensure the book has page numbers or fixed layout**  \n   - If possible, open a PDF or book known to have real pages (for example, a designed layout PDF, or a DAISY book with page numbers).  \n   - Try the page scroll command (space + dots 1-4-5-6 to go down a page) or equivalent. See if that works. If it does, then the issue is just that your usual books lack page markers.  \n\n3. **Set EasyReader\u2019s Navigation Mode**  \n   - In EasyReader, find the Navigation Mode (bottom part of screen) and see if you can set \u201cPage\u201d instead of smaller units. ([yourdolphin.com](https://yourdolphin.com/support/article?id=32&lid=1&utm_source=openai))  \n   - Use Book Navigation \u2192 Pages, and pick a page number to jump directly to it.  \n\n4. **Use the panning buttons on your Dot Pad X**  \n   - Those triangular buttons should move forward/back either by ~20 characters *or* to the \u201cnext multiline page\u201d if multiline is active. If you haven\u2019t tested this, try using the right panning arrow and see if that jumps full pages when you pan through multiline braille blocks.  \n\n5. **Check VoiceOver Braille and Reading Mode settings**  \n   - On your iPhone: Settings \u2192 Accessibility \u2192 VoiceOver \u2192 Braille \u2192 make sure Dot Pad X is selected.  \n   - Check the Braille Reading Mode / Rotor settings: some modes affect how text is segmented (by item, by text, etc.). If VoiceOver is in a mode that isn\u2019t multiline mode, some of the Dot Pad\u2019s buttons may act differently. ([manuals.plus](https://manuals.plus/dot/pad-x-portable-and-versatile-tactile-display-manual?utm_source=openai))  \n\n6. **Try a different book/app**  \n   - Try reading in Kindle app: you said it works there. Compare with Voice Dream / EasyReader. See what setting they use in Kindle that\u2019s giving you page jumps. Maybe replicate it.  \n\n7. **Update firmware or software**  \n   - Make sure your Dot Pad X firmware is up to date (connect to Dot Canvas, check for updates).  \n   - Make sure your iPhone is on the latest iOS that supports multiline braille well.  \n\n---\n\nIf you want, I can walk you through the exact steps on Voice Dream Reader / EasyReader for your iPhone model + iOS version so you can check each of those settings. Would you like me to do that?"
    }
]