headphone bug in Lineage ROMs. - OnePlus 5T Questions & Answers

I recently installed the Lineage ROM and then the Pixel Xprience Unofficial ROM. I faced this problem that whenever I connected earphones, there was no output via the earphones.Youtube videos even lagged when playing with earphones on but was fine with speakers in the Pixel Xprience ROM.
Did anyone else face this issue?

breakingbot said:
I recently installed the Lineage ROM and then the Pixel Xprience Unofficial ROM. I faced this problem that whenever I connected earphones, there was no output via the earphones.Youtube videos even lagged when playing with earphones on but was fine with speakers in the Pixel Xprience ROM.
Did anyone else face this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/sho...665&p=75020309
Flash 5.1.1 stable OOS firmware and flash in twrp and reboot
Done
Let me kn if it worked

sauaditi said:
https://forum.xda-developers.com/sho...665&p=75020309
Flash 5.1.1 stable OOS firmware and flash in twrp and reboot
Done
Let me kn if it worked
Click to expand...
Click to collapse
I currently am on limited data plan so it will take a while for me to download 5.1.1 stable OOS.
But I observed that the above errors were not present on MoKEE ROM and AOSP Extended ROM or when I went back to OOS Open Beta 9. Tried dirty flashing Lineage over both AOSP Extended and MoKEE but the issue persisted.

Just the firmware is 60mb. Type docs oneplus 5t firmware xda into google. They are flashable zips

Solved.
Flashing the OOS 5.1.1 ROM helped. The earphones problem appears solved in Lineage ROMs. Thankyou for the guidance.

Related

Weird connectivity issue in Marshmallow

Hi, I've been using lolipop (CM12) for quite a while in my N7.
Recently I've upgraded to marshmallow.
But I'm facing two problems.
1. I can not find any other device In SHAREiT send mode.
2. I can not find any other device in KOF 98 bluetooth multiplayer mode.
I've tried CM13 latest stable,beta and pureNexus (AOSP based) marshmallow rom.
This happens in both firmware. Tried pureNexus stock kerner, cm stock kernel and ElementalX kernel.
However this problem doesn't occur if I use Lolipop (CM12 or any other lolipop).
I'm totally clueless as why this is happening.
can any one please help?

Problem with custom ROM (xiaomi mi5s with ViperOS)

Hello guys, i have a anyonning problem.
I have install the ViperOS in my xiaomi mi5s and open gapps with no problem. It's running very well.
But, i can't watch no one video, have freezes all time and no sound. This is happening in all apks, YouTube, instagram, and others.
Someone have the solution for solve this? I don't want back to the MIUI never more :crying:
Regards
Edit: i have already try to install lineageOS too, but the problem is the same. And another OG version too, no sucess
Flash the latest firmware
How can i update my firmware?
Edit: i already have the latest version of the ROM. I need another update to install?
https://github.com/fjtrujy/capricornCNFirmware
Download latest firmware from there and just flash it via twrp. It should solve the problem
And what was the solution? I have the same problem
Flash 7.12.21 because Viper OS is old ROM and it won't probablu work with newer firmwares. But yuo can always try
predragiPredrag said:
Flash 7.12.21 because Viper OS is old ROM and it won't probablu work with newer firmwares. But yuo can always try
Click to expand...
Click to collapse
Thank you

NO Sound NO USB Detection after reverting back to oreo based rom from PE

Hello,
Hope you guys are doing well!
Guys i require some help. Yesterday i have flashed pixel experience latest CAF rom and today I reverted back to Havoc OS Mod but unfortunately i am not getting sound output and not even my device is detecting in PC. Only charges. Also pen drive via OTG is not being detected.
Please help.
Flashing Method of PE:
Pie Firmware
Compatible TWRP
ROM
Reboot
Flashing Method Havoc OS Mod:
Oreo Firmware
Official TWRP
ROM
Reboot
Please help.

Bluetooth in pie custom rom

Hi, everyone. I am facing an issue with bluetooth when I upgrade Resurrection Remix Pie 20190417 to any other rom, I have tried different june's updates like AEX, CRDROID and RR and it always is the same issue: bluetooth seems to work fine but when incall it does not make any ringing sound, it' so weird, the settings are the same in all the roms and bluetooth apk seems to be the same, but it does not work 100% and now the question: anybody has this problem or I'm the only one who has this issue?????
Same here on rr 04.17
I think I have tried all the roms available for Mi A2 Lite: AEX, RR, CrDroid, AICP, AOSiP. How can be possible that bluetooth doesn't work for me in all of them???? Is it possible to rollback bluetooth files somehow?????? I do not know what to do, but what I know is this: problem with bluetooth is related to some update in bluetooth files after may, I mean June's or July's roms do not work but May's ones work perfectly.
kreizas said:
Same here on rr 04.17
Click to expand...
Click to collapse
Hi, do you still have bluetooth issue???? Have you found a solution??? I´m not findind anything
Hi, no solution

Treble bootloop on G960F

Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939

Categories

Resources