MiA1 APTX support for Pie - Xiaomi Mi A1 Questions & Answers

So my wife recently gifted me an APTX enabled headset and i've been trying to get APTX to work on my MiA1 that's recently been updated to Pie.
Problem is, i can set the codec to APTX via developer options but as soon as i exit the setting menu, the codec then reverts back to SBC.
Headset is the Sennheiser 4.5 BTNC.
I've been using google to look for solutions but seeing that i've recently updated to Pie, the only solution i found was for Oreo.
Anybody experience the same? Thanks!

Try the "APTX for Android Oreo & Pie" module on the Magisk repo.

@laymonage @enteng_kabizote does that worked?

enteng_kabizote said:
So my wife recently gifted me an APTX enabled headset and i've been trying to get APTX to work on my MiA1 that's recently been updated to Pie.
Problem is, i can set the codec to APTX via developer options but as soon as i exit the setting menu, the codec then reverts back to SBC.
Headset is the Sennheiser 4.5 BTNC.
I've been using google to look for solutions but seeing that i've recently updated to Pie, the only solution i found was for Oreo.
Anybody experience the same? Thanks!
Click to expand...
Click to collapse
my friend, if the cellphone is rooted and installed magisk, it would be better for you to install VIPER4Android FX and be able to do the settings from situ.module Viper you can download directly from the magisk repo.
my friend, if the cellphone is rooted and installed magisk, it would be better for you to install VIPER4Android FX and be able to do the settings from situ.module Viper you can download directly from the magisk repo

Related

Dolby Atmos for CM 12.1

Hey guys, i tried to install dolby atmos, but doesnt work "forced stop" anyone know how install this mod correctly?
http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
Thanks
it seems that you are not the only one experiencing it. If you go one page back on that thread there is also a nexus7 user suffering from the FC issue. you can try to find the answer in the thread but just wait till tomorrow and it might get answered by @worstenbrood as he is probably sleeping now.
you must install SELinux Mode Changer first, then open app/ touch Permissive/reboot/ install dolby atmos again

aptX Bluetooth works on many/all LineageOS devices

Google it up.
If your phone came with aptX stock OS then you can still use aptX after flashing LineageOS (after some file copying). :good:
This was not the case with CyanogenMOD.
CZ Eddie:
> If your phone came with aptX stock OS then you can still use aptX after flashing LineageOS (after some file copying).
Do you happen to know where file libbt-aptX-ARM-x.x.x.so file (likely libbt-aptX-ARM-4.2.2.so) and any other such files can be obtained from assuming LineageOS 15.1 needs/uses them at all? (this thread tells us it should be there for AptX support) That file is not included into LineageOS 15.1 and doesn't come with the APTX-Enabler.zip patch from this thread either. This is for Samsung Galaxy A3 2017 (SM-A320FL). I already tried asking around here and here besides that thread and strangely no replies so far. I understand LineageOS does support AptX for a couple of years by now (on devices with AptX support in their stock ROMs). Many thanks in anticipation...
dandreye said:
CZ Eddie:
> If your phone came with aptX stock OS then you can still use aptX after flashing LineageOS (after some file copying).
Do you happen to know where file libbt-aptX-ARM-x.x.x.so file (likely libbt-aptX-ARM-4.2.2.so) and any other such files can be obtained from assuming LineageOS 15.1 needs/uses them at all? (this thread tells us it should be there for AptX support) That file is not included into LineageOS 15.1 and doesn't come with the APTX-Enabler.zip patch from this thread either. This is for Samsung Galaxy A3 2017 (SM-A320FL). I already tried asking around here and here besides that thread and strangely no replies so far. I understand LineageOS does support AptX for a couple of years by now (on devices with AptX support in their stock ROMs). Many thanks in anticipation...
Click to expand...
Click to collapse
Just use the Magisk aptX module

How to export Dolby atmos in Yoga tab 3 plus?

Yoga tab 3 plus has 4 speakers, and it has offical dolby atmos in its rom. Anybody knows how to export dolby atmos and make a package so I can flash it in third-party roms.
Thank you.
BTW, the offical rom is android 6.0.1 while I'm in android 7.1. I'm using lineageOS and rooted. I'm wondering if I can locate those files and add or replace them.
zkn1021 said:
BTW, the offical rom is android 6.0.1 while I'm in android 7.1. I'm using lineageOS and rooted. I'm wondering if I can locate those files and add or replace them.
Click to expand...
Click to collapse
Nobody here will be able to answer that question. Please check out this thread
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
What you want to do has been done there.
Previously the LeEco version posted there worked well but doesn't anymore maybe because of changes in LineageOS. The Lenovo version posted there still seems to work but I am not sure if it produces the best quality.
Try A.R.I.S.E. It will blow you away (has Dolby Atmos as well).

LineageOS 15.1 Bluetooth problem

