[Q] Editing build.prop breaks camera? - ZTE Axon 7 Questions & Answers

Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks

bluenote73 said:
Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks
Click to expand...
Click to collapse
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.

amphi66 said:
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.
Click to expand...
Click to collapse
Thanks. That worked for me. I don't know wtf is the problem with that build.prop editor I was using, but it worked flawlessly through the last 2 updates, but suddenly after B25 just seems to cause this problem right away.

Related

Fixes for everyone

Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
First of all, all I need from you to have is a root browser app and some simple knowledge about editing files in there, changing permissions, moving stuff around, and all that stuff. I personally use "root browser" app. It's up to you. Whatever app you're comfortable with is fine.
1. The annoying "AT&T address book subscription" or whatever they call it pop-up window that pops in your face every time you open your contacts.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, not anymore [emoji16] thanks to @NunHugger for pointing that out for us in one of his posts on the alliance ROM thread (and I happened to be an OCD. I take a screen shot of every useful post that I think will help me in the future and throw it in my SD card)
Using your root browser app navigate to system/csc/feature.xml and find this
<CscFeature_Contact_EnableAAB>true<
and change the "true" to false. Save, reboot, and enjoy.
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
3. If you flash an international based ROM, you may lose your AT&T 4GLTE signal icon and end up with only G4 in the status bar. Even though it doesn't mean you don't have LTE, but hell it's so annoying to look at.
That's a very easy one. From your root browser, navigate to system/build.prop and find this
ro.product.name=hltexx
And replace the "xx" with "att". Save, reboot, and enjoy.
Also, I don't know who figured it out first. it's an old one (since the note 2 days)
4. Losing screen rotation functionality.
Due to "debloating" especially for those who have just gotten root (thanks to @geohot) and they're debloating the hell out of their phones. LOL
Some problems might occur thanks to samsung for linking so many of their bloat to the device's main functions. I ran into this problem and it drove me crazy. Thanks to the power of Google search and this gentleman here @phyowaiummg for posting the solution for it. It's caused by removing samsung hub with titanium. Titanium removes this
"libgnustl_shared.so"
file (that apparently controls the rotation function on our phone) from system/lib when you uninstall samsung hub with it. Just find that file in another ROM zip file. Extract it and throw it into your system/lib. Change permissions to rw-r-r and reboot.
Do NOT delete. Just freeze with titanium. It's not worth it. You're only going to save 150+ MB by deleting all the bloat. IF you can't help it, then use "root app delete" app from play store and delete the bloat.
5. HOW TO FULL UNROOT AFTER TOWELROOT (how I did it. It worked for me):
First you need to be on stock ROM (assuming you have a backup of it).
a. Un-install recovery from SS then Un-install the app-SS- itself.
b. Open up your "root browser". On the very first page, just keep scrolling down and find "SS" folder. Delete that.
C. From supersu app, go to settings/full unroot and press that and continue accepting all the windows that pop up. (Do NOT reboot yet).
d. From root browser, navigate to system/app and look for the supersu apk and see if it's there. If so, delete it. If it's not there, then you may find it in system/prev-app or data/app. Delete the hell out of it wherever you find it.
f. From root browser, navigate to system/xbin and find busybox and su and delete both.
d. Now reboot and cross your fingers it works. It worked for me.
Let me know if it works for you as well, please!
6. If you don't like the 480 DPI on your phone and think that your apps are too big. Or you don't want to use any apps/xposed modules (or for some reason those modules didn't work for you) to change that, then there is a method for you to do so by only a small edit in your build.prop (Thanks to @UK2K for bringing it up to this thread. Make sure to smack his "like" button wherever you find his posts ) . Some folks say that 375 DPI is the perfect way to go.
You can do that by just opening your "root browser" app. Navigate to system/build.prop then find
ro.sf.lcd_density=480
and change 480 to 375, save, reboot, and, as always, enjoy!
If you would like to save the original just put a "#" at the beginning and make it look like this:
#ro.sf.lcd_density=480
and just create a new one by typing it like this:
ro.sf.lcd_density=375
then, save and reboot.
7. This is an awesome addition by @hp79. Make sure to smack his "like" button.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"
8. For those who are having GPS not locking problems, I've found this fix on XDA YouTube channel. What it is, is just download the file that has your country's/region's name from this website and throw it into your system/etc then reset your permissions to rw-r-r and reboot. It worked like a boss for me and I hope that for you, too.
Just follow what this video says http://youtu.be/oU67XHD0kj4
-Another fix for the GPS, just in case the above didn't work for you, found by @39FarmallM (thank you, sir):
I am going to quote his post for you guys:
"http://www.rom-central.com/showthrea...te-3-Rom-N9005 <==[This is where he found his fixes]
[SOLUTION] GPS Fix - When moving back to Note 3 Rom {N9005}
Hi guys
A lot of users have GPS problems when they move back to a NOTE 3 ROM after flashing a S5 PORT ROM.
Here is a possible fix. Tested only on N9005
Solution 1
On your dialer type in this USSD *#0011#
Press menu key > press back
Press menu key > press key input > Q
Press menu key > press key input > 0000
Wait for a few seconds and the screen options will change
*MAIN MENU comes up
*Tap [2] UE SETTING & INFO
*Tap [1] SETTING
*Tap [2] SYSTEM
Press om UMTS (Not there)
Press on Common (Not there)
*Press on [3] NV Rebuild
Press on NV Rebuild (Just once)
*[3] ALL
Wait for 30 seconds and then shutdown your phone
Power On phone
GPS should work fine now
Recommend to use GPS STATUS app to reset and download AGPS Data
Solution 2
Assuming you are on a S5 Port ROM, make sure GPS is enabled
Boot into recovery and without wiping anything "dirty" flash a note 3 rom and reboot
There will be a lot of force closes once reboot is complete. Reboot back into recovery
Wipe data and reboot into the Rom again. There may be a few force closes. Reboot back into recovery
Wipe 3 times (data, cache, system, boot)
I recommend latest Philz Recovery (use intall new rom option to wipe) <== [This is for those who have unlocked bootloaders and are able to flash a custom recovery. It still works with Safestrap, just in case you wonder]
Restore or install your desired Note 3 rom
GPS should work fine
Thanks"
-A Third fix by @rogerinnyc (thank you, sir). And since he has attached a zip file for you guys then I will just give you the link to his post and you do the rest
Hope that helps some of you guys. If anyone has a fix that I don't know about, please just pm me and I'll add it to op. Enjoy fellas.
...!!!
The first one for getting rid of that stupid contacts sync thing worked great! Thanks!
I just destroy that software with Titanium backup anytime it is a problem.
Nice write up k-alz
Sent from my SM-N900A using Tapatalk
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Walter.White said:
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Click to expand...
Click to collapse
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
K-Alzwayed said:
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Great info thanks
tmoore3496 said:
Great info thanks
Click to expand...
Click to collapse
No problem buddy. Hopefully it helped you.
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
UK2K said:
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Click to expand...
Click to collapse
You're very welcome, man. Glad I could help
azpatterson3 said:
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
Click to expand...
Click to collapse
Welcome to the awesomeness of our community where everyone is nice and very helpful.
DPI change
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
UK2K said:
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
Click to expand...
Click to collapse
Thanks, man. I'll add it to OP. :good:
K-Alzwayed said:
Thanks, man. I'll add it to OP. :good:
Click to expand...
Click to collapse
Sweet! My first mention! :laugh:
Thanks Sir.
Brilliant wi-fi fix!
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
K-Alzwayed said:
Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
Click to expand...
Click to collapse
sethomas1975 said:
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
Click to expand...
Click to collapse
No problem. Glad it helped [emoji16]
THANK YOU!
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
jpstiehl said:
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
Click to expand...
Click to collapse
Glad It worked for ya man
Here's some to add. One is for soft-menu, and the other is for disabling AT&T wifi by renaming the SSID.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wifi/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"

Trying to change model number. build.prop doesn't work

Hello,
I'm trying to change the info displayed in my Model Number in "About phone" in Settings.
I have edited build.prop and even used XPosed with Device Faker. It does display the new Model Number in XPosed or any other application but when going to "Settings --> About Phone" , it still displays the original name, which is grayed-out and it's bugging the hell out of me, the fact that I can't change it.
Does anyone have an idea of what I can do, short of flashing a custom ROM?
I'm using stock ROM and rooted.
What are you editing it with, a build.prop app? I normally used root explorer and have never tried any of the apps for that. I'm guessing they do ask for root privileges and you change the system to write to make the changes and back to read only after the changes?
I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings
UzY3L said:
I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings
Click to expand...
Click to collapse
Did you search the entire build.prop? It's possible that the name could appear more than once.
Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.
UzY3L said:
Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.
Click to expand...
Click to collapse
In my phone settings, in the "software channel" part....mine shows "ATTMX". Is it possible to edit that to show something else??
If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app
rbeavers said:
If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did that. Doesn't work. Motorola went to a lot of trouble to stick that model number there for good. I wonder why?
Doesn't matter anymore. I bought an LG G3. Same size, same battery, much better specs, less battery life. An acceptable tradeoff.
Thank you all for your answers!

Enable tethering through build.prop issues

So recently... I have tried to enable tethering through editing the build.prop. Upon reboot... My camera app stops working and 3rd party camera apps become buggy if I try to replace the stock app.
I am using the "net.tethering.noprovisioning=true" technique.... And changing nothing else. Has anyone else run into this issue or does anyone have a fix.
Issue specifics:
- Happens no matter on stock ROM rooted or custom ROM (currently on resurrection remix)
- flashlight will also stop working until I edit quick menu icons and then it works.
- I have tried wiping cache and formatting.
- tried rebooting
- tried backing up build.prop and restoring it... Issue still stays.
- for awhile I was using elementalx kernel... But the problem still seems to stay on Ex or stock kernel.
- happens on both android 6.0.1 and 7.1.1 ( 7.1.1 currently used)
- moto g4 xt1625 (non-amazon) Athens retus phone model
Any thoughts or fixes?
Thanks
Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks
30mmrain said:
Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks
Click to expand...
Click to collapse
I had the same exact problem, and tried many of things you tried without success. I finally tried the solution on another site and it fixed all the problems. After I tried it, I realized it was probably a permission issue on build.prop.
I'm not allowed to post the link of the site. However, long story short, try changing the permissions of build.prop by using chmod 644 build.prop, or change build.prop to -rw-r--r-- .

Pixel UI Sounds

Hey folks,
Coming from a pixel, I really missed the nice sound it played when you touch anything on the screen (sounds similar to google keyboard touch sounds). So here's what I did:
1. Had a friend with a rooted pixel send me his UI sounds (https://drive.google.com/file/d/10bI8faSnKBSwT0LRS2stk7g1Q9rrIRSf/view?usp=drivesdk)
2. Located the file that controls touch sounds (/system/product/media/audio/ui/Effect_Tick.ogg)
3. Using a root browser (mixplorer is my favorite), I tried copying and pasting over the current Effect_Tick.ogg, no luck. Tried deleting the current Effect_Tick.ogg, no luck. Tried changing permissions on the live file, no luck. I checked file size and the pixel one is smaller than the oneplus file, so I'd think partition size wouldn't be a problem.
I'm running android 11 with magisk. I'm wondering if android no longer lets you change live system files? Maybe this is something I need to change while phone is in fastboot? Think this breaks safetynet?
Thanks for the input folks!
xxBrun0xx said:
Hey folks,
Coming from a pixel, I really missed the nice sound it played when you touch anything on the screen (sounds similar to google keyboard touch sounds). So here's what I did:
1. Had a friend with a rooted pixel send me his UI sounds (https://drive.google.com/file/d/10bI8faSnKBSwT0LRS2stk7g1Q9rrIRSf/view?usp=drivesdk)
2. Located the file that controls touch sounds (/system/product/media/audio/ui/Effect_Tick.ogg)
3. Using a root browser (mixplorer is my favorite), I tried copying and pasting over the current Effect_Tick.ogg, no luck. Tried deleting the current Effect_Tick.ogg, no luck. Tried changing permissions on the live file, no luck. I checked file size and the pixel one is smaller than the oneplus file, so I'd think partition size wouldn't be a problem.
I'm running android 11 with magisk. I'm wondering if android no longer lets you change live system files? Maybe this is something I need to change while phone is in fastboot? Think this breaks safetynet?
Thanks for the input folks!
Click to expand...
Click to collapse
did you know how to do?
Morloc2 said:
did you know how to do?
Click to expand...
Click to collapse
Nope, never got it to work. I don't think it's possible
xxBrun0xx said:
Nope, never got it to work. I don't think it's possible
Click to expand...
Click to collapse
thx for reply me
maybe is possible with pc
how can we surf in android folders when we connect the phone to the pc?

NO AUDIO INPUT AND OUTPUT

Hello!
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos (youtube, netflix, spotify, chrome, etc). I cant record videos too.
What is wrong with my device? Do we have audio patch for this? I have also custom rom my phone with DotOS v.5.0.1 thru TWRP.. tell me if im missing a system app..
dyoliya said:
Hello!
i’m very new with having custom ROM. And I flashed my device with DotOS v5.0.1 thru TWRP. (Also tried diffrent custom rom)
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos. I cant record videos too.
did i miss something? Im sorry im really new with this. I dont know if there is a patch that i should use...
Click to expand...
Click to collapse
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)
zgfg said:
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)
Click to expand...
Click to collapse
ive done that. after flashing a ROM, I format data..
My audio was working before I custom ROM too. idk if i should just go back to stock rom
UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.
There are codes that you dial and you can test all your hardware separately. It depends on rom, so you have to try
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
I’ve tried going back to android 10 but the Original problem of my phone goes back again. It lags big time!! So i dont have a choice but to switch to a custom ROM.
i havent tried editing propsconfig yet. How do you do that?
swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
I have same problem but no one is trying to replace Audio ichha
Jeetp126 said:
I have same problem but no one is trying t
Click to expand...
Click to collapse
yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.
swaggyp01 said:
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.
Click to expand...
Click to collapse
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props
zgfg said:
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props
Click to expand...
Click to collapse
Thanks for explaining everything brother. Now I will do a research about editing audio or sound on build prop. Hopefully this is not a hardware issues.
Same issue encountered with me also. I am in a great distress right now. Tried more than 30+ roms (including recover, fastboot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat'll be a great help indeed!!
dyoliya said:
UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.
Click to expand...
Click to collapse
Exactly same thing happened with me, at that time I was on Miui global stable 12.0.9.0.. It happened all on a sudden. Now I am phoneless
swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
Same exactly
If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os
Jeetp126 said:
If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os
Click to expand...
Click to collapse
Yes You are right
IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275
IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275

Categories

Resources