You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know why, but if you using the experimental-hooks version you will semi-brick the adrenaline homebrew
When you running adrenaline, you choose the adrenaline Setting by press the button from Dualshock 4 controller, the controller get disconnected right away. The screen goes black, and the Power LED keep blinking.
After few second i press the power button and had to unlock the screen, the game goes freeze and i have to exit adrenaline by Vita button instead.
ds4vita 1.2 does not have this problem but the Analog stick stop moving every 5 second.
So my suggestion solve the analog problem of ds4vita 1.2.
p/s : Shoulder buttons had wrong assist for somegame. Night of Azure have L2/R2 assist as shoulder button instead of L1/R1. Retroarch have the same problem
The text was updated successfully, but these errors were encountered:
I've been getting a similar problem, only this time when opening Adrenaline, the screen just goes black, turns the screen off, after I press the power button to wake it back up, an error message shows up and I went back to the Vita menu.
I don't know why, but if you using the experimental-hooks version you will semi-brick the adrenaline homebrew
When you running adrenaline, you choose the adrenaline Setting by press the button from Dualshock 4 controller, the controller get disconnected right away. The screen goes black, and the Power LED keep blinking.
After few second i press the power button and had to unlock the screen, the game goes freeze and i have to exit adrenaline by Vita button instead.
ds4vita 1.2 does not have this problem but the Analog stick stop moving every 5 second.
So my suggestion solve the analog problem of ds4vita 1.2.
p/s : Shoulder buttons had wrong assist for somegame. Night of Azure have L2/R2 assist as shoulder button instead of L1/R1. Retroarch have the same problem
The text was updated successfully, but these errors were encountered: