yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] wingoku:
I think currently OS is capable of running different processes on different cores, however it cant run single process on multiplr cores. There are a APIs that you can call to explicitly execute your on multi threaded and multi core environment. However most apps don't use them, if Google can automatically divide those tasks to run on multicore, it will make differnece of night and day. I am not really , how can this be done effectively but if resources are put into figuring out this, it can be done.
[Nexus 5 Original Android Development] nmlssit:
How to properly test the limit of my phone? I was setting every freq (following your table from the top) in Kernel Adiutor when suddenly the phone crashed.

I mean, is there some kind of crash log that says at what freq my phone crashed? Meanwhile it's official, I can't handle -100 offset

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] marf28101995:
No, so you have to test all the frequencies one by one... I know it takes time that's why I didn't finished mine yet ;)
[Nexus 5 Original Android Development] Vaizen:
Well I don't know about you but with latest BlissPop and Blu_Spark after setting up the kernel O experienced one random reboot but that was all. After that my setting set on boot applied with no problems and not a single random reboot. That is why I haven't had the chance to publish a syslog.
[Nexus 5 Original Android Development] daweeze02:
Can someone help me. I flashed this on my Pure Nexus rom and can only boot to fastboot now

nexus 6 fall-through from normal boot

I am flashing the rom again now to get it back up
[Nexus 5 Original Android Development] nmlssit:
This is Nexus 5 subforum ?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] daweeze02:
lmfao oops I thought I grabbed the nexus 6 kernal...... Well this was a first thanks
[Nexus 5 Original Android Development] nmlssit:
Yay! Thank you for the tips! Not even finished yet, just -75 general plus UVed more 300 and 422 MHz

Now I have to test the phone on mobile data only.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Arstoien:
The UV guys could go to a UV thread. I'm not sure how many people would be interested in uv table that works on your devices. Besides, finding the limit to where your device doesn't crash for one day, isn't what I would keep my device on. I'd always go a step or two higher. Not worth the risk for such minimal benefits. Plus, too much undervolting may cause variety of issues, not just OS crash. Just google the stuff and find credible sources.
[Nexus 5 Original Android Development] sroma1980:
Forget undervolt! It overheats the cpu ergo the phone and it caps your cpu performance with little or none gain on battery. Just cap cpu in mhz and the gpu. I use 1.5 mhz on all cores and gpu to 320. Thats good enough for most usage, including heavy games!
[Nexus 5 Original Android Development] nmlssit:
LOL UVing IS reducing the heat by the meaning of the term undervolt itself. Plus, I flashed this kernel with stock setting and I got ~3hrs SOT. After I set the cpu freq at 1700, modified hotplug, GPU at 320, power saving aggressive but i still got ~3hrs of SOT.

Now I ONLY UVed and magically gained 2hrs more in SOT, here's your "none gain in battery".

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] sroma1980:
Ok. Its works for you. For me its the opposite.:confused:
[Nexus 5 Original Android Development] xlife18:
Hey [MENTION=3873953]eng.stk[/MENTION], could you please add faux's sound support to your kernel? I remember your previous kernel code_blue had it.
[Nexus 5 Original Android Development] MrMarques01:
This has been discussed already. Faux sound is buggy on Lollipop, hence it won't be added.
[Nexus 5 Original Android Development] frikakwa:
Are you kidding? It has been discussed 10000 times... and this won't be added!

http://xdaforums.com/google-nexus-5/orig-development/kernel-t2697951/post62540183#post62540183
[Nexus 5 Original Android Development] xlife18:
Calm your horses people, I was not aware of any issues since I never had any (On lollipop while using Code_Blue). Now I know it is gone for good.
[Nexus 5 Original Android Development] odin13:
Faux Sound works fine...you just need faux' app to control it properly :)

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] Arstoien:
People jump because that's been asked many times, and before requesting something (not even talking about asking), it's a common sense to search first. Atlantis has even asked to stop discussions on this topic.
[Nexus 5 Original Android Development] marf28101995:
but this is blu_spark thread and the dev is Mr Rui Santos or as everybody know him [MENTION=3873953]eng.stk[/MENTION] ;)
[Nexus 5 Original Android Development] Arstoien:
Lol, of course my bad, I keep messing up the threads these days. Bud yeah, eng.stk asked for that.
[Nexus 5 Original Android Development] ynoterdep:
SnoopSnitch

What would the development path be to get SnoopSnitch supported in blu_spark for the Nexus 5 and 6?

