[ROM]-[11.0]-[KIEV]-LineageOS-18.1-[UNOFFICIAL]

[roiikka]

@roiikka sorry, what model of earphone are you using? Your saying this is reproducable on stock, but works properly on other phones? Your mentioning AAC a lot, something that's inherently lossy. Viper4android is too. Idk, kinda lost. Maybe post a new logcat, preferably on lineage, so we can see what's happening?

Oh! Was saying that it's lossy on Stock, non-existant on this ROM, Kiev Lineage Unofficial and was giving as much background/reasons as I could in hopes it would be implemented, possibly. My fault.

I use the Sony Wi-C200 earbuds. They have amazing bass response on my S5, lossy-ish on Stock Kiev and it stays no HD, only APTX apparently here on these custom ROMs of the 5G Ace, Moto One. I get the infamous "greyed out HD" switch in dev settings. In Stock for the 5G Ace it has "disable AAC whitelist", you untick it, it says reboot, you do so and bam! HD AAC audio over bluetooth. No SBC needed. And APTX works. You guys want a logcat of that switch? I'd be more than happy to do so just say so and I'll get back on stock real quick. I'm on @SyberHexen s nice port of Havoc OS testi.g right now and same thing as his Lineage OS port but sticking with wired earbuds and seeing what you guys can do with this bluetooth thing.

Been seeing this thing about Sony needing to use LDAP or whatever it's called now, all this "contracts" smorgisporg. But it works on stock OS, like I said. It says "HD AAC", ya.

You guys want a log of that Disable AAC Whitelist switch ? **Standing by** ..

 

[fddm]

It's right here in the specs:

https://www.sony.com/electronics/support/wireless-headphones-bluetooth-headphones/wi-c200/specifications

SBC with AAC fallback. No way to know what's actually happening without a logcat or hardware to test though.

 

[roiikka]

It's right here in the specs:

https://www.sony.com/electronics/support/wireless-headphones-bluetooth-headphones/wi-c200/specifications

SBC with AAC fallback. No way to know what's actually happening without a logcat or hardware to test though.

Ok let me get one of this Whitelist switch for you guys. I really think that that's where it's at on this model of the device. One sec.
Also, while I'm doing this: How do I properly restore a nandroid backup on this thing? A-B slot-wise and such. Backing up via the recommended TWRP here, booted from the command prompt in Windows. Just so I don't have to re-do everything to get back in to Havoc OS again for the time being. Thanks in advance ✌

 

[roiikka]

It's right here in the specs:

https://www.sony.com/electronics/support/wireless-headphones-bluetooth-headphones/wi-c200/specifications

SBC with AAC fallback. No way to know what's actually happening without a logcat or hardware to test though.

Actually never mind about the backup restore. It freezes TWRP, I forgot. I think it's the encryption thing. Got to figure that out later, maybe.

Getting stock back now via Lenovo Rescue and Smart Assistant. Give me like 30 minutes to a hour or so

 

[roiikka]

Ok, here I attached the logcat.
This is me turning on the screen, turning "off" the switch and toggling bluetooth, repeating the process again and then just toggling the switch itself off then on again
And a screenshot of the switch
In Android 10 Stock

EDIT: Trying to send the logcat by attachment. How do I put it up? I tried in a code box but it said it's too long even shortened ..

EDIT 2: See next post

 

[roiikka]

Had to put it in a folder

 

[roiikka]

I can test it out when you guy(s) are done if you decide to take me up on it and integrate it into the ROM

Goodmorning

 

[fddm]

Just had a quick look. It spits out an error for SBC sink that seems to imply that the rom is not built with support. It's even possible Moto didn't pay license fees for it, so it couldn't be enabled, idk. Will need to give it a closer look.

 

[roiikka]

Just had a quick look. It spits out an error for SBC sink that seems to imply that the rom is not built with support. It's even possible Moto didn't pay license fees for it, so it couldn't be enabled, idk. Will need to give it a closer look.

That makes perfect sense. Standing by then, while reverting to wired or APTX, then.

No rush, even. Just wanted to get all that out there best I could. Especially if it's something contract related. Completely understandable. Supply & demand (factory-wise AND dev-wise, mind you)

