Hey,
dumb question, does anybody have problems with loosing already bonded devices over night/hours?
I just reinstalled and rootet (AP with magisk [but no TWRP]) my device and slightly debloated it (by hand). So far so good.
But every couple hours it forgets the paired devices (Car Radio and Galaxy Gear).
Does anybody have an idea or at least a hint how i can monitor what is going to happen?
thx in advance
Matt
I'm a little bit further. Every time when i disable BT, the device emptys the config.
I found the bt_config.conf file. But the system does not seem to refer to it. Because when i back it up and restore it to the original path the BT does not connect.
So, does anyone knows where/who's the initial Config file.
thx in advance
Install the libsecure_storage magisk module from ianmacd. That should fix it.
AMEN!!!! Thx, thats it.
Can you describe what it does?
Donkeykong307 said:
Install the libsecure_storage magisk module from ianmacd. That should fix it.
Click to expand...
Click to collapse
zero5liters said:
Hey,
dumb question, does anybody have problems with loosing already bonded devices over night/hours?
I just reinstalled and rootet (AP with magisk [but no TWRP]) my device and slightly debloated it (by hand). So far so good.
But every couple hours it forgets the paired devices (Car Radio and Galaxy Gear).
Does anybody have an idea or at least a hint how i can monitor what is going to happen?
thx in advance
Matt
Click to expand...
Click to collapse
I have the exact same problem. My S10+ keeps forgetting already connected BT Devices since I rooted it. I'm gonna try that libsecure_storage Magisk module.
I am suffering from this on my plus, does anyone know which section the "Install the libsecure_storage magisk module" is located on forum?
Best wishes
Wingchundub said:
I am suffering from this on my plus, does anyone know which section the "Install the libsecure_storage magisk module" is located on forum?
Best wishes
Click to expand...
Click to collapse
If you havent found the forum you could try this alternative:
https://forum.xda-developers.com/ga.../zip-libbluetooth-patcher-fix-losing-t4017735
Thank you, But unfortunately it not work
It came up with :- Updater process ended with ERROR 1
Related
UPDATE: It works fine!
Using my xposed module or patched Telecom.apk you won't see never "Headset is plugged in" notify...
in TtyManager method "onWiredHeadsetPluggedInChanged" just bypass a condition.
Special thanks:
- Sony
- Ciocedj
- me, of course
Not trying to rain on your parade or anything, just stating the fact that there's already an existing xposed module that does just that: https://forum.xda-developers.com/xposed/modules/mod-noheadsetnotification-t3458184
mhaha said:
Not trying to rain on your parade or anything, just stating the fact that there's already an existing xposed module that does just that: https://forum.xda-developers.com/xposed/modules/mod-noheadsetnotification-t3458184
Click to expand...
Click to collapse
I've never seen before... Sorry however I've already made my own module some weeks ago... The patch is the same only different approach.
Cool, there's nothing to be sorry for, I was merely informing you that there actually is an existing module for the function you're describing, and possibly save you some time from developing a duplicate solution for the same problem.
Thank you for sharing your work.
Cheers!
Michele2 said:
UPDATE: It works fine!
Using my xposed module or patched Telecom.apk you won't see never "Headset is plugged in" notify...
in TtyManager method "onWiredHeadsetPluggedInChanged" just bypass a condition.
Special thanks:
- Sony
- Ciocedj
- me, of course
Click to expand...
Click to collapse
Hi I am running Nougat which doesn't work with Xposed. I tried your Telecom.apk but am not able to install it. It says the file is corrupted. Is there a way to get this mod without Xposed?
Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?
I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Are you using the hide root feature?
If so then that is probably your issue.
opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!
ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:
jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!
stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?
webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?
Used S10 for half a month, not sure but seems like happened after magisk rooted, and no magisk module installed, it also happened to another person I know.
Never booted to system without magisk, and sometimes paired devices lost even when I didn't restart at all.
Anyone knows the solution? It's really important for Galaxy Buds users, thx!
Solved with Libsecure_storeage...magisk module, please delete this thread, thx
mansonstein said:
Solved with Libsecure_storeage...magisk module, please delete this thread, thx
Click to expand...
Click to collapse
Sorry can you explain?
Tks.
Has anyone been able to get Viper4Android working an Android 11? i flashed using the April 2021 Factory Image and have tried following multiple threads and guides, but have never gotten V4A to work consistently/completely.
Viper4android Android 11??
There is viper4android for android11 or I need to wait?
forum.xda-developers.com
This is the Viper4Android I've used for 6+ months. Its the only working, plug and play version I've found for Android 11. You simply download the zip, flash in magisk -- and done. There's nothing else you need to do.
Its 100% safe. Its 100% working. So easy.
I can vouch for it... And love it!
Click on the youtube link, and the zip is in the info there. No need to watch the video. Just flash with magisk or a kernel manager... and done.
I'm on LineageOS for microG 18.1, Proton kernel 1.4, Magisk rooted and this is not working for me. Further more, it mess up with SElinux making it disabled. Fortunatelly, there is an app SElinux switch, that on every boot make it Enforcing again.
I have the 5a but there are no posts yet.....
are any of you getting V4a to work using the USB port ? I run my phone usually into a dac via the usb, but Viper's only working on my phone through the headphone jack.
That YouTube video has been removed. Any chance someone could post the .zip? TIA
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
mmarcz said:
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
Click to expand...
Click to collapse
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Are you rooted normally with magisk per the instructions in this forum? Thats all I've done. Do you have a phone from google or from a carrier?
I got mine from google. Im rooted per the normal instructions. I have magisk v2.7.2.1 and the magiskhide props config modules installed. Ive never had a bootloop with either.
Not really sure what else to try. For what its worth, I cant get viper working on a rooted pixel 3, no bootloops, but the status always says abnormal.
Danny St. Angelo said:
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Click to expand...
Click to collapse
mmarcz said:
Are you rooted normally with magisk per the instructions in this forum?
Click to expand...
Click to collapse
Yes. And updating using this thread (thank you @drdionysius).
(Thanks for the reply btw.)
mmarcz said:
Do you have a phone from google or from a carrier?
Click to expand...
Click to collapse
Bought from a 3rd party actually, sealed box, no carrier branding or firmware.
Magisk version (from Canary channel) is f822ca5b (23001) -- that doesn't look right lol... oh, and Systemless hosts module installed only.
I only lost Viper when I updated to the September factory image
<shrug> idk why </shrug->
don't think it happened with other updates.
I'm pretty sure tho that I'd be in top shape, also indebted, if someone could post ViperFX_Android11.zip since the above referenced YouTube vid is gone and, with it, the link and I can't find the same version anywhere else. Thank you very much.
I just received my used 4a 5g. Got V4A v2.7.2.1 downloaded from Magisk v23 working last night...but it was a long trial & error ordeal. First download it showed Unsupported and Abnormal. Thought maybe it needed the Audio Mod Library but that didn't work. Then I tried the Audio Compatibility Patch to no avail. I tried V4A Legacy. Mulitple installs and uninstalls of all the various modules and combinations. At this point I'm not even sure what I did, or in what order/combination, but V4A is installed and working as intended. I do NOT have any of the Audio modules installed, just V4A. Don't know why it didn't work originally, or what made it finally work after fiddling with it for about an hour, but for me, that's my story/advice. Wish I could give an exact process to follow.
Here you go
mmarcz said:
Here you go
Click to expand...
Click to collapse
Top man!
Thank you
mmarcz said:
Here you go
Click to expand...
Click to collapse
Thanks for posting this! The version I had (v2.7.2.1) didn't work as reliably as it should. Often times it wasn't "processing". I uninstalled it and installed yours. So far it seems to be working well.
BIG BONUS - your version allows to view settings for the speaker, ear-buds, & blue-tooth without actually being connected to said devices. I never liked that "feature" of the newer V4A versions.
what about android 13?
I have been having a few issues lately. When I rooted my phone, I lost access to rcs messaging (like it wont let me register for it) and when I connect to a Bluetooth device it disappears from the paired list when I restart the phone. Another issue is that I no longer can see the estimated time till 100% when charging my phone. Does anyone else experience this or does anyone know how to fix it?
My kernels which I had installed are: physwizz --> carbon -> eureka -> carbon (current)
My device is rooted with magisk and the only module right now is the vipe4android module.
Any help would be appreciated.
Borkode said:
I have been having a few issues lately. When I rooted my phone, I lost access to rcs messaging (like it wont let me register for it) and when I connect to a Bluetooth device it disappears from the paired list when I restart the phone. Another issue is that I no longer can see the estimated time till 100% when charging my phone. Does anyone else experience this or does anyone know how to fix it?
My kernels which I had installed are: physwizz --> carbon -> eureka -> carbon (current)
My device is rooted with magisk and the only module right now is the vipe4android module.
Any help would be appreciated.
Click to expand...
Click to collapse
time until end of charging is not shown due to kernel. At the expense of bluetooth, it's kind of because of the firmware.
SirKosichka said:
time until end of charging is not shown due to kernel. At the expense of bluetooth, it's kind of because of the firmware.
Click to expand...
Click to collapse
I just flashed stock firmware and rooted with magisk and also installed twrp. I noticed that I am still having the bluetooth issue even tho I have a mostly stock config now.
Borkode said:
I just flashed stock firmware and rooted with magisk and also installed twrp. I noticed that I am still having the bluetooth issue even tho I have a mostly stock config now.
Click to expand...
Click to collapse
I can't help you with the problem with bluetooth
SirKosichka said:
I can't help you with the problem with bluetooth
Click to expand...
Click to collapse
Oh okay, thanks - I got to fix the issue by flashing the bluetooth library patcher module for Magisk if someone is having that issue.