Low Microphone Fix [Android 11] [Custom ROM] [Root required] - Xiaomi Poco F2 Pro (Redmi K30 Pro) Guides, News, &

This was done on a Xiaomi Poco F2 Pro (lmi) running crDroid 7.16 (Android 11). The low microphone volume issue seems to be prevalant on a lot of POCO devices running Android 11.
After all the "revoke microphone permissions from the Google app" fixes didn't work, this one did.
Disclaimer: You need a rooted phone. Obviously I don't give any guarantees, warranty or am responsible for anything you might break, although I don't think you can really break anything here.
I am mostly doing this write up, since I noticed a lot of people with the same / similar issues, but almost no solutions to it at all.
I used FX File Explorer for this, but any file explorer capable of acquiring root permissions should work.
This guide is specifically for the Poco F2 Pro (lmi), but the process should be similar on all other android phones.
I am also not sure whether you need to edit all the values that I did, but I didn't waste time on trying to pinpoint which values did it exactly.
Furthermore, I increased the values from their original 6 to 12 first, then to 18, and it barely changed, but there was a noticeable improvement from the original '6'.
0) Have a rooted phone, install a file explorer with root capabilities.
1) Go to /system/vendor/etc/ to find your "mixer_paths.xml" file
- it might also be under /system/etc/
- you might also have more than one file, for this guide we also need to edit the "mixer_paths_overlay_static.xml" file
2) Mount the "etc" folder to Write/Read, otherwise you won't be able to edit the .xml file
- in FX File explorer open the menu on the top right, and select the most bottom option "Mount read/write" or sth. along those lines
3) Open the first file, "mixer_paths.xml" and change the following values
- (remember you can search for entries)
- main-mic: ADC1 Volume from 6 to 12
- top-mic ADC4 Volume from 6 to 12
- back-mic ADC2 Volume from 6 to 12
- under 'tri mic devices' find the ADC1 / 2 / 4 Volume values and change them from 6 to 12
- under 'unprocessed mic' change ADC4 Volume 12 to 24
- under 'unprocessed stereo-mic' ADC1+4 Volumes 12 to 24
- save this file.
4) Open the second file, "mixer_paths_overlay_static.xml"
- find the ADC Volume entries for 1 / 2 / 3 /4 and change all of them from 6 to 12
- 'handset-mic' ADC1 & 4 Volumes 6 to 12
- 'speaker-mic' ADC4 Volume 6 to 12
- under 'dual mic devices' find the ADC1 & 4 Volumes and change them from 8 to 16
- save this file.
5) Remount the folders as read-only.
6) Reboot your phone.
7) Profit!

Related

Access all apps from market

