evilsocket / evilsocket/pwnagotchi

[BUG] Screen Disabled in Auto Mode

Open
#993 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
9.2k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

**This only seems to have started with the new 1.5.5. release. I did not see it happen in the previous release.**

After flashing an SD card and going through the normal setup, the screen would load up and change in MANU mode while plugged into my computer. All seemed to work without issue. But then when I would unplug the rpi0w from the power port and into the data port, the screen would never change.

However, once I went back into MANU mode, the screen would show how many handshakes were captured, friends were made, etc, indicating that despite no change in AUTO mode, the Pwnagotchi was still doing something.

I ended up re-flashing the SD and starting with a _super _simple__ '''config.toml''' file and then adding my customizations in one by one until the issue was reproduced. I then went back one step and and removed the block I had just added and voila, the screen worked again.

**To Reproduce**
Steps to reproduce the behavior:
1. Flash SD card with Pwnagotchi 1.5.5
2. Remove and Replace the SD card and add your config file into the '''boot''' of the SD card.
3. Include this section of code:

`bettercap.silence = [`
`"ble.device.new",`
`"ble.device.lost",`
`"ble.device.disconnected",`
` "ble.device.connected",`
`"ble.device.service.discovered",`
`"ble.device.characteristic.discovered",`
`"wifi.client.new",`
`"wifi.client.lost",`
`"wifi.client.probe",`
`"wifi.ap.new",`
`"wifi.ap.lost",`
`"mod.started", `
`]`

**These are my steps, but today I will be attempting to add the block of code back in and out with other plugins in the config file to see how it affects the screen.**

**Expected behavior**
Take note of any numbers or data on the screen while it is working (plugged into data port). Once you unplug the Pwnagotchi from the data port of your rpi0w and plug it into the power port, you'll see the led flash and then become solid, but the screen will not change.

When you then plug it back into the data port, you should see update data, handshakes, kicked stations, etc, that was different from when you previously had it plugged into the data port.

**Screenshots**
The above is fairly straight forward, but as I mess with it today, I'll take some screen shots.

**Environment (please complete the following information):**
- v1.5.5.
- OS version
- Rpi Zero W, Waveshare_2 e-ink display
- A confirmed, good working, data usb cable.

I will update this today if I get some changes to work on it.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue on a Raspberry Pi Zero W with the Waveshare_2 display, Pwnagotchi 1.5.5, and the reported bettercap.silence block in config.toml. Compare display updates in MANU and AUTO modes, then trace how that configuration affects screen updates; done when AUTO mode continues showing current handshakes and other data after switching power ports.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.