yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Tommy-Geenexus:
Aokp is CAF based, so it won't work.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] estallings15:
TIL. I hadn't realized they'd switched. Has the whole world gone mad?
[Nexus 5 Original Android Development] Tommy-Geenexus:
Yeah i don't like it either.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] chikimonke:
Makes sense if you think about it, as Roman works for CM now.
[Nexus 5 Original Android Development] estallings15:
It's confirmed. The whole world has gone mad.
[Nexus 5 Original Android Development] fcisco13:
Roman CM?? Really??

Whatchu talking bout willis!
[Nexus 5 Original Android Development] chikimonke:
Since January http://www.androidpolice.com/2014/0...under-roman-birg-joins-cyanogen-incorporated/
[Nexus 5 Original Android Development] 77claudio77:
Is it compatible with stock rom?

any problem with it?

Thx
[Nexus 5 Original Android Development] PetritH:
yeah, no issues
[Nexus 5 Original Android Development] kowloon12:
This! I was was addicted to s2w but I had to stop using it because this very problem..

Anyone else? Someone with a workaround?
[Nexus 5 Original Android Development] SnoopHTC:
F2FS

[MENTION=4195844]show-p1984[/MENTION]

Hello,

First, i use your kernel with Mahdi ROM and IT'S PERFECT!! THANKS!!!

Tried f2fs from here and when i flash the last build, i have this message : "Type password to decrypt storage"

It's OK with AOSP kernel and if it's correct, with an old build of your kernel, it's ok.

i also tried to flash : 1 mahdi 2 aosp kernel 3 your kernel and 1 mahdi 2 aosp kernel 3 reboot and first setup then flash your kernel (with clean flash eatch time)

If you have time, can you check why? I can test and repport or send a bug file if you want.

Thanks by advance.
[Nexus 5 Original Android Development] garynych:
f2fs work on 3.4.86

