Hello,
I've been using Official CM 11 for a while because of the OTA Updates and less bugs, but I have a problem.
(asked on CM Forum and got no answer)
There is a bug in video which is taking place when I'm opening or closing an app. It's like there is no "VSync", the image gets teared.
Tried Agni Kernel, no succes.
Does anyone know why is CM 11 doing that? It happens no matter what I try. Thanks in advance!
Related
Unfortunately I don't have rights to ask on http://forum.xda-developers.com/showthread.php?t=2540250 ([ROM] CyanogenMod 11.0 - VILLUMINATI - December 7, 2013) so I'm creating new thread here.
Yes, I did my best to search the question, but cannot find anything related.
I used CM10, CM10.1, CM10.2 so I know what I'm talking about. I did NOT have the issues in these ROMs.
Current CM11.0 ROM dated by Dec. 7, 2013
Yesterday I've tried CM11.0 and found some issue which I cannot find mentioned anywhere.
1. Camera:
When I try to record video with [HD 720p|HD 1080p] resolution the picture is freezing after start of the recording and camera hangs.
I have to reboot my smartphone to get the camera (photo or video) working again.
I CAN successfully record video only with SD 480p resolution.
2. Slow Settings menu navigation (if compare with CM10, CM10.1, CM10.2).
Scroll is a bit slower, it's not critical.
Entering to a menu (for example About phone) is a bit slower - not critical but I don't like it.
Exiting from a menu (for example About phone) is MUCH slower - it's critical and very annoying.
Any idea ?
Did anyone have these issues ?
Currently I've downgraded back to CM10.2 (Andriod 4.3.1) where everything is fine.
Q&A for [ROM+KERNEL][4.4.4] Stable CyanogenMod 11 [October 5, 2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
contacts issues
I am unable to import my contacts. I have tried to do so from my sim and also from a vcf file on an sd card. when trying from sim it simple doesn't work no message, nothing. When trying from the vcf file it says downloading and then nothing shows up once it says it is complete. I have verified using cm10.2 that the sim is readable (it works to get contacts there) and the vcf file is readable there also. I would love to use this rom but this issue makes it unusable not just a glitch. This is with the 9-23 version. I have also been unable to install the oct 5 version. I simply get install aborted error I have verified the sums and still con't install. Thank you for any help.
T989, Running 4.4 Stable, Calling doesn't work?
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Zzchechi said:
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Click to expand...
Click to collapse
I'm having the same problem. I can fix it temporarily by re-flashing the ROM, or even just going into recovery and wiping cache and dalvik cache. But after a day or so, the problem comes back. I know it's not a hardware mic/speaker problem because Hangouts calls work fine. This is very vexing.
I'm running CM 10.2.0.
Zzchechi said:
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Click to expand...
Click to collapse
pixbuf said:
I'm having the same problem. I can fix it temporarily by re-flashing the ROM, or even just going into recovery and wiping cache and dalvik cache. But after a day or so, the problem comes back. I know it's not a hardware mic/speaker problem because Hangouts calls work fine. This is very vexing.
I'm running CM 10.2.0.
Click to expand...
Click to collapse
Using Hangouts Dialer or video recording with the newest version of Snapchat causes this issue.
Sultanxda said:
Using Hangouts Dialer or video recording with the newest version of Snapchat causes this issue.
Click to expand...
Click to collapse
I uninstalled Hangouts Dialer, and have never used Snapchat, and I still have this problem.
Glad to have the Sultan back!
Hi Sultan,
I cannot post yet in the Development Forum but I am very glad that you are back developing again for the Hercules. I really love your ROM and Custom kernel.
Hercules 4.4.4 sultan issue 4x msaa
Hi I need some guidance, 4x msaa Will not save after reboot Along with many dev options also miecraft will freeze and reboot it 4x msaa is not on I was thinking permissions were incorrect but I tried some stuff to no avail. I can't help but feel there is a simple fix, plz help as I love this ROM and sultan and ghost and others work?
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?
I've been trying to figure out what is the best ROM for Note 2 N7100, I have tried a few below but even the stable versions have some issues.
1) Paranoid Android
-4.45 [STABLE] (Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly)
-4.43 [STABLE] (Screen black out unexpectedly)
2) CYANOGENMOD
-11 [SNAPSHOT M11] (Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly)
-Nightly Build (They are nightly so can't complain)
NOTE: CM 11 NIGHTLY (December 3, 2014), that build is very stable as compared to other Nightly builds.
3) SLIMKAT
4.4.4 Build 8.0 [OFFICIAL] (Sync Issue, Apps purchased in Google Play not downloading, Wifi Issue)
4) DN4
I know this is a very new ROM and they haven't released a stable version, but even after flashing the patch, it throws a lot of error.
5) PAC MAN
Nightly Build (August 25, 2014) This ROM I found very amazing, high in performance and awesome battery life. But it has the same issues as CM & PA: Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly.
6) OmniROM
I didn't get a good chance to go through this ROM, but it got stuck at sync as well. So removed it.
One thing very common in all these ROM's is when charging the phone in Power Off mode, the battery Icon is stuck and the phone hangs. Although, the phone is charging, but it won't start through the power button. You'd have to remove the battery and put it in again.
Any suggestions about a very stable ROM for N7100? (No TouchWiz! )
P.S: This is my first post, so please excuse any errors.
So I installed CM 13 on my G3 when it first got out, and it was full of buggs but very fast. I want to install a newer version of CM 13 again now. Did they fix the bugs? Thanks
A number of bugs have been fixed. You can view the CM13 changelog for the G3 here (change to whichever model you have)...
http://www.cmxlog.com/13/d851/
Do you know if CM13 fixed the bug relating to bluetooth low energy mode that was an issue in all 5.X AOSP roms? I'd really like to be able to use my heart rate monitor. I'm on a stock-based rom until then.