Hallo,
I installed LineageOs 15.1 on my hlte, and I had a problem with bluetooth
It works fine with music and media, but during a phone call I hear only an intermittent noise
it seems the same problem exlained here, at #3: https://forum.xda-developers.com/lineage/general/kb-article-troubleshooting-bluetooth-t3646969
after installing LineageOS 14, everything works good
GtrFabius said:
Hallo,
I installed LineageOs 15.1 on my hlte, and I had a problem with bluetooth
It works fine with music and media, but during a phone call I hear only an intermittent noise
it seems the same problem exlained here, at #3: https://forum.xda-developers.com/lineage/general/kb-article-troubleshooting-bluetooth-t3646969
after installing LineageOS 14, everything works good
Click to expand...
Click to collapse
Hello.
I've installed LineageOs 15.1 on my note 3 n9005 and bluetooth calls doesn't work on my radio car (music and media works good ). Before I installed it I had Aryamod 6.5 (marshmallow).
I don´t know how I can fix this problem. Please can you help me or tell me how you did it?
Thank you
GtrFabius said:
Hallo,
I installed LineageOs 15.1 on my hlte, and I had a problem with bluetooth
It works fine with music and media, but during a phone call I hear only an intermittent noise
it seems the same problem exlained here, at #3: https://forum.xda-developers.com/lineage/general/kb-article-troubleshooting-bluetooth-t3646969
after installing LineageOS 14, everything works good
Click to expand...
Click to collapse
I have same problem. Is thee any way to fix it?
omidpand said:
I have same problem. Is thee any way to fix it?
Click to expand...
Click to collapse
no
Hi all. LOS 15.1 same BT behaviour in car connection as yours guys. Also my Xiaomi electric scooter 365pro can't be seen by my BT. So... in Developer options ---> Bluetooth AVRCP version ---> change from default AVRCP 1.4 to AVRCP 1.6 . it my help
Doonayek/eMINEm said:
Hi all. LOS 15.1 same BT behaviour in car connection as yours guys. Also my Xiaomi electric scooter 365pro can't be seen by my BT. So... in Developer options ---> Bluetooth AVRCP version ---> change from default AVRCP 1.4 to AVRCP 1.6 . it my help
Click to expand...
Click to collapse
I'm having the same bluetooth problem with phone calls and an unofficial LOS 15.1 (https://forum.xda-developers.com/galaxy-note-3/general/rom-lineageos-15-1-t3743272 with lineage-15.1-20180808-UNOFFICIAL-hlte.zip) but setting AVRCP version to 1.6 did NOT fix my problem.
Did anyone try upgrading to 16.0 ?

Galaxy S10+ SM-G975F Galaxy Watch pairing issue with Magisk

Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Could it be related to tripping knox through rooting (i.e. then some of the Samsung apps will not work e.g. Samsung Health)? I am unable to register S.Health and Wearable (on my rooted S7 edge) will not work.
However, working fine on non-rooted S10+.
Does this help?
https://forum.xda-developers.com/galaxy-s10/how-to/guide-samsung-health-knox-0x1non-root-t4075853
Boot into TWRP and flash @ianmacd's multidisabler
I have the same issue with not rooted s10+ and gear s3
Xenenon said:
Hello,
Exactly Same problem!!!!!
Stuck badly!!!
Any solution!!!!
Ahmed
Click to expand...
Click to collapse
xBrownieCodez said:
Boot into TWRP and flash @ianmacd's multidisabler
Click to expand...
Click to collapse
I did but the problem remains the same!!!
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
lladwein said:
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
Click to expand...
Click to collapse
oops! It did not work on mine S10+
Getting frustrated day by day!
I think the era of Rooted Devices is over!!!!!
Xenenon said:
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Click to expand...
Click to collapse
Anything you figure out!
Please do share with me!!!!
I flashed Beyonde Rom 6.7 it comes based on the latest April Patch.
This fixed all my problems
No Bugs yet with this rom
https://forum.xda-developers.com/ga...pment-exynos/rom-beyondrom-v6-0-t4017921/amp/
Flash with TWRP
Health works
Bcs of magisk all my banking works fine (Sparkasse germany)
I LOVE IT
GeekSiddiqi said:
Anything you figure out!
Please do share with me!!!!
Click to expand...
Click to collapse
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
any update on this issue ?
Xenenon said:
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
Click to expand...
Click to collapse
But do you lose the Samsung stock camera with this Rom? I have the same exact problem as you. When I was running the Evolution X custom Rom I could connect. But I wasn't happy with the camera that Rom provided. The stock camera on this phone is so amazing and one of the main reasons I bought the phone. I feel cheated when I have to give that up
nasheednashy said:
any update on this issue ?
Click to expand...
Click to collapse
I was having the exact same issue. I just activated magisk hide. And also installed the magisk module, Bluetooth library patcher. Now mine paired up first try. Not sure which helped or if it was a combination of both. But I'm paired up now.
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
synite said:
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
Click to expand...
Click to collapse
Did you found a way to connect them?
Inviato dal mio Pixel 3 utilizzando Tapatalk
Hi! Given a Samsung Galaxy Watch Active 2 (LTE) watch and a rooted Galaxy S10 (Android Q). Bluetooth pairing starts but does not end. Two Magisk modules id have been installed but I can't pair them. Is there anything you can bring together? So much for all the stupidity to read, but no answer or stupidity throughout. I can't install Viper4android on the same phone under Android 10. Magisk 21.4, but the 2.7 Viper doesn’t go up. It is installed by plugin, but not among applications. Can these be solved somehow? There was no problem under Android 9. Unfortunately, for the latest Android Q version, XEH version November 27, 2020, TWRP is not trable either. I download the right version, with Magisk, I boot into the AP with Odin, then start button, and odin closes immediately. Nothing goes on this ****ty Android Q. I am waiting for help together or separately! Thanks!
Any update on this issue?
I have problem pairing my Galaxy S21 Ultra and Galaxy Watch Active 2.
No pairing issues before rooting (stock firmware). After rooting using both stable Magisk V22 and Canary 22005, it stuck on Finalizing Pairing screen. I also noticed that the Bluetooth and Samsung accessory icons briefly shown on the notification bar (appear part of the screen) and then disappear.
I hope someone has solution to this.

Categories

Resources