Troubleshooting
If your device isn't working properly, you should find a solution here.
- the battery percentage actually shows just the voltage, which changes not linearly
- the overlay doesn't update when framebuffer isn't updated
- emulators need manual button configuration (for some reason emulationstation cant make a good default config)
- LVGL gets confused with input from both touchscreen and joysticks
- for some reason, the overlay for touchscreen needs to be trcompiled on any new system
- chromium isn't working with alsa equalizer
Those issues hopefully will be fixed in the future, if you want to help then please contribute at iNapMalinka-Code!
First of all, check that you've soldered the FPC connector right. There's a very high chance that even though it looks ok, it may be not soldered properly. Try to solder it again and check the connections with a multimeter.
It could be either a connection or software problem. If you're sure that the connector and Pi are soldered properly, the driver may simply not be loading. Ensure that:
- there's a path specified to it in file
/etc/rc.local - there's a file at the specified path
- the file has permission to run:
sudo chmod 777 (file)should work. You can try to run the driver manually withsudo (file) &.
That means your display isn't as fast as others are. Sadly all you can do is to rebuild the driver with a lower higher speed divider - you may want to read the official driver guide here.
Type in dmesg | grep ft to show all boot messages related to ft. If you get something like this:
Your touch panel isn't connected properly. Check once again if your ribbon is attached properly, and if your connector is soldered as it should be.
It's probably because of pressure from the case. Try to tighten or loosen a few screws and see if that helps. If the touchscreen isn't working properly even without case, it may be broken.
Make sure that more than 3.3v are being applied to the 5v pins - a charged battery should provide 4.2v. Remember to flip the switch, insert the SD card, and again, check the connections.
Check your config.txt file again. You should see a headphone device after typing in aplay -l command.
If you still don't get any sound, check the connections, and type in alsamixer to change the volume manually. If you're sure all of that is correct, check your speakers and amplifier, try to detect where the signal is lost.
Type in alsamixer -D equal to show an equalizer:
While playing a sound, adjust it as needed.
Make sure that the button contacts are clean, and wipe them with IPA alcohol again. If you feel they're not working well, it may be a poor print quality or lack of postprocessing.
That means that the driver didn't load. Ensure that:
- there's a path specified to it in file
/etc/rc.local - there's a file at the specified path
- the file has permission to run:
sudo chmod 777 (file)should work. Try to run the driver manually withsudo (file) &.
You can re-assign them by resetting the configuration in EmulationStation. You can do it with the retropie-config script.
If you didn't use old joysticks that possibly could have drift problems, it's probably a bad connection. You can check this by pressing a finger on joystick connector - if the behavior changes, then try to reconnect the joystick. Do it very carefully, those carbon paths are very fragile. If you think it's too late then try cutting a little bit of them. The connector should "catch" the unused pad, but still, you may want to consider replacing the bad joystick.
Remember to check the print quality and make some good postprocessing - just try it out before the final assembly, if there's still something more to trim. You may also want to add a little spring so the button will always jump back.