yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] simonarturo:
Not officially at least.

Some kind soul repackaged r56 into a zip and posted it 2 or 3 pages back
[Nexus 5 Original Android Development] Aerowinder:
http://xdaforums.com/showthread.php?p=53898445

May be of interest to some.
[Nexus 5 Original Android Development] hellshinoda:
The default max freq of r55 has been scaled down to 1.55Ghz, am I correct?
[Nexus 5 Original Android Development] fredfox_uk:
Nope. Thermal throttle is probably the cause.
[Nexus 5 Original Android Development] shreddintyres:
Franco has stated he won't be doing a kernel for L until it is fully released, specifically he doesn't care about the preview in terms of supporting it since there are invariably going to be a multitude of changes from the preview to actual release so he will only be supporting kit Kat for now
[Nexus 5 Original Android Development] tigger360:
AFAIK Franco won't have a kernel for L until it is officially released to the public as there are many things that could change and it would be a waste of time to develop a kernel for it.

---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------

Sorry, didn't see the post above while I was typing mine :D
[Nexus 5 Original Android Development] Clauu:
All the best for the latest r55 kernel, after ~12h of some usage with 40min calls some sms hangouts and wifi allwayws on i still have 88% battery :) Good job
[Nexus 5 Original Android Development] Aerowinder:
I've had it happen after the device was idle for several minutes and was cold to the touch. I'll see about getting some screenshots with FKU and System Monitor next time it happens. It's almost like the throttling activates during usage, but never turns off. The weird thing was that System Monitor was showing usage above the supposed allowed limit.
[Nexus 5 Original Android Development] matesc:
I just had a random reboot on the latest test build after touching the back soft button while browsing FB. Log attached.

Edit: not sure if it's kernel related
[Nexus 5 Original Android Development] derPianist:
If it's the app, nuff said.
[Nexus 5 Original Android Development] pkelly517:
Might have something to do with the 3GHz over clocking.
[Nexus 5 Original Android Development] matesc:
Well weird. I do not OC. Never. Actually I didn't touch the freq.... [emoji54]
[Nexus 5 Original Android Development] Aerowinder:
[MENTION=3292224]franciscofranco[/MENTION]

r55, I did not touch the clock speed, it goes by itself to 1958MHz. Manually re-selecting 2265MHz seems to fix (per System Monitor), I don't have enough data to support that theory, yet. I've attached below everything I could think of to help you track this issue down.

The clock speed is changing on it's own, presumably due to throttling (I have my throttle temp set to 55c). If it is throttling, it is not adjusting itself back to where it is supposed to be after it cools down, but System Monitor shows no indication of it ever getting close to the throttle temp.

It may be relevant that I use PAM in FKU to underclock my games to 652MHz. This is the only adjustment I make to the standard clock speed of 2265MHz.

I've seen this issue before on the older releases, through clean flashes, stock ROM, SlimKat. I can't reliably reproduce it, but it happens frequently enough that I've noticed it.

For what it's worth, I use r17 on flo, and haven't run into this issue yet.
[Nexus 5 Original Android Development] californicated:
I can confirm throttling and not going back. I didn't post a log as I undervolted and thought this was the issue.

r56 test
[Nexus 5 Original Android Development] Clauu:
[MENTION=4788211]Aerowinder[/MENTION] could you please attach a img to freq voltages?
[Nexus 5 Original Android Development] Aerowinder:
Sure. I don't UV. And the only time I UC is with FKU's PAM for games. Which seems to work fine, and even revert to proper settings after I'm done.
[Nexus 5 Original Android Development] franciscofranco:
Are you sure you're running FK? I don't throttle to 1,9GHz.

Dunno, watchdog triggered but nothing in the log.
[Nexus 5 Original Android Development] kouske:
I'm now on faux kernel and on purity 4.4.4.

If I would like to switch to francos kernel without issues, what is the procedure?
[Nexus 5 Original Android Development] franciscofranco:
Flash FK...
[Nexus 5 Original Android Development] Aerowinder:
Pretty certain, yes :)

I will keep an eye out and try to pull more logs. Maybe one of these times I will get lucky and something useful will show up in them.
[Nexus 5 Original Android Development] kouske:
No need to return to stock or anything? Just flashing it over is fine?
[Nexus 5 Original Android Development] simonarturo:
If you want to be 100% on the safe side, just dirty flash your Rom and then flash Franco Kernel
[Nexus 5 Original Android Development] kouske:
I'm not worried about it not booting, I'm afraid of a conflict after installing... If the install went through OK then it's good enough?
[Nexus 5 Original Android Development] simonarturo:
Anyone has some nice, up-to-date Per App Modes profiles?

