Thanks I just turned off driver signing and rebooted. Gonna try that next. Can I ask (and again, another dumb one) but when this unit goes into the EDL mode, the screen just turns black with nothing on it, is that correct? I am holding vol up and down, powering on, then once i see the momentary logo flash I let go and its just a black screen while I do things. Just want to make sure Im not missing something dumb here either. Again thanks for the help and responses!
Hey pgale, great write-up!
In the spirit of sharing setup and whatâs workingâŚ
Couple of data points based on my on-going testing with the three units I have. All on 8.1, with the bromite webview installed via Magisk, and using the Fully Kiosk application. First, this issue is new, and just popped up. Iâve lost wifi connections after somewhere between 7 & 10 days. This is with the unit/s being less than ten feet from the wifi router. Second, switching between the Fully Kiosk app and an Android application (Iâm trying to use it as a combination of HA & music player) such as Ampache, Dsub or Tempo seemed to randomly stop the turn screen off functionality within the Fully Kiosk app.
So, to âresolveâ these issues, what Iâm using is an automation via a button press on the HA dashboard that will switch to the Android app, wait for 5 minutes, then push the Fully Kiosk App to the foreground, and then turn off the screen. This gives me enough time to select an album or a podcast or radio station, and the music will continue to play in the background after the HA dashboard pops back up. Using this automation process seems to be working; using the motion detection feature in the Fully Kiosk app will turn the screen on, and the timer to turn the screen off in the Fully Kiosp app works. When I didnât have the "turn screen offâ after pushing the Fully Kiosk app to the foreground, I had intermittent failures; the screen would just stay on.
Finally, Iâm using the same strategy for the wifi issue, I have an automation in HA that will reboot the Lenovo at three oâclock in the morning, wait for 4 minutes (to make sure the reboot process finishes) than push the Fully Kiosk App into the foreground (the Fully Kiosk app is also set to autostart within its settings) and then wait 3 minutes and then turn the screen off. Whatâs cool about this solution is that as I stated previously, I found that the âTeamsâ app has to be installed and running to resolve the issue of inconsistent motion detection within the Fully Kiosk to turn the screen on, and to resolve the issue of the screen brightness randomly changing/dimming. With this automation, despite the âTeamsâ App popping up immediately upon reboot, and seeming taking over the device, the automation will get the HA dashboard in the Fully Kiosk app browser up and running, and displaying on the unit.
Hope this of help to someone.
Jeff
Yes exactly that - the screen is black after a brief flash of the logo.
Thatâs interesting and annoying for you. Iâve not seen any WiFi issues - at least I donât think so. My devices have been on for a few weeks now but I have been constantly updating the dashboards and restarting the browser so wonder if thatâs been masking the issue - or I just donât have it.
IMHO itâs faster and less frustrating to flash on Linux, even if that means you have to learn.
QFIL is quite the mess - maybe itâll work for you - but probably it wonât; in either case you donât get much visibility into why.
Edl on windows requires you to have both a working python environment and properly configured drivers.
On Linux, both of these things just work.
Honestly, the only people for whom flashing from microsoft is âeasierâ are those who are already familiar with python development on windows.
2 Likes
There is a live cd on edlâs github page to make it even easier. 
Gonna try it on my wifeâs PC in a few. If that doesnt work I will temp turn off my pihole and start down that road. I guess in the end I will have a SD Card ready for the future for anything I need to do. Just curious, and please excuse my ignorance, but Ive been meaning to make a back up SD for my pihole anyhow (sadly I used the lite, GUIless one on my current). I can do all of the on the regular RPI OD 64bit I assume? May make sense to do 2 birds with 1 stone sorta thing assuming it will work. Thanks!
Again excuse my ignorance here but with this, what basic steps do I need to do before Im at the point at which I can run the handful of commands? Can I flash RPi OS to sdcard, throw in my RPi, basic setup, get into the system then run this?
If your wifeâs computer has a dvd drive, just use the edl livecd I mentioned above?
Oh I didnt realize thats what it was (desides the obvious DVD name lol). So I actually have a DVD ROM still. I will give it a try, thank you
Should work just as well using a Thumb drive.
1 Like
Thanks all I may need to try that tomorrow. I assume if I just make it Bootable right?
As for my adventures into LinuxâŚ
so I had planned to make a 2nd copy of pihole as a backup for my pi anyhow so used this as an excuse. I include the rpi os gui on this one. Anyways I donât entirely know what I doing and I donât mean to turn this into a Linux support thread but maybe yall can offer some hopefully basic advise.
Booted in, got on the main interface with keyboard and monitor
downloaded the flash file
Went to the edl github and ran all the commands under the linux section, weâll minus the ones for other versions of Linux (did the umbuntu ones)
I noticed the very last command for sudo python setup. Py (sorry not looking at exact command just memory) seemed to throw some trace errors after running for a bit.
I didnt notice this as first so I moved the flash files over to the main edl directory and ran the command posted on post 1 (changed from. /edl to edl for beginning)
It started to run but thru an error about a package for âusbâ.
For shits and giggles I reran that last command again (on edl page for the setup py)
Then the edl command, this time it got past the USB and now has one for âpyzlaâ.
Rerunning the setup Py one more time I see where itâs grabbing that and I seems like it gets past that but then fails right after.
I guess my question is, does this mean there is an issue with where it pulling the files from? It all seems like grabbing the files should be pretty basic yet itâs failing. Again Iâm pretty noob with this so if itâs something dumb Iâm overlooking id appreciate. Worst case I will try the bootable usb tomorrow. Thanks all!
Iâve never tried to install it outside of my home directory.
I just
sudo apt install adb fastboot python3-dev python3-pip liblzma-dev git
sudo apt purge modemmanager
then from ~/, I
git clone https://github.com/bkerler/edl
cd edl
git submodule update --init --recursive
pip3 install -r requirements.txt
and to use it;
cd ~/edl
./edl
1 Like
USB passthrough doesnât work but PCI does.
Maybe this is my problem. Went thru the steps again and on pip3 install - r requirements.txt got this
Sorry again to be dumb here but Iâm using a rpi 3 which does not have pci on it. Is that going to be an issue?
That was in reply to an older post getting it to work on an ubuntu vm on proxmox. Nothing to do with your situation.
Thanks Matt. Ive been going thru it with the virtual environment or what. I think the main issue now may be that Im using PiOS because I couldnt get all the python stuff to install via requirements.txt. For example I had to manually install lxml which did seem to work. Also on keystone-engine it yelled about cmake so I installed that manually (again seemed to work). Only remaining one is keystone-engine and when I run it, after 2min it hangs on the spinning wheel. I left it for 20min but still no response. Going to let it sit longer and see if any change. If not I will take it I am not ready for linux.
Just stinks I think I was close, once that was in everything was ready to run EDL.
Anyhow I dont mean to take away from the purpose of this thread with linux noob stuff.
Thanks all for the help and sorry to go down the linux blackhole. So I think Im in business. Was quite the journey but I can say I landed on using the âdvd liveâ using rufus to put to a bootable USB. From there just had to grab the files on another pc, put on usb drive and copy over and everything worked kinda like someone mentioned. Gonna mess now with the set up of the system itself now and play with it. Again, thanks all
Also for anyone looking at this in the future, I strongly encourage going this route, unless you know linux. I suppose the cool thing is if I have to do this for a 2nd unit, I think the whole operation will take me 5min to boot to the USB, hook up the cable and run the command so thats promising