Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > PocketBook > PocketBook Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 05-09-2025, 12:56 PM   #76
wold
Zealot
wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.
 
Posts: 134
Karma: 87012
Join Date: Apr 2021
Device: Lux 5, Libra 2, PRS-T2N
Quote:
Originally Posted by Mr Groch View Post
Here is debug log after connecting PocketBook Era Color:

Code:
18:26:49 Debug: "AVATeR v0.18.0 Build: 33d5fee (x86_64, Qt v6.8.3) OS: 'Windows 11 Version 24H2' (x86_64) Qt: v6.8.3, style: fusion "
(...)
18:26:49 Debug: Device scan completed
18:27:17 Debug: Monitor received arrival of device interface: "\\\\?\\USB#VID_1D6B&PID_0104#20080411#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
18:27:17 Debug: Ignoring unsupported USB device with VID/PID/REV (hex): 1d6b 104 0
18:28:09 Debug: Opening debug log viewer...
18:28:32 Debug: Opening debug log viewer...
Thanks for manual fiolder mode - it works for all my annotations on device!

Thanks! This helped fixing it.

Attached is a fixed Windows 0.18.1 Qt6 executable. It goes into the /bin/ directory of the AVATeR install dir. An official release will follow soon.

Its git hash is #ecf9ab4, with 2 minor changes (accepting VID 0x1d6b in hex... and decimal). The Windows machine wasn’t yet updated with the Linux fixes, so the binaries are comparable.
Attached Files
File Type: zip avater-0.18.1-ecf9ab4.exe.zip (449.5 KB, 6 views)
wold is offline   Reply With Quote
Old 05-09-2025, 02:24 PM   #77
Mr Groch
Member
Mr Groch began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Jun 2019
Device: Kindle PW 4, PB Era Color
Unfortunately it is not working

Here is new debug log:

Code:
20:21:06 Debug: "AVATeR v0.18.1 Build: ecf9ab4 (x86_64, Qt v6.8.3) OS: 'Windows 11 Version 24H2' (x86_64) Qt: v6.8.3, style: fusion "
20:21:06 Debug: - Device monitor active? true
20:21:06 Debug: - Portablemode?  true
20:21:06 Debug: - App dir:  "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64"
20:21:06 Debug: - Datadir via CLI? false
20:21:06 Debug: - Datadir path:  "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\data"
20:21:06 Debug: - Settings devices:  "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\data\\devices.conf"
20:21:06 Debug: - Settings general via CLI? false
20:21:06 Debug: - Settings general:  "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\avater.conf"
20:21:06 Debug: - Help path:  "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\manual\\manual_en.html"
20:21:06 Debug: - Temp dir path: "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\tmp"
20:21:06 Debug: - Debug: console? / logmode / globals logmode: false 2 2
20:21:06 Debug: - Logfile: "C:\\Users\\groch\\AppData\\Local\\Temp\\avater_debug.log"
20:21:06 Debug: ---
20:21:06 Debug: Setting up core
20:21:06 Debug: Setting up main window
20:21:06 Debug: Building MW menus
20:21:06 Debug: Restoring MW settings from: "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\avater.conf"
20:21:06 Debug: Setting image cache size to (KB): 100000
20:21:06 Debug: Restoring MW settings finished
20:21:06 Debug: Constructing search widget
20:21:06 Debug: Trying to restore viewer settings from "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\avater.conf"
20:21:06 Debug: Finished restoring viewer settings
20:21:06 Debug: No cbox items yet. Not showing annotations
20:21:06 Debug: Setup connections
20:21:06 Debug: Starting update routine (may be user-disabled)
20:21:06 Debug: Starting automatic check
20:21:06 Debug: No updatecheck necessary. Elapsed time: 93377
20:21:06 Debug: Starting device monitor. Minimal waiting threshold set to 6
20:21:06 Debug: Performing startup scan
20:21:06 Debug: Starting scan_devices
20:21:06 Debug: Getting local mirrors from: "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\data\\devices.conf"
20:21:06 Debug: Ignoring local mirror with serial/mirrortype/vendor:  "1746721893" -1 65534
20:21:06 Debug: Getting USB interfaces
20:21:06 Debug: Ignoring unsupported USB device with vendorID (hex): 13d3
20:21:06 Debug: Ignoring unsupported USB device with vendorID (hex): 4f2
20:21:06 Warning: No first child found. Ignoring device.
20:21:06 Debug: Processing storage events...
20:21:06 Debug: Updated readers count: 0
20:21:06 Debug: Done
20:21:06 Debug: Device scan completed
20:21:09 Debug: ---------scan---------
20:21:09 Debug: Closed viewer menus
20:21:09 Debug: Closed MW menus
20:21:09 Debug: Starting scan_devices
20:21:09 Debug: Getting local mirrors from: "C:/Users/groch/SynologyDrive/Roboczy/eBook Readers/Pocketbook/avater_windows_amd64\\data\\devices.conf"
20:21:09 Debug: Ignoring local mirror with serial/mirrortype/vendor:  "1746721893" -1 65534
20:21:09 Debug: Getting USB interfaces
20:21:09 Debug: Ignoring unsupported USB device with vendorID (hex): 13d3
20:21:09 Debug: Ignoring unsupported USB device with vendorID (hex): 4f2
20:21:09 Warning: No first child found. Ignoring device.
20:21:09 Debug: Processing storage events...
20:21:09 Debug: Updated readers count: 0
20:21:09 Debug: Device scan completed
20:21:12 Debug: Opening debug log viewer...
Maybe this is my fault - this time I run AVATeR after connecting my PocketBook Era Color - so it is fully initialized as mass storage device, earlier it could detect it before chosing PC mode on device after connecting USB cable...
Mr Groch is offline   Reply With Quote
Advert
Old 05-09-2025, 04:33 PM   #78
wold
Zealot
wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.
 
