yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] mendozaram:
Whats your config? Did you underclock? Greenify? O similar?
[Nexus 5 Original Android Development] ltjmax:
All stock on the latest PureNexus. I use greenify for some apps, but I'm not sure it makes a big diffirence. Blu_Spark is just awesome
[Nexus 5 Original Android Development] Devil Trigger:
There's a way to set the max screen off freq?
[Nexus 5 Original Android Development] eng.stk:
Nope, that is deprecated in MM
[Nexus 5 Original Android Development] :
Dt2w On/Off ?
[Nexus 5 Original Android Development] ltjmax:
Off
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r69

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] frikakwa:
[MENTION=3873953]eng.stk[/MENTION]: you're the best Mate! So lucky to have the benefit of your kernel always up to date and more and more efficient! :good:

Edit: will be the best version ever... the sexy r69! ;)
[Nexus 5 Original Android Development] coffeecore:
This thread is always sooo quit, I guess that says a lot about your work [MENTION=3873953]eng.stk[/MENTION] ;)
[Nexus 5 Original Android Development] drac0:
****ing amazing!!!

What more is there to say, just I will keep my fingers crossed for the next Nexus hardware support. Once again thanks very much mate! Rock on! :good:

blu_spark evangelist
[Nexus 5 Original Android Development] eng.stk:
Thanks guys, rock on!
[Nexus 5 Original Android Development] stankyou:
While my Nexus 5 is happy with blu_spark, my Nexus 6P hopes that one day, there will be one for it too. :P
[Nexus 5 Original Android Development] eng.stk:
Nope, the only Nexus I will be checking out is the next ones.

But if the policy stays as it is, it will be a long time for me to come to Nexus devices again.
[Nexus 5 Original Android Development] stankyou:
Yup. I fully understand and respect your decision. It's just... it's just... hard.for.me.to.let.go.
[Nexus 5 Original Android Development] hacktheheaven:
WoW

This is my first post in this Nexus 5 forum. I have tried few other kernels but the speed, stability, and battery performance was literally awesome. Kudos to the developer. BTW I am using the latest version which is R69 with Pure Nexus Rom.
[Nexus 5 Original Android Development] Primokorn:
Another donation to thank you again for keeping our beloved N5 alive! :D

4FR07809G9726215E
[Nexus 5 Original Android Development] eng.stk:
Thanks mate, beer mode: on:good:
[Nexus 5 Original Android Development] doma8108:
Hi eng.. I just want to thank you as it's already two years I'm using your amazing kernel.. Good job, muito obrigado :thumbup::thumbup::thumbup:
[Nexus 5 Original Android Development] eng.stk:
Thanks man!

Keep it real, keep it true, keep it blu :)
[Nexus 5 Original Android Development] miseusegau:
[MENTION=3873953]eng.stk[/MENTION]...Perfect my friend..thanks..;)...:cool::cool::cool:
[Nexus 5 Original Android Development] miseusegau:
Double post sorry..:)
[Nexus 5 Original Android Development] alen1901:
had one big problem, and im not sure if its kernel related, but i think it is. anyways, my phone freezed and i left it to sit for few minutes because usually it comes back to normal. this time i had to force reboot with power button. when i did that, my phone started to optimize apps on start, which you dont get with force reboot. and when my phone fully booted i had something to see, my phone was fully erased, every single thing, internal memory too. so i checked partitions to see what format it is, and oddly somehow phone forced system partition to go from f2fs back to ext4, which wiped my whole phone?

EDIT: is it possible to format system partition to f2fs at all? i forgot if its possible, but data and cache were in f2fs and didnt change to ext4. anyways, my phone got fully wiped for some reason after a reboot.
[Nexus 5 Original Android Development] eng.stk:
Nope, but since you don't use stock ROM you 're out of support parameters.

Lot's of stuff can happen.

f2fs works fine, I use it myself in all my devices.

You can't have system as f2fs, only data and cache

Also iirc, it's not the first time stuff like that happens in your phone, maybe you have something wrong there.
[Nexus 5 Original Android Development] alen1901:
well, im using aosp rom with little addons, dev wants it to be how google made it, simple and intuitive without bloat. and i had only freezes because of chrome when i have 10 or more tabs opened. so i need to force reboot. and not even once i had a problem of device self wiping. but my friend had that once when navigation was working on some low end phone. i guess some things needs to perfectly align for it to trigger. anyways i put data and cache partitions back to ext4, and full wipe is on the way so we will see.
[Nexus 5 Original Android Development] kostelo:
Best kernel ever, especially battery-wise. I use it with dirty unicorns ROM and undervolted about -65mV every frequency step. It literally flies. Stable as rock. Keep it up man.

Sent from my Nexus 5
[Nexus 5 Original Android Development] 093236:
Oh my god!

I have the same issue a few days ago!

I am sure that I have not formatted the system partition to f2fs, only formatted data and cache to f2fs.

I have lost everything and I can just restore my internal storage's data a few months ago[emoji20]

I was using PureNexus 3/15 build with blu_spark #69.
[Nexus 5 Original Android Development] fKm:
I had the same problem last week. Suddenly my data partition was formatted and I had to restore everything. Now I use ext4 again and dont have problems so far.
[Nexus 5 Original Android Development] Arstoien:
Sorry to say but.. backups. Many different ways to automate them and not worry about anything on your phone being totally lost.
[Nexus 5 Original Android Development] ralph.bethke1:
Hi,

sorry to say that I have had the exact same issue with f2fs (for data & cache) on r69 Kernel ONLY, previous versions worked like a Charm for me. I ran into this during re-installation on my phone using latest Google stock rom. Re-installed three times with f2fs somehow automatically dropping data, which got visible upon reboots. Gladly I did backup my data before re-installation (as always). I will try to reproduce this as soon as I have time to capture logs, for now I am back to ext4.

Sorry again, but looks like the f2fs update(s) have introduced a very nasty bug.

Apart from that the Kernel is great.

Best regards

Ralph

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] autry7:
I too have lost data with f2fs. First time I lost everything second time only a few apps and all downloaded files. Both on current version. I'm switching back ext4
[Nexus 5 Original Android Development] alen1901:
Its different if you format partition 1st time, its normal to get everything wiped. But if its wiped after using it for a whole, its strange. :D

Sent from Pure Nexus 5

---------- Post added at 03:09 AM ---------- Previous post was at 03:06 AM ----------

I had app backup every week on usb, but as of marshmallow, titanium backup can no longer make backups on usb, and i dont want to upload on internet. And no memory on phone. And internal storage backup needs to be done manually every time on pc to be sure all backed up ok.

Im also glad that im not the only one, that means theres something wrong with f2fs, or there is some way to trigger that storage wipe thing.

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] 093236:
I rebooted the phone because it was very slow, and it said "XXX is updating...", just like after flashed a new ROM and the dalvik cache has been wiped.

After that, I found that all the thing, included Internal Storage has been wiped.

Luckily, I have TWRP's backup that before I update to r69

I need to find a easier way to backup the internal storage because I don't want to it every time:eek:

anyway, I still thanks the blu_sp★rk team because I still love it!:good:
[Nexus 5 Original Android Development] autry7:
Both times I triggered it was with the phone powering itself off. The first time I was installing the gsam root helper and I used the app to reboot the phone. Completely wipe. The second time the phone died while using Skype and that was only a partial wipe. All the stuff I downloaded was gone but about 50 percent of my apps survived
[Nexus 5 Original Android Development] jazzh:
I installed bluespark kernel on march mm with cata on top of it. It works great so far. If i have ext4 partitions only and not f2fs am i secure from this weird deletions you're talking about?
[Nexus 5 Original Android Development] 093236:
Actually, I don't know.

We just found some people have the same issue with some configurations are same (f2fs with r69).

And no user reported the ext4 partitions have this issue at the moment.
[Nexus 5 Original Android Development] nexttjme:
Is it ok if i use this kernel with AICP rom?
[Nexus 5 Original Android Development] Joy Bangla:
Yes you are safe. f2fs is not stable and still people use it???. You will get data corruption and only a little performance improvement.
[Nexus 5 Original Android Development] fKm:
To be honest in every single release before f2fs was stable as rock. Only with the latest build these problems occur. So your question why people still use it is unnecessary.
[Nexus 5 Original Android Development] eng.stk:
f2fs is stable and there's more to it than just performance, you don't know what you're talking about.

You had a cache rebuild, also happens with ext4 sometimes if you do dirty shutdowns.

Nothing new there.

Well I don't see a root cause and I can't replicate it in any of my devices.

Can be a bug introduced on upstream, but I think highly improbable because I only merge from f2fs-stable branch (which is somewhat tested).

But some stuff is backported, so it can be something there. I will revert to previous iteration and wait for a new tag being merged to see how it goes.

Meanwhile, your update status in TWRP is also important. On OPX I need to keep the TWRP kernel with updated components so all goes smoothly.

I had storage issues in hammerhead in the past because of this.
[Nexus 5 Original Android Development] alen1901:
I have latest twrp too. Ill test the same usage pattern on ext4 and see if i get this freezes or wipes. Maybe like you said, its some bug introduced. But if data is lost on phone force reboot, that means f2fs could force wipe phone because of lets say damaged data or cache? Like, f2fs didnt "save" stuff before force reboot, so it demands wipe?

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] eng.stk:
You missed the point: having latest TWRP doesn't mean you have it updated to latest components.

TWRP also has a kernel that needs latest updates. On OPX TWRP uses blu_spark inside so it's always updated by me because I maintain it.

f2fs doesn't delete nothing, storage control has stuff to deal with partition states and probably some dirty state is trigered (can be headers issues for instance), thus you get the clean state.
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r72

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] jazzh:
Thx. No problems so far, battery great as usual :)
[Nexus 5 Original Android Development] drac0:
I just got the very same problem with the r69 and f2fs for the first time ever!

I had to reboot normally and after some weird long boot up I just got to new device screen like everything was data factory wiped, wtf? My data partition were still there like all my files within internal storage, but I got to warning internal problem notification screen saying something got really ****ed up and now end up with completely destroyed setup.

So yeah, I got back to TWRP and restored my week old backup with r66 when everything was running perfectly all the way from initial blu_spark release. Its true r69 introduced some nasty (f2fs?) bug cos now if I try to factory reset or to wipe everything (except my internal storage) I get the warning notification that pops up upon finished first time setup boot. Crap.

If I restore back to older build with r66 again and just dirty flash new build and r72 over it, everythig seems to be fine. Crazy?

But if I deceide to clean flash and wipe everything (except my internal storage) prior to clean flashing, I'm finished again with the same internal problem warning notification on initial screen saying that only data factory will help, sadly it doesnt.

At some moment in time I will need to make clean flash so this problem will wait for me there as well.

So guys any solution for this or I'm done to completely format my device and all partitions and keep my fingers crossed that will solve this ****ing issue?

Thanks to everyone and hope this gets resolved quickly!
[Nexus 5 Original Android Development] eng.stk:
You probably derped your data going back and forth.

If I were you, I would take my stuff out of the phone, format partitions on fastboot and format in TWRP again to f2fs if you want.

Only way to get it clean clean.

See what I told about TWRP above.
[Nexus 5 Original Android Development] coffeecore:
[MENTION=3873953]eng.stk[/MENTION] You are on fire, will create a PayPal account soon so I can pay you a well deserved beer.
[Nexus 5 Original Android Development] autry7:
Also to the OP I hope my posts weren't interpreted as complaining or anything. I was simply trying to provide some information for a possible fix. I understand that wanting to be on the cutting edge means you may end up cut. I just wanted to thank you for your work and other than my issue this kernel is rock solid, fast as hell I'm loving fast lane and good battery life to boot. Keep up the good work. :good:
[Nexus 5 Original Android Development] drac0:
I did just that and everything is running smoothly. Thanks for advice and rock on! :highfive:
[Nexus 5 Original Android Development] zibiksior:
I had exact same situation when I changed rom from Cataclysm to Pure Nexus ROM. I had f2fs on cataclysm and after fresh install of pure nexus with wiping all partitions my phone suddenly restarted to factory defaults... I thought there were some problems with partitions so I flashed factory image than twrp and changed partition to f2fs again. Exactly like [MENTION=3873953]eng.stk[/MENTION] wrote. Right now no problems so far.
[Nexus 5 Original Android Development] cdonald:
I had the F2FS issue on r72 after dirty flashing from the previous version, but did not reformat partitions yet. Still no issues for those that reformatted, I presume?
[Nexus 5 Original Android Development] zibiksior:
I didn't flash r72 yet but I will do it right now. On r69 after reformat everything was ok so far.
[Nexus 5 Original Android Development] cdonald:
Let me know how it goes. I had the r72 issues after cleaning up my system with SD Maid, then rebooting (SD Maid has never given me issues before)
[Nexus 5 Original Android Development] zibiksior:
Just flashed r72 and system boot up normally. I would suggest you to make that format. I don't know what caused that kind of behavior but after reformat everything seems to be fine.
[Nexus 5 Original Android Development] cdonald:
Good to know. Thank you.
[Nexus 5 Original Android Development] mendozaram:
Question.... I already have my data partition on F2FS.... But, when i did it i forgot to format my cache partition to F2FS too. (So, only have Data on F2FS)

