Development [ROM][OFFICIAL][lemonadep][12] LineageOS 19

[vangry2020]

Go to the stock dialer, make a call, turn the speakerphone on, turn the speakerphone back off, and hang up the call. Does that fix the issue for you?

I have no issues with the dialer im specifically talking about whats app audio recording messages. Could be app related issue.

 

[EtherealRemnant]

I have no issues with the dialer im specifically talking about whats app audio recording messages. Could be app related issue.

Try it and see if it works. My microphone was messed up system wide until I figured that out on my 9 on StagOS using C.48 base and I'm curious if it works for you guys too. Once I do this, the microphone works fine in everything until I reboot.

 

[vangry2020]

Try it and see if it works. My microphone was messed up system wide until I figured that out on my 9 on StagOS using C.48 base and I'm curious if it works for you guys too. Once I do this, the microphone works fine in everything until I reboot.

Just tried your method unfortunately it didn't fix the issue.

 

[EtherealRemnant]

Just tried your method unfortunately it didn't fix the issue.

Sorry that it didn't work. I have to do that to even be able to control the volume on calls after a reboot, these C.48 ROMs are all buggy when it comes to audio.

 

[NeWONEx]

@LuK1337
Thank you for your efforts and time, I would like to report an issues, after phone fully discharged and turned off. I connect to charger and it stuck in OP boot logo and to make it works I need to force turn it off by pressing on power button and Vol+&Vol-, and once it boot I can see battery level is above 50% already. I guess it is stuck in offline charging mode.

 

[djsubterrain]

Guys, if you want to support bugs you need to provide logs captured when you're trying the action that you have a fault in.

 

[om22]

Audio recordings on whatsapp and telegram are problematic in ROMs based on oos12. The audio is too low.

When this is fixed I will happily switch to lineage again. Currently on OOS 11 again only because of that bug, which is a bummer.

It's in every app that does audio recordings. Recorder app, stock cam filming, gcam filming, WA in-app cam filming, snapchat filming, WA oder Telegram voice messages.

However didn't get any complaints while being in calls that my volume was too low. Seems to be working all right in calls. The other apps, all unusable.

@LuK1337 Can I provide any log that could be helpful?

 

[NeWONEx]

Anyone has phone app crash when you try to copy number?

 

[EugenStanis]

Anyone has phone app crash when you try to copy number?

All fine here

 

[IAMHOBBES]

I've tried installing ADB drivers and even oneplus drivers, but the cmd always gives me "waiting for any device"

 

[Psk.It]

I've tried installing ADB drivers and even oneplus drivers, but the cmd always gives me "waiting for any device"

use the originale cable, chance port

 

[IAMHOBBES]

use the originale cable, chance port

The charger cable that came with the phone?

 

[Psk.It]

The charger cable that came with the phone?

yes the originale red cable

 

[IAMHOBBES]

says the same thing. Are there any specific ADB drivers I need.

 

[Psk.It]

says the same thing. Are there any specific ADB drivers I need.

when you plug the phone to PC, do you hear the sound?
can you identify it on PC devices?


let's start from scrarches:
developer options enabled
usb debug on
oem unlock on

turn off your phone and (disconnected) reboot in fastboot mode
once you see the "fastboot mode" boot you can plug it to PC

if the device is noto recognized, click on in, update deivers, select google adb device

 

[IAMHOBBES]

It pops up on my computer, and I can access the internal storage, but when I'm in the ADB cmd, and type "fastboot devices", nothing shows up, then "fastboot oem unlock" and it always tells me "waiting for any device".

 

[acloh0411]

It pops up on my computer, and I can access the internal storage, but when I'm in the ADB cmd, and type "fastboot devices", nothing shows up, then "fastboot oem unlock" and it always tells me "waiting for any device".

type adb devices in cmd

 

[Psk.It]

It pops up on my computer, and I can access the internal storage, but when I'm in the ADB cmd, and type "fastboot devices", nothing shows up, then "fastboot oem unlock" and it always tells me "waiting for any device".

if you can access memory you are not in fastboot mode, maybe you are in recovery mode

go to reboot menu, select bastboot
It's a complet black screen with just white labels


but overall, if you are not able to reboot in fastboot mode, are you sure you want continue?

 

[IAMHOBBES]

I can get into fastboot mode, but it doesn't change anything.

 

[chilean03n]

I can get into fastboot mode, but it doesn't change anything.

In Device Manager, does the phone show up as Android or Android Phone under Other Devices? If so, you need to download the Google USB driver (Google "Get the Google USB Driver"). Extract it then Google "Manually installing Android ADB USB Driver."