https://opensource.srlabs.de/projects/snoopsnitch
[Nexus 5 Original Android Development] alen1901:
[MENTION=3873953]eng.stk[/MENTION] you plan on getting 5x or 6p? I hope blue_spark for nexus 5 will be maintained until next nexus phone with snapdragon 820. [emoji14]

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] eng.stk:
None. I'm a Moto G 2015 user now and I'm cool with it.

Google continues playing with the prices in Europe, I learned my lesson with shamu.

6.0 build is pretty much certain, but I will not support N5 (or N6 for that matter) until the end of times...
[Nexus 5 Original Android Development] alen1901:
Yeah, prices are too high in my country too (phones wont be availabe until at least january). I will camp with n5 for one more year, then ill jump one whatever phone has fingerprint reader and s820, i hope for nexus device. Until that.. New n5 battery order. :D

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] ofer6483:
Prices are high, but otherwise it will be impossible to sell my n5....
[Nexus 5 Original Android Development] bigknowz:
No new Nexus

Sorry to hear I won't be enjoying some blu on N6P, at least my son will when he gets my N5. It is unfair that Europe has to pay so much.
[Nexus 5 Original Android Development] nmlssit:
Anyone else experiencing a huge battery drop while stand-by on M?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] bgboii:
So I had 22% of battery and so I plugged in my phone to charge. I decided to reboot it while charging and when it boots up it shows 40%. Why does it do that? And what should I do to fix this?
[Nexus 5 Original Android Development] Primokorn:
Not related to blu_spark. The answer has already been given: "New n5 battery order" :)
[Nexus 5 Original Android Development] ast00:
Trust me, it can always get worse. I'm Hungarian and we have 27% VAT and we earn half as much money as the most part of Europe.
[Nexus 5 Original Android Development] pianistaPL:
Hello, beautiful. (Root works).
[Nexus 5 Original Android Development] nmlssit:
Any strange behaviors? I've been reported the phone is not going into deep sleep properly, but who told me that is not using blu_spark.
[Nexus 5 Original Android Development] pianistaPL:
Hmm, that can be true, but I have to power off my screen for awhile to be sure.

However, Android 6.0 is really smooth, SMOOTHER than Lollipop. Can't wait for custom ROMs.
[Nexus 5 Original Android Development] eng.stk:
That's what you get using crap other than blu_spark lol
[Nexus 5 Original Android Development] chris096:
Does root work with M release and blu_spark?
[Nexus 5 Original Android Development] craigacgomez:
Should work just fine. Permissive SELinux will allow root, and the rest of the kernel changes are relatively minor (comparing the AOSP kernel source)
[Nexus 5 Original Android Development] tmihai20:
Can somebody tell me if the battery optimization are still active with blu_spark? Does the kernel need anything special for this to work?
[Nexus 5 Original Android Development] chris096:
Ok I flashed kernel -> reboot (just to be sure :P) -> flashed supersu

It worked fine without any bootloops and apps receive their root permissions, thank you again!

Inviato dal mio Nexus 5 con XDA Forums
[Nexus 5 Original Android Development] coffeecore:
Can't wait for blu_spark marshmallow, stock image is really snappy :D
[Nexus 5 Original Android Development] tmihai20:
Using the latest available recovery (2.8.7.0) and this kernel I was able to root M. Just so you know. Do not flash the su binary and try to boot with stock kernel, you will get a bootloop.
[Nexus 5 Original Android Development] tylerdurden83:
Can I ask you which root guide did you follow? Cheers
[Nexus 5 Original Android Development] pianistaPL:
Just flashed SuperSU 2.49 after blu_spark.
[Nexus 5 Original Android Development] UnknownzD:
I just want to add something to my last post. Clearly your init.rc for Android M is still outdated, and if you have a look at the official git source, you will see that it is different. That's may be the reason why your kernel can't boot any ROM containing f2fs partition as at this moment, but I am not really sure atm.

From https://android.googlesource.com/platform/system/core/+/android-6.0.0_r1/rootdir/init.rc

service vold /system/bin/vold \
--blkid_context=u:r:blkid:s0 --blkid_untrusted_context=u:r:blkid_untrusted:s0 \
--fsck_context=u:r:fsck:s0 --fsck_untrusted_context=u:r:fsck_untrusted:s0
class core
socket vold stream 0660 root mount
socket cryptd stream 0660 root mount
ioprio be 2

Edited:

