yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] akapolips:
Dirty flash over Blu-spark booting on N with Mcaosp Rom.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] bartolinio:
[MENTION=4039377]akapolips[/MENTION] This is not a good idea

bluspark makes changes to the ramdisk
[Nexus 5 Original Android Development] akapolips:
Hi thanks for warning me I didn't now that.
[Nexus 5 Original Android Development] bartolinio:
always

flash a custom kernel on the stock
[Nexus 5 Original Android Development] morfances:
Dirty flash over Blu-spark on N yashade2001 (Clean Rom) not boot
[Nexus 5 Original Android Development] rizqi_ir:
Bokrom
[Nexus 5 Original Android Development] morfances:
I confirm, with bokrom build stuck on the Google logo
[Nexus 5 Original Android Development] Arstoien:
After 9hrs uptime – no slowdowns and still smoother and more responsive than r91. I could even lower the input boost freq back to 1.1GHz from 1.3, which I had on r91. Good job with this one. I kind of lost need for per app profiles now.

Sent from my Nexus 5
[Nexus 5 Original Android Development] rizqi_ir:
It boots on bokrom. R u using bluspark before that?
[Nexus 5 Original Android Development] morfances:
Not,clean flash bokrom-gapps build 19/09
[Nexus 5 Original Android Development] Dungeon47:
Update: As others have reported, it works on CleanAOSP by yashade2001.

Tried on Sanhtosh AOSP N build for Sept 16, clean flash of stock boot img, then franco92. Sits at Google logo before boot animation.
[Nexus 5 Original Android Development] drive2droad:
Clean flash on [ROM] [NOUGAT] CleanAOSP [7.0.0_r6 / NRD90U] by yashade2001 & it works as advertised , thanks a lot [MENTION=3292224]franciscofranco[/MENTION] for r92 .
[Nexus 5 Original Android Development] osm0sis:
Guys who are experiencing issues on Nougat ROMs: remember AnyKernel2 zips should only be initially flashed over the boot.img that comes with the ROM.

Guys who are passing on this information: please refer to this as the ROM's "default boot.img" and not "stock boot.img" as I think that's resulting in some people thinking Stock ROM, which is of course a Marshmallow ramdisk and won't work with the Nougat ROMs.
[Nexus 5 Original Android Development] wvanstraalen:
No WiFi networks are showing up on Android 6 with r92. Is there a WiFi fix that I don't know about?
[Nexus 5 Original Android Development] fatspirit:
Yep. Search the thread.
[Nexus 5 Original Android Development] duffymm:
Hello

I know it's not a very "tech" or detailed feedback, but I still "feel" that the r87 version is the most smooth compared to all next releases (r92 included).

It's just a everyday use feeling, not much real benchmark or whatever involved.

I just wanted to share my experience, with Stock 6.x rom and Franco Kernel since ages.
[Nexus 5 Original Android Development] Julosch:
[ROM] [NOUGAT] CleanAOSP [7.0.0_r6 / NRD90U] by yashade2001

works on this one but i can't use the app correctly can you tell me why? cant use the download zip and auto flash options

its says unsupported device even though i have nexus 5 ?!
[Nexus 5 Original Android Development] yashade2001:
just flashed r92. works on my N build but all of the cores are always online. is that normal? [MENTION=3292224]franciscofranco[/MENTION]

by the way where is the source for r92?
[Nexus 5 Original Android Development] osm0sis:
Most likely because AOSP seems to use stupidly different device names and such, like "AOSP on Hammerhead" instead of "Nexus 5", etc. It'll need to be changed back by the developer.
[Nexus 5 Original Android Development] wvanstraalen:
Thanks, I found it.

In a distant past I fiddled around with the OMAPI to get Android Pay to work in the Netherlands. However, I need to have some time on my hands to flash the latest stock. How are the latest N-roms on the Nexus 5 holding up or is it better for the time being to stay at stock?
[Nexus 5 Original Android Development] franciscofranco:
Because you're probably in a rom that hasn't updated the Wi-Fi firmware or something.

Yes because on r87 (and older) I had a derp on one of the merges which forced the device to end up in higher frequencies than it needed. I fixed it on r88 and then I kept adjusting some parameters to make it slightly smoother again without ****ing your battery too much.

Because I haven't "officially" released r92 for N, which needs me to create a new space for Nougat on my server for tha app to fetch.

Yes. Source is indicated in the OP.... After 3990 pages of posts the OP is your friend.....
[Nexus 5 Original Android Development] Julosch:
There is no Wifi showing on Nougat too. I am on [ROM] [NOUGAT] CleanAOSP [7.0.0_r6 / NRD90U].