The ones I've seen around are kind of dated.

I'm trying to strike a balance between Uv/Uc, performance and battery life
[Nexus 5 Original Android Development] californicated:
I've got it! To reproduce the bug, where the cpu throttles and doesn't raise frequency again:

- give your phone some love and let it feel warm inside

- reboot the phone while it's hot

-> surprise! check your cpu frequency in fku

Sure it has to do with thermal throttling. But while it should scale up again, it doesn't. Will post a log in a few min

Edit:

dmesg

last_kmsg

logcat

Some further information:

- PA 4.41

- ART

- already saw the kernel throttling to 1,2ghz, 1,9ghz or like this time 1,5ghz

- now tried with uv, or touching any other fku settings

- already cleared fku data
[Nexus 5 Original Android Development] braders2k:
I'm getting failed to play video after watching any streamed video on test image.. it plays vid then error occurs..
[Nexus 5 Original Android Development] franciscofranco:
Yeah I guess there's some odd problem when the Kernel thermal throttles during boot or immediately after boot. I'm gonna check if there's **** code on my routine. Thanks for the detailed bug report with logs etc :)

Thanks for the detailed report.
[Nexus 5 Original Android Development] Tzfardaya:
well, there is the thread about fku settings and pam modes in my signature, as to being dated, they don't change much/often, once you find a set that works for you, it tends to continue working until/unless there are major changes in the kernel (as to UV, don't bother with that, it's less of a battery help than you might think, sure it helps a bit with heat generation, but the consequences/side effects from not setting it properly far outweigh the heat reduction gains... im(ns)ho )
[Nexus 5 Original Android Development] TrenchKato:
Makes sense. I have the stock max cpu set on boot and the problem went away. Didn't bother to investigate further.
[Nexus 5 Original Android Development] frankwhite8536:
r55 Wifi not connecting fully

Ever since I flashed r55 I'm not able to connect to my home Wifi. It connects but I don't believe I'm getting an ip but it's definitely not giving me Internet. Anyone else with this issue? Any thoughts on a fix?
[Nexus 5 Original Android Development] Tzfardaya:
Iirc, WiFi stack is stock... Something else is probably causing the derp (55 may have triggered the event... But)
[Nexus 5 Original Android Development] franciscofranco:
Maigode, Wi-Fi is 200% stock.
[Nexus 5 Original Android Development] sjknight413:
May I ask what the stock frequencies for r55 are? My max is stuck at 1190 and occasionally goes down to 729. Is this the intended behaviour?
[Nexus 5 Original Android Development] franciscofranco:
No, you're thermal throttled...
[Nexus 5 Original Android Development] sjknight413:
Ah I see, probably should have realised that.

My phone isn't especially hot though, sitting at 44 degrees according to your app. Guess the solution is to just switch it off and leave it a while so I'll do that.
[Nexus 5 Original Android Development] frankwhite8536:
O

I read something about the ramdisk being included between 54-55. The reason I mention is because I was going to attempt a logcat. I've never done one since usually someone else has my issue first. When I looked up how to do one the post was regarding this individual that made some ramdisk changes and then couldn't connect to Wifi.

Anything I can do just let me know. Im 99% sure it happened with the upgrade. My other devices don't have an issue. I can even connect to my other Wifi network upstairs that's hardwired to the one I can't connect to downstairs.
[Nexus 5 Original Android Development] franciscofranco:
The ramdisk thing was just to increase the tcp window, has nothing to do with Wi-Fi directly.
[Nexus 5 Original Android Development] franciscofranco:
Because you asked and I was not feeling lazy next FKU will have a proper frequency selector for hispeed_freq, input boost freq, sync freq, and other important fields that require freqs.
[Nexus 5 Original Android Development] Tzfardaya:
What he's not saying, is that while all the freqs are now in a selectable drop down, they get randomly scrambled each time you open the drop..... :p

That'll teach us to ask for enhancements again...
[Nexus 5 Original Android Development] Tzfardaya:
Uh oh... I just gave you an idea, didn't I?
[Nexus 5 Original Android Development] matesc:
Well a shiny new test image appeared on the server. This time I better don't share 'my work' ;)

What are the changes, Franco? :)
[Nexus 5 Original Android Development] franciscofranco:
I picked a small patch from myfluxi to remove latency from the screen on and off sequence from 200ms to 20ms.
[Nexus 5 Original Android Development] matesc:
Thanks, nice!

I don't now if it's placebo or not, but the L commits seem to reduce wakelocks like introduced at the I/0, btw. Great work as always!

