Volume keys are not being identified about microg-unofficial-installer HOT 24 CLOSED

Sorry for the wait but the code isn't ready yet, I had encountered a strange issue that I need to fix.

from microg-unofficial-installer.

Very good, thanks for the testing :)

from microg-unofficial-installer.

Aurora Services isn't installed by default, but during the zip flashing you could use the live setup to enable it.

from microg-unofficial-installer.

Does TWRP support this type of installation? Because when I flash the zip, no timeout is activated so I can press the volume button, it just starts installing.

from microg-unofficial-installer.

Yes, it works perfectly in TWRP.

TWRP have an option to copy log.
Could you please flash the zip, copy the log and post it here so I can see what happens?

from microg-unofficial-installer.

dmesg.log
logcat.txt
recovery.log

from microg-unofficial-installer.

@fabianski7
The warning that I have put was too much generic, now I have improved it.
Could you please retry with this test build and then post the recovery.log again?

Edit: Link removed

from microg-unofficial-installer.

sorry the delay

recovery (1).log
logcat (1).txt
dmesg (1).log

from microg-unofficial-installer.

@fabianski7
No problem but you have flashed the v1.3.1-beta, not the one linked.

from microg-unofficial-installer.

No problem but you have flashed the v1.3.1-beta, not the one linked: https://androidfilehost.com/?fid=10620683726822057649

true 🤦‍♂️

Well, now I can access the installer. The problem now is that I press the volume key only once and it registers twice.

This was an example. I pressed the + button to install Aurora Services, but it ended up installing NewPipe as well

QUESTION: Do you want to install Aurora Services?
+) Yes
-) No

/tmp/custom-setup-a5k/origin/priv-app/AuroraServices.apk
 
Key press: + (42)
 
Enabling: Aurora Services
Verifying... OK
QUESTION: Do you want to install NewPipe?
+) Yes
-) No

/tmp/custom-setup-a5k/origin/app/NewPipe.apk
 
Key press: + (42)
 
Enabling: NewPipe
Verifying... OK

recovery (2).log
logcat (2).txt
dmesg (2).log

from microg-unofficial-installer.

@fabianski7
When you have time could you please try this new test build and tell me if the situation has improved or nothing is changed and post the recovery.log again?

Edit: Link removed

from microg-unofficial-installer.

Well, now I can access the installer. The problem now is that I press the volume key only once and it registers twice.

Stills the same

recovery (3).log

from microg-unofficial-installer.

@fabianski7
It is a really strange issue, could you please try even this and post the log?

Edit: Link removed

from microg-unofficial-installer.

recovery (4).log

from microg-unofficial-installer.

Is the problem reduced or it is still the same?

from microg-unofficial-installer.

stills the same

from microg-unofficial-installer.

Could you please try this and post the recovery.log?

Edit: Link removed

from microg-unofficial-installer.

Here you go
recovery.log

The double-click is still happening, and when I press the button, this message is displayed: Invalid choice!!!

And google play was unfortunately installed this time 😫

from microg-unofficial-installer.

@fabianski7

Hi,
it seems that the problem is in the parsing; it get the wrong key code.
Since it works on my phone maybe on your phone it emit a different sequence on key press.

Could you please do this?

• Restart the phone in the recovery
• Connect to the pc via usb
• On the pc on the command prompt execute: adb shell
• Inside the adb shell execute: cat /dev/input/event3 | hexdump -v -x
• Press volume + on the phone and transcribe the output the you get inside the shell
• Release volume + on the phone and transcribe the output the you get inside the shell
• Press volume - on the phone and transcribe the output the you get inside the shell
• Release volume - on the phone and transcribe the output the you get inside the shell

from microg-unofficial-installer.

it seems that I don't have hexdump installed :'(

127|OnePlus6:/ # cat /dev/input/event3 | hexdump -v -x                                                                 
/system/bin/sh: hexdump: inaccessible or not found

from microg-unofficial-installer.

@fabianski7

Could you please do this?

• Restart the phone in the recovery
• Connect to the pc via usb
• On the pc in the command prompt execute: adb shell
• Inside the adb shell execute: cat /dev/input/event3 > /tmp/event-log.dat
• Press and release volume + on the phone
• Close the adb shell
• On the pc get the saved file with: adb pull /tmp/event-log.dat .
• Upload the file event-log.dat here

from microg-unofficial-installer.

Here is the file. Github does not allow .dat files to be uploaded and I chose not to change the format

https://drive.proton.me/urls/737ACT7ESC#tqIE19Oi2ba9

from microg-unofficial-installer.

@fabianski7
The problem was that the timestamp of the input event is more bigger on your phone (probably because of the differences between 32/64-bit) and the data that I need was shifted.

It should now be fixed, could you please try this and post the recovery.log?
https://androidfilehost.com/?fid=10620683726822062571

from microg-unofficial-installer.

recovery.log

now works perfectly!

from microg-unofficial-installer.