Thanks again! Take care, guys

 

[joshtb86]

was hoping someone could help - when i flashed the ROM, all of the folders look encrypted and i do not have read or write access so i cannot continue with gapps or magisk

 

[SyberHexen]

was hoping someone could help - when i flashed the ROM, all of the folders look encrypted and i do not have read or write access so i cannot continue with gapps or magisk

You'll have to flash files via otg, external SD or adb sideload.
Currently decryption is a no go for Android 11 roms as we've upgraded the encryption methods

 

[eurovive]

hi just wondering is all functions like nfc, sensors and 5g connection works as well?
Best Regards
Nick

 

[GigaPVP]

I have the moto one 5G ace with xfinity mobile, I installed lineage but it wont connect to service

So basically, here is what happens:

• When on stock android 11, everything works properly
• When lineage are flashed, cellular does not work
• When the phone is first booted up in lineage, cellular connects for 5 seconds (3-5 bars) which is what is supposed to happen in my area, but after 5 seconds, it drops the connection (the cellular icon shows an X next to it)
• For the rest of setup, cellular issues prevail, and I am forced to use Wi-Fi. Choosing to use mobile data just causes it to loop.
• After setup, when going into settings and changing my cellular connection to LTE/UMTS, I get connected to xfinity mobile. I am able to use data, however, calling and Wi-Fi do not work, no 5G, and much lower signal then what I usually get, and it detects as verizon. Changing the APN does not help

So to recap:

• For the first 3-5 seconds of setup, there appears to be a working connection, but it drops
• The ims works as its supposed to (I think) until I change the preferred network setting
• Changing the preferred network setting does yield some success, but no 5G and no calling/texting
• Xfinity mobile runs on verizon, and the sim originally detects itself as a verizon sim, which could be the cause of this problem

So does anyone have a solution for my issue?

 

[roiikka]

 

[rppgaty]

Hi.

When I try to playback some files, I get no audio (in Pulsar and Eleven / Music), though mpv is unaffected when testing with the same files. Other files are entirely unaffected.

 

[shawn.abdushakur]

Sorry, I haven't done this in years; so, please forgive any lack on my part. I flashed TWRP and then Lineage. It wouldn't let me flash Open Gapps saying it was the wrong version. I proceeded anyway assuming I could go back and flash the correct version later. I tried, but Lineage had written its own recovery. I flashed TWRP again as I didn't know how to flash using the Lineage recovery. Now, when I put files on the device, they don't show up in TWRP. I'm not sure where to go from here. Thanks in advance.

 

[roiikka]

I have the moto one 5G ace with xfinity mobile, I installed lineage but it wont connect to service

So basically, here is what happens:

• When on stock android 11, everything works properly
• When lineage are flashed, cellular does not work
• When the phone is first booted up in lineage, cellular connects for 5 seconds (3-5 bars) which is what is supposed to happen in my area, but after 5 seconds, it drops the connection (the cellular icon shows an X next to it)
• For the rest of setup, cellular issues prevail, and I am forced to use Wi-Fi. Choosing to use mobile data just causes it to loop.
• After setup, when going into settings and changing my cellular connection to LTE/UMTS, I get connected to xfinity mobile. I am able to use data, however, calling and Wi-Fi do not work, no 5G, and much lower signal then what I usually get, and it detects as verizon. Changing the APN does not help

So to recap:

• For the first 3-5 seconds of setup, there appears to be a working connection, but it drops
• The ims works as its supposed to (I think) until I change the preferred network setting
• Changing the preferred network setting does yield some success, but no 5G and no calling/texting
• Xfinity mobile runs on verizon, and the sim originally detects itself as a verizon sim, which could be the cause of this problem

So does anyone have a solution for my issue?

Not yet, no.
I have the XFinity one too and it's locked to my buddy's account so I have no way of testing it yet til I pay it off for him. I traded it for stuff with him. Everything works fine on my end over here but until I get it unlocked I can't test it on my TMobile or anything. I just use WiFi calling/texting app ..

 

[roiikka]

