yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] swat4samp:
Are you kidding me :eek: Since when did the official site for downloads replaced the original kernel with bricked kernel? I never heard about that kernel before nor did i visit that kernel thread at all. I only have elementalx, franco and codeblue kernels and i flashed code_blue latest version over previous version. OR maybe, i may have flashed the same kernel version instead of latest one.

I will flash latest version once again after dirty flashing rom. I will post the log here if i get any random reboot. So please stop you-are-on-different-kernel solution :rolleyes:
[Nexus 5 Original Android Development] GtrCraft:
You downloaded the wrong kernel nothing wrong with the site. No previous of code_blue. You have bricked running in that log
[Nexus 5 Original Android Development] gippy2:
Nothing like being moaned at for being right is there..[emoji22]
[Nexus 5 Original Android Development] eng.stk:
Mate stop making other people idiots.

That log is from another kernel (TWRP kernel by the looks of it). Period.

This kernel (and any serious kernel testing) in not meant to be tested on secondary ROMs.
[Nexus 5 Original Android Development] ali262883:
I meant without app is it possible? Because I've always had problems with that app
[Nexus 5 Original Android Development] swat4samp:
Right, so you guys won't believe what i said and instead say i'm making others stupid. That's very generous. I already told youthat i have only 3 kernels, code-blue (247 and 253), elementalx and franco kernels on my phone. If there's any mistake from my side, it would've been that i might flash any of these kernels instead of original kernel. But you guys just say that its from bricked kernel and now you are saying its from TWRP kernel( which i have absolutely no idea at all). How could i possibly flash other kernel which i don't even have on my phone? Well, end of topic. From now on, i won't post any logs if i had any errors. I will continue to use this kernel no matter as i find it perfect for my phone. Its just that posting a log makes you identify the bug and might help you to solve bugs in the future. I guess posting logs isn't enough. I need to record a video before flashing the latest kernel to make you guys believe that i'm using the latest kernel. No disrespect for anyone as i know the truth and you guys wont believe by looking into the log.
[Nexus 5 Original Android Development] Hopper8:
I'm only coming in on the back end of this.. but, to make sure:

-Is the kernel on your primary ROM if using Multi-ROM?

-Did you re-flash the ROM before flashing kernel?

I assume traces of other things will appear in logs if these are not followed. I imagine you know what you're doing, no disrespect meant by asking simple questions :)
[Nexus 5 Original Android Development] gippy2:
Well at the very least there has to be a big misunderstanding..He didnt flash bricked kernel...But this is not code blue..So at the very least we can all agree on that ...My question is why after reading this would anybody think this is anything other than bricked ??????

[ 0.000000] Booting Linux on physical CPU 0

[ 0.000000] Initializing cgroup subsys cpu

[ 0.000000] Linux version 3.4.0-bricked-hammerhead-twrp-g7b77eb4 (showp1984@Unimatrix001-lnx) (gcc version 4.7.2 20120910 (prerelease) (Linaro GCC 4.7-2012.09) ) #1 SMP PREEMPT Fri Jun 6 17:29:04 CEST 2014
[Nexus 5 Original Android Development] GtrCraft:
Its not any of the kernels he mentioned, it looks like bricked or twrp
[Nexus 5 Original Android Development] swat4samp:
I absolutely mean no disrepect to those who ask any kind of question while debugging problems nor to those who react in other ways. It may sound obvious by looking into the log that i may use other kernel but that's absolutely not the case which is what i'm trying to explain. Thanks for asking patiently.

First of all, i'm not using multi rom. I'm using PA 4.5beta 1 with of course this kernel. I used 247 before. I just dirty flashed the latest kernel 253 over 247. So i didn't reflash rom before flashing kernel. I know if i use other kernel, i should dirty flash rom and then flash kernel. But as i was on the same kernel, i thought dirty flash kernel is enough. If that's the problem, i will definitely clean install kernel. But i really don't know why the log shows that i'm on other kernel. And, i know what i'm doing.

---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------

That's what i really don't understand at all. Had the log shown any of the kernels i have, it would've been easily understood that i might have flashed other kernels. But i really, honestly and will swear to anyone that i don't have those mentioned kernels at all.
[Nexus 5 Original Android Development] GtrCraft:
Dirty flash rom and then flash kernel, something went wrong for sure
[Nexus 5 Original Android Development] swat4samp:
Yup, will try that. I guess people really need to start believing others irrespective of what logs show :D
[Nexus 5 Original Android Development] gippy2:
[MENTION=4478993]swat4samp[/MENTION]...Can you do a screenshot of "your about phone "....This is a very unusual situation...
[Nexus 5 Original Android Development] Hopper8:
Just read the log file... I see. Good to see you around though mate! Hope you're doing well :)

