If you have a Boox Max Lumi 1, I could really use your help and I'd marry you.

snuggy · 03-24-2024, 04:20 AM

Hello,

In this thread here I go through the insanity of updating my Boox Max Lumi 1 and finding that the touch screen no longer worked.

Boox Support believes this is just coincidental behaviour of the touch screen failing directly after an update. I just... I can't accept that. It's technically preowned, sure, but has literally never been unused.

I messaged Renate privately about this, as he's got a lot of experience with Boox devices, and you can check out me soliciting support from people on Reddit, and it turns out that one of the /dev/event things has disappeared.

I'm just wondering if someone with a Boox Max Lumi 1 can run the commands that Renate has suggested in this DM.

Essentially, it's just:

http://www.temblast.com/download/inscan

http://www.temblast.com/download/2cscan

Code:

adb push

them to /data/local/tmp, chmod them and run them.

Code:

C:\>adb push inscan /data/local/tmp
C:\>adb shell
$ cd /data/local/tmp
$ chmod 755 inscan
$ ./inscan

Look, honestly -- I'd be extremely grateful.

Thank you,
Fraser

snuggy · 03-24-2024, 09:30 AM

Quote:

never been unused

sorry, I mean used; this situation is clearly making me crazy x

Renate · 03-24-2024, 01:20 PM

The files are inscan and i2cscan

Did I mention lsmod?
I'm not sure that this uses kernel modules or how many.

Code:

$ lsmod

But if one were for touch and it went missing or became incompatible....

snuggy · 03-25-2024, 03:24 AM

Quote:

Originally Posted by Renate

The files are inscan and i2cscan

Did I mention lsmod?
I'm not sure that this uses kernel modules or how many.

Code:

$ lsmod

But if one were for touch and it went missing or became incompatible....

Ah, gotcha! Yeah, I have all the lsmod (just wifi) but /dev/input differs in one input method, input8.

I'm trying to follow up with the guy I found who has one, I'll keep you posted x

snuggy · 03-27-2024, 12:04 AM

Quote:

Originally Posted by Renate

The files are inscan and i2cscan

Did I mention lsmod?
I'm not sure that this uses kernel modules or how many.

Code:

$ lsmod

But if one were for touch and it went missing or became incompatible....

Here's the readout from the bloke on reddit

Code:

MaxLumi:/data/local/tmp $ ./inscan                                    
# Key Abs Rel Sw  Name  
-- --- --- --- --- --------------------------------  
0  X              qpnp\_pon  
1  X   X          onyx\_emp\_Wacom I2C Digitizer  
2  X   X          pt\_mt  
3  X       X      hbtp\_vm  
4  X              sf-keys  
5  X              onyx-hall  
6  X              gpio-keys  
7              X  sdm660-snd-card-skush Headset Jack  
8  X              sdm660-snd-card-skush Button Jack

Code:

MaxLumi:/data/local/tmp $ ./i2cscan
/dev/i2c-2  /soc/i2c@c176000 - failed
/dev/i2c-4  /soc/i2c@c178000 - failed
/dev/i2c-6  /soc/i2c@c1b6000 - failed
/dev/i2c-8  /soc/i2c@c1b8000 - failed

Cheers mate!

bigwigs · 03-27-2024, 09:33 AM

check out this post - https://help.boox.com/hc/en-us/commu...-screen-Frozen

See if it helps with recovery of ur Lumi

Renate · 03-28-2024, 05:01 AM

Yes, you need to be rooted for i2cscan to work. Sorry.

I can't find your listing for inscan. How does it differ from the reddit post?

leader_montanus · 03-30-2024, 06:22 AM

Hi, here is the output from i2scan and inscan, both now run as root:

MaxLumi:/data/local/tmp # ./i2cscan

Code:

/dev/i2c-2  /soc/i2c@c176000
  60  W0R0        

