yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] MarshallCS:
Quick and probably easy question. I've installed and had no troubles with Cmod11 via the installer on my Nexus 5 (straight talk sim.) However every time I try to flash a nightly (even a clean install) I get a com.android.provision has stopped loop that will not let me get to the launcher. Any suggestions?

Thanks
[Nexus 5 Original Android Development] dannyella:
How to??
[Nexus 5 Original Android Development] zimlokks:
How long has the device been on?
[Nexus 5 Original Android Development] MaxRabbit:
I've been giving field reports from 1/31. Currently running 1/31 with non-CAF mod and Franco kernel. Battery life is godlike (see screenshot), and ROM is essentially bugless. I'm very happy with this setup until CM gets the kernel act together.
[Nexus 5 Original Android Development] TheBenz:
How about the sound Problem?

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] zimlokks:
I'm using franco's r33test6 with non-CAF mod and I still have the audio issue.
[Nexus 5 Original Android Development] MaxRabbit:
No sound issues.
[Nexus 5 Original Android Development] TheBenz:
Great! When i tried yesterday, i could not set a lower sond then max ... But ill try again later :) THX

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] MaxRabbit:
What exactly was your issue? Perhaps I just haven't ran into it yet.
[Nexus 5 Original Android Development] Curiousn00b:
http://forums.androidcentral.com/showthread.php?t=356987

Here goes a nice CM11 boot animation that showed up.
[Nexus 5 Original Android Development] TheBenz:
If you listen to music, it plays with maximal Volume all time , what ever the Volumen slider says

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] km00000:
Does anyone know of a way to turn off album art from showing on the lock screen? I would like to have just my wallpaper show.
[Nexus 5 Original Android Development] km00000:
Anyone else not being able to minimize notifications correctly? It is happening with other applications as well; not just Spotify.
[Nexus 5 Original Android Development] RainMotorsports:
Anyone have some earlier builds than the 25th. I accidently wiped my phone in a foolish chase for something and the builds I liked most were only on it.

The 15th was one of them that I really liked, I popped onto M2 for the mean time. But TeamSpeak 3 didn't seem to be working properly on the 25th.
[Nexus 5 Original Android Development] DrunkFuX666:
I'm a little confused... I thought we couldn't use Franco on cm now due to the changes implemented and Franco decided not to go forward with a separate cm kernel soooo... People reporting using r33 with this... A little confused...

Sent from my Nexus 5
[Nexus 5 Original Android Development] j3di:
There is a flashable zip a few pages back that looks to revert the CAF changes so that you can use third party kernels without issues. So you should be able to use Franco kernels without the volume issue.

I haven't used it so I don't know if its works 100%
[Nexus 5 Original Android Development] dannyella:
CM with ART is amazing.. :D
[Nexus 5 Original Android Development] j3di:
Which GApps are you using?
[Nexus 5 Original Android Development] dannyella:
PA gapps micro modular
[Nexus 5 Original Android Development] chris6278:
r33 is out for francos kernel? Can someone please post a link for it? Cant find it in francos thread
[Nexus 5 Original Android Development] Enddo:
its a test. found on his ftp site
[Nexus 5 Original Android Development] lowrider82:
Anyone tried today's build? Mem leak still present?

Sent from my Nexus 5

---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------

How do u get cm with art? What are the differences? Any drawbacks? Does gravitybox work with art?

Sent from my Nexus 5
[Nexus 5 Original Android Development] fleischbanane:
Has anyone a working camera with today's nightlys.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] MaxRabbit:
I use Bluetooth for audio, so I actually cannot guarantee this is not a problem.
[Nexus 5 Original Android Development] kylon:
Yep 0302

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] MaxRabbit:
That is normally a setting within your music app's menu.
[Nexus 5 Original Android Development] km00000:
I'm using Spotify. But I'd imagine it would be a mod that modifies the lock screen.
[Nexus 5 Original Android Development] dannyella:
No just flash.
[Nexus 5 Original Android Development] dpvu:
You can flash with ART. Just know if you have a lot of apps they will all have to be initialized again so don't expect to be up and running for a little while if you use ART.
[Nexus 5 Original Android Development] Jsparta26:
Seems like MMS issues are fixed in this build:)
[Nexus 5 Original Android Development] dannyella:
Switched from dalvik to art in developer settings. ART is noticeably faster. Xposed framework doesn't work with ART so no gravity box doesn't work with ART. Initial boot or when cache is cleared takes too long like 15-30 mins. Also installing apps takes a bit longer than dalvik. Finally some apps have not yet been update to work with ART. Those app will crash. I have 157 apps, no issues with any of them. Other than these, it runs great. Apps open a lot faster like they're in memory.. Try it. If u don't like it, you can always switch back.. :good:
[Nexus 5 Original Android Development] chris6278:
Can u please post a link of r33 or that site? Cant seem to find it
[Nexus 5 Original Android Development] HughesNet:
Restart your phone.
[Nexus 5 Original Android Development] MaxRabbit:
Strange, it seems Spotify does not support disabling the album art lock screen:

http://community.spotify.com/t5/Hel...lock-screen-widget-in-Android-4-2/td-p/567482

Further reading:

http://forums.androidcentral.com/sa...-music-widget-bar-lock-screen-how-remove.html
[Nexus 5 Original Android Development] Enddo:
Franco Test Kernels
[Nexus 5 Original Android Development] Smedo:
Do you use Greenify or an app that kills all your applications?
[Nexus 5 Original Android Development] jdh10475:
(test) Running the 31st after 48 hours without a reboot I have about 200 meg of available ram my phone is become annoying to use.

Yes I know a reboot will temp fix. Just seeing how low it will go.

Update- two minutes after posting this my phone rebooted.
[Nexus 5 Original Android Development] MaxRabbit:
Yea, I've been posting about my experiences on 1/31 and the best thing to do is install the non-CAF mod and then Franco kernel.
[Nexus 5 Original Android Development] j3di:
The Franco beta kernel suffers from the same memory leak problem.
[Nexus 5 Original Android Development] vergilbt:
Is there a themer inside?
[Nexus 5 Original Android Development] km00000:
Yes. I use Greenify. But I do not have Gmail or GEL hibernating.
[Nexus 5 Original Android Development] MaxRabbit:
But Franco stable has been working great for a good month.
[Nexus 5 Original Android Development] slg60:
Please fix Video playback. Some YouTube Videos are shuttering in sound and bring only black screen... No fix since last 6 nightlys...?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Smedo:
Yes

I would advise: clean install. Setup Google account and download gmail. Before you install all your other apps: test how gmail and GEL work...
[Nexus 5 Original Android Development] marcusva79:
So ram leak got fixed?
[Nexus 5 Original Android Development] detdett:
Who told you that?
[Nexus 5 Original Android Development] marcusva79:
No one did. Was just checking.
[Nexus 5 Original Android Development] Mr_Comple:
Not yet unfortunately...stick with the 26th nightly..

sent from a real nexus device
[Nexus 5 Original Android Development] dannyella:
I actually don't have a problem with ram.. Phone works as expected, no drawer redraws. Y'all need to stop checking ram and need to move on with your life and your phine.. Lol:p
[Nexus 5 Original Android Development] marcusva79:
I have went to purity
[Nexus 5 Original Android Development] q1t1:
Just wait an uptime > 24h (without reboot or flash) and then you will check your ram too.

And seeing it < 200mb will make you laugh a little less loud...
[Nexus 5 Original Android Development] sn0warmy:
I know this will inevitably piss off those "OMG never ever ever ask for OTAs!!!!!" people but this is ridiculous...

4.4.2 has been out for almost 3 months now and there still isn't a single release candidate, let alone a stable build? I've had to remain on stock due to bluetooth issues with my car and just about every ROM available and I finally popped back in here to grab the latest stable build to test it out. I was shocked to see the lack of progress and remaining major bugs that you guys are continuing to report. Not to mention that since CM7 every new iteration of CM has had less and less unique features in it. Lately, it takes a new version of Android to get released for the CM team to finally get moving and push a stable build out of a version that is now outdated.

