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
Related
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).
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
As we've now finally got lineage os ported to our device as well as a treble support of some sorts, what are the advantages or drawbacks of running either?
Basically I want to drop Samsung and run a aosp ROM on my s8
I can either flash a port like lineage os 16 (which works quite well by the way) or I can go with Hades treble and flash an gsi ROM.
What would be the benefits or drawbacks of either solution?
I hope someone that has now tested both solutions can comment here.
I am assuming here. I think the treble ROMs can to updated with the latest sercurity patches more easily.
I think the los16 port to the s8+ can do the same but from a developers view I don't know how difficult it is to implement each month.
I'm on a treble rom now and always will be due to the fact that the Samsung s8+ patches are coming every 3 to 6 months now after the September sercurity patch.
I need clarification but I think that is the case.
Happy flashing
...
In regard to twrp backups. It can be done in treble. Just don't backup the system image. Click everything else. It works for me.
Is it actually already possible to activate treble on an Samsung S8 and install afterwards a GSI rom like "Pixel Experience"? So far I just found this "Project Treble for Samsung Galaxy S8".
_tnt_ said:
Is it actually already possible to activate treble on an Samsung S8 and install afterwards a GSI rom like "Pixel Experience"? So far I just found this "Project Treble for Samsung Galaxy S8".
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...-device-development/aosp-hadestreble-t3953333
Apologies for cryptic title. My Mi A1 has multiple issues and a patchy update history. I don't know how to narrow this down to a single, simple question. Hope someone can help to make sense of this.
History: Bought new with stock Android One, Oreo. Few months later updated to Android One, Pie (official update). This caused big problems with wifi (connections constantly dropped and VERY slow downloads). Thought about reverting to Oreo, but decided to change to Lineage (which at the time was Oreo). So I downgraded from Android One Pie to Lineage 15 (Oreo). Generally worked OK, but with 3 big problems:
1. No sound during phone calls (I can't hear them, they can't hear me). Found a workaround involving editing the build.prop file (sorry, can't post link), but fix is temporary and needs regular re-boots.
2. Fingerprint sensor not working (no options to set fingerprint).
3. Camera app lost functionality related to dual lens.
I subsequently updated from LOS 15 (Oreo) to LOS 16 (Pie). Issues still there.
I wonder if I have some missing/incompatible vendor firmware components, but I don't really understand how this works. If I download and install, say, a LOS rom, does it contain EVERYTHING my phone needs to work, or do I need to already have some proprietary bits somewhere on the phone?
Is my best bet to start afresh (clean slate) and if so what would you recommend? Any help/insight greatly appreciated!
Hey pal, the Android Pie Firmware has some kind of anti-roll back protection, so when you install a non-pie ROM such as LOS 15 using Pie Firmware you'll have that problems like no-fingerprint, no incall audio, etc. If you install an Oreo Firmware with an Oreo ROM, you'll have fingerprint but no IMEI/Signal (and other problems).
You have 2 options:
1) Update your firmware to the latest Pie version and install a ROM like Pixel Experience or HavocOS (both Pie) and you're set, IMEI, Signal, Audio and Fingerprints will be working OK.
2) Install the latest Pie compilation using MiFlash and leave it stock.
Greetings.
Thanks for prompt reply! Can you spell something out for me please?
Regarding 1) I have already updated to LOS 16, which is Pie. Is that what you meant by "update your firmware to the latest pie"? Or do you mean a stock firmware? If the latter, then I could find a MIUI rom (from en.miui.com) but not Android One.
Regarding 2) Again, by "latest Pie compilation" do you mean the stock rom, like the MIUI mentioned above?
Thanks
Because many users are repeatedly asking this and everyone needs to answer again and again, I write it up here:
This is only true for Oreo and later Custom ROMs! For nougat refer to post #3 by @TheFixItMan (thanks for the tip that users still use nougat )
You can choose between this ways (doing both is wasted time!)
- Have stock Oreo installed before flashing your ROM (for most users not an option because they already have the issue)
- Flash https://github.com/nift4/nift4.github.io/releases/tag/cedric-fp-fix over your existing custom ROM
Yes, it's so easy
do you have the fix for Lineage os 14.1, i tried this ine didn't work for me. :s
Pedro_r said:
do you have the fix for Lineage os 14.1, i tried this ine didn't work for me. :s
Click to expand...
Click to collapse
Download stock nougat firmware and flash just the following two parts
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
For fingerprint to work you need to have a base stock firmware that matches the base of the rom you are using - so in the case of lineage 14.1 that is nougat
The zip file in the op contains oero files so is for people who never bothered flashing oero firmware when they flashed an oero based custom rom
OP should explain what the zip file does (flashes the two files I've mentioned but from oero firmware) to help people understand the issue
TheFixItMan said:
Download stock nougat firmware and flash just the following two parts
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
For fingerprint to work you need to have a base stock firmware that matches the base of the rom you are using - so in the case of lineage 14.1 that is nougat
The zip file in the op contains oero files so is for people who never bothered flashing oero firmware when they flashed an oero based custom rom
OP should explain what the zip file does (flashes the two files I've mentioned but from oero firmware) to help people understand the issue
Click to expand...
Click to collapse
I explain, thanks for the tip
Hi,
I have a motog5 xt1676.
I was on Nougat and I updated to Carbon Rom (after trying with lineage 17, same issue) and i have to choices:
-Doing nothing and people can hear me when i am in speakerphone but the fingerprint doesn't work.
-I patch with the first link for orea then the fingerprint work but people can't hear me when i'm in speakerphone.
Patching with nougat files does nothing...
Is there a way to edit the fix or to make a fix myself avoiding the speaker issue ?
I though to change build.prop or a way to change the way sound is mixed during call but i did'nt test changing all lines.
Do you have an other idea ?
A fix for pie ? ( Carbon is Pie when Pie is cooked too much time =D )
Thank you,
Pierre Archer
The ROM: CARBON-CR-7.0-OPAL-RELEASE-cedric-20200920-0426
piecraxe said:
Hi,
I have a motog5 xt1676.
I was on Nougat and I updated to Carbon Rom (after trying with lineage 17, same issue) and i have to choices:
-Doing nothing and people can hear me when i am in speakerphone but the fingerprint doesn't work.
-I patch with the first link for orea then the fingerprint work but people can't hear me when i'm in speakerphone.
Patching with nougat files does nothing...
Is there a way to edit the fix or to make a fix myself avoiding the speaker issue ?
I though to change build.prop or a way to change the way sound is mixed during call but i did'nt test changing all lines.
Do you have an other idea ?
A fix for pie ? ( Carbon is Pie when Pie is cooked too much time =D )
Thank you,
Pierre Archer
The ROM: CARBON-CR-7.0-OPAL-RELEASE-cedric-20200920-0426
Click to expand...
Click to collapse
As explained
If your stock rom firmware is nougat I suggest updating it to oreo to use pie custom rom
Read my post above (post number three) for full explaination
Any other issues is probably a rom issue - I don't even think carbon rom is actively supported for this device. Use lineageos/Mint os from dev section
TheFixItMan said:
As explained
If your stock rom firmware is nougat I suggest updating it to oreo to use pie custom rom
Read my post above (post number three) for full explaination
Any other issues is probably a rom issue - I don't even think carbon rom is actively supported for this device. Use lineageos/Mint os from dev section
Click to expand...
Click to collapse
Thank you !
Sorry, I midunderstood, I understand better now.
Then installing oreo stock ROM add more "compatibility files" to link with a pie ROM from nougat.
Lineage os is not officially supported on motog5 device, thats why i looked for carbon. But the unofficial lineage os for motog5 look like as frequently updated as "official" carbon rom. I dont know if Carbon updates are caring of hardware details and if they are released without real adaptation. Lineage os pay probably more attention to hardware because motog5 is not officially supported by lineage... Idk...
Thank you,
Pierre Archer
piecraxe said:
Thank you !
Sorry, I midunderstood, I understand better now.
Then installing oreo stock ROM add more "compatibility files" to link with a pie ROM from nougat.
Lineage os is not officially supported on motog5 device, thats why i looked for carbon. But the unofficial lineage os for motog5 look like as frequently updated as "official" carbon rom. I dont know if Carbon updates are caring of hardware details and if they are released without real adaptation. Lineage os pay probably more attention to hardware because motog5 is not officially supported by lineage... Idk...
Thank you,
Pierre Archer
Click to expand...
Click to collapse
Don't be concerned too much about the terms official and unofficial
Nearly all lineageos roms will start off as unofficial - it's users who build it. It's only when they are submitted to lineageos and they add it to their build server it becomes official but its the same device tree.
The only reason the lineage os rom has not been made official is because the camera is not fully working like it is in stock rom so it doesn't meet the criteria to be submitted