Develop Bugs

[ROM][5.1.1] CM12.1 Official Nightlies for Find 7A/S

Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:

Somebody successfully flashed it ? It works ?

raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.

Anyone tried 20150119 build yet? is it working??

CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.

It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.

I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small

on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7

sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.

mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app

You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries

Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers

darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.

ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:

Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/

Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )

alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.

Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.

Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?

Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.

WiFi issue: Phone randomly reboots

Hi,
I recently flast the AOSB Kitkat rom (v 1.3.7) on my Galaxy Grand. I have noticed that the phone keeps rebooting many times when it tries to connect to a wifi network. There is no issue once connected or if wifi is off. But only during connection it reboots. I have tried clearing the cache and dalvik but it didn't help.
Any help would be appreciated.

ibshar said:
Hi,
I recently flast the AOSB Kitkat rom (v 1.3.7) on my Galaxy Grand. I have noticed that the phone keeps rebooting many times when it tries to connect to a wifi network. There is no issue once connected or if wifi is off. But only during connection it reboots. I have tried clearing the cache and dalvik but it didn't help.
Any help would be appreciated.
Click to expand...
Click to collapse
Try to flash cm12.1

I really like this ROM and don't want to move to lollipop. Any other option?

ibshar said:
I really like this ROM and don't want to move to lollipop. Any other option?
Click to expand...
Click to collapse
The random reboot is a bug and it never got fixed as dev stopped in 2014
If you want a kitkat rom then you could try AOGP, dev also stopped but it was my ro before switching to lollipop.
If you try AOGP don't get the last build as that had some serious problems, get one before that.
You can read about it in that thread.
This is the one aogp_i9082-KK-NIGHTLY-20141111-0421.zip

RichyE said:
The random reboot is a bug and it never got fixed as dev stopped in 2014
If you want a kitkat rom then you could try AOGP, dev also stopped but it was my ro before switching to lollipop.
If you try AOGP don't get the last build as that had some serious problems, get one before that.
You can read about it in that thread.
This is the one aogp_i9082-KK-NIGHTLY-20141111-0421.zip
Click to expand...
Click to collapse
Oh ok, thanks for the info... If all the kitkat roms have been discontinued, can you please point to a stable lollipop rom that does not have any major issues.

ibshar said:
Oh ok, thanks for the info... If all the kitkat roms have been discontinued, can you please point to a stable lollipop rom that does not have any major issues.
Click to expand...
Click to collapse
I would suggest at the moment AICP R2
After that BlissPop 5.1.1 V3.5 but this has at the moment some cosmetic problems and maybe you can better wait with that one until v3.6 is released

CM 12.1/13 for Oppo Find 7 X9076 / new Display-Panel

I just got a Find 7(s) X9076 and wanted to install CyanogenMod.
If I take one of the official download page (which are all CM 13) the screen shows everything in wrong colors.
I think (so far I read this from the other threads) it's because of a new displaypanel.
Is there any CM that is working for this display?
What is the problem with this panel, when can I install from official CM-Page?
Best regards
gragib

gragib said:
I just got a Find 7(s) X9076 and wanted to install CyanogenMod.
If I take one of the official download page (which are all CM 13) the screen shows everything in wrong colors.
I think (so far I read this from the other threads) it's because of a new displaypanel.
Is there any CM that is working for this display?
What is the problem with this panel, when can I install from official CM-Page?
Best regards
gragib
Click to expand...
Click to collapse
Hi there! I think your best bet is to go and try omnirom either 5.1.1 or 6.0.1 whichever suits your taste.
Currently im running omnirom 6.0.1 on the new panel similar as you and it is absolutely great! I suggest that you should go and try it out.
Cheers!

DingleBell said:
Hi there! I think your best bet is to go and try omnirom either 5.1.1 or 6.0.1 whichever suits your taste.
Currently im running omnirom 6.0.1 on the new panel similar as you and it is absolutely great! I suggest that you should go and try it out.
Cheers!
Click to expand...
Click to collapse
Suscribe, i run omni 6.0.1 and it works like a charm, everything runs fine and fast, great work from Maxwen, thanks man.

