yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Technecium:
It's your baby, Franco. Do what you think is best. You won't hear any complaints from me.

koeASOP 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] mibtnt:
I'm back on r33 with dalvik and PA4.1beta :cool:

As I flashed r33 i noticed the difference to stock.
[Nexus 5 Original Android Development] blueren:
Micro stutters while scrolling / app transition animation is driving me nuts! Bumping the min cpu freq to > 300 doesn't seem to work always.. isn't anyone else noticing this? It's extremely minute but it's still there.. the stutters.. minute jerks.. r34 test, by the way.

To elaborate - open g+/newsstand etc and filling tire finger. It's fine for a fraction of a second and then it has a fits attack. I've already set the boost pulse duration to 550000.
[Nexus 5 Original Android Development] peikojose:
So which was the last version without these evil caf patches? r32? Thanks...
[Nexus 5 Original Android Development] Tzfardaya:
have you tried raising the input_boost_freq? I think a higher cpu speed would help more than a longer hold at a lower speed...
[Nexus 5 Original Android Development] zukа:
Just as an update, I've posted a few times in this thread about what others have called a 'memory leak' that I was experiencing with R33 and R34. I asked multiple times how to generate logs to help Franco troubleshoot this, but nobody was able to tell me how, and most suggested that because they had not experienced this it was probably a rogue app.