I got 4+ SOT every day with location history on. 50/50 - LTE/WiFi, WiFi background scan off, no UV, no UC.. Just enjoying the phone :)
[Nexus 5 Original Android Development] Technecium:
I'm having an issue with recording video on t56 and this may also be related to what a user complained about earlier when viewing video. After reverting the commit below, video recording works again.

Commit: 951f6bb2736042a29ceef5a8c9053cd21d244912

Pastebin: logcat App that fails to record correctly: com.hovans.autoguard

I will also be passing this info along to the app dev.
[Nexus 5 Original Android Development] limzm:
Does PA has the native OTG? If so you can PM me, and you won't need stickmount for it.
[Nexus 5 Original Android Development] Hopper8:
Test build running sweet here so far, thanks! Response time for turning on the screen is incredible ?

Sent from my Nexu5
[Nexus 5 Original Android Development] der_sascha:
[KERNEL] [GPL] [N5] franco.Kernel - r55

After flashing test r56 I get reboots after 5 second on boot so I am back on r55
[Nexus 5 Original Android Development] occtec:
Log would be helpful ;)

---------- Post added at 05:03 PM ---------- Previous post was at 04:57 PM ----------

Here's a reference guide on how to log all your kernel related errors plus others. This guide is especially for those that report issues but ARE NOT providing logs. http://xdaforums.com/showthread.php?t=2185929 this will better help [MENTION=3292224]franciscofranco[/MENTION] to determine the cause and apply the best solution ;)

A big thumbs up to [MENTION=3605868]tonyp[/MENTION] for his time and effort in creating this reference guide and this useful thread [emoji106]
[Nexus 5 Original Android Development] nexusmaniac:
Damn! It's so annoying hearing all of this talk about the new test kernels and not being able to use them on L. But I just can't bring myself to flash back to 4.4.4! :P
[Nexus 5 Original Android Development] gamerZ1:
No problem with R56 until now.
[Nexus 5 Original Android Development] der_sascha:
I am using the vormertweaks script maybe that's why
[Nexus 5 Original Android Development] Juzman:
Latest test running fine on PA 4.41 + ART with (modified) vomer tweaks.
[Nexus 5 Original Android Development] franciscofranco:
You have something seriously ****ed up on your device.
[Nexus 5 Original Android Development] der_sascha:
Maybe to much undervolting?
[Nexus 5 Original Android Development] iPsychoGeek:
Unselect undervolting on boot. R56 don't have 345MHz frequency.
[Nexus 5 Original Android Development] JNewms:
That's definitely something that could happen with over doing the UV.
[Nexus 5 Original Android Development] android4temo:
I'm sure this is posted somewhere in this wonderful and most lengthy thread but... Does anyone have screenshots of their best "battery saving" setup using FK? Thanks for the love.

Sent From My Rooted Nexus 5
[Nexus 5 Original Android Development] matesc:
Hey franco! I don't know if you've noticed already but making of videos seems to be broken on r56 test. It takes the video but it doesn't save it. Tested on multiple camera apps(stock as well). The problem doesn't exist on stable r55.

Edit: has been already reported.
[Nexus 5 Original Android Development] ben_pyett:
also suffering from video saving failure on latest test 56
[Nexus 5 Original Android Development] Hopper8:
Confirmed, that the video will not save when on r56 test. Logcat: https://www.dropbox.com/s/suz6bqrqft6ss0z/2014-07-05-21-03-38.txt

I'm not near a PC, so that was only taken on my phone. Apologies Fransisco if it doesn't contain the necessary information because of that.

Sent from my Nexu5
[Nexus 5 Original Android Development] sjknight413:
Is the thermal throttling on this really strict? My phone just won't go past 1190mhz. It got up to 1.9ghz this morning but after about five minutes or so of use it goes straight back to 1190. It's stuck at 1190 at boot too.

What is the stock max frequency so I can just set it at that?
[Nexus 5 Original Android Development] blueren:
U are not alone. I used to have that. The moment thermal throttle kicked in, it used to down the max freq. Then the max freq used either get stuck there, or stay at 1190. A reboot wouldn't fix it. The only way i was able to deal with it was to raise the throttle temp to 75.

I don't see that happening anymore though. I'm running the latest PA.
[Nexus 5 Original Android Development] nexusmaniac:
I will, thanks for the advice ;) haha
[Nexus 5 Original Android Development] Enddo:
that depends. do you live in the Sahara desert. with FKU you can see what the thermal throttle temp is set, and you can even change it
[Nexus 5 Original Android Development] sjknight413:
I live in England, so in theory it should never throttle! Haha.

I've set the throttle temp to 75 as suggested above and it seems to be fine.

