Related
Hey all,
I 've been experimenting with different ROMS, setups etc for my AXON 7 and I with all roms except BadBoyz which is based on the official ZTE rom I had the "no sound" bug on calls. Although workaround is enabling / disabling the speakerphone while on call, I think it is not so convenient (and even with Macrodroid task I still had issues).
So, I just installed LOS again, then the OpenGApps stock package BUT I disabled the Dialer App (#DialerGoogle) on gapps-config.txt thus remaining with the stock LineageOS dialer.
I have been using this setup for two days and I did not experience any call issues.
Just a heads up for a possible bug fix, can you guys / gals test this on another rom and update this topic?
You will find my gapps-config.txt attatched below:
How do you apply fix? To build.prop or gapps before flashing?
borijess said:
How do you apply fix? To build.prop or gapps before flashing?
Click to expand...
Click to collapse
You just do not flash opengapps google phone / dialer app
WizeMan said:
You just do not flash opengapps google phone / dialer app
Click to expand...
Click to collapse
I always flash the micro package that comes with no dialer and I still have the issue.
I have never ever used gapps or any other kind of google bs (well, except for the rest of the OS ) and I have the issue. Mind you that it doesn't seem to happen after having triggered the loudspeaker in any way (music etc.) before making a call. Per boot even, it seems.
Hey guys.
I, and other people for sure, have been using V4A as a go-to equalizer app for some time. However, I've noticed that it suddenly stopped working on any rom I try to install, be it the stock-based roms or custom ones.
In my case, it began with builds from around September 20. and it goes like this:
I either flash an all-in-one v4a zip(with its libraries, which was the only one that worked for me) or try to install drivers through the app itself.
Now the thing is that no matter if I have Magisk(with or without the "Magisk fix") or the LineageOS SU, it either says that the app doesn't have root permission(even though it has and is shown to be allowed in the managers) or it says that it installed the drivers, tells me to reboot and asks for a driver reinstall after that and following reinstalls and reboots.
I've also noticed that even the stock Equalizer apps in AospExtended, LineageOS, Citrus-CAF and stock Moto 7.1.1 force close when a song plays and don't affect the music playback when they actually open and are enabled.
I even thought that they might conflict with V4A so I tried deleting them before installing V4A(without positive results).
In the end, Icreated this thread to see if others are facing the same issue or/and know a solution.
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Lyngze said:
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Click to expand...
Click to collapse
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
LameMonster82 said:
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
Click to expand...
Click to collapse
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Lyngze said:
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Click to expand...
Click to collapse
I did the following:
Reset and begin from scratch....
-Install TWRP latest version if you have not.
-Make backup external of your data, media, etc.
-Wipe everything cach, system, dalvik, data, internal.
-Restart in recovery.
-Download a EUI 19s rom on PC and transfer to your TWRP map on your phone.
-Install trough TWRP the EUI Rom and let it boot.
-Make the minimalist settings, so the rom is installed on your phone.
-After that go to recovery, choose format your phone.
-Restart recovery.
-Transfer the modem firmware 26S, your choise Oreo rom, and Gapps arm 64, 8.1, nano to your phone.
( Advice: infrag AICP unofficial 20032018 version, bugless)
-install those together without reboot in between.
-After that Reboot system.
When making settings in the rom CHOOSE NEW PHONE, DO NOT DOWNLOAD YOUR SETTINGS TROUGH GOOGLE ACCOUNT and do not install other backups.
Then you will have a total clear phone.
Very much work but it helped me with camera and audio problems.
I hope it does for you too.
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Lyngze said:
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Click to expand...
Click to collapse
It is the Bluetooth file of 15S....That's a very long time ago.
I'm not sure with compatibility.
Very much so, however a similar approach might work with say 19S.
But I don't know how to get the .so file without flashing the rom and copying it from the system directory...
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Lyngze said:
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Click to expand...
Click to collapse
Does your bluetooth status says connected (no phone)
in the same post https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635/page2 pn #12 there is bluetooth so file
try that... it works on every EUI version... to verify .. try EUI 16s (Indian ver) and check your bluetooth device
Thank you for pointing that out!
I have tried with a clean install of the entire 15S ROM without any help.
I tried the .so file with my Oreo system, and now I cannot event turn bluetooth on...
Regarding bluetooth status it just says "connected" followed by battery percentage.
I can turn phone audio on or off without problem, but when turned on there is simply no sound in calls...
Hi Guys !
In this early stage we found out how to boot android Q (Erfan GSI) with a vendor/boot combo and some patches.
How to : file : https://mirrors.lolinet.com/firmware/gsi/
1. flash Q vendor/ boot combo. In fact it's latest Mokee vendor + los16 boot : https://androidfilehost.com/?fid=1395089523397937735
2. system.img (a only)
3. flash Permissiver_v2
4. flash FixZygote
5. boot
NOTE :
1. do select your SIM when it pops up the first time ! Calls should work and LTE should show up
2. a reboot messes up your APN and will disable LTE again - making a new APN will fix the LTE
What's working :
* BT working and can be toggled on/off
* NFC seems to be working but can not be toggled OFF - to be tested if it's indeed working when ON
* calls but laggy dialer - volume can be adjusted when calling
* LTE - but a reboot will disable LTE again - restoring to default or making a new APN and reboot will enable LTE again
* file manager works but very laggy sometimes
* stereo speakers
* magisk 19.0 (special one) root ok but manager crashes
What's NOT :
* wifi
* playstore : to be looked into / someone could login others couldn't...
* camera
.....
So for those who want to test, give it a try.
Perhaps some future patches will help on further development.
Thnx @yarecco
Man, is it possible to boot latest build? Or make data and some more works on April build from your guide?
HYPECUT said:
Man, is it possible to boot latest build? Or make data and some more works on April build from your guide?
Click to expand...
Click to collapse
It's not possible to get a fully functioning Android Q until Phh officially supports it into his AOSP builds, or we get a Pie vendor/kernel.
SOME MINOR UPDATE INFO ON BOOTING LATEST GSI 10
Latest GSI don't need additional files (like Permissiver or FixZygote) to boot properly. It's fairly easy to setup your phone.
Some files you might need :
1. vendor : Speedy A7 Vendor_Boot(Baddar RC1.1 kernel) Combo
2. GSI's : take a peek here :
https://sourceforge.net/projects/expressluke-gsis/files/
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
https://github.com/phhusson/treble_experimentations/tags
https://sourceforge.net/projects/developerluke-roms/files/GSIs/
...
3. gapps : https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/ tip : take the pico one otherwise, depending gsi size, you might have to resize system (error70 when gapps are flashed)
4. magisk : https://sourceforge.net/projects/developerluke-roms/files/phh-magisk/
5. button reverse if needed (flash in magisk) : A2017X_swap_button_Module_unity_key
....
Installation : starting from Pie
1. wipe system, vendor, data, cache
2. flash speedy vendor combo
3. flash rom img to system
4. boot phone ( if red light, no worries, just press power to boot ) (also no worries when no OS seems to be installed when trying to boot out of twrp)
5. reboot twrp
6. flash pico gapps (some gsi like PE10 have gapps included) and magisk 20.2 (note : if you get a gapps error70, you'll have to resize system after flashing the img)
7. reboot and enjoy
BUGS :
Have tested some gsi now and only major bug is the NFC.
Depending on the gsi you might have a non working camera, fp too.
After testing some gsi, imo these are worth a try : with working camera, wifi, calls, fp, BT, hotspot
* HAVOC 3.0 : https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/
* PE10 : https://sourceforge.net/projects/expressluke-gsis/files/PixelExperience/Ten/
* AOSP 10.0 v204 : https://github.com/phhusson/treble_experimentations/releases/tag/v204
* EvolutionX 3.3 : https://sourceforge.net/projects/expressluke-gsis/files/EvolutionX/Ten/
Feel free to comment on your personal use.
Ofc GSI are still to improve but worth a try.....till we have our own device specific Q roms
thnx @atakan33
why not using Speedy latest Combo with kernel RC1.2 ?
https://androidfilehost.com/?fid=6006931924117923540
Temporay fix for the CAMERA on LOS17
Just flash this in twrp ( do mount system ) : A2017X_LOS17_GSI_camera_fix
or manual fix :
search system/etc/ld.config.27.txt
change : namespace.vndk.links = system,default to namespace.vndk.links = system,default,runtime
thnx @AndyYan @phhusson
Hi raystef66,
I installed this a couple of hours ago. Installation was a breeze following your guide. I had a play services error but a wipe of data/cache fixed it. I installed the aosp 10 version. Bluetooth seems to not be working for me, it connects but does not play sound thru B/T speaker and WIFI doesn't auto connect after reboots. Everything else seems to work pretty well (I didn't try NFC) but the camera worked for me without flashing anything else. Really nice job, especially for first go round at 10.
Thanks a million.
tlarm said:
Hi raystef66,
I installed this a couple of hours ago. Installation was a breeze following your guide. I had a play services error but a wipe of data/cache fixed it. I installed the aosp 10 version. Bluetooth seems to not be working for me, it connects but does not play sound thru B/T speaker and WIFI doesn't auto connect after reboots. Everything else seems to work pretty well (I didn't try NFC) but the camera worked for me without flashing anything else. Really nice job, especially for first go round at 10.
Thanks a million.
Click to expand...
Click to collapse
can you log on matlog app while connecting and playing media and do adb shell dumpsys media.audio_policy and send it for txt
cant boot
hello
i installed the spuddy combo , gsi from havoc A only after wiping.
but the phone not booting just stack on the logo.
any suggestions?
ty
david
atakan33 said:
can you log on matlog app while connecting and playing media and do adb shell dumpsys media.audio_policy and send it for txt
Click to expand...
Click to collapse
Okay, I think I have the log, it's 7,000+ words long, do you want that posted on here?
tlarm said:
Okay, I think I have the log, it's 7,000+ words long, do you want that posted on here?
Click to expand...
Click to collapse
yes send it for txt file
atakan33 said:
yes send it for txt file
Click to expand...
Click to collapse
hopefully this worked
tlarm said:
hopefully this worked
Click to expand...
Click to collapse
p.s. prob should have noted I had flashed PE10 instead of the asop 10 I tried yesterday but the result is the same.
tlarm said:
hopefully this worked
Click to expand...
Click to collapse
one more log needed we need log from using matlog ( from playstore) .Send log while music playing on bt speaker .
atakan33 said:
one more log needed we need log from using matlog ( from playstore) .Send log while music playing on bt speaker .
Click to expand...
Click to collapse
That was while I was attempting to play on bt speaker. It connected but no sound came from bt speaker, intermittently the sound would come out of the phone speaker but for only a one second and then no sound at all.
tlarm said:
That was while I was attempting to play on bt speaker. It connected but no sound came from bt speaker, intermittently the sound would come out of the phone speaker but for only a one second and then no sound at all.
Click to expand...
Click to collapse
Here's from the matlog app. I had to zip the file because the txt file was to large to upload. This is prob more info than you asked for but wasn't sure how to do only adb shell dumpsys media.audio_policy from the app.
tlarm said:
Here's from the matlog app. I had to zip the file because the txt file was to large to upload. This is prob more info than you asked for but wasn't sure how to do only adb shell dumpsys media.audio_policy from the app.
Click to expand...
Click to collapse
thanks .Thats enough
Apart from unstable NFC in GSIs I've tried (Havoc 3.0 and EvolutionX 3.3) sometimes UI hangs and for now they are not as smooth as LiquidRemix (PIE) which is my favourite GSI (I'm using it till now).
In Evolution I've found option to wake phone by double tap which is something new in GSIs I've tried so far. Also Evolution comes with GApps so you don't have to flash it separately and worry about system partition being too small. Overall it's all going in good direction
^^Stable enough for daily use?
I'm really digging the battery life on android 10 on the 7t. I've had the set up in my sig for well over a year now. It's ok and works well but battery life could be better (esp considering new battery installed earlier this year).
Edit: I'll answer my own question. No. The nfc keeps cycling on/off. I think that's also what's introducing significant lag.
Hopefully this can be resolved to give this device a bit more life.
Nice, I wasn't sure if the Axon 7 will get some Q love.
Will try some of these ROMS.
Thanks OP
Hello everyone, I unlocked my phone's bootloader and flashed Pixel Experience ROM. Everything works fine except earpiece when I'm calling someone. I tested the earpiece with some apps from playstore and realized that the volume is very very low when compared to stock rom. I cleaned the grill, flashed another rom (havoc os) but the issue still persists. Naturally, I googled the issue and there were many more mi phones having this issue. It's said that miui 12 may bring a fix for this. I explored and saw people were editing "Mixer_paths.xml" files for increased volume. Now the problem here is that I think Android 10 has new permission restrictions for /system because I can't edit the file. I'm very new to this phone so if you guys have had this problem can you please help me out on how to solve this? Or you could also recommend some other rom that doesn't have this issue. TIA!
I fixed it by myself. I installed "Root Browser" by Jrummy and went into root/system/vendor/etc/mixer_paths.xml
There are 3-4 mixer files and you have to edit all for it to work.
First change the permissions to rw-rw-rw for all 3-4 files and search for "Volume Control". Change all 84 values to 94. Now change permissions back to what they originally were rw-r--r--
Reboot and enjoy!
Hi, I have a similar problem on my redmi note 9 pro, but my ROM are the original miui12.5.8.0.
I installed Root Browser, but I can't save the changes... Could you help me?I don't know how to change the permission, wen i try to change, i have no permission info.
Thanks