This is happening on my phone too (LG G5 US 992) my joycons work fine on my Nintendo switch v2 wired or wireless.
My phone is running Android 7.0.0 (the one from LG).
I tried to use both that doesn't work and only one it still has lag the phone is Bluetooth 4 so it should work fine but it doesn't and the buttons on the right joycon press the ones on the left one so I can't play Minecraft PSP version on my phone probably have to get a old iPhone 6s because iOS isn't as broken as Android is
My phone is running Android 7.0.0 (the one from LG).
I tried to use both that doesn't work and only one it still has lag the phone is Bluetooth 4 so it should work fine but it doesn't and the buttons on the right joycon press the ones on the left one so I can't play Minecraft PSP version on my phone probably have to get a old iPhone 6s because iOS isn't as broken as Android is
- Joined
- Feb 23, 2015
- Messages
- 575
- Trophies
- 0
- Age
- 25
- Location
- France
- Website
- www.youtube.com
- XP
- 1,536
- Country
Joycon are officially supported in Android 11, you only need to hope your phone manufacturer will update your phone to Android 11 when it comes out.
Ffffffffff
I just got Android 10 last month... FML. Looks like I be waiting another year for Samsung to get their shit together.
- Joined
- Feb 23, 2015
- Messages
- 575
- Trophies
- 0
- Age
- 25
- Location
- France
- Website
- www.youtube.com
- XP
- 1,536
- Country
This isn't possible. If it was, that's a very big security issue. Root is like system administrator, there shouldn't be any way of granting it to a non-root user.
I'm trying to find the hex values to edit in my bluetooth.default.so. I already did find the "B1 F5 48 7F 88 BF 4F F4 48 71" and edit it as Igloo suggested, and it made no difference on my device. I'm using a Sony Xperia Z5 compact. Bootloader unlocked and running Lineage 14.1 - Android version 7.1.2
I put the bluetooth file in a decompiler, Ghidra and searched for some of the information listed here, namely HidSSRMaxLatency and I got quite a few hits, I just dont know what value I should be editing in hex.
I've read that its the 800ms for the SSR, but I'm not sure
These are some of the search results I came up with in Ghidra and they seem to point directly to where I need to edit but the problem is that I'm not sure HOW to edit them. I mean changing the value from 800 to 0 in the Hex Editor.
This last one seems to have a reference to the uVar = 800 which is the mov.hi.w that
MK73DS was referencing.
I noticed that Igloo the original creator of this has been offline since 2018 so I doubt he is going to chime in to provide any advice on hex editing that 800 value.
If anyone wants to take a crack at editing or check the file I'm uploading it on my google drive here.
https://drive.google.com/file/d/1z40fcYH5-mghZsJICrAcO_QCvXUyXkkU/view?usp=sharing
For the time being I'm going to continue to experiment and try and see if I can fix it.
I put the bluetooth file in a decompiler, Ghidra and searched for some of the information listed here, namely HidSSRMaxLatency and I got quite a few hits, I just dont know what value I should be editing in hex.
I've read that its the 800ms for the SSR, but I'm not sure
These are some of the search results I came up with in Ghidra and they seem to point directly to where I need to edit but the problem is that I'm not sure HOW to edit them. I mean changing the value from 800 to 0 in the Hex Editor.
This last one seems to have a reference to the uVar = 800 which is the mov.hi.w that
MK73DS was referencing.
I noticed that Igloo the original creator of this has been offline since 2018 so I doubt he is going to chime in to provide any advice on hex editing that 800 value.
If anyone wants to take a crack at editing or check the file I'm uploading it on my google drive here.
https://drive.google.com/file/d/1z40fcYH5-mghZsJICrAcO_QCvXUyXkkU/view?usp=sharing
For the time being I'm going to continue to experiment and try and see if I can fix it.
Last edited by 01X,
If you still have that Magisk module on hand I would very much appreciate it. Experiencing this lag on my OnePlus 7T right now whenever I sync up my Pro Controller.
For the future people that stumble on this thread, I made a magisk module that will modify the libbluetooth_qti.so file
just copy the zip file and install it in the magisk manager. (works on Android 10, Oneplus 7T Pro)I wasted like 10 hours for this simple thing because I had no knowledge about magisk modules.
What I have learned while I was searching for solutions:
- You cannot edit Android 10 System files with adb or root explorer (idk you just can't)
- The easiest way is making a magisk module that overrides the file.
Is this thread still alive?
I have an old tablet (Samsung Galaxy Tab 2 7") with a clean ROM of KitKat 4.4.2 installed that i want to use it to play some Snes games through an emulator
I have a generic "pro controller" gamepad, that has almost 1 full second of delay, and wonder if this method can also work with android 4.4.2 devices
Even when i find the bluetooth.default.so file, i can't find any of the hex values @igloo suggested
Also tried some disassemble softwares to search for values called bta_hh_read_ssr_param, MOV, or 800 or 500 but i have no idea what am i doing.
Is anyone familiar with disasseble so i can share the bluetooth.default.so file and help me find the correct hex values to write in the hex editor?
I have an old tablet (Samsung Galaxy Tab 2 7") with a clean ROM of KitKat 4.4.2 installed that i want to use it to play some Snes games through an emulator
I have a generic "pro controller" gamepad, that has almost 1 full second of delay, and wonder if this method can also work with android 4.4.2 devices
Even when i find the bluetooth.default.so file, i can't find any of the hex values @igloo suggested
Also tried some disassemble softwares to search for values called bta_hh_read_ssr_param, MOV, or 800 or 500 but i have no idea what am i doing.
Is anyone familiar with disasseble so i can share the bluetooth.default.so file and help me find the correct hex values to write in the hex editor?
Similar threads
-
Xdqwerty
what are you looking at? -
Sicklyboy
-
K3Nv2
-
Psionic Roshambo
-
NinStar
-
@
Sicklyboy:
I'm planning to start building it back up though. Plus, Usenet automation around music downloading has gotten so much better since then
-
@
Psionic Roshambo:
I used to use high end headphones and speakers JBL back when they made good speakers lol X-Fi Fatality edition sound card on PCI with XP back when Windows had good sound....
-
-
@
Sicklyboy:
I use AKG K7XX headphones for daily use, but Meze 99 Classics when I want to *enjoy* the music+1
-
@
Psionic Roshambo:
I mean built in sound on mobo's has gotten way better but still XP handled sound better and X-Fi was still better than onboard audio even to this day
-
@
Psionic Roshambo:
Hell not sure what was going on but for like a few weeks MP3's sounded muffled, some driver or Windows update fixed it. Thank god lol
-
-
@
Sicklyboy:
Oh boy Massdrop has $1100 IEMs. Want, but not at that price lmao. https://drop.com/buy/campfire-audio-andromeda-emerald-sea-iem
-
@
Sicklyboy:
I'd sooner buy the Meze 109 Pro if I was dropping that much on headphones. I don't even like buds/IEMs
-
@
Sicklyboy:
I got the Google Pixel Pro buds, they're good enough for when I need portable audio. And some really cheap IEMs that Dankpods recommends, I think the KZ ZSN Pro+1
-
@
K3Nv2:
I'd stick with cheapo Chinese $10 ones quality is actually becoming on pair with name brand since name Brand usually quads the price up anyway loose one bud that's another $200
-
@
Sicklyboy:
My Pixel Pro buds shit the bed a month or two ago. My wireless charger (which they do support Qi charging) absolutely COOKED them. Caused some problem that caused the case to heat up to 180F+
-
@
Sicklyboy:
They were like 9 months out of warranty but I hit up Google support anyway and told them how hot they were getting and they replaced them with new ones because they wanted these for failure analysis lol
-
-
-
-
-
@
Sicklyboy:
Apparently the case has a problem with >15W wireless chargers. Google design fault, that one.
-
-
-
-
-
-
@
Sicklyboy:
@Xdqwerty, power through a coil of wire causes an electromagnetic field to be generated. Another coil of wire can be set up to harness the power from that electromagnetic field and turn it into usable energy for charging a device
-
