First of all, thank user @Bobgle for the fix. He killed the fish with that, so big kudos.
I just had to add a little line of code to the /system/etc/media_profiles.xml. I know it's not your rom which has the problem, I'll tell the other developer how to fix it as well. I first found out that it was a common problem through your NOPE Kernel FAQ, though, so it's definitely worth adding.
This is the line of code:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
Has to go right between these two and should look like this:
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
<AudioEncoderCap name="amrnb" enabled="true"
minBitRate="5525" maxBitRate="12200"
minSampleRate="8000" maxSampleRate="8000"
minChannels="1" maxChannels="1" />
Once you've done that it's working. I also replaced this line in the media_codecs.xml:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
I'm not sure if that was necessary. Anyway, it's working.
Click to expand...
Click to collapse
I've put his message in the spoiler. I'll put it simply below, hopefully correctly.
-Open /system/etc/media_profiles.xml
-Find
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
-After that line of code squeeze in this:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
-Save and close
-Open: media_codecs.xml (Same folder.)
-Find:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
-Replace the line with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
-Save, close reboot.
Post results, and stuff and hopefully he will be able to answer stuff. The issue was in the ROM itself apparently, so it should work for any CM10 based such.
Edit: Of course, since this is not thoroughly tested, make sure you do a backup before you edit anything.
Not helped.
Desire C,MiniCMv7,NOPE Kernel
Dark_AssassinUA said:
Not helped.
Desire C,MiniCMv7,NOPE Kernel
Click to expand...
Click to collapse
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.
Bobgle said:
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.
Click to expand...
Click to collapse
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip
Dark_AssassinUA said:
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip
Click to expand...
Click to collapse
Glad I could help.
wwooowwwww .....thnxx bro...really it worked....i always had to switch back to sense bcoz of voice message problem in watsapp n other such apps...u saved my life...
Related
Thanks to anyone can help me
a121232 said:
Thanks to anyone can help me
Click to expand...
Click to collapse
decompiler SystemUI.apk
go to : projects\SystemUI.apk\res\layout
open status_bar_tracking.xml
in line like this: <View android:background
you can change colore. two first code(ff) for alpha color change to ex aa
or better way
a 9.png file named status_bar_background in drawable-ldpi.
remove .9 from name. edit this file in image editor (ex photoshop) then make a .9.png file with draw.patcher or make a normal png file in 240X320 resolation named status_bar_background.png (delet status_bar_background.9.png)
okey go to status_bar_tracking.xml change:
Code:
<View android:background=#[COLOR="Red"]xxxxxxxx[/COLOR]
to:
Code:
<View android:background="[COLOR="SeaGreen"]@drawable/status_bar_background[/COLOR]"
compiler again apk.
** don't forgot to delet edited file from keep folder and resources.arsc if you use apk manager!!!
Hello,
In this thread I will be compiling a list of tricks and techniques that I use to build roms for our phone.
I am not a developer, so some of the fixes in this may be bandaid-y and I may not be able to help will all errors, but I will post fixes for those that I have encountered.
This thread is a WIP and will be updated as I receive questions and encounter problems myself. This hopefully will be a good source of knowledge for those who are interested in compiling other roms for our phone, and from this hopefully we will see some more roms developed.
Building
First of all, the device trees. Thanks to codewerx, who has generously created a device tree we can use for our phone.
I would like to link you to the following guide, which instructs you on how to build AOSPA (formerly Paranoid Android).
http://forum.xda-developers.com/showthread.php?t=1863547
You can follow this guide verbatim, as it is mostly laid out for i9300, however we must add this to the Manifest.xml rather than what he has provided.
Code:
<remote name="gh"
fetch="https://github.com/" />
<project name="teamhacksung/android_device_samsung_i9305" path="device/samsung/i9305" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" />
<project name="teamhacksung/proprietary_vendor_samsung_i9305" path="vendor/samsung/i9305" remote="gh" revision="cm-10.1" />
Check to see if any of these are already in your manifest, and remove them if they are.
To make sure that the correct RIL for phone support is included,
1. Navigate to your frameworks/opt/telephony folder.
2. Open a shell session in this folder.
3. Apply this change by codewerx http://review.cyanogenmod.org/#/c/31703/ by
4. Typing the following into terminal
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_opt_telephony refs/changes/03/31703/1 && git cherry-pick FETCH_HEAD/[code]
[B]Fixes[/B]
If you encounter the following error:
[code]make: *** No rule to make target `/home/sam/RootBox/out/target/product/i9305/obj/SHARED_LIBRARIES/libTVOut_intermediates/export_includes', needed by `/home/sam/RootBox/out/target/product/i9305/obj/EXECUTABLES/mediaserver_intermediates/import_includes'. Stop.
Navigate to vendor/samsung/smdk4412-common/proprietary, and open Android.mk
The reason we get this error is because the propietary files are not copied over properly, so we must edit the line in Android.mk which resembles
Code:
ifneq ($(filter i9300 n7100 n8000 n8013,$(TARGET_DEVICE)),)
to
Code:
ifneq ($(filter i9300 [b]i9305[/b] n7100 n8000 n8013,$(TARGET_DEVICE)),)
- Reserved -
Link missing
Could you please add the link to the howto you mentioned?
perchrh said:
Could you please add the link to the howto you mentioned?
Click to expand...
Click to collapse
Oh wow i'm so sorry about that haha I was sure i embedded it
I'll fix it now
Thanks!
I was also able to build CyanogenMod 10.1 using your xml-excerpt.
The "Fixes" section turned out to be unnecessary, as they were already applied for CM.
The RIL-step is still necessary, though.
hey there...
nice work... but can you say me, how i can get the flac support back to my i9305 on aosp?!
perchrh said:
Thanks!
I was also able to build CyanogenMod 10.1 using your xml-excerpt.
The "Fixes" section turned out to be unnecessary, as they were already applied for CM.
The RIL-step is still necessary, though.
Click to expand...
Click to collapse
I wrote a similar guide for CM, see http://forum.xda-developers.com/showthread.php?t=2164954
Can anyone port the CM12.1 Camera app. ( .apk or .zip file ).
Thanks
I wouldnt recommend that..
Instead Just use Google camera or Open Camera... (But your choice)
Too lazy... Just install the apk
(Dont know whether itll work or not. depending on which rom you're running on)
http://drive.google.com/file/d/0Bx8B-WYmLpHIY3ZlNm1uYXdQVkE/view
sagar846 said:
Instead Just use Google camera or Open Camera... (But your choice)
Too lazy... Just install the apk
(Dont know whether itll work or not. depending on which rom you're running on)
http://drive.google.com/file/d/0Bx8B-WYmLpHIY3ZlNm1uYXdQVkE/view
Click to expand...
Click to collapse
does it support slomo video recording at 60 fps and 120 fps ?
You can't shoot slowmotion with CM Roms , only stock .
Valentin4ou93 said:
You can't shoot slowmotion with CM Roms , only stock .
Click to expand...
Click to collapse
actually you can on moto g 2013/motox 2014. i got it working by messing with media_profiles.xml. i can try fixing it for moto g 2014 too, just give me the cm12.1 media_profiles.xml file from /system/etc/. but it will only work on moto camera app.
ask in question thread.
kraatus90 said:
actually you can on moto g 2013/motox 2014. i got it working by messing with media_profiles.xml. i can try fixing it for moto g 2014 too, just give me the cm12.1 media_profiles.xml file from /system/etc/. but it will only work on moto camera app.
Click to expand...
Click to collapse
Files are the same, just show me your modified falcon one and I might push it to CM if I confirm it working on my device.
LuK1337 said:
Files are the same, just show me your modified falcon one and I might push it to CM if I confirm it working on my device.
Click to expand...
Click to collapse
these are the additional lines needed for slowmo ( from motox2)
Code:
[COLOR="Red"]<!ATTLIST VideoEncoderCap maxHFRFrameWidth CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRFrameHeight CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRMode CDATA #REQUIRED>[/COLOR]
Code:
<VideoEncoderCap name="h264" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="3840"
minFrameHeight="144" maxFrameHeight="2160"
minFrameRate="15" maxFrameRate="120"
[COLOR="Red"] maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />
[/COLOR]
<VideoEncoderCap name="h263" enabled="true"
minBitRate="64000" maxBitRate="2000000"
minFrameWidth="176" maxFrameWidth="720"
minFrameHeight="144" maxFrameHeight="480"
minFrameRate="15" maxFrameRate="30"
[COLOR="red"]maxHFRFrameWidth="0" maxHFRFrameHeight="0"
maxHFRMode="0" />[/COLOR]
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="1920"
minFrameHeight="144" maxFrameHeight="1080"
minFrameRate="15" maxFrameRate="60"
[COLOR="red"]maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />[/COLOR]
slowmo will work with stock moto camera app, but there's a little problem. on stock firmware slowmo video is recorded at 120fps and runs at 15 fps (1/8 speed ) , and by this method it will record video at 120fps but it will run it at 30fps ( 1/4 speed ). atleast it's better than having nothing.
kraatus90 said:
these are the additional lines needed for slowmo ( from motox2)
Code:
[COLOR="Red"]<!ATTLIST VideoEncoderCap maxHFRFrameWidth CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRFrameHeight CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRMode CDATA #REQUIRED>[/COLOR]
Code:
<VideoEncoderCap name="h264" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="3840"
minFrameHeight="144" maxFrameHeight="2160"
minFrameRate="15" maxFrameRate="120"
[COLOR="Red"] maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />
[/COLOR]
<VideoEncoderCap name="h263" enabled="true"
minBitRate="64000" maxBitRate="2000000"
minFrameWidth="176" maxFrameWidth="720"
minFrameHeight="144" maxFrameHeight="480"
minFrameRate="15" maxFrameRate="30"
[COLOR="red"]maxHFRFrameWidth="0" maxHFRFrameHeight="0"
maxHFRMode="0" />[/COLOR]
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="1920"
minFrameHeight="144" maxFrameHeight="1080"
minFrameRate="15" maxFrameRate="60"
[COLOR="red"]maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />[/COLOR]
slowmo will work with stock moto camera app, but there's a little problem. on stock firmware slowmo video is recorded at 120fps and runs at 15 fps (1/8 speed ) , and by this method it will record video at 120fps but it will run it at 30fps ( 1/4 speed ). atleast it's better than having nothing.
Click to expand...
Click to collapse
Kk it actually does work, thank you for contributing to CM lol.
LuK1337 said:
Kk it actually does work, thank you for contributing to CM lol.
Click to expand...
Click to collapse
thanks , i was kinda surprised when i got it working considering im a noob.
Please upload the file.
kraatus90 said:
thanks , i was kinda surprised when i got it working considering im a noob.
Click to expand...
Click to collapse
Please @LuK1337 or @kraatus90 upload the modified file.
Does this enable HDR mode as well?
tbiwalkar said:
Please @LuK1337 or @kraatus90 upload the modified file.
Does this enable HDR mode as well?
Click to expand...
Click to collapse
don't have modified file for this device, give me original so i can modify it, or just add those red lines by yourself.
HDR in videos or photos ? if you are asking about videos then no.
Photos.
---------- Post added 28-10-2015 at 12:03 AM ---------- Previous post was 27-10-2015 at 11:43 PM ----------
kraatus90 said:
don't have modified file for this device, give me original so i can modify it, or just add those red lines by yourself.
HDR in videos or photos ? if you are asking about videos then no.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B-j7fkMgO998U21PMGh5RWZWeDA/view?usp=docslist_api
tbiwalkar said:
Photos.
---------- Post added 28-10-2015 at 12:03 AM ---------- Previous post was 27-10-2015 at 11:43 PM ----------
https://drive.google.com/file/d/0B-j7fkMgO998U21PMGh5RWZWeDA/view?usp=docslist_api
Click to expand...
Click to collapse
don't flash it,just extract and replace. enjoy
lel i changed media_profiles.xml and now it only records in 288p 15 fps and i cant switch front camera xD
kraatus90 said:
don't flash it,just extract and replace. enjoy
Click to expand...
Click to collapse
Thanks a lot! slow motion is working fine . also Camera can click pictures in HDR. only thing left is cropping slowmo videos like in stock based roms. thanks a ton @kraatus90
Helllo , friends I am developed this mod for users who love recording .....!
Steps to install this mod :
TWRP and Other recovery
then install this from recovery
reboot system and enjoy clear crystal clear recording.
Features of this mod :
Incall volume fixed.
Noiseless recording.
also working same for nougat and oreo roms only files is different....!
Downloads:
Nougat:
https://www.androidfilehost.com/?fid=746010030569959423
Oreo:
https://www.androidfilehost.com/?fid=962187416754465960
Your mod gave me static sound in recording.
Sushant9096 said:
Hello welcome all of you , I am developed this mod of crystal clear audio recording for users who loved recording and use starmaker and another applications like this.....
Let's enjoy my mod ......
Must remember your device is unlocked for install this mod...!
Steps to install this mod :
TWRP and Other recovery
then install this from recovery
reboot system and enjoy clear crystal clear recording.
Downloads :
Crystal clear recording mod v1.0:
How To Download :
1 . Search redmi 4x androidfilehost on google
2 . Go to Redmi 4x downloads
3 . find my name sushant9096
4 . go to sushant9096 files
5 . go to crystal clear recording mod
6 . then download file in this folder
Click to expand...
Click to collapse
Instead if this long process just give link of your file here,
Can't find
Het OP, why not save a lot of typing and post direct link?
https://androidfilehost.com/?w=files&flid=252043
Looks like you changed the ACDB id for mic to 2 (default is 4, other mods use 1)
Can you explain? Is this for Nougat and Oreo?
Cheers
I am unable to post links because I am new user in xda so my account not have allowed to post external link
...thank you @tweakradje
@Sushant9096 Ah I see. You're welcome.
@Sushant9096
I have looked at the new files. Can you tell me where you get all the ACDB profile id's from? From audio.primary.msm8937.so? The acdb profiles databases cannot be read without Qualcomm tools. (/etc/acdbdata/*acdb)
I don't think it is very useful to override every device's acdb id in audio_platform_info.xml
in the <acdb_id> section.
In this case you want other acdb profile for recording in stereo?
<device name="SND_DEVICE_IN_HANDSET_STEREO_DMIC" acdb_id="21"/>
Other acdb sound profiles to try: (assuming that are defaults from your audio config file)
SND_DEVICE_IN_MAIN_MIC acdb_id="4"
SND_DEVICE_IN_TOP_MIC acdb_id="11"
SND_DEVICE_IN_FRONT_MIC acdb_id="11"
SND_DEVICE_IN_HANDSET_DMIC_MUSIC acdb_id="21" <--- I took this profile
SND_DEVICE_IN_HANDSET_DMIC_VOICE acdb_id="533"
SND_DEVICE_IN_HANDSET_DMIC_INTERVIEW acdb_id="1045"
SND_DEVICE_IN_HANDSET_DMIC_HD acdb_id="2581" <--- Interesting profile
If your mappings are correct and represent the default profiles id's in your audio_platform_info.xml then acdb id 21 is the audio profile for SND_DEVICE_IN_HANDSET_DMIC_MUSIC
Of course you need to disable Fluence for audio recording too with this line in build.prop
persist.audio.fluence.audiorec=false
Please tell more about how you get this so we can learn.
Cheers
tweakradje said:
@Sushant9096
I have looked at the new files. Can you tell me where you get all the ACDB profile id's from? From audio.primary.msm8937.so? The acdb profiles databases cannot be read without Qualcomm tools. (/etc/acdbdata/*acdb)
I don't think it is very useful to override every device's acdb id in audio_platform_info.xml
in the <acdb_id> section.
In this case you want other acdb profile for recording in stereo?
<device name="SND_DEVICE_IN_HANDSET_STEREO_DMIC" acdb_id="21"/>
Other acdb sound profiles to try: (assuming that are defaults from your audio config file)
SND_DEVICE_IN_MAIN_MIC acdb_id="4"
SND_DEVICE_IN_TOP_MIC acdb_id="11"
SND_DEVICE_IN_FRONT_MIC acdb_id="11"
SND_DEVICE_IN_HANDSET_DMIC_MUSIC acdb_id="21" <--- I took this profile
SND_DEVICE_IN_HANDSET_DMIC_VOICE acdb_id="533"
SND_DEVICE_IN_HANDSET_DMIC_INTERVIEW acdb_id="1045"
SND_DEVICE_IN_HANDSET_DMIC_HD acdb_id="2581" <--- Interesting profile
If your mappings are correct and represent the default profiles id's in your audio_platform_info.xml then acdb id 21 is the audio profile for SND_DEVICE_IN_HANDSET_DMIC_MUSIC
Of course you need to disable Fluence for audio recording too with this line in build.prop
persist.audio.fluence.audiorec=false
Please tell more about how you get this so we can learn.
Cheers
Click to expand...
Click to collapse
@tweakradje
Fluence is needed for noiseless audio recording , Check my mod by recording something you like and see clarity and then give me feedback.
Fluence is already disabled..in build.prop
Sushant9096 said:
@tweakradje
Fluence is needed for noiseless audio recording , Check my mod by recording something you like and see clarity and then give me feedback.
Fluence is already disabled..in build.prop
Click to expand...
Click to collapse
I am looking into it.
Can you answer this: Can you tell me where you get all the ACDB profile id's from?
Thanks
tweakradje said:
I am looking into it.
Can you answer this: Can you tell me where you get all the ACDB profile id's from?
Thanks
Click to expand...
Click to collapse
@tweakradje
Join Qualcomm Developer Network and another devices source code of Xiaomi devices like redmi 4x to know more acdb_id profiles
Your Welcome....!
@Sushant9096 Thanks for the info!
tweakradje said:
@Sushant9096 Thanks for the info!
Click to expand...
Click to collapse
@tweakradje
Your Welcome....!
speaker stopped working! How to uninstall it??
sayansadhukhan62 said:
speaker stopped working! How to uninstall it?
Click to expand...
Click to collapse
If you are using pure kernel then its not my mod issue my mod isnt supported for this kernel so change your kernel to lh or stock kernel ....!
Let me share my findings to get perfect calibrated stereo professional sound recording for Redmi 4X Nougat.
in /etc/audio_platform_info.xml only add one override line in the acdb_ids section:
Code:
<!-- dual mic for video and audio recording (def 34), override with SND_DEVICE_IN_HANDSET_DMIC_MUSIC acdb_id 21 -->
<!-- with acdb id 4 set "DEC1/2 Volume" max to 94, else use 104 -->
<device name="SND_DEVICE_IN_HANDSET_STEREO_DMIC" acdb_id="21"/>
in /etc/mixer_paths_qrd_sku1.xml increase default recording volume. Make sure there is no extra "DEC1 Volume" lines in handset-stereo-dmic-ef or speaker-dmic-endfire path. (presuming you are not using broadside)
Code:
<!-- tweakradje increase default recording level from 84, if acdb id is 4 then max 94
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" /> -->
<ctl name="DEC1 Volume" value="104" />
<ctl name="DEC2 Volume" value="104" />
You can override the recording level anytime with for example:
Code:
adb shell su -c tinymix 'DEC1 Volume' 114
adb shell su -c tinymix 'DEC2 Volume' 114
Someone should build an mixer app for setting recording levels.
You can increase volume levels at any time with this for example:
Code:
adb shell su -c tinymix 'RX1 Digital Volume' 92
adb shell su -c tinymix 'RX2 Digital Volume' 92
adb shell su -c tinymix 'RX3 Digital Volume' 92
That is it. Please try and let us know.
tweakradje said:
Let me share my findings to get perfect calibrated stereo professional sound recording for Redmi 4X Nougat.
in /etc/audio_platform_info.xml only add one override line in the acdb_ids section:
Code:
<!-- dual mic for video and audio recording (def 34), override with SND_DEVICE_IN_HANDSET_DMIC_MUSIC acdb_id 21 -->
<!-- with acdb id 4 set "DEC1/2 Volume" max to 94, else use 104 -->
<device name="SND_DEVICE_IN_HANDSET_STEREO_DMIC" acdb_id="21"/>
in /etc/mixer_paths_qrd_sku1.xml increase default recording volume. Make sure there is no extra "DEC1 Volume" lines in handset-stereo-dmic-ef or speaker-dmic-endfire path. (presuming you are not using broadside)
Code:
<!-- tweakradje increase default recording level from 84, if acdb id is 4 then max 94
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" /> -->
<ctl name="DEC1 Volume" value="104" />
<ctl name="DEC2 Volume" value="104" />
You can override the recording level anytime with for example:
Code:
adb shell su -c tinymix 'DEC1 Volume' 114
adb shell su -c tinymix 'DEC2 Volume' 114
Someone should build an mixer app for setting recording levels.
You can increase volume levels at any time with this for example:
Code:
adb shell su -c tinymix 'RX1 Digital Volume' 92
adb shell su -c tinymix 'RX2 Digital Volume' 92
adb shell su -c tinymix 'RX3 Digital Volume' 92
That is it. Please try and let us know.
Click to expand...
Click to collapse
Thank you for this useful info I will try this In next version of my mod...
I'm currently using "Sound Fix v1" by thejayyadav (Magisk module)
Which is the main difference with yours? ?
Do this mod affect smule app ? Or other karaoke app? I means "noiseless"
Hey @Sushant9096, is this mod compitible for other devices like redmi 3s
Hi guys,
I really love RR and since there seems to be no one else who is willing to maintain the latest Resurrection Remix ROM for the Samsung Galaxy S9 and S9+ for Android Q, I offer you this unofficial version.
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
Note:
By downloading this ROM you take full responsibility of all consequences by your own!
I'm not responsible if you brick your device or do any other damage.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Download and changelog for starlte and star2lte:
https://freeze.ws/RR
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
Please don't ask me for support how to flash!
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Kernel Source: https://github.com/yarpiin/White-Wolf-Uni-LOS
Resurrection Remix Source: https://github.com/ResurrectionRemix
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
There are four changes I've made:
- The default networkTransitionTimeout is decreased from 60 to 30 seconds.
- The bluetooth icon in the status bar is visible as soon as bluetooth is enabled (and not only if a bluetooth device is connected).
- The battery LED color can be set individually for the range 90 to 99% (so you have <90% charging, 90% to 99% nearly full and 100% full).
- I did some small undervolting starting with release from May 2022. If you don't want this, just flash another kernel, e.g. White Wolf.
Everything else is default RR!
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
This is the roomservice.xml with all sources I use for the build:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!--Device trees-->
<project name="ResurrectionRemix-Devices/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_crownlte" path="device/samsung/crownlte" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" clone-depth="1" revision="Q" />
<!--Hardware-->
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" clone-depth="1" revision="lineage-17.1" />
<!--Vendor-->
<project name="BlissRoms-Devices/proprietary_vendor_samsung" path="vendor/samsung" remote="github" clone-depth="1" revision="q" />
<!--Kernel-->
<project name="yarpiin/White-Wolf-Uni-LOS" path="kernel/samsung/universal9810" remote="github" clone-depth="1" revision="master" />
</manifest>
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
As long as there is no RR for Android 11 and as long as I stick to my SGS9, I will provide security updates in this thread.
I hope you enjoy it.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Big thanks to the LineageOS team, to synt4x93, to yarpiin, to garett_09 and especially to all the RR developers.
Thank you for this amazing ROM!!
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
One more hint:
Here you find the latest basebands for the SGS9 (big thanks to jaeck!):
https://forum.xda-developers.com/t/...0-22-08-2021-android-10-pie-stockrom.3858990/
For me, the latest version from 07/27/2021 performs best concerning battery consumption in comparison to the modems of the whole last two years.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Feel free to donate, if you want to
Does Android Auto work?
abra-kadabra said:
Does Android Auto work?
Click to expand...
Click to collapse
Just tried it with my F36. It didn't work using USB at all and using bluetooth the google assistant tried to do something after pushing the assistant button of my car, but there was also no connection possbile.
But to be honest, I'm not even sure if my car supports Android Auto. Maybe someone else could test who is sure that his/her car supports it.
Thanks Freeze24 i was gonna build this since i have the same device, going to try and see how the performance and battery life is.
Just curious, how is this compared with the official one?
nnaaffffuu said:
Just curious, how is this compared with the official one?
Click to expand...
Click to collapse
In fact it's the same with the following differences
- the latest security fixes are included
- the bluetooth icon is visible in the status bas as soon as bluetooth is enabled and not only if a device is connected
- the networkTransitionTimeout is set to 30s instead of the default 60s (this is the time your device stays awake after a change in the network connection occured)
Hi Freeze24,
Thank You for opening this thread and all your good work. Your Rom with the latest security patches is very welcome and much apreciated.
(Just Downloaded the newest one and everything is running fine.)
Hey, why the other thread was closed?
I cant get a working safetynet and i cant make my bank apps working? any help please...
Havel_88 said:
Hey, why the other thread was closed?
I cant get a working safetynet and i cant make my bank apps working? any help please...
Click to expand...
Click to collapse
garett_09 doesn't maintain this ROM anymore, that's why I took over with this unofficial build.
To be honest, I also didn't get banking apps work with newer Magisk versions.
Gladfully I still have an old Canary version which works. But I even couldn't reinstall this old version any more, because you need to hide Magisk and in the hiding process it downloads the APK from the Magisk server and then you have again the new version which doesn't work... at least for me.
So I'm really stuck. Can't reinstall my phone.
### UPDATE ###
Unfortunately there are no updates coming from the RR team since September.
Thus I decided to implement the security fixes by myself.
-> Updated patch level to 2022-04-05
-> Download: https://freeze.ws/RR
I've implemented the following fixes:
Code:
CVE-2021-0652 CVE-2021-0705 CVE-2021-0708 CVE-2021-0651
CVE-2021-0483 CVE-2021-0926 CVE-2021-0653 CVE-2021-0928
CVE-2021-0650 CVE-2021-0930 CVE-2021-0919 CVE-2021-0970
CVE-2021-0704 CVE-2021-0967 CVE-2021-0964 CVE-2021-0968
CVE-2021-0965 CVE-2021-0952 CVE-2021-0969 CVE-2020-0338
CVE-2021-39623 CVE-2021-39621 CVE-2021-39626 CVE-2021-39627
CVE-2021-39629 CVE-2021-39628 CVE-2021-39659 CVE-2021-39674
CVE-2021-39692 CVE-2021-39667 CVE-2021-39704 CVE-2021-39706
CVE-2021-39707 CVE-2021-39705 CVE-2021-39796 CVE-2021-39803
CVE-2021-39808 CVE-2021-39809 CVE-2021-39807
Thanks for your work. Good rom.
### UPDATE ###
-> Updated patch level to 2022-05-01
-> I did some small undervolting. If you don't want this, just flash another kernel, e.g. White Wolf.
-> Download: https://freeze.ws/RR
I've implemented the following fixes:
Code:
CVE-2022-20004
CVE-2022-20005
CVE-2021-39700
CVE-2022-20114
CVE-2022-20011
CVE-2022-20112
CVE-2022-0847
CVE-2022-20009
I would love to use this rom, installed yesterday and very happy with it but cannot get CTS to pass for magisk which i need for banking apps to use as my daily rom. Have you managed to get this working?
Have you tried Magisk Canary?
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
I'm not sure if it will work. At least you need to hide the Magisk app itself and use the MagiskHide function.
I sorted it, thanks
Slayerkodi said:
I sorted it, thanks
Click to expand...
Click to collapse
So it's working?
Freeze24 said:
So it's working?
Click to expand...
Click to collapse
Yes it's working fine, I didn't use canary just original magisk, no issues - works fine
### UPDATE ###
-> Updated patch level to 2022-06-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20006
CVE-2022-20138
CVE-2022-20130
CVE-2022-20124
CVE-2022-20134
CVE-2022-20135
CVE-2022-20142
CVE-2022-20144
CVE-2022-20147
CVE-2022-20123
CVE-2022-20131
CVE-2022-20129
CVE-2022-20143
CVE-2022-20141
CVE-2022-24958
CVE-2022-25258
CVE-2022-20132
CVE-2022-25375
### UPDATE ###
-> Updated patch level to 2022-07-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20219
CVE-2022-20229
CVE-2021-0981
CVE-2022-20223
CVE-2022-20221
CVE-2022-20224
CVE-2022-20230
CVE-2022-20227
### UPDATE ###
-> Updated patch level to 2022-08-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20344
CVE-2022-20350
CVE-2022-20358
CVE-2022-20346
CVE-2022-20353
CVE-2022-20347
CVE-2022-20360