roi_xordo said:
Suscribe, i run omni 6.0.1 and it works like a charm, everything runs fine and fast, great work from Maxwen, thanks man.
Click to expand...
Click to collapse
Yeah.. As of right now, Maxwen omnirom 6.0.1 is the best rom for the newer type of lcd panel. Im using it as a daily driver and had not encountered any problems.
Big shoutout and cheers to Maxwen for the rom. :good:

Many THX for all replies!
I have now the omnirom 5.1.1 installed and its running very well.

New LCD + OmniRom = BSoD > Random Reboots // + Spectrum = Random Reboots
Hi guys
I really feel bad when i read your comments, and notice that you all succeed to get OmniRom runing smoothly.
I'm facing random reboots while using Omnirom (Spectrum also) with X9076 new LCD panel, and it get worst when it's charging.
Do anyone know how to solve this problem.
I already tried clean install by flashing last Spectrum (to get latest Modem & Firmware) then wiped all and flashed Omnirom 5.1.1/6.0.1, but it doesn't work
Also i saw somewhere that it will be good to reflash everything step by step so i flashed starting by ColorOS 1.2.9 then 2.0.8 then 2.1.5 then OmniROM but random reboots still occur.
Please guys help me, i cannot stand that anymore.

Hi, which recovery do you use? I flash omni (both versions) with TWRP (full wipes dalvik, cache, etc) and no issues, everything works fine, no bsod's, no reboots...
Cheers

roi_xordo said:
Hi, which recovery do you use? I flash omni (both versions) with TWRP (full wipes dalvik, cache, etc) and no issues, everything works fine, no bsod's, no reboots...
Cheers
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.2 to flash OmniRom, I wipe all (Cache, Dalvik, Internal, System, Data) i only keep raw partitions (to not lose LVM)

otmanes1 said:
I'm using TWRP 2.8.7.2 to flash OmniRom, I wipe all (Cache, Dalvik, Internal, System, Data) i only keep raw partitions (to not lose LVM)
Click to expand...
Click to collapse
I dont understand it mate, we have the same phone (x9076 + r63419 Panel) and the same recovery (2.8.7.2), but in my case this roms works great (5.1.1 and 6.0.1, both roms works fine)
Did you try to format data? Backup what you need and in the wipe menu, instead of wipe, try to format data, then flash the rom, the gapps, and wipe dalvik cache only before reboot. I dont know if this will work to you, but is the only thing I can think of...
I tried Spectrum rom too, and except for the known issues (camera, gps icon, etc..), everything else works right, no bsods, no reboots...
Good luck

gragib said:
I just got a Find 7(s) X9076 and wanted to install CyanogenMod.
If I take one of the official download page (which are all CM 13) the screen shows everything in wrong colors.
I think (so far I read this from the other threads) it's because of a new displaypanel.
Is there any CM that is working for this display?
What is the problem with this panel, when can I install from official CM-Page?
Best regards
gragib
Click to expand...
Click to collapse
this will work on new screen display
http://pan.baidu.com/s/1gevNd1D#path=%2FOPPO%20Find%207%2FCM12.1-Find7

QTeknology said:
this will work on new screen display
http://pan.baidu.com/s/1gevNd1D#path=%2FOPPO%20Find%207%2FCM12.1-Find7
Click to expand...
Click to collapse
Hi. Can you confirm that version works in panel R63419? I tried soooo many nightlies from cyanogen and so many other roms with cyanogen based and no one works...

roi_xordo said:
Hi. Can you confirm that version works in panel R63419? I tried soooo many nightlies from cyanogen and so many other roms with cyanogen based and no one works...
Click to expand...
Click to collapse
Tried It ?
Inviato dal mio Find7 utilizzando Tapatalk

QTeknology said:
Tried It ?
Inviato dal mio Find7 utilizzando Tapatalk
Click to expand...
Click to collapse
No i dont, i dont like to waste my time... i am sure that no one ROM based in cyanogen will work whit our panel. Try Omnirom, is the best ROM for the find 7