It just seems to me that since starting their legitimate business in late 2013 the CM team has pushed their core fan base to the wayside. Disappointing, to say the least. :(
[Nexus 5 Original Android Development] detdett:
Can you build a stable rom for us to try?
[Nexus 5 Original Android Development] sn0warmy:
Of course not. But I also didn't create a business off of building stable ROMs.

Now that they've chosen to become a legitimate business based off of ROM development then I think it is fair to look at them in that light. In my industry, as well as most others, if you fail to continue to produce what got you to where you are in the first place, let alone continue to innovate with new features, you'll be surpassed quickly by your competitors. CM is failing to produce at the rate they were previously and their current "product" lacks in MANY ways. Especially when you compare it to Cataclysm, Paranoidandroid, CarbonRom, SlimRom etc., who all provide more features and seem to be significantly more stable with less bugs.

It's just sad to see that the CM ROM has become nothing more than a mediocre option that can no longer pride itself on having unique features and being the most bug free.
[Nexus 5 Original Android Development] topgeardave:
Do you ever look at cm's github? The amount of under the hood improvements with CAF assimilation is crazy. Just because you can't see it, doesn't mean it's not there. CM is a very stable ROM with a few bugs. There might not be any stable or RC builds and that's because CAF integration isn't finished yet. Come back in a couple of more months when all the latest drivers have been incorporated. Since CM9 cm has been all about performance, stability and reliability. Adding loads of customisations increases the likelihood for things to go wrong. However it's a free world so flash what you think is right for you.

Just my 2 cents
[Nexus 5 Original Android Development] detdett:
No one held a gun to your head to use the rom.

Did you pay a single penny to use this rom?

:facepalm:

If people are offering positive criticism, it's more than welcome. However, negatively attacking cm is uncalled for.

Go build your own rom if you're so "disappointed"
[Nexus 5 Original Android Development] lowrider82:
Has the cm team aknowledged the mem leak issue? R they working on a fix? Anyone knows?

Sent from my Nexus 5
[Nexus 5 Original Android Development] detdett:
You think? A fix will be released when it's ready.
[Nexus 5 Original Android Development] RainMotorsports:
He is asking if any developer has acknowledged the problem. Just because we are on one of the most supported phones doesn't mean nothing gets overlooked. Someone in the thread might have seen something and he wasn't asking for an ETA just information.

Just like when I started having the Pandora issue and someone spotted a commit that wasn't even pushed yet but was related to fixing the issue. Someone happened know about it and the truth was a developer already knew about the problem.

Personally I have to assume there is more than one Nexus 5 laying around the CM teams desks but hey you never know.
[Nexus 5 Original Android Development] detdett:
He is asking if there's a fix
[Nexus 5 Original Android Development] RainMotorsports:
He also asked that yes that is true. The first question still stands and there is no real reason to beat up on him about it. If he didn't pose all his questions in one post he would have asked them later and that does no one any good. Maybe its just working customer service as a developer but I look at the question that is valid and ignore the rest.

ETA on a fix is when it arrives, same answer every time. Is the issue known... completely different.

I am not seeing any related bug reports in CM's JIRA but its hard to search for such a broad issue.
[Nexus 5 Original Android Development] aldyu:
We'll wait for m3 b4 we can report if the issue still there then.

Sent from my Nexus 5
[Nexus 5 Original Android Development] lowrider82:
Hey detdett, i didn't ask for eta or force anyone. All i asked is if any developer actually confirmed/aknowledged the issue so we can rest assured it will be fixed as it's been more than a week of releases with the same bug. Try to be nicer next time instead of replying like a db.

Sent from my Nexus 5
[Nexus 5 Original Android Development] detdett:
Hey. I'm just replying to your comment about whether or not it will be fixed. Of course it will be fixed... Do you think a developer likes to have bugs in his / her rom?

As you have pointed out, it's been over a week and the bug still persists. Try to put yourself in their shoes. Would you expect you don't know of a bug if people talk about it everywhere?

I will just be thankful for what cm has accomplished thus far
[Nexus 5 Original Android Development] lowrider82:
Oh I am thankful, but it would be nice to see some dev say guys thanks for pointing out, we will fix it. Doesn't matter how long it takes..... Anyway, even with the release of 25th the phone rocks!

Sent from my Nexus 5
[Nexus 5 Original Android Development] km00000:
Well the last couple of pages got heated really fast... Lol

I got my Nexus 5 last week so I am not up to date yet. Still reading. Could someone tell me when the memory leak happened? I would like to go back to a previous build. It seems like it happened around 1/25 or so. More or less what I am asking is which nightly is best at the moment. Battery life isn't really impressing me on the latest nightly. This is making me charge a couple times a day which isn't possible at times. I came from a ZeroLemon on a GS3 so I am used to 2-3 days of battery life.

Also which nightly would work best with Franco Kernel? Or where could I get the non-CAF mod?

I have searches through about 50 pages on multiple threads and have yet to actually find a link to the non-CAF mod.
[Nexus 5 Original Android Development] dannyella:
I doubt any dev know about the mem leak problem or even consider it a problem.. Otherwise, it would have been fixed by now considering how fixes are released fast usually in next nightly..

It's been days now and still nothing..
[Nexus 5 Original Android Development] Chris123NT:
I've poked a few people about it, namely steve, but nothing has been done yet. I have been rolling back the recent kernel changes for my own builds which fix the problem, thus proving the issue is with the last batch of kernel commits.
[Nexus 5 Original Android Development] DrunkFuX666:
Everyone needs to calm the duck down here... Just if its taking more time than your used to for a fix, doesn't mean they dont know about it or don't care or whatever... Its quite possibly a more difficult fix than anticipated won't be merged or reverted till it's 100% fixed or 100% can't be fixed... That's why its called a Nightly... Its bound to have bugs for N amount of days.

There's nothing wrong in my opinion of asking if its been acknowledged, but assuming they don't know about it JUST because they havnt fixed the problem yet is ridiculous... That's like saying the only possible reason someone doesn't do/fix something is because they don't know about it...

Let's all take a breather and chill out... Those who don't like the current build can revert to the 26th build... In the mean time I'm sure there are plenty people who are staying on the latest nightly and will report back as soon as the mem leak is fixed... You can update then... But tilll then... Let's not be so impatient...

Thank You

Sent from my Nexus 5
[Nexus 5 Original Android Development] nh5:
Here's my take, who is really deciding that CAF is the better path to take? Everyone claims its faster and more optimized. Personally I can't believe that Google engineers would have left so much on the table by not implementing the so called changes and improvements implemented by the CM team. All I see is two fragmented environments making development more complicated. These past few days honestly have made me sad to see what CM has done to development recently it just looks like a big convoluted mess from part time freelance developers over thinking development on hardware they played no role in developing but they seem to be forcing what they believe is the best into the wider development community.

That's just my two sense. No hate please!
[Nexus 5 Original Android Development] GuestK00150:
can you post your builds somewhere? Would like to use the latest changes without the kernel memory issues...
[Nexus 5 Original Android Development] topgeardave:
Apparently it's not a memory leak, it's just cm's way of using free ram by caching everything to the ram to make apps load up faster when placed in ram.
[Nexus 5 Original Android Development] kong:
Another alternative would be using Chaos kernel 10.0 beta 8. The changelog suggests that it fixes CM's default kernel’s memory management problem.
[Nexus 5 Original Android Development] lowrider82:
Do i just flash it without anything else? Or do I need to get CAF? If i need caf.. How exactly do I install it?

Sent from my Nexus 5

---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------

Says who? I highly doubt cm would use such a way to manage memory, cause it has exactly the opposite effect... Extreme slowdowns not speeding up.

Sent from my Nexus 5
[Nexus 5 Original Android Development] kong:
Yep, just flash it over. CM11 is already a CAF-based ROM.
[Nexus 5 Original Android Development] lowrider82:
How does chaos compare to franco?

Sent from my Nexus 5
[Nexus 5 Original Android Development] topgeardave:
Neobuddy89. The developer for chaos kernel in the Android development section. He's fixed the ram caching by implementing his own idea in. Give his kernel a try. Make sure you download the latest beta 10b8 which is uploaded on the second to last page. Version 9.2 on the OP is obsolete as it's non caf. http://d-h.st/wDd
[Nexus 5 Original Android Development] kong:
Sorry can’t comment on that. I’ve never used franco’s on CM11 :silly:
[Nexus 5 Original Android Development] topgeardave:
Better performance and battery life is the same I'd reckon. Maybe better under wifi but that's arguable.

---------- Post added at 11:47 AM ---------- Previous post was at 11:34 AM ----------

I understand your point. But the truth is the N5 is an AOSP device where most of the hardware files are released to the public. And because Qualcomm want to control their IP they only kind of release generic drivers to Google. However with CAF Qualcomm can pick and choose which ever files they want to release. Like for example the optimised dalvik and bionic files which were released by Motorola yet Google didn't include it in the N5.
[Nexus 5 Original Android Development] ssauger:
So todays nightly got some kernel changes:

kernel/lge/hammerhead

ea19feb ARM: dts: msm: Increase OCMEM BW request for video decode

e507157 ASoC: msm: hold lock while allocating and freeing ASM clients

60e0d8f ASoC: compress: Update lock for dpcm calls

77ff8fc audio: ocmem: fix the ocmem driver crash during video playback

93cac54 msm: mdss: Check extra mmb allocated to a pipe

936229d msm: lpm: remove redundant assignment

f7f9679 gpu: ion: fix use-after-free in ion_heap_freelist_drain

61e7d07 ion: remove unused function

7e8429c msm: lpm_levels: fix driver compilation issue

a01c4e8 msm: mdss: Reset pipe's mfd parameter during pipe free

9bf4791 msm: mdss: Return suspend without delay in NOTIFY UPDATE

2659f16 ARM: dts: Reintroduce dual config for CPU on msm8974

b72dec7 msm: msm_bus: Modify IB aggregation at master

ae52472 arm: new way of handling ERESTART_RESTARTBLOCK

85128b8 arm: if there's no handler we need to restore sigmask, syscall or no syscall

96b071e cpufreq: interactive: Fix null pointer dereference in interactive governor

d76a9e8 msm: vidc: add sleep of 100us before clock disable

6340940 Revert "msm: mdss: Fix DSI event handler for dynamic FPS configuration"

25543ee Revert "mmc: core: do not reinsert prepeared FUA and FLUSH requests in stop flow".

0ef3ce4 Revert "mmc: sdhci: retune on cmd or data CRC error"

Can someone tell if this is relevant for fixing the mem problem?
[Nexus 5 Original Android Development] Jsparta26:
Obviously. If you look at the top of the page also a senior member also explains its not a men leak but rather the way the memory manager handles cache processes. :)
[Nexus 5 Original Android Development] WoodburyMan:
Bluetooth has been broken for something like at least a week possibly 2 weeks for me. What fixed it for me was running Euroskank builds. http://fitsnugly.euroskank.com/?rom=cm11&device=hammerhead They include a bunch of new bluetooth commits in code review that seems to have fixed all my issues. Before that it would randomly crash and restart, would not pair to my car, and would pair to my Pebble Watch but wouldn't transmit data and other odd behaviors. Seems fine with the new commits.
[Nexus 5 Original Android Development] j3di:
I don't see these on the CyanogenMod code review? Where did you get this info please?
[Nexus 5 Original Android Development] dannyella:
I see a lot of kernel changes in today's nightly 04/02 in cmupdater but not in http://www.cmxlog.com/11/hammerhead/ ... Why is that?:confused:
[Nexus 5 Original Android Development] ssauger:
In CyanogenUpdater (phone) push the nightly, then you get the changelog. I copied i from the changes.txt of the jenkins build.
[Nexus 5 Original Android Development] myfifth:
GPS doesn't work properly, is that known issue for everyone?