I'm not responsible if your phone crashes, bricks, vanishes or display Apple logos, or if you buy apps you can't use because "wrong version".
Also, experimental tweak, don't expect miracles - It is useful for developpers and curious guys ^^
Okay guys, here is a very easy tweak to allow you to display/install (NOT use, most won't work) all apps from Market (your version and all upper), just add the stuff I give below and you're ready to go
What you need : rooted phone, Android (1.6, 2.x.y, 3.x... Stock or not)
File to edit : /system/build.prop
How to edit : Root explorer
How long : 5 minutes (edit, reboot, try)
** Make a backup of your build.prop !!!!!! (Root Explorer will do it automatically) **
1. Root Explorer > Go to /System/ > Long press build.prop and click Open in Text Editor
2. Find the line :
Code:
ro.build.version.sdk=7
Simply edit the value (API Level) according to what you want to display.
Code:
API Level = 7 >> Android 2.1 (Default)
API Level = 8 >> Android 2.2
API Level = 9 >> Android 2.3
API Level = 10 >> Android 2.3.3
API Level = 11 >> Android 3.0
Save and check backup is created, then reboot and try searching apps you usually can't access (ie. for Android 2.1 : Flash Player)
What it will do :
* Display & install apps for your current Android version AND upper versions (ie. if you set API Level to 9, you will see apps for Android 2.1 + 2.2 + 2.3). Dunno if you can display previous versions, but you can try levels 3,4...
* Allow you to get .apk directly from Market (install, then copy apk with Root Explorer)
What it will not do :
* Make the downloaded/installed apps of other versions to work. The apk will come with no icon, service name and will probably crash when you'll try to run it - You can try to patch it with APK Manager. So do not buy apps, you will probably won't be able to use them ! (Check also the version, Market will NOT warn you about the app's API Level)
Hope this will help people to port .apk files from other versions to our old 2.1...
what about device fingerprint?
DooMLoRD said:
what about device fingerprint?
Click to expand...
Click to collapse
I haven't tried, but there are also several strings you can edit in the build.prop... Those *should* allow to change fingerprint.

AmeriCanAndroid screen size issue

so i just flashed the AmeriCanAndroid rom and everything is running smoothly. the only issue is that the screen is very small. like the notification bar is so small i can hardly see it. the lock screen is a little bigger then a US stamp. i searched the original thread but there are over 1500 pages and the search function yeilded no results . so how do i fix the screen size?
The very first page of ACA thread says
"-Starting with 080111 and later, users can edit /sdcard/android/startup.txt prior to booting to adjust LCD_DENSITY, GPS_ZONE, and DATA_SIZE (data.img)
(ie: the default lcd_density of ACA is 167. Edit the lcd_density= value to 240 to get standard sized icons and fonts)"
The part you're looking for is to change the value to 240.
I do agree, its a plague to look through that thread and search ain't no help if you don't search right
RE: Wrong Section
Hi...please put this in the questions and answers section...iron fist will be on you ...here are some solutions I found by simply using the search:
You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
hope this helps you out
Or if that doesn't work, go to spare parts and uncheck "compatibility mode" then reboot phone
Pansi SMS screen size issue
I am using american android 2.3.7.
I have installed Pansi SMS application for messaging but some how it is not coming on the fullscreen of HD2. It is just capturing upper middle part of the screen Neither am i able to open the settings of Pansi SMS. Even the windows key is not working to open its setting.
How can i resolve this.
Is there any other SMS app as good as PANSI ?

Enable Native Hotpot

Enable Native Hotspot
confirmed sprint nexus 6
1. Must be rooted
2.download sqlite database editor or equivelant app
3.hit data folder
4.hit data folder again
5 hit com.android.providers.settings
6. hit databases
7. hit settings.db
8. hit global
9 hit the + sign or add new
10. under the name write tether_dun_required
11. under value set that to 0
12 then save reboot and enjoy
Will add video soon
Thread closed
Steps also mentioned in this thread

|HELP| IR REMOTE cyanogenmod 13 lg g2 d802

If i have cyanogenmod 13 rom, how can i install a apps that support ir ?
(quick remote , Peel Smart Remote , control-it!)
YuvalHas said:
If i have cyanogenmod 13 rom, how can i install a apps that support ir ?
(quick remote , Peel Smart Remote , control-it!)
Click to expand...
Click to collapse
tadaaaaaaaaa
http://forum.xda-developers.com/lg-g2/themes-apps/port-lg-quickremote-aosp-mm-g2-g3-t3302437
Controlling Cyanogenmod13 (aka LineageOS 13) via TeamViewer
Hi. I've been searching fro a way to control a Cyanogenmod13 device and I finally found it!
My device is SM-N900 Samsung Galaxy Note 3 (ha_3g international).
1. Go to Google play market and install application: QuickSupport (there are QS letters written in the top left corner of the icon).
2. Run the app. After TeamViewer downloads the QS Addon APK, retrieve it from Internal Storage/Android/data/com.teamviewer.host.market/files/Download/TeamViewerQSAddon.apk
Use a file explorer that has root permissions and the ability to change files and folders permissions (I use ES)
3. Create a folder in /system/app/ or /system/priv-app/ named TeamViewerQSAddon with rwx r-x r-x (I used /system/app/).
3.1 To change permissions in ES - long tap --> 3 dots in the lower right corner MORE --> and then Properties (or somth like that Idk 'cause I use russian version) then in the lower part of the Properties window there will be the line: Permissions. Tap Change and mark as follows: Owner: 1,2,3; Group: 1,3; Others: 1,3.
4. Put the APK in that folder and change its permissions to rw- r-- r--
4.1 To change Permission again: long tap, More, Permissions. Tap change permission and mark as follows: Owner: 1,2; Group: 1; Others: 1.
5. Reboot and it must work! Tested on my SM-N900 ha_3g running LineageOS 13.0-20170204-UNOFFICIAL-ha_3g. I guess that Official will do just the same. Good luck pals!

How to expand the volumen steps for speaker/headset and phone on the Z5C

Hi,
as you know the steps for the speaker/headset and phone volume are not so smooth in Z5C stock rom. You can edit them in a easy way without hacking any files. To edit the values you need a rooted phone.
Steps:
1. You to system and open the build.prop. For this I use the app BuildProp Editor from the playstore BuildProp Editor, but you also take the internal text editor.
2. Open the file build.prop
3. insert at the end of the file these two entries:
Code:
ro.config.vc_call_vol_steps=6
ro.config.media_vol_steps=30
4. save the file and restart your phone.
Bingo - you have now many more steps for vol +/-
The first code line is for call volume
The second code line for media volume
Tested on Z5C 32.4.A.1.54 - stock rom
You can use any number of steps that you want.
Enjoy
Remember: You are responsible for everything that you are doing with your phone.
I will try adding these settings with resetprop in a service.d script and see if it works
Results: nothing changed when I put the script in service.d, but it works perfectly in post-fs-data.d
Thank you

Categories

Resources