Sound crackling and distortion on the galaxy A5 (2017) - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

Hi. I'm kinda new to xda forums.
When I stream music via youtube, soudcloud, drive, spotify (you got it), the sound is completely ok.
When I play an mp3 however, the sound is distorted.
My AOSP rom is based of lineageos, so I tried my best deleting audiofx via debloat (magisk module) and deleting audio_effects.conf and soundeffects in /system/vendor/lib, yet the problem persists. I'm completely lost.
If anybody knows about this issue or how to fix it, help is appreciated. Thank you!
If you need a logcat, gtfo or anything, I'll be available.

is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.

leo31 said:
is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.
Click to expand...
Click to collapse
But is has to be. I used AOSP on a s3 mini and htc one. Both didn't had this issue. Only this one had.

Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor

CoinKiller said:
Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor
Click to expand...
Click to collapse
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.

Check google app settings and disable ok google now
Also battery life was trash when i installed the rom for myself

TechGuyOnTechIT said:
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.
Click to expand...
Click to collapse
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).

moozer said:
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).
Click to expand...
Click to collapse
I understand that this rom is unnoficial and comes with bugs, but the problem is software-wise, which means it can be fixed, even though we need to dig deeper to the root files. Maybe we can recreate or port the samsung drivers used for audio, deleting all traces of audiofx and other minor fixes just to acomplish this. This may sound unrealistic, impossible and bluffing, but the limits are not only from the rom. Maybe we need custom kernel, or who knows.
Heck, there is little to no talk regarding this issue, so I presume some don't have this issue which could mean only a handful of devices have, because of revisions, idk.
So to sum it up, it could be fixed, but I guess no one has the time and motivation to do it.

Related

getting phone replaced, unsure of what to run

I tried running cm12.1 before. That was fine until phone audio stopped working. Pretty sure its a software issue with the phone since wifi calling worked. I am not sure if I should try another ROM and if I do, which one. I am afraid to run cm12.1 after my audio issue with the last phone. Stability and reliability would be priority. I am disappointed this phone doesn't have stock lolipop. Any suggestions?
4 roms to try.
vandamere said:
I tried running cm12.1 before. That was fine until phone audio stopped working. Pretty sure its a software issue with the phone since wifi calling worked. I am not sure if I should try another ROM and if I do, which one. I am afraid to run cm12.1 after my audio issue with the last phone. Stability and reliability would be priority. I am disappointed this phone doesn't have stock lolipop. Any suggestions?
Click to expand...
Click to collapse
Vandamere,
There are a lot of great roms out there, but if I may be so bold, a really stable, battery friendly, lightweight, Bluetooth friendly rom is SlimLP, it is Slimroms 5.1.1, and is available here:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-slimlp-jfltetmo-t3377731
The Marshmallow roms all have some issues with Bluetooth, but a feature rich rom that is very stable is AOKP MM, which is located here:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-aokp-mm-t3391994
In either event, there really is no "wrong" choice, there are a lot of great roms out there, like @javelinanddart CyanogenMod 13 with the Cake kernel:
http://forum.xda-developers.com/gal...pment/rom-cyanogenmod-13-cake-kernel-t3390721
And an old favorite by @TJSteveMX, the RR:
http://forum.xda-developers.com/gal...ent/rom-resurrection-lollipop-v5-4-5-t3115155
I hope that helps! Have fun! Another thing you could do is read through the posts in the forums for the roms to see what features you like, and see what the general response is from the users who post there.
Like AlaskaLinuxUser said, the only ROM's that seem to have any issues are the 6.0.1 MM ones. That is only with the Bluetooth, from my own trouble scooting it seem the problem is when your Bluetooth device can answer calls and play music. If you are listening to music and get a call the phone will lock up and crash. There is a setting in the Team-OctO MM ROM I am running to disable one of the two under the Bluetooth setting. For example, my LG Tone's only play music, so when I get a call it just rings normal and I pick it up.. if I want. haha.

reasons to upgrade 8.1?

just curious if its worth updating to 8.1 with the January update going around?
Yes, always better to move forward than go backwards...
galaxys said:
Yes, always better to move forward than go backwards...
Click to expand...
Click to collapse
i was asking as the 8.1 december update had caused issues for some people and i was checking to see of they had fixed those issues
No issues here. Actually the screen is much more responsive. Plus latest Security patches, etc...
galaxys said:
No issues here. Actually the screen is much more responsive. Plus latest Security patches, etc...
Click to expand...
Click to collapse
awesome i was worried since the december update caused some issues but its good to see they fixed the responsiveness issue.
8.1 was necessary to get bluetooth to work with my car; I think they did a lot of bluetooth enhancements there.
I have had one unexpected shutdown since 8.1 (I'm on beta so that's over 2 months or so), that's the only downside (and no idea if that was really 8.1 specific).
The December 8.1 update has been great for me. I originally had huge issues using my fingerprint reader in apps, it now works flawlessly every time on 8.1. I have seen some multitouch issues playing Rules Of Survival, but I don't play that much so it's not a huge deal breaker for me.
Lol. I've been holding off updating to 8.1 because
a) I really like the current set up of my phone (rooted, workaround to carrier blocking mobile hotspot, stable OS)
b) I know i'll run into a bunch of hiccups trying to replicate this state mentioned above on 8.1
I do want to try the AR stickers and the supposed camera improvements, so will end up upgrading.... eventually.
8.1 was necessary to get bluetooth to work with my car; I think they did a lot of bluetooth enhancements there.
I have had one unexpected shutdown since 8.1 (I'm on beta so that's over 2 months or so), that's the only downside (and no idea if that was really 8.1 specific).
Click to expand...
Click to collapse
cool ive had some trouble with bluetooth but not alot just somedays it wants to be annoying and the rest of the time its fine.
The December 8.1 update has been great for me. I originally had huge issues using my fingerprint reader in apps, it now works flawlessly every time on 8.1. I have seen some multitouch issues playing Rules Of Survival, but I don't play that much so it's not a huge deal breaker for me.
Click to expand...
Click to collapse
so the fingerprint reader issue went away after using it for a while? have you updated to the january ota?
Youngbloodx said:
Lol. I've been holding off updating to 8.1 because
a) I really like the current set up of my phone (rooted, workaround to carrier blocking mobile hotspot, stable OS)
b) I know i'll run into a bunch of hiccups trying to replicate this state mentioned above on 8.1
I do want to try the AR stickers and the supposed camera improvements, so will end up upgrading.... eventually.
Click to expand...
Click to collapse
lol couldn't agree more but i want the active edge remapping option that just came out and it requires 8.1 sadly
razgriz1234 said:
just curious if its worth updating to 8.1 with the January update going around?
Click to expand...
Click to collapse
Yes! Because all the Kool Kids have.
Only issue I'm having with January 8.1 is same as I was having with December 8.1 which is the screen does not show who's incoming calling for whatever reason I have no idea. I had thought maybe it was because I was unlocked, rooted, etc... but right now I'm not, am fully stock and locked in and it still doesn't show, ugh. Other than that though, the January 8.1 is snappy, the touch responses are definitely better and I swear it almost seems like the blue tint at angles is much less noticeable or better now, but placebo probably.
CJ-Wylde said:
Only issue I'm having with January 8.1 is same as I was having with December 8.1 which is the screen does not show who's incoming calling for whatever reason I have no idea. I had thought maybe it was because I was unlocked, rooted, etc... but right now I'm not, am fully stock and locked in and it still doesn't show, ugh. Other than that though, the January 8.1 is snappy, the touch responses are definitely better and I swear it almost seems like the blue tint at angles is much less noticeable or better now, but placebo probably.
Click to expand...
Click to collapse
That issue is very annoying. I was hoping it would have been fixed with the January update, too. Back in December, I ended up making a macro with Macrodroid to turn the screen on with an incoming call, and it's fixed the problem for now. I think the phone app needs to be updated. I've given feedback through the phone app, but there has been no update for weeks.
The Autofill API has some improvements, and apps like 1Password are reliably filling in most apps and webpages (tested the latter with Chrome). This has been one of the reasons (for me at least) to come back to Android after a fairly long hiatus.
AR stickers are also cool.
And who doesn't like bleeding edge?
It's also been pretty stable.
8.1 is ONLY good if you need HD voice other than that it's buggier, finger print scanner is worse, lock screen touch response issues are more apparent for A LOT of people. So much so Google is aware of the issues. Also 8.0 battery life is WAY better than 8.1.
Sent from my Pixel 2 XL using Tapatalk