What is the max frequency of this kernel? Is it 1.9ghz as that is what I'm stuck at now. I was under the impression It was 2.3ghz.
[Nexus 5 Original Android Development] Aerowinder:
2265 is stock speed.
[Nexus 5 Original Android Development] blueren:
Be advised that it will still get randomly set to a freq the moment u throttle at 75. Most ppl will flag you down as a simple matter of thermal throttle. But u n I know it's not. :P

Sent from my Nexus 5
[Nexus 5 Original Android Development] Aerowinder:
The mysterious 1958MHz strikes again. Franco is aware of the issue, it was reported yesterday. He said he was going to have a look over that code. In the mean time, see if setting 2265MHz on boot via FKU resolves it.
[Nexus 5 Original Android Development] K Rich:
I think I'm in love with R56 ☺
[Nexus 5 Original Android Development] simonarturo:
Re-re confirming the camera not saving videos issue on r56
[Nexus 5 Original Android Development] cdx47:
FYI you can still take pictures while the video is being recorded. Not much use of course if the video is not saved.
[Nexus 5 Original Android Development] SpecRek9:
All right, I wasn't aware of that, good to know.

Thanks
[Nexus 5 Original Android Development] Smoosh1:
[MENTION=3292224]franciscofranco[/MENTION] What do you think about my suggestion/ request which I made here (post #31906)?

BTW: Starting from FKU 11.5.1 changing the zip-path works now on my device. Thanks for that.
[Nexus 5 Original Android Development] peikojose:
Hi guys, anyone care to test and give your options about these configs? I was going to be in a long trip so try to underpower the phone without making it a Nexus One hehe and used these, I was impressed because I did think the phone was going to be really slow (maybe I don't use any intense app?):

No UV

Maximum CPU frecuency

1190Mhz

Minimum CPU frecuency

300Mhz

interactive

bootpulse_duration

350000

go_hispeed_load

90

hispeed_freq

729000

input_boost_freq

1190000

sampling_down_factor

60000

sync_freq

729000

up_threshold_any_cpu_freq

1036000

up_threshold_any_cpu_load

65

hotplug control

load_threshold

20

cpufreq_unplug_limit

729000

min_time_cpu_online

4

MaxGPU 200Mhz

up_threshold 25

down_threshold 14
[Nexus 5 Original Android Development] Rxpert:
One bug I noticed on the L based test kernel was video recording fails to save

Confused the hell out of me last night when I tried to record the fireworks

Edit: I see others have seen this as well
[Nexus 5 Original Android Development] yoyoz808:
+1
[Nexus 5 Original Android Development] fredfox_uk:
s'not just me then :) cool, I thought the vino d'plonko was effecting my thought process too much !
[Nexus 5 Original Android Development] EnricoTFYKD:
+1 here to confirm the video not saving bug. Looks like something that has to do with the venus video subsystem:

<6>[14916.395767] MSM-CPP cpp_load_fw:843 CPP FW Version: 0x10020003

<6>[14922.113454] msm_vidc: 4: Opening video instance: d6120000, 0

<6>[14922.165791] pil_venus fdce0000.qcom,venus: venus: Brought out of reset

<7>[14922.178683] msm_vidc: 1: No more formats found

<7>[14922.178697] msm_vidc: 1: No more formats found

<6>[14922.183785] msm_vidc: 4: Closed video instance: d6120000

<6>[14922.185581] msm_vidc: 4: Opening video instance: d6120000, 0

<6>[14922.231444] pil_venus fdce0000.qcom,venus: venus: Brought out of reset

<7>[14922.243756] msm_vidc: 1: No more formats found

<7>[14922.243772] msm_vidc: 1: No more formats found

<6>[14927.107695] msm_vidc: 4: Closed video instance: d6120000

<3>[14941.394059] msm_sensor_config:1775 sensor state 0
[Nexus 5 Original Android Development] simonarturo:
Question:

Do you prefer to Undervolt or to Underclock? I'm trying to strike a good balance between power consumption and performance in general and Per-App Modes and would like my settings to save battery without introducing slowness.

I have read that underclocking is not the best option as it makes the cpu work more to perform tasks than if it were at higher speeds. Opinions?
[Nexus 5 Original Android Development] JNewms:
UV won't affect battery life. If you UV too much your device will reboot.
[Nexus 5 Original Android Development] simonarturo:
What are the kernel settings that play a part in battery life? I read that the most important part of a kernel is how fast it goes back to the lower frequencies

Oh and one more thing! In the Speaker Gain setting, if you want to boost the sound, should you input - or + numbers?

Thanks!
[Nexus 5 Original Android Development] franciscofranco:
Few things:

* The video thing is caused by one of Android L's Kernel patches with improvements in the Video decoder subsystem. Probably needs heavy userspace patching to match the Kernel changes so I'll revert it for the next release

* With this crazy better CPU frequency calculation we can decrease the input boost frequency dramatically and have no performance degradation and more battery life.

I'll push a new test .img in a couple minutas.

EDIT: pushed to the tests folder.
[Nexus 5 Original Android Development] TheLastSidekick:
Yup same thing happened to me, just didn't show up in the gallery. I was like... damn. Luckily my girlfriend saves the day for once with her..... Yuck iPhone. At least she knows it's a bad phone and wants to get the S5.

Trying new test kernel like Franco said should be fixed. Franco you work quick!

Seeing a stupid comment on Google Play about an app you love and marking it as "spam". You've done it too.
[Nexus 5 Original Android Development] jmudrick:
New test image fixes, thanks.
[Nexus 5 Original Android Development] Technecium:
Decrease? I'm starting to think it can be done away with at this point. I have it match my Minimum Frequency on my own build, so 96MHz, and I see no reduction in performance.
[Nexus 5 Original Android Development] franciscofranco:
Well, no wonder, this new calculation makes things SO much better and surprisingly battery life unchanged or even better. Thanks for letting us know. Maybe next build I'll decrease boostpulse to 250ms.
[Nexus 5 Original Android Development] Bobtehblob:
I've been running boost pulse of 250ms for quite a while now and see no difference in performance. The CPU reacts so quickly now that there is just no micro stutters anywhere! Top work Franco!
[Nexus 5 Original Android Development] simonarturo:
So what is a good number to set input boost freq at?
[Nexus 5 Original Android Development] Technecium:
The latest commit has it at 1036800

---------- Post added at 01:37 PM ---------- Previous post was at 01:33 PM ----------

Would setting it to '0' disable it? I'm just asking, not that I would suggest doing anything like that. Because when you do at it to 0 all seems just fine :D

Just installed FKU 11.53 (361) and the button to set Voltage Control on boot is gone. Intentional?
[Nexus 5 Original Android Development] RobbieL811:
I can confirm. Just updated and voltage control set on boot is missing.
[Nexus 5 Original Android Development] kecinzer:
You mean this https://github.com/franciscofranco/hammerhead/commit/4995c0b1ae4a40ca8f326f7fb8469db56feea33d right?

This commit also caused that kernel can't be builded inline with ROM. We needed changes for it in hw/qcom/media, but there are not those changes in l-preview branch.
[Nexus 5 Original Android Development] RobbieL811:
Link isn't working.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Juzman:
Mine is at 652800, sync at 729600 and hispeed_freq at 960000.
[Nexus 5 Original Android Development] Technecium:
Yes, the changes in the kernel code require changes on the platform side as well.
[Nexus 5 Original Android Development] kecinzer:
I just don't understeand why google didn't push these changes for other projects too. May be we have to wait for final L release.
[Nexus 5 Original Android Development] franciscofranco:
Ups :)

Yes.
[Nexus 5 Original Android Development] Edge330:
How to remove vomer script after I applied it?
[Nexus 5 Original Android Development] jamaljmys:
all the op download links are down and not working .

any other link please for last release?

thank you all
[Nexus 5 Original Android Development] cobhc:
http://192.241.177.15/Nexus5/4.4/zips/franco.Kernel-nightly-r55.zip
[Nexus 5 Original Android Development] paradoxiumwind:
I'm still getting this with the latest r55 and FKU app, does anyone else use SlimKat with this and are able to save their settings on reboot?
[Nexus 5 Original Android Development] ArtieQ:
r55 feels a bit choppy, coming from r53.
[Nexus 5 Original Android Development] Technecium:
With a root enabled file manager, check the permissions of the files in /data/data/com.franco.kernel/shared_prefs/

They should all be 0660
[Nexus 5 Original Android Development] paradoxiumwind:
Thanks, looks fine to me?

https://i.imgur.com/suiwnwb.png
[Nexus 5 Original Android Development] Technecium:
Yes, all good there. Perhaps the directory permissions?

/data/data/com.franco.kernel - 0751

cache, files, shared_prefs - 0771

lib - 0777
[Nexus 5 Original Android Development] mattcoz:
I'm having the same issue, did you figure anything out?
[Nexus 5 Original Android Development] paradoxiumwind:
/data/data/com.franco.kernel - 0647

cache and files are 667

lib is 777

shared_prefs 667 too

I'll change them to match what you posted and see if that does it.

Edit: I changed the values to yours, and FKU seemed to just start with a fresh profile when ran and the permissions are back to the old values, nothing saved still.