Marshmallow Headset noise fix for CM based rom? - Xiaomi Redmi Note 3 Questions & Answers

Is there any fix for annoying headset noise on CM based marshmallow roms. Any kind of Flashable zip or a kernel that fixes this.?
Sorry posting it here. There was no reply on Q&A thread.

Following

Only in Redon Kenzo V3.0.0 kernel because for some people idk they had force closes(?)
Anyway on this kernel I lost ability to change rotation till I reflash a ROM.

Wrong section
Níghtwìng

Go to /system/etc and edit file mixer_patchs_wcd9326.xml
find line
value="CLS_H_HIFI"
edit to
value="CLS_H_LP"
Then open Audio FX and turn off all sound effect, reboot.

Related

[ROM] [5.1.1] Custom OxygenOS [04-04-16]

Custom OxygenOS OneplusX - COSX ROM
Intro
First of, I'm not a developer. I'm just a guy who put a couple of things together. I'm a bit above noob-level, so dont excpect high end stuff like some prestigious developers. That being said, I have put this ROM together because of the lack of ROMS based on our original software for the OneplusX. Don't expect to much, the most things happen under the hood. So no shiny backgrounds or boot screens.
Disclaimer
You know the drill, flashing happens under own responsibility. I have tested everything on two devices, and will not put anything online that can possibily harm or damage our device in any way. This being said, if you need support, ask in this thread.
Open Source
The ROM i have created is for the community, which in my opinion also means it should be fully open source. You can edit everything you want. You can use it as base for whatever you like. No need to ask permission or give reference. Seeing the amount of customized original software, I would be happy to see more custom oos roms pop up. No need to put restrictions on anything. Please just don't bother me with antutu benchmark related complaints.
ROM
Now lets talk business
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
perhaps more, cant remember everything
Instructions
1 Obtain Root access and Custom Recovery
2 Download zip file from link
3 Boot into recovery
4 Install zip from sdcard
5 Wipe data and cache
6 Reboot phone
7 Wait for system deodexing (+/- 10 min)
8 Restart phone again
Download
Link will be provided later on
Thanks
- Thanks to everyone buying this phone and making the community what it is today
- Thanks to everyone in the past learning me how to soup a rom together
- Special thanks to Boeffla for providing his kernel and support of integration in this ROM
- If I forgot someone, Thank-you:good:
XDA:DevDB Information
COSX ROM, ROM for the OnePlus X
Contributors
winesh
ROM OS Version: 5.1.x Lollipop
Based On: OxygenOS
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2016-04-04
Created 2016-04-04
Last Updated 2016-04-03
Notifications
- Link will follow in the evening
Changelog
-x-
What's next
- This is version V1. If you have wishes or requests for a future version, please reply. I will see if i can add it in version V2 or upcoming versions.
- Everything is confirmed working. If you by any chance run into bugs, please report them.
So what's different about this rom than stock OOS? I'd give this a shot!
Interesting, I am waiting for the download link and changelog / feature list to give it a go.
Finished compiling, link will be axailable within couple of hours.
@joey24z1 for difference see rom details
@batam for feature list see rom details
Deodexed
Click to expand...
Click to collapse
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
By theming support you mean layers? Or what..?
namquang93 said:
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
Click to expand...
Click to collapse
http://codeversed.com/deodexed-vs-odexed-rom/
Hi. @winesh...
I think placeholder threads are not allowed as per the rules...
However, thanks for your contribution ..looking for download link ASAP
Sent from my ONE E1003 using Tapatalk
I think OP managed to put most of the tweaks one can do to the Stock OOS and created a zip flash package.
IIRC, I did pretty much similar things on my Stock OOS before moving over to CM13.
Good Job OP saving a lot of time for those who want to enjoy the stock experience.
Coud you post a benchmark test?
solidwave643 said:
Coud you post a benchmark test?
Click to expand...
Click to collapse
Did you read the op? Flash the rom and run the test yourself....
Get the link..
winesh said:
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
Click to expand...
Click to collapse
Good work :good: Might try this as I kinda liked OOS but I'm currently running Marshmallow and CM based crDroid, so also might not go back to Lollipop
Biggest issues I had with the stock OOS 2.2.0 were:
1. Camera in low light situations. I think it's fixed here with Snapdragon camera?
2. Random rebooting, sometimes few times a day, sometimes few days without. Mostly occurred when playing any game with stock ROM. Is this custom OOS more stable?
3. I could not assign Menu action to HW buttons e.g. long pressing and this led to situation where I had to install Xposed framework and some module to get Menu in Titanium Backup to change backup location to SD card. Is this fixed here with Custom Hardware keys remap?
I know I should test this ROM myself, just pointing out biggest issues I had with stock OOS.
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
coolasnju1993 said:
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
Click to expand...
Click to collapse
Same request here. :fingers-crossed:
Thanks for your work!
So proximity wake up ambient display works in this rom ?
And what type of themes are supported ? Layers or CM ?
Theme support
So OP, You have provided Layers or CM theme engine into rom?
Though Layers supported Stock OOS 2.2.0(Partially not all the themes were working) .
anshu goel said:
http://codeversed.com/deodexed-vs-odexed-rom/
Click to expand...
Click to collapse
I said that deodexed is slower than odex rom. So that means this rom is slower than original OOS right ? Please correct me if I'm wrong.
Waiting for download link...
Will give a shot today...