/dev/i2c-4  /soc/i2c@c178000
  1f                qcom,camera  i2c_camera
  24  W0R0  In use  pt_tp  pt_i2c_adapter
  34  W0R0  In use  aw881xx_smartpa  aw881xx_smartpa
  35  W0R0  In use  aw881xx_smartpa  aw881xx_smartpa
  3f        In use

/dev/i2c-6  /soc/i2c@c1b6000
  09  W0R0  In use  wacom  wacom_ts  Wacom digitizer
  38        In use  lm3630a  lm3630a_bl  TI LED controller

/dev/i2c-8  /soc/i2c@c1b8000
  0b  W0R0  In use  tc358762  tc358762  Toshiba display interface bridge
  48  W0R0  In use  max17135  max17135  Maxim Eink power management

MaxLumi:/data/local/tmp # ./inscan

Code:

 # Key Abs Rel Sw  Name
-- --- --- --- --- --------------------------------
 0  X              qpnp_pon
 1  X   X          onyx_emp_Wacom I2C Digitizer
 2  X   X          pt_mt
 3  X       X      hbtp_vm
 4  X              sf-keys
 5  X              onyx-hall
 6  X              gpio-keys
 7              X  sdm660-snd-card-skush Headset Jack
 8  X              sdm660-snd-card-skush Button Jack

snuggy · 03-30-2024, 10:31 AM

Hey, here's mine from the one that doesn't work

Code:

MaxLumi:/data/local/tmp # ./i2cscan
/dev/i2c-2  /soc/i2c@c176000
  60  W0R0

/dev/i2c-4  /soc/i2c@c178000
  1f                qcom,camera  i2c_camera
  24                pt_tp
  34  W0R0  In use  aw881xx_smartpa  aw881xx_smartpa
  35  W0R0  In use  aw881xx_smartpa  aw881xx_smartpa
  3f        In use

/dev/i2c-6  /soc/i2c@c1b6000
  09  W0R0  In use  wacom  wacom_ts  Wacom digitizer
  38        In use  lm3630a  lm3630a_bl  TI LED controller

/dev/i2c-8  /soc/i2c@c1b8000
  0b  W0R0  In use  tc358762  tc358762  Toshiba display interface bridge
  48  W0R0  In use  max17135  max17135  Maxim Eink power management
MaxLumi:/data/local/tmp #

Compared with leader_montanus, pt_i2c_adapter for hex 24 is missing.

Code:

MaxLumi:/data/local/tmp # ./inscan
 # Key Abs Rel Sw  Name
-- --- --- --- --- --------------------------------
 0  X              qpnp_pon
 1  X   X          onyx_emp_Wacom I2C Digitizer
 2  X       X      hbtp_vm
 3  X              sf-keys
 4  X              onyx-hall
 5  X              gpio-keys
 6              X  sdm660-snd-card-skush Headset Jack
 7  X              sdm660-snd-card-skush Button Jack

Again, the problem is with what should be Key 2, pt_mt, appears to be missing in inscan.

Phew! What do you reckon Renate?

snuggy · 03-30-2024, 10:42 AM

Also, to put everything in one place: I asked for someone with a working Boox Lumi, this is leader_montanus listing his input devices on reddit

Code:

MaxLumi:/ $ ls -l /dev/input
total 0
crw-rw-rw- 1 root input 13,  64 1972-08-26 23:51 event0
crw-rw-rw- 1 root input 13,  65 1972-08-26 23:51 event1
crw-rw-rw- 1 root input 13,  66 1972-08-26 23:51 event2
crw-rw-rw- 1 root input 13,  67 1972-08-26 23:51 event3
crw-rw-rw- 1 root input 13,  68 1972-08-26 23:51 event4
crw-rw-rw- 1 root input 13,  69 1972-08-26 23:51 event5
crw-rw-rw- 1 root input 13,  70 1972-08-26 23:51 event6
crw-rw-rw- 1 root input 13,  71 1972-08-26 23:52 event7
crw-rw-rw- 1 root input 13,  72 1972-08-26 23:52 event8
crw-rw-rw- 1 root input 13,  63 1972-08-26 23:51 mice
crw-rw-rw- 1 root input 13,  32 1972-08-26 23:51 mouse0
crw-rw-rw- 1 root input 13,  33 1972-08-26 23:51 mouse1

Mine is missing event8 when compared with his.

Renate · 03-30-2024, 07:06 PM

We can see that the 4-0024 has a problem.
It's not claimed by a driver.
Is it that the driver is missing? Or did the hardware fail and the driver bailed out?
Check dmesg for anything to do with pt_tp.
If there was a problem it would say so.
If it never tried to load it there would be nothing.

Does this actually have Wacom (with a stylus)? Does that work?

Those input numbers are only useful to see if something is missing.
That's because they are given out dynamically.

leader_montanus · 03-30-2024, 07:33 PM

On my (working) Max Lumi I get the following from dmesg when I filter on "pt_i2c_adapter" (missing from snuggy's output)

Code:

[157935.942028] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_ON, start pt_core_resume_!
[157935.942030] ONYX_TP: pt_i2c_adapter: pt_core_resume_:start
[157935.942057] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power on success
[157935.942067] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[157936.242796] pt_i2c_adapter 4-0024: [2] _pt_poll_for_fw_exit_boot_mode: FW exited BOOT mode in 100ms, sys_mode=1
[157936.242812] pt_i2c_adapter 4-0024: [2] _fast_startup: Exit FW BOOT Mode after 100ms
[159181.503659] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_OFF, start pt_core_suspend_!
[159181.503662] ONYX_TP: pt_i2c_adapter: pt_core_suspend_:start
[159181.503690] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power off success
[159388.683536] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_ON, start pt_core_resume_!
[159388.683538] ONYX_TP: pt_i2c_adapter: pt_core_resume_:start
[159388.683555] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power on success
[159388.683561] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[159388.895112] pt_i2c_adapter 4-0024: [2] _pt_poll_for_fw_exit_boot_mode: FW exited BOOT mode in 60ms, sys_mode=1
[159388.895118] pt_i2c_adapter 4-0024: [2] _fast_startup: Exit FW BOOT Mode after 60ms
[159390.002110] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_OFF, start pt_core_suspend_!
[159390.002111] ONYX_TP: pt_i2c_adapter: pt_core_suspend_:start
[159390.002133] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power off success
[159709.070362] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_ON, start pt_core_resume_!
[159709.070364] ONYX_TP: pt_i2c_adapter: pt_core_resume_:start
[159709.070391] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power on success
[159709.070402] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[159709.273610] pt_i2c_adapter 4-0024: [2] _pt_poll_for_fw_exit_boot_mode: FW exited BOOT mode in 60ms, sys_mode=1
[159709.273626] pt_i2c_adapter 4-0024: [2] _fast_startup: Exit FW BOOT Mode after 60ms
[159926.013919] ONYX_TP: pt_i2c_adapter: fb_notifier_callback:FB_OFF, start pt_core_suspend_!
[159926.013921] ONYX_TP: pt_i2c_adapter: pt_core_suspend_:start
[159926.013945] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power off success

Filtering on "pt_tp" suggested by Renate:

Code:

[157965.702723] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout qcom_rx_wakelock a800000.ssusb 800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2 onyx_charging_lock pt_tp_wake 
[157995.782787] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout qcom_rx_wakelock epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158025.862941] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158055.942701] ONYX: Pending Wakeup Sources: KeyEvents PowerManager.SuspendLockout qcom_rx_wakelock a800000.ssusb onyx_charging_lock pt_tp_wake 
[158086.022752] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout a800000.ssusb onyx_charging_lock pt_tp_wake 
[158116.102727] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout qcom_rx_wakelock a800000.ssusb onyx_charging_lock pt_tp_wake 
[158146.182849] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158176.262919] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158206.342925] ONYX: Pending Wakeup Sources: KeyEvents PowerManager.SuspendLockout qcom_rx_wakelock epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158236.422717] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158266.502732] ONYX: Pending Wakeup Sources: PowerManagerService.WakeLocks PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158296.582817] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158326.662689] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158356.742871] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158386.822764] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158416.902738] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158446.982877] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158477.062902] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158507.142957] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158537.222763] ONYX: Pending Wakeup Sources: KeyEvents PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158567.302766] ONYX: Pending Wakeup Sources: event2 KeyEvents PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158597.382879] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158627.462866] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158657.542864] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158687.622819] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158717.702755] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158747.782911] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update a800000.ssusb onyx_charging_lock pt_tp_wake 
[158777.862733] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[158988.423716] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159018.504023] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159048.584009] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159078.664012] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159738.800473] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout qcom_rx_wakelock a800000.ssusb 800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2 onyx_charging_lock pt_tp_wake 
[159768.880803] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159798.959852] ONYX: Pending Wakeup Sources: qcom_rx_wakelock a800000.ssusb onyx_charging_lock pt_tp_wake 
[159829.039621] ONYX: Pending Wakeup Sources: qcom_rx_wakelock epdc_update epdc_power a800000.ssusb onyx_charging_lock pt_tp_wake 
[159859.120554] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159889.200631] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[159919.280810] ONYX: Pending Wakeup Sources: a800000.ssusb onyx_charging_lock pt_tp_wake 
[160280.240684] ONYX: Pending Wakeup Sources: PowerManager.SuspendLockout a800000.ssusb onyx_charging_lock pt_tp_wake

Good luck.

snuggy · 03-30-2024, 11:56 PM

Quote:

Originally Posted by Renate

Does this actually have Wacom (with a stylus)? Does that work?
.

It does, and that's working without issue.

Quote:

Originally Posted by Renate

We can see that the 4-0024 has a problem.
It's not claimed by a driver.
Is it that the driver is missing? Or did the hardware fail and the driver bailed out?
Check dmesg for anything to do with pt_tp.
If there was a problem it would say so.
If it never tried to load it there would be nothing.

Similarly filtering by "pt_i2c_adapter"

Code:

MaxLumi:/ # dmesg | grep -iC 3 "pt_i2c_adapter"
[    0.916217] create_and_get_core_pdata: No data for setting 'parade,test_regs'
[    0.916219] create_and_get_core_pdata: No data for setting 'parade,btn_keys'
[    0.916223] create_and_get_core_pdata: irq_gpio:0 rst_gpio:0\x0ahid_desc_reg:1 level_irq_udelay:0 vendor_id:0 prod_id:0\x0aflags:38 easy_wakeup_gesture:0
[    0.916615] ONYX_TP: pt_i2c_adapter: onyx_tp_dt_parse:vdd: yes, vdd_ctrl: gpio:62, vcc: yes, vcc_ctrl: gpio61, vcc-voltage:3000000,reset: gpio66, irq: gpio67
[    0.916625] ONYX_TP: pt_i2c_adapter: pt_devtree_create_and_get_pdata:irq_gpio:67 rst_gpio:66, hid_desc_register:1 level_irq_udelay:0, vendor_id:0 product_id:0, flags:38 easy_wakeup_gesture:0
[    0.916635] create_and_get_u16_array: parade,abs size:50
[    0.916638] pt_devtree_create_and_get_pdata: 1 child node(s) found
[    0.916674] ONYX_TP: pt_i2c_adapter: onyx_tp_hw_init:start
[    0.916720] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power on success
[    0.916725] ONYX_TP: pt_i2c_adapter: onyx_tp_hw_init:success!
[    0.916738] pt_i2c_adapter 4-0024: [2] pt_probe: PARADE No HW detect function pointer
[    0.916746] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[    0.931827] pt_i2c_adapter 4-0024: [2] pt_hw_hard_reset: executed HARD reset
[    0.931835] pt_i2c_adapter 4-0024: pt_setup_irq: Value Passed to gpio_to_irq =67
[    0.931841] pt_i2c_adapter 4-0024: pt_setup_irq: Value Returned from gpio_to_irq =263
[    1.094956] ONYX_TP: pt_i2c_adapter: _pt_detect_dut_generation:finish, dut_gen: 1
[    1.097864] pt_i2c_adapter 4-0024: [1] pt_hid_output_validate_app_response: APP output response, wrong report_id
[    1.097875] pt_i2c_adapter 4-0024: [1] _pt_request_active_pip_protocol: pip_version Not Detected
[    1.097882] pt_i2c_adapter 4-0024: [1]  === PIP Version Not Detected, Skip Enum ===
[    1.106756] pt_i2c_adapter 4-0024: [1] pt_hid_output_validate_bl_response: BL output response, ERROR:2
[    1.106768] pt_i2c_adapter 4-0024: [1] pt_enum_with_dut_: Error on launch app r=-71
[    1.106776] pt_i2c_adapter 4-0024: [2] pt_enum_with_dut_: DUT Enum Attempt 2
[    1.106792] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[    1.121876] pt_i2c_adapter 4-0024: [2] pt_hw_hard_reset: executed HARD reset
[    1.258986] pt_i2c_adapter 4-0024: [1] pt_hid_output_validate_bl_response: BL output response, ERROR:2
[    1.258995] pt_i2c_adapter 4-0024: [1] pt_enum_with_dut_: Error on launch app r=-71
[    1.259003] pt_i2c_adapter 4-0024: [2] pt_enum_with_dut_: DUT Enum Attempt 3
[    1.259016] pt_i2c_adapter 4-0024: [2] pt_xres: 20ms HARD RESET on gpio=66
[    1.274103] pt_i2c_adapter 4-0024: [2] pt_hw_hard_reset: executed HARD reset
[    1.408322] pt_i2c_adapter 4-0024: [1] pt_hid_output_validate_bl_response: BL output response, ERROR:2
[    1.408332] pt_i2c_adapter 4-0024: [1] pt_enum_with_dut_: Error on launch app r=-71
[    1.408342] pt_i2c_adapter 4-0024: [1] _legacy_generate_hw_version: SYSINFO and BL_INFO are not ready
[    1.408351] pt_i2c_adapter 4-0024: [2] pt_enum_with_dut_: HW Version: FFFF.FFFF.FF
[    1.408362] pt_i2c_adapter 4-0024: [2] pt_enum_with_dut_: Completed Enumeration rc=-19 On Attempt 4
[    1.408374] pt_i2c_adapter 4-0024: [2] pt_probe: cd->startup_status=0x0001 status=0x0101
[    1.408381] pt_i2c_adapter 4-0024: [1] pt_probe: Enumeration Failed r=-19
[    1.408387] pt_probe PARADE error_after_startup
[    1.408478] ONYX_TP: pt_i2c_adapter: onyx_tp_power:power off success
[    1.408630] pt_probe failed.
[    1.408740] pt_loader_init: Parade FW Loader Driver (Version TTDL.04.11.977092) rc=0
[    1.408752] pt_device_access_init: Parade TTSP Device Access Driver (Built TTDL.04.11.977092) rc = 0
MaxLumi:/ #

Filtering dmesg on "pt_tp", nothing is returned.

Code:

MaxLumi:/ # dmesg | grep -iC 3 "pt_tp"
1|MaxLumi:/ #

Any ideas? I know this could be hardware, but it just seems too coincidental that it was working fine on factory firmware and stopped immediately after updating. Just a bit confusing.

Renate · 03-31-2024, 02:12 AM

Quote:

Originally Posted by snuggy

Any ideas?

71 is EPROTO (Protocol error) which indicates the the thing is not talking I2C correctly.
That still could be software/DTB error if they didn't get the power, the speed or the reset pin correct.

PT is "Parade Technologies".
Since the driver gave up, it's not in use.
I'd try to write some code to see if I could read the ID or something.

Renate · 04-02-2024, 03:31 PM

Oh, now I see.
Parade Technologies bought out the Cypress True Touch stuff.
That was the cyttsp5 stuff.
It's possible that you have a mixup between DTB and kernel or kernel mods.
Look for pt_ and cyttsp in the DTB (or just post it).

03-24-2024, 04:20 AM	#1
snuggy Member Posts: 18 Karma: 10 Join Date: Feb 2024 Device: Boox Max Lumi	If you have a Boox Max Lumi 1, I could really use your help and I'd marry you. Hello, In this thread here I go through the insanity of updating my Boox Max Lumi 1 and finding that the touch screen no longer worked. Boox Support believes this is just coincidental behaviour of the touch screen failing directly after an update. I just... I can't accept that. It's technically preowned, sure, but has literally never been unused. I messaged Renate privately about this, as he's got a lot of experience with Boox devices, and you can check out me soliciting support from people on Reddit, and it turns out that one of the /dev/event things has disappeared. I'm just wondering if someone with a Boox Max Lumi 1 can run the commands that Renate has suggested in this DM. Essentially, it's just: http://www.temblast.com/download/inscan http://www.temblast.com/download/2cscan Code: adb push them to /data/local/tmp, chmod them and run them. Code: C:\>adb push inscan /data/local/tmp C:\>adb shell $ cd /data/local/tmp $ chmod 755 inscan $ ./inscan Look, honestly -- I'd be extremely grateful. Thank you, Fraser

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
where to download the v3.2.4 firmware of boox max lumi 2?	sageren	Onyx Boox	4	02-03-2024 11:13 AM
Free Boox Max Lumi 1 (Eu)	Neru	Flea Market	0	10-16-2022 11:11 AM
Boox Max Lumi: Best file format for annotations?	GaryHogg	Onyx Boox	2	05-07-2021 09:28 AM
Buy Onyx Boox Max Lumi	mr_sm1th	Flea Market	0	12-13-2020 11:24 PM
Onyx Boox Max Lumi Stylus Issues	philprofessor	Onyx Boox	3	11-04-2020 06:50 PM

03-24-2024, 01:20 PM	#3
Renate Onyx-maniac Posts: 3,139 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	The files are inscan and i2cscan Did I mention lsmod? I'm not sure that this uses kernel modules or how many. Code: $ lsmod But if one were for touch and it went missing or became incompatible....

03-27-2024, 09:33 AM	#6
bigwigs Enthusiast Posts: 42 Karma: 604 Join Date: Feb 2024 Device: Kindle Paperwhite	check out this post - https://help.boox.com/hc/en-us/commu...-screen-Frozen See if it helps with recovery of ur Lumi

03-28-2024, 05:01 AM	#7
Renate Onyx-maniac Posts: 3,139 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Yes, you need to be rooted for i2cscan to work. Sorry. I can't find your listing for inscan. How does it differ from the reddit post?

03-30-2024, 07:06 PM	#11
Renate Onyx-maniac Posts: 3,139 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	We can see that the 4-0024 has a problem. It's not claimed by a driver. Is it that the driver is missing? Or did the hardware fail and the driver bailed out? Check dmesg for anything to do with pt_tp. If there was a problem it would say so. If it never tried to load it there would be nothing. Does this actually have Wacom (with a stylus)? Does that work? Those input numbers are only useful to see if something is missing. That's because they are given out dynamically.

04-02-2024, 03:31 PM	#15
Renate Onyx-maniac Posts: 3,139 Karma: 12537601 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Oh, now I see. Parade Technologies bought out the Cypress True Touch stuff. That was the cyttsp5 stuff. It's possible that you have a mixup between DTB and kernel or kernel mods. Look for pt_ and cyttsp in the DTB (or just post it).

Advert

Advert