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
Related
So I'd been using a replacement Z ultra for a few days after cracking my screen and receiving what I'd assume was a refurb. Now no media will play, all forms of applications that can source media from all different paces can't play anything. EG facebook videos throw up an error, walkman app when selecting a song will skip each song on an album one at a time, yutube videos "There as an error"
My question is, has anyone encountered this before, or how would I go about trying to diagnose it, I've already factory restored along with flashing a CE firmware, along with restoring to my first TA backup., to no avail.
Thanks.
This is happening to me too I messed with the media xml
Hope I can fix this root and locked bootloader my Xperia is mute
No more tinkering for me pure stock
RealityFails said:
This is happening to me too I messed with the media xml
Click to expand...
Click to collapse
That's what's really odd, surely restoring to factory, flashing a default ftf or anything else should fix it.
StonedPanda said:
That's what's really odd, surely restoring to factory, flashing a default ftf or anything else should fix it.
Click to expand...
Click to collapse
I'm pure stock just root, I went to copy the media_paths. xml and my sound is all gone so we're both facing the same issue.
I made a copy of the default xml but when I put it back, still no sound, YouTube error and songs skipping really fast.
Hey bro I fixed it myself.
Here is how.
If you need the original mixer_paths.xml I can provide that. You must delete the file you want to replace and not overwrite it.
So in my case I wanted the volume increase what I did was download it, overwrite my original and reboot and had no sound. You must delete the current mixer_paths.xml completely off your phone and then install the custom one.
So again to regain sound
Navigate to device, system, etc and delete the mixer_paths.xml before placing the new one DO NOT OVERWRITE
Have you deleted the file named platform.xml in system/etc?
Please double check it and make sure the permission of that file is 644.
someone found a solution?same problem here :crying:
Makidonu said:
someone found a solution?same problem here :crying:
Click to expand...
Click to collapse
Hello.
Have you resolved sound and media problems for your C6833?
I have same issue and I'm stuck. I don't know what to do exactly.
Thank you.
I posted a solusolution
Good morning/afternoon/evening !
I own an Alcatel One Touch Idol 3 5.5", and I installed CM 12.1 on it. I have been experiencing random reboots for a little time, usually about 3 or 4 an hour, so I decided to ask for some help there. I managed to get the logs just before the phone shuts down (btw it is not a soft reboot), they are in the pastebin lower. There is another pastebin with the modified build.prop (Pimp My Rom, L Speed). I tried to disable (freeze) some apps (Greenify, I even tried to uninstall Xposed) that could be the cause of this, but it didn't work :-/ I also tried to comment some lines in the build.prop that I added manually or that some apps added, but it did'nt work neither.
If you need any other file/list/whatever, just ask ^^
Thanks a lot !
Arlialcatel
Logs : pasted[dot]co[slash]af56d930
Build.prop : pasted[dot]co[slash]78cbcb51
(I cannot post links :-/ )
Hello everyone, the other day I decided, after 3 years of stock ROM (5.1.1), to change ROM on my Note 3 Neo (N7505). I installed TWRP, I downloaded a build of Lineage 14.1 and installed it. But stupidly I didn't read the list of things that don't work, such as the camera and the dial app. So I decided to return temporarily to the stock ROM. Later I found a Cyanogen build compatible with my N7505 without any particular problems, so I installed it. No problems here. But when i had a glance at the "memory" section of the settings, I found that the space occupied by the system was equal to 4.6 GB. A little unusual. Using the ES file manager I found two folders, a /system that weighs 400 mega (probably the one where is Cyanogen) and a /sys with 4 GB (with inside 200.000 files and 60.000 subfolders!). I think the problem is the folder /sys, probably when I changed rom I didn't wiped something, and there are still the files of the Lineage and the stock, stored in this folder. Now I have 4 gigabytes of useless files, and what I would like to do is delete everything and then install the cyanogen. But among the TWRP wipes there isn't /sys, only /system; with the root permissions I can't delete it, and I also tried with ADB, but it's a mess. It's like 4 days that I look on the net how to fix it, but I didn't find anything that could help me. I thought about making a cut of the / sys files and past 'em in / system and then wipe everything from TWRP, but I don't know how ADB works and I wouldn't mess it up. If anyone has better ideas I'll really appreciate it, thank you very much in advance.
Also, sorry for bad English but is not my native language.
The earpiece does not work during calls, speaker mode does work, headphones also do work.
I made following changes to the build.prop file,
From:
ro.vendor.audio.sdk.fluencetype=fluence
To:
ro.vendor.audio.sdk.fluencetype=none
Gave 644 permission to build.prop after the changes. That fixed the issue for the first time but issue appeared and not the change to build.prop does not work. I am on Pixel Experience Pie rom, I have tried flashing RR Oreo and Syberia Pie rom but the issue persists. Any other changes that can help to fix this issue ?
There are some threads where soundabout app is mentioned, but that is not available on Playstore, tried installing it using apk but that also did not help
Please help folks !
Good day.
Just want to point out that it's not my first time rooting a phone and playing with settings. But of course I could've done something dumb so please be patient.
So our device has some GPS issues. Mainly is that it detects some satellites but is unable to get a strong signal and establish a fix.
I tried crDroid 7.17 (Android 11) and VoltageOS 1.6 (Android 12.1). On both I had the issue.
Then I decided to try to tweak /vendor/etc/gps.conf. I made a backup of the file and edited it a bit. As a result phone stopped even seeing satellites. And the problem didn't disappear after I restored the file to original state. I'm a bit confused how a simple operation like this could cause such problems?
I tried editing and restoring file via Total Commander and Root Explorer apps. I also tried Magisk Global Optimized GPS File Replacer. Nothing worked. The only solution is to reinstall ROM.
Is something different on newer ROMS? On older ones I had no issues editing gps.conf or hosts files.
Dirty flash your rom or flash the right vendor image
Could also be HW issue. Antennas last almost nothing.