kernel building from source

Hi, i got nice working zenfone port of lollipop 5.0
It have 500mb free ram and works very fast. Firmware is up to date. Will be good alternative for stock lg.
But wifi, camera and bluetooth does not work.
I rhink its a kernel problem.
With lg stock kernel (with asus ramdisk) is as i wrote but with cm12 kernel bluetooth works but touch is control only by circle point.
Ps every hw wifi bluetooth.. lib replace is a bootloop etc
Anyway i think it needs special kernel for this port,
Ps phones have the same cpu gpu etc very similar
Zenfone kernel source https://github.com/shakalaca/ASUS_ZenFone_A500KL?files=1
Dont know if lg shared their sources.
Anyone who have knowledge about building kernels (i dont have) please help thanks in advance
@Vagelis1608
@mobiusm
@Nikita Pro Android
@Zaaap72
@invaderjohn
Screenshots:
forum.xda-developers.com/showpost.php?p=69803370&postcount=14
Works
-ril
-touch screen
-zen apps
-UI
-DATA LTE ..
Does not work:
-wifi
-bluetooth
-camera
-no sdcard
?nfc?gpsgps
From what I understand, you used CM12 as base, right?
If you use the CM12 libs, does it bootloop?
Also, LG has shared their sources.
Vagelis1608 said:
From what I understand, you used CM12 as base, right?
If you use the CM12 libs, does it bootloop?
Click to expand...
Click to collapse
Thanks for answer.
No, stock 5.0.2 as base (but only zimage from kernel and firmare files from system\etc).and similar..
When i change libs to this from stock or cm i get bootloop.
I tried cm kernel but many bugs, only fixed bluetooth.
With lg kernel zimage and asus ramdisk rom works nice but must be something wrong with drivers because no wifi bluetooth and sdcard. Its possibble to fix it? By change some files from lg to asus kernel and build it?
WYPIERDAALAAC said:
Thanks for answer.
No, stock 5.0.2 as base (but only zimage from kernel and firmare files from system\etc).and similar..
When i change libs to this from stock or cm i get bootloop.
I tried cm kernel but many bugs, only fixed bluetooth.
With lg kernel zimage and asus ramdisk rom works nice but must be something wrong with drivers because no wifi bluetooth and sdcard. Its possibble to fix it? By change some files from lg to asus kernel and build it?
Click to expand...
Click to collapse
I think that you need to get some files from LG kernel ramdisk to the one you are using.
Try to capture a logcat of what is failing (e.g. capture a logcat while trying to turn on WiFi, Bluetooth, etc.). It should give you an idea of what is causing stuff to fail.
BTW, you can find LG's sources here: http://opensource.lge.com/index
Vagelis1608 said:
I think that you need to get some files from LG kernel ramdisk to the one you are using.
Try to capture a logcat of what is failing (e.g. capture a logcat while trying to turn on WiFi, Bluetooth, etc.). It should give you an idea of what is causing stuff to fail.
BTW, you can find LG's sources here: http://opensource.lge.com/index
Click to expand...
Click to collapse
Ok, i will make logcat but i never build from source.
I will upload rom today for test.
Ps in rc files in ramdisk i remove # from the lines about sdcard it should fix no sdcard read but it makes bootloop.
Ok, anyway i will make logcat and i'll write here.
If you will have any idea - go ahead.
LOL. 5.0 ported from zenfone with cm12 kernel... hells mix.
You will not fix wifi or camera via rebuilding kernel.
Nikita Pro Android said:
LOL. 5.0 ported from zenfone with cm12 kernel... hells mix.
You will not fix wifi or camera via rebuilding kernel.
Click to expand...
Click to collapse
5.0-5.0.2 api level 21- the same i used kernel from this old cm12 build (5.0.2 base).
I tried add missed lines in ramdisk files but bootloop ;\
I had no time yestarday but today i will try look for logcat.
If no solution by kernel rebuild so how to make it work if rom works nice, much better than stock lg.
WYPIERDAALAAC said:
5.0-5.0.2 api level 21- the same i used kernel from this old cm12 build (5.0.2 base).
I tried add missed lines in ramdisk files but bootloop ;\
I had no time yestarday but today i will try look for logcat.
If no solution by kernel rebuild so how to make it work if rom works nice, much better than stock lg.
Click to expand...
Click to collapse
I meaned that your idea to PORT abandoned android 5.0 (it's the worst version of new material-designed android versions) from another device to our and try to get working all parts (I am underlining word "PORT" again. That rom was BUILT not for our device specifies and have many wrong working blobs).
Nikita Pro Android said:
I meaned that your idea to PORT abandoned android 5.0 (it's the worst version of new material-designed android versions) from another device to our and try to get working all parts (I am underlining word "PORT" again. That rom was BUILT not for our device specifies and have many wrong working blobs).
Click to expand...
Click to collapse
Maybe its worst ver but works better than 5.0.2 from lg.
You meant that is too much differences between firmares to make this port fully working? Even if the calling sound 4g etc works without much firmware modyfing, same cpu gpu.. I though its possibble to make it bug free with KK will be better, more easy or its stupid idea?
Try this values from CM13 write in build.prop , i got less laggy 5.0.2
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
also min free for multitasking i use this down : ps ( @WYPIERDAALAAC will be good to find default values from CM 13, if you know write pls )
ro.sys.fw.mOomMinFree1=49152
ro.sys.fw.mOomMinFree2=61440
ro.sys.fw.mOomMinFree3=65000
ro.sys.fw.mOomMinFree4=70000
ro.sys.fw.mOomMinFree5=80000
ro.sys.fw.mOomMinFree6=100000
and delete line with min processor frequency 7xx , to have default 300mz this prevent owerheat ( if delete Zram have more lag, i keep him)
Sorry for this off topics
Boki11111 said:
Try this values from CM13 write in build.prop , i got less laggy 5.0.2
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
also min free for multitasking i use this down : ps ( @WYPIERDAALAAC will be good to find default values from CM 13, if you know write pls )
ro.sys.fw.mOomMinFree1=49152
ro.sys.fw.mOomMinFree2=61440
ro.sys.fw.mOomMinFree3=65000
ro.sys.fw.mOomMinFree4=70000
ro.sys.fw.mOomMinFree5=80000
ro.sys.fw.mOomMinFree6=100000
and delete line with min processor frequency 7xx , to have default 300mz this prevent owerheat ( if delete Zram have more lag, i keep him)
Sorry for this off topics
Click to expand...
Click to collapse
i'll try, thanks.
today i will upload new version of stock to my rom thread
(still as backup because re-builded system img looks like corrupted when i flash it by twrp,
no problem with system.dat but cant do that with stock system img)

Newbie need answers and its guidance for build rom

####After seen lots of tutorials i know how to build rom and made one
But
There are few questions i couldn't found for google, or difficult to found------
1) how to make lineage os for unofficial device?
2) how to make update build with same rom and latest security patch?
3) how to edit buildprop and updator script once and no need to manual update in updated build?
4) how to solve bootloop related bugs ?
5) how to fix heat related and sensors related issues?
6) is there any script or kitchen which can help me to update or tweak roms from source insted manual typing commands
Thanks in advance

any fix for Blueooth issues in non MIUI roms?

it seems every non MIUI rom bluetooth audio is broken. there are various fixes posted but none built into a rom yet. additionally, none of the posted fixes work for me. has anyone found anything that works?
I have not experienced any problems with audio via BT on GSI AOSP 8.1 or AICP Mordiford.
Maybe you have a problem with this because you have not updated Firmware and Vendor from MIUI.
Not sure but it's listed as not working in nearly every rom
Are there instructions anywhere to update firmware?
Edit - I updated firmware and same problem unfortunately no fix

Anyway to enable on-screen keys on the unofficial (Q) 17.1 Lineage os rom?

Because Android 10 is read only, there was no viable way to enable navbars unless the feature was activated within the custom kernel, which the creator hasn't enabled yet and has since stopped updating the rom. There was hope however on this thread I found (https://forum.xda-developers.com/7t-pro/help/mount-r-want-to-update-build-prop-t4096033) where build.prop edits in android 10 can stick with an .sh extention-write, so I was hoping if someone can post a video/tutorial about just this method as an alternative to editing the build.prop on this rom. Open to other any ideas in the comments below.

Categories

Resources