*I am not responsible for bricked devices
I've been having problems with the microphone for a long time, metallic voice in the calls, recording (like Whatsapp and Messanger and camera) very low and distorted. I replaced my microphone with a new one, I did not investigate if the microphone was faulty or my output of mob was faulty, but the problem was not solved. My problem is from the time of cm11 44s, only in this way I can perfectly use my microphone with any rom I flash.
This modification definitely fix the low mic issue on call.
Do not flash these zip for ROM based on OxygenOs.
INSTALLATION INSTRUCTIONS
NOTE: I recommend using the latest TWRP and do Nandroid Backup (for safety),In case the fix gives some problems, restore the backup.
1. Flash zip version (All roms/Oreo)
2. Wipe Cache and Dalvik (Optional )
3. Reboot
For any problem:
Contact Telegram
@OpIcarus
Contributors
@OpIcarus
@Silvered
Version Information
Status: Stable
Created 2018-03-01
P.S. Do not call me a dev. :silly:
I had this problem just for phone calls (not recording) and with MicFixOreo everything works again now! Thank you very much for this
Many thanks. Does that fix loud inaudible records during live concert ?
kdpkke said:
I had this problem just for phone calls (not recording) and with MicFixOreo everything works again now! Thank you very much for this
Click to expand...
Click to collapse
I am glad to help u!
Remember the thanks to the thread if i help u ?
FrenchSparda said:
Many thanks. Does that fix loud inaudible records during live concert ?
Click to expand...
Click to collapse
I do not know, I have a concert on March 16th, I'll try!
OpIcarus said:
*I am not responsible for bricked devices
I've been having problems with the microphone for a long time, metallic voice in the calls, recording (like Whatsapp and Messanger and camera) very low and distorted. I replaced my microphone with a new one, I did not investigate if the microphone was faulty or my mother's output was faulty, but the problem was not solved. My problem is from the time of cm11 44s, only in this way I can perfectly use my microphone with any rom I flash.
This modification definitely fix the low mic issue on call.
Do not flash these zip for ROM based on OxygenOs.
INSTALLATION INSTRUCTIONS
NOTE: I recommend using the latest TWRP and do Nandroid Backup (for safety),In case the fix gives some problems, restore the backup.
1. Flash zip version (All roms/Oreo)
2. Wipe Cache and Dalvik (Optional )
3. Reboot
For any problem:
Contact Telegram
@OpIcarus
Contributors
@OpIcarus
@Silvered
Version Information
Status: Stable
Created 2018-03-01
P.S. Do not call me a dev. :silly:
Click to expand...
Click to collapse
What changes are applied? How does this differ from other fixes?
Mothers output is faulty ?what the word mean?
pankspoo said:
Mothers output is faulty ?what the word mean?
Click to expand...
Click to collapse
I can not speak well in English, and I was referring to the motherboard. Laughing under a thread where I have made available a Fix for the resolution of a problem, it is out of place, but 'Risus abundat in ore stultorum'
Karut said:
What changes are applied? How does this differ from other fixes?
Click to expand...
Click to collapse
several changes in mixer_paths.xml and audio_platform_info.xml
OpIcarus said:
several changes in mixer_paths.xml and audio_platform_info.xml
Click to expand...
Click to collapse
Additionally to the standard changes?
Code:
ro.qc.sdk.audio.fluencetype=fluence to ro.qc.sdk.audio.fluencetype=none
/system/etc/audio_platform_info.xml: <device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" /> to <device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
mixer_paths.xml: DEC4 value from 84 to 92?
Because these help only somewhat...
Karut said:
Additionally to the standard changes?
Because these help only somewhat...
Click to expand...
Click to collapse
yes, even the change to build.prop, I forgot I'm sorry. In addition, I often modified only that value by bringing it from 40 to 4, for a period I solved and the problem presented itself again. To see all the values changed, open the file mixer_path and audio_platform with wordpad, and compare to the original, the file I modified it long ago and tested for months, I do not remember all the changed values
up
for those who still have problems after the flash
1)-Use MiXplorer app
2)-go to root/system/etc for KK/LP/mm users
*FOR OREO USERS*
-go to root/system/vendor/etc
3)Copy the files
4) Go to build.prop and:
'ro.qc.sdk.audio.fluencetype=fluence' to 'none'
OpIcarus said:
several changes in mixer_paths.xml and audio_platform_info.xml
Click to expand...
Click to collapse
Nice... You worked out all those changes on your own ? If yes then you must be called a dev...
---------- Post added at 06:14 PM ---------- Previous post was at 06:05 PM ----------
OpIcarus said:
for those who still have problems after the flash
1)-Use MiXplorer app
2)-go to root/system/etc for KK/LP/mm users
*FOR OREO USERS*
-go to root/system/vendor/etc
3)Copy the files
4) Go to build.prop and:
'ro.qc.sdk.audio.fluencetype=fluence' to 'none'
Click to expand...
Click to collapse
Soon (maybe already) in oreo ROMs, ro.qc.sdk.audio.fluencetype will be changed to ro.vendor.audio.sdk.fluencetype, because CAF is moving to vendor prefixes for their system props (in fact in MSM8916 audio HAL it has already been changed and I've pushed it to LAOS Gerrit: https://review.lineageos.org/#/c/210875/) So msm8974 (our SOC) might follow suit as well...
can we back out the changes if we find any trouble after flashing the zip?
jayaraj.chinna said:
can we back out the changes if we find any trouble after flashing the zip?
Click to expand...
Click to collapse
Copy the files I've edited to the internal memory before using the zip or replacing them manually
Adithya R said:
Nice... You worked out all those changes on your own ? If yes then you must be called a dev...
---------- Post added at 06:14 PM ---------- Previous post was at 06:05 PM ----------
Soon (maybe already) in oreo ROMs, ro.qc.sdk.audio.fluencetype will be changed to ro.vendor.audio.sdk.fluencetype, because CAF is moving to vendor prefixes for their system props (in fact in MSM8916 audio HAL it has already been changed and I've pushed it to LAOS Gerrit: https://review.lineageos.org/#/c/210875/) So msm8974 (our SOC) might follow suit as well...
Click to expand...
Click to collapse
Thx man
If you want to donate for the work
PAYPAL: [email protected]
I think I have to review the zip, the manual replacement works better, I do not know why
FIRST AND AFTER THE FIX
OpIcarus said:
for those who still have problems after the flash
1)-Use MiXplorer app
2)-go to root/system/etc for KK/LP/mm users
*FOR OREO USERS*
-go to root/system/vendor/etc
3)Copy the files
4) Go to build.prop and:
'ro.qc.sdk.audio.fluencetype=fluence' to 'none'
Click to expand...
Click to collapse
Hi,
due to Oreo change, I think that in build.prop, in place of "ro.qc.sdk.audio.fluencetype=none" you'll have to place "ro.vendor.audio.sdk.fluencetype=none".
have fun. ....always!
Related
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the source.
V4 Flashable ZIP: https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA
Obligatory screenshots: https://imgur.com/a/cXrnH
Working
As Shamu is a supported device, most things work well here:
Booting
Cellular (Calling, SMS and data)
Audio
Wi-Fi
Bluetooth
GApps (see below)
Easter egg
Not working (?)
Not working on Verizon, as reported here
There are probably more
GApps
This build has dm-verity enabled. With the stock kernel, GApps will not show up, or a warning is displayed when booting. To solve this, either use a custom kernel or use FED-Patcher.
After installing OpenGApps, you may encounter force closes during the Setup Wizard.
replica102 said:
You can just skip setup without editing the build.prop. Just tap on the four corners of the screen, starting from top left, clockwise. Do it right, and you'll get sent to home screen.
Click to expand...
Click to collapse
Afterwards, to get rid of the Play Services force closes, go to Settings > Apps > Three dot menu > Show system and find Google Play Services. Enter the Permissions menu and grant all the permission it needs.
If apps requiring WebView force close, try excluding "WebviewGoogle" using the gapps-config config file. Details are available here.
Sources
This build was compiled on a modified tree. See the changelog for details.
Vendor blobs are downloaded from https://developers.google.com/android/nexus/blobs-preview
Changelog
Code:
V4 - NRD90U - That's what I call "Useless"
Flashable ZIP: [url]https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA[/url]
- Updated to 7.0.0_r6/NRD90U. So you want the shiny new build number? Here you go!
V3 - NRD90S
Flashable ZIP: [url]https://mega.nz/#!35Zl0QyY!gUYM79Fs_I6tm2RdEJw1v5S30qQqJ2RA1B3EosKlSqk[/url]
- Updated to 7.0.0_r4/NRD90S, with September's security updates.
V2 - NRD90M - A proper build... and more!
Flashable ZIP: [url]https://mega.nz/#!f4wSnTDL!3ifsV_qC_r-MJ-y45yDcwemkgTGY_jTr_OObHRktC-M[/url]
- The product name is now "Nexus 6" instead of the default "AOSP on Shamu". The modified device tree is available [URL="https://github.com/zhaofengli/device_moto_shamu"]here[/URL].
- The navigation bar editor is now accessible in System UI tuner. This is done by reverting [URL="https://android.googlesource.com/platform/frameworks/base/+/72195a011128d1c516149763c4c156539a470ed5"]this commit[/URL].
- I found out that I checked out the master branch for a handful of repositories when playing around. This is now fixed.
- This build was compiled with external/icu at [URL="https://android.googlesource.com/platform/external/icu/+/683055d9b50491dedbadea4e8ffb484e99e4f52b"]683055d[/URL] (the current master). This is to get RIL working.
- Developers: See [URL="http://forum.xda-developers.com/showpost.php?p=68556855&postcount=10"]this post[/URL] for a full explanation of the solution to get RIL working on 7.0.0_r1.
V1 - Initial build
Note: On a closer look, this is actually not a proper 7.0.0_r1 build. You should download V2 instead for a smoother experience.
Flashable ZIP: [url]https://mega.nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY[/url]
Mods: Please move this thread to the appropriate section if required.
Where did you get blobs from?
Kernel source?
Well done on being the first XD
neobuddy89 said:
Where did you get blobs from?
Kernel source?
Click to expand...
Click to collapse
Blobs are from https://developers.google.com/android/nexus/blobs-preview
And as said, I haven't changed the source in any way. Kernel source is available at https://android.googlesource.com/device/moto/shamu-kernel/+/android-7.0.0_r1
Edit: Wow, didn't look too closely. That's the prebuilt kernel, and the corresponding source hasn't been uploaded yet.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
The mega link don't work.
serch826 said:
The mega link don't work.
Click to expand...
Click to collapse
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Twiggy000b said:
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
I removed the <dot> but it doesn't work.
serch826 said:
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
looks like mega is having server issues... i got it though
---------- Post added at 06:28 AM ---------- Previous post was at 06:25 AM ----------
Zhaofeng Li said:
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Click to expand...
Click to collapse
the log shown was simulating actions and then went to success. let me try again
Twiggy000b said:
looks like mega is having server issues... i got it though
Click to expand...
Click to collapse
Thanx mate!
cerico76 said:
I removed the <dot> but it doesn't work.
Click to expand...
Click to collapse
i retract my last response lol, you also gotta put a "." between mega and nz lol mega is alive!
Thanks, will download and try asap!
EDIT: i guess it will encrypt the device?
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Q9Nap said:
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Click to expand...
Click to collapse
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Noob Question:
Where can I get the GApps file for this build?
Thanks!
edwaine said:
Noob Question:
Where can I get the GApps file for this build?
Thanks!
Click to expand...
Click to collapse
Use open gapps
Sent from my Nexus 6 using Tapatalk
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
In twrp I wiped everything except internal storage. flasked. still have my files. So, no it does not force encrypt. Your welcome.
Zhaofeng Li said:
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Click to expand...
Click to collapse
So.. this probably force encrypts device, right?
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
harpin14789 said:
So.. this probably force encrypts device, right?
Click to expand...
Click to collapse
Flash this after flashing the rom zip and you don't have to worry about it:
http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
Very early builds of Android Nougat for our beloved Nexus 7 2013
What works:
Audio
Brightness
GPU Acclereration
Bluetooth
Wifi
GPS
NFC
Location services
Camera and video recording
Video playback
MTP
Sensors
Bugs:
- very poor 1080p video recording quality????
- ??
Download: v0.6
Gapps: opengapps.org (micro version recommended)
Sources: https://github.com/aosp-msm8960
Code:
[B]Changelog: [/B]
[B]v0.6[/B]
- wifi location fixed thx to @nbehary
- deleted gapps
- update to NRD90U (September security patch level)
- Night mode and nav bar settings enabled (you can find it in System UI Tuner)
- playback improvements
- proper device name (I hope so :D )
[B]v0.5[/B]
- settings fc fixed
- enabled Doze!
- 1080p 60fps option hidden in yt (our SoC doesn't support it)
- proper device name
- pico gapps included
- gapps permissions fixed
- audio improvements
- video playback improvements
- little clean
- enforcing selinux mode
[B]v0.4[/B]
- saving pictures fixed
[B]v0.3[/B]
- sensors fixed
[B]v0.2[/B]
- userdebug build (no more red border)
- video playback fixes (almost fixed - problems with 1080p 60 fps videos)
- NFC
- now rom is super smooth (just try it!)
[B]v0.1[/B]
- initial release
Maintainers:
DevSwift1
zaclimon
parrotgeek1
Credits:
opengapps team
Question I know sensors arent working yet, does this mean we can't force rotation, ie force landscape mode?
Sent from my Nexus 6P using Tapatalk
@DevSwift1 you did not post newest device tree on github, with camera fix etc
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
djkinetic said:
Question I know sensors arent working yet, does this mean we can't force rotation, ie force landscape mode?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
https://apkpure.com/set-orientation/com.googlecode.eyesfree.setorientation
parrotgeek1 said:
@DevSwift1 you did not post newest device tree on github, with camera fix etc
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
https://apkpure.com/set-orientation/com.googlecode.eyesfree.setorientation
Click to expand...
Click to collapse
here is camera fix https://github.com/FloNougat/androi...mmit/06887bb997a30a8f5b1b7bae2cc0dfbd8f08c35d
DevSwift1 said:
here is camera fix https://github.com/FloNougat/androi...mmit/06887bb997a30a8f5b1b7bae2cc0dfbd8f08c35d
Click to expand...
Click to collapse
No no no no nooooooo thats a terrible hack
At least set androidboot.selinux=permissive on kernel command line on boot.img
parrotgeek1 said:
No no no no nooooooo thats a terrible hack
At least set androidboot.selinux=permissive on kernel command line on boot.img
Click to expand...
Click to collapse
In future builds it will be changed
With MultiROM the rom can not flash ?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Sun_Dancer said:
With MultiROM the rom can not flash ?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
nope
Sun_Dancer said:
With MultiROM the rom can not flash ?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
for multiroom you can use kernel from @Tk-Glitch http://forum.xda-developers.com/showpost.php?p=68367876&postcount=2565 but with this kernel camera will not work
parrotgeek1 said:
No no no no nooooooo thats a terrible hack
At least set androidboot.selinux=permissive on kernel command line on boot.img
Click to expand...
Click to collapse
now we should focus on sensors and gps
Have you managed to rid the red outline flashes? I'm trying to make a build to removes it but I'm not sure how I'm going about it.
Nexus11 said:
Have you managed to rid the red outline flashes? I'm trying to make a build to removes it but I'm not sure how I'm going about it.
Click to expand...
Click to collapse
To get rid of those I had to edit the build.prop and change the string ro.build.type from eng to userdebug. If you want to build a userdebug rom you have to change the lunch properties.
Sent from my MotoG3 using Tapatalk
Guys, this is some really incredible stuff you are doing, and I think I can speak for many of us simpletons that don't know how to compile ROMs by saying that we thank you immensely for breathing new life into our aging Nexus 7's.
I'll be sure to try out every build that goes through here and offer as much help as I can.
Thanks again guys!
Thank you for amazing work on this tablet
Dziekuje za twoja wspaniala robote na ten tablet
@DevSwift1
You could try using all proprietary files from these new ones from N preview! Maybe it would fix GPS, sensors, h264
https://developers.google.com/android/nexus/blobs-preview
parrotgeek1 said:
@DevSwift1
You could try using all proprietary files from these new ones from N preview! Maybe it would fix GPS, sensors, h264
https://developers.google.com/android/nexus/blobs-preview
Click to expand...
Click to collapse
Those are the same as what is on the normal binaries page for the N7. (or I missed myself downloading them from that page. They are what I have locally anyway, and I'm pretty sure I got them from the regular page)
Thanks for hard work.
Audio works well now, but it seems caution appears earlier than stock marshmallow.
Working good for me. I didn't lose my recovery. I'm on multirom 3.0.0. I injected boot sector after installing. I'm using the stock kernel too. I installed as primary though. Thanks for all your hard work. Hope this helps others on multirom.
GPS is actually working for me. (I'm sure. I get my location is Maps with Device Only, and just to make sure installed GPS Status & Toolbox. GPS is working.)
No idea what I could say to help. It is v0.1, Gapps Nano (with Maps installed from Play). I did nothing special installing.
(Also, full Location Services seems to work too.)
nbehary said:
GPS is actually working for me. (I'm sure. I get my location is Maps with Device Only, and just to make sure installed GPS Status & Toolbox. GPS is working.)
No idea what I could say to help. It is v0.1, Gapps Nano (with Maps installed from Play). I did nothing special installing.
(Also, full Location Services seems to work too.)
Click to expand...
Click to collapse
Ok I will check it deeply
Edit: yep, it works
Hello Everyone,
at 1st let me state that this is not my work, it's the work of @Dante63 that's posted and maintain by him on the Miscellaneous Android Development Section of XDA... i just helped him test it.
this works on OnePlus 3 & 3T.
Update Sept 2nd 2018
Version 2.0
based on 5.0.5 file was provided by @mcdachpappe big thanks to him
Updated to Magisk Template 17.0
Download from Google Drive
OR
Attachment
Version 1.0 (outdated and wont work on newer OOS 5.0.X)
OnePlus3/T Google Drive - SoundMod - TWRP + MAGISK
on the GDrive forlder there're 4 files
1- the original file used to make the mod (may be used to revert for non Magisk users without backup)
2- DYI file for manual placement with root explorer (system/vendor/etc with 0644 permission)
3- TWRP flashable zip
4- Magisk Module
Note & Warning /
when using this mod with AML (Audio Modification Library) you need to either install it after AML or replace the file "mixer_paths_tasha.xml" inside the AML module with the one in this mod, other wise the file included on AML will be the one working and this mod wont.
DIY Volume Level:
Speaker Volume isn't present in the mixers
Code:
<path name="speaker">
------------------
<ctl name="RX0 Digital Volume" value="90" /> <!--earpiece , default is 84, Safe up-to 95, beyond is DANGEROUS-->
------------------
</path>
again All thanks to @Dante63 to his work and support.
to check change logs
https://forum.xda-developers.com/showpost.php?p=75203703&postcount=2
The magisk module works solid here. Thanks for sharing.
Thank you @theduke7 for creating the Thread, however I do encourage that I check the 3T mixer files, regardless it may work but there may be slight difference which if they had few additional features, they'd lose them... It won't take much time, If anyone can post the mixers for 3T and mention me, I'll check them ASAP and report if 3T is Similar to 3...
Dante63 said:
Thank you @theduke7 for creating the Thread, however I do encourage that I check the 3T mixer files, regardless it may work but there may be slight difference which if they had few additional features, they'd lose them... It won't take much time, If anyone can post the mixers for 3T and mention me, I'll check them ASAP and report if 3T is Similar to 3...
Click to expand...
Click to collapse
sure m8, i added a notice to the op, and i'll add it again here
Verified working On 3T as well.
My 3t mixer`s but i have 3 files on rr oreo https://yadi.sk/d/flTm0huE3TbDyC
On OP3T Omni 8.1 I have only 3 files too. https://drive.google.com/open?id=1V185f5L5aJNF8yJFBy0N7rc8jfWhlK_M
Feedback
On op3t RR nougat there is one file in the:
/system/vendor/etc (mixer_paths_tasha.xml)
And two files in the:
/system/etc (sound_trigger_mixer_paths_wcd9330.xml and sound_trigger_mixer_paths.xml)
I attached these files.
Dward40 said:
My 3t mixer`s but i have 3 files on rr oreo https://yadi.sk/d/flTm0huE3TbDyC
Click to expand...
Click to collapse
ejdam_ said:
On OP3T Omni 8.1 I have only 3 files too. https://drive.google.com/open?id=1V185f5L5aJNF8yJFBy0N7rc8jfWhlK_M
Click to expand...
Click to collapse
Sam998 said:
Feedback
On op3t RR nougat there is one file in the:
/system/vendor/etc (mixer_paths_tasha.xml)
And two files in the:
/system/etc (sound_trigger_mixer_paths_wcd9330.xml and sound_trigger_mixer_paths.xml)
I attached these files.
Click to expand...
Click to collapse
thank you guys, i think @Dante63 can take a look at these, but i think we need files from OOS, the Oreo OP3T OS , they'll be accurate and work on every rom.
theduke7 said:
thank you guys, i think @Dante63 can take a look at these, but i think we need files from OOS, the Oreo OP3T OS , they'll be accurate and work on every rom.
Click to expand...
Click to collapse
Sam998 said:
Feedback
On op3t RR nougat there is one file in the:
/system/vendor/etc (mixer_paths_tasha.xml)
And two files in the:
/system/etc (sound_trigger_mixer_paths_wcd9330.xml and sound_trigger_mixer_paths.xml)
I attached these files.
Click to expand...
Click to collapse
ejdam_ said:
On OP3T Omni 8.1 I have only 3 files too. https://drive.google.com/open?id=1V185f5L5aJNF8yJFBy0N7rc8jfWhlK_M
Click to expand...
Click to collapse
Each one of you provided their mixers and each mixer is different from the other...
My Question is which one of you gave me the STOCK OnePlus 3T?
UPDATE: None of you gave me STOCK Mixers
Dward40 said:
My 3t mixer`s but i have 3 files on rr oreo https://yadi.sk/d/flTm0huE3TbDyC
Click to expand...
Click to collapse
I got a request for OP3T on my thread for Oreo, and it was Stock Mixers, which Match the OP3...
Yes they are Compatible...
But I have no clue what are these Mixers here, Probably Custom...
The SoundMod will work regardless, but if their ROM depend on the Custom Mixer it (unlikly to happen) it will have issues...
So it's a Trial and Error for them...
But STOCK OP3T is Fine...
You can remove the Notice
Dante63 said:
Each one of you provided their mixers and each mixer is different from the other...
My Question is which one of you gave me the STOCK OnePlus 3T?
UPDATE: None of you gave me STOCK Mixers
I got a request for OP3T on my thread for Oreo, and it was Stock Mixers, which Match the OP3...
Yes they are Compatible...
But I have no clue what are these Mixers here, Probably Custom...
The SoundMod will work regardless, but if their ROM depend on the Custom Mixer it (unlikly to happen) it will have issues...
So it's a Trial and Error for them...
But STOCK OP3T is Fine...
You can remove the Notice
Click to expand...
Click to collapse
yes ,8, the ones provided here are custom,
i'll remove the notice
Is this true stereo or just earpiece enabled to play L channel?
przemcio510 said:
Is this true stereo or just earpiece enabled to play L channel?
Click to expand...
Click to collapse
I think it just enables dual speaker
can this mod damage the earpiece?
omar2005 said:
can this mod damage the earpiece?
Click to expand...
Click to collapse
If you pump too much volume, yes, it can be damaged
Nougat? Specifically Sultans LOS
omar2005 said:
can this mod damage the earpiece?
Click to expand...
Click to collapse
As long the sound comes out clean and clear, then no harm will be done... Crackles and noise will damage the earpiece..
moSess said:
Nougat? Specifically Sultans LOS
Click to expand...
Click to collapse
Put a request on my thread for your LOS ROM...
this looks good, but sorry a bit confuse with this "on the GDrive forlder there're 4 files"
i have magisk, should i use "OREO_MAGISK_OnePlus3_3T_DualSpeaker.zip" only? Or should I do something with those 4 in different methods for each file?
and where should i paste volume level code?
thanks.
abayer.kate said:
this looks good, but sorry a bit confuse with this "on the GDrive forlder there're 4 files"
i have magisk, should i use "OREO_MAGISK_OnePlus3_3T_DualSpeaker.zip" only? Or should I do something with those 4 in different methods for each file?
and where should i paste volume level code?
thanks.
Click to expand...
Click to collapse
Yes, that's exactly the file I flashed
Can confirm that the magisk mod is working wonderfully on one plus 3 running Unleash OS.
abayer.kate said:
this looks good, but sorry a bit confuse with this "on the GDrive forlder there're 4 files"
i have magisk, should i use "OREO_MAGISK_OnePlus3_3T_DualSpeaker.zip" only? Or should I do something with those 4 in different methods for each file?
and where should i paste volume level code?
thanks.
Click to expand...
Click to collapse
the zip you mentioned is right for you....
the vol level code need to be added to the file inside the magisk module then replaced...
open the module and inside the folder system > inside several folders there's an xml file, open in a text editor... the lines are already there, you can adjust the level ... max is 95 (or you're going to blow up your ear piece, also if you're going to use v4a or any similar audio mod also keep the level in the 84-87 range... max 90 if you're very cautious with the device volume...obviously this is do at your own risk thing, Dante63 set it up for the safe level.
Simple flashable zip to patch system audio on treble ROMS!
Credits:
Hmuny99
Phhusson
Schnedi
Thank you guys. You're amazing!
Tested and working!
DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Link: https://github.com/hmuny99/GsiSystemAudioFix
Huh? What audio problem is there?
aLexzkter said:
Huh? What audio problem is there?
Click to expand...
Click to collapse
I had audio issues when I used the Pixel Experience GSI. The audio was distorted. I'll see if it works. Hopefully I can test it within the day.
Tested on Pixel Experiece GSI. Works like a charm. Can confirm :good:
haakufurou said:
Tested on Pixel Experiece GSI. Works like a charm. Can confirm :good:
Click to expand...
Click to collapse
How did you flash the pixel experience Rom. Steps can be helpful
Benfatica said:
How did you flash the pixel experience Rom. Steps can be helpful
Click to expand...
Click to collapse
Bruh, just flash like any other GSI...
Flash a base MIUI ROM or a MIUI vendor image if you have one. (I'm coming off of Xiaomi.EU's MIUI 10.3.12.)
Format Data. (Do this if you have previously booted MIUI. Ignore if you've just flashed it.)
Wipe Cache, Dalvik, and System.
Flash Pixel Experience IMG as a System Image.
Boot and setup your device.
Reboot to TWRP.
Flash the fixaudiogsi.zip file.
Reboot to System.
haakufurou said:
Tested on Pixel Experiece GSI. Works like a charm. Can confirm :good:
Click to expand...
Click to collapse
Hello!. Could you kindly check if Android Auto works on Pixel Exp. ROM?.
Thanks in advance.
haakufurou said:
Bruh, just flash like any other GSI...
Flash a base MIUI ROM or a MIUI vendor image if you have one. (I'm coming off of Xiaomi.EU's MIUI 10.3.12.)
Format Data. (Do this if you have previously booted MIUI. Ignore if you've just flashed it.)
Wipe Cache, Dalvik, and System.
Flash Pixel Experience IMG as a System Image.
Boot and setup your device.
Reboot to TWRP.
Flash the fixaudiogsi.zip file.
Reboot to System.
Click to expand...
Click to collapse
Thanks
currao said:
Hello!. Could you kindly check if Android Auto works on Pixel Exp. ROM?.
Thanks in advance.
Click to expand...
Click to collapse
My apologies. May I please know what to look for to tell that Android Auto is working? I don't really use it. I just need to know what to look for.
The app does run, BTW...
haakufurou said:
My apologies. May I please know what to look for to tell that Android Auto is working? I don't really use it. I just need to know what to look for.
The app does run, BTW...
Click to expand...
Click to collapse
"All you need" is a compatible car. I mean, a car where you could plug the phone with usb cable and check if android auto is launched in phone and showed in the screen car.
Many thanks
currao said:
"All you need" is a compatible car. I mean, a car where you could plug the phone with usb cable and check if android auto is launched in phone and showed in the screen car.
Many thanks
Click to expand...
Click to collapse
Oh, dear. Sorry. I don't really have a car. I know a few people but all they have are traditional faceplate car stereos. I can't help out with that.
haakufurou said:
Oh, dear. Sorry. I don't really have a car. I know a few people but all they have are traditional faceplate car stereos. I can't help out with that.
Click to expand...
Click to collapse
Many thanks anyway.
Enjoy weekend
Regards.
Enviado desde mi Mi 9T mediante Tapatalk
I just checked the source code repository. The zip file simply executes a single line of shell code:
> echo ro.audio.ignore_effects=true > /data/local.prop
I'd argue most people shouldn't need to boot into recovery to flash a zip, when they can execute a single line instruction.
haakufurou said:
I had audio issues when I used the Pixel Experience GSI. The audio was distorted. I'll see if it works. Hopefully I can test it within the day.
Click to expand...
Click to collapse
I heard that is a problem with bluetooth audio on Pixel Experience on Mi 9T. Is it true? It's big deal for me because I'm using my bt headphones everyday.
pok5 said:
I heard that is a problem with bluetooth audio on Pixel Experience on Mi 9T. Is it true? It's big deal for me because I'm using my bt headphones everyday.
Click to expand...
Click to collapse
I believe calls via bluetooth don't work. It's a GSI issue and not just a Pixel Experience one. Every GSI has it. Media through bluetooth, though (i.e. music, videos, games), work properly.
haakufurou said:
I believe calls via bluetooth don't work. It's a GSI issue and not just a Pixel Experience one. Every GSI has it. Media through bluetooth, though (i.e. music, videos, games), work properly.
Click to expand...
Click to collapse
Thanks, good to know. I don't need BT call since my mic's on my earphones are utter crap.
flubba86 said:
I just checked the source code repository. The zip file simply executes a single line of shell code:
> echo ro.audio.ignore_effects=true > /data/local.prop
I'd argue most people shouldn't need to boot into recovery to flash a zip, when they can execute a single line instruction.
Click to expand...
Click to collapse
I know, i'm the creator of the "zip", but since for a lot of people could be quite annoying to do so i made this zip to "simplify" the life of the enthusiast lazy modder
currao said:
Hello!. Could you kindly check if Android Auto works on Pixel Exp. ROM?.
Thanks in advance.
Click to expand...
Click to collapse
I'm also interested. AndroidAuto is not working on global/eu rom :crying:
Pheggas said:
Simple flashable zip to patch system audio on treble ROMS!
Click to expand...
Click to collapse
I tried to flash it on Lineage OS 16 GSI and it fixed the sound issues! It seems like the sound distortion issue appears right after LOS installation, without any additional modules / apps.
Thanks for your work, @hmuny99, @Pheggas.
What do u mean (flash it like a system image??)
Can u explain
Cuz i tried to install it but its bricked everytime
---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ----------
haakufurou said:
Bruh, just flash like any other GSI...
Flash a base MIUI ROM or a MIUI vendor image if you have one. (I'm coming off of Xiaomi.EU's MIUI 10.3.12.)
Format Data. (Do this if you have previously booted MIUI. Ignore if you've just flashed it.)
Wipe Cache, Dalvik, and System.
Flash Pixel Experience IMG as a System Image.
Boot and setup your device.
Reboot to TWRP.
Flash the fixaudiogsi.zip file.
Reboot to System.
Click to expand...
Click to collapse
What do u mean (flash it like a system image??)
Can u explain
Cuz i tried to install it but its bricked everytime
Project treble for Xperia X [ android 10]
Based on Sony Open Devices
Based on Pavel's works
I am not responsible for bricked devices, dead SD cards,.
This is built as dual model, but it could also work on F5121.
Required files:
[OEM file:] Download link
Recommend: V9
[Treble files:] Download link
[Twrp-Q] Download link
How to flash::
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Format Data and Cache in twrp
Flash treble images in fastboot mode:
Code:
fastboot flash:raw boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can also download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fourth: Flash a GSI compatible System image and boot! Notice: GSI should be arm64 A/B type
Code:
fastboot flash system < Path of GSI-System.img >
Source Codes
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 10.0 Q
ROM Kernel: Linux 4.9
Version Information
Status: Testing
Donation:
Paypal
Created 2020-10-25
Last Updated 2020-10-25
Res
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
HTML:
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
Tested on LineageOS 17.1 GSI, sound is fine when calling.
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
this is a known issue, I will fix it soon
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Tested on F5122 ( Dual ), confirmed Lineage, Havoc and PE, AOSP can be used daily/
However if anyone planning to listen some music on it, use .flac format, .mp3 give you no sound, also Viper not working
---------- Post added at 08:28 AM ---------- Previous post was at 08:24 AM ----------
Noname_90 said:
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Click to expand...
Click to collapse
did you flashed an OEM system image
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Noname_90 said:
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Click to expand...
Click to collapse
only a few chance that OEM image would fully functional, i recommend using Official phhusson GSI, currently running Havoc 3.8 and calling have sound
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Phone doesn't awake from deep sleep. I was put it on my desk than pressed power button 10 minutes later and phone waited with black screen than rebooted itself. Anyone has this issue?
Cubbins said:
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Click to expand...
Click to collapse
I've created an issue in bug tracker and i will update all of them there ( in future )
TechnoHT said:
I've created an issue in bug tracker and i will update all of them there ( in future )
Click to expand...
Click to collapse
I noticed it. Thanks. Will see what I can do
Hello, thanks for the amazing work :victory:. The only issue is that I cannot add any fingerprint, tried with descendant x and havoc 3.8.
Other than that, everything is working for me, thank you
for anyone getting .mp3 crashing/no audio, please try to install Viper4Android and turn on Legacy mode in settings
( for further bug + fix just visit bug tracker )
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
&(*) said:
@Sjll
Would you be willing to do a Kugo (X-Compact) port (when you have a moment, if possible)?
Click to expand...
Click to collapse
Pretty sure the vendor.img in cache will boot with X-Compact as the partitions are identical. I have a modified boot with the path set for vendor in kernel (hardcoded). Please advise.
&(*) said:
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
Click to expand...
Click to collapse
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Cubbins said:
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Click to expand...
Click to collapse
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
&(*) said:
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
Click to expand...
Click to collapse
I have the kernel, device tree, everything. So soon you will get a build. But I only have Xperia X, so you will be my eyes and ears