So... If i format my cache partition alone to change it to F2FS, i will get my phone totally formated?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] cdonald:
I had to do this before, and I'm 90% sure that if you are only formatting cache, then your data will remain intact.
[Nexus 5 Original Android Development] eng.stk:
blu_sp★rk r73

All right crew!

New build is up with Nexus April updates, 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:
Woohoo keep on rockin!!! :highfive:
[Nexus 5 Original Android Development] jazzh:
Can I apply this new r73 kernel on the previous march update mmb29v?
[Nexus 5 Original Android Development] :
Sure
[Nexus 5 Original Android Development] kostelo:
Sorry if it has been asked many times, but is there any possibilities that any kind of sound control is implemented in your kernel [MENTION=3873953]eng.stk[/MENTION] ? I mean the mic volume is kind of low in my phone and in noisy environments, the person in the other end of the line has some hard time listening to my voice. Is there any way we can increase the mic level if it won't be implemented in the kernel?

Thanks for your offer to the community.
[Nexus 5 Original Android Development] Jo_Jo_2000:
What is fastlane?
[Nexus 5 Original Android Development] Arstoien:
Two tips for you: don't quote the op, and use search
[Nexus 5 Original Android Development] Primokorn:
I'm using blu_spark r73 on Dirty Unicorns and I tweak the kernel through Kernel Adiutor (original version).

I have a bug (which is not only related to r73): the vibration strength doesn't stick after a reboot (back to 61% instead of 100%) - yeah, "apply on boot" is checked :p

DU team doesn't support custom kernels and you don't support custom roms so I'm a bit lost. Who can help? :D

I only have a kernel manager app and no manual script to tweak the kernel.

No issue with other settings (fastlane, backlight dimmer, usb fast charge,...).

What is the command to edit the vibration strenght at boot through a script? I'd like to try without Kernel Adiutor to avoid all possible risks with this app.

The following command still works?

echo 100 > /sys/class/timed_output/vibrator/amp

I have 100 in Kernel Adiutor but 99 in amp file...

EDIT: same issue by using a script. "amp" shows 60.
[Nexus 5 Original Android Development] Stevica Smederevac:
It's on all roms. If it's cm based, solution is to adjust vibration in sound settings and it will stick. Otherwise I don't know the solution :victory:. Something is wrong with Kernel Adiutor.
[Nexus 5 Original Android Development] Primokorn:
It's not related to Kernel Adiutor (see my EDIT) and DU is based off AOSP. Probably a rom issue/incompatibility though.
[Nexus 5 Original Android Development] Stevica Smederevac:
My experience is as i said. On all aosp or cm roms, same issue with KA. Only thing that worked is vibration strength in sound settings, if there is such option.
[Nexus 5 Original Android Development] eng.stk:
It's a Kernel Adiutor bug introduced in 0.9.9.4 due to vibration function refactor. Happens in other devices/ROMs/kernels also.

I just reverted to 0.9.9.3 until a fix is pushed.
[Nexus 5 Original Android Development] Primokorn:
Well, I still have the bug with a script (Kernel Adiutor option disabled/Apply on boot unchecked).
[Nexus 5 Original Android Development] eng.stk:
Probably you have some permission issues due to your setup.

Install Adiutor 0.9.9.3 it will work fine.
[Nexus 5 Original Android Development] Primokorn:
Nope, it didn't work either.
[Nexus 5 Original Android Development] Stevica Smederevac:
Confirmed, not working on 9.9.3 either.
[Nexus 5 Original Android Development] eng.stk:
That's something wrong with your ROM, messing up your cache and data. Try clearing Google Play data, sometimes it helps

ok I'll check it :good:
[Nexus 5 Original Android Development] Hatshipuh:
Didn't say I had this with your kernel which I'm using for some time now ;)
[Nexus 5 Original Android Development] unsivil_audio:
I experienced the missing apps thing (only about 30 of them were missing) after I flashed away from ElementalX. No big deal though, I keep everything backed up with TiBackup. Awesome kernel btw! I am back to experiencing great battery life, without disabling much in the way of features. I left you a small token of my thanks, and I encourage others to as well. :thumbup:
[Nexus 5 Original Android Development] eng.stk:
Yeah I got, thank you mate:good:

