Develop Bugs

Weird CM 11 and CM 11 based ROMS issue with calling

Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex

nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM

I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.

I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.

Is it fixed yet? Any news on this?

Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?

Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.

Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.

I installed the stock rom after this issus. I think the stock rom has a good battery life.

cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!

Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?

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

[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?

screen flickering or glitches on custom Roms (LOS & AOSP )

screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?

A logcat sent to the ROM dev might be an idea.

Kaleem_qadir said:
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
Click to expand...
Click to collapse
Wrong firmware

XDRdaniel said:
Wrong firmware
Click to expand...
Click to collapse
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?

Kaleem_qadir said:
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Click to expand...
Click to collapse
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.

tnsmani said:
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
Click to expand...
Click to collapse
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?

Kaleem_qadir said:
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Click to expand...
Click to collapse
Unless it says Unified or 3/3T, they are different and flashing the wrong one can brick your phone.

Still not solving
I am still having issues. My nav bar gets a mirror effect on the uperside of the screen
I have a Oneplus A3000

Hello i have the same issue have you got any solution ?

I replaced my crack screen last month and last night I tried flashing AOSIP rom (From latest Open Beta) and got screen flickering and glitches to the point it was unusable. Wiped my phone clean again and tried RR rom and got the same flickering and glitches. Now I'm back to latest Open Beta. I wonder wether my new screen is the problem that caused me unbale to flash aosp roms? Because before my screen cracked I tried almost every rom and it's fine. Any idea guys?

I have the same problem, and I do too had my screen replaced, but some folks on OnePlus forum said that never replaced the screen
I tried many diferent versions of the firmware, and nice looking none fix for me

I have the same problem too, I've tried many kernels and many ROMs, it seems that only Sultanxda's ROM and Official ROM can be used. I've tried to compile MoKee with Sultanxda's Kernel source, it worked perfectly too. So I think that there maybe something kernel related is broken, and only Sultanxda fixed that. Maybe you could try it.

Thanks for reply . Los 14.1 and miui 9 are also ok

I've the same issue, and I think for the same cause because I replaced my cracked screen also, maybe OnePlus 3 have something like knox on samsgung where it'll be broken when rooted, Waiting to see if there's some kind of a solution because if the OOS (or OOS Beta) works fine it could be a kernel or firmware issue.

So it looks like the problem is with the replacement screen. Funny, because this is the 2nd time I replaced the screen (dont ask) but I didn't have flickering problem with the first one. Hopefully any talented devs can figure out the issue and resolves it, will gladly help however I can.

The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.

Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
thanks a lot .. i wil try this weekend for sure

Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.

rsm23 said:
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
Click to expand...
Click to collapse
Well, by "next" I mean builds from 20180309 onwards.

Tried the 12-03 release, it does fix the screen errors, touch stop working if the screen is turned off, I need to reboot to it work again

Fingerprint gestures occasionally stop working in new ROM versions

A month ago or so I updated my CrDroid 5.3 to a newer version and I noticed that sometimes my FP gestures stop working. I then flashed LineageOS, same thing. Also tried AospExtended and Resurrection.
In each ROM the gestures work for a few moments and then the button just stops registering. I need to press and hold it for a few tries, like 10 seconds or so. It then starts working again, but stops again moments later.
So I wonder if I am the only one with this problem. I clean flashed each new version. I wonder, does it maybe have to do with some new security update regarding fingerprints? I can imagine all ROMs include the newest security patches.

Same here. It's a weird bug! sometimes clearing the cache will fix it, sometimes not.

Anyone have a permanent solution?

I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
Thanks, I'll check this one out.

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
In the latest version of Havoc and Syberia, this error has been fixed

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
Dude. That ROM doesn't even have FP gestures. I just wasted my time on installing it. Its colors are also oversatured and it doesn't even have other color profiles. Why did you suggest it..?

kerelberel said:
Why did you suggest it..?
Click to expand...
Click to collapse
Because I'm still using it and there is no problem for me so far

alirazaagha said:
Because I'm still using it and there is no problem for me so far
Click to expand...
Click to collapse
It doesn't have FP gestures..

kerelberel said:
It doesn't have FP gestures..
Click to expand...
Click to collapse
I installed BL first time with nano gApps and there was no problem. I later tried Evolution X ROM for a change and didn't like it for few reasons. Then came back to BL. This time, I installed Pixel gApps. During setting up the phone, I misspelled my email address and when I tried to adjust it by going back, the FP didn't work. I rebooted the phone and since then, there is no problem. TRY REBOOT ONCE!
You can correct colors through Kernel Adiutor though.

I run LineageOS 16, and sometimes after a update, the FP gestures are not working. In LOS there is a menu to switch it on/off. Switching it off and then back on resolves the issue for me (but in the recent updates, I didn't encounter the issue, maybe it was fixed).