Posts: 134
Karma: 87012
Join Date: Apr 2021
Device: Lux 5, Libra 2, PRS-T2N
Code:
20:21:06 Warning: No first child found. Ignoring device.
This part doesn't sound good... one guess is these newer android devices operate their USB system differently. Though it could be a different device with the same VID (Linux Foundation), which is used by more devices

Any chance this is running in a VM like VirtualBox? There some things just behave differently, requiring adding delays in different places.
wold is offline   Reply With Quote
Old 05-09-2025, 04:59 PM   #79
Mr Groch
Member
Mr Groch began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Jun 2019
Device: Kindle PW 4, PB Era Color
No - just bare Windows 11 PC (laptop).

PocketBook Era Color is not an Android reader. Classic PocketBook Linux device.
PocketBook Improved Driver for Calibre is detecting it fine - maybe there you can find a solution:
https://www.mobileread.com/forums/sh...d.php?t=345618
Mr Groch is offline   Reply With Quote
Old Yesterday, 07:12 AM   #80
wold
Zealot
wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.
 
Posts: 134
Karma: 87012
Join Date: Apr 2021
Device: Lux 5, Libra 2, PRS-T2N
Quote:
Originally Posted by Mr Groch View Post
No - just bare Windows 11 PC (laptop).
That's good to know. This warning made me think of that first. Early development was done in a VM on Linux.


Quote:
PocketBook Era Color is not an Android reader. Classic PocketBook Linux device.
PocketBook Improved Driver for Calibre is detecting it fine - maybe there you can find a solution:
https://www.mobileread.com/forums/sh...d.php?t=345618
Earlier they shared the Inkpad Color 3 VID, matching your log. That was added to AVATeR way back, but not to a 2nd white/acceptlist. Fixing that ought to have solved this. I'll read up there ASAP.

Quote:
Maybe this is my fault - this time I run AVATeR after connecting my PocketBook Era Color - so it is fully initialized as mass storage device, earlier it could detect it before chosing PC mode on device after connecting USB cable...
Ensure the reader runs in PC mode, and the drives are mounted/visible to Windows. Then start AVATeR or do a rescan.

If the drives aren't mounted, AVATeR can't see/reach them. It might detect the reader if connected without PC mode, as you noted, and as clued by this debug line:

Quote:
18:27:17 Debug: Monitor received arrival of device interface: "\\\\?\\USB#VID_1D6B&PID_0104#20080411#{a5dcbf 10-6530-11d2-901f-00c04fb951ed}"
Note the #20080411# part usually shows the serial. This is however not a classical PB serial (something like YTFA0300014~), and suggests this being the USB 'stub device' that temporarily shows up when connecting a PB reader like the Lux5. For the Lux5 this stub uses the Google VID - and hides itself. Perhaps they changed that, and the device is now always visible. Without PC mode, it would hide its drives, explaining the "no child" error.

I'll need to walk through the USB code, and add more debug output. Like logging the error code, and when a compatible device was found, with its credentials Perhaps that can tell us more.

Quote:
20:21:06 Debug: Ignoring local mirror with serial/mirrortype/vendor: "1746721893" -1 65534
This needs fixing too, a 'random' serial (read: epoch date) used by the new localpath (device from path) feature, has stored data in devices.conf.
wold is offline   Reply With Quote
Advert
Old Yesterday, 12:08 PM   #81
Mr Groch
Member
Mr Groch began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Jun 2019
Device: Kindle PW 4, PB Era Color
Second debug log I've attached is in PC mode for sure, and I ran 2 rescans
Mr Groch is offline   Reply With Quote
Reply

Tags
annotations, pocketbook


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Viewer annotations in Calibre Katja_hbg Viewer 8 04-01-2024 09:55 PM
Annotations in Calibre Ebook Viewer jstash Calibre 1 05-22-2020 02:24 AM
Testing pocketbook apps sigizmund PocketBook Developer's Corner 4 03-10-2020 09:11 AM
Viewer with Annotations and Highlights Cjammi ePub 0 03-07-2017 04:07 AM
How do I get an avater? GA Russell Feedback 6 12-21-2010 09:50 PM


All times are GMT -4. The time now is 01:49 AM.


MobileRead.com is a privately owned, operated and funded community.