yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] nickmv:
I'm curious as to why you think it's not the kernel, when uninstalling franco kernel and going back to the stock kernel fixed the problem. Also, I'm not going to do a full wipe, because i just did that last week. I've had several RMA's to get a proper Nexus 5 over the past few weeks, and the one I just sent back last week developed this same issue right before I sent it back (RMA for unrelated reasons). I ended up starting over from scratch and it fixed it, but I didn't have enough time to thoroughly test to see if the problem would come back, since I had to ship the phone back.

This current phone is on a fresh from-scratch start as well, so there's no need to do yet another full wipe. I want to be very clear to state that I'm NOT running off a restored backup from TWRP, etc. This is a 100% from-scratch start on the phone, and I installed each app from scratch, not from backup.

All I know is that uninstalling franco kernel FIXED it, period. I can't imagine how it's NOT the culprit, based off of that. I also should mention -- trying to use the FKU app while those problems were going on yielded nothing. I could launch the app but a gray screen all I'd see in the app. No text, no menus, nothing. And usually after doing that, a bunch of cascading force closes would occur.

As of now, I'm back on franco kernel and it appears to be running fine, but I have a feeling this same thing is going to happen in about another week.
[Nexus 5 Original Android Development] static416:
So I used the tool suggested here:

And it looks like my last_kmsg.log is filled with "init: cannot execve('/system/bin/qrngd'): Permission denied" right before the phone stops responding. I've attached the log file. It seems to be the same issue quoted below:

I'll attempt to make the same change and see if it helps anything.
[Nexus 5 Original Android Development] nickmv:
Regarding my issues, someone just posted the following on Reddit about it:

"Franco kernel r33 has been found to cause some pretty serious memory leak issues. Which leads to sluggish performance over time and also terrible battery life. Stay away from franco kernel for now. There's also an r34 build floating around xda but it's been having the same issues, too"

I'm curious as to what this is all about, and whether it's the issue I'm having. I would think that if it's a mem leak, then a reboot would fix it. But rebooting does not fix my issue. Only uninstalling r33 fixes it.
[Nexus 5 Original Android Development] coolnow:
The mem leak issue is well known and yes, a reboot fixes it, but your problems sound much more serious. Can you try to install the Linaro kernel (based on franco's) and see if you have the same problems? Also try and clear FKU's app data in case there are some deformed settings. If not, i'd suggest sticking with Faux or something until franco fixes it for you (assuming it's a kernel problem and not a problem of an app or service that interfaces with it). The reason i personally don't see it as a problem with the kernel is that: if it was, then most if not all of us would be experiencing the same problems. It's more likely that it's another app you use, or a setting that's messing everything up. I like to keep my installed apps to a minimum (only keep the ones i use) so there's not many causes for problems on my end.

FWIW, i'm running PA 4.1 beta with r33 and alternate between ART and Dalvik (with Xposed and GravityBox). No problems to report right now.
[Nexus 5 Original Android Development] Testraindrop:
Well apparently some people think there is a memory leak, I haven't seen it yet, but maybe 255 hours ontime is too short...

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] nickmv:
Well that's definitely a long-ass time, but all I know is exactly what I reported regarding crashes, etc.

I made sure to pay attention to what I've been doing on my phone, since the first occurrence of the problem on my phone last week. This time when it happened, I decided to actually get rid of franco kernel, and low and behold, the instant I did that, all the problems went away.

But again, a memory leak suggests that a reboot would fix things. In my case, that was not fixing things. The phone would slowly just get worse and worse, with more crashes, and more apps becoming unresponsive (FKU and BetterBatteryStats being the notable ones). Only uninstalling franco and replacing with the stock boot-img/kernel fixed it. And of course, as I said, I'm back on franco and working fine yet again. But I have a feeling there's a damned good chance that it's going to happen again within a week.

SOMETHING made the phone freak out, and the kernel is all I'm seeing as the culprit.
[Nexus 5 Original Android Development] icbt:
Did someone encounter a FC when you use the FKU / Display control apps after color control -> Load a color profile -> selected the profile :confused:

I have updated to r33 and downloaded the latest FKU.

And I have just changed the phone to nexus 5 from 4
[Nexus 5 Original Android Development] abbz123:
r32 is flawless.

I highly recommended using 32 if you have any errors with 33 or 34.
[Nexus 5 Original Android Development] nickmv:
It's interesting that you mention that. So, last week, right when I was starting to have these problems for the first time, I noticed everything was sluggish, but also that my color profile wasn't applied.

So, I launched the FKU app, and tried to apply a profile (Vomer_Balanced), and it wouldn't do it. Instead, it would always lock up right at pressing Apply, and wouldn't go any further. Didn't work for ANY profiles.

I have no idea how this was related to everything, but it was one of many problems that started occurring before I wiped.
[Nexus 5 Original Android Development] dastinger:
I'm not saying that you're experiencing the memory leak issue and did not notice but something I noticed one of the times I started having launcher redraws and some apps getting killed was that the system settings were not giving me accurate RAM readings. I had enough free RAM in order to have all my already opened apps running and some more. But, when I checked on System Monitor within FKU, used RAM was a lot more than what system settings was telling me.

Also, I don't know for certain that System Monitor was right and system settings wasn't but, given what was happening to my phone, I think System Monitor was, in fact, showing correct reads.
[Nexus 5 Original Android Development] msgfromside3:
Just use camera a lot and everyone should see the redraw issue. I experienced it with r32, r33, r34. It is not kernel related and Google has confirmed the bug already. If you don't use camera a lot, it is likely that you would never see it.
[Nexus 5 Original Android Development] dastinger:
I don't believe the problem is with the camera app only. When I was using r32, I used the camera a lot more than I did since r33 and I didn't experience issues. Not that I noticed at least. I know this because I was in London at the time and r32 was the first version of the kernel on my N5 and I took a lot of pictures... there must be an issue with the camera since Google acknowledged it but I don't think that it's just that. So many things were added to r33 that it's understandable that some of them are causing issues.. but it's also hard to find out which ones are doing it.
[Nexus 5 Original Android Development] P.Mobile:
cant wait to test something new! :fingers-crossed:
[Nexus 5 Original Android Development] Notechis:
Overclocked 34 test ... 1 1/2 days - 5 hrs SOT

not bad at all :)
[Nexus 5 Original Android Development] whitedragonz83:
System Monitor counts used RAM as used+cached. The system settings in Android shows either used or cached, but not both combined. So System Monitor will always show "nearly full RAM usage" I would imagine. This is also how Linux should be operating, minimal truly "free" RAM with most either used or cached.
[Nexus 5 Original Android Development] dastinger:
Oh, never thought of that. Then both are correct... well, don't know what's going on then. When I start getting redraws and apps getting killed, I always have around 500MB free RAM. Probably the cached processes then...
[Nexus 5 Original Android Development] whitedragonz83:
Yeh, it's a bit confusing trying to watch this thread about the issues with RAM since r33/r34. I initially reported a true RAM issue with one of the tests in r33, but since then, it has been a lot of confusion.

App redraws are tough to diagnose as depending what apps were used just previously will have a large effect. I've been on stock for a little bit because I'm still seeing how things behave here a bit more. One thing I was wondering if I just don't notice the redraws (if they are occurring on stock), because it basically is running at 2.3GHz anytime I touch the screen. This would minimize the redraws to almost nothing I assume, compared to the much lower frequencies Franco usually has running when people touch the screen.

Did any touch boost or Interactive changes occur that would make it more apparent between r32->r34? That's something I'd be curious about at least.
[Nexus 5 Original Android Development] Testraindrop:
Now that you mention FKU and BBS crashing, I remember someone reported way back similar issues, it was a problem with Superuser.

Do you use superuser or SuperSU?

If SuperSU, do you use the latest one?
[Nexus 5 Original Android Development] dastinger:
Hum, so what you're basically saying is that redraws could exist on stock but you just don't notice them because the process is faster due to higher clock speeds? That makes sense but I don't believe that's what happens.. it would have been noticed already in other kernels or even stock because the issue is not with redraws only (not with me at least). When I start getting launcher redraws, Widgetlocker starts getting killed constantly so I guess the same thing would happen to other apps too. I notice it happening to Widgetlocker because, when it happens, I lose the lockscreen and go directly to the homescreen.

I think there were changes to the governor but I'm not sure. Anyway, like I said, there were so many things added to r33 that it's pretty easy that one of them (or more) is causing this.
[Nexus 5 Original Android Development] whitedragonz83:
True, Widgetlocker would be very noticeable. It does sound like some change in r33-r34, because otherwise more people would report about Widgetlocker redraws who use other kernels. Very odd.
[Nexus 5 Original Android Development] nickmv:
Man, you keep nailing it on the head. I was thinking earlier that SuperSU may causing issues, but now that I'm back at work, I can't, for the life of me, remember WHY I thought that.

But anyways, in my attempts to fix it BEFORE removing franco.kernel, I uninstalled SuperSU's updates, bringing it back to its "factory" state. Then I reinstalled the updates. It didn't make any difference, unfortunately.

Anyhoo, I'm still running on the newly reinstalled franco.kernel, and all seems well so far. We'll see soon.
[Nexus 5 Original Android Development] Dougshell:
Very happy indeed. Facebook, texting, 3 hour talk time. Some web browsing as well.

Tons of per app settings
[Nexus 5 Original Android Development] engrboy:
I noticed my screen was flickering today. Mainly when I was using my camera would it flicker. Then I had a reboot while I was using Instagram. I am currently running Purity 2/28, r33. Unfortunately, I am using ART which I know doesn't get a lot of support, but I figure I would post the logs anyway. Hope it can be some help.

Last_kmsg - http://pastebin.com/2yeNDx9x

logcat - https://mega.co.nz/#!JMMU2bCL!GlIqFIb6vsXEPcPTmq11K9v8aUthVxAyifCDM3mOYCs
[Nexus 5 Original Android Development] THE_KINGDOM:
Again i'm noticing a lot of bug's in r33. I didn't have any of these bugs on stock.

delayed screen on very very often, data drops, home button lag/black screen for 30 seconds when trying to go home screen.

I'm going to try r32, and if it's not any better I'm gonna be force to go back to the stock kernel which worked flawlessly with Cataclysm.

Really all I want is a stable kernel with fast charge. Stock kernel is stable and fast, add fast charge to that and I'm happy
[Nexus 5 Original Android Development] jumparound246:
...without words. Go ahead and do it yourself.
[Nexus 5 Original Android Development] nickmv:
Define fast charge. The Nexus 5 already has an insanely fast charging system due to the new technology Qualcomm implemented into it. There's not much more that can be done, without sacrificing longevity of the battery.
[Nexus 5 Original Android Development] snives:
Fastcharge is full power charging while on a USB port of a computer/car.
[Nexus 5 Original Android Development] DieGo316:
I'll bet $1000000000 that you are the only one complaining when using this kernel, almost everyone got a stable experience, amazing battery life and 0 lag.

try reflashing the kernel or a full wipe :)
[Nexus 5 Original Android Development] SwiftLeeO:
What is the most stable version (if there is one) reported to work with CM 11? I love stock but I love CyanogenMod, and this kernel looks really nice so I would like to use it with CM if possible.
[Nexus 5 Original Android Development] RobbieL811:
Read the first few lines of the OP.

Sent from my Nexus 5
[Nexus 5 Original Android Development] SwiftLeeO:
Well I did read it. I'm not that stupid. The reason I asked is because I've seen a few people in some threads about what rom and kernel they use for the N5 and they say CM11 with franco. Unless theres another franco.Kernel, then I think my question is valid.
[Nexus 5 Original Android Development] THE_KINGDOM:
ok I may have figured out the problem...

adjusting the CPU in FKU, is causing my phone to stutter significantly. Even only increasing it to 2419MHz is causing massive lag. I believe 2265MHz is stock? Whenever I go back into the CPU manager settings in the app, the max cpu frequency has changed to something different/settings wont sick.

The CPU monitor is also completely inaccurate because it doesn't register half of the CPU frequencies I've tried setting.

I've tried restoring app to defaults, anybody else experiencing these probems r33?
[Nexus 5 Original Android Development] RobbieL811:
I think that there are some packages somewhere that you can flash to make CM compatible with AOSP kernels but idk where they're at. Also, you can use older versions of CM that will work with FK. My advice to you is to find a good AOSP ROM if you wanna use FK. In my opinion, SlimKat is way ahead of CM anyways! Try that one. Works great with FK. Or go complain to CM about breaking compatibility, just please don't be one of the people that end up doing that here! Hope this helps.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Enddo:
you need better battery stats logs for when this issue is happening. until then it will be considered a userspace issue and it's on you/your device
[Nexus 5 Original Android Development] brooklyn718941:
I'm using a complete untouched stock ROM, I can't find the menu to over our under clock any help thanks
[Nexus 5 Original Android Development] paulkono:
franco, I'm curious, are you using stock rom or a custom one? And if so, which one? Thanks!
[Nexus 5 Original Android Development] WettbackMartyr:
Need a kernel tuning app like Franco. Kernel updater (FKU) or Trickster Mod. Both on the play store.
[Nexus 5 Original Android Development] benthian89:
He is a stock rom user since the dawn of time
[Nexus 5 Original Android Development] PetritH:
He always uses stock, he responed this too many times.

oops, [MENTION=3244473]benthian89[/MENTION] beat me =P
[Nexus 5 Original Android Development] Enddo:
fast charge via USB will net you 1000mA charge. full power charging via a wall outlet is 1500
[Nexus 5 Original Android Development] Tzfardaya:
I take it everyone has fallen asleep?
[Nexus 5 Original Android Development] njnets123:
With our phones too
[Nexus 5 Original Android Development] Nbsss:
Quick question, how does the boot.img differ from a boot.zip? Do they both contain the ramdisk?
[Nexus 5 Original Android Development] Tzfardaya:
the way fku is set up, as the phone thermal throttles the max speed currently available is displayed in the app..

the cpu monitor only shows the most used, not all the available cpu freqs...

As you overclock, the cpu generates more heat, the more heat generated, the more the device throttles down to protect the cpu, that's probably where your lag is coming from...

Mind if I ask why you're trying to overclock?

but do you sleep as well as your phone does?

both have the same info... only difference is in how they are installed... the img is flashable using flashify or fastboot, the zip is for use in a recovery.. That's the only difference.
[Nexus 5 Original Android Development] Nbsss:
then why is it that flashing a different kernel zip, its recommended to dirty flash your rom first? I thought this was to restore the stock ramdisk, but this isn't the case?
[Nexus 5 Original Android Development] Tzfardaya:
TBH, I've never heard that recommendation.. :P and the only time I flash my rom is if I bugger it up messing around in files I shouldn't be...

And even then, it's always a clean wipe... full flash, start from scratch...

But, if you believe in dirty flashing your rom before you flash the next kernel zip, then you should do the same before flashing a kernel img.

because as I said... same information, just different presentation.
[Nexus 5 Original Android Development] Nbsss:
i mean between different kernels from different devs, as they may use different ramdisks?

Anyhow, been using these settings for last 3 days with good results if anyone wants to give them a spin. Changing the GPU settings really helps with the microstutters i occasionally get, so been able to use a lower input boost without noticing lag.

GPU Control:

Max: 320

up_threshold: 25

down_threshold: 5

CPU Manager

boostpulse_duration: 300,000

go_hispeed_load: 92

hispeed_freq: 1574400

input_boost_freq: 960,000

sync_freq: 652000

up_threshold_any_cpu_load: 40
[Nexus 5 Original Android Development] Tzfardaya:
It should help with the stutters, while you've lowered the max gpu speed, you've also tweaked it to ramp up faster and stay higher longer.