Locate was hardly responsive
[Nexus 5 Original Android Development] Chris123NT:
I can post them, but they are a tad modified, I removed some of the CM "bloat". Mainly CMAccount, WhisperPush, CMUpdater etc... And I changed out some of the default walls because IMO the new defaults in CM are horrific.

Plus I have a bunch of cherrypicks etc... But yeah I'll post one later today if you want.
[Nexus 5 Original Android Development] Dani26:
Youtube is fixed in last nightly? Thanks
[Nexus 5 Original Android Development] Jsparta26:
You know guys we give little credence to small touch ups in ROMs. Example would be the new cm easter egg that was implemented. That and the memory fixes. That made my day:)

Now if only cm added center clock and full battery theme compatibility then this ROM would be perfect to me:D
[Nexus 5 Original Android Development] R0axet:
Which easter egg?

Which easter egg are you referring to?:confused:
[Nexus 5 Original Android Development] dannyella:
Mem leaks fixed..opened all apps in phone, i had 1.2 gb ram left.. :))
[Nexus 5 Original Android Development] kong:
I’d wait for at least 12+ hrs before jumping into conclusion… It usually happens after a long period of use.
[Nexus 5 Original Android Development] MaxRabbit:
That's not how memory leaks happen. Imagine a faucet dripping water. At first it doesn't seem like a big deal, but after a few days your basement is flooded ;)

---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------

Are you automating that process of removing all the bloat? If so, would you mind sharing how? Feel free to PM if it is more appropriate.
[Nexus 5 Original Android Development] dannyella:
aiite...i'll keep checking..