after update source to version 3.4.89 ,f2fs not work at all kernel :( (all say "type password to decrypt storage")
[Nexus 5 Original Android Development] ausaras:
Touch screen active during call

I think I found a bug.

During a call, the screen is turned off by the proximity sensor. But the phone still registers touches.

So, even though the screen is off, I am able to end the call by pressing where the END CALL button is.

I am on Slim build 5 with latest Bricked build (0406). But i think this behaviour exists in older versions, too.

Thank you!
[Nexus 5 Original Android Development] t0mas_:
there is a patch somewhere to stop touchscreen registering touches while on call, showp also commented about it a while ago, search the thread to get more info...

---------- Post added at 11:49 AM ---------- Previous post was at 11:43 AM ----------

this:

http://xdaforums.com/showthread.php?p=51403620
[Nexus 5 Original Android Development] ausaras:
Mmm...i can't seem to find the patch.
[Nexus 5 Original Android Development] t0mas_:
hehe the patch is in some other kernels code. not included in bricked. the link is just to showps comment on it
[Nexus 5 Original Android Development] yyz71:
Is faux sound working with this?
[Nexus 5 Original Android Development] yyz71:
Cool thanks:good:
[Nexus 5 Original Android Development] Phazmos:
Yyz - like the rush tune?
[Nexus 5 Original Android Development] Garrykd:
Hi Phazmos,

YYZ is the code for the Toronto international airport.....but seeing as Rush is from Toronto it might be related.

But that's just a guess.. [MENTION=3866104]yyz71[/MENTION] would know best
[Nexus 5 Original Android Development] Phazmos:
Didn't know that was the code for an airport, but I'll bet a buck that was what rush had in mind.

Makes sense now!
[Nexus 5 Original Android Development] yyz71:
Yep that's right.. From moving pictures 1982
[Nexus 5 Original Android Development] spica123:
Best kernel and app available! Tried many other but nothing compares.
[Nexus 5 Original Android Development] zz_marcello:
Thats true!

And the best is together with Bruce AOSP version of CM11 your can combine it even with the latest Cyanogenmod nightlies.

http://xdaforums.com/google-nexus-5/development/rom-kernel-linaroquickbooot-t2716428

Just flash Bruce CM11 Nightly and Bricked Kernel afterwards.
[Nexus 5 Original Android Development] spica123:
Hope Dennis will have some time to update grouper for latest KitKat as well. Maybe this only makes sense when 4.4.3 is released.
[Nexus 5 Original Android Development] DevShaft:
Yes, it's the stock kernel.
[Nexus 5 Original Android Development] davy917:
Just bought KControl.. Is it compatible with Nexus 5?
[Nexus 5 Original Android Development] george241312:
Does it work on aosp?
[Nexus 5 Original Android Development] fatappel:
Just got 5 hours screen on time with normal but heavy usage w/ latest...

Sent from my Nexus 5
[Nexus 5 Original Android Development] show-p1984:
Inofficially: yes.

Officially: no, but that is just a change in the description with the next update.

Yes.
[Nexus 5 Original Android Development] fatappel:
[MENTION=4195844]show-p1984[/MENTION] I'm sticking with you. Keep up the good work.

Sent from my Nexus 5
[Nexus 5 Original Android Development] davy917:
Hmm getting bootloop on latest stable.. Running Cataclysm and latest CWM.

I've never pulled logs or anything before, how do I do that so I can actually be helpful?

Edit: The only thing I changed since last flash was flashing the latest CWM, so I flashed TWRP back on it and now it is all good. Something with the .zip doesn't seem to be playing right with the latest CWM, I tried other kernels and I didn't get the bootloop.
[Nexus 5 Original Android Development] shri_chanakya:
Must say this is awesome kernel. Paired with omni rom.

Have exchange server with push. Google sync always on.

Thank you...
[Nexus 5 Original Android Development] show-p1984:
Since it's 7am, I am just dropping in to leave this:

[YOUTUBE]APR6iR3QnBc[/YOUTUBE]

Touchscreen driver force on in sleep by flar2.

Furthermore I ported back nearly everything (except the algorithm itself) from s2w2, which should make this s2w the easiest to port to other devices, ever.

It's still early, but I wanted to show off something :p

Now gn8 :)
[Nexus 5 Original Android Development] davy917:
I see this error in KControl when going into GPU settings, does it just mean we can't change any GPU settings yet?
[Nexus 5 Original Android Development] show-p1984:
Exactly. I am working on that since the driver changed a bit too much for KControl to handle this automagically.
[Nexus 5 Original Android Development] davy917:
[MENTION=4781351]shri_chanakya[/MENTION] wtf???? That battery life seems almost impossible dude. You're on pace for 9 hrs SOT on a 2300mAh battery. Something doesn't add up.
[Nexus 5 Original Android Development] shri_chanakya:
I too thought so but still has 39% remaining with almost 5 hrs screen on with total 16 hours of use. Won't be charging it till it goes to 2%. Will take screenshot and share again. let's see ...
[Nexus 5 Original Android Development] DevShaft:
That's looking good. Nice surprise (for me at least) to wake up with. Thanks and sleep well ;).
[Nexus 5 Original Android Development] jaco1975:
I am delighted with this kernel.tiene consume very good and performs very well in my Rom thanks

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] leoaudio13:
Could you mind share your settings ? Much appreciate man!
[Nexus 5 Original Android Development] noonecanhide:
Someone said that this kernel is compatible with CWM, but in it's description it says AOSP ? :)
[Nexus 5 Original Android Development] IharpI:
Do you mean cm?

The install script should make it work with both.

If not I have compiled my own for cm11.
[Nexus 5 Original Android Development] leoaudio13:
I can't wait for the LG G2's Knock Knock feature.
[Nexus 5 Original Android Development] tibere86:
I assume on show-p1984 stock kernel settings, correct?
[Nexus 5 Original Android Development] DroidIt!:
Another great combo is SlimKat + Bricked + kcontrol. The Slim team based their kernel off of Bricked, so whether you use the Slim kernel or Bricked, kcontrol works great for both. :good:
[Nexus 5 Original Android Development] jlevy73:
This kernel is stunning. Been averaging about 6 hrs of SOT with terrible 3G reception. With another kernel was only able to get 4 hrs SOT. Thanks Dennis.
[Nexus 5 Original Android Development] janres155:
Can you share your settings? I am comparing different setups. :)
[Nexus 5 Original Android Development] f4bio:
[MENTION=4195844]show-p1984[/MENTION]

I see so many kernels in this section updated weekly and your last update was roughly 2 months ago.

Aren't there any fixes, updates, whatever worth merging or needed?

Don't get me wrong, I am on bricked since forever and I guess it is a good thing if you don't need to fix anything.

I'm just wondering :)
[Nexus 5 Original Android Development] Splder:
I'm facing a small problem

If I turn screen off single core off then I get random reboots when the screen is off

Has anyone else faced this problem
[Nexus 5 Original Android Development] RobbieL811:
I too would like to see more development on this kernel. It is awesome as it is, but could possibly be better with more work. On the other hand though, you never know what might be happening in his personal life. That may be a reason that he hasn't been around in a while.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Splder:
here is a last_kmsg after the random reboot
[Nexus 5 Original Android Development] EdgA#1:
And we wait for the CAF version ;)

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] jlevy73:
I'm running it as pre-configured by the OP (DT2W and S2S off).
[Nexus 5 Original Android Development] show-p1984:
Show me something that is not working / can be improved and I will.

Otherwise: writing new code takes time.

I just refuse to update this kernel with meaningless updates, where the end user has no gain other than seeing 50 new commits in the changelog. As a result of that this kernel is stable. I just don't need to push 4 hotfixes a week that revert 10 commits of the 50 meaningless ones that got pushed :p

Last boot reason: wdog_reset

You got bitten by the watchdog.

I will take a look at the code, but this usually indicates a hw issue. You probably set too low voltages which are unstable with > one core at low clocks (which would be the case if you disable screen off single core and the screen is actually off)

Oh right. I totally forgot about that. I am currently plagued with hw failures. 4 of the new HDDs I bought for my basement-buildserver show signs of disk cache errors and therefore lead to data corruption. Searching for the issue (meaning: testing each RAM module on it's own on errors, testing each hard disk for block errors, updating the raid controller firmware, checking power supplies, checking cables, the backplane, etc etc etc), dealing with the RMA process and backing up data + slowly hot swapping all drives has kept me busy the last weeks.

Now it seems to be proven that it's either a fw bug, or hardware fail of 4 Monday morning products.

That much luck... I should have filled out a Lotto ticket instead of ordering hard disks that day. :)
[Nexus 5 Original Android Development] Splder:
I was running everything 100% stock no uv just turned that 1 setting and I get random reboot every time I keep screen off for a long time

I can undervolt normally - 75 mv and my phone never reboots but even at stock voltages it still reboots if I turn single core off

I even used trinity kernel at - 75mv and that keeps 4 cores on so I don't think it could be a hw problem

Maybe if anyone else can report if there running it fine with single core screen off?
[Nexus 5 Original Android Development] f4bio:
yeah... that's what I figured :) thanks for confirming
[Nexus 5 Original Android Development] DoesntPostAThing:
I kind of like it this way. Excessive updates for minor details usually end up with a bunch of complaints, then I end up hopping between two versions only to have a "fixed" version come out after a day of flashing back and forth, and then after only a few days of stable use another update comes out. Bricked is fine as it is, and noticeably faster than anything in Riptide, the only one that could match current performance on Bricked is stock kernel. But that's boring.
[Nexus 5 Original Android Development] Tommy-Geenexus:
[MENTION=4195844]show-p1984[/MENTION]

your thermal control is the best invention ever made for gamers like me :P

Sent from my Bricked™ Nexus
[Nexus 5 Original Android Development] DroidIt!:
Might be a noobish question as I'm sure there's resources out there :) but is there a central place for what all the different settings do and what recommended settings are for kcontrol + bricked. Haven't looked into TOO much myself yet, just kind of curious.

from my N5
[Nexus 5 Original Android Development] RobbieL811:
I have wondered this too. I just assumed that the way that it came when installed were the recommended settings. I would like to try to learn a few more things about tuning this kernel and his version of MP Decision.
[Nexus 5 Original Android Development] DoesntPostAThing:
What is up with these logs:

05-26 17:51:55.561: E/PowerHAL(868): touch_boost: failed to send: No such file or directory

Fills up the logcat as soon as I touch the screen. Running AOSPA, but I've never seen these before, and touch boost is a kernel thing, right?
[Nexus 5 Original Android Development] show-p1984:
http://xdaforums.com/showpost.php?p=47402434&postcount=21
[Nexus 5 Original Android Development] DoesntPostAThing:
Thank you. Nothing to worry about then I guess.
[Nexus 5 Original Android Development] Pretoriano80:
I agree with you, if ain't broken don't fix it.

Only thing still missing is color profiles support in KControl. And regarding gamma control i know that myfluxy removed the negative values from the code (and i guess he was right about it because until now nobody proved that both positive and negative values are needed) but afaik not all kernel developers updated their code with this change, maybe only those that base their work on cyanogen.
[Nexus 5 Original Android Development] yak84:
Hello to all, are the screen colors and screen dimmer are like in the stock Google kernel?

I mean after flashing and without changing kernel settings.
[Nexus 5 Original Android Development] gpvecchi:
[MENTION=4195844]show-p1984[/MENTION]: have you changed your mind or CAF version is still on its way? Thank you!
[Nexus 5 Original Android Development] maddes1402:
http://xdaforums.com/showpost.php?p=52920757&postcount=1790
[Nexus 5 Original Android Development] Janzen254:
I think the minimum brightness is lower with Bricked.

Colors are the same but you can adjust them.
[Nexus 5 Original Android Development] yak84:
Yeah after I've searched for minimum brightness (which I should have done in the first place) I found that indeed my eyes not fooling me and the screen is less bright.

Is there a setting in Kcontrol or a file in sys that can be changed in order to get the stock brightness levels back?
[Nexus 5 Original Android Development] Janzen254:
Why can't you just increase the screen brightness setting?
[Nexus 5 Original Android Development] t0mas_:
since you kind of asked :P

there is still a problem with touch screen registering while on call if I'm not mistaken. also power button toggle and/or timeout would be great. I know there are patches out there you know about, you did comment on it a while a go. but maybe there is another/better way of doing it?
[Nexus 5 Original Android Development] yak84:
[MENTION=4195844]show-p1984[/MENTION], I have a little bug to report.

It happened twice before , cpu(0) min freq got stuck @960MHz (mpd boost freq) without me changing anything in kernel settings.

I've attached bug report zip file with logs.
[Nexus 5 Original Android Development] show-p1984:
New beta up, which fixes one instance where this issue could occur. (If it doesn't fix your particular issue check all apps that might interfere with cpu core-states and report back)

Edit:

There was an issue with the upload. I am not at home currently and therefore can't fix it tonight.

I have said this multiple times: This is not a kernel issue. The kernel relays ALL input requests to Android, which is perfectly ok. Android should now decide which ones to ignore based on the device state. A kernel solution for this is possible, but it's simply the wrong tool for the job.

The minimum brightness allowed, which you can manually set, is lowered. This doesn't affect auto brightness though. The auto-brightness blmap is slightly (and I really mean, SLIGHTLY) lowered for very low ambient light levels and cannot be overwritten/changed without a recompilation. The auto-brightness blmap for mid to bright ambient light levels remains untouched.

Nobody should have an issue with this change. The blmap change simply slightly lowers the screen brightness when it's pitch black around you anyway and you don't need an eye cancer laser++ in your hand where an eye cancer laser+ will suffice just fine.

In manual mode the static change of the min allowed brightness can be undone by moving the slider a bit further to the right.

If you want to recompile the kernel without the auto-brightness blmap change, then revert this commit:

https://git.bricked.de/bricked/hammerhead/commit/c36f9aeb14c02366211a4d08434b5a406f78d0bf

If you want to recompile the kernel without the min allowed brightness change, then revert this commit:

https://git.bricked.de/bricked/hammerhead/commit/d09e1426bc65bfda8dd3ee1d68abec5d0d7e2dbe

afterwards recompile with: '. buildme.sh <branch you are on>'
[Nexus 5 Original Android Development] RobbieL811:
Did you take the beta from today down? I tried to flash and phone wouldn't boot. Came back to redownload thinking it was a bad download, and it wasn't there. Was something wrong with it?

Edit - Nevermind. I see your edit up there now. I didn't read like I was supposed to. Sorry.

---------- Post added at 06:54 PM ---------- Previous post was at 06:23 PM ----------

Here is a build of today's update. It works. I flashed already. Nothing extra except Show-P1984 commits from today. http://d-h.st/Vza
[Nexus 5 Original Android Development] ausaras:
So, I take it the touchscreen registering during call issue still exists?

Is it possible to let me know where to find the patch to fix it?

Thank you!
[Nexus 5 Original Android Development] SnoopHTC:
F2FS

Hello, any news about F2FS?, I found that:

- https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.4.91

- https://github.com/flar2/ElementalX-N5/commit/7c4736d72213073747f334af9050fd3114f8eb98

I don't know why but when I flash first mahdi ron then AOSP-F2FS kernel then ElementalX 0.41, it's ok.

And it's possible to have the full version of linux kernel in "about" (currently we see 3.4.0)?

Thanks by advance. :)
[Nexus 5 Original Android Development] show-p1984:
Fixed it before breakfast :)

Copy and paste hit me hard in the buildscript for jenkins... (zImage vs zImage-dtb ftw -.-)

http://bricked.de/index.php?action=kdownload&device=hammerhead&release=beta&type=aosp
[Nexus 5 Original Android Development] Splder:
still same problem on latest 02/06/14 EXP build

here is a last_kmsg from the latest beta still says i go bitten by the wdog :(

what is msm_pm_enter: cannot find the lowest power limit or is that normal
[Nexus 5 Original Android Development] t0mas_:
i know you have, and I read what you wrote. but the problem is getting rom developers to do something in that direction. because from their point of view they would be dealing with a problem that a kernel function created. I'm not saying that your solution is bad in any way, I was just trying to ask you to consider another if there is maybe a third option. I'm sorry if I offended you, it's just that I like your kernel and s2w very much, and that problem is quite annoying. and of course, thank you for all the work you put in.
[Nexus 5 Original Android Development] DroidIt!:
About in call touch events, if you think about it, it really would be a fix for ROM dev's. If show-p did do a kernel fix then it would be ONE universal set of values for ALL ROMs. I could see that creating all kinds of problems. The ROMs don't even all use the same dialer and the ones that do use aosp based, some of those are quite tweaked as well. So, just my opinion, but I think kernel side would be a bad idea. Sometimes my cheek hits the dial pad when I'm in a call, but I personally would ask in my ROM thread if it happened enough or if it bothered me enough. Just my opinion. :)

from my N5

---------- Post added at 02:12 PM ---------- Previous post was at 02:01 PM ----------

Just as another thought. If you really like your rom and bricked and don't wanna switch either and the main problem is the dialer for you, there are alternate dialer's in the play store. I personally love the rom I'm on with bricked, so I don't think I'd change either, so that's the route I might look at. I love my rom but I still do replace/delete some system apps to fit my particular wants. So, I don't think there'd be a problem with trying an alternate from the play store. :good:
[Nexus 5 Original Android Development] ix3u:
I have only had this problem when I'm in a call and the dialpad is open, which is frustrating if on a call where you have to listen and select options, but on a regular call never had any problems.
[Nexus 5 Original Android Development] chikimonke:
4.4.3 Kernel Source is out https://android.googlesource.com/kernel/msm/+refs
[Nexus 5 Original Android Development] estallings15:
Now THAT is good news.
[Nexus 5 Original Android Development] show-p1984:
Nope this is:

Beta for 4.4.3 is out! (Haven't flashed yet, didn't get the official update. Kinda *****y about seeing how long it takes to reach Germany :p)

http://bricked.de/index.php?action=kdownload&device=hammerhead&release=beta&type=aosp
[Nexus 5 Original Android Development] Luigi_2:
now THIS is good news
[Nexus 5 Original Android Development] PhoenixFx:
Cool :good:

Flashed it over stock 4.4.3, booted and working alright so far (15 mins). Will report if I run into any issues.

S2W works :D! Couldn't wait till I got that working again..
[Nexus 5 Original Android Development] raubkatze:
Thanks for the great work!

Flashed the latest build over self-compiled 4.4.3 PA - work fine so far. Bought an app to support :)
[Nexus 5 Original Android Development] Remoteconcern:
Confirmed. Kernel working well on 4.4.3. Love having it back.
[Nexus 5 Original Android Development] PetritH:
Thanks as usual show-p
[Nexus 5 Original Android Development] DroidIt!:
I've been running the last version of bricked + slim for the last 2 weeks and not seen any issues with that one either :) Best kernel I've seen by quite a stretch. No lags, reboots, battery drain or any other problem. Great work here show :)

from my N5
[Nexus 5 Original Android Development] EdgA#1:
Running stock 4.4.3 with xposed and last bricked...

What can I say, as always! ! Liquid and saving together! For me the best kernel

Oh.. Now i found a bug?!

If I adjust the volume louder in kcontrol point (8), it takes on them, but if I then use the volume keys up / down do, the controller reverts back to 0 in kcontrol
[Nexus 5 Original Android Development] 26.2man:
CM11

How does this kernel play with the latest nightly of CM11? Just curious since there arent many that have updated themselves for 4.4.3
[Nexus 5 Original Android Development] Silentbob999:
For CM11 you need to search for a "CAF" kernel. Don't try any kernel that doesn't mention being specifically for CM & CAF.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] Alcibiade:
You can use it Bruce's latest built of CM11. It's a non CAF version of CM11 and has been updated to 4.4.3 on June 6th.

Until we finally have a CAF version of Bricked :)
[Nexus 5 Original Android Development] CallumMarks77:
For 4.4.3 doni flash stable or exp?
[Nexus 5 Original Android Development] DroidIt!:
Sounds like both are working fine. I'm on the stable and it's perfect with 4.4.3 and others are on the beta and it's working good also. [emoji106]

from my N5