Okay, it is clear that the way that you unpack the existing boot.img and re-use the extracted file, will cause the device to enter a bootloop. So, for everyone who is going to use this kernel without flash the stock Android M kernel before (aka dirty-flashing the system.img only), they will have some troubles unless they have modified the ramdisk file on their own. I will make a detailed simple method in here for people who wants to do an update to Android M with this kernel, rather than re-flashing the entire phone.

For people who has tried to update your phone with the dirty-flashing trick, and then get boot-looped with this kernel, here is how to fix the problem. Or if you want to try to update the phone without wiping the entire phone, you can try the following if you want.

First way (easy way):

1. Make the phone entering the fastboot mode

2. Just flash the system.img

3. Flash the stock boot image extracted from factory image via the "fastboot flash boot ......" command

4. Flash TWRP / Multirom TWRP to the recovery partition via the "fastboot flash recovery ......" command

5. Run the zip file in the recovery mode, either using ADB sideload or using the MTP connection to transfer it.

Remember, if you forget to flash the stock boot image / kernel before flashing the zip file, your phone will enter into boot loop, because the init.rc and the init.environ.rc never get updated with the old 5.X kernel.

Second way:

1. Extract all the init file from the stock Android M boot image

2. Repack them to the blu_spark kernel with Android Image Kitchen or edit the editramdisk.sh script to include the init.rc file and init.environ.rc file into the zip file.
[Nexus 5 Original Android Development] eng.stk:
There is no mine init.rc, because blu_spark uses the one in the boot.img installed at the moment.

So if you flash blu_spark on top of factory image boot.img, it will use init.rc from factory image boot.img.

Same applies for other ROMs. It uses init.rc from the ROM boot.img

It will not make bootloop or whatever, don't post useless hackings.

It's clear in OP that people should have ROM in clean state before flashing blu_spark.

Upgrading from lollipop (or M3 for that matter) is the same always was.

fastboot system.img, fastboot boot.img, flash blu_spark (and root, busybox, etc)

It will update like a normal OTA, all data will be kept
[Nexus 5 Original Android Development] UnknownzD:
You never say something like this to warn people who is going to upgrade the Android M, and tbh, even in that case, your kernel will be using a lot of resources coming from other kernel, which could be a violation of GPL or license provided with these resources.

And stop saying your kernel is perfect, ask anyone who is currently using your old 5.X kernel to update the kernel to 6.0 one without flashing the stock kernel at once, the phone will stay in the boot loop forever. And it is clearly that you NEVER mentioned that in the OP.
[Nexus 5 Original Android Development] j0hnh0lmes:
Your an ass. Please see yourself out. Running his kernel on 6.0 with no problems. Many others are reporting running fine also. The problem is YOU. K thanks bye.
[Nexus 5 Original Android Development] eng.stk:
Sure, the kernel isn't noob proof.

Any person in perfect mind will use a system.img from M and a boot.img from L? That's ridiculous.

Now stop being annoying and go troll somewhere else.
[Nexus 5 Original Android Development] ^Reloaded^:
Do you know what a kernel is ??
[Nexus 5 Original Android Development] tmihai20:
Guys, do not feed the trolls. He knew exactly where to hit Rui, because he left the kernel development once. Bootloop only appears if you try to root Marshmallow with the stock kernel.
[Nexus 5 Original Android Development] eng.stk:
blu_spark r30

All right crew!

New build is up, mellow style ;p

root is now available in enforced mode thanks to chainfire.

Just go to SuperSU thread and download the kernel zip http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Extract the boot.img (not a flashable zip)

go to recovery, flash boot.img, flash SuperSU v2.50, flash blu_spark

Profit
[Nexus 5 Original Android Development] emerica243:
Was using R25 M just fine. Flashed R30 and stuck at boot logo.
[Nexus 5 Original Android Development] marf28101995:
That happens when you don't follow instructions...
[Nexus 5 Original Android Development] emerica243:
Im able to flash a boot.IMG in twrp? I thought it was zips only.
[Nexus 5 Original Android Development] Arstoien:
It is (you can't flash img through the recovery). You need a pc to flash img
[Nexus 5 Original Android Development] emerica243:
found a button that lets u flash IMG files through TWRP...got it all working with R30. My apologies with not following the Eng.Tks post above
[Nexus 5 Original Android Development] anazhd:
It works! Gonna try how it goes. 4hours sot on stock kernel + the new battery optimization in marshmallow. Gonna see if blu_spark can do better :)
[Nexus 5 Original Android Development] ead_25:
i'm donwload .zip and flash in twrp but bootloop? help me please. thank a lot
[Nexus 5 Original Android Development] :
Thanks dude. Was just waiting for this. BTW, this is an awesome kernel.
[Nexus 5 Original Android Development] eng.stk:
Because you're rooted and you didn't follow the instructions on the damn release post.
[Nexus 5 Original Android Development] Ben36:
Does this kernel modify system files on installation?
[Nexus 5 Original Android Development] tmihai20:
You must follow the steps once for Marshmallow. I had flashed r25 before, flashing f30 over it led to a bootloop. I flashed stock boot and stock system images, just to be sure and then followed the mentioned steps I assume that from now on we will be able to flash new blu_spark kernels over the existing ones.
[Nexus 5 Original Android Development] luckana:
U just need to flash the modified boot.img from chainfire beforehand. Nothing that hard
[Nexus 5 Original Android Development] marioemp2k7:
The only changes this kernel makes to the system is to rename the current sysctl.conf, thermal-engine-hh, mpdecision and power.msm8974.so.
[Nexus 5 Original Android Development] 7sen:
Boot loop here
[Nexus 5 Original Android Development] ramig:
No problems here, thanks
[Nexus 5 Original Android Development] axl30:
reboot with antutu benchmark or crash at 3d test
[Nexus 5 Original Android Development] Balino:
Happens on elementalx aswell... I think antutu isn't updated to work with android 6.0.

But for me it just force close
[Nexus 5 Original Android Development] timmygadget:
Installed latest kernel as per instructions, running very smooth☺
[Nexus 5 Original Android Development] alexxandro84:
can you tell me the steps to get root and this kernel? using nexus root toolkit
[Nexus 5 Original Android Development] Eltorito94:
Version r30 is compatible with cyanogen 12.1?
[Nexus 5 Original Android Development] rpr69:
Followed instructions to a T, worked perfectly. Thanks again for letting us use your work eng.stk!
[Nexus 5 Original Android Development] hectorviov:
There's no 5.1.1 version to download, so I'm guessing it isn't...
[Nexus 5 Original Android Development] j.llorente:
Root is not workink OK for me. SuperSU works OK, but LMT doesn't work correctly, and Kernel Adiutor neither, if I try to delete a build.prop line, the app FC. With other kernels is OK. With blu r25 in Android 6.0 Final and supersu 2.49 is OK. But with blu r30 and supersu 2.50 not.
[Nexus 5 Original Android Development] eng.stk:
Nothing to do with kernel.

Change of selinux context sometimes derp apps. clean flash if you must.

All root apps that worked in M3 wirk the same in 6.0

No problem at all with Adiutor.
[Nexus 5 Original Android Development] fajarlazuarding:
I can't edit build prop either using root explorer or kernel adiutor editor, seems like RW isn't working. But the root is working nicely. Is there anything wrong?
[Nexus 5 Original Android Development] mendozaram:
Anyone using this kernel with xtrasmooth (6.0) ?
[Nexus 5 Original Android Development] AndresOrue:
Thank you so much installed as OP instructions and working like a charm ( root working perfect in stock Android 6 )
[Nexus 5 Original Android Development] eng.stk:
Did you guys upgraded from 5.1 to 6.0 or started from 6.0 clean?
[Nexus 5 Original Android Development] fajarlazuarding:
Clean flash. I did exactly what op said about flashing steps. I'm not sure what's wrong on my side
[Nexus 5 Original Android Development] eng.stk:
Welll on my device I upgraded from 5.1 to 6.0 and I have no major issues.

But for some, the rw issue manifests when ro.secure=1, like in stock kernel (and the one patched by chainfire).

I will not patch blu_spark to ro.secure=0 because it's a security feature and some apps like bank apps don't work without it.

And things are still in development, it takes time. In the words on Chainfire http://xdaforums.com/showpost.php?p=63188419&postcount=2061

So if you must, find a base boot.img with ro.secure=0 and flash blu_spark after.
[Nexus 5 Original Android Development] alen1901:
Anyone has problem with titanium backup restoring apps? I followed instructions (in first i just didnt flash blue spark kernel), and when go to restore app it says "analisis error", "problem with package analising", something like that. Then i flashed the kernel and still the same. I tried few backups i made before which were working correctly on lollipop. Also, dont flame me, but i use Lucky patcher to remove adds from some apps where adds are popping all over, and it says " root not stable, update your root". And yes i installed busybox. It has to do with SElinux permissions?

EDIT: also wifi takes a long time to connect comparing to lollipop, looks like i have an old and slow phone.. anyone experience the same?
[Nexus 5 Original Android Development] marf28101995:
Nope not on my side ... So its a clean install right ?

Anyway I'll say this here but its not directly to you its to all users

You guys just clean flash and the 1st thing you do is what ?

Restore data from previous versions lol this is 6.0 now you should start all from the ground only once because they backup the apps and data now on 6.0

So if you clean flash don't restore **** from previous android versions..it won't be clean anymore and I'll probably cause problems on your side...

I flashed factory image

Twrp

Chainfire's kernel image

Su 2.50

Blu_spark

And all is working perfect this way so if you don't follow this don't come here tell x y z isn't working lol
[Nexus 5 Original Android Development] alen1901:
thats what titanium is for, to restore apps you need. i updated it to latest version compatible with 6.0, on lollipop and marshmallow, and what im getting is, that titanium cant restore any app on marshmallow, and still it can on lollipop. and if i go to install app manually, it works (even though its not updated for marshmallow). so either its some SElinux stuff, root or something else.
[Nexus 5 Original Android Development] fKm:
I don't have any problems with restoring apps via TB with stock ROM and blu_spark. There is something you are doing wrong.
[Nexus 5 Original Android Development] marf28101995:
Yes this is just a temporary way to root I think, that's why chainfire is here

Anyway we will see later because this is all recent :)
[Nexus 5 Original Android Development] xeraphael:
[MENTION=3873953]eng.stk[/MENTION],

I was wondering if it would be possible for you to include the ramdisk changes on your kernel, so we don't need to flash Chainfire's modified kernel first? But no worries if it isn't.

Thanks.
[Nexus 5 Original Android Development] eng.stk:
Possible? Yes

Will I do it? No

That would bring problems to future custom ROMs and on the other hand supersu is in constant development so I'll keep it as it is.

Works with present implementation and should work with the future ones also.
[Nexus 5 Original Android Development] xeraphael:
Sure. Thanks all the same. :)

But out of curiosity: how would this affect custom ROMs? Wouldn't any ROMs that want root need those policies in the ramdisk anyway?
[Nexus 5 Original Android Development] eng.stk:
Sure custom ROMs will need the new su policies added (if in the meanwhile chainfire doesn't come up with other way) and will be pre rooted.

The problem is that if I overwrite sepolicies entries in custom ROMs with the stock ones (which is what we have), it would derp features that have specific rules added on custom ROMs (custom entries would be overwritten).

Has I said, I will keep it simple and open because the future waill change quite often.

And I have better things to do that constantly update kernel releases because of stuff that is not directly kernel development related.
[Nexus 5 Original Android Development] rpr69:
I have the same problem with Kernel Adiutor and build.prop editing, but it works in ROM Toolbox Pro. All I changed was the LCD DPI, not sure what RTP does differently, but it works.

For the record I did a complete wipe of the phone, installed 6.0, and then rooted using eng.stk's process, and have had no issues thus far, other than the above, which has a work around.
[Nexus 5 Original Android Development] yukkio:
Hi, I have my data partition with f2fs will it bea problem upgrading to 6.0 plus blue active? Thanks.
[Nexus 5 Original Android Development] tubazeppelin:
Do I still need to flash the boot.img if I'm already on 6.0, rooted, and using another custom Kernel? Or can I just flash blu_spark and go from there?
[Nexus 5 Original Android Development] pianistaPL:
It shouldn't be a problem.
[Nexus 5 Original Android Development] fajarlazuarding:
Well, ill try another stock flashable zip later when I have time. Thanks for the response tho.

Unfortunately, I haven't and can't buy RTP atm. Seems like I have to stick with it now. Thanks mate for the heads up.
[Nexus 5 Original Android Development] rpr69:
RT Lite allows build.prop editing, just tried it.
[Nexus 5 Original Android Development] SGT John Doe:
Don't know if i should blame the Kernel or Rom, but i start here to see if someone else has the same problem.

Every time i play a game on my phone it freezes up or get very slow (several minutes just to close app) after a couple minutes of gaming. Feels almost like a memory leak issue.

I've tried several different CPU governors.
[Nexus 5 Original Android Development] andresee:
What rom? No issues on mine with games. But im running stock 6.0 and r30 with SU 2.50
[Nexus 5 Original Android Development] SGT John Doe:
Cataclysm