Sorry, I haven't done this in years; so, please forgive any lack on my part. I flashed TWRP and then Lineage. It wouldn't let me flash Open Gapps saying it was the wrong version. I proceeded anyway assuming I could go back and flash the correct version later. I tried, but Lineage had written its own recovery. I flashed TWRP again as I didn't know how to flash using the Lineage recovery. Now, when I put files on the device, they don't show up in TWRP. I'm not sure where to go from here. Thanks in advance.

I just don't flash TWRP. I boot it from the PC every time "fastboot boot 'twrp.img'" . Literally when you flash it it flashes to the other partition (partition "B". It starts on "A" by default) so you do it like this;

1. from STOCK, boot into TWRP from unlocked bootloader, flash CopyPartitions.zip & flash LineageOS Unofficial
2. reboot bootloader and boot TWRP from bootloader again
3. flash GApps then Magisk
4. reboot to bootloader again and do "fastboot -w" then tap the "Start" (power button) and it should boot
5. easy

If you mess up you usually have to use the Lenovo Rescue & Smart Assistant from the site to start all over again.
It's pretty easy once you get the hang of it.
I'm coming from my Galaxy S5 so it confused me a bit about the A/B partition thing. You basically have to flash Lineage from TWRP booted onto the "A" partition, then when it reboots to TWRP again it goes to the "B" partition automatically after flashing then you flash everything else from there and then "Start" (power button on bootloader screen) after you wipe data with the "fastboot -w" command.

In TWRP in "Reboot" is A/B slot switching by the way.
Every time I switch slots I reboot/boot TWRP all the way back to TWRP just in case, to be sure.

Hope this helps!

 

[shawn.abdushakur]

I just don't flash TWRP. I boot it from the PC every time "fastboot boot 'twrp.img'" . Literally when you flash it it flashes to the other partition (partition "B". It starts on "A" by default) so you do it like this;

1. from STOCK, boot into TWRP from unlocked bootloader, flash CopyPartitions.zip & flash LineageOS Unofficial
2. reboot bootloader and boot TWRP from bootloader again
3. flash GApps then Magisk
4. reboot to bootloader again and do "fastboot -w" then tap the "Start" (power button) and it should boot
5. easy

If you mess up you usually have to use the Lenovo Rescue & Smart Assistant from the site to start all over again.
It's pretty easy once you get the hang of it.
I'm coming from my Galaxy S5 so it confused me a bit about the A/B partition thing. You basically have to flash Lineage from TWRP booted onto the "A" partition, then when it reboots to TWRP again it goes to the "B" partition automatically after flashing then you flash everything else from there and then "Start" (power button on bootloader screen) after you wipe data with the "fastboot -w" command.

In TWRP in "Reboot" is A/B slot switching by the way.
Every time I switch slots I reboot/boot TWRP all the way back to TWRP just in case, to be sure.

Hope this helps!

When I reboot into the bootloader after step 1, I get a bunch of empty folders with scrambled numbers and letters in the sdcard directory.

 

[shawn.abdushakur]

I just don't flash TWRP. I boot it from the PC every time "fastboot boot 'twrp.img'" . Literally when you flash it it flashes to the other partition (partition "B". It starts on "A" by default) so you do it like this;

1. from STOCK, boot into TWRP from unlocked bootloader, flash CopyPartitions.zip & flash LineageOS Unofficial
2. reboot bootloader and boot TWRP from bootloader again
3. flash GApps then Magisk
4. reboot to bootloader again and do "fastboot -w" then tap the "Start" (power button) and it should boot
5. easy

If you mess up you usually have to use the Lenovo Rescue & Smart Assistant from the site to start all over again.
It's pretty easy once you get the hang of it.
I'm coming from my Galaxy S5 so it confused me a bit about the A/B partition thing. You basically have to flash Lineage from TWRP booted onto the "A" partition, then when it reboots to TWRP again it goes to the "B" partition automatically after flashing then you flash everything else from there and then "Start" (power button on bootloader screen) after you wipe data with the "fastboot -w" command.

In TWRP in "Reboot" is A/B slot switching by the way.
Every time I switch slots I reboot/boot TWRP all the way back to TWRP just in case, to be sure.

Hope this helps!

Is Lineage flashed into slot A and Gapps and Magisk into slot B?