Symptoms of the 'memory leak' (if that's what it is) are -

- can only have one app open at a time

- delay in UI animations and transitions, up to 3 seconds

- cannot open keyboard in any text field (due to it being another app)

- force closes on larger apps like Chrome and Kindle

- can only be fixed with a restart

Just to be clear, I was getting amazing battery life on R33/R34, I just had to reboot my phone twice a day or this would keep happening.

I've changed to ElementalX kernel for now and the problem has disappeared. This is the only change I have made, so it's not a rogue app. I hope I can come back to Franco's kernel if this gets recognised or fixed, and I'd be more than happy to try and help troubleshoot if someone points me in the right direction :D

I also bought Franco's great app today to show my support
[Nexus 5 Original Android Development] Tzfardaya:
heh, you're not the only one with the issue, and if you've been following today, franco thinks he might have squished part of it on his local build, he (and others) think that the memory leaks and other small issues have to do with the partial caf implementation he's been using... cherry picking patches and modifications that caf has put out into his kernel. unfortunately, he's only building a kernel, and is starting to think that some of the caf code needs userspace changes as well, (which is why caf distros like cm don't play well with aosp kernels, but franco was trying to walk a line between them, use some caf changes to improve his aosp kernel)

Right now franco is deciding whether or not to revert back to an earlier kernel version, before he added all the caf code and basically start over again.

As to logs, I did answer you before, and there's really no way to log memory usage...
[Nexus 5 Original Android Development] inscythe:
I just got my Pebble Steel, and I got this connection issue as well. I was on r34test from the first time I used the Pebble, and I thought I might have gotten a faulty unit. I'm gonna try running r32 and see whether the disconnections still happens.
[Nexus 5 Original Android Development] bradputt:
Yeah, I revert to r32 after too many problems with sound clipping and screen redraw issues. It's been perfect on 32 for me.
[Nexus 5 Original Android Development] Tzfardaya:
might be something with the pebbles.... I consistently use 2-3 bluetooth devices simultaneously for about an hour a day (drives to/from work) and aside from the issues I've stated earlier with my nuvi (it doesn't like to share) the connections are fairly solid...

That being said... none of my connections use the low power bluetooth standard, which I'm assuming that the pebble does... So I'd suggest trying r32 and the stock kernel. see what the differences are in how the stock kernel handles the pebble vs r31-34. Grab the dmesg logs (kmesg) for the connects/disconnects as well... maybe there's something in there...

Aside from the bt connection issue, how do you like the pebble?
[Nexus 5 Original Android Development] zukа:
Sweet - well I'll definitely keep checking updates over the next few days. Thank you for your reply, and obviously thank you to Franco for all his hard work
[Nexus 5 Original Android Development] fbf2201:
I never connect multiple devices via bluetooth and still have disconnects with the latest builds. His situation with multiple devices is obviously a different thing or even related (?).

[MENTION=3292224]franciscofranco[/MENTION]

Please consider taking a look at this issue as well. Our maybe it just dissappear with your rebuild.
[Nexus 5 Original Android Development] Tzfardaya:
I'm pretty sure mine isn't related... I'm certain it's just the nuvi gps not wanting to share... :P

It disconnects and sulks when my phone tries to get a three or four way going...

like I said, it happens with the stock kernel too..
[Nexus 5 Original Android Development] Vollspacken:
Same issue here with r34-test from 27/2 on carbon rom. Raising the input_boost_freq to 1497000 lowers the micro stuttering, but it doesn't fix it. This thing didn't happen in r33, i wonder what is the problem here.

But in return the battery life is amazing!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
didn't the input_boost_freq use to be 1574000?

Something about higher frequency for the l2 cache or something?
[Nexus 5 Original Android Development] perrocaliente:
Is the battery life on r31 still good? I've been waiting for a version without memory leaks but if he's going to start over I think I might just go ahead and download r31
[Nexus 5 Original Android Development] Tzfardaya:
battery's pretty solid on all of the release versions... other issues started cropping up with the test-33's, so even r32 should be good

I'm on test-34 and to be honest, while I'm tracking the memory to try and catch something sneaking in, it's not affecting the usage of my phone, but I think the leak is slow enough that it needs a couple days to take hold, whereas I rarely go longer than two days without rebooting for some reason.
[Nexus 5 Original Android Development] Vollspacken:
On r34-test ot's on 1344000 for me, i don't know why. That's why i raosed it since it was higher in previous versions

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
a lot of the tunables seem to change from one release to the next. :P

But I do recall when the input freq seemed much higher than now... might that be when the microstutters were absent?
[Nexus 5 Original Android Development] inscythe:
2+ hours into r32, and this is currently the longest stretch my Pebble keeps the connection ever since I owned it. I'm gonna wait till tomorrow's morning to call it a complete test though...

So far, Pebble Steel is very sleek, mature in terms of design. It is a smartwatch that does look more like a proper watch than a gadget. Although, to be fair, with the same kind of money, you can get a 'proper' slightly higher-end watches like Casio Edifice or something, I'm liking the functionality. However, due to the aforementioned connection issues, I haven't fully explored much of the interesting features. So for, I'm only using it to push notifications and control my music. Let's hope r32 is gonna work fine.

I'll switch back to r33 and r34test to grab some logs if r32 turns out to be fine.
[Nexus 5 Original Android Development] big_adventure:
Seriously, let your phone handle all of that for you, UNLESS you specifically have an app that misbehaves and wakelocks the phone. I have 2 apps (and only two) that I absolutely have to close manually or they kill the battery, but I have never, ever manually quit any other app on my phone.

Apps that are guaranteed wakelocks:

Puzzle Quest

Uber

If I leave one open, I am guaranteed to never drop into deep sleep. Uber, in particular, has to be specifically killed from Settings > Apps > Running > Force Stop - swiping it away will NOT kill its wakelock.

Apps that never wrongly wakelock my phone but which are used frequently/constantly:

Google stuff (Gmail, Hangouts, Drive, Maps, Chrome, etc.)

Spotify

8sms

WhatsApp

Evernote

Dropbox

DoggCatcher

MX Pro

Facebook

Twitter

Autolib'

RATP

SNCF Transilien

Subway Surf

Badland

Le Gorafi

NY Times

BBS

FKU Paid

AS.Parrot

Instagram
[Nexus 5 Original Android Development] daniel84cs:
[MENTION=3292224]franciscofranco[/MENTION] with latest R34 T2 wooooow.

My personal record with 90% in 3G.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] big_adventure:
I'm REALLY not sure time travel is a good idea in a pickup.

Well THERE'S your problem - didn't anyone ever tell you not to play with your dongle while driving?
[Nexus 5 Original Android Development] tylerdurden83:
Asking only to understand it better myself, not to suggest to you what you should be doing. Do you have to start everything from scratch, or you can roll back to the r32 tags, since r32 seemed to not suffer from the sound and ram issues?
[Nexus 5 Original Android Development] Arathon:
Hi, i don't know if this is kernel related but i'm having a lot of problems with my mobile connection, every-time i switch from 2g to 3g or vice versa i lose the connection for 10 to 60 sec (the same behavior happens if i set the mobile type as 2g/3g). Moreover I've noticed some random drops of the connection, one sec i have 5 bars and on the others connection unavailable.

