yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] aznxk3vi17:
This is the lag I was experiencing (and still am) before. However, I tested and flashed back to the stock kernel and the issue remained. Strangely enough, it only happens to me when the page I'm swiping to is already loaded. I.e., if I'm swiping to a new page that I haven't seen yet, the swipe animation is completely smooth.
[Nexus 5 Original Android Development] omvir:
Gotta sleep. Didn't have enough time to drain the battery today :(
[Nexus 5 Original Android Development] iamsachin:
Subscribed
[Nexus 5 Original Android Development] Wanya79:
Good Morning guys

im on Franco R10 and i lost over 8 % over Night, with everything on, less NFC, Location on Battery Saving, Wifi Scan always disabled. For my oppinion thats too much and my accu drain is @ use too high, i never reach some of the DOT's posted in here

I will attache an Screenshot here from BBS 1.15 Beta 01

can you help me, what is wrong?
[Nexus 5 Original Android Development] franciscofranco:
NetworkLocation wakelock.
[Nexus 5 Original Android Development] b.spec:
First full day on r10 and I'm impressed with the results. Battery is down to 8% and managed to squeeze out 17 hours on battery and almost 5 hours of screen time. Great start!
[Nexus 5 Original Android Development] blacknet101:
Good battery life on r10 hopefully r11 improves but even if it doesn't this is good enough for me since I'm coming from the LG G2 I'm impressed how this kernel can give me this type of battery life :) :p
[Nexus 5 Original Android Development] Wanya79:
Thanks for your reply! Can you recommend me, what should i change, to lower that?
[Nexus 5 Original Android Development] franciscofranco:
Nice to see ya'll happy with the battery life :)

Need sleep, r11's coming tomorrow. Good night!

Disable location reporting when you don't need it.
[Nexus 5 Original Android Development] beaver2233:
This is not the kernel...just the taptalk app...happens on my S4 also
[Nexus 5 Original Android Development] Wanya79:
Sleep well, and thanx again for your Help. I've now disabled Location Reporting, it's called "Standortbericht" in german, i hope i've disabled the correct one. There stands that Google Now and Google Maps use it, i also deactivate Location History..
[Nexus 5 Original Android Development] kuyam:
I don't see a single significant app there.. what do you do for 5 hours with the screen on?
[Nexus 5 Original Android Development] Nocturnal86:
Well thats normal in my opinion especially with everything on I get the same and it seems pretty normal considering all the stuff you have on Google Now always listening Wifi location and battery saving all that except bluetooth and nfc. But who knows maybe it can be improved.
[Nexus 5 Original Android Development] blacknet101:
Well I use Hangouts since its my default SMS app and I'm texting my gf all day. I've taken pictures since we help each other with homework.

I listen to music on my way to work and school and on my way back home.

Installed my apps from the Play Store and also set up my Bank Accounts.

I'm also on TapaTalk and Google+ a lot always refreshing to see new post or new updates. :):sly:
[Nexus 5 Original Android Development] Cheater912:
Amazing. Just about 4 hours of SOT. Too tired to fully drain it!

Sent from my Nexus 5
[Nexus 5 Original Android Development] blacknet101:
Well today is over, same with my N5 :) it's been a good day
[Nexus 5 Original Android Development] msgfromside3:
+1 I have Gravity Box, though.

First of all, I said earlier that UV can destabilize your phone. That was the reason CM kernel hadn't been supporting UV from its stock kernel and I think it was the right decision. If you want to UV your phone, my suggestion is only report the issue when you can repro the issue without UV. I have had three phones so far and I haven't had one with being stable with UV (bad luck?) Maybe franco, you should set that as the bug reporting policy for the sake of your sanity. :)

I saw redraw issue from r32 before. For some reason I don't see it any more, either from r32 or r33. Something else might have impacted, not kernel. Maybe I can try to use camera more, but even so, why is it the kernel issue? I thought camera is in the user land.

PS: BTW, r33 is great. It is snappier and better battery life while sleeping.
[Nexus 5 Original Android Development] Enddo:
No ram leaks with PA B6 here. Maybe its the ROM people are using, or the apps people are using
[Nexus 5 Original Android Development] msgfromside3:
Yeah, I suspect the redraw issue that I saw with r32 was GB issue. Only thing changed was GB actually before I upgraded to r33 and the issue went away before r33 upgrade.
[Nexus 5 Original Android Development] Batfink33:
Yep everything s fine now for me on stock voltage. It was a mess when undervolted.
[Nexus 5 Original Android Development] vcharette:
Battery life on r33 is INSANE. 49% and I am at 16 hours and counting. 23% screen and 14% calls. Thanks [MENTION=3292224]franciscofranco[/MENTION] !!
[Nexus 5 Original Android Development] Tzfardaya:
as, I've said before... :P The "camera mem leak" Isn't a leak... it's google making tweaks to the camera app to stay resident in memory... probably as part of the fixes released as part of 4.4.2 to make it faster... but people want to see a memory leak so they clamp on to this and keep repeating "it's a leak! it's a leak! it's a leak!"

---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------

There's a reason why when I start asking why, what, how, I ask if people are undervolting and underclocking... UV causes problems, UC too much and your phone starts lagging...
[Nexus 5 Original Android Development] b_rangel29:
Myself and another user have been bringing this up to franco ever since i saw it start to happen with the camera on the test 33's. For some reason it was overlooked. I really like the kernel, but i agree with you as well, constantly rebooting is getting annoying.
[Nexus 5 Original Android Development] jd1639:
Help franko and logcat it then

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
So tell us, what are you doing differently than the rest of us to have these issues? (what's happening with the camera?)
[Nexus 5 Original Android Development] b_rangel29:
Opening the camera app, taking a picture/messaging a pic. Causes ram to jump and never releases until reboot.

Also, after opening/using camera i noticed wakelocks with the camera and battery drain.
[Nexus 5 Original Android Development] jd1639:
You're a senior member here ,logcat it and post the logcat here

Sent from my Nexus 5
[Nexus 5 Original Android Development] b_rangel29:
Its already been done.
[Nexus 5 Original Android Development] jd1639:
Cool, then franko will deal with it when and if he can

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
You mean what I tested back on the 14th?

I didn't post my findings for r33 because they just repeated what I had already stated wrt to franco's kernel...

percentage change was identical from r32 and r33 (and stock)

What's happening with the Camera app that you all seem to think is a leak is simply the camera app staying resident in ram, I am assuming that google did that as part of the 4.4.2 camera fix to help speed it up...

Setting android to "no background process" clears the camera app from memory, and the ram usage drops back to pre camera level...

---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------

There's nothing for franco to deal with, franco kernel acts exactly as stock wrt to the camera app that he's complaining about... it's not the kernel but the app that's the "issue"

---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------

Would you like me to run these tests again with r33 and post the results? or is my testing from the 14th enough... r32 and r33 results were for all intents and purposes identical...

or better yet, you follow the methodology I showed, and you do the tests, post your results...
[Nexus 5 Original Android Development] GeekMcLeod:
I've seen the original post, I think a quote, or you repeating your findings and now this.

So I hope the questions about this die down soon. I'm out of town and will be spending most my nights on my phone, on these forums and really hate seeing questions repeated over and over and it happens way too much.

Posted from under your bed.
[Nexus 5 Original Android Development] b_rangel29:
Tzfardaya I'm going to mess around with it a little more and I'll post anything i find.
[Nexus 5 Original Android Development] Tzfardaya:
I know, I've been repeating myself about it since the 14... finally got fed up with it and decided to quote my findings, since apparently they were missed by everyone claiming the camera was leaking... after all it's been 5 days since I ran those tests... that's ancient history in this thread....

sorry about the long quote post then... I know how fun it is to scroll through that on mobile...

I think you've seen the original posts, several comments on them quoting them, me repeating the finding several times since (about 3 or 4 times TODAY), and now me quoting them directly myself... :P
[Nexus 5 Original Android Development] franciscofranco:
I tested the same conditions with stock Kernel and with r33. Both scenarios show me the same results, after using the camera there's a chunk of memory that gets allocated and stays allocated. In my opinion that is related to the improvements on the camera startup time from 4.4.1/2. If the camera memory stays allocated and not freed then Android has to allocate the chunk again, this way the startup, specially from the lockscreen, is way faster. I don't see any change in that behaviour being stock or r33. That said what bothers me greatly is, why should we care if we "lose" 150mb of ram for the camera? We have 2GB...

Another thing, what is that wakelock you speak off? The Kernel driver for the camera does not hold any wakelock when you're not using the camera. What sometimes gets pegged is the camera daemon that is userspace, not Kernel.

If you have other concerns or you want to debate this further be my guest and I'll answer.
[Nexus 5 Original Android Development] Tzfardaya:
THANK YOU!

Maybe they'll listen to you, after all I'm just another user, but you're the developer... :P

Maybe I'm not as concise as you were... that's why they didn't listen to what I was saying. :D
[Nexus 5 Original Android Development] TrenchKato:
The leak issue started with me as soon as I jumped on R 33 @ version 3. I even had and RMA come in and flashed version 5 directly from stock. Different devices same result. I will also add that I don't use the camera at all. They seem to be totally at random. No UV either.

I don't care how much RAM is being used as long as it is released when needed.

[MENTION=470754]Franco[/MENTION], I am not ruling out that I could be doing something wrong. Maybe it's just a badly behaving app. I am just at my wits end as I have even tried going back to the factory image. I really appreciate you taking one more look.
[Nexus 5 Original Android Development] Tzfardaya:
are you still using one of the test 33's or have to switched up to r33 yet? those test versions were known to have memory leaks... it's why it took so long for r33 to be released.....
[Nexus 5 Original Android Development] TrenchKato:
I'm on the official. I've gone back to the stock kernel and use FKU to flash since it came out.

Ot: with Google Voice typing I say FKU. And it types fvck you... :eek:
[Nexus 5 Original Android Development] Tzfardaya:
okay, so you're on the release version, don't use camera, don't undervolt... remind me, what are the issues you're having... (do you underclock? if so, how much)

What are the apps you use immediately prior to the issue?
[Nexus 5 Original Android Development] TrenchKato:
I have GPU underclock and input boost freq at 1.19. I notice it most with chrome and feedly. Or if I'm alternating between social networking apps.

That makes me think. I remember reading something about the CPU reading to be above 1.5 to get the max frequency with ram.
[Nexus 5 Original Android Development] Tzfardaya:
check the ram usage of each app in the developer settings (process stats) if you're on the stock rom after you have your issue, record them, reset your kernel (flash stock, remove the .bak extension from the two files renamed) then use the phone in the same manner that would cause issues on the franco kernel for you, check the app ram stats... compare to the ones you recorded... let me know which apps are different. :P

But odds are that your current issues have more to do with your tweaked fku settings... :P try using the kernel with stock values only for a bit... see if you still have any issues.. (turn off all per app tweaks too)
[Nexus 5 Original Android Development] :
So only a few people have had the issue where the right earphone doesn't work? I have no issue with r33 besides when playing music
[Nexus 5 Original Android Development] Polv89:
Why the max frequency return ever to 960?

XD

Edit. Sorry, i think it's a problem with other applications that have root permissions.

Inviato dal mio Nexus 5 (by Nexusarena.it)
[Nexus 5 Original Android Development] venelar:
Anyone play riptide gp2? I occasionally have instances where the screen becomes unresponsive and the touches do nothing. I can't reproduce it though, was curious if anyone sees it.
[Nexus 5 Original Android Development] TrenchKato:
Will do. I appreciate it.
[Nexus 5 Original Android Development] franciscofranco:
You just answered yourself. The memory needs to be allocated for a smooth camera experience, that's why it stays there for a long time. Other than that as I said a couple posts earlier, I'm at 60h straight without rebooting the device and I'm with 650mb ram used, everything works as it should, there's no leaks anywhere. If there were leaks you would see ram being consumed and consumed and consumed and at this point I would be with 100mb free.

Thermal throttle.

While charging?
[Nexus 5 Original Android Development] venelar:
Not charging.
[Nexus 5 Original Android Development] Tzfardaya:
no issues here, but I only played for a bit...

Do you undervolt, underclock (either the full system or via per app)
[Nexus 5 Original Android Development] venelar:
Nothing. I flash Franco and forget.
[Nexus 5 Original Android Development] jenkem110:
If you still need to undervolt, try lowering the input_boost_freq to 1190000. That seemed to help me and I don't get reboots anymore. I've been doing it since franco raised it for the people complaining about "lag" as I never experienced it to begin with. I'm -75 with no issues so far.
[Nexus 5 Original Android Development] Tzfardaya:
only reason that lowering the input_boost would help is if the -75 was just a little too lean for the stock input_boost... try nudging your UV up by 5 or 10... (-70 or -60 instead of -75)
[Nexus 5 Original Android Development] jenkem110:
Even at -25 to -50 I would get stutters or reboots unless I lowered the input because I guess the waking and instantly touching the screen would take to much power at "stock" input boost. I first noticed the problem when he raised it a couple months ago which is why I tried lowering it. Seems to work for me so I'm sticking with my set up lol :p
[Nexus 5 Original Android Development] vomer:
yup, but I made some slight changes recently to them :cool:
[Nexus 5 Original Android Development] eluspo:
R33 here, smooth like butter. Havent run into any issues at all. Im all stock except the kernel. I really dont understand while some users have problems with the kernel. I have been using this kernel since my n4 and no issues at all. Best combo with it is stock kernel. Once again, good job as always and keep it up [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] Tzfardaya:
that's odd.... why do you UV if I may ask? my phone runs cool enough that I don't bother most of the time (except 300... I have that set to 600...)
[Nexus 5 Original Android Development] TrainNanpaMaster:
I'm guessing you don't do gaming.
[Nexus 5 Original Android Development] Tzfardaya:
nothing heavy... a couple time wasters (unblock me and the like) and The Simpsons: Tapped Out.... :P

I Underclock Simpsons to 960 for battery.... clocking it down that much also keeps the heat down so no uv is needed anyways...

I prefer to uc as much as I can rather than risk uv and system instability.... too many things can start glitching with uv...
[Nexus 5 Original Android Development] eustilou:
Arararagi's screen dimmer module can get the brightness even lower.

It would be nice to have that mod added to the kernel.

http://xdaforums.com/showthread.php?t=2514765
[Nexus 5 Original Android Development] qdoba:
Running R33 with the latest nightly carbon Rom. The battery life is great on standby. The only problem I have is the high amount of RAM being used which slows down the system over time. When I check on my app settings it shows 1.2 gigs of ram being used. I didn't have this problem with R32. I will flash back to r32 to test again.
[Nexus 5 Original Android Development] Savant:
I'm wondering people with the redraw issues and ram issues on what Roms they're using since, I'm using stock and I switched to cataclysm and no problems whatsoever. People should post what ROM and setup with ram issues and the like.
[Nexus 5 Original Android Development] Tzfardaya:
do you undervolt, underclock, or make any changes via fku?

---------- Post added at 09:32 PM ---------- Previous post was at 09:27 PM ----------

I think that the problems everyone is having has more to do with their tweaks that worked with r32, but cause problems now on r33 because of the sheer number of changes between the two kernels...if they would just clear their fku settings, leave them at default, the problems would go away....

afterwards, they can start tuning for the new kernel.

franco already stated that uv settings from r32 may or may not work on r33... (I think that just because their phones aren't rebooting right away, the UV is still causing errors ans glitches in their systems)
[Nexus 5 Original Android Development] Savant:
[MENTION=4860519]Tzfardaya[/MENTION] yeah people are stuck in their ways with certain things and being hard headed.
[Nexus 5 Original Android Development] krazeecracker:
What are the slight changes?
[Nexus 5 Original Android Development] fleen:
I would like to offer a sugestions for the fku app.

In the voltage control you got the +25 & -25 global controls what do you think and if its possible to make it something like a text box where you input the value like 5 and then 2 buttons for +/- so you can easily control smaller global changes?

You can also make it a max value and a default value of 25.
[Nexus 5 Original Android Development] Enddo:
Is RAM leaking even a kernal thing? Sounds like it would be more of a ROM thing
[Nexus 5 Original Android Development] Tzfardaya:
depends what/how it's leaking...

memory management is likely a kernel task, but leaking apps and rom frameworks are userspace.. :P

the various 33 tests should have shown that ram leaking can have a kernel cause.. :P

But I don't think that franco make many changes to that system (if any)
[Nexus 5 Original Android Development] aswinrulez:
My screen flickers at times. Running r33..i made no changes to kernel settings
[Nexus 5 Original Android Development] Tzfardaya:
color shift or backlight?
[Nexus 5 Original Android Development] amphi66:
In less than brilliant ambient lighting N5 Auto-brightness will cause flickering. Try setting brightness at a fixed % and see if it stops.
[Nexus 5 Original Android Development] franciscofranco:
In theory its an alright idea, but that would be overly complicated for 90% of the users and something I don't look forward to.
[Nexus 5 Original Android Development] aswinrulez:
Auto brightness was off

---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------

colour shift happens.Not just black
[Nexus 5 Original Android Development] foxdigital2k2:
Pretty cool
[Nexus 5 Original Android Development] fleen:
True never underestimate the stupidity of the human race.
[Nexus 5 Original Android Development] Nocturnal86:
Franco just had a kernel panic

http://pastebin.com/EpfXtZYJ

Im stock r33 beta FKU Gravity Box Xposed UV -50 and 650mv at 300mhz and nothing different than before. I was using the phone fine and went into Chrome then it locked up and showed the rendering of the page clipping like it was interlaced and then the phone just rebooted. I have the full log if you want it just let me know.

I read that UV might be causing issues do to the changes in r33 so Im gonna go stock voltages and see how that goes but that kernel panic was weird and Ive never had one ever on one of your kernels.
[Nexus 5 Original Android Development] Seadra:
So any updates for the headphones issue franco? I am on cata+francor33 , will going to stock+r33 will solve this?
[Nexus 5 Original Android Development] gee2012:
There is a thread with pre-rooted stock roms http://xdaforums.com/showthread.php?t=2557523, you can flash it in recovery and restore the apps with TB or Helium after the flash. Backup Cata and just try it.
[Nexus 5 Original Android Development] harshalkatakia:
UC to 960Mhz, UV -75 on all steps and not one reboot in the last 48+ hours.
[Nexus 5 Original Android Development] ali262883:
Does Franco kernel come with pre-loaded sound enhancement mod?
[Nexus 5 Original Android Development] i860:
For me flashing again ( auto flash 33 from fk ) with the headphone in will do the trick. Cata + franco r33 and http://xdaforums.com/showthread.php?t=2532788
[Nexus 5 Original Android Development] androidsnax:
[

Just to say guys - I had this issue exactly when coming from R32 to R33 on Cataclysm ROM. I did a full wipe and reinstalled the ROM and the issue is gone. Had NOVA launcher closing, starting etc etc ("redraws"?) - Im not too clued up on my terminology! I had planned to get logs and post etc but thought Id better try a clean start... seems to have worked so maybe give that a bash if you havent already? (Unless the F man wants logs etc....)
[Nexus 5 Original Android Development] aswinrulez:
I was able to replicated the issue. If i tilt the phone backward suddenly and then forward like seesaw, then screen flickers.

And i am having issue with the proximity sensor i guess.I dont know if it is omni rom problem or kernel problem. Even if im on call and eventhoug screen turns off , the touch still remains active..i can hear the keypad sound and dial pad sound while on phone. When i hang up the call i would see many applications opened coz my cheek would have touched the screen and opened them up

Can anyone help me?.
[Nexus 5 Original Android Development] ali262883:
whats the best settings of cpu, gpu and threshold for playing games.. there are slowdowns in games like aphalt 8, nfs most wanted ..
[Nexus 5 Original Android Development] alanwyl:
The performance governor, why else would it be there. And don't undervolt.
[Nexus 5 Original Android Development] ali262883:
Ok should i change from ondemand to performance?
[Nexus 5 Original Android Development] The Gingerbread Man:
Check out my learner lounge thread, page 23 device settings. Games slow due to thermal throttle, just use per app modes underclock a bit 1728 MHz for instance

Under volt is fine as long as people are sensible and don't expect miracle

You can only choose performance or interactive
[Nexus 5 Original Android Development] ali262883:
I don't undervolt.. Will setting governor to performance help in smoother gaming?? And please also link ur learner lounge thread
[Nexus 5 Original Android Development] KuChar_:
yes.
[Nexus 5 Original Android Development] ali262883:
Okk thank you :):thumbup:
[Nexus 5 Original Android Development] KuChar_:
[MENTION=4437173]Piereligio[/MENTION]

any news about your color profile? :)
[Nexus 5 Original Android Development] xtcdk:
everything smooth . beanstalk r33

hammerhead/yuga/meow/DU/Cyanfox/Beanstak user
[Nexus 5 Original Android Development] The Gingerbread Man:
It just forces Max speed to the CPU, its expensive in battery life for prolonged use
[Nexus 5 Original Android Development] Piereligio:
Testing it. ;)