I usually go the other way... I don't encounter too many microstutters, or if I do, they haven't bothered me. :P

Mine are usually max 400, up 75, down 50, with per apps to modify as needed...

If the new kernel comes with it's own ramdisk, why would you need to reflash the rom's kernel/ramdisk, it would just get overwritten again by the next kernels zip/img...
[Nexus 5 Original Android Development] Nbsss:
Yeah that's why i was confused.

eg.

Edit: maybe he mentions this as franco uses a different thermal driver, which reflashing system would remove?
[Nexus 5 Original Android Development] Tzfardaya:
I can see it being necessary when one custom kernel uses a custom ramdisk and a second used the stock ramdisk... need to dirty flash the rom to get the stock one back...

Even with franco's custom thermals, no need to flash stock,. just go in with a file browser and remove the .bak from two files... (can't remember the exact paths to them right now, but they have been mentioned several times in this thread... or I could dig in my own phone..)

Here's a post with the paths...
[Nexus 5 Original Android Development] Nbsss:
But you said the .zip includes the ramdisk lol

yep i know about the .bak files (its in the FAQ :p)

but reflashing the system is "easier" so maybe that's why he mentions this?
[Nexus 5 Original Android Development] blueren:
Where is franco these days

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
I am only talking about franco's zip/img... I don't use any other kernels... it would depend if the other dev's package their zip/img files with kernel and ramdisk...

In franco's case, his zip and img files contain the same information for the same release... Whether other dev's do the same is up to the other dev's...

as for me, I find it easier to remove 2 .bak extensions than reflash a whole rom image... (I make too many changes to build.prop to enjoy reflashing/re-editing/copying over a backup again)
[Nexus 5 Original Android Development] Nbsss:
Gotcha, so not all devs package the ramdisk with the kernel, but Franco does.
[Nexus 5 Original Android Development] Tzfardaya:
Real life got in the way for a bit, and he needs to spend some time giving loving to the other nexus devices... we can't expect him to love only us all the time... :P

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

I don't know if they do or not... I only use franco's kernels (or stock) and haven't dealt with any other kernel dev...

they might, or they might not... depending on what they think is necessary...

---------- Post added at 09:36 PM ---------- Previous post was at 09:34 PM ----------

Franco might also be taking some time reversing many of the commits between 32 and 33, he did mention he was thinking of reverting all those changes, since they included a lot of caf code which might be where the issues that started with 33 are from, the caf commits he cherry picked may need userspace support and not just kernel support..
[Nexus 5 Original Android Development] vomer:
Busy with schtuff ;) he made a post a while back about it

Sent from my Nexus 7
[Nexus 5 Original Android Development] Enddo:
im pretty sure franco recommends this. you can use the search feature to find the post
[Nexus 5 Original Android Development] rofik_gitara:
anyone use r33+latest PA?
[Nexus 5 Original Android Development] DforDesign:
Hi franco.

Wanted to ask you about F2FS implementation. What do you think about it? Do you have any plans to feature it in your hammerhead kernel?
[Nexus 5 Original Android Development] namurt:
holy crap, the F2FS questions are flying already?!
[Nexus 5 Original Android Development] JNewms:
What is F2FS?
[Nexus 5 Original Android Development] inscythe:
Flash-friendly file system... A simple Google search will give you that in the first result.

I don't think it will be supported anytime soon, as Franco's kernel is all about simplistic optimization rather than bleeding edge stuffs.
[Nexus 5 Original Android Development] JNewms:
Thanks for reminding me about Google, forgot it existed.
[Nexus 5 Original Android Development] m0h1t:
CPU temp threshold

My phone often throttles. I see lot of people recommending that the CPU temp threshold be increased to 70-80 etc.

Is it safe to up it to 70C for daily use?
[Nexus 5 Original Android Development] The Gingerbread Man:
I was going to ask the same thing!
[Nexus 5 Original Android Development] JNewms:
Edit. I'll behave.
[Nexus 5 Original Android Development] FAdrums:
LMFAO

Tapatalked from my Franco Paranoid ARTified Hammerhead