Furthermore if i try to update a lot of apps from the play store only few of them will be updated even thought the phone is still connected and the play store says update ongoing. I have to stop the process and restart it every time it freezes.

Does any of you have any of these problems?

P.S sorry for the english not my native lang, andI don't know if catlog would be usefull, but i'll try to catch the problem and i'll upload it.
[Nexus 5 Original Android Development] FAdrums:
OT, but does anyone know any app to take a logcat so I don't have to do all that painful ADB process? Thanks :)

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Shane_IL:
Sounds like a fast dormancy problem, do some reading about it but basically some phones have this feature enabled by default and if your mobile network doesn't support it it can cause these exact issues.
[Nexus 5 Original Android Development] italia0101:
I noticed that straight away , i believe it was the 1.5ghz step before ,doesn't seem like a big increase , but its helped me fore sure ... i put it back up and the stutters are gone.
[Nexus 5 Original Android Development] Arathon:
so i need to set ro.ril.fast.dormancy.rule=0 in build.prop, no? ok i'll try it and i'll report. By the way my mobile operator is vodafone (italy) how can i know if they really support it or not?

EDIT: i checked the build.prop file and i don't see any ro.ril.fast.dormancy.rule, should i add it?
[Nexus 5 Original Android Development] @wells:
https://play.google.com/store/search?q=logcat&c=apps&hl=en

catlog is ok
[Nexus 5 Original Android Development] fbf2201:
Logcat Extreme is quite good. You can follow the log in a floating window and do log records.
[Nexus 5 Original Android Development] FAdrums:
Thanks guys! Tbh I don't understand whats going on, on the actual logs! Lol

But I'm having weird issues since last night. SuperSU fc, google search fc, keyboard fc. Don't really know why. Did a clean install of PA 4.1 + FK r34 test + Viper mod and running ART. Any ideas?

Edit: logcat I took just after rebooting when had the fc's. Not sure if it has any valid info.

https://www.dropbox.com/s/d80j2wwv3fr6mk1/2014-03-04-11-16-31.txt

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Ben36:
Did a clean install and then used titanium backup?
[Nexus 5 Original Android Development] FAdrums:
No bro! I don't use TB at all!

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] zukа:
I had the same issue on r33/r34 - apparently it's a ram leak that some users have been experiencing. I think Franco is working on it, but for now your best bet is flashing r31
[Nexus 5 Original Android Development] pikachukaki:
I had this anoying think when you press the power and the screen don't light up...anyone know where this is caused by???im with r31 btw with my settings on gov and hotplug....maybe those are causing it?
[Nexus 5 Original Android Development] blueren:
So I'm under the assumption setting input boost to 150000 fixes the stutters? Wonder if it was brought down deliberately to extract more juice.. whatever the case maybe, stutters on a nexus is a big no no! :|
[Nexus 5 Original Android Development] italia0101:
Set it to 1574000.... Yea that really helped smooth things out for me
[Nexus 5 Original Android Development] Damix2:
I have a big problem. I wiped everything and flashed SlimKAT with Franco kernel. My nexus is often rebooting when I undervolt - 75mV global, 300MHz@650mV, and even on - 50mV global, 300MHz@650mV... My N5 is running on latest SlimKAT stable version and franco r33.

It's strange because before the wipe everything was running stable even on global - 75mV, 300MHz@650mV. What I have to do to fix these reboots ? It's so strange...

Wysłane z mojego Nexus 5 przy użyciu Tapatalka
[Nexus 5 Original Android Development] @wells:
don't undervolt. really.
[Nexus 5 Original Android Development] Tzfardaya:
yes, don't undervolt... undervolting this device seems to cause more problems than it solves (unless you spend a week or so fine tuning the UV, but then the next kernel released changes what the device can handle)
[Nexus 5 Original Android Development] Damix2:
With undervolting I can get better SoT and the phone doesn't get so hot. It's strange because before with the same configuration everything was running stable...

Wysłane z mojego Nexus 5 przy użyciu Tapatalka
[Nexus 5 Original Android Development] sirovai:
UV can causes more problems than the really benefits it gives. Mine experience.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] static416:
So I decided to run full encryption on my device and it looks like R33 is not a fan of encryption.

When awake or charging it functions fine no lag or anything else. But if it's allowed to go into deep sleep it silently dies and phone shuts off, almost like it's undervolted (though I just use the stock settings). In fact, even bumping up the voltage overall by 25mV, and a further 50mV on the two lowest frequencies seems to have no effect. Any other suggestions?

Flashing back to the stock kernel fixes the problem and everything is fine. Flashing back to R33 reproduces it 100% of the time. I've gone back and forth a few times to verify.

I attempted to run catlog to capture the problem, but it didn't show anything notable. Is there a special way to capture the log right up until the moment it dies? I decreased it to 50 lines of buffer before writing to SD, perhaps I'll try 0, though that might be kind of hard on the system.
[Nexus 5 Original Android Development] shreddintyres:
In recent versions of Franco kernel I believe since r32 some changes were made that influence the close table i remember it being discussed at length, additionally whenever you switch kernels it's a good idea if you must uv to start from scratch. I personally have had no issues with uv but I have gone through and made sure to UV each frequency step by step to ensure stability.

Make sure to uncheck set on boot for voltages and start fresh to eliminate your issues. That or globally start bumping your voltages up.

Cheers
[Nexus 5 Original Android Development] toocool4all:
Hi please help. I was not getting 3g so I by mistake deleted all partition in recovery and now I have no os installed and no Rom to flash in internal memory so what should I do
[Nexus 5 Original Android Development] DespairFactor:
I am running ART and this kernel on rooted stock with no issues at all:)
[Nexus 5 Original Android Development] jmartino5920:
I'm loving everything about this damn phone. Most of all, this kernel. Been rocking franco going on 2 years now!

Thanks franco!

Sent from my Nexus 5
[Nexus 5 Original Android Development] ChazzMatt:
With Flashify app you can back up stock kernel, before flashing new custom kernel. Even though I've flashed several of Franco kernels, I can always restore stock kernel if I wish -- because I backed it up first.

Not that I plan on going back. I've been running Franco kernels since July 2012. But you asked how to restore stock kernel and this is an easy way...
[Nexus 5 Original Android Development] Langduscher:
Why not use FKU bèta.......
[Nexus 5 Original Android Development] Martin-Doc:
because beta
[Nexus 5 Original Android Development] jmartino5920:
:rolleyes:

Sent from my Nexus 5
[Nexus 5 Original Android Development] ChazzMatt:
Look, this discussion went on for awhile and the guy was basically told he had to flash the freakin' stock image back to get stock kernel.

I'm the ONLY one who gave him a decent answer and an EASY answer -- with a screenshot even. :) You have a better answer, why didn't YOU help him?
[Nexus 5 Original Android Development] DespairFactor:
Why cause an issue over something so trivial? Also, your solution only does flash the stock kernel back...

It was never stated he had to flash back to stock completely, I told him that the img is in the stock files.
[Nexus 5 Original Android Development] javacody:
The beta has only been working for N5 for a few days. I wish I would have known about the flashify app before I installed r5 but there's also a zip in this thread that contains the stock kernel.

Lots of options and no need to get pissy with one another.
[Nexus 5 Original Android Development] ChazzMatt:
My solution does EVERYTHING. Did you even look at the screenshot?

Backs up current kernel, backs up current recovery, restores old kernels, etc.

Franco is still adding stuff back to his Nexus 5 compatible FKU app. Until a couple days ago you couldn't back up and restore kernels. You always could with Flashify.

I've been using Franco's apps and kernels long before you ever joined XDA.
[Nexus 5 Original Android Development] DespairFactor:
It does everything? Can it make you not so hostile?

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

I agree there is no reason for him to be upset because someone asked him why he didn't use another application instead.
[Nexus 5 Original Android Development] mpkothari:
Running r10 with ART since last night and haven't had any major issues i.e. force closes or restarts or hangs but have noticed some jank while scrolling in xda app. Hopefully this is just an app issue BC I haven't seen scroll stutter in any Google apps i.e. People, Play Music, etc.
[Nexus 5 Original Android Development] JNewms:
OK guys. I think he has his answer. There is no need for arguing. Let's try to steer this back on topic and focus on development. ?
[Nexus 5 Original Android Development] STi_Fanatic:
I'm also running ART with r10 on the stock ROM - only stutter I have noticed is when I load an external webpage via the Reddit is Fun app. That could just be shoddy coding though, I assume that app uses the WebView widget to display external sites.

But the other 99.95% of my phone works flawlessly on ART.
[Nexus 5 Original Android Development] sluflyer06:
Does your solution work if the phone won't boot? Fastboot flash boot boot.img > an app I can't access unless the phone is working. ;)
[Nexus 5 Original Android Development] bigknowz:
Factory Boot Image

Here you go

https://www.dropbox.com/s/0kj9hf5hi6ugyu9/boot.img
[Nexus 5 Original Android Development] Langduscher:
Really....

fastboot flash boot boot.img

And that's it (when one does not know how to retrieve boot.img from stock images .... don't bother participating in The Journey To Better).

Want to back up & restore stock img - (amongst kernel tweaking) Pay & use FKU. Easy as that. Francisco teaching how to flash stock kernel image is a BIG PLUS imho.
[Nexus 5 Original Android Development] Wenzo2:
thanks :)
[Nexus 5 Original Android Development] DesertVelo:
How are you trying to update/create the file? A little more information would be helpful... If you manually updating the file, please make sure that you have R/W enabled for your utility/editor. Make sure that the permissions are set correctly after the confirmed update of the file. If you are using a terminal, enter su before executing the command. Also, make sure that you have all of the zeros, for example: 320000000 (yes, 7 zeros).
[Nexus 5 Original Android Development] ChazzMatt:
Look if the guy wanted to be helpful he could say, "You can also use FKU". Bonus points if he posted a screenshot showing how. There's room for more than one right answer.

Instead of "why not use FKU?" sounded like he was grading my answer, like I hadn't done good enough. :silly: I wasn't even talking to him, initially. But if he's going to join the conversation, he's going to be respectful.

My answer is as good as or better than FKU. Your answer is not easy, more technical.
[Nexus 5 Original Android Development] PetritH:
Wrong place bro, get wugfresh developement tools, flash stock then do whatever u want
[Nexus 5 Original Android Development] snives:
You'll need to fastboot and start fresh.
[Nexus 5 Original Android Development] PainfulLover:
Hotfix, for all bugs, lmaotsedung.
[Nexus 5 Original Android Development] pikachukaki:
Ok to the more experience eye how this setups feels... I don't know if the r34-test has all the cores on all the time but that's how it works now... Tell me where I'm wrong... Remember those are extremely battery life (I want them to be) settings

Σεντ φρομ μυ Νεχυς 5
[Nexus 5 Original Android Development] blackdragoon:
Hi all,

Not sure if this has already been posted but something in R33 broke per-apps mode (unless the toaster notifications have been removed). I just realized within the last few days that I didn't see notifications of per-app mode being applied and disabled when opening/closing apps that I had set profiles for.

I just flashed back to R32 right before I posted this and the notifications were back.

Other than that, thanks for a great kernel, Franco!
[Nexus 5 Original Android Development] sirovai:
Recovery +adb sideload

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Kernel version doesn't affect per app, that's all the fku app... Are you greenifying or completely closing the fku app? Swiping out of recent, using the back button to leave (rather than home button), or force closing it it the settings->apps page? If so.. STOP IT.. :P fku needs to be active in the background to work.. Either automatically during the boot process or after you've manually opened it..
[Nexus 5 Original Android Development] big_adventure:
What probably happened is that the famous mem issue popped up, and the system killed the FKU service. This has happened to me after a couple of days running ever since the mid-r33 tests. Simply reboot, and it'll all work again.
[Nexus 5 Original Android Development] blackdragoon:
No, I don't have FKU greenified, and I never swipe it out of Recent Apps, or close it at all.

---------- Post added at 11:29 AM ---------- Previous post was at 11:29 AM ----------

I tried flashing back to R33, which automatically rebooted my phone after, but Per Apps still didn't work until I flashed back to R32

Update: Weird. I just flashed R33 back a third time and eventually, Per App mode started working for me again.
[Nexus 5 Original Android Development] AGiLiT:
Franco's new Per-App Modes app gets a nice little plug here: