Has anyone got any further with the virtualsoftkeys not loading/working after a while with Fully Kiosk Browser auto-loading on boot?
I don’t want to have to go to each device after a power cut etc and start Fully.
There are a load of settings in Fully relating to other apps - is there something in there preventing it working or something that can be added to help it along?
Thanks.
It seems I’m struggling a bit. I can’t get adb to work, although I have enabled developer mode. I don’t think it’s my USB-C cable, as they are the ones that came with my Pixel 3 and Pixel 8, which I used to flash LineageOS onto my phones.
I tried the edl command, but no luck there either. I can get into the bootloader recovery screen, but I’m unable to do much there beyond basic stuff. Still, no luck with running adb from the bootloader screen.
I’m using a Dell XPS with Ubuntu and am extremely familiar with Linux. I have installed countless custom ROMs. So, at the moment, I’m a bit at a loss. It feels like this Lenovo is locked down pretty tightly or I’m just missing something stupid. Or maybe both USB-C cables that came with my Pixel phones are just not compatible with the Lenovo.
So exactly what stage are you at in the installation instructions and what are you seeing?
I followed this slightly expanded guide as the paths were a little tricky to start. Have you done all that?
https://community.home-assistant.io/t/is-this-the-perfect-standalone-tablet-for-ha/658422/153
What does dmesg say when you plug it in? You should see something like this;
[1684392.495848] usb 1-1: new high-speed USB device number 18 using xhci_hcd
[1684392.645339] usb 1-1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 3.18
[1684392.645341] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1684392.645342] usb 1-1: Product: Android
[1684392.645343] usb 1-1: Manufacturer: Android
[1684392.645344] usb 1-1: SerialNumber: HUA0BP9W
Making a symbolic link to the flash folder solves the path problem;
ln -s kingston-ha-rom/flash flash
I’ve had the best luck using full paths with edl, for example;
./edl qfil \
/home/your-user/edl/kingston-ha-rom/bin/rawprogram.xml \
/home/your-user/edl/kingston-ha-rom/bin/patch0.xml \
flash/ \
--loader=/home/your-user/edl/kingston-ha-rom/bin/prog_emmc_firehose_8953_ddr.mbn
Are you holding down both vol + and vol - when you power it up?
Do the volume buttons work?
Yeah, that’s the problem. I get nothing, but if I plug in my Pixel, it works fine, and I see
[30372.155096] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 4.40
[30372.155119] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[30372.155127] usb 3-1: Product: Pixel 3
So right now, either the USB port is bad on the Lenovo or it’s turned off. Maybe the cable, but I’m not so sure it’s the cable since this cable works with my Pixel3 and Pixel7.
I’m at no stage, and that’s the problem; the USB port just doesn’t want to be recognized. It could be the cable, but I am not so sure since the cable works fine with my Google Pixel 3 and Pixel 7.
I saw some other posts (not here) that someone had problems with USB cables with odd results (maybe data corruption?) and a change of cable solved it. Worth trying.
And how about trying USB 2 if you have one - or a USB 2 hub.
Damn, good suggestion! Just plugged it into my old Linux PC from a million years ago, and what do you know!
[ 145.751647] usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 145.909063] usb 1-6: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 3.18
[ 145.909085] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 145.909094] usb 1-6: Product: Android
[ 145.909101] usb 1-6: Manufacturer: Android
[ 145.909106] usb 1-6: SerialNumber: HUA0B7XS
Glad I keep old PCs kicking around. At least it’s a start; now adb shell drops me onto the tablet. Thanks for that suggestion; would never have even thought of trying that!
My XPS is fairly new, being about 6 months old, so perhaps the newer USB chipsets don’t agree with Lenovo’s USB chipset.
Excellent - glad it’s working. These devices are fabulous - I’ve just ordered my fifth device!
Success! I was able to flash it to the OP’s ROM. It’s possible that my problem was related to Google’s USB-C to USB-C cables. I used a different USB-A to USB-C cable with my older Linux machine. So if others encounter similar issues, it could be related to the cable and/or USB chipset.
I’m experiencing this too:
While tech savvy I’m not great with Android debugging. Are there any logs or something that would be worthwhile to grab?
Most plain USB-C to USB-C cables expect devices to follow specifications for this scenario. That means they need to be able to negotiate USB mode and power.
The ThinkSmart View has a very primitive USB-C interface with only VCC, GND, D+ and D- connected. No smarts there, but good enough for USB 2.0 if used in a USB-A port on the host device or an appropriately configured USB-C to USB-C cable.
Any ideas how to change to wpa2? I click on my AP, and when i click edit i cannot scroll down any further to select the security settings. Is there a way to do this via adb or is there some special sauce that im missing with A11?
lol, nm. i have another AP that i was able to connect to. Unsure why the first one didnt connect appropriately.
@dinki question. I cannot seem to find where i turn the lock screen off for A11. I search settings and i dont find anything specifically saying to turn it off. I set the Lock to none. Is that it? Also, when i toggle open/close on the physical camera toggle, it puts the device to sleep and i cant wake it up without closing the camera (which means i dont have a camera). Im gonna try and restart with the camera open and see if that takes care of it.
Yes. I set lock to none. That camera slide acts as a power button. It’s odd.
You should be able to set Fully Kiosk or Wallpanel to ‘keep display on’ or ‘keep alive’ to keep the display from sleeping.
Ok rebooting with the camera slot open seems to work.
Just an update on the AP issue. The only difference between my two APs is the one that isnt working has 2.4, 5 and 6 mhz frequencies and the other only 2.4 and 5 on. Unsure if thats the real reason but its the only thing i see different.