roi_xordo said:
No i dont, i dont like to waste my time... i am sure that no one ROM based in cyanogen will work whit our panel. Try Omnirom, is the best ROM for the find 7
Click to expand...
Click to collapse
that link is from wuxianlin, the best developer for find7 and oneplus.
It's a special version of cm12.1 released unofficially later the end of cm12.1 for find7 and it's for new panel.
I don't waste my time too, I have older panel so I don't have reason to flash It.

[ROM][2016-10-27][Quarks][CM 13.0 Unofficial][6.0.1]

Latest update: 2016-10-27 To view a changelog, you can visit http://www.cmxlog.com/13/quark/ for a rough idea up to the build date.
Hi all. I was able to compile this stock build of CM 13.0 thanks to the efforts/hard works of Skrilax_CZ, baybutcher27, the folks who created Resurrection Rom Remix, and those over at CyanogenMod. It takes some minor features from Resurrection Rom apparently (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock CM 13 and I use this daily. I and the other authors/devs assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings->Cellular networks->Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
My recommendations to install:
Install TWRP 3.0.2 if you haven't already: http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
Perform a backup of your current system/ROM (not really needed if just flashing a newer version).
Perform a factory reset/wipe (if coming from another ROM). If not coming from another ROM, still safest to do a dalvik/art cache reset.
Install the .zip
Install the appropriate google apps (http://opengapps.org/ , ARM, 6.0). I would think nano or micro is best.
(Optional) Install a custom kernel. The best at the time of this writing are at:
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526 (CM-NX-RR-M builds for Marshmallow)
The latest is here: https://www.androidfilehost.com/?w=files&flid=50122
Wipe dalvik/art cache if you install another kernel.
Reboot and enjoy
Kernel Adiutor is very good for performance/power saving adjustments:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
If you are using bhb27 kernels, then you should use his version of Kernel Adiutor:
https://www.androidfilehost.com/?w=files&flid=48767
Here is the link to the latest ROM on the hosting website:
[2016-10-27]https://www.androidfilehost.com/?fid=457095661767104611
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=52716&sort_by=date&sort_dir=DESC
I'll be back to post updates fairly regularly (~every 1-2 weeks), but I also work full time in addition to being a Dad (those of you who are know how that is ) and won't really be able to response to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232 (device, vendor, and kernel trees). Thanks and God bless.

I just flash this version and its absolutely amazing.
Good job devs!
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...

I have been tempted to flash this all day, but I love how smooth my phone has been on resurrection remix and I enjoy the extra customizations it has. I'm eagerly awaiting the next resurrection remix build for all the latest git changes

emi.guego said:
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...
Click to expand...
Click to collapse
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.

calsurferpunk said:
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.
Click to expand...
Click to collapse
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.

emi.guego said:
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.
Click to expand...
Click to collapse
Yeah that sounds like the stock cm kernel then if you didn't flash anything like that separately. I don't know if it would help, but you could always try the other kernel I posted about and see if Android Auto works (would have to restore your backup if you didn't want to keep it). It just depends how much you care and if it's worth staying with the ROM to you. There's obviously bound to be some bugs, but I enjoy using a lean version of the latest and greatest system. Thanks for the feedback .

Installed it 2h ago, everything is running fine so far.
This is smoother than the old cm and than rr too. I'm impressed!
I'm using Bhb Kernel.
My phone is turbo charging, led is working...
No bugs for me.
Nice job, mate! I'm glad we got a new cyanogenmod that we can have updates. Keep strong!
Enviado de meu Moto MAXX usando Tapatalk

thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much

Maro' said:
thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much
Click to expand...
Click to collapse
I've just been going under the built in privacy guard and setting advanced permissions to where apps I don't need to start at boot are denied, in addition to also denying a lot of them from being allowed to keep the device awake. I get very little battery drain in standby this way. If the cell signal is too weak though, it's really hard to prevent extra drain as it over compensates to get a good signal.

Updated ROM to CyanogenMod 13 changes as of March 24.

calsurferpunk said:
Updated ROM to changes as of March 24.
Click to expand...
Click to collapse
Changelog?

Debuffer said:
Changelog?
Click to expand...
Click to collapse
It's a little hard to say since there is a lot and I am just syncing to the main CyanogenMod 13 repository. However, this is a good link if you go by the date and something similar (such as the Nexus 6 which shares a lot of hardware).
http://www.cmxlog.com/13/shamu/

This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.

calsurferpunk, can you fix wifi on XT1254 with stock Brasil 1225's 6.0.1 ROM? CM12.1 and CM13 detect Moto Maxx and Droid Turbo radio very good!

*GPS*
working for U guys? For me not (BB kernel, location: Europe)

soccertolive said:
This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.
Click to expand...
Click to collapse
Your assumption is correct. I don't believe this has ever worked with CyanogenMod. I'm on Verizon and haven't seen it.

Maro' said:
*GPS*
working for U guys? For me not (BB kernel, location: Europe)
Click to expand...
Click to collapse
I had this problem on other ROMs as well until I restored the original manufacturer ROM, set GPS to device only, verified it worked, then flashed the new ROM. You might have to do the same here. I believe it's been a long ongoing bug with CyanogenMod (and probably others).

pretty thx for the cm13,did it have ambient display?

I am downloading this at work right now. It is slow and will take me a couple to download.
While it is dl'g, I have a question about wiping. Do I still need to do a factory reset if I am coming from a marshmallow cm13 RR rom?Baybutchers?
Also, I have not been able to get my GPS to work properly. In your post #17, you referred to original manufacturer rom. Where can I get this rom to set the gps? I do have computerfreek's room saved as a backup if I could use it? I don't have easy access to a computer to do a fastboot.
Thx.
Sent from my DROID Turbo using Tapatalk

Wait, ROM was updated to day 24?

cm14.1 nightly official, Echo in calls

I understood echo was corrected in cm14 10/11 official nightly.
I am still suffering that badly, or did I misunderstood the fix?
Sorry!

Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.

1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I did a clean flash & test it, no luck
Also the same, when restore my data from backup with TWRP... As expected.
What I mean is people in the other end hearing bad echo.

mjkoira said:
I did a clean flash & test it, no luck
Also the same, when restore my data from backup with TWRP... As expected.
What I mean is people in the other end hearing bad echo.
Click to expand...
Click to collapse
I just tried in my car thru Bluetooh system.
It´s working fine there, no echo.

1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I believe that fix corrected the problem of zero audio coming through in calls, which happened after the official build was out.
Sent from my ONEPLUS A3000 using Tapatalk

1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I'm still getting echo in 11/11 build

The problem still persists in the 11/11 build, but it's only when using the speakerphone.
Sent from my ONEPLUS A3000 using Tapatalk

I just read about someone having no echo without flashing Gapps, then after flashing Gapps he had echo. Could be Gapps issue?
Sent from my OnePlus3 using XDA Labs

Doesn't appear to be. I'm on an unofficial 11/17 from https://nyyu.tk/cm/ (got impatient awhile back), with pico gapps but I also tried "Banks" when cm14/14.1 wasn't official yet. My location/service provider are T-Mobile USA close to Seattle, WA. My OP3 was purchased in mid-June, model A3000, current baseband on firmware 3.5.5 ".0.c1.9.2-00004-M8996FAAAANAZM-1".
Every couple days when I update I wipe the cache, dalvik, and system partitions, then reboot twrp prior to installing the updated CM and pico gapps. When I'm on firmware 3.2.7 it's less than when I'm on firmware 3.5.5. I have tried bringing my phone back to almost complete stock (thanks to the unbrick guide), then tested gapps/no gapps, 3.2.7/3.5.5 firmwares, different versions of twrp, clean/dirty flashes, official/unofficial builds.
When in Bluetooth it's fine, wired gaming headset it was reduced until a certain distance from caller (one room away), headset audio was low echo but speakerphone was so bad the caller had to hang up it was starting to cause a reverb.