baseband: M8974A-2.0.50.2.29
[Nexus 5 Original Android Development] franciscofranco:
****ing custom roms. I seriously ****ing hate them. How hard is it to ship with updated Wi-Fi firmware?

It says on the ****ing commit: https://github.com/franciscofranco/hammerhead/commit/4785a82decb15a5398ff0a723e01084877942a46

"Required FW for bcm4339 >= 6.37.32.RC23.34.43"

**** me. Someone have a good reason why custom roms repackagers just don't do this? Is it Google's fault? I always get the ****ing blame and all the ****ing posts about "omfg no wifi" or "1 star, you suckas". It doesn't personally affect me, but it's annoying and then I get angry and make posts like this. And I'll probably get a warning from XDA from cursing, but it's unmanageable and doesn't matter how many times I tell users to stop using retarded roms they obviously don't know better and actually users shouldn't be needing to care about this.

Sorry for the rant.

****.
[Nexus 5 Original Android Development] irfaniphank2:
flash this mate http://xdaforums.com/showpost.php?p=68395715&postcount=9110
[Nexus 5 Original Android Development] franciscofranco:
Take a spin with the Kernel I'm attaching. Using some different interactive parameters just for fun & testing. Also made some big improvements on the thermal driver. [MENTION=4544860]osm0sis[/MENTION] been using this for 2 days. This is just for tests, I dunno if I'll make the changes permanent since it's hard just for me to measure battery life impact. That's where you come in.
[Nexus 5 Original Android Development] fuzzmz:
Problem is that the issue is reproducible even on stock Android which isn't updated on the latest version. I'm running stock 6.0.1 Feb1 2016 patch level (build MMB29Q) and the FKUpdater app did no check to see if my build is compatible with the latest kernel or not, it just let me flash it and what do you know, no wifi!
[Nexus 5 Original Android Development] Naitsabes123:
Why are you an Feb patch lvl? -.-

That just doesn´t make sense. Using old software, but trying out the newest Kernel possible?
[Nexus 5 Original Android Development] Mrcactuseater:
This is beyond pathetic. If you could read at all the past 50 or so pages, you would know old roms do not work with new kernels. Why you would even be on a feb1 build is beyond me too....
[Nexus 5 Original Android Development] Dungeon47:
People always take the path of least resistance. It's manifested laziness. It's the same as not reading the OP, or the XDA rules, etc. People just can't be bothered to care beyond the minimal effort of getting what they want, whether when building a ROM, or when using or installing one. We've created a society of self-entitled slobs who don't want to think for themselves because it's hard and can make them feel bad. Back in my day we just told people like that to grow up.
[Nexus 5 Original Android Development] Alex Kane:
I really like the new cpu_gov settings, especially under load. Since you eliminated above_hispeed_delay, it scales upwards like a mo********r. I'll keep the current (testing) setup for about a week, to evaluate battery results.
[Nexus 5 Original Android Development] Dungeon47:
Running CleanAOSP (N), flashed over r92 . This test boots fine, but as soon as FKUpdater applies settings, I get a reboot.I tried clearing saved on boot settings, but had the same result. Open to any suggestions that might help with testing, or I'm happy to stay on r92 for the time being.
[Nexus 5 Original Android Development] Arstoien:
the new tunables so far are really smooth. The frequencies are jumping high very quickly but seem to come back down fast too. Tasks seem to be completed quicker and device seem generally faster to response and smoother when scrolling. I have doubts though that it'll increase the battery usage but lets test and see…

Franco, any backdoor changes or just the tunables?

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
There are several things to consider:

1 - There's an implicit "contract" between me and my Nexus users in which it's assumed you're all running the latest versions of the platform. You have a Nexus, use it as is;

2 - When there are breaking changes like this (in which the Kernel needs some magical change on userspace to have a certain functionality work) I announce in the changelogs something like "WARNING! Don't flash this if you're not on security release X". I end up copy pasting that warning at least 2 or 3 changelogs over the breaking release. Even with big bold warnings users end up flashing without reading. They complain, they down-rate, they uninstall, they call me names and so forth. But that's ok. After those 2-3 releases I assume most users have caught up, and so I remove the warning. I can't be babysitting every time and spamming the changelogs endlessly;

3 - Updated information is always in the OP. The OP is linked in the first page of the app in a big ass XDA card. Users can't guess I have stuff there for them, but it's a good starting place when in doubt;

4 - I can potentially be more enforceful during flash and wrap everything around yet another protection layer, but that'll make you stop receiving updates or even be notified when there's an update for you if you're stuck in an older platform release so you'll come here asking me where the hell are the updates from the app you just bought and why I am slacking and the cycle continues.

This is something I really care about and there's always room for improvement on my end, but it's almost impossibru to cover all variables and different builds, different requirements etc. If you have suggestions I'm more than happy to read & consider.
[Nexus 5 Original Android Development] franciscofranco:
That is weird... what settings are you applying? Maybe I can try & replicate. It's a hard crash like the whole device goes back to the Google logo then Android boot, or simply straight to Android boot anim? If it's hard crash can you get me the /proc/last_kmsg? If it's a soft reboot can you open up an adb logcat shell before it applies the boot settings up to the point where it crashes and give me a copy pasta or the error (if there's any)?

That would be super useful as I don't know what I should be looking for or if it's a derp on my end (?).

There's no other magic here. Besides the governor tunable changes I only made improvements in the thermal driver: https://github.com/franciscofranco/hammerhead/commit/ab770a192e778d2aaee0d0c51a8f5412355db077
[Nexus 5 Original Android Development] Arstoien:
Sure, you said that, I forgot. Comming with some (not so great feedback). While playing a game and charging at the same time the device restarted. Then booted, loaded the homescreen, and a few seconds later rebooted again. Unplugged, but did the same (proably still hot). I suppose it's got something to do with the thermal changes. I flashed r92, here's the last_kmsg, hope that helps.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Nope, nothing related to the thermal driver changes. I went to improve the thermals right because of that issue. I can replicate it with geekbench and I don't know where it comes from. It happens less after my thermal driver changes, but it still happens. Log says "hw_reset" and I'm not able to find out where it comes from... not yet at least.
[Nexus 5 Original Android Development] Arstoien:
Oops I forgot to include the log but you seem to know about the issue then. Any advice on a workaround for the time being? Hasn't happened to me before but perhaps I haven't played a game while charging, or perhaps the device got hotter due to staying longer at higher frequencies.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
I don't know yet. I spent a couple hours trying to figure out (couple days before the .zip I posted here) and so far no go. It seems to happen as soon as it reaches the last level of throttling (don't know why yet). Lower the temp threshold to 55/60, it should throttle sooner so it doesn't get so hot or something - not sure it'll prevent it, but I think it'll help. I'm still investigating.

EDIT: This also happens on the official r92 and I didn't know. I'll keep digging.

EDIT 2: Yeah doesn't happen on r91. I have some clues now.

EDIT 3: I take that back, happens on r91 too. Wtf.
[Nexus 5 Original Android Development] Dungeon47:
Here's the dump. EDIT: The only settings I change are -25mhz to voltage, and adjustments to Headphones and Headset gain (3 each), and applying a color Profile (Perfect2.2). I leave everything else stock. I did try it again after removing the voltage setting from onboot, but had the same result. Glad to answer any other questions if it'll help.
[Nexus 5 Original Android Development] AceofSpades90:
Excuse my ignorance

I have been out of the XDA or development game for good till I got my Nexus 5 3 years ago. Anyhow, I have 2 questions:

1. Has VoLTE resolved in Nexus 5 yet? Stock kernel/ril doesn't offer it.

2. I understand it is common place to overclock CPU and GPU but is Ram/Bus speed overclock available?

That is all. I know these questions might have been asked before but so far I couldn't find a reliable source.
[Nexus 5 Original Android Development] franciscofranco:
1 - Not that I know of, but I don't follow hacks

2 - Nope
[Nexus 5 Original Android Development] franciscofranco:
Ok the crash is related to thermals, even after I throttle all the cores there's an occurence where the internal cpu sensors report a gigantic temperature (close to 110C) for like a sample. I've seen it jump from 70C to 109C directly in a space of 250ms so yeah if reported temp is that high the device just shuts itself down. I always thought HH's cpu temp sensors were weird, they can jump up/down too fast. Maybe lowering the temp threshold is a good idea for now just to see if by throttling sooner that it doesn't weirdly jump to something as high as that. I'll also play with offlining cpu2 and cpu3 if it hits Note 7 heat levels. Still considering, I'll have plenty to consider during the weekend. This has been present for a while, I wonder how no one experienced it. It's not really a bug on my end though, just using a different thermal throttle than stock which is pretty heavyweight in all senses.
[Nexus 5 Original Android Development] Mercedec777:
using the third day r92. the maximum temperature was 53-55C°. Average constant 45-48C°. And such a problem, I have not seen.
[Nexus 5 Original Android Development] Arstoien:
perhaps somehow it only affects some devices?

Sent from my Nexus 5
[Nexus 5 Original Android Development] fatspirit:
I've had one kernel panic recently, but don't know if it has anything to do with extreme overheating.
[Nexus 5 Original Android Development] Arstoien:
in my modest testing I have to say I don't see any higher battery usage. General normal usage. Little more time is spent in higher freqs but lots more is spent in very low freqs. I guess one compensates for the other.

Sent from my Nexus 5
[Nexus 5 Original Android Development] 12paq:
This ^^ Lmao!

Kernel boots and runs fine with stock settings. No lag, no high heat on both N ASOP and N CM14.

All good.
[Nexus 5 Original Android Development] morfances:
Work fine on Miui 8

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Arathon:
Tried it on Nitrogen OS N but i got stuck on google logo.
[Nexus 5 Original Android Development] drive2droad:
Doesn't work on Nitrogen OS , not even on the updated 25/09 build which he released a few hours ago . I am back on CleanAOSP with r92 & it works flawless .
[Nexus 5 Original Android Development] Mercedec777:
I had a problem at the ROM by Santosh M. And I set first Blu spark 106, and then fk 92?.
[Nexus 5 Original Android Development] ZaKaRia OuH:
hey.

i'm on Aosp Nougat 7.0 lattest build by Santhosh.

i want to install a custom kernel.

what do you please suggest for me blu sparks or franko kernel ?

and what instruction should i follow to flash it?

should i do any wipe or just flash the zip through recovery?

just to let you know i have a massive battery drain and the slow chargin bug.

thank you in advance.
[Nexus 5 Original Android Development] Mercedec777:
Hi!

I do not know much English, but I'll try to answer. I really enjoyed fk 92+ Naptime.

Instructions: Set Rom Santhosh M-> BS106> FKr 92

I made the kernel configuration: app Kernel Auditor

CPU/CPU governor tunables/hispeed_freq - 422

CPU/Input Boost Frequency Core 1-2-3-4 - 652

sorry for my bad english??
[Nexus 5 Original Android Development] Arstoien:
To follow up on that: damn, it's much smoother without slowing down with time passing whatsoever. And battery is at least as good, if not better. Definitelly keeper setup. Genius.

Funny you ask that here, but cool, I'll play along. I've used both and I'm currently using Franco. It's feature rich, smooth, and battery efficient (not that the last one would matter much in your case). And you know what – the fact that after all this time, after Google has dropped support for the device, the dev not only updates it with the security updates or makes small improvements, but is ready to try and test new things – that's pretty good argument right there imo.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Paschfire:
Much smoother, battery life is also very acceptable. I am either getting the same or a little more battery reserve than I normally do with day to day usage.
[Nexus 5 Original Android Development] gobonja:
[MENTION=3292224]franciscofranco[/MENTION]

r92 works on CleanAOSP and mcaosp, but on NitrogenOS and itrg's AOSP it doesn't.

Here is on NitrogenOS last_kmsg if you are willing to check it out.

Thanks in advance
[Nexus 5 Original Android Development] ZaKaRia OuH:
what do you mean with "Set Santhosh M->BS106>Fkr 92" ????
[Nexus 5 Original Android Development] Mercedec777:
1) Flash ROM Santosh M

2) Flash Blu spark 106

3) Flash Franco kernel 92

Putting you need in this order. Otherwise, the system does not start, hangs on the Google logo.
[Nexus 5 Original Android Development] ZaKaRia OuH:
excuse my ignorance but,

should i first flash blu sparks 106,then flash franco kernel 92?

and why ?

should i do any wipe or something that before flashing franco kernel 92 ??
[Nexus 5 Original Android Development] Alex Kane:
It is remarkably smoother (more granular target_loads) and ~40ms more responsive since there is no burst latency. Keep in mind that boostpulse_duration is clocked at 60ms (compared to the previous 250ms).

Also, instead of frequently ramping at hispeed_freq ~1GHz it piggybacks the lower (cheaper) frequencies resulting in potential battery savings. Anyway, really impressed so far :D. I'll continue evaluating battery life.
[Nexus 5 Original Android Development] Mercedec777:
Yes!

"and why ?"

Because the system hangs at the logo. problem as in NitrogenOS.

"should i do any wipe or something that before flashing franco kernel 92 ??"

Nope.
[Nexus 5 Original Android Development] Ruben8ap:
Operating in 14 CM unofficially by Satosh
[Nexus 5 Original Android Development] franciscofranco:
Glad to see such good comments about the test r92. I'm in NYC for the week and I haven't brought my N5. I'll wrap things up with test r92 when I'm back and push r93 without changing any setting. Thanks for the feedbacks, keep 'em coming.

bootspulse stuff isn't used. I'll remove them like I did on other devices since it's used anywhere.
[Nexus 5 Original Android Development] fatspirit:
[MENTION=3292224]franciscofranco[/MENTION], here's r92's kernel panic (second for me): http://pastebin.com/xP5FS7VP
[Nexus 5 Original Android Development] morfances:
Beltz N with franco r92 work fine

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] milestone2mod:
I had to use my Nexus 5 for a couple of weeks since I had to RMA my Nexus 6P three (f***ing) times. Don't even ask.

I've used r91, r92 and the new test kernel extensively. All I have to say is: It's impressive. Impressive, how well a 3-year old device has held up so well that it outperforms even current devices in everyday-usage. Impressive, also, how a few subtle changes in the kernel's configuration can elevate the user experience quite substantially. The new test kernel really does it's magic (at least for me).

I feel like the improved governor and boost settings could help lower-performance devices like the Nexus 7 2013, too. And the changes you made to the thermal config could help keeping "hot" devices like the Nexus 6P and 5X a little cooler.
[Nexus 5 Original Android Development] osm0sis:
Only just noticed this myself last week! I tracked the breaking change to the zImage and between r83 and r84 (so a commit somewhere between 2016-04-20 and 2016-06-07), and have made [MENTION=3292224]franciscofranco[/MENTION] aware so hopefully he can figure out a fix. :good:
[Nexus 5 Original Android Development] franciscofranco:
r93 is up! It has some cool stuff in there, I'm sure you're going to love it! Also thanks to [MENTION=4544860]osm0sis[/MENTION] for keeping up with this AK2 work, it helps me immensely. Make sure you send him a beer, he deserves it!

https://plus.google.com/u/0/+FranciscoFranco1990/posts/dMWEE58HM5D
[Nexus 5 Original Android Development] stark_br:
Up and running on CM14.

thx:good:
[Nexus 5 Original Android Development] fatspirit:
I'm experiencing strange reboots on r93 ()-8
[Nexus 5 Original Android Development] franciscofranco:
That was helpful.
[Nexus 5 Original Android Development] fatspirit:
Don't be so sarcastic. I'll give you more info later.
[Nexus 5 Original Android Development] sga999:
Same for me. I just installed marshmallow build M4B30X. Rooted, installed Xposed. All looked fine. Then auto-flashed r93. It boots up, but keeps rebooting after being up about a minute or two. Then I booted into recovery and flashed Elemental kernel. All is well with that kernel. I don't have any more information to offer at this time. I hope fatspirit is supplying that.

I only use the Franco kernel for color/gamma control.

UPDATE: Using fkupdater, I flashed r92, Good. Then r93. Now it's fine. So something must have gone wrong the first time I flashed r93 with fkupdater, even though it seemed to be successful and rebooted.
[Nexus 5 Original Android Development] franciscofranco:
You mean during boot while the animation is playing?
[Nexus 5 Original Android Development] kted:
Same here.

Autoflashed R93 while still in the previous security update and got in a bootloop that rebooted the phone approximately 20 seconds after it completed the boot.

Flashed the latest MM (keeping data) rooted, autoflashed again R93, bootloop again.

Flashed the stock kernel and had to root again.

Then cleared FKU's data, reflashed R93 and all is OK now.

Must be something wrong there. It was not a fluke, happened twice in a row.

I don't know which of the steps fixed it (flashing stock first, or clearing FKU's data) since I was in no mood for a scientific approach at 3 AM [emoji42]

Tapatalked from my Nexus 5
[Nexus 5 Original Android Development] sga999:
No, it booted up past the animation. For me, it was about a minute after the home screen showed, and I was starting to click on an icon.
[Nexus 5 Original Android Development] fatspirit:
http://pastebin.com/7tJjjZcV

Hope you'll see something useful here.
[Nexus 5 Original Android Development] fatspirit:
More info: r93 works fine on MOB31E, reboots after boot on M4B30X.
[Nexus 5 Original Android Development] Felindril:
Same here. Just upgraded the N5 to M4B30X and it cannot boot properly with kernel r93 (reboots during starting process).