You should dirty flashed your ROM before flashing from other kernel, maybe it's that.

Or your ROM has some black magic ;p
[Nexus 5 Original Android Development] eng.stk:
You were the first ,thanks mate :highfive:
[Nexus 5 Original Android Development] unsivil_audio:
Dark magic? Definitely. :D Carbon Rom FTW. Carbon doesn't have an option for dirty flashing, it formats /system every new nightly (which I did, flash a new nightly).
[Nexus 5 Original Android Development] Spectrum75:
What matters is that Code Blue is becoming one of our first choices regarding kernel flashing. :cowboy:

Is it only my first impression or the latest build is a battery monster..?!

Not much time today due to work but 2% idle drain after 8 hours...? :good:
[Nexus 5 Original Android Development] imageMaster:
sync_freq freeze on Mahdi :(
[Nexus 5 Original Android Development] Vollspacken:
Is that one called a synq_freeze? it happens to me on every build with this kernel on mahdi too, the only thing it helps is to close the media-thing in the cache of active apps, the issue should be gone then.

But in this case it's the ROM and not the kernel that causes the freeze, am i right?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] eng.stk:
I dont know what media thing is that, but looks like something is using your cpu heavily... nwver got that on AOSP ROMs.
[Nexus 5 Original Android Development] eng.stk:
Well guys I'm getting some unwanted behavuor wih SIO...guess some fairness is needed, raw performance doesn't always cut it I guess. Trusty FIOPS will be back by default
[Nexus 5 Original Android Development] sirovai:
You're not the only one who has noticed that with SIO.
[Nexus 5 Original Android Development] daigoro64:
+1 here.
[Nexus 5 Original Android Development] eng.stk:
My latest test is like buttery butter: FIOPS is back and MSM_Sleeper was removed due to hiccups with MSM_Hotplug.

Runinig a Linaro GCC 4.10 kernel on a Sabermod GCC 4.10 is amazing, blazing fast.
[Nexus 5 Original Android Development] Yusei:
PM me to me and I'll test it for you.

;)
[Nexus 5 Original Android Development] nokiagye:
Sw2wa?
[Nexus 5 Original Android Development] PetritH:
Nope
[Nexus 5 Original Android Development] ali8383:
Nice performance , i hope battery same :) i just flash it on mahdi rom
[Nexus 5 Original Android Development] ali8383:
This kernel is really good , performance + battery life

Thank you for it
[Nexus 5 Original Android Development] omvir:
Omfg.... I'm getting an hour more battery life on r131 over r126... With very similar usage. Wow, this is just... Amazing. Will post pics soon. Have 5% still remaining :p

Edit:
[Nexus 5 Original Android Development] eng.stk:
Then clearly is something to do with your setup

You can try to chmod 0664 or 0777 see if it helps.

scripts go in /su/su.d in MM

Don't forget changing from 0.9.9.4 to 0.9.9.3 you need to uninstall the apk and clean any folders of Adiutor in sdcard

Also try with a lesser nunber like 90% for instance. idk if 100% on Adiutor is absolute 100%
[Nexus 5 Original Android Development] Primokorn:
Same issue? Same rom?
[Nexus 5 Original Android Development] Stevica Smederevac:
Samd issue, not the same rom.
[Nexus 5 Original Android Development] Spectrum75:
For those having problem with vibration setting on Kernel Adiutor :

Made some testing in Krexus Rom ( aosp based, no vibration setting included ),

With latest version of Kernel Adiutor --> no luck

With prev version 0.9.9.3 --> success :)

( bug already mentioned in Kernel Adiutor : https://github.com/Grarak/KernelAdiutor/issues/396

and https://plus.google.com/109413932407717501378/posts/JU7WRMxLTHb )
[Nexus 5 Original Android Development] marf28101995:
OT

That storage thought :D
[Nexus 5 Original Android Development] eng.stk:
blu_spark level: pro
[Nexus 5 Original Android Development] mr.ace:
any update for new mob30d factory images?i think google changed something in this for better peformance?right??
[Nexus 5 Original Android Development] nmlssit:
I flashed it along with r73, all fine so far.

Inviato dal mio Nexus 5 utilizzando Tapatalk