In this case... I don't know. If it were me, I'd say that something is screwy in your system and would be clean flashing ROM + kernel. That's probably a smart thing to do seeing as you're facing a few issues anyway? Just make sure that your'e starting fresh, if you still get issues after that, grab a new log and make sure this one says code_blue ;)
[Nexus 5 Original Android Development] swat4samp:
Right now, i flashed elementalx kernel. Will dirty flash rom and then install latest code blue 253 and report it.
[Nexus 5 Original Android Development] q-doth:
I can't download frandom in the 1st post link, can someone give me anoter link ?
[Nexus 5 Original Android Development] gippy2:
LOl you would be murder in a court case...**** defending you..:laugh::highfive:

[MENTION=4851213]Hopper8[/MENTION].... Good to see you around dude..Im amazed the lads have still got their S2. [MENTION=1228651]fusionjack[/MENTION] .was talking about a new phone last xmas lol...
[Nexus 5 Original Android Development] Hopper8:
-removed-

That's a dropbox link, maybe it'll work for you. I had no issues with the OP link but oh well.

[MENTION=3873953]eng.stk[/MENTION], I hope that's ok. I'll remove the link if you'd like.
[Nexus 5 Original Android Development] eng.stk:
TWRP uses Bricked kernel and that's where the log it's from.

Also sometimes testing kernels in secondary ROMs can make issues like that.

Basically, you pulled the log from the recovery kernel.

End of discussion guys, move on ;)

No mirrors please, next time pm the guy.

Thanks.
[Nexus 5 Original Android Development] q-doth:
Thanks bro, i've already download from your link. :good:
[Nexus 5 Original Android Development] Hopper8:
Apologies. Link removed now.
[Nexus 5 Original Android Development] swat4samp:
Allright, you guys must believe me this time :D I dirty flashed rom and then installed latest code_blue 253. Took last_kmesg log and guess what. It still shows as bricked kernel just like my previous log :confused: While on stock PA kernel, i took the log and it showed the default kernel itself. So i guess, this kernel always shows the bricked kernel in that log. Hope we can end this discussion once and for all.

http://pastebin.com/xe7iMbM1
[Nexus 5 Original Android Development] eng.stk:
You're getting TWRP kernel again, just reboot the phone once after flash Code_Blue.

That's nothing wrong with the kernel, stop making affirmations without any technical background. It's annoying...

http://pastebin.com/bvyhfaDr
[Nexus 5 Original Android Development] swat4samp:
Here's the log which i took before flashing code_blue. I'm on elementalx at that time. It shows elemental itself in that log. http://pastebin.com/ZWDscbDN I guess it shows bricked kernel only for me alright. Sorry for annoying you. Don't take me wrong, i'm not telling that there's something wrong with this kernel. It's just that it shows that way in the log. Now that it only shows that way for me, its clear to end this discussion :good:
[Nexus 5 Original Android Development] eng.stk:
Really man, I'm really making an effort here...

Did you do as I said? No.

When you do" reboot to recovery "and flash a kernel, the last_kmsg will be of the last rebooted kernel, which is TWRP kernel.

This is because after you flash a file you press reboot on TWRP!

Just reboot to recovery, flash Code_Blue, go to ROM, normal reboot and the last:kmsg will be from Code_Blue...

This is true for Code_Blue, franco or any other kernel.

If you can't understand this simple reality, I give up.
[Nexus 5 Original Android Development] swat4samp:
I'm really really really sorry :( Its my fault, i usually check log after flashing kernel and rebooting to system straight from recovery. Now, after rebooting manually, the log is showing code_blue. I really didn't understand the reboot part, so i thought just rebooting from recovery would be fine. And you were right when you said, don't make assumptions without having technical background. Sorry once again. Hope you forgive me :o Thanks for having patience and explaining the real problem to me.
[Nexus 5 Original Android Development] alen1901:
Just to report, latest exp version. After 2 cycles, same settings like on r209, except blue_active governor. little worse battery - 4:17 hours of screen on time and 14% battery left. On r209 4:20 hours of screen on time and 20% left. I would say roughly 15min less screen on time with similar usage, but perfomance is way better on r253, phone is more responsive. Thumb up for this one. ;)

Sent from Pure Nexus 5
[Nexus 5 Original Android Development] eng.stk:
UKM

Very happy to announce that UKM is 100% compatible with Code_Blue, current version and the ones following.

Latest v3.1 beta build will be released when [MENTION=5658634]apb_axel[/MENTION] is ready, stay tuned :fingers-crossed:

Very proud to be on the same team as [MENTION=5658634]apb_axel[/MENTION], [MENTION=4544860]osm0sis[/MENTION] and my friend [MENTION=3685904]ak[/MENTION]
[Nexus 5 Original Android Development] RamDrt:
Yes! Been following this and was excited to see you were beta testing to help iron out any errors.
[Nexus 5 Original Android Development] hjjiang:
hey does any1 know of a good app to keep this kernel up to date? instead of coming to the thread?
[Nexus 5 Original Android Development] GtrCraft:
There is no app
[Nexus 5 Original Android Development] Gallardo994:
Just amazing. That's all I can say.
[Nexus 5 Original Android Development] ¶ha€dru$:
synapse is crazy (awesome)! just when i thought I actually knew about advanced settings..

:cheers:
[Nexus 5 Original Android Development] Hopper8:
Awesome :) the funny thing is, I flashed ukm about 5 hours before you posted that, on a wild guess that it would work based on the UKM OP... Now it's official :D nice work! Loving Synapse :)

Sent from my Nexu5
[Nexus 5 Original Android Development] Nucleotide:
That's a cute story. Thanks for sharing. :good:

As I said, it was my own personal experience with it so far. I'm not complaining - in fact I couldn't give two ****s.

For you it may be better. That doesn't mean there is something wrong with my setup. Everyone has a different setup and will experience difference results.
[Nexus 5 Original Android Development] psp9000333:
how do you use synapse? do you flash the UKM zip file? I downloaded it from androidfilehost but it said it was for the nexus 4. I can't risk bricking my device.
[Nexus 5 Original Android Development] vsot13:
There is no app. And whats wrong with the thread?:p

http://xdaforums.com/showthread.php?t=2736986 This is good place to start

From my N10
[Nexus 5 Original Android Development] Audioboxer:
UKM 3.0 and synapse are saying both mpdecision and MSM hotplug are enabled. I take it that's a bug? (default kernel settings)
[Nexus 5 Original Android Development] Hopper8:
Where are you checking? Mine looks like this :

And that's only the replacement hotplugging. But are you looking somewhere else as well?

Sent from my Nexu5
[Nexus 5 Original Android Development] chazall1:
Long time kernel user on nexus devices. Installed code blue yesterday and I must say this is running very very nice. Thanks! wow!
[Nexus 5 Original Android Development] Audioboxer:
A couple of restarts of Synapse and it went away. Was on that page prior to MSM hotplug.
[Nexus 5 Original Android Development] Jamith:
I'm trying to use Synapse with the experimental kernel and the latest SlimKat but it say that my kernel or ROM doesn't support the app, I'm missing something or this doesn't work with my ROM?
[Nexus 5 Original Android Development] 11wallace11:
Don't forget to flash the UKM zip provided in the main app thread here on XDA.
[Nexus 5 Original Android Development] modstorm:
Been running r253 + Frandom + Slim for 2 days and so far so good! Performance is great and the battery seems to be holding up well too (however I haven't tested it enough to make a solid claim).

I was wondering, is it possible to add higher frequency GPU steps such as Uber has? Are there any known issues with doing so? On all the past devices I've had, overclocking the GPU made the phone perform much better so I'm assuming the same will hold up for the N5.

Great work on the kernel ! :)
[Nexus 5 Original Android Development] swat4samp:
[MENTION=3873953]eng.stk[/MENTION] Had random reboot while playing videos on youtube. Also on some videos, i noticed green lines on top and bottom of the video.

http://pastebin.com/hg5EpuxN I'm on PA4.5 beta1 with default kernel settings as usual
[Nexus 5 Original Android Development] famazi:
New ukm is out enjoy
[Nexus 5 Original Android Development] eng.stk:
No Overclock of CPU or GPU, not worth the trouble.

You had a crash on video subsystem. Tell me a video so I can test.
[Nexus 5 Original Android Development] swat4samp:
Are you asking about the video right before reboot appeared or the one with green lines? In both cases, i really don't remember the videos as i watched it yesterday night before sleep :o Next time, i will post the log along with video :good:
[Nexus 5 Original Android Development] Gallardo994:
YouTube has viewable history. You can check that by time or anything else.
[Nexus 5 Original Android Development] swat4samp:
Unless i turned it off ;)
[Nexus 5 Original Android Development] modstorm:
Thanks for your reply :) So any GPU overclock gains will be negligible ?
[Nexus 5 Original Android Development] eng.stk:
I doubt it's kernel related (in the way of added commits). But even then obviously if I can't test/replicate there's no issue...

Log in this case doesn't help much, just shows a video subsystem crapping himself.

But I would like to test those videos since I don't have such issues (and neither the other people using Code_Blue).

In our device, the only thing you will gain with OC is instability, more heat and less battery.

To gain 2 fps or a bunch of points more in Antutu? I don't need it.
[Nexus 5 Original Android Development] swat4samp:
Maybe i derped youtube too much that it restarted at some point :o Will report as soon as i get the issue again with the video
[Nexus 5 Original Android Development] dometech:
I'm using the last codeblu with Purity... I have the problem with lighting sensor because measured always a low values of lux... I do not use the auto regulations of light... Someone have found this problem?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] jyuuken:
Hi guys, im curious about frandom. Any link about it? Cant seem to find a link
[Nexus 5 Original Android Development] :
http://xdaforums.com/showthread.php?p=54744568
[Nexus 5 Original Android Development] ¶ha€dru$:
one persistent problem i notice is when i have flashed frandom then the media server acts up. maybe it world be best to force stop media scanner. anyone else notice this?
[Nexus 5 Original Android Development] linozoid:
poor battery life... using latest version.. ??
[Nexus 5 Original Android Development] -DroidIsDNA-:
This is not enough information for you to make a claim like that. The dev isn't a magician who can just make your battery life better, especially if you provide so little information.
[Nexus 5 Original Android Development] Andromendous:
My battery life is great, almost got 6hrs screen on time with pretty good usage.
[Nexus 5 Original Android Development] androidfreak007:
Better than ever before. Awesome kernel.

Running r253, frandom activated, stock settings and latest purity.

Now, playing around with synapse.
[Nexus 5 Original Android Development] linozoid:
haha... maybe my n5 battery is totally dying now...
[Nexus 5 Original Android Development] bknightt:
to apply frandom simply flash it right after having flashed the kernel correct?
[Nexus 5 Original Android Development] vsot13:
Correct

Sent from my Nexus 5
[Nexus 5 Original Android Development] UnicOrnseeD:
With this kernel I'm getting 16 hours of battery with 6.5 screen on time! Benchmarking [MENTION=564321]323[/MENTION]37 on antutu
[Nexus 5 Original Android Development] Arju:
What rom and kernel settings?
[Nexus 5 Original Android Development] UnicOrnseeD:
I'm running purity and stock kernel (changing settings in synapse kind of made things worse) w/frandom. Basically made my N5 2x better!

Sent from my Nexus 5
[Nexus 5 Original Android Development] bigknowz:
Audio derp resolved

The issue I had with audio hiccups on radio handoffs is gone since changing to 2 cores min / 1.7 GHz max with screen off. Tested on Rocket Player and Poweramp, wich is impressive considering PA is known to be a CPU hog. Thanks [MENTION=3873953]eng.stk[/MENTION].
[Nexus 5 Original Android Development] marjune23:
You said a while ago you're using this kernel, then you've just mentioned your on stock kernel...

That's confusing now mate...

Edit: Sorry he was asking for kernel settings...

I just woke up a while ago while reading and commenting... Half asleep in short ?
[Nexus 5 Original Android Development] UnicOrnseeD:
Stock settings. It was asked what kernel settings I was using. Sorry about the confusion

Wouldn't be posting in this thread if I was on a different kernel

Sent from my Nexus 5
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r276

All right crew!

Here we go for another round!

I'm finally debuting dyn_hotplug: Dynamic hotplug driver for hammerhead (aka blu_hotplug), heavily based on stratosk amazing work on the mako.

This is a conservative yet powerful hotplug solution, performance is +/- the same, but temps will go down and battery will go up.

I'm using min 2 cores online (no hotplug touch boost, that's for cpu-boost), max 1 core screenoff. I'm sure you will like it.

Also, flar2 msm_sleeper is enabled to keep fret at 1190MHz on screenoff, powersuspend available on hybrid mode (autosleep and lcd hooks).

Lot's of other goodies and fixes, check changelog!

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!﻿
[Nexus 5 Original Android Development] gippy2:
Awesome... Been waiting for this... I'm on it sir.... Awesome kernel.......
[Nexus 5 Original Android Development] eigokyoukan:
Sounds like fun on a bun! Thank you good sir, looking forward to playing with this! :D
[Nexus 5 Original Android Development] marjune23:
Thank you mate for this gigantic changes...

Time to test and and report back after...
[Nexus 5 Original Android Development] refedit:
You're great

"És ganda máquina" :)
[Nexus 5 Original Android Development] PetritH:
Wow, this thing is smooff as something that's really smooth... great job man.
[Nexus 5 Original Android Development] Hopper8:
Awesome work! Time to test ? just wondering, in synapse the GPU indicates that it's at 27mhz quite often (see screenshot).... I assume this isn't the case, and it's a bug with synapse /UKM?

Sent from my Nexu5
[Nexus 5 Original Android Development] eng.stk:
No bug, that's the correct freq, 27MHZ aka gpu min standby freq.

That's auto by the chip, you can only change min "work" freq and max "work" freq
[Nexus 5 Original Android Development] UnicOrnseeD:
Wondering what the easiest way to reset synapse default kernel settings is.

Sent from my Nexus 5
[Nexus 5 Original Android Development] eng.stk:
Go to Syanpse settings and untick Apply on boot. Reboot. Profit :good:
[Nexus 5 Original Android Development] Hopper8:
Ah my mistake. I read the setting below it as minimum gpu freq, but instead it's the minimum freq that it scales down to, as in the minimum apart from standby freq. Cool thanks :)

Sent from my Nexu5
[Nexus 5 Original Android Development] bknightt:
my device was derping everytime I opened boom beach or clash of the clans, could it be due to the min core setting to only 1? sorry I don't have a log to provide, asking because it only returned to normal after reset by key, not claiming to be fault of the kernel whatsoever, just wondering if it might be related. I don't want to bash the awesome work of eng.stk, I'm not claiming it's kernel's fault, please keep this in mind.

also, tks eng.stk for the great work.
[Nexus 5 Original Android Development] Aerowinder:
Not seeing it on my end.
[Nexus 5 Original Android Development] bknightt:
you're using stock settings with frandom and ukm? tks for the feedback.
[Nexus 5 Original Android Development] J_Whit85:
Any way to get the stock auto brightness back?
[Nexus 5 Original Android Development] gippy2:
Have you tried gamma in synapse
[Nexus 5 Original Android Development] J_Whit85:
Synapse tells me no UCI support detected
[Nexus 5 Original Android Development] gippy2:
You need to flash that first ....
[Nexus 5 Original Android Development] J_Whit85:
Flash what
[Nexus 5 Original Android Development] gippy2:
Sorry I'm tired just got in from work..The UKM 3.1 zip from the synapse thread ...

http://xdaforums.com/android/software/zip-synapse-script-universal-kernel-t2736986
[Nexus 5 Original Android Development] BTT8:
Still holding on to 209 since it has treated me so well. But this latest version has got me all curious George about it.
[Nexus 5 Original Android Development] indian84:
So if I am correct, no need to flash fardom now?
[Nexus 5 Original Android Development] Hopper8:
Errm. Not sure why you say that? Pretty certain you still need to flash it if you want frandom.

Sent from my Nexu5
[Nexus 5 Original Android Development] Nucleotide:
r276 is very nice! I'd give it a crack. :good:
[Nexus 5 Original Android Development] RajRockyBalboa:
Boot Loop

stuck with a weird problem. Had flashed r253 and was experimenting with some kernel managing apps (Trickster and Synapse and Kernel Tweaker). Got stuck on bootloop (reboots on animation after google logo) flashed multiple kernels....got it working with r179 beta....but flashing any other kernel (Code blue latest r276 included) results in bootloop...tried other kernels as well....none work but only r179 does...:silly: tried replacing my original build.prop as well from the stock rom..same result...don't want to reflash the entire rom...any suggestions are welcome...Thanks...already tried removing all kernel managing apps and setting default settings.
[Nexus 5 Original Android Development] theflamemaster:
Recomended kernel manager

what kernel manager do you guys use. thank you.
[Nexus 5 Original Android Development] hooliganx:
1 page back...

http://xdaforums.com/showthread.php?p=54811371

n5sk7.2.Robbie-08.12gapps199art

EX1.04twrp2.7.1.0rd2.08

----------------------------------------------------------------------------

have doubts about Slim? click here:

http://slimroms.net/index.php/faq
[Nexus 5 Original Android Development] Andromendous:
Sometimes i think things get so messed up theres nothing you can do but fastboot back to stock and start over. But if you want to try a last resort, if you use twrp, might work with clockwork maybe, you can try this.

By the way, what rom are you using?
[Nexus 5 Original Android Development] RajRockyBalboa:
I am on stock rom. For last resort what should I try? Flashed Furnace Kernel and it's working but want to come back to my fav Code blue...:(