No sound on earpiece while in call, speakerphone works fine...

-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. ? I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
quan2032 said:
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
Click to expand...
Click to collapse
Mine is I can't hear them but they can bear me. What the hell is going on. Hahaha! If all else fails I'm going to get a new top receiver speaker put in at a shop close by. It does appear that many Xiaomi devices have had sound issues and have had speakers replaced. If you search on YouTube Xiaomi no sound on call or speaker replacement you'll see MANY videos on "how to." Quite a few videos specifically for mi mix 2. They should let us upgrade at least to the mix 2s for free.
I'll try 3.0 havoc but I've flashed around on Android 10 and 9 and problem hasn't gone away. Still zero sound on my end on calls but all speakers work doing anything else. Appreciate the recommendation. Thanks for commenting. Later today's ill flash 3.0 and see what's up. Then I may pull a few kernels from other roms and switch em out with whatever I'm on and see if I can't get something going that way.
I will also post a log of me on the phone talking and maybe someone can see something that's wrong... Hope so anyway..
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Sinchanwa said:
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Click to expand...
Click to collapse
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
flash713 said:
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey there just want to know is your problem solved?
Sinchanwa said:
Hey there just want to know is your problem solved?
Click to expand...
Click to collapse
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
flash713 said:
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Sinchanwa said:
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Click to expand...
Click to collapse
I never thought that my sound issue was related to havoc in any way I am almost positive its a broken speaker. Looks as though that type of thing happens often on this device and other xiaomi devices. Google search receiver speaker replacement really fast and watch how many things show up about it. Its all over. I'm going to get a replacement. Using my moto g7 power rn as my main phone so I can have conversations and hear on my end. I always clean flash everything I flash. I never fail to wipe data, system, cache, delik cache on any install.
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
r_nally said:
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
Click to expand...
Click to collapse
This is just too strange. So maybe my issue does have something to do with installing Havoc 3.1. That was the first rom I flashed after I unlocked my bootloader and speaker worked fine on latest MIUI Global rom before... I wonder if it's possible to break a speaker due to a rom installation? I've never heard of that before. I thought surely it was just the rom and was a bug or a firmware problem. I flashed all kinda firmwares afterwards in latest twrp and also sideloaded a few to see if maybe something wasn't right with recovery and like you say it did not change anything at all. I still get zero sound on my receiver speaker while on a call.
I'm going to try a few more things and see if it does anything. If I find a fix or something that allows me to hear anything at all out of my end on receiver speaker I'll most definitely add it here in a post and to the op. Seems like there would be more people than us if it had something to do with Havoc... Idk. Appreciate your information. I hope we can get this fixed soon. I never even hardly used my phone when the speaker worked. ? I bought it used off swappa and about two weeks later unlocked and flashed Havoc and no sound during calls on my end.
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
r_nally said:
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
Click to expand...
Click to collapse
I used an app off Google play store to test speakers and my receiver speaker works but refuses to work during a call on my end. It did have sound come through loud and clear when I ran the tests I did when it first happened. I've flashed using magisk stable, canary, formatted data, used different firmwares, everything know to mankind and searched around and tried several things online and nothing. I've been trying to boot the Android 10 GSIs to see if that makes any difference but have had no luck using the same vendor and boot everyone used on pie GSIs so I snatched some from different roms and still no luck on GSIs that are Android 10. Lemme find link to test all i used and I'll return and post a link. Brb
Sent from my OnePlus5 using XDA Labs
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
r_nally said:
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
Click to expand...
Click to collapse
I doubt it and I did make a post there a while back about it. There are many others there ok that thread who reported sound issues and I wanted to confirm what for sure caused it before I put the blame all on a rom... The speakers on this device have had issues MANY times based on all the reports i read all over the internet. But if I can confirm exactly what it is I'll dang sure be very open about it online and let the world know in hopes that if it was something I did maybe someone else won't and I can somehow prevent it. But I did make a post there when it occurred. Search my username on the thread and you'll see it.
When you set a ringtone does sound come from your top speaker? On my device it does. Just curious. See if you can hear any sound selecting different ringtones. ?
Sent from my Mi MIX 2 using XDA Labs
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
I'm going to clean flash now after I do a backup and I'll install havoc and NanoDroid which eliminates Googles hold on all our devices. Once I get all setup I'll run some tests and see if maybe this solves it.
NanoDroid: https://forum.xda-developers.com/showthread.php?t=3584928
[MODULE/SYSTEM] NanoDroid 22.5.1.20200102 (microG, pseudo-debloat, F-Droid + apps)
No difference
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
On my other device , Moto G7 Power see the 8th post here: https://forum.xda-developers.com/g7-power/development/rom-havoc-os-3-2-t4058987
This time I haven't had it occur on G7 Power but when I saw that guys post I had a flash back. :/
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread.
[edit 17Jul20]
OK, it happened again today. No sound from top speaker when making or receiving calls. Had to switch to speaker phone. Then I cleared the 'Contact and dialer' app cache memory. (And for good measure the other caller and dailer apps also. TOP SPEAKER CAME ALIVE AGAIN!! So I am pretty sure its a bug/memory issue.
What I did: Long press the dailer icon - tap on App info - press 'Clear data' icon and select to clear chache memory.
ToBadX2 said:
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread. - Christo
Click to expand...
Click to collapse
What's crazy is this happened on my device just after I wiped data, system cache and flashed HAVOC which was the first rom that I flashed when I got this device. And I flashed my firmware and it did nothing at all. I'm getting a another speaker from eBay this week. They're only like $3 US. Gonna replace it and see what happens. ?

Stock ROM Vs Custom

This question is probably repetitive but I'm really curious if the stock ROM on the Samsung A70 is better than the custom roms?
I've had this phone for a couple months and I have stuck with the stock ROM and now I want to try some custom ROM maybe lineage. So how is the performance of the phone on other ROMs?
I've been running LOS 17.1 for a few weeks now. Tried it with gapps, and now without gapps.
I think that it is purely a matter of personal opinion, and nobody can tell you how much you will like any option. But, for me, I am really liking LOS without gapps. My battery life is drastically improved. I mean that it is easily lasting 2 full days between charges, as opposed to one day and my usage hasn't changed.
But there are compromises. For example, a gappless system isn't always giving notifactions immediately. I have no option at all to add fingerprints (not bothered though, never used them anyway). Downloading apps isn't always as easy as just opening play store.
Sometimes, especially after a call, my screen is black but is on. I have to manually turn screen off, then on again. And then there is a lag of unlocking the screen, just very unresponsive for a few seconds. That's the only time it happens.
The only way that you will know is to try it and compare for yourself to see which you prefer, and if the tradeoffs are worth it
I've been running LOS 17.1 for a few weeks now. Tried it with gapps, and now without gapps.
I think that it is purely a matter of personal opinion, and nobody can tell you how much you will like any option. But, for me, I am really liking LOS without gapps. My battery life is drastically improved. I mean that it is easily lasting 2 full days between charges, as opposed to one day and my usage hasn't changed.
But there are compromises. For example, a gappless system isn't always giving notifactions immediately. I have no option at all to add fingerprints (not bothered though, never used them anyway). Downloading apps isn't always as easy as just opening play store.
Sometimes, especially after a call, my screen is black but is on. I have to manually turn screen off, then on again. And then there is a lag of unlocking the screen, just very unresponsive for a few seconds. That's the only time it happens.
The only way that you will know is to try it and compare for yourself to see which you prefer, and if the tradeoffs are worth it
Click to expand...
Click to collapse
Thanks for the heads up! I have LOS 17.1 on my Galaxy Note 5 and it has been great! My A70 is my primary phone, so I'll have to be sure of what I'm doing. Are there any other trade-offs? thanks
---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------
Bloda said:
This question is probably repetitive but I'm really curious if the stock ROM on the Samsung A70 is better than the custom roms?
I've had this phone for a couple months and I have stuck with the stock ROM and now I want to try some custom ROM maybe lineage. So how is the performance of the phone on other ROMs?
Click to expand...
Click to collapse
Lineage OS 17.1 is great, but as the other guy said, there are a few trade-offs. I currently use the Stock ROM on my A70, it's great.
pengwhen said:
Thanks for the heads up! I have LOS 17.1 on my Galaxy Note 5 and it has been great! My A70 is my primary phone, so I'll have to be sure of what I'm doing. Are there any other trade-offs? thanks
Click to expand...
Click to collapse
The camera only reports as 8MP. But again, this doesn't matter to me as I'm not a photographer.
TWRP can't always decrypt files stored in System, but I don't mess with the system files anyway. Some have this issue, some don't. Not sure why, it seems to be a random glitch.
My phone is my only phone. Unlocking bootloader, flashing TWRP recovery and then the ROM was worrying, but went very smoothly. Switching from stock to LOS was like having a completely different phone in my hands. It felt brand new and I had to go through setting it up and learning how to get the best from it again.
I honestly think that the only way to know if it will suit you is to give it a try as we all use our devices differently. It is easy enough to go back to stock ROM using Odin if you don't like it. Just make sure that you have everything backed up first.

Distorted & Crackling audio from speaker - LineageOS OFFICIAL ROM [Redmi Note 8]

Hi! I'm new here and to the XDA community in general, so apologies if this isn't the perfect place to post it here, or if this should've been posted in the ROM thread- I'll probably post in both, anyways :b
I installed the latest firmware of my phone, the Xiaomi Redmi Note 8, and flashed both the latest Lineage Recovery and LOS Rom, as of March 28th 2021, so the latest version seems to be March 15.
Everything seems to be working fine, except for ONE thing- and that is the speaker. The speaker sounds HORRID right now. Putting it at a max volume makes the sound so crackly and distorted. Especially when listening to music- voices sound fine, but the instrumental is so blown up. The best analogy would be if all music sounded like earrape. That's what music on my phone sounds like right now.
I've been researching and researching, and this issue with audio seems to be a common problem with LineageOS users. However, as of 2021, it seems like no one has found a fix? I've tried disabling audiofx, messing with the system, EVERYTHING AND ANYTHING that I could find online. And it still sounds terrible!
The only solution according to people was to fully reset your phone through the recovery, which I kind of doubt will fix things in my situation, plus it would be a pain to move all the files from this phone to the new reformat. I wanted to explore my options and if there was any- ANY fix. It's seriouslyy bugging me.
I hope that the problem is easily solved and I can have normal sounding music back again! (I've had normal music on an older build of LOS, It was just this time that really triggered this awful bug)
bump? (is bumping allowed)
It seems the RN8 forums are seeing very little traffic lately.
The only thing that occurs to me is changing the audio processor; do you have Magisk?
pnin said:
It seems the RN8 forums are seeing very little traffic lately.
The only thing that occurs to me is changing the audio processor; do you have Magisk?
Click to expand...
Click to collapse
Aw. That sucks.
Unfortunately no, I don't have this phone rooted as I don't really need rooting for a particular reason. Some people have pointed this audio issue on AudioFX, some people have said it only got fixed by reflashing their rom, which kinda sucks as I'd basically have to do the whole setup all over again
Will changing the audio processor fix the speakers? How do I do that?
redandvidya said:
Will changing the audio processor fix the speakers? How do I do that?
Click to expand...
Click to collapse
I know how frustrating it is to try to solve a problem by getting into another so I totally understand your being wary -- I suggest you educate yourself thoroughly on the caveats implied.
I can't guarantee anything (plus my 2nd RN8 is still awaiting unlocking) but I am a fan of Viper4Android -- available as standalone but much easier to setup as a Magisk module, hence my question.
Usually, the built-in processor is disabled during V4A setup and while this can be tricky at times, I have nothing but praise for V4A (I get it in all devices I have ever owned).
pnin said:
I know how frustrating it is to try to solve a problem by getting into another so I totally understand your being wary -- I suggest you educate yourself thoroughly on the caveats implied.
I can't guarantee anything (plus my 2nd RN8 is still awaiting unlocking) but I am a fan of Viper4Android -- available as standalone but much easier to setup as a Magisk module, hence my question.
Usually, the built-in processor is disabled during V4A setup and while this can be tricky at times, I have nothing but praise for V4A (I get it in all devices I have ever owned).
Click to expand...
Click to collapse
Okay so, after some research and testing, I am 99% sure that the problem is with AudioFX. I found out how to mess with the confusing UI and was able to drag the stuff up and down, and it CONSIDERABLY made an impact. The bug was still there though, no matter what settings I dragged up and down I'd still have terrible audio. BUT switching between the presets made an impact on the audio. Hundo P. I lowered the bass so much that for like 5 minutes I had okay (bassless) audio, then it came back. So it is a software issue.
Would factory resetting and reflashing the rom fix it? I dunno. I really don't have a need or want for rooting my phone to fix this bug as I am content with default audio apps. I might consider it though, especially because I used a "volume booster" app I found on the play store a few times.
But yes, I am just asking if formatting everything on the phone and reflashing the rom would fix it.
redandvidya said:
Hi! I'm new here and to the XDA community in general, so apologies if this isn't the perfect place to post it here, or if this should've been posted in the ROM thread- I'll probably post in both, anyways :b
I installed the latest firmware of my phone, the Xiaomi Redmi Note 8, and flashed both the latest Lineage Recovery and LOS Rom, as of March 28th 2021, so the latest version seems to be March 15.
Everything seems to be working fine, except for ONE thing- and that is the speaker. The speaker sounds HORRID right now. Putting it at a max volume makes the sound so crackly and distorted. Especially when listening to music- voices sound fine, but the instrumental is so blown up. The best analogy would be if all music sounded like earrape. That's what music on my phone sounds like right now.
I've been researching and researching, and this issue with audio seems to be a common problem with LineageOS users. However, as of 2021, it seems like no one has found a fix? I've tried disabling audiofx, messing with the system, EVERYTHING AND ANYTHING that I could find online. And it still sounds terrible!
The only solution according to people was to fully reset your phone through the recovery, which I kind of doubt will fix things in my situation, plus it would be a pain to move all the files from this phone to the new reformat. I wanted to explore my options and if there was any- ANY fix. It's seriouslyy bugging me.
I hope that the problem is easily solved and I can have normal sounding music back again! (I've had normal music on an older build of LOS, It was just this time that really triggered this awful bug)
Click to expand...
Click to collapse
try force stop and freez "AudioFX"
you can also delete it with recovery file manager
loopypalm said:
try force stop and freez "AudioFX"
you can also delete it with recovery file manager
Click to expand...
Click to collapse
I disabled the AudioFX app, that did nothing. How would deleting it make it any better? Please elaborate, bc if this could be fixed by just deleting AudioFX that'd be great
redandvidya said:
I disabled the AudioFX app, that did nothing. How would deleting it make it any better? Please elaborate, bc if this could be fixed by just deleting AudioFX that'd be great
Click to expand...
Click to collapse
i said "delete" because i was not sure you can disable it
but since you disable it and that fix nothing i suggest doing a full backup (boot/dtbo/system/vendor/data/persist)
(i don't think your current recovery will do it, use OrangeFox)
try another rom (RRos) and check the sound
if the problem still there that means it's a hardware problem
loopypalm said:
i said "delete" because i was not sure you can disable it
but since you disable it and that fix nothing i suggest doing a full backup (boot/dtbo/system/vendor/data/persist)
(i don't think your current recovery will do it, use OrangeFox)
try another rom (RRos) and check the sound
if the problem still there that means it's a hardware problem
Click to expand...
Click to collapse
Welp! After hours and hours of what is essentially torture, it's sadly not a software problem This goddamn terrible issue exists on all the multiple roms I've tried flashing and reflashing. Pixel Experience, RR, I EVEN FLASHED THE ORIGINAL MIUI ON IT AND ITS STILL BROKEN. I am so tired!
So now there's only two possible culprits:
1. Hardware problem - I really really don't want it to be this one, with the state of the pandemic I can't easily go to a repair shop right now, and dealing with this broken speaker sucks! It's even worse once I realized that it could just be a dust issue.
When I blow using my mouth into the speaker, I get normal sound for 2 seconds until the crappy earkiller terrible music is back. So it's definitely fixable!! Some way. The only solution I have seen so far is that you take the phone apart and wipe the "grill" of the speaker with a Q-Tip. Another idea in my head is to use compressed air and blow it into the grills so that I don't have to take it apart. However, I am doubting the long term use of this solution, I'm not sure if it'll work.
I even goddamned flashed MI UI back on my phone even though I extremely hate it JUST to use the clean speaker feature, which didn't work. The only thing that works for a SECOND is blowing with my mouth into the speaker.
2. Firmware problem - To be fair, the terrible music only started happening shortly after I flashed the latest firmware (v.12.0.4) + latest build of LineageOS 17.1 (March 15) + latest LOS Recovery, same date.
I have used this phone for several months now, (since May 2020?) and for 95% of the time have worn a case. I have a tempered glass screen protector, and I'm not sure how I could've possibly dropped my phone that could have broken the speaker. However, it has been in some quite dusty places, so that's the ONLY thing that could make it a hardware problem- but why now? Why now only when I flash a new firmware? Why not a week before I flashed it? Or a day or two? So that's also sus as heck.
So here are the solutions, from best to absolute worst for me:
1. It is simply a firmware problem. I don't know if I'm allowed to do this, because I really don't want any potential of bricking this phone, but I'd simply "flash" an older version that doesn't have this bug (specifically, v12.0.3, but if that one has this bug too I am going to) Please let me know if I could do this though, I don't wanna brick this phone. Alternatively I could root it and edit the file that it "changed" that caused this, however because I don't know which file causes the bass to sound this terrible, that could be another challenge in it of itself.
2. It is simply a small dust problem. I can buy a can of compressed air with a straw online, and clean out those speakers, and it will be fixed permanently.
3. It is a hardware problem that can only be fixed by taking apart the phone and cleaning the dust with a Q Tip. This is the one I hate the most as it requires me to go to a store which is impossible during the pandemic. I use my speaker for a LOT of things, so I can't handle not having one right now.
Alternatively, an option that I could use is switching to Viper and tweaking it so that the BASS (which seems to be the main culprit right now for the broken audio, as voices in songs mostly sound fine?) is low as heck. That might ruin the sound of the speaker, but it's a crappy workaround that could just work for now.
This thread about the Redmi Note 7 Pro could give some final hope for me. It described "bad audio distortion", however it is about when you're RECORDING VIDEO, not SPEAKERS. However, it is the closest I have to what I have right now. All the other threads I found on google seemed to only happen in certain apps, which is NOT the audio that I have.
Still, if this theory could prove that all I need to do to fix this overblown bass / distorted audio is to edit a config file in the vendor firmware, it'd be golden!
I really just need help fixing this phone's speakers omg ;-;
Bump, anyone know if flashing older firmware is okay and won't brick my phone? Would compressed air damage my phone? I really don't know what to do at this point.
If you're willing to risk it, my bet would be on (very careful) disassembly and cleaning the speaker with a photography compressed air can/pump. Might be worth having professionals do it, though.

Categories

Resources