Now you understand why i never get in a hurry to report bugs, most of the time 'end-user' find a way to fix by self and share the solution :highfive:
will make this added to CM11-FAQ
[DEV/DEBUG] CM11 debug thread for Falcon
- Thread starter matmutant
- Start date
Now you understand why i never get in a hurry to report bugs, most of the time 'end-user' find a way to fix by self and share the solution :highfive:
will make this added to CM11-FAQ
Now you understand why i never get in a hurry to report bugs, most of the time 'end-user' find a way to fix by self and share the solution :highfive:
will make this added to CM11-FAQ
Thanks man, I was just dying to get back to cm, sorry for being flustered and thanks again for all your help, we need you in the community.
It's not official but many people use m8fix now. See in cm11 thread.
Sent from my Moto G using XDA Free mobile app
I am aware of that but I was just wondering why we are so slow at the official releases.
Sent from my Moto G using Tapatalk
I have a bug in last nightly.. My phone reboots when i try to see a video. I cannot provide logcat because my phone always reboots. Anyone knows anything about that? I need video playback :/
jonnybowley
Senior Member
@matmutant yes this feature works in US stock ROM as of 4.4.2
When will USB audio be added to CM11 for Moto G?
My friend flashed the latest Nightly and he can't make any calls because the call shuts itself off automatically.
Reflashed stock and problem still happens.
He can receive calls and texts but can't make calls or send texts.
Dialer turns the call off automatically.
Any idea?
Reflashed stock and problem still happens.
He can receive calls and texts but can't make calls or send texts.
Dialer turns the call off automatically.
Any idea?
It's a problem with Nightlies 23/07 and after... Flash this fix after the Rom or go back to the 21/07 nightly : https://mega.co.nz/#!SJEGUAJS!ex9mS8z3BIXxauA5L3DsGGt-BIbP-vatTTA2aLS5US8
Yep agreed. Staying on the 21st build. Also builds after the 21st break video playback in SnapChat and Facebook, ain't nobody got time fo that.
I flashed about a month ago and as of today I've no calls, symptom exactly as described bar I can send texts. Last call I made was Saturday, so today is when the issue has arisen (AFAIK dialler has not been updated and rebooting does nothing).
Apparently not. See above.
Could you give further details? Atm I'm travelling so need my phone, so I'm desperate for a fix.
D
Deleted member 5261650
Guest
Well, i'd like to submit a bug which is kind of annoying coz since the 24th July Nightly Release sound does not work on xt1032 anymore. Same on 25th release.
Is anyone working on a fix?
Is anyone working on a fix?
Nightlies are back again as of a recent commit to git!
Sent from my XT1032 using XDA Premium 4 mobile app
Nightlies are back again as of a recent commit to git!
Sent from my XT1032 using XDA Premium 4 mobile app
I just flashed it....
So far it's good...
Data is OK.. Will test the rest...
Update..
Video and audio is OK (for songs... I didn't test for calls..)..
GPS was taking long time to fix position... After changing GPS config file it worked...
I'm using xt1033 from Brazil, but I just have one Sim...
Last edited:
During the call, screen remains off, and I cant disconnect the line...
(xt1033, Dualsim, 1st SIM on call)
This is not happening with me.
I did the tests
1 - Sent a call TO SIM 1 and was able to disconnect.
2 - Sent a call FROM SIM 1 and was also able to disconnect.
Was is OK with you in previous builds?
Can't it be a problem with your proximity sensor?
It worked on m6... But now, it dissapeared on latest nightly too... It strange, but, atm I don't care
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
20CM11 debug thread for Falcon
This thread is related to CM11 for Moto G (Falcon) maintained by Ethan Chen
for debugging purpose, i need this only thread to centralize the data
==> Report bugs (documented) i'll sort them by relevance (importance : low [L]; medium [M]; high [H]) and follow them to Ethan Chen.
Before Asking anything here, please refer to RC-FAQ & CM11 FAQ by @pinguijxy
refer to this post for general commands
- post 2 : known and solved
- post 3 : pending
- post 4: irrelevant
to improve CM11 for Falcon, you could :- post results after following protocols,
[*]help me to set up test new protocols,
[*]give advices about them
[*]suggest things to investigate IF you can prove it worths to
How To Report?
20140819-edit : Please use "Bug Report" button at the top of the thread instead of posting in thread.
give at least :
- model : XT103* ?
- rom build : cm-11-yyyymmdd-NIGHTLY-falcon ?
- kernel build :
- logcat?
- way to reproduce ? (ok this is the best, but not always easy, or even possible to do)
XDA:DevDB Information
[DEV/DEBUG] Official CM11 debug and dev thread for Falcon, ROM for the Moto G
Contributors
matmutant, pinguijxy, CyanogenMod, Ethan Chen
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-08-19
Last Updated 2015-01-1010No major problems so far. RAM usage seems to increase over time like in official CM, but much slower and less predictable. "Lost RAM" drops by 20-30 MB from time to time. It feels like my voodoo "fixed" one of some more problems, but only longer testing will tell.
So here you go. Standard disclaimer, no warranty yadda yadda yadda.
Code:[...] Total PSS by category: 108786 kB: Native 101428 kB: Dalvik 52426 kB: .dex mmap 48599 kB: .so mmap 47478 kB: Dalvik Other 20583 kB: Other dev 15317 kB: Ashmem 13803 kB: .apk mmap 6924 kB: Unknown 4286 kB: Stack 3092 kB: Other mmap 1734 kB: .ttf mmap 170 kB: .jar mmap 8 kB: Cursor 0 kB: code mmap 0 kB: image mmap 0 kB: Graphics 0 kB: GL 0 kB: Memtrack Total RAM: 903272 kB Free RAM: 469660 kB (110976 cached pss + 274788 cached + 83896 free) Used RAM: 373874 kB (313658 used pss + 3608 buffers + 11320 shmem + 45288 slab) Lost RAM: 59738 kB ZRAM: 4304 kB physical used for 15248 kB in swap (131068 kB total swap) KSM: 44048 kB saved from shared 8208 kB 184956 kB unshared; 326004 kB volatile Tuning: 64 (large 256), oom 122880 kB, restore limit 40960 kB (high-end-gfx)
Code:up time: 03:39:53, idle time: 01:56:57, sleep time: 01:35:43
Code:$ md5sum cm-11-20140319-UNOFFICIAL-falcon-test2.zip 690636b7b10bd48bcec4fc9a8116fed6 cm-11-20140319-UNOFFICIAL-falcon-test2.zip
Edit: Test build removed, use cm nightly + zip from here.8
The only commit that needs to be reverted is the commit 1c8afaa0734547907076c45245aa4030a9049ccb with the funny commit message:
Revert "Revert "msm: mdss: Detach mdss iommu on static screen"" commited and authored by dhacker29
This raises for me 2 questions @dhacker29:
- Why was the original commit reverted?
- Why was the revert again reverted?
Apparently when I revert the revert which is a revert (wow, that's a lot of reverts), then I get rid of the lost RAM bug...
Just compiled the current git head with only 1c8afaa0734547907076c45245aa4030a9049ccb reverted, and everything seems to be fine. Let' see how the long-term usage will turn out.7
Yeah I'll put it on the code review, I've just been lazy the last day or two there is one or two extra commits that need to be merged with the update for it to compile, ill get it up there tomorrow night probably.6Im currently trying to reproduce the ram bug on a build I compiled 30min ago. So far I couldn't achieve more than 100 MB of "Lost RAM", currently it's at ~45 MB.
Because someone said the bug happens with all versions since 20140224, I searched for commits in the device specific repositories that were pushed just after this date, especially in the kernel and qcom display repository. What I found were some commits from 26/02 in android_kernel_motorola_msm8226: https://github.com/CyanogenMod/android_kernel_motorola_msm8226/commits/cm-11.0?page=11
I tried to revert those (cc12abf69bf608b1accffb15682bdeecd36aaaa3..6a8acccc9a65df6cd8782d8858003dea75cfa6e8), got an error during compilation and reverted 518351814c0f60c3ffad26bead05624b668c05ee in android_hardware_qcom_display-caf-new as well (git blame helped here).
It seems that there are still some problems, "Lost RAM" does not go below 40 MB and rises sometimes to as high as 95 MB. But maybe that's just normal. I will test the build for some hours/days and report. If I don't get any problems, I may upload it for others to try so we can verify that the bug was introduced by said commits and track it down further.
