yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] mr.ace:
yes i know but some important thing is changed on this update
[Nexus 5 Original Android Development] eng.stk:
No, that's only for HMP devices.

They created a new kernel branch for n5 android-msm-hammerhead-3.4-marshmallow-mr2 but it's the same as previous android-msm-hammerhead-3.4-marshmallow-mr1

No kernel changes atm.
[Nexus 5 Original Android Development] udnekzl:
you are fast. thank you!

wonder why google made a branch separation anyway
[Nexus 5 Original Android Development] tmihai20:
Maybe they want to test Android N on Nexus 5. This would be an absolute surprise. I will get Android N on my Nexus from PureNexus, most likely.
[Nexus 5 Original Android Development] eng.stk:
What's that got to do with anything?

They probably want to keep the same tags across devices.
[Nexus 5 Original Android Development] tmihai20:
I was thinking they may want to use that branch as a base for the Android N Nexus 5 kernel. Aren't there 2 branches for the same kernel? This was my understanding.
[Nexus 5 Original Android Development] eng.stk:
There's several branches for hammerhead tree since 4.4, marking OS updates (5.0, 5.1, etc) or same OS but new baseline (release, mr1, mr2 etc)

Doesn't mean nothing besides Google making a common tag to several 6.0.1 devices

If they would make a N (preview) branch they would already done it.
[Nexus 5 Original Android Development] tmihai20:
I forgot that Google did that, this is also a common practice. I got a little too excited about it. Thank you for clearing it up.
[Nexus 5 Original Android Development] nmlssit:
Am i The only with some kind of delayed feedback with fastlane 0? Everything stock, rom too.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] amir7777:
I'm finding a bit of stutter when I open my notifications from the lockscreen. It opens the app but before opening completely stutters a little

Sent from my Nexus 5
[Nexus 5 Original Android Development] marf28101995:
Set Fastlane to 1 if you don't care about that extra battery that it gives you
[Nexus 5 Original Android Development] Primokorn:
I got it working :p

1. Remove KA 0.9.9.4 (Force stop, clean app data, uninstall) and clean everything with SDMaid

2. Copy this script into /system/su.d (permissions 0777 to be sure lol)

#!/sbin/sh
echo 95 > /sys/class/timed_output/vibrator/amp

3. Reboot and install KA 0.9.9.3

4. New reboot to check the vibrator strength at boot.

KA always displays +1 to the vibrator strength so I put 99 in my script. Thanks for your help mate :good:

/system/init.d/ is depreciated since MM but AFAIK su.d is reserved for SuperSU scripts (closed-source with a confused future) so what happens if we are using CM SuperUser or phh's SuperUser?
[Nexus 5 Original Android Development] eng.stk:
Glad you got it :highfive:

Kernel Adiutor 0.9.9.3 would work the same, some people tested it for me on DU and others ROMS and it actually works fine.

There is no init.d support since LP, su.d does exactly the same but with parameters to correctly launch the daemon properly.

Any init.d script will work on su.d, nothing closed source about it. The path is /system/su.d to normal installs, but in MM systemless is /su/su.d

Since I only care about stock ROM, I don't care about superuser, but in case of CM init.d should work idk.

Supersuser is bugged for several root applications and other stuff.
[Nexus 5 Original Android Development] xeraphael:
[MENTION=3873953]eng.stk[/MENTION],

Since blu_plug supports a "plug_threshold" tunable, I had the idea of underclocking cpu0 and cpu1, and asking the hotplug to prioritize unplugging cpu2 and cpu3 first whenever possible.

Namely,

echo 1267200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1267200 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

echo "0,0,1,1" > /sys/module/blu_plug/parameters/plug_threshold

cpu0/1 will be underclocked and running for normal tasks, while cpu2/3 will (in theory) kick in only at higher loads and get unplugged first when load drops back down. Idea is to focus on battery savings, obviously.

Just wondering if you've already tried this before and I'll be wasting my time, or if you think it's worth a shot.
[Nexus 5 Original Android Development] Mrcactuseater:
Kind of like the big.LITTLE idea? Seems cool!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 5 Original Android Development] eng.stk:
That doesn't work because cpu policy is shared with all cpus.

Also it would need per cpu changes added to kernel, make blu_plug to work with per cpu, etc.

I don't think in this SoC that it pays, an Non HMP device is a Non HMP device.
[Nexus 5 Original Android Development] xeraphael:
Alright, thanks man.
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r75

All right crew!

New build is up, go get it!

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[Nexus 5 Original Android Development] drac0:
****ing fabulous!!! :good::good:
[Nexus 5 Original Android Development] eng.stk:
Couldn't say it any better :highfive:
[Nexus 5 Original Android Development] nexterultim:
Hi, Eng.stk! I've made a nice mod for your kernel. Source code and history are there: github.com/alesaiko/blu_spark

A main change is Devfreq framework, which handles all the GPU transitions. It's the only kernel on AOSP that has it. Please, check it out and say your opinion about it. Of course, if you're interested, you can grab parts of code or a source fully, I don't need any credits.
[Nexus 5 Original Android Development] eng.stk:
Thanks, but I dont need or want CAF cruft on blu_spark.
[Nexus 5 Original Android Development] nexterultim:
It's preety stable although. I was experiencing random reboots on original bs, logs said it was wdog_bite, while running this kernel I've no problems. If it's stable, why not?
[Nexus 5 Original Android Development] Chitown021:
What sound modifying solutions do you use with this kernel? I've been using EX for awhile now and the ability to increase the sound output is baked into the features. Just curious, I've been wanting to experiment with other kernels, but I've got to be able to up the sound as the standard is just too quiet.
[Nexus 5 Original Android Development] nexterultim:
There is no sound control in original bs
[Nexus 5 Original Android Development] CataHd:
Where did you find that?
[Nexus 5 Original Android Development] Chitown021:
Thanks, that's what I figured, just wondering what people that use bs use in addition to it to control volume. I'm guessing something like V4A?
[Nexus 5 Original Android Development] Eltorito94:
link for the rom? your impressions ?
[Nexus 5 Original Android Development] nmlssit:
+1

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Arthur4ik:
is there support for Kali Nethunter?

https://github.com/offensive-security/kali-nethunter/wiki/Modifying-the-Kernel

https://idlekernel.com/nethunter/nightly/
[Nexus 5 Original Android Development] yuannovesa:
Best kernel with best rom...

I love this build R75 with some tweak and Lspeed...

Thx dev.. :good:
[Nexus 5 Original Android Development] iPsychoGeek:
#IWantToBelieve
[Nexus 5 Original Android Development] jazzh:
This r75 is the best I've tried so far. I'm getting 4h SoT with MMB29X with 2 year old battery. it works so good I'm afraid to try r75 on MOB30D build :)

Has anyone tried this combination, working well I assume...?
[Nexus 5 Original Android Development] rpr69:
It works, I haven't noticed any difference in battery, but I also don't pay all that much attention to it. If I had to guess, about the same.
[Nexus 5 Original Android Development] ensboarder:
I have tried some apps on the play store but doesn't work
[Nexus 5 Original Android Development] nmlssit:
Dude can we have some explanation?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Stevica Smederevac:
He edited the build. prop.
[Nexus 5 Original Android Development] nmlssit:
Some others guessed that too, but i don't want to believe them yet, it's too lame.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Stevica Smederevac:
I have no other explanation why he's not sharing with someone who is interested.
[Nexus 5 Original Android Development] nmlssit:
Could be closed beta, he sometimes posts blu_spark versions not yet released. But i want answers. Im very thrilled For a PA comeback.

Sorry For the OT [MENTION=3873953]eng.stk[/MENTION]

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] drac0:
He is the blu_spark team member, is why sometimes he waves with closed beta releases at out faces lol. [MENTION=4939514]marf28101995[/MENTION] share that PA link mate, people are getting nervous! :p
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r78

All right crew!

New build is up, go get it!

This features the all new HZ race google started on N5X and N6P backported to the N5, enjoy!

http://www.androidpolice.com/2016/0...e-improvements-a-do-not-disturb-fix-and-more/

Also lot's of upstream stuff :)

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[Nexus 5 Original Android Development] Primokorn:
Supercharged updates, I love it! :D
[Nexus 5 Original Android Development] Eltorito94:
Great! You are on fire! :D
[Nexus 5 Original Android Development] adrianocolvero:
Sorry guys, but what exactly is "HZ"?
[Nexus 5 Original Android Development] nexterultim:
HZ - is a tickrate of system timer. In r78 it was set to 300 instead of stock 100, like in the newer Nexus devices (5X, 6, 6P). The more value is set - more performance you get. Timer impacts all the real-tasks, so it's a very important value, that can truly improve the performance and responsibility. But I'm not sure about the power consumtion. Need to test a little bit more
[Nexus 5 Original Android Development] phantom146:
We will encounter little to no battery drain on this one. Though this vastly increase performance, the system timer of 300 wont compromise the battery since its still a small jump on stock. Basically its like a sync_frequency syncing from 422mhz rather than 300mhz.

Though ill be testing this one and see where this goes :)
[Nexus 5 Original Android Development] Joy Bangla:
**Applause**

Now i'm scared to turn on fast lane. You should rename it to hyperspeed lane as my device is already in the fast lane!! from an hour of usage i can say battery consumption is almost similar to r75.
[Nexus 5 Original Android Development] jazzh:
My overnight deepsleep usage with r78 is excellent, seems like the same as with r75 - 2% overnight. ;)
[Nexus 5 Original Android Development] eng.stk:
Yeah me and my team have been testing it for a week and all points to better performance (not 200%better, but better) with +/- the same battery usage.

Win win so far :)

Ahahah awesome stuff dude, just made my day!
[Nexus 5 Original Android Development] kawadana:
Hi people, i've a weird issue...I'm using blue_spark since an year. I recently had to return totally stock so I flashed the latest factory image, than root and twrp (all working good and fine). The problem is that when I flash blue_spark+SuperSU (twrp 3.0.2), flash goes well without errors but when I reboot system, kernel is the stock one and not b_s... I know that's a developer thread but it's the first time I got this sort of issue and I don't know what to do to solve it.

I'm doing something wrong? Thank u for the support! [emoji482] [emoji4]
[Nexus 5 Original Android Development] GorfDroid:
Is anyone else getting stuttering audio with these most recent kernels? I am still using version 63 which is the latest one that doesnt give me problems.
[Nexus 5 Original Android Development] vipinbp:
Go ahead and use the latest.. I've never had stuttering audio.. And I've always used blu-spark kernels..
[Nexus 5 Original Android Development] eng.stk:
Nope.

You're having SuperSu to restore previous boot.img

Just flash blu_spark zip

People should know this things by now (or read twrp log output)
[Nexus 5 Original Android Development] carlese:
Don't know if it's just me, but it seems that v78 is a little bit laggy and more battery consuming.. For now I found that v75 is by far the best I tried..
[Nexus 5 Original Android Development] GorfDroid:
I have to downgrade back to r63. I can't take the audio glitches which I haven't had to deal with since android 5.1 came out.
[Nexus 5 Original Android Development] starche_old:
I'm running Blu kernel @1276 and undervolting. Guess what - buttery smooth and blazing fast.

I tried pretty much all kernels available here and this one do not have any lag whatsoever.

Oh, and did I say is by far the very best battery life?

Of you're using kernel auditor, clean cache and reinstall the app.
[Nexus 5 Original Android Development] drac0:
Dude why so? No need to downgrade. I'm with the spark sorcery from the very beginning going back to code_blue era and no audio glitches whatsoever! I'm listening my fav music with Phonograph player every day on my way to work and back and never ever experienced any glitches with spark. Also I'm using almost a year old mod by [MENTION=4269794]klavsanson[/MENTION] which is workin' like a charm with blu_spark'd PureNexus. There is something on your end for sure. Try clean flashing. Cheers!
[Nexus 5 Original Android Development] GorfDroid:
It is indeed the new android m kernel interfering with viper4android. I found the answer here:

http://xdaforums.com/nexus-6/themes-apps/viper4android-t2952137

And here:

http://xdaforums.com/showpost.php?p=65346831&postcount=6223
[Nexus 5 Original Android Development] ChemBot:
Is anyone having issues with dt2w? I flashed 78 on top of 75 and dt2w is broken. It seems like it'll work once after a dozen taps and nothing after that. I wiped kernel audiutor data, rebooted, reapplied my settings and no go. Flashing back to 75 results in dt2w working fine.
[Nexus 5 Original Android Development] sroma1980:
Same here!
[Nexus 5 Original Android Development] Creative9170:
And also same here!
[Nexus 5 Original Android Development] eng.stk:
On stock ROM is the same as it always was, can't replicate.

All normal here, must be something particular to your setup

No lags, maybe a little bit more power hungry but not that much

I'm happy with the config.
[Nexus 5 Original Android Development] carlese:
I had previously dirty flashed v78 over v75.. Now I wiped system, cache and dalvik, reflashed rom and everything seems smooth, no lags and battery in par with v75 which is really great..
[Nexus 5 Original Android Development] ChemBot:
I'm using the latest Chroma. I understand that you do not support other ROMs, I just wanted to share my results with others in my situation. Also, I ended up trying a full wipe and reinstall of Chroma with 78 and I'm still having problems with dt2w, but I noticed something strange. On 75 and older it only takes one finger tap to wake it up, but on 78 I've noticed that if I double tap with 2 fingers at the same time the screen will wake maybe 80% of the time on the first try. Just FYI
[Nexus 5 Original Android Development] GorfDroid:
The interactive governor (and interactive like governers like blu active) in marshmallow kernels is causing problems with v4a. See my previous post. I followed the fixes and everything's fine now. I can finally use up to date bluspark kernels!:D:D:D
[Nexus 5 Original Android Development] xmaciek82x:
If you enable fastlane, the v4a issues will go away and you can stick with blu_active.
[Nexus 5 Original Android Development] GorfDroid:
It works! Awesome.

Thanks!:D:D;);):):)
[Nexus 5 Original Android Development] eng.stk:
I finally manage to replicate I think (needed my wife help lol)

Maybe the panel has some HZ dependency that makes it so, idk. Altough I don't see anything, maybe original authors patch it in future to make it work better with new changes.

All in all it's a hack and I don't use dt2w, if it's derped I'll probably remove it.

I don't design anything with an app or personal preferences in mind (other thany own ofc).

Sound with MusicFX and AudioFX is fine on stock setup, I don't care about xposed or viper audio or any of that, sorry.

If your dsp app is power hungry, use the kernel tunables accordingly, that's why they are there :)
[Nexus 5 Original Android Development] alen1901:
I must say that with latest version im getting constant better battery results, after testing it for couple of days. And performance is awesome too. Clean flash of rom and kernel. Nice stuff.

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] nexterultim:
There is a dependency in DT2W driver. You should modify timinings this way:

#define PWRKEY_DUR	180 in "wake_timeout.c" and

#define DT2W_PWRKEY_DUR	180

#define DT2W_FEATHER	150

#define DT2W_TIME	150

#define TRIGGER_TIMEOUT	150

wake_lock_timeout(&dt2w_wakelock, 150); in "doubletap2wake.c"

This would fix broken gestures :3
[Nexus 5 Original Android Development] eng.stk:
Not all timers have direct HZ dependency.

But I can take a look again, we'll see.
[Nexus 5 Original Android Development] nexterultim:
It helped me although. Now all gestures work like it was on HZ 100
[Nexus 5 Original Android Development] eng.stk:
Actually I missed a HZ dependency when I first looked into it, the rest shouldn't need changes, need to test.

Thanks for the heads up :good:
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r82

All right crew!

New build is up, go get it!

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[Nexus 5 Original Android Development] Chaos2Theory:
Thanks for the new build, something i've been meaning to ask recently though is is it perfectly alright to just dirty flash the newest kernel versions on top of old blu_spark ones or should we dirty flash the rom again first?
[Nexus 5 Original Android Development] eng.stk:
Don't thank me, just hit the thanks button, that's why it exists ;)

Yes, just flash over the previous versions is ok.
[Nexus 5 Original Android Development] ChemBot:
I can confirm that dt2w works fine now on r82. Great job!
[Nexus 5 Original Android Development] fapste:
[MENTION=2696129]EmG.[/MENTION]stk something i have noticed time and again, when the phone is plugged in a socket, the phone FLIES! Even Facebook runs smooth as hell. Smooth like iPhone's UI but when I unplug the phone, the performance drops and lags are very noticeable when the battery level is below 85.

I have been noticing is for the last 4 or 5 builds. Why is this happening?
[Nexus 5 Original Android Development] Isley_:
For me it is the opposite, when I plug my phone it lags for like two minutes and then it becomes normal, but this only seems to happen when I have fast charge enabled. And same, I have been noticing this for the last builds.

The battery also gets very hot, like 43 degrees, but I suppose it is because of fast charge.
[Nexus 5 Original Android Development] shri_chanakya:
Thermal throttle would be kicking in when you put on charge. That will under clock the cpu till temperature goes down..
[Nexus 5 Original Android Development] eng.stk:
Nope there is no lag in blu_spark, ever. And i can't reproduce that behavior.

Nothing changed related to charging or whatever.

If you need more performance turn fastlane on.

Fast charge doesn't make the phone charge faster, only unlocks drawing more power from hi power USB 2.0 ports.

Which is way under default charging specs of stock charger anyways.

Battery heats up when charging (specially if you start charging from low percentage left) and it throttles to protect itself.

Nothing new.

Yep, correct.
[Nexus 5 Original Android Development] Isley_:
It's strange because when I have fast charge enabled, my phone actually charges faster. Not lying. I have only noticed this with this Kernel, it is a plus in my opinion.
[Nexus 5 Original Android Development] eng.stk:
If you use stock charger it will charge at 1200mA on this kernel, doesn't matter if fast charge is on or off (google caps the stock charger at 1000mA).

This phone can go up to 1500mA if the charger allows it (high power chargers).

The only way fast charge can affect charging time is if you're using a cheap charger detected as USB and thus using 500mA.

If you use fast charge o this situation it will try to use more amps if available (like a high power USB 2.0 PC port).

Fast charge only makes difference in USB mode.
[Nexus 5 Original Android Development] frankdd89:
I've been testing this Kernel with cyanogenmod 13 - release channel 2016-04-18 with xposed framework v83

No problems so far, everything is working flawlessly =) Thanks to the dev and happy flash everyone
[Nexus 5 Original Android Development] atomic339:
What flash first: kernel or SuperSU?
[Nexus 5 Original Android Development] bhuvan9111:
Most of the time kernel installs the supersu , even if you flash the supersu first and flash the kernel nothing is going to change. You will have both of them.
[Nexus 5 Original Android Development] eng.stk:
I prefer to flash kernel then supersu.

If you already have supersu flashed, just flash the kernel.

blu_spark zip doesn't flash anything related to supersu or superuser, will use whatever you have in your system.
[Nexus 5 Original Android Development] bhuvan9111:
Yeah others kernels do flash like elementalX, i have been using your kernel since ages like from the begining

The legendary codeblue for nexus 5 lollipop and even now i am using your kernel for best performance as well as 6hrs sot (the best so far). Thanks for this bro.
[Nexus 5 Original Android Development] shri_chanakya:
Flash supersu then kernel... Super su overrides boot image if it is system less root.
[Nexus 5 Original Android Development] kurt.gomez:
is diag mode still enabled in the latest build?
[Nexus 5 Original Android Development] Creative9170:
I can confirm blu_sparks works on MIUI 7 Marshmallow too.
[Nexus 5 Original Android Development] bhuvan9111:
Hey buddy i just wanted to check the miui 7 based on MM. So if you could give the link to xda post it would be great.
[Nexus 5 Original Android Development] Creative9170:
You can easily search it ;)

http://xdaforums.com/google-nexus-5/general/miui-7-released-nexus-5-t3188470
[Nexus 5 Original Android Development] barbocorp:
6h SOT? What's your configuration? My best was 3h SOT under Wifi connection
[Nexus 5 Original Android Development] bhuvan9111:
Max clock to 1.4Ghz (youtubing,web browsing, small games, movies, music,etc) or 1.7Ghz for big games

And min clock to 300Mhz( stock)

Governor - on demand ,

-50V undervolt cpu

hotplug:-

Max no of cpu on 3 (cores)

Min no of cpu on 1(core) ( of course )

Max screen off cpu 1 (core)

Max screen off clock under 1Ghz ( below 300Mhz would make your sound dumb if you listen to music while your device is asleep )

Screen brightness around 20-30% (always indoors )

Wake controls ( double tap to wake bottom half for 15min after screen goes off)

Wifi on all the time

No mobile data

Locations off

Sync on

Greenify,naptime

Last but not least AICP latest build with latest kernel

Average sot 4.5hrs

Max sot around 5 hrs 50min

Max stand by 17hrs ( at 4hrs sot)

Min stnad by 2hrs ( at max sot)

It seems pretty big but those are the little ones which brings a lot of difference.

And i have around 200 apps in my phone and all greenified with more than 730mb free ram all the time.

Hit like if this helps you.
[Nexus 5 Original Android Development] jazzh:
Excellent.
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r86

All right crew!

New build is up, enjoy!

If you're using f2fs, I recommend backup your data to external source in case you have any hiccups, it's a large update on the driver.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[Nexus 5 Original Android Development] eng.stk:
Since several builds, never changed it

#
# Diag Support
#
CONFIG_DIAG_CHAR=y

#
# DIAG traffic over USB
#
CONFIG_DIAG_OVER_USB=y