Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No mouse or keyboard ability #34

Open
jake5253 opened this issue Nov 1, 2020 · 1 comment
Open

No mouse or keyboard ability #34

jake5253 opened this issue Nov 1, 2020 · 1 comment

Comments

@jake5253
Copy link

jake5253 commented Nov 1, 2020

  • [No] I am running an official build of SHRP, downloaded from https://shrp.team/devices
  • [As of Oct.30 source] I am running the latest version of SHRP
  • [Various informations from twrp] I have searched for my issue and it does not already exist

Device codename: Allwinner T8
SHRP version: Not sure. Can't get that far. (source from Oct. 30)
**SHRP Official status: ** Unofficial. I compiled from source and built my own device tree

WHAT STEPS WILL REPRODUCE THE PROBLEM?

I built from source with a device tree I made, using the unit's pre-compiled kernel. Admittedly I'm not sure what I'm doing. I've never compiled a recovery before.
The device is a car stereo, generic chinese one-company-makes-a-bunch-and-they-get-rebranded situation. Depending on what specific ROM I go by, by majority, it's called Allwinner T8 "Octopus". The ro.board is sometimes called exdroid, octopus, t8_p2, auto. It's hard to give you anything specific based on build/default.prop because theres so many rebrands of the same device.

Anyways, I have a bootable SHRP image, it comes up to a screen that mentions unmodified system. I have no touch control, which is expected. I was only able to access the OEM recovery one time ever and that didn't even have touch support, but a usb mouse worked. I figured mouse/keyboard support was fairly standard so it didnt even cross my mind when I started figuring out how to compile a device tree and building SHRP myself. I'm freakin pumped that my first successful compile actually boots!? But sad that I can only get as far as that first screen. I'm not looking for touch support. As I mentioned, OEM recovery didn't even have touch-ability, I just want usb mouse/keyoard... Is there something I've missed? Is this an easy fix? Any help would be ultra appreciated. I'd be glad to upload my device tree and/or the compiled recovery image, if it would be helpful. Please let me know. I don't want to make it a public repo because those seem to disappear rather quickly.

Also, as an added bonus, so far I'm entirely unable to get ADB to see the device either in a running state or in recovery. The makers purposely crippled that functionality. The only USB-to-PC connection I've had any success with is Allwinner's version of download mode, which is how I installed my SHRP build. That being said, I unfortunately cannot attach any dmesg or logs.

@epicX67
Copy link
Member

epicX67 commented Mar 11, 2021

  • [No] I am running an official build of SHRP, downloaded from https://shrp.team/devices
  • [As of Oct.30 source] I am running the latest version of SHRP
  • [Various informations from twrp] I have searched for my issue and it does not already exist

Device codename: Allwinner T8
SHRP version: Not sure. Can't get that far. (source from Oct. 30)
**SHRP Official status: ** Unofficial. I compiled from source and built my own device tree

WHAT STEPS WILL REPRODUCE THE PROBLEM?

I built from source with a device tree I made, using the unit's pre-compiled kernel. Admittedly I'm not sure what I'm doing. I've never compiled a recovery before.
The device is a car stereo, generic chinese one-company-makes-a-bunch-and-they-get-rebranded situation. Depending on what specific ROM I go by, by majority, it's called Allwinner T8 "Octopus". The ro.board is sometimes called exdroid, octopus, t8_p2, auto. It's hard to give you anything specific based on build/default.prop because theres so many rebrands of the same device.

Anyways, I have a bootable SHRP image, it comes up to a screen that mentions unmodified system. I have no touch control, which is expected. I was only able to access the OEM recovery one time ever and that didn't even have touch support, but a usb mouse worked. I figured mouse/keyboard support was fairly standard so it didnt even cross my mind when I started figuring out how to compile a device tree and building SHRP myself. I'm freakin pumped that my first successful compile actually boots!? But sad that I can only get as far as that first screen. I'm not looking for touch support. As I mentioned, OEM recovery didn't even have touch-ability, I just want usb mouse/keyoard... Is there something I've missed? Is this an easy fix? Any help would be ultra appreciated. I'd be glad to upload my device tree and/or the compiled recovery image, if it would be helpful. Please let me know. I don't want to make it a public repo because those seem to disappear rather quickly.

Also, as an added bonus, so far I'm entirely unable to get ADB to see the device either in a running state or in recovery. The makers purposely crippled that functionality. The only USB-to-PC connection I've had any success with is Allwinner's version of download mode, which is how I installed my SHRP build. That being said, I unfortunately cannot attach any dmesg or logs.

Mouse problem was